Newsletter: monthly mandate & ERP support changes

Home › Guides

Invoice language, tax rounding and number formats across countries

Small formatting choices cause a surprising share of localization defects. A tax amount that differs by one cent between the invoice and the e-invoice file is rejected by a validator. A date printed as 03/04 is read as March by one customer and April by another. An invoice in the wrong language may not meet a local requirement. None of these is hard to fix, but each has to be decided, configured and tested per country.

This guide covers tax rounding (per line or per total), number, date and currency formats, and invoice language. It shows the effect of rounding with a worked table and gives a format checklist.

Decide how tax is rounded

There are two common methods:

Each authority may have a rule or a preference, and structured invoice formats often include validation rules that check how line, tax and document totals relate. Ask the tax owner which method applies in each country, and check the validation rules of the e-invoice format you send. Then set the ERP accordingly, per legal entity if needed. Do not let the ERP, the e-invoicing converter and the customer's system each round differently.

Worked example

The 20% rate is an example only. Three lines are invoiced at the same rate.

LineNetTax, unroundedTax, line rounding
11.990.3980.40
22.490.4980.50
33.330.6660.67
Total7.811.5621.57
Total rounding: 7.81 × 20%1.5621.56

Line rounding gives 1.57; total rounding gives 1.56. A difference of 0.01 per invoice looks trivial, but if the ERP posts 1.57 and the e-invoice file shows 1.56, the file may fail validation, and over thousands of invoices the tax account will not agree with the return.

Example entries: the same invoice under each method (illustrative)
StepAccountDebitCredit
Total roundingTrade receivables9.37
Sales revenue7.81
Output VAT1.56
Line roundingTrade receivables9.38
Sales revenue7.81
Output VAT1.57

Pick one method per entity and use it in the ERP, the invoice print, the e-invoice file and the tax report. Where an amount in foreign currency is converted for the tax report, decide also whether you convert the rounded tax or recalculate it from the converted net; see invoice, tax, ledger and reporting currencies.

Number, date and currency formats

Structured files usually use fixed formats (for example a dot as decimal separator and an ISO-style date), whatever the country. Printed or PDF invoices are read by people and follow local habits. Keep the two apart: the file follows the specification, and the print follows the customer's locale.

Invoice language

Some countries set rules on the language of invoices or of particular invoice types. This site records one verified example: on the Saudi Arabia page, simplified tax invoices must be issued in Arabic (source: ZATCA). For other countries, check the authority's current notice; this site does not yet hold language facts for them. Where a second language is allowed or required, decide which fields are translated (item descriptions, payment terms, legal notes) and where the translations live.

Format checklist

ItemDecision per countryWhere configuredTested
Tax rounding method (line or total)
Rounding precision for tax and totals
Cash rounding on payable total, if used
Decimal and thousands separators on print
Date format on print
Currency code or symbol and its position
Invoice language and translated fields
Number and date format in the e-invoice file (from the specification)
Character set for names and addresses

Test each country with an invoice that has many lines with awkward amounts, a credit note, a foreign-currency invoice and names with local characters. Compare the printed invoice, the e-invoice file, the ledger posting and the tax report. The acceptance tests guide shows how to record the evidence.

Worksheet

Use the rounding and format checklist.

Worksheet: Rounding and format checklist

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Show the worksheet

Use with the invoice language, rounding and number formats guide. One copy per country or legal entity.

Decisions

ItemDecisionSource or reasonApproved by
Tax rounding method (line or total)
Rounding precision
Cash rounding
Separators on print
Date format on print
Currency display
Invoice language and translated fields
e-invoice file formats (from the specification)

Rounding test

LineNetRateTax unroundedTax line-rounded
Total rounding result

Other tests

Sources checked: 27 October 2026. The Saudi language fact comes from the verified row on this site. Rounding rules and other language rules are national and are not stated here.

Data on this site: E-invoicing country × ERP matrix · Country pages with sourced key facts

In E-invoicing operations: previous Operate self-billing and buyer-issued invoices without duplicating purchases · Guides by task · All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-27.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: · Markdown version · Suggest a correction

Newsletter – monthly digest of mandate and ERP support changes. Subscribe on the home page.