How to connect your billing system to an ERP

SaaS companies connect billing to their ERP with a native sync that posts four things to the general ledger: customers, invoices (with their lines and tax), payments and refunds, and revenue entries. Billing stays the system of record for contracts and invoices; the ERP stays the system of record for the books. The integration works when every record has a stable ID on both sides, the chart of accounts is mapped once, and payments are matched to invoices before they reach the ledger.

What moves from billing to the ERP

A quote-to-cash platform creates far more operational data than the ledger needs. The ERP should receive what accounting uses to close the month:

1. Customers. One customer record per billing account, with the legal entity, currency and tax details. Created once, then updated.
2. Invoices and credit notes. Header, lines, tax amounts, currency and due date. Each line carries a product or item mapped to an income account.
3. Payments and refunds. Cash received, the fees taken by the payment provider, and which invoices each payment settles. This is cash application, and it is where most reconciliation work sits.
4. Journal entries. Deferred revenue, recognized revenue, unbilled receivables, and sometimes provider fees and FX differences. Some platforms post these as journal entries; others send invoices and let the ERP build the entries.
5. Revenue schedules. For ASC 606 or IFRS 15, the schedule that spreads an annual invoice over twelve months. It can be computed in billing and posted as entries, or rebuilt in the ERP’s own revenue module.

The key design choice is where revenue recognition happens. If the billing platform documents ASC 606 recognition, it can post monthly recognized revenue directly. If not, the ERP needs a revenue module and must receive enough contract detail (start date, end date, performance obligations) to compute it. Our page on ASC 606 revenue recognition lists platforms that document the first option.

Worked example

This is an illustrative example with round numbers.

A customer signs an annual contract on January 1: $12,000 for the platform, invoiced upfront, plus usage billed monthly in arrears. Payment comes in by card on January 10, with a $360 processing fee.

Date	Event in billing	What reaches the ERP
Jan 1	Annual invoice issued	Invoice $12,000: debit accounts receivable $12,000, credit deferred revenue $12,000
Jan 10	Payment received	Payment $12,000 applied to the invoice; cash $11,640, fee expense $360
Jan 31	Month closes	Journal entry: debit deferred revenue $1,000, credit subscription revenue $1,000
Feb 1	Usage invoice for January, $450	Invoice $450, credited to usage revenue (recognized as delivered)

If the payment provider pays out net of fees in a batch with forty other payments, the ERP must still see forty invoices settled and one fee total. That is why cash application, the matching of payouts to invoices, belongs in the integration scope and not only in a bank-reconciliation spreadsheet.

Common pitfalls

• Posting summaries instead of invoices. A single daily journal entry for “all billing” is easy to build and impossible to audit. Auditors and collections teams need invoice-level records in the ERP.
• Unmapped products. A new plan created in billing without an income account mapping either fails to sync or lands in a catch-all account. Ask how the platform blocks or flags unmapped items.
• Two revenue engines. Running recognition in billing and in the ERP at the same time produces two deferred revenue balances. Choose one.
• Payout matching left out. Provider payouts net of fees and refunds do not match invoice totals. Without cash application, someone reconciles them by hand every month.
• Multi-entity and multi-currency. If you invoice from two legal entities, each needs its own subsidiary mapping in the ERP, and FX gains or losses must be posted somewhere.
• Edits after sync. Changing an invoice in billing after it posted to a closed period should create a credit note, not overwrite a locked record.

Checklist: what to ask a vendor

• Is there a native connector for your ERP, such as NetSuite, QuickBooks, Xero or Rillet?
• Which objects sync: customers, invoices, credit notes, payments, refunds, fees, journal entries?
• Does the platform post general ledger entries itself, or only documents for the ERP to process?
• Is ASC 606 / IFRS 15 recognition computed in billing, and are revenue schedules posted to the ERP?
• How are payouts from payment providers matched to invoices (cash application)?
• How are entities, currencies, tax codes and the chart of accounts mapped, and who maintains the mapping?
• What happens when a sync fails or a period is closed? Is there an error queue you can retry from?

Which quote-to-cash platforms document it

The platforms below document ERP sync and general ledger entries, ranked by their overall score. 41 of the 44 platforms we score document an ERP sync, 35 document general ledger entries, 32 document cash application and reconciliation, and 24 document all four capabilities including ASC 606 and IFRS 15 recognition.

See the full ERP sync ranking, or the scoring criteria for what each level means. If the sales side matters as much as the accounting side, read how to sync ARR, MRR and invoices back into your CRM.

FAQ

Should revenue recognition run in billing or in the ERP?

Either works, but only one should run. Billing has the contract detail, so recognizing there avoids re-sending it. An ERP revenue module makes sense if you already run it for non-subscription revenue.

Do I need journal entries if invoices already sync?

Invoices cover receivables and billed revenue. Deferred revenue releases, unbilled usage and payment fees need journal entries, either posted by the billing platform or built in the ERP.

Is a CSV export to the ERP good enough?

At low volume, for a few months. It breaks with credit notes, partial payments, multiple currencies and audits, because nothing links the ERP record back to the billing record.