← All guides · Formats & conversion
Multi-currency e-invoices: currency codes, totals and what validation checks
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
Every amount on an e-invoice is expressed in the invoice's currency, declared once as an ISO 4217 code (BT-5). This product's validator accepts EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK and NOK; anything else — including the word 'Euro' — fails BR-04. Lines, tax breakdowns and totals all compute in that single currency, rounded to two decimals.
What is the invoice currency in EN 16931?
The invoice currency (BT-5) is the ISO 4217 code in which all the invoice's amounts are expressed. The engine's CURRENCIES set is {EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK, NOK} and BR-04 states: 'Currency is not a supported ISO 4217 code' when the value falls outside it. In the UBL output the currency appears as the document currency code, and every monetary amount inherits it.
One invoice, one currency
The model is deliberately simple: a single document currency governs every figure on the invoice — line prices, extensions, tax amounts, totals. There is no per-line currency and no exchange-rate field doing quiet conversions in the background. If you bill a client in two currencies, you issue two invoices; if your costs are in one currency and your price in another, the conversion happens in your pricing, before the invoice exists, and the invoice speaks only its own currency.
That simplicity is what lets the BR-CO arithmetic be absolute: totals reconcile because every operand shares a unit. The moment an invoice mixed units silently, its totals would be numerology. Structured invoicing refuses the ambiguity at the model level — a discipline worth appreciating if you have ever untangled a spreadsheet invoice whose total 'included the conversion, roughly'.
The code list and BR-04
Thirteen codes are supported here, covering the EU's currencies and the majors a European supplier meets: the euro, the US dollar, pound sterling, Swiss franc, and the currencies of Poland, Sweden, Denmark, Czechia, Hungary, Romania, Bulgaria, Croatia and Norway. The validator's demand is formal — the value must be one of these codes — and the failure is blunt: type 'Euro', 'eur ' with a stray space in a data import, or an exotic code outside the list, and BR-04 stops the conversion.
Invoices to EU clients are most often EUR simply because the eurozone dominates the mandate map, but the code must follow the contract, not the geography: a Swiss client's CHF invoice and a Polish client's PLN invoice are equally ordinary. What is not ordinary — what no receiving system will accept — is ambiguity about which currency a figure is in. The code settles it in three letters.
Rounding in different currencies
The engine rounds monetary values to two decimals (half-up) at the defined points — per line extension, and through the totals computation. That convention is uniform across the supported currencies in this implementation, which keeps the arithmetic portable: an invoice's figures reconcile identically whether its code is EUR or SEK, because the rounding rule travels with the computation rather than with local habit.
Where your own pricing works in fractions — hourly rates with repeating decimals, unit prices in tenths of a cent — decide the rounding at the line, in the price you state, rather than expecting totals to absorb it. The line extension is quantity times the stated price, rounded once; a price chosen at two-decimal precision makes every downstream figure exactly reproducible by your client's system and your own books alike.
Currency, VAT and the client's books
The tax breakdown is computed in the invoice currency: taxable amounts and tax per category-rate pair, in the document's code. Your client's system books those figures as stated — a EUR invoice enters a EUR ledger directly; a foreign-currency invoice enters their process with the currency attached as data, which is precisely what their accounting needs to handle conversion on their side, at their rates, under their policies.
For your own books the symmetric point holds: export the conversion to Xero, QuickBooks or CSV and the figures arrive with their currency context intact, derived from the validated invoice rather than re-typed from a PDF whose currency symbol someone had to squint at. Currency errors in bookkeeping are disproportionately transcription errors — a $ read as a € in a hurried manual entry. Structured data, exported rather than transcribed, retires that whole species of mistake.
Practical currency policy for EU-facing suppliers
Agree the invoice currency in the engagement terms, before work starts, and record it in the client record beside the identifiers. Defaulting each invoice afresh invites drift — the same client billed in EUR in March and USD in April because a template was copied from another client's file. Where a client asks for a currency outside the supported list, that is a conversation to have before invoicing, not a code to improvise at conversion time.
And keep the demonstration discipline: the converter's form takes the currency in §1 with the other header fields, because it is a header-level fact about the document. Set it deliberately, like the type code — another three-character field whose correctness decides whether the receiving system can act on everything that follows it.
Multi-currency invoicing in 5 steps
- Agree the invoice currency in the engagement terms and record it in the client record.
- Use the exact ISO code (EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK, NOK) — never a word or symbol.
- Keep one currency per invoice; split multi-currency billing into separate invoices.
- State unit prices at two-decimal precision so line extensions reproduce exactly in any system.
- Export conversions to your accounting tool so currency context travels with the figures — no transcription.
Worked example: the same engagement in two currencies, honestly separated
A consultant bills a Swiss client CHF 4,200.00 for a workshop series (invoice A, currency CHF, lines CHF-denominated, tax per the agreed treatment, totals in CHF) and a Polish client PLN 9,600.00 for the same programme (invoice B, currency PLN). Each invoice reconciles internally to the cent under the BR-CO checks, because neither mixes units.
The tempting shortcut — one invoice, some lines 'in francs, roughly converted' — would fail the model's basic premise and produce a total nobody could recompute. Two clean invoices cost one extra conversion; the shortcut costs the invoice's credibility in both clients' systems.
Frequently asked questions
Which currency codes are accepted?
EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK and NOK. BR-04 rejects anything else, including currency names written as words.
Can one invoice carry two currencies?
No — the document currency (BT-5) governs every amount on the invoice. Bill in two currencies as two invoices.
How are amounts rounded?
To two decimals, half-up, at defined points in the computation (line extensions and totals) — uniformly across currencies in this engine, so totals reproduce exactly.
Should EU invoices always be in EUR?
The code follows your contract with the client. EUR is most common across the mandate map, but CHF, PLN and the other supported codes are equally valid where agreed.
Does the tax breakdown show currency per line?
The breakdown is computed in the invoice's single currency — taxable amount and tax per category-rate pair, all in the document currency code declared in the header.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Structured invoice fields: every field an EN 16931 invoice needs, checked
- Invoice totals and the BR-CO rules: how e-invoice arithmetic must reconcile
- EN 16931 business rules explained: what BR codes mean when validation fails
- Exporting converted invoices to Xero, QuickBooks and CSV
- Convert your first invoice free: a walkthrough of the one-invoice job