How to Sync a Chart of Accounts Between AR and ERP Systems
A step-by-step way to keep an AR system and an ERP on the same chart of accounts — one owner, a mapping table, a control account and a month-end check.
AR postings → one ledgerFIG.01
Short answer
An AR system and an ERP stay in step when only one of them owns the chart of accounts. Pick the owner, list each account the AR side uses against its ledger code, have your accountant approve that list, block account creation everywhere else, and compare customer balances with the receivables control account at every month-end.
Key takeaways
- Two systems that can both create accounts will always drift apart.
- The ERP ledger should own the chart; the AR system is a subledger that posts into it.
- The mapping table is an accounting document — the accountant approves it, the developer implements it.
- One comparison proves the sync works: open customer balances against the receivables control account.
- Failed transfers need a visible queue and a named person to clear it.
An accounts receivable system — a billing platform, a collections tool, a customer portal — and an ERP both hold accounts, and each believes its own are correct. The trouble shows at month-end: the AR system says customers owe one figure, the ledger says another, and somebody spends two days finding the difference. The cause is nearly always the same. The two systems are not posting to the same chart of accounts.
Why the two charts drift apart
- An account is added in one system and never in the other.
- The same account carries a different code or name on each side.
- The AR system keeps detail by customer and invoice that the ledger holds as one total, and nobody documented the link.
- Tax, discounts, write-offs and advances are posted to whichever account seemed right on the day.
- A transfer fails overnight and nobody is told.
Step one is a decision, not a connection
Before anything is integrated, decide which system owns the chart. In almost every case it should be the ERP's general ledger, because that is where the trial balance, the tax return and the audit come from. The AR system then becomes a subledger: it keeps the customer-by-customer detail and posts into accounts the ledger defines. An AR system that is allowed to invent accounts will sooner or later invent one the ledger has never heard of.
Build the mapping table
The mapping is a plain table that says, for each kind of entry the AR system makes, which ledger account receives it. It is an accounting document: the accountant writes and approves it, and the developer implements exactly what it says.
| AR event | Ledger accounts it posts to | Decide in advance |
|---|---|---|
| Invoice raised | Receivables control account, and revenue | One revenue account, or one per product line or branch |
| Tax on the invoice | Output tax payable | Which ledger account each tax code uses |
| Payment received | Bank or cash, against receivables | Where unallocated receipts are held |
| Advance from a customer | Customer advances, a liability | When it is set against an invoice |
| Discount or credit note | Sales discounts or sales returns | Who may approve one |
| Bad debt written off | Bad debt expense, against receivables | The approval limit |
| Exchange difference | Exchange gain or loss | Which rate is used, and on what date |
The sync, step by step
Syncing a chart of accounts between an AR system and an ERP
Name the owner
Put in writing that the ERP ledger owns the chart of accounts and the AR system posts only to accounts the ledger defines.
List what the AR system uses today
Export every account, code and tax code it posts to, including the ones nobody remembers creating.
Map each one
Match every AR account to a ledger code. Merge duplicates and retire accounts that have no ledger equivalent.
Get the accountant's sign-off
Approve the mapping table before development starts, because changing it later means reposting history.
Lock account creation
New accounts are opened in the ERP and passed to the AR system automatically. Creating one on the AR side is switched off.
Post through the control account
Individual invoices and receipts stay in the AR system; the ledger receives them against one receivables control account, line by line or as a daily summary.
Handle failures in the open
Every rejected entry goes to a queue with its reason, and one person is responsible for clearing it.
Reconcile at month-end
Total open customer balances in the AR system must equal the control account in the ledger. Explain any difference before the period is closed.
The one figure that proves it works
The test of the whole arrangement is a single comparison: total open customer balances in the AR system against the receivables control account in the ERP, on the same date. If they agree, the sync is working. If they do not, the difference is almost always one of four things — a journal posted directly to the control account, a failed transfer, a timing difference at the cut-off, or an account that exists on one side only. Blocking manual journals to the control account removes the first cause altogether.
Changes after go-live
Charts of accounts change: a new branch, a new product line, a new tax code. Treat each change as a small procedure. The accountant requests it, it is created in the ERP, it flows to the AR system, and the mapping table is updated the same day. A mapping table a year out of date is how the drift begins again.
The wider picture — which records each system owns, and what crosses between them — is in integrating an ERP with your accounting software, and ERP vs accounting software covers whether you need both at all. CloudPak runs a custom ERP portal with integrations. If your receivables and your ledger disagree every month-end, we can map it with your accountant as part of an ERP or CRM project.
Frequently asked questions
How do I sync a chart of accounts between AR and ERP systems?
Choose one system — normally the ERP ledger — as the owner of the chart, map every account the AR system posts to onto a ledger code, stop accounts being created anywhere else, and reconcile the receivables control account every month.
Which system should be the master for the chart of accounts?
The one the financial statements come from, which is almost always the ERP or accounting ledger. The AR system holds the customer detail and posts into the ledger's accounts.
What is a receivables control account?
A single ledger account that carries the total owed by all customers. The detail by customer and invoice lives in the AR system, and the two totals must agree.
Should the sync run in real time?
It does not need to. A scheduled transfer, hourly or nightly, with a visible failure queue is easier to reconcile and is enough for accounting.
What if the totals do not match at month-end?
Look for manual journals posted to the control account, failed transfers, entries dated either side of the cut-off, and accounts that exist in only one system. Fix the cause, not only the balance.
/Services in this article
/ERP & CRM Systems by country
Keep reading
All articlesPOS Software in Pakistan: What a Retail Shop Actually Needs
What to look for in point-of-sale software for a shop in Pakistan — fast billing, stock by item, cash control per shift, customer credit, working offline and FBR integration.
HR and Payroll Software in Pakistan: What It Has to Get Right
How payroll software should handle attendance, leave, overtime, advances, tax and statutory deductions for a business in Pakistan — and when it belongs inside an ERP.
Hospital Management System: Admissions, Wards, Pharmacy and the Final Bill
What a hospital management system has to handle once a patient is admitted — beds, orders, pharmacy and lab charges, panel billing and discharge — and the order to build it in.
Odoo vs Custom ERP: How to Choose Between a Platform and a Build
An even-handed comparison of Odoo and a custom-built ERP — editions, customisation, upgrades, cost over time and ownership — and the situations where each is the better choice.