04 / Payment reconciliationSettlements are hard to trace back to transactions.
Payment providers and internal systems use different references, dates and formats. Fees, refunds, chargebacks, currency conversion and settlement timing all sit between a sale and the payout. Even with a reconciliation prepared, the team still has to confirm what reached the ledger.
Common causes
- Fees deducted from the payout instead of invoiced separately.
- Refunds and chargebacks netted against later settlements.
- Currency conversion at the provider’s rate on the settlement date.
- Reserves and rolling holds released in later periods.
- The provider’s settlement day not matching the ledger’s period.
What to check first
- Rebuild one payout from the provider’s transaction-level report.
- Check whether fees are recorded gross or net, and that the treatment is consistent.
- List open reserves and holds at period end.
- Compare what was imported to the ledger with what the reconciliation approved.
What I can deliver
Every payout matched to the sales it settles, with fees, refunds and currency differences shown separately. Anything that doesn’t match goes to a short review list, and after posting, the ledger is checked against what was approved.
How it is solved
Make matching rules explicit.
Retrieve provider and internal records through APIs or consistent file inputs, then match in code on identifiers, amounts, currencies and timing rules. Send ambiguous matches to review. Classify timing items, duplicates and unexplained differences, each with a next step.
Verify what reached the ledger.
Where posting is in scope, build the approval steps into the workflow. After posting, read the records back from the accounting system and compare company, period, values and posting state. Run this check automatically after each import.
Wider benefits
- Focused investigation
The team works through classified exceptions with the source detail attached.
- Stronger controls
Missing, duplicated or changed import records are caught independently.
- Team cover
Documented rules and a shared exception list let colleagues take over without rebuilding the matching logic.
Is this the problem in front of your team?
Describe how it shows up in your business. The next step is a focused investigation, a review of one workflow, or a wider finance systems assessment.