Automated payment reconciliation: how to reconcile cross-border payments
Payment reconciliation means matching every payment in and out of your accounts to the invoice, bill or ledger entry it belongs to. Automated payment reconciliation does that matching with rules and data feeds instead of spreadsheets. Cross-border payments make it harder, because FX, deducted fees, short references and timing gaps all break simple one-to-one matches.
Payment reconciliation means matching every payment in and out of your accounts to the invoice, bill or ledger entry it belongs to. Automated payment reconciliation does that matching with rules and data feeds instead of spreadsheets. Cross-border payments make it harder: FX changes the amount, intermediary banks deduct fees, some rails truncate references, and payments land on different days. This guide explains how automated reconciliation works and how to set it up for cross-border flows.
Why cross-border payments break simple matching
| Cause | What you see | How to handle it |
|---|---|---|
| FX conversion | Amount received differs from the invoice amount | Reconcile in the invoice currency, and record the FX rate and margin |
| Deducted fees | Short payment under SHA or BEN | Tolerance rule for expected fees; record fees separately |
| Truncated reference | Invoice number cut off or missing | Short, unique references with the invoice number first |
| Timing | Payment arrives a day or more later, or across a weekend | Date window in the matching rules |
| Several currencies | Balances in GBP, EUR and USD | One ledger per currency account, reconciled separately |
| Returns | A payout comes back, minus fees | Treat as its own event and reopen the bill |
For why fees get deducted on the way, see what is an intermediary bank?
How automated payment reconciliation works
- Collect the data. Pull payment data from your bank or provider by API, bank feed or file, and capture events from webhooks.
- Normalise it. Put every item into one shape: date, amount, currency, reference, counterparty, and the provider’s own ID.
- Match in layers. Exact reference and amount first; then rules with tolerances for fees, FX and dates; then payer name or account.
- Queue the exceptions. Anything unmatched goes to a person, with the reason it failed.
- Post to the ledger. Matched items are booked against the invoice or bill, with fees and FX as their own lines.
- Close the loop. Reconcile account balances, not just transactions, at the end of each day.
References by rail
References are the strongest matching key, but each rail limits their length:
| Rail | Reference length |
|---|---|
| Faster Payments | 18 characters |
| CHAPS | 35 characters |
| SEPA credit transfer | 140 characters |
Use one unique reference per invoice and put the invoice number first, so it survives the shortest rail you use.
What to measure
- Auto-match rate: the share of items matched without a person. Track it per rail and per currency.
- Exception age: how long unmatched items wait. Old exceptions hide real problems.
- Unexplained differences: small amounts written off without a reason. They add up.
Controls that matter
- Separation of duties: the person who resolves exceptions should not also approve payments.
- An audit trail: record why each item matched and who resolved each exception.
- Daily balance checks: the ledger and the account balance should agree every day.
- Verify webhooks: check each signature before you trust an event, and still read the account history periodically.
Where KwiikPay fits
KwiikPay gives businesses named GBP, EUR and USD accounts in their own company’s name, held apart from KwiikPay’s own money, with FX across 40+ currencies, the margin shown before you confirm, and payouts across 30+ corridors to 80+ countries through regulated banking partners. Every payment carries your reference, and account activity records who started each payment.
On plans with API access, the KwiikPay API lets you read every ledger movement on each account, deposits as they arrive, payouts and their state, conversions with the rate they filled at, and your balance. Signed webhooks report deposits and completed or returned payouts. See the developer page and our payment API integration guide.
KwiikPay onboards companies incorporated in the European Economic Area, the United Kingdom, Gibraltar, Switzerland and Canada, where any authorisation their activity requires is current. Companies elsewhere are assessed individually, with no presumption of approval. Account opening is by invitation: request an account and the team replies within one business day.
KwiikPay is a trading name of KWP Finance Limited — registered in Canada as a Payment Service Provider under the Retail Payment Activities Act (RPAA), supervised by the Bank of Canada, and as a Money Services Business with FINTRAC (MSB registration number C100000942), including dealing in virtual currency. These are registrations, not licences. KwiikPay is not authorised by the FCA. KwiikPay is not a bank; banking and e-money services are provided by regulated partner institutions.
FAQs
What is automated payment reconciliation?
It is matching payments to the invoices, bills and ledger entries they belong to using software rules and data feeds, instead of doing it by hand. Payment data arrives from your bank or provider by file, API or webhook, the rules match each item, and anything that does not match goes to an exceptions queue for a person to resolve.
Why is cross-border payment reconciliation harder?
Because the amount, the currency and the reference often change on the way. FX turns one invoice amount into another, intermediary banks can deduct fees under the SHA and BEN charge options, some rails truncate references, and payments arrive on different days in different time zones. Each of those breaks a simple exact match.
How does automated payment matching work?
In layers. First exact matches on a unique reference and amount; then rules with tolerances, such as an amount within an expected fee range or a date window; then matches on the payer's name or account. Whatever is left becomes an exception. Good setups record why each item matched, so an auditor can follow it.
What payment references should I use?
A unique reference per invoice, short enough for the tightest rail you use. Faster Payments references are limited to 18 characters, CHAPS to 35 and SEPA credit transfers to 140. Put the invoice number first, so it survives any truncation.
How do I handle fees deducted from international payments?
Record the fee as its own line rather than as an underpayment. Set a tolerance rule for expected intermediary fees, flag anything outside it, and where you pay suppliers, consider the OUR charge option so they receive the full amount.
How do webhooks help reconciliation?
A webhook tells your system the moment something happens, such as a deposit arriving or a payout completing or coming back, so you reconcile from events rather than waiting for a daily statement. Verify each webhook's signature, and still run a periodic read of your account history to catch anything an event missed.
