← Library
◆ Settlement · ReconPayment InfrastructureOctober 25, 2026 · 5 min read

Explain one bank credit before comparing a day of sales

A credit on the bank statement needs an explanation tied to its batch. A signed worksheet separates a matched reference from an explained amount.

Article
Reading time
5 min read
Sections
4
Published
October 25, 2026
LinkedInEmail
In this essay4 sections

A bank statement shows a credit of 216. The sales dashboard for the same date shows 250. Before anyone calls the difference a payment loss, finance needs to establish which settlement batch the credit belongs to and which report lines belong in that batch.

This investigation starts with money that has arrived. Its artifact is a bank-credit-to-batch worksheet. A late payout investigation starts elsewhere, with an expected instruction whose arrival has not been established. A cash forecast asks a third question about future availability.

A finance analyst compares two document folders and a calculator at her desk.

Match the identity before the amount

Record the receiving bank account, posted currency, bank reference, value or booking date as relevant, and amount. Find the provider payout or batch reference through the documented report and banking evidence. Use the appropriate merchant-account context. Two credits with similar amounts are not interchangeable candidates.

Adyen's settlement reconciliation guidance separates batch-level and transaction-level work. A batch can contain activity from different sales dates and payment methods. At transaction level, one payment can have multiple journal entries, so a payment reference alone is not necessarily a unique report row. Adyen batch-level reconciliation Adyen transaction-level reconciliation

If the bank reference is missing or the report maps ambiguously, leave the match provisional. Do not choose the nearest amount merely to clear the day's exception count. Ask the provider or bank for the supported trace and preserve what is still unknown.

Work from the batch's signed entries

The following worksheet is fictional and uses one currency. It assumes gross captured amounts, separately reported fees and the listed reserve movements. The labels and identifiers are teaching examples, not a copy of a provider export schema.

Worksheet line Source event Amount included Why it belongs
L1 Earlier sales date, captured transactions +180 Assigned to the identified batch
L2 Later sales date, captured transactions +70 Same batch despite a different sale date
L3 Refund adjustment −20 Explicitly booked to this batch
L4 Separately reported processing fee −7 Not already deducted in L1 or L2
L5 Reserve retained −10 Documented withholding in this example
L6 Prior reserve released +5 Release joins this batch, not the original sales day
Expected batch amount Sum of L1–L6 218 250 − 20 − 7 − 10 + 5
Bank credit Posted statement entry 216 Matched reference, amount still differs
Open difference Expected minus observed 2 Cause not yet established

A second currency needs its own worksheet unless an evidenced conversion connects the records. Do not add 100 euros and 100 dirhams into a 200-unit total. Where conversion applies, retain the conversion reference, source and destination amounts, rate convention and any separately identified charges.

Avoid two deductions that make a false match

First, establish whether a report amount is gross or net. If the fee is already included in net settlement, subtracting it again understates the expected credit. The worksheet deliberately uses gross values and a separate fee row so the arithmetic is visible.

Second, understand the payout balancing entry. Adyen identifies MerchantPayout as the debit that balances the paid-out batch. Treating it as another trading expense and subtracting it from an already calculated payout would count the movement twice. Use the report's documented journal semantics. Adyen transaction-level reconciliation

Keep the original export intact. Add classifications in a working layer that retains the source file, row identity and calculation version. An analyst should be able to explain why a row was included, excluded or allocated without editing the provider's evidence.

Explain a posted bank credit using its batch lines
1. Identify the posted credit and batch

Match account, currency and supported references. The credit has arrived; its composition needs explanation.

Ambiguous association

Leave the match provisional and obtain the supported trace. Do not select a nearby amount.

Recheck the credit-to-batch identity
A supported association permits calculation
2. Reconstruct the signed batch amount

Retain source rows; distinguish gross, net, fees, reserves and the payout balancing entry.

Compare the reconstructed amount with the bank credit
3. Does the evidence explain the difference?

In the example, 218 expected versus 216 observed leaves 2 unexplained.

Difference unexplained

Keep an owned exception. A possible fee is a hypothesis, not a balancing entry.

Recalculate when new source evidence arrives
An evidenced correction and repeat calculation may close the case
4. Retain a reproducible explanation

Another analyst can reconstruct every inclusion, exclusion and correction from unchanged source evidence.

The posted credit is real within this fictional worksheet, but the two-unit difference remains unexplained. Keep the original calculation and its source rows.

Leave the two-unit difference open

The example has not reconciled. It has identified a batch, reconstructed 218 and observed 216. A possible bank charge is a hypothesis until the relevant bank or provider evidence establishes it.

Assign the discrepancy an owner and next action. The investigation might find an omitted adjustment, a mistaken batch association, a documented charge or a different posting. Record the correction with its source; preserve the first calculation rather than quietly overwriting it.

The exception-management guide covers queues and resolution evidence. For the larger architecture joining orders, provider events and cash, use three-way reconciliation. This worksheet sits inside that system as a specific explanation of one posted credit.

Before closing the case, ask another analyst to reconstruct the amount from the retained source lines. They should reach the same result and understand every unresolved entry. A matched reference with a known discrepancy is useful progress. It should remain visibly different from a fully explained credit.

The worksheet, dates implied by its labels and amounts are fictional. Provider report guidance was checked on 25 October 2026.

Tags
settlement reconciliationbank creditpayout batch

Closing thought and further reading

A credit on the bank statement needs an explanation tied to its batch. A signed worksheet separates a matched reference from an explained amount.

Share article
LinkedInEmail
Keep reading
View all essays
Settlement & Reconciliation

Three-Way Reconciliation at Scale

Three-way reconciliation connects PSP records, the internal ledger and bank movement. Match the evidence, explain differences and assign the next action.

5 min read
Settlement & Reconciliation

Exception Management in Reconciliation

Exception management is where reconciliation either becomes a product or becomes a permanent ops queue.

5 min read
Payment Infrastructure

Issuing a card creates a service obligation

Disabling a lost card completes one action while earlier transaction questions may remain. Give the customer a clear account of both completed and open work.

4 min read
Operating proof
  • Simpaisa Payment Infrastructure Platform

    A regulated, multi-rail payments platform processing $1B+ annual GTV and 270M+ payments a year across pay-in, payout, wallets (DCB/IBFT), card acquiring (MPGS/MDES), settlement, FX and cross-border corridors, PCI DSS and ISO/IEC 27001 certified.

  • Settlement + Reconciliation Engine: Automated Recon at $1B+ GTV

    A multi-rail settlement and reconciliation engine, canonical double-entry ledger, three-way auto-reconciliation, exception management and corridor-aware payout windows. Closed the gap between treasury, finance and product at $1B+ GTV.

Continue the conversation

Need help applying this to your business?

Explore practical support for payment operations, product decisions, program delivery and AI automation, grounded in the challenges behind this essay.

Explore relevant supportEmail Rizwan
Payments Infrastructure Notes

Interested in future field notes?

Request email updates on payments, product decisions, program delivery and practical AI. Your request goes to my inbox for follow-up.

A request for occasional updates, with no weekly schedule promised.