Why processor statements and the ledger still disagree

When a Taiwan payment firm sits down for an audit, the first friction is rarely fraud. It is the quiet gap between the processor’s settlement file and the revenue ledger. Fees may be netted differently, foreign-currency batches may post a day later, and chargebacks may hit a suspense account that no one clears on a fixed cadence.

Start with the calendar, not the export

Ask which business day the processor uses for cut-off, then compare that to when your general ledger closes. Many mismatches shrink once both sides use the same settlement date rather than the card authorisation date.

Sample the noisy buckets

Suspense, merchant reserves, and fee accruals deserve denser samples than clean card sales. In fieldwork we often pull every item aged over seven days in suspense before we touch routine sales lines.

Document the story in one paragraph

Supervisors and boards do not need every join key. They need a short explanation of why a known difference exists, who owns the clearance, and when it should disappear. That narrative belongs beside the reconciliation, not in a separate chat thread.

If your team is preparing for a fintech assurance audit, bring the last three months of break logs to the scoping call.