General Ledger / Reconciliation is where ERP discipline either begins or breaks.
Sub-Ledger to GL Reconciliation (AP) looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: The AP control account on the GL exactly matches the AP sub-ledger balance, all differences are explained and resolved, and the signed reconciliation is available for auditors.
The control flow a finance team actually needs.
Step 1
AP Sub-Ledger Balance Computed From...
Step 2
Compare To GL Control Account Balance
Step 3
Reconciliation Report Lists Matched And...
Step 4
Differences Flagged With Amount And...
Step 5
Correcting Entries Reference The...
The ERP surface involved.
Module
General Ledger / Reconciliation
Actors
AP Clerk, Controller, GL System, AP Sub-Ledger
Tier
Tier 0
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 6, 2026
AP sub-ledger balance computed from open bills minus credits; compare to GL control account balance; reconciliation report lists matched and unmatched items; differences flagged with amount and transaction reference; correcting entries must reference the reconciliation document; controller sign-off with timestamp recorded; reconciliation stored for audit; reconciliation blocked if either period is not closed; no modification of original transactions during reconciliation
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | AP sub-ledger balance computed from open bills minus credits | Given a closed period with posted AP transactions |
| Control 2 | compare to GL control account balance | when the AP clerk runs sub-ledger-to-GL reconciliation |
| Control 3 | reconciliation report lists matched and unmatched items | then the report shows matched and unmatched items, the AP sub-ledger total equals the GL control account balance, and the controller can sign off with timestamp |
| Control 4 | differences flagged with amount and transaction reference | |
| Control 5 | correcting entries must reference the reconciliation document | The AP control account on the GL exactly matches the AP sub-ledger balance, all differences are explained and resolved, and the signed reconciliation is available for auditors. |
| Control 6 | controller sign-off with timestamp recorded | The AP control account on the GL exactly matches the AP sub-ledger balance, all differences are explained and resolved, and the signed reconciliation is available for auditors. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At period end, the AP clerk runs the sub-ledger-to-GL reconciliation for accounts payable. The system computes the open AP balance from all posted but unpaid bills and vendor credits, then compares it to the GL control account balance for the same period. Differences are surfaced in a reconciliation report listing each unmatched item with its amount, date, vendor, and reference number. The clerk investigates each difference - common causes include timing differences on batch posts, manual journal entries bypassing the sub-ledger, or system errors. Adjustments are made via correcting journal entries, not by modifying original transactions. The controller signs off on the reconciliation, and the system records the sign-off with timestamp. |
| Control rules | AP sub-ledger balance computed from open bills minus credits; compare to GL control account balance; reconciliation report lists matched and unmatched items; differences flagged with amount and transaction reference; correcting entries must reference the reconciliation document; controller sign-off with timestamp recorded; reconciliation stored for audit; reconciliation blocked if either period is not closed; no modification of original transactions during reconciliation |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`ap_reconciliations` { id: string, external_id: string, entity_id: string, period_id: string, subledger_balance_minor: int64, gl_control_balance_minor: int64, variance_minor: int64, currency_code: char(3), status: enum(IN_PROGRESS,SIGNED_OFF), signed_off_by: string, signed_off_at: timestamptz }; `ap_reconciliation_items` { id: string, reconciliation_id: string, item_type: enum(MATCHED,SUBLEDGER_ONLY,GL_ONLY), amount_minor: int64, reference: string }; (reference, product may differ).API and events
`POST /v1/ap-reconciliations` { entity_id, period_id, external_id } -> 201 { id, subledger_balance_minor, gl_control_balance_minor, variance_minor, items }; `POST /v1/ap-reconciliations/{id}/sign-off` { signed_off_by } -> 200 { status: SIGNED_OFF }; emits `gl.ap_reconciliation.signed_off` event; idempotent via `external_id`.State transitions
`IN_PROGRESS -> SIGNED_OFF`; guard: original transactions are immutable during reconciliation; correcting entries must reference the reconciliation id; re-open requires controller approval.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.