What are the known limitations of the Maxio integration?

When sending Maxio 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.

Components and other add-ons are not tracked separately, but are combined into the overall subscription.

The Maxio API does not support notification (webhook or events) or a polling mechanism for us to identify when a customer has been deleted from Maxio. Thus, it's currently not possible for SaaSync to remove customers from ChartMogul that get deleted in Maxio (after the initial sync). These customers can be manually deleted in ChartMogul's user interface.

The Maxio API does not provide a time stamp along with the date they provide on service periods for an invoice line item. The impact of this is seen when a customer has a prorated invoice and it's especially noticeable when the service period for the proration is short in duration. We attempt to use a system timestamp associated with the transaction but it's not perfect and causes prorated movements to be slightly different from what Maxio may believe the MRR to be. This issue is self correcting once the next non-prorated invoice occurs.  This limitation is covered in more detail here.