When sending Chargify data to ChartMogul, we strongly recommend setting your churn recognition setting in ChartMogul to Always recognize cancellations as churn at the time of cancellation. 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 Chargify API does not support notification (webhook or events) or a polling mechanism for us to identify when a customer has been deleted from Chargify. Thus, it's currently not possible for SaaSync to remove customers from ChartMogul that get deleted in Chargify (after the initial sync). These customers can be manually deleted in ChartMogul's user interface.
The Chargify 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 Chargify 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.
- If a customer is re-synced using the customer re-sync tool, any invoices that are not tied to a subscription will not be re-synced. This is due to a deficiency in Chargify's API where you cannot filter invoices by customer.
- The integration does not currently support Maxio's Multifrequency feature.