Ledger reconciliation services
Ledger reconciliation
The invoice matched. The ledger still didn't balance. Everything interesting happens in between — subledger variances, intercompany mismatches, timing differences, and cut-off errors that hold the close open. We run that queue.
The trial balance doesn't explain itself
Your ERP produces a trial balance. It tells you the numbers. It does not tell you why the AP control account is $18K higher than the subledger, why intercompany doesn't net to zero, or why the bank reconciliation has items aged past 30 days.
Those answers require investigation — pulling subledger detail, tracing journal entries, matching intercompany transactions across entities, and separating genuine errors from timing differences that will self-clear. At scale, this is the work that holds the close open.
Our agents reconcile every GL account against its supporting detail. They investigate every variance, propose a resolution, and attach the full reasoning. The result: a clean reconciliation delivered on your close calendar, not after it.
Six reconciliation types we run
Each type follows a structured investigation path. Our agents know which supporting detail to pull, which tolerances apply, and when to escalate.
AP subledger to GL
The AP ageing says $2.4M outstanding. The GL control account says $2.38M. The $20K gap is usually timing — invoices posted in AP but not yet journalled, or payments recorded in the GL but not yet cleared in the subledger.
Intercompany eliminations
Entity A invoiced Entity B. Both recorded it — but at different exchange rates, in different periods, or with different GL codes. The agent matches by transaction reference, flags mismatches, and proposes the elimination entry.
Multi-entity GL coding
A shared-services cost centre allocated expenses across four entities. The allocations don't sum to the source. The agent traces each allocation back to the original journal and identifies the rounding or omission.
Timing differences and cut-off
Revenue recognised in one period, cash received in the next. Accruals posted at month-end, reversed on Day 1. The agent separates genuine breaks from timing items and tracks reversals through to clearance.
Bank-to-book reconciliation
The bank statement shows $4.2M. The cash GL shows $4.17M. The difference is in-transit deposits, uncleared cheques, and bank fees not yet posted. The agent matches each item and ages anything uncleared past threshold.
Fixed asset register to GL
The asset register says $12.8M net book value. The GL says $12.6M. The gap is usually a disposal not yet journalled, a revaluation not reflected, or a depreciation run that didn't complete.
Tolerance rules and escalation paths
Not every variance is a problem. Tolerances define what auto-clears and what requires human review. Rules are configurable per account type, entity, and period.
| Account type | Example threshold | Action |
|---|---|---|
| Subledger-to-GL variance | ±$100 or ±0.1% of control account balance | Auto-clear within tolerance; escalate above with line-item detail |
| Intercompany balance | Zero tolerance (FX rounding excepted at ±$5) | Escalate any net difference; propose elimination journal |
| Timing items | Auto-clear if reversal posts within 5 business days | Age and escalate if uncleared past period-end +5 days |
| Bank reconciling items | Individual items >$10K or aged >3 days | Flag for treasury review; auto-clear below threshold |
| Allocation rounding | ±$1 per entity per allocation | Auto-clear; log for audit trail |
Systems we connect to
We pull trial balance, subledger detail, and journal entries directly from your ERP. No CSV exports, no manual uploads, no middleware.
| System | Integration capability |
|---|---|
| NetSuite | Multi-subsidiary consolidation, intercompany elimination, GL impact analysis |
| Sage Intacct | Dimensions-based reconciliation, statistical accounts, multi-entity close |
| QuickBooks Enterprise | Class and location-level GL reconciliation, bank feeds matching |
| Microsoft Dynamics 365 | Financial dimensions, intercompany accounting, subledger journals |
| Acumatica | Subaccount reconciliation, inter-branch balancing, consolidation workbooks |
| SAP Business One | Profit centre reconciliation, internal orders, period-end closing cockpit |
Who uses this
Multi-entity groups
Holding companies with 5–50 entities that need intercompany eliminations and consolidated GL reconciliation every period.
Finance teams at close
Controllers and accounting managers who need every balance sheet account reconciled before the close checklist can sign off.
Audit-ready organisations
Firms preparing for external audit that need documented reconciliations with supporting evidence for every material account.
Related services
Invoice reconciliation
Three-way match, price variances, quantity mismatches, and GL coding errors — resolved before the invoice hits the ledger.
Accounts payable reconciliation
AP subledger to GL, vendor statements, accruals, and month-end close calendar — the upstream feed into ledger reconciliation.
Intercompany reconciliation guide
How intercompany balances break, why eliminations fail, and the investigation workflow that resolves them.
Family office reconciliation
Portfolio, custodian, and NAV reconciliation for single and multi-family offices — positions, cash, and corporate actions.
Frequently asked questions
What is ledger reconciliation?
Ledger reconciliation is the process of verifying that every account in the general ledger agrees with its supporting detail — subledgers, bank statements, asset registers, and intercompany counterparties. It is the control that confirms the trial balance is complete and accurate before financial statements are prepared.
How is this different from invoice reconciliation?
Invoice reconciliation matches individual invoices to POs and receipts — it operates at the transaction level. Ledger reconciliation operates at the account level: confirming that the sum of all transactions in a subledger agrees with the GL control account, and that the GL as a whole is internally consistent.
What causes subledger-to-GL differences?
The most common causes are timing (a transaction posted in the subledger but not yet journalled to the GL), manual journal entries that bypass the subledger, system integration failures where a feed drops records, and coding errors where a transaction posts to the wrong GL account.
How do you handle intercompany reconciliation?
We match intercompany transactions by reference, amount, and date across all entities in the group. Where mismatches exist — different FX rates, different posting periods, missing counterparty entries — the agent proposes the correcting entry and routes it for approval before the elimination journal is posted.
What does the engagement look like?
We start with a scoping call to map your chart of accounts, entity structure, and close calendar. Then we configure reconciliation rules per account type, set tolerance thresholds, and establish escalation paths. You receive a daily reconciliation status with proposed resolutions — and a clean close package at period-end.
Close the books on time, every time
Tell us your entity structure, your ERP, and your close calendar. We'll scope the engagement and show you what the first reconciliation cycle looks like.