How to reconcile payments across multiple currencies and payment providers
Payment reconciliation connects your business records, each provider's activity, its payouts and the receiving account.
Payment reconciliation connects your business records, each provider's activity, its payouts and the receiving account. Keep currencies separate until you can explain the conversion. Use a report that answers the matching question: Stripe's payout reconciliation report, for example, connects an automatic payout with the transactions behind it. Its balance report serves a different purpose. Stripe payout report, Stripe balance report.
The workflow below is a proposed way to organise that work across providers. Adapt it to the reports and account arrangements you actually have. It is not a promise that all providers supply identical fields or use the same settlement rules.
Choose the evidence before building a matching rule
Start by listing the providers, receiving accounts and currencies in scope. For each combination, identify the business record, provider activity report, payout record and receiving-account statement available to your team. Keep the original files alongside your working data so another reviewer can trace a result back to its source.
Stripe's documentation illustrates why report selection matters. Its balance report shows activity in settlement currency after conversion and does not itself associate payouts with payment transactions. For automatic payouts, use the payout reconciliation report to investigate the batch. Stripe balance report.
Make an evidence checklist for your own environment. Record which report supplies the transaction reference, the amount and currency, the payout relationship and the relevant dates. Mark a missing connection explicitly. Do not assume that a sales export and a settlement report describe the same stage of the payment.
Connect the business transaction to the provider record
Use a reference that survives from your business system into the provider's report. Stripe supports custom metadata in itemised reporting, which can help connect its transactions to accounting records. Stripe balance report.
As a working rule, retain the original business reference and provider identifier together. Preserve the account and currency as part of the match. A repeated amount is a reason to review the evidence, not a reliable identifier on its own. Where the connection is ambiguous, leave the item unresolved and state what information would resolve it.
Keep the matching rule readable. A reviewer should be able to see which fields were used and why the match was accepted. If someone corrected a reference manually, retain the explanation rather than silently replacing the original value. This proposed record of decisions is also useful when the team later decides which steps are suitable for automation.
Explain the payout rather than comparing sales totals
Stripe's itemised payout report includes payments, refunds, disputes, fees and other balance transactions. Use the included movements to explain the payout instead of comparing a gross sales total directly with a bank receipt. Stripe payout report.
For each provider, document the equivalent connection its own reporting supports. Start with a payout or settlement reference where one exists. Keep the components together with that transfer in your working record. If the report does not give you a batch relationship, record that limitation and investigate the provider's documented reconciliation route.
Separate the questions you are trying to answer. Does the provider's report explain the transfer? Does the receiving account show that transfer? Does the business system contain the underlying transaction? A match at one stage should not silently close an unexplained difference at another stage. Retain a clear review state for each unresolved connection.
Investigate currencies and dates before calling an item missing
Stripe's payout report uses estimated arrival dates, which can differ from the date a bank posts the deposit. Report processing can also finish after the payout arrives. Stripe payout report.
For your own reconciliation, note what each date field represents and which time zone the report uses. Keep the reporting period and account statement period visible. When a transfer seems absent, inspect the relevant neighbouring dates and report availability before treating it as an unexplained loss.
Where a conversion occurs, preserve the original and settlement amounts and currencies supplied by the records. Stripe's balance reporting presents transactions in settlement currency after conversion; that is a reason to identify which currency you are matching at each stage. Stripe balance report.
Treat a missing transaction, a separately reported fee and an exchange difference as different investigation questions. The person responsible for your accounts should decide the accounting treatment. This operational workflow does not decide recognition, valuation or tax policy.
Give unresolved differences an owner and a next action
The different movement types in Stripe's payout report provide a useful starting point for an exception list: payments, refunds, disputes and fees need to remain distinguishable. Stripe payout report.
For each exception, record the affected references, account, currency, observed difference and evidence still needed. Assign someone to investigate and write down the next action. Use practical descriptions such as missing reference, unexplained payout component, conversion question or date mismatch. These are proposed review categories, not universal provider statuses.
Close an exception when the relationship is explained and the supporting record is retained. If the same gap returns, review the reference capture, export mapping or responsibility that causes it. Automating a rule whose inputs are still ambiguous makes that uncertainty harder to inspect. Begin automation with the matches your team can already explain consistently.
When the problem crosses systems, define the coordination work
If the recurring difficulty is the handoff between providers, internal records and teams, scope a discussion around the unresolved connection. Bring an outline of the providers, currencies and available reports, without sending confidential transaction records.
Discuss your financial systems with FundsEarth. Establish the problem and the implementation scope before choosing a new tool or provider.