What are the known limitations of the Zuora sync to ChartMogul?

The two most prominent issues with the Zuora integration are:

• When a transaction (invoice, credit memo, etc.) is deleted in Zuora the Zuora API does not maintain the transaction. In other words, there is no indication that the invoice was deleted - thus deleted items persist in ChartMogul. We highly recommend that transactions are cancelled or voided instead of being deleted when possible. We have developed an optional solution to this issue that require you to enable notifications through custom events.

• The Zuora API does not support time stamps when notifying of the service period for a subscription. This can lead to a couple situations where the MRR is off from what is expected.

  1. On prorated invoices (especially where the duration of the service period is approaching zero) this can lead to a difference in what Zuora reports for MRR due to the impact of the time difference.

  2. When a lot of amendments come in for a subscription all with the same date, it can create an ordering problem in ChartMogul given ChartMogul usually requires accurate timestamps in order to know how they order things before calculating MRR.

When sending Zuora data to ChartMogul, we strongly recommend setting your churn recognition setting in ChartMogul to When the subscription ends in your billing system (default). This allows us to properly set the churn date that the billing system provides. This is a global setting and will affect all data sources.