Subledger

Subledger is a detailed subsidiary ledger, such as the accounts receivable, accounts payable, or fixed asset subledger, that feeds summary totals into the general ledger. A subledger holds transaction-level detail for one area, such as receivables or fixed assets, and posts a summarised total to the general ledger.

Category: Accounting SoftwareBest Accounting Software

Your AP team reconciled the accounts payable subledger to the GL last month and found a $140,000 discrepancy that took three days and five people to trace. The source was a posting that updated the subledger but not the GL, and the discrepancy had been building for six weeks. A subledger is a detailed subsidiary ledger that holds transaction-level data for one account category, which then rolls up into the matching control account in the general ledger. The accounts payable subledger contains every individual vendor invoice and payment. The accounts receivable subledger contains every customer invoice and receipt. The fixed asset subledger contains every individual asset and its depreciation schedule. The GL control account for each category shows only the total balance, the sum of everything in the subledger. The subledger holds the detail; the GL holds the summary. The link between them is where the risk sits. When it breaks, and a transaction updates one side but not the other, the discrepancy can build undetected for weeks or months. The longer it runs, the more transactions may be affected and the more investigation it takes to find the source.

How subledgers feed the general ledger

In a well-integrated system, posting a transaction in the subledger automatically creates the corresponding GL entry. When an AP clerk posts a $25,000 vendor invoice in the AP module, it creates the invoice in the AP subledger (increasing what the company owes that vendor) and at the same time creates a GL debit to the relevant expense account and a credit to the AP control account. The two stay in sync because the GL entry is created in the same posting event as the subledger entry. The risk appears when that coupling breaks. Where the subledger and GL are separate modules, either in different systems or in one system that syncs in batches instead of posting in real time, there is a timing gap. The subledger can update first and the GL batch can fail silently, leaving the two out of sync. That is what happened in the scenario above: a batch posting updated the AP subledger but didn't complete the GL update, and nobody caught it because the subledger-to-GL reconciliation ran monthly, not daily. Third-party integrations add to this risk. A standalone expense management tool that posts to AP via API, or a billing system that posts revenue recognition to the GL, creates a data path outside the accounting system's native controls.

AR, AP, and fixed asset subledgers

The three most common subledgers (accounts receivable, accounts payable, and fixed assets) fail in different ways. AR subledger failures often come from cash application errors: payments received and posted to the bank account but not applied to specific invoices in the AR subledger, which leaves invoices open that should be closed. Over time, the AR aging shows balances that have already been collected. AP subledger failures usually come from the batch synchronization problem described above, or from invoices voided in AP without a matching GL reversal. Fixed asset subledger failures often come from assets that were bought but never entered in the fixed asset module. The cash payment is in the GL, but the asset isn't in the subledger, so no depreciation runs. Each of these failures only shows up in a reconciliation between the subledger and the GL control account, and how often you reconcile determines how long errors build before you find them. Monthly reconciliation means errors can build for 30 days. Weekly reconciliation catches them within a week. Daily reconciliation (typically automated) catches them immediately. The right cadence depends on transaction volume and the materiality of potential errors. For AP, where invoice volumes are high and amounts can be large, weekly subledger-to-GL reconciliation is a defensible control standard.

How platforms handle it

When you evaluate accounting software, the main subledger question is whether the sync between subledger and GL is transactional (every subledger posting creates an immediate GL entry in the same database transaction) or batch-based (subledger postings accumulate and sync to the GL on a schedule). With transactional sync, the two records can't drift apart: if the GL entry fails, the subledger posting fails too and rolls back. With batch sync, they can be out of step for the length of the batch interval, and a failed batch can leave them permanently out of sync unless someone detects it and reruns the batch. Platform-native subledgers (AP and AR modules built into the same ERP as the GL) mostly use transactional sync in modern systems. Third-party integrations, such as a separate expense management tool, a standalone billing platform, or an acquired subsidiary on a different ERP, almost always sync in batches, which makes the reconciliation control mandatory. In vendor evaluations, ask directly: how does the system detect a failed batch sync between the subledger and GL, and what is the recovery process?

Questions to ask

Is subledger-to-GL synchronization transactional (immediate, same database transaction) or batch-based? If batch-based, what is the sync frequency and how are batch failures detected?
Does the system provide a native subledger-to-GL reconciliation report that can be run on demand, showing any differences between the subledger balance and the GL control account balance?
For third-party integrations that post to subledgers via API, is there an independent reconciliation mechanism to verify the integration hasn't created a discrepancy?
What is the process for investigating and resolving a subledger-to-GL discrepancy once it is found: who has access to both records, and what authorization is required to post a correcting entry?

Two subledger assumptions that create month-end surprises

The first is assuming the ERP keeps subledger and GL in sync automatically. That holds for native subledger modules with transactional sync. It breaks for batch-synchronized integrations, heavily customized systems, and any data path that runs through an external tool. Finance teams that go months without a subledger-to-GL reconciliation often find discrepancies that have been building since the last time someone checked. Treating subledger-to-GL reconciliation as a discrete close task, with a named preparer, a reviewer, and a documented process for resolving exceptions, catches these before they become material. The second assumption is that a clean AR aging means the AR subledger is accurate. Aging reports are generated from the subledger. If the subledger contains unapplied cash, misapplied payments, or invoices that should have been written off, the aging looks inflated even when the GL balance may be correct. Checking subledger accuracy means more than comparing the total to the GL. You also have to review what makes up the balance for items that shouldn't be there.

Subledger against general ledger

The general ledger holds one balance per account. The subledger holds the detail behind it: which customer, which invoice, which asset. Reconciling the two is a standing close task, because a subledger that no longer ties to its control account means either the detail or the summary is wrong, and statements are produced from the summary.

Comparing accounting software

The dividing line in this category is whether a tool owns the ledger or sits beside it running reconciliations and the close checklist. Once subledger is settled as a requirement, read the Accounting Software category guide for how the market splits, then weigh the BlackLine profile against the FloQast profile on that requirement rather than on the feature list. Our BlackLine pricing breakdown records what the vendor publishes and what is quote-based. The BlackLine against FloQast comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the accounting software ROI calculator so the business case is written down before a vendor writes it for you.

Frequently asked questions

How is a subledger different from the general ledger?

The general ledger holds summary balances by account: the total accounts payable balance at period-end, for example, with no detail on which vendors are owed what. The subledger holds the transaction-level detail behind that total: every open invoice by vendor, with invoice date, due date, payment terms, and payment history. The GL control account and the matching subledger balance should always agree, and when they don't, you need a reconciliation investigation. Operational teams work in the subledger (AP clerks process invoices and payments in the AP subledger, credit teams manage collections in the AR subledger), while accounting teams verify and report from the GL.

What is a control account and how does it relate to a subledger?

A control account is the GL account that carries the total balance of a subledger. The AP control account on the balance sheet equals the sum of all open vendor invoices in the AP subledger. The AR control account equals the sum of all open customer invoices in the AR subledger. Well-controlled environments generally prohibit posting directly to a control account (bypassing the subledger), because it creates a gap between the subledger detail and the GL total. The only legitimate postings to a control account are the ones the subledger system makes automatically. If someone posts a manual journal entry straight to the AR control account, the GL balance changes but the subledger doesn't, leaving an unexplained reconciling difference that can be hard to trace later.

Account Reconciliation, Accrual Accounting, and Audit Trail come up in the same workflow as subledger, and the rest of the accounting software cluster is indexed in the finance operations glossary.