Why Does Everyone Reconcile If Computers Did the Work?

A customer pays $100. The payment provider says the charge succeeded. Later, the merchant receives a bank deposit that is not $100.

Nothing is necessarily wrong.

The deposit may combine many customer payments. Fees may have been deducted. A refund or dispute may have changed the balance. Some transactions may still be pending while others became available. The payout date may not match the sale date.

This is why reconciliation survives every promise of financial automation.

There is no single computer doing “the payment.”

The merchant records an order. The processor records a payment and changes to its internal balance. The card network or ACH operator carries messages and settlement obligations. The bank records a deposit. Accounting records revenue, fees, refunds, and cash. Each system observes a different event at a different boundary.

Reconciliation asks whether those partial records describe the same economic result.

A processor’s payout report makes the problem visible. One bank deposit can correspond to a batch containing charges, refunds, disputes, fees, and adjustments. Stripe, for example, provides balance records and payout-reconciliation reports specifically so a merchant can connect the transactions in a processor balance to the amount delivered to its bank account.

The identifiers do much of the real work. A payment ID connects the application to the processor. A balance-transaction ID connects the payment to a change in the processor’s ledger. A payout ID groups the changes sent to the bank. A bank trace or reference helps locate the external transfer.

Without those links, teams reconcile by amount and date. That works until two payments share an amount, a payout crosses a reporting boundary, or a correction arrives late.

Good reconciliation does more than make totals equal. It preserves the mismatch long enough to understand it.

• A payment exists locally but not at the provider.
• The provider accepted it, but the application missed the response.
• A payout contains an adjustment the accounting system did not classify.
• The bank received a different amount from the processor’s expected net.
• A return or dispute changed a transaction after an earlier report closed.

Automatically forcing one ledger to match another can hide the very failure reconciliation was meant to expose. The useful outcome is not always “fixed.” Sometimes it is “explained,” “waiting for external evidence,” or “assigned for review.”

Computers reduce the manual work of matching records. They do not remove the need for independent records to agree.

Automation can move the money.

Reconciliation proves which movement everyone is talking about.

Further Reading

• Stripe, How to Select a Report
• Stripe, Payout Reconciliation
• Federal Reserve Financial Services, FedACH APIs