Three-Way Reconciliation: Bank, Ledger, Gateway

Three sources, three questions

The bank statement answers cash

The bank statement is cash evidence. Credit and debit lines tell you whether money moved. Value date, bank reference, and transfer description are the keys into the other two sources.

Do not mix operating, collections, and expense accounts in one worksheet without a split. If the company uses several virtual accounts, reconcile per VA or merchant code first, then roll up.

The ledger answers recognition

The ledger answers when revenue, receivables, deposits, or fees were recognised. Cash journals, receipt journals, and gateway clearing accounts must trace to a settlement batch, not only to a daily total.

A clearing account that never clears is a signal that three-way work is incomplete. Growing clearing balances usually mean sales recognised without settlement, or settlement journalised twice.

The gateway file answers the payment cycle

The settlement report answers what happened in the payment chain: successful charges, pending items, voids, refunds, and fees. Without that file, finance sees a bank deposit as a net number that cannot be unpacked.

Bank Indonesia is overhauling the payment-system architecture through PBI 10/2025 and PADG 32/2025, effective 31 March 2026, with payment gateways bundled under Payment Transaction Forwarding. Settlement files and provider roles can change, so three-way reconciliation must survive format shifts rather than cling to one vendor template.

A method you can repeat

Lock the period before matching rows

Set separate cutoffs for cash, recognition, and settlement. A calendar day is rarely enough, because a gateway may settle T plus one or T plus two while sales are recognised on the authorisation date.

Write the cutoff calendar down. Who exports which file, when a file is final, and what happens if the bank file arrives late should be agreed before close starts.

Match in layers, not in one pass

Start at batch, then move to transactions. Match daily gateway settlement totals to bank credits. Once the batch matches, explode it into transaction lines, then into receivable or revenue journals.

Only then work fee, tax, and refund differences. If the team matches every sale to every bank credit, the work explodes because the relationship is one-to-many.

Use stable keys: settlement batch number, merchant ID, settle date, and amount. Bank description can be a fallback. It should not be the primary key, because banks truncate or rewrite transfer text.

Separate break types on day one

A timing break is not an amount break. A deposit that lands tomorrow morning must not be mixed with fees that will never equal gross sales.

Useful working categories: settlement timing, fees and tax, refunds and chargebacks, splits across accounts, off-gateway receipts, and journals posted to the wrong account. Each category needs an owner and an age limit.

Open items need an expected close date. Without that date, the exception list becomes a dump that reopens at every month-end.

Where the work usually breaks

Net deposits versus gross sales

Gateways often settle net of fees. A ledger that books gross sales without a separate fee account will always break. Fix the account mapping before adding new matching rules.

If fees are withheld at source, the journal should split cash, fees, and receivables in one package. If fees are invoiced later, fee reconciliation has its own cycle and should not pollute deposit matching.

One bank credit, many transactions

Marketplaces and gateways roll many payments into one or a few credits. One-to-one spreadsheet matching fails here. You need a batch rule plus a supporting transaction list.

Keep the detailed settlement file as a required attachment, not a file opened only after the break is already large. Without detail, three-way work collapses into guesswork.

Refunds that cross periods

A customer refunds at month-end and cash leaves early next month. If the period is not locked, teams patch with journals that have no trail. Mark the item open with an expected settle date instead of forcing a false match.

Chargebacks are harder because they can reverse sales recognised months earlier. Accounting policy for reserves and re-recognition should be agreed with external auditors before matching rules are written.

Mixed operating accounts

A company that uses one account for online sales, customer transfers, and supplier payments makes three-way work cloudy. Split the collections account if you can. If you cannot, description tagging and virtual accounts become mandatory.

Controls reviewers actually ask for

Healthy three-way reconciliation produces three artefacts: a working paper that points to the three source files, an aged open-item list, and a log of who matched or adjusted. Auditors do not need a pretty spreadsheet. They need proof that breaks were not closed in silence.

Set an operational review threshold, not only an audit threshold. Tiny items that repeat every day are a mapping signal, not noise to ignore.

Daily review catches timing. Weekly review catches mapping. Monthly review closes items that cross cutoff. Mixing those three rhythms into one close meeting is a classic reason reconciliation slips.