Skip to content

GL Reconciliation

GL Reconciliation helps finance users confirm that general ledger balances agree with the supporting records behind them. It is used to detect missing entries, duplicate entries, timing differences, incorrect accounts, and unresolved suspense items.

Navigation: Accounting > Operations > GL Reconciliation

Workspace Reference

WorkspaceHow Users Reach ItWhat Users Usually Do There
GL ReconciliationAccounting -> Operations -> GL ReconciliationCompare GL balances with supporting records, match items, flag exceptions, and finalize reconciliation.
GL JournalsAccounting -> Operations -> GL JournalsInspect journal lines, source references, reversals, and failed postings behind reconciliation differences.
Account Balances And Financial ReportsAccounting -> OperationsConfirm account movement, control balances, trial balance, and statement impact.
Service WorkspacesLoans, Deposits, Billing, POS, Wallets, Shares, Assets, Inventory, Production, Agriculture, and PaymentsReview the source records that should agree with GL balances.

What To Reconcile

Different account types need different supporting evidence.

Reconciliation AreaWhat Users Compare
Bank accountsGL bank lines against bank statement lines.
Cash and till accountsGL cash movement against till sessions, cash counts, and drawer activity.
Wallet and provider accountsGL wallet or provider movement against wallet transactions, holds, settlement, and provider confirmations.
ReceivablesGL control account against invoice balances, allocations, and customer sub-ledgers.
PayablesGL control account against supplier, party, or payout obligations.
Loan controlsGL control account against loan account balances and loan transaction history.
Deposit controlsGL control account against deposit account balances and account transactions.
Suspense and clearingItems that should be cleared, allocated, reversed, or investigated.

Reconciliation Workflow

  1. Select the account, currency, business unit, and period.
  2. Review opening balance, movement, and closing balance.
  3. Compare GL lines with the supporting source records.
  4. Mark matched items where the amount, date, reference, and party context agree.
  5. Flag unmatched or suspicious items.
  6. Investigate the reason for each exception.
  7. Correct the source record, post an approved adjustment, or document a valid timing difference.
  8. Finalize the reconciliation when exceptions are resolved or explained.

Matching Guidance

A good match usually has enough agreement across:

  • Amount.
  • Currency.
  • Transaction date or value date.
  • Party, account, wallet, bank, or till context.
  • Business reference.
  • Source module or transaction type.

Do not match items only because the amount is the same. High-volume accounts often have repeated amounts.

Exception Types

Common reconciliation exceptions include:

  • Missing GL entry.
  • Source transaction not posted.
  • Duplicate posting.
  • Wrong account or business unit.
  • Wrong sub-ledger.
  • Timing difference.
  • Unreleased hold.
  • Failed settlement.
  • Reversed source transaction with unreversed GL.
  • Manual journal posted without enough supporting detail.

Resolving Exceptions

The correct fix depends on the cause.

If the source transaction is correct but not posted, post or replay the approved accounting action where the module allows it.

If the GL entry is wrong, use the approved correction or reversal workflow rather than editing history.

If the difference is timing-related, document the reason and confirm it clears in the next period.

If the account requires sub-ledger tracking, confirm the journal line has the correct party, account, wallet, loan, deposit, or other supporting ledger context.

Good Practice

  • Reconcile high-volume cash, bank, wallet, and settlement accounts daily.
  • Reconcile control accounts at least monthly.
  • Do not close a period while material exceptions remain unexplained.
  • Keep notes clear enough for another finance user or auditor to understand the decision.
  • Separate posting and reconciliation responsibilities where possible.

Pinkapple ERP by Stat Solutions Network