General Ledger Reconciliation: Process, Checklist, and Oracle Examples

Learn how Controllers reconcile general-ledger accounts to subledgers and supporting records, investigate differences, and maintain reviewable evidence.

<p>General ledger reconciliation is the process of proving that each GL account balance agrees with an independent source, such as a subledger, bank statement, fixed-asset register, or supporting calculation. Finance teams investigate differences, post approved corrections, document unresolved items, and retain evidence and reviewer sign-off before closing the reporting period.</p> <p>Matching totals is only the beginning. A complete reconciliation must explain what makes up the balance, why differences exist, who owns each unresolved item, and when it will be cleared.</p> <h2>TL;DR</h2> <p>General ledger reconciliation compares GL balances with independent supporting records. A controlled process includes complete postings, consistent report parameters, account ownership, risk-based review, aged reconciling items, evidence, and independent approval.</p> <p>In Oracle environments, reconciliation also depends on tracing balances through General Ledger, Subledger Accounting, Payables, Receivables, Cash Management, Assets, and other source modules. Connected GL reporting can reduce data gathering and make differences easier to investigate, but professional judgment and review remain essential.</p> <h2>What Is General Ledger Reconciliation?</h2> <p>General ledger reconciliation verifies that the balances recorded in the GL are complete, accurate, appropriately classified, and supported.</p> <p>For each material account, the reconciler should be able to answer four questions:</p> <ol type="1"> <li><p>What makes up the ending GL balance?</p></li> <li><p>What independent record supports that balance?</p></li> <li><p>Why does any difference exist?</p></li> <li><p>What correction or future action is required?</p></li> </ol> <p>For example, an accounts payable control account should agree with the total liability supported by the AP subledger. A cash account should reconcile with bank and Cash Management records. A prepaid-expense account should agree with a roll-forward schedule showing its opening balance, additions, amortization, and ending balance.</p> <p>A reconciliation is not complete merely because the workpaper contains the GL balance. The support must independently substantiate that balance or explain every material difference.</p> <p>This is also what separates reconciliation from <a href="https://splashbi.com/blog/what-is-general-ledger-reporting">general ledger reporting</a>. Reporting shows what has been recorded. Reconciliation tests whether that record agrees with the underlying financial activity.</p> <h2>General Ledger Reconciliation vs. Trial Balance vs. Account Reconciliation</h2> <p>These processes use related accounting data but establish different things.</p> <table> <thead> <tr> <th><strong>Process or Output</strong></th> <th><strong>What It Establishes</strong></th> <th><strong>What It Does Not Establish</strong></th> </tr> </thead> <tbody> <tr> <td>Trial balance</td> <td>Total debits equal total credits</td> <td>That individual accounts are correct or supported</td> </tr> <tr> <td>GL report</td> <td>Shows account balances, journals, and recorded activity</td> <td>That the activity agrees with an independent source</td> </tr> <tr> <td>Account reconciliation</td> <td>Proves one account balance using supporting evidence</td> <td>That every GL account has been reviewed</td> </tr> <tr> <td>Subledger-to-GL reconciliation</td> <td>Confirms a subledger agrees with its GL control account</td> <td>That unrelated accounts and manual journals are appropriate</td> </tr> <tr> <td>General ledger reconciliation</td> <td>Coordinates the substantiation and review of relevant GL accounts</td> <td>That every financial risk has been eliminated</td> </tr> <tr> <td>Balance-sheet reconciliation</td> <td>Substantiates balance-sheet accounts</td> <td>That all income-statement activity has been analyzed</td> </tr> </tbody> </table> <p>A balanced trial balance proves arithmetic equality. It cannot detect a duplicate entry with equal debits and credits, a misclassification between accounts, an entry posted to the wrong period, or an unsupported balance.</p> <p>General ledger reconciliation normally gives priority to balance-sheet accounts because their balances carry forward from period to period. Revenue and expense accounts may be reviewed through reconciliations, variance analysis, journal testing, or other analytical controls, depending on their risk and the organization’s accounting policy.</p> <h2>Which General Ledger Accounts Need Reconciliation?</h2> <p>Every material GL account should be covered by a defined reconciliation or analytical-review policy. The supporting source depends on the nature of the account.</p> <table> <thead> <tr> <th><strong>GL Account Area</strong></th> <th><strong>Independent or Supporting Source</strong></th> <th><strong>Common Differences</strong></th> </tr> </thead> <tbody> <tr> <td>Cash</td> <td>Bank statements and Cash Management records</td> <td>Outstanding payments, deposits in transit, bank fees, unmatched statement lines</td> </tr> <tr> <td>Accounts payable</td> <td>AP subledger, invoice register, payment register, and aging</td> <td>Unaccounted invoices, unposted activity, manual journals, and cut-off differences</td> </tr> <tr> <td>Accounts receivable</td> <td>AR subledger, receipts, credit memos, and aging</td> <td>Unapplied receipts, backdated transactions, write-offs, and manual journals</td> </tr> <tr> <td>Fixed assets</td> <td>Asset register and depreciation schedules</td> <td>Unposted additions, retirements, depreciation, or construction-in-progress transfers</td> </tr> <tr> <td>Inventory</td> <td>Inventory valuation, costing, and physical counts</td> <td>Cost updates, in-transit inventory, quantity differences, and obsolete stock</td> </tr> <tr> <td>Payroll</td> <td>Payroll register and payroll accounting output</td> <td>Benefit accruals, off-cycle payroll, timing, and mapping differences</td> </tr> <tr> <td>Intercompany</td> <td>Counterparty records and matching entity balances</td> <td>Timing, currency, account mapping, and unmatched partner entries</td> </tr> <tr> <td>Prepaids and accruals</td> <td>Roll-forward schedules and supporting calculations</td> <td>Missed amortization, incorrect reversals, stale estimates, and incomplete support</td> </tr> <tr> <td>Clearing and suspense</td> <td>Transaction-level clearing detail</td> <td>Unmatched transactions, missing references, and aged balances</td> </tr> <tr> <td>Tax accounts</td> <td>Tax returns, calculations, and payment records</td> <td>Timing, jurisdiction, deferred items, and classification differences</td> </tr> </tbody> </table> <p>Not every account needs the same reconciliation frequency.</p> <p>High-risk accounts such as cash, intercompany, tax, clearing, and major subledger-control accounts may require daily, weekly, or monthly attention. Stable, low-value accounts may be reviewed less frequently if the policy, risk assessment, and control environment support that decision.</p> <p>Frequency should reflect materiality, transaction volume, volatility, fraud exposure, estimation uncertainty, and potential financial-statement impact.</p> <h2>How Do You Reconcile the General Ledger?</h2> <p>A controlled general ledger reconciliation follows the same basic sequence for every account, even when the supporting evidence differs.</p> <h3>1. Define the reconciliation scope</h3> <p>Identify the ledger, entity, accounting period, currency, account combination, and reporting basis. Confirm whether the reconciliation covers a single account, an account range, a subledger control account, or multiple ledgers.</p> <h3>2. Roll forward the previous reconciliation</h3> <p>Confirm that the current opening balance agrees with the previous period’s approved ending balance. Carry forward unresolved items with their original dates, explanations, owners, and target resolution dates.</p> <h3>3. Verify posting completeness</h3> <p>Before comparing balances, confirm that required transactions have been accounted, transferred, and posted. Review interface failures, unposted journals, incomplete subledger processes, and activity recorded after the reporting cut-off.</p> <h3>4. Extract the GL balance and activity</h3> <p>Run the GL balance and transaction detail using controlled parameters. Save the ledger, entity, period, account, currency, and posting-status selections with the reconciliation.</p> <h3>5. Obtain independent support</h3> <p>Retrieve the subledger total, bank statement, asset register, inventory valuation, payroll register, contract, calculation, or roll-forward schedule that supports the GL account.</p> <h3>6. Compare the records</h3> <p>Calculate the difference between the GL and the supporting balance. For high-volume control accounts, begin with the total difference before moving into transaction-level investigation.</p> <h3>7. Classify every reconciling item</h3> <p>Common categories include:</p> <ul> <li><p>Timing differences</p></li> <li><p>Unaccounted transactions</p></li> <li><p>Transactions not transferred or posted</p></li> <li><p>Missing or duplicate entries</p></li> <li><p>Incorrect accounts, entities, periods, or currencies</p></li> <li><p>Manual journals to control accounts</p></li> <li><p>Intercompany mismatches</p></li> <li><p>Foreign-exchange differences</p></li> <li><p>Unsupported or stale balances</p></li> </ul> <h3>8. Correct or assign the difference</h3> <p>Post an approved adjustment or correcting journal when the accounting record is wrong. Do not post a plug merely to force the reconciliation to zero.</p> <p>Legitimate timing items should remain visible with an explanation, owner, expected clearing date, and aging status.</p> <h3>9. Review, approve, and retain evidence</h3> <p>An independent reviewer should confirm the source reports, calculations, material items, adjustments, unresolved differences, and evidence. Retain the completed workpaper and approval according to the organization’s record-retention policy.</p> <h2>How Does General Ledger Reconciliation Work in Oracle?</h2> <p>Oracle GL reconciliation begins with complete accounting and posting, then uses specialized reconciliation reports to compare General Ledger with its source modules.</p> <p>Oracle recommends verifying that all relevant subledger transactions have been imported, and journals posted before running reconciliation reports. Its predefined reports support cash, payables, receivables, journals, account analysis, and other reconciliation requirements. <a href="https://docs.oracle.com/en/cloud/saas/financials/26d/ocuar/general-ledger-reconciliation-reports.html">Oracle General Ledger Reconciliation Reports</a></p> <table> <thead> <tr> <th><strong>Oracle Area</strong></th> <th><strong>Accounting Objects</strong></th> <th><strong>Primary Reports</strong></th> <th><strong>What to Investigate</strong></th> </tr> </thead> <tbody> <tr> <td>General Ledger</td> <td>Balances, journals, account combinations, and periods</td> <td>Trial Balance, Account Analysis, journal reports</td> <td>Unposted journals, manual entries, incorrect periods or accounts</td> </tr> <tr> <td>Subledger Accounting</td> <td>Accounting events, journal entries, and transfer status</td> <td>Subledger Accounting reports</td> <td>Unaccounted, untransferred, rejected, or summarized entries</td> </tr> <tr> <td>Payables</td> <td>Invoices, payments, liability distributions, and SLA entries</td> <td>Payables to Ledger Reconciliation, Payables Trial Balance</td> <td>Manual GL postings, accounting status, invoice and payment timing</td> </tr> <tr> <td>Receivables</td> <td>Transactions, receipts, adjustments, and SLA entries</td> <td>Receivables to Ledger Reconciliation</td> <td>Unapplied receipts, backdated transactions, and accounting differences</td> </tr> <tr> <td>Cash Management</td> <td>Bank accounts, statement lines, receipts, and payments</td> <td>Cash to General Ledger Reconciliation</td> <td>Unmatched bank activity and book-to-bank timing</td> </tr> <tr> <td>Fixed Assets</td> <td>Asset books, additions, transfers, retirements, and depreciation</td> <td>Asset and GL reports</td> <td>Unposted depreciation, additions, transfers, and retirements</td> </tr> <tr> <td>Clearing accounts</td> <td>Journal lines and reconciliation references</td> <td>Reconciled Transactions Report</td> <td>Open clearing items and missing references</td> </tr> </tbody> </table> <p>The Payables to Ledger Reconciliation report shows summarized and detailed reconciling data, including beginning balances, period activity, ending balances, and differences. Reviewers can drill from a difference to the underlying detail. <a href="https://docs.oracle.com/en/cloud/saas/financials/26a/ocuar/considerations-for-payables-to-general-ledger-reconciliation.html">Oracle Payables-to-Ledger guidance</a></p> <p>The Receivables to Ledger Reconciliation report provides a similar comparison between receivables and accounting balances. It can expose differences involving transactions, receipts, adjustments, and how that activity was accounted. <a href="https://docs.oracle.com/en/cloud/saas/financials/26d/faofc/guidelines-for-using-the-receivables-to-general-ledger.html">Oracle Receivables-to-GL guidance</a></p> <p>Where practical, restrict postings to AP and AR control accounts to their designated subledger sources. Oracle recommends avoiding non-Payables sources posting to Payables accounts because unrelated manual journals create additional reconciliation differences.</p> <p>An <a href="https://splashbi.com/glossary/accounts-payable-aging-detail-report">accounts payable aging report</a> can support the AP review, but aging and reconciliation answer different questions. Aging explains how long invoices have remained outstanding. Reconciliation determines whether the subledger and GL agree.</p> <h2>What Should a GL Reconciliation Control Tower Show?</h2> <p>A GL reconciliation control tower should show which accounts are complete, where material differences remain, how long they have been open, and who owns the next action.</p> <p>The following is an illustrative design:</p> <table> <thead> <tr> <th><strong>Account</strong></th> <th><strong>Owner</strong></th> <th><strong>Risk</strong></th> <th><strong>GL Balance</strong></th> <th><strong>Supporting Balance</strong></th> <th><strong>Difference</strong></th> <th><strong>Oldest Item</strong></th> <th><strong>Status</strong></th> <th><strong>Reviewer</strong></th> </tr> </thead> <tbody> <tr> <td>Cash clearing</td> <td>Treasury Accounting</td> <td>High</td> <td>$4.82M</td> <td>$4.80M</td> <td>$20K</td> <td>4 days</td> <td>In review</td> <td>Controller</td> </tr> <tr> <td>AP control</td> <td>AP Accounting</td> <td>High</td> <td>$12.40M</td> <td>$12.32M</td> <td>$80K</td> <td>12 days</td> <td>Exception</td> <td>Accounting Manager</td> </tr> <tr> <td>AR control</td> <td>AR Accounting</td> <td>High</td> <td>$8.75M</td> <td>$8.75M</td> <td>$0</td> <td>0 days</td> <td>Complete</td> <td>Controller</td> </tr> <tr> <td>Intercompany</td> <td>Corporate Accounting</td> <td>High</td> <td>$2.10M</td> <td>$1.89M</td> <td>$210K</td> <td>35 days</td> <td>Overdue</td> <td>Group Controller</td> </tr> <tr> <td>Prepaids</td> <td>General Accounting</td> <td>Medium</td> <td>$640K</td> <td>$630K</td> <td>$10K</td> <td>61 days</td> <td>Action required</td> <td>Accounting Manager</td> </tr> </tbody> </table> <p>Useful control-tower metrics include:</p> <ul> <li><p>Percentage of accounts prepared and approved</p></li> <li><p>Unreconciled value by risk tier</p></li> <li><p>High-risk accounts past due</p></li> <li><p>Items older than 30, 60, and 90 days</p></li> <li><p>Manual journals posted to control accounts</p></li> <li><p>Unaccounted, untransferred, or unposted Oracle transactions</p></li> <li><p>Reconciliations awaiting review</p></li> <li><p>Accounts without current evidence</p></li> <li><p>Recurring differences by source and root cause</p></li> </ul> <p>Completion percentage alone can create false confidence. A close with 98% of accounts complete may still carry material risk if the remaining accounts include cash, intercompany, tax, or high-value subledger controls.</p> <h2>What Are the Best Practices for General Ledger Reconciliation?</h2> <p>Strong reconciliation controls make ownership, differences, evidence, and review visible.</p> <table> <thead> <tr> <th><strong>Best Practice</strong></th> <th><strong>Risk Reduced</strong></th> <th><strong>Evidence the Control Is Working</strong></th> </tr> </thead> <tbody> <tr> <td>Maintain an account inventory</td> <td>Accounts omitted from the close</td> <td>Every material account has an owner, reviewer, and cadence</td> </tr> <tr> <td>Assign frequency by risk</td> <td>High-risk accounts reviewed too late</td> <td>Risk tiers and documented review frequency</td> </tr> <tr> <td>Standardize report parameters</td> <td>Inconsistent balances and periods</td> <td>Saved ledger, period, entity, currency, and status selections</td> </tr> <tr> <td>Reconcile subledger controls first</td> <td>Detail reviewed before totals agree</td> <td>AP, AR, cash, assets, and inventory tied to their GL controls</td> </tr> <tr> <td>Restrict manual control-account journals</td> <td>Unexplained subledger-to-GL differences</td> <td>Approved journal sources and exception monitoring</td> </tr> <tr> <td>Age every difference</td> <td>Old items repeatedly carried forward</td> <td>Original date, owner, explanation, and resolution target</td> </tr> <tr> <td>Separate errors from timing</td> <td>Incorrect or premature adjustments</td> <td>Documented reconciling-item categories</td> </tr> <tr> <td>Prohibit unsupported plugs</td> <td>Balances forced to agree without evidence</td> <td>Adjustments linked to approved support</td> </tr> <tr> <td>Separate preparation and approval</td> <td>Self-review weakens the control</td> <td>Independent reviewer sign-off</td> </tr> <tr> <td>Preserve complete evidence</td> <td>Audit support reconstructed later</td> <td>Source reports, calculations, journals, notes, and approvals retained</td> </tr> <tr> <td>Analyze recurring differences</td> <td>The same process failures repeat</td> <td>Root-cause reporting and corrective actions</td> </tr> </tbody> </table> <p>Dedicated account reconciliation software may automate matching, certification, workflow, and exception routing. Connected GL software supports a different but complementary requirement: getting governed balances and transaction detail into the reconciliation process without rebuilding the data path every month.</p> <p>BlackLine’s reconciliation guidance emphasizes retaining supporting documentation, while segregation of duties requires the preparer and approver to be different people.</p> <h2>How Does GL Connect Support Oracle GL Reconciliation?</h2> <p><a href="https://splashbi.com/products/glconnect">GL Connect</a> supports Oracle reconciliation by making GL balances, journal activity, and subledger details easier to refresh, investigate, document, and review inside Excel.</p> <table> <thead> <tr> <th><strong>Reconciliation Friction</strong></th> <th><strong>How GL Connect Helps</strong></th> </tr> </thead> <tbody> <tr> <td>Static Oracle exports become outdated</td> <td>Reports can be refreshed from connected Oracle data</td> </tr> <tr> <td>A GL balance lacks supporting context</td> <td>Users can drill from balances to journal and subledger detail</td> </tr> <tr> <td>EBS, Fusion, and EPM reporting are separated</td> <td>One reporting environment supports hybrid Oracle estates</td> </tr> <tr> <td>Reviewers need supporting evidence</td> <td>Users can manage attachments and route approvals</td> </tr> <tr> <td>Reports are rebuilt every period</td> <td>Templates can be reused, refreshed, scheduled, and shared</td> </tr> <tr> <td>Multi-ledger review requires separate workbooks</td> <td>GL Connect supports reporting across ledgers</td> </tr> <tr> <td>Finance depends on IT for report changes</td> <td>Finance users can build and refresh reports within Excel</td> </tr> </tbody> </table> <p>GL Connect provides real-time reporting for Oracle EBS and direct, near real-time reporting for Oracle Fusion Cloud. It also connects to Oracle Cloud EPM for reporting across actuals, budgets, and forecasts.</p> <p>Its drilldown lets users move from a GL balance to balance detail, journal entries, and subledger transactions. That traceability helps the reconciler identify what created a difference and gives the reviewer a clearer evidence path. GL Connect also supports attachments, approval routing, report distribution, and reporting across ledgers.</p> <p>GL Connect supports reconciliation through access, traceability, evidence gathering, and review. It should not be described as automatically matching every transaction or certifying every account. Accounting ownership, exception resolution, adjustment approval, and independent review remain part of the control process.</p> <p>Learn more about <a href="https://splashbi.com/solutions/oracle-reporting-modernization">modernizing Oracle reporting</a> without replacing the ERP systems and accounting controls already in place.</p> <h2>Make Your General Ledger Reconciliation Explainable</h2> <p>General ledger reconciliation is not a month-end exercise in making two cells equal. It is the controlled process of proving what each balance contains, identifying why differences exist, resolving errors, aging legitimate open items, and preserving the evidence behind the conclusion.</p> <p>When Oracle data is difficult to extract and investigate, <a href="https://splashbi.com/products/glconnect">GL Connect</a> can give finance teams a faster, more traceable path from GL balance to journal and subledger detail.</p>

FAQ

What is general ledger reconciliation?

General ledger reconciliation compares each relevant GL account balance with an independent supporting source, such as a subledger, bank statement, asset register, or calculation. Differences are investigated, corrected or documented, reviewed, approved, and retained as evidence supporting the period-end balance.

How often should general ledger accounts be reconciled?

Frequency should reflect risk, materiality, transaction volume, volatility, and company policy. High-risk accounts may require daily, weekly, or monthly reconciliation. Stable, low-risk accounts may be reviewed quarterly. Material balance-sheet and subledger-control accounts are normally reconciled during every financial close.

What is the difference between a trial balance and GL reconciliation?

A trial balance lists account balances and confirms that total debits equal total credits. GL reconciliation tests whether individual balances agree with independent supporting records. A trial balance can balance even when transactions are duplicated, misclassified, posted to the wrong period, or unsupported.

What causes differences between a subledger and the general ledger?

Common causes include unaccounted transactions, entries not transferred or posted, manual journals to control accounts, timing and cut-off differences, incorrect account mappings, duplicate activity, backdated transactions, currency differences, and incomplete subledger processes.

Can general ledger reconciliation be automated?

Parts of the process can be automated, including data extraction, report refresh, transaction matching, exception identification, workflow, and aging. Automation does not replace accounting judgment, supporting evidence, adjustment approval, or independent review. The available automation depends on the ERP, reporting layer, and reconciliation software.

What should a GL reconciliation workpaper include?

A complete workpaper should include the account, period, entity, currency, GL balance, supporting balance, difference, reconciling items, explanations, aging, owners, expected resolution dates, adjustments, source reports, supporting evidence, preparer, reviewer, approval dates, and unresolved-item roll-forward.