Multi-currency invoicing is an accounting and reconciliation problem. You need a clear base currency, a rate source, rounding rules and a policy for gains and losses.
Key takeaways
- Store the transaction currency and the base-currency value at the rate used.
- Define the rate source and the time of capture; do not use a client-supplied rate.
- Round consistently and document the policy for tax and totals.
- Model the state and the exceptions before building the happy path.
What the system must model
- Reconcile payments in the settlement currency, including provider fees.
- Report in the base currency; show the original currency for the customer.
How to build it
- Choose the base currency. The currency of your reporting and tax.
- Define rate rules. Source, capture time and fallback.
- Model invoices. Transaction currency, base value, rate and rounding.
- Handle payments. Settlement currency, fees, partial payments and refunds.
- Reconcile. Invoice → payment → bank → ledger.
- Report. FX exposure and gains/losses with the accountant.
Design decisions
| Area | What to decide | Why |
|---|---|---|
| Base currency | Reporting currency | One source of truth |
| Rates | Source and timestamp | Audit the rate used |
| Rounding | Line vs total | Document the rule |
| Payments | Settlement currency | Separate fees and FX |
| Tax | Local rules | Get advice |
| Reporting | Base-currency reports | Explain FX differences |
Controls and reconciliation
- Keep an audit trail for money, tax and access changes.
- Make every event idempotent; retries are normal.
- Reconcile the provider, the ledger and the bank on a schedule.
- Test failure paths: declined payments, duplicate webhooks, refunds and partial payments.
- Document who owns finance, tax and technical support.
A minimum data model
| Entity | What it must hold | Why it matters |
|---|---|---|
| Customer | Identity, tax status, addresses, consent | Invoices and tax depend on it |
| Product/plan | Price, currency, tax code, effective dates | Prices change over time |
| Invoice | Lines, tax, due date, status | The legal record |
| Payment | Provider ID, amount, status, timestamps | Reconciliation |
| Credit/refund | Reason, amount, approval | Revenue and tax corrections |
| Audit event | Actor, action, before/after | Disputes and controls |
Launch checklist
- Test a full lifecycle: quote, invoice, payment, refund and credit note.
- Test a failed payment, a duplicate webhook and a manual retry.
- Reconcile a full day of transactions against the provider and the bank.
- Check tax rounding, currency formatting and negative amounts.
- Give finance a read-only view and a documented correction process.
- Monitor queue depth, failed jobs and reconciliation differences.
Failure modes to design for
| Failure | What the system should do | What to monitor |
|---|---|---|
| Duplicate webhook | Ignore by event ID; keep one ledger entry | Duplicate-event count |
| Payment timeout | Show an unknown state; reconcile, never assume failure | Pending payments |
| Price change mid-cart | Revalidate and show the new total | Price-mismatch errors |
| Partial refund | Adjust the invoice and tax proportionally | Refund reconciliation |
| Currency mismatch | Reject or convert with an explicit rate | FX differences |
| Job backlog | Alert before invoices or emails are late | Queue age |
Operational metrics
- Invoices created, paid, overdue and failed, by day.
- Reconciliation differences and the time to resolve them.
- Payment success rate by method and market.
- Tax and currency exceptions that required manual review.
- Time to close the month and the number of manual journals.
- Support tickets per hundred transactions.
Common mistakes
- Building the checkout before the billing state model.
- Trusting client-side amounts, currencies or tax rates.
- Ignoring refunds, credit notes and failed payments.
- Launching without daily reconciliation.
Frequently asked questions
Agree a source and a capture time with your accountant. The important thing is consistency and an audit trail, not a perfect rate.
Record the difference between the invoice value and the settled amount in the ledger. Confirm the treatment with your accountant.
Yes, but decide who bears the FX cost and how refunds and fees are handled. Show the currency and the amount clearly.
Use a documented rule per line or per invoice and keep it consistent. Test the totals against the tax authority's expectations.
Sources and further reading
- Stripe Billing documentation (docs.stripe.com)
- GOV.UK: VAT (gov.uk)
- EU VAT rules for businesses (europa.eu)
Related services
Building a billing or POS flow?
Describe the plans, currencies and payment methods. I will map the state model and the reconciliation points before you build.
How to cite this guide: Nur Hossain Repon, “Build multi-currency invoicing for your business: guide”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/build-multi-currency-invoicing-for-your-business-guide.





Comments
No comments yet.