People conflate subledger close with GL close. They aren't the same event. The subledgers — AP, AR, payroll, inventory — finalize on Day 2 of close and roll their totals up to the general ledger control accounts. The GL itself doesn't close until consolidation runs on Day 5. The reconciliation in between is where everything that went wrong during the month finally surfaces.
The flow that should tie
Each major subledger feeds a corresponding control account in the GL:
The four subledgers and the control accounts they roll into
Every subledger transaction should roll into a control account entry. The subledger detail (every open invoice, every payroll line, every inventory SKU) should sum exactly to the control account balance. When it doesn't, the reconciliation identifies why.
The principle matters for audit. Under PCAOB AS 2201 on internal control over financial reporting, subledger-to-GL reconciliations are among the entity-level controls auditors test — because it's where manual override and integration failures show up first.
Where subledger-to-GL reconciliation breaks
Timing — the subledger closed before late entries posted. AP closes at 5pm on Day 2. Three vendor invoices arrive at 6pm for the prior month. They get accrued via a manual JE to the GL, but the AP subledger doesn't reflect them as open invoices yet. The control account is right; the subledger detail is short three invoices; the reconciliation has a timing variance that requires a documented rollforward.
Manual JEs that bypass the subledger. A senior accountant books an AR reclass straight to the GL without going through the AR module — for a deduction writeoff, a credit memo correction, or a reclass between entities. The control account balance moves; the AR subledger doesn't. Every month that JE goes unmatched, the variance grows. Manual JEs that touch control accounts are the single largest source of subledger-to-GL variance at most mid-market companies.
Subledger close while the period stays open for adjustments. AP "closes" on Day 2 by stopping new invoice entry for the prior period. But the actual subledger period stays open for corrections and reversals. If the GL control account is locked while the subledger is still moving, or the subledger is locked while the GL is being adjusted for audit points, the balances diverge at the point-in-time measurement.
System integration failures nobody notices until Day 4. The AR module pushes summary JEs to the GL nightly via an automated integration. One night the push fails silently — no alert, no error log anyone checks daily. The AR subledger reflects new invoices; the GL doesn't. The control account is short by a full day's invoicing. Nobody notices until the subledger-to-GL rec runs on Day 4 — and by then the close target has already slipped.
What gets caught at the subledger-to-GL rec
| Variance type | Root cause | Resolution |
|---|---|---|
| Unposted entries | Integration failure | Re-push or manual JE with reversal |
| Miscoded entries | GL account error | Reclass JE on both sides |
| Duplicate JEs | Manual JE + auto-push double-posted | Reverse one |
| Currency translation gaps | Inconsistent revaluation rates | Agree rate source per account |
| Period reopens | Subledger and GL locked at different points | Coordinate lock timing |
The structural shift that matters here is continuous reconciliation. Teams that reconcile subledgers daily — rather than once at period-end — turn the Day 4 investigation into a Day 1 confirmation, and the close gates that depend on a clean subledger-to-GL tie out hours instead of days earlier.
What good looks like
A clean subledger-to-GL reconciliation has every control account tied to the subledger detail with a documented variance ledger for known timing items. Manual JEs that touch control accounts are flagged at posting — not discovered at month-end. Integration push failures surface within minutes and trigger a re-push before the next business day. Period locks are coordinated: when AP closes for the period, the GL AP control account locks at the same time.
The same principle applies across the broader close stack. The AP automation benchmarks post shows what top-quartile AP teams achieve on invoice processing time — the subledger-to-GL rec is one of the controls that makes those numbers durable rather than one-time lucky closes.
See how Cadel handles subledger and GL reconciliation as a continuous workflow — or get in touch to discuss your current control account variances.