Free tier

← All guides · EN 16931 & validation

10 common e-invoice mistakes — and the rule that catches each one

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

The same mistakes recur wherever PDF habits meet structured validation: (1) totals typed instead of computed (BR-CO); (2) standard lines at 0% (BR-S-08); (3) reverse charge without the buyer's VAT identifier (BR-AE-02); (4) cross-border invoices missing the seller's identifier (BR-CO-26); (5) negative lines for discounts; (6) credit notes coded 380 instead of 381; (7) currency written as a word (BR-04); (8) merged VAT treatments on one line; (9) invoices with no lines (BR-16); (10) sending the PDF alone into a mandate country.

Why these mistakes recur

Each mistake is a PDF-era habit colliding with a specific EN 16931 rule implemented in this product's validator — the BR-CO totals comparisons, BR-S-08, BR-AE-02, BR-CO-26, BR-03, BR-04, BR-16 and the line rules (BT-129 quantity, BT-146 price, BT-151/152 category and rate). They recur because templates encode them: fix the template and the mistake class dies; fix only the invoice and it returns next month.

Mistakes 1–3: arithmetic and VAT habits

1. Typed totals. The payable amount carried from a quote or typed over a computed figure disagrees with the lines by design or by drift, and BR-CO-13/14/15 compare them mercilessly. Fix: never supply totals; let the engine derive them, and treat any expected-totals mismatch as a factual hunt (missing line, stale price, misplaced discount).

2. S at 0%. A template defaults every rate to zero, and standard-rated lines inherit it — BR-S-08 requires S to carry a rate above zero. The deeper error is usually categorical: the line is really reverse charge (AE) or zero-rated (Z) wearing S as a default. Fix: choose the category deliberately per line, then set the rate the category demands.

3. Reverse charge without the buyer's identifier. Years of PDFs never asked, so the field is empty when BR-AE-02 asks. Fix at onboarding: identifiers are collected with the engagement paperwork, gated before first invoice, and stored in the client record — never chased at billing time.

Mistakes 4–6: identifiers, signs and codes

4. Missing seller identifier cross-border. BR-CO-26 requires the seller's VAT identifier (BT-31) whenever countries differ. Fix once, permanently: the identifier lives in the seller template, verified character-by-character against your registration, inherited by every invoice.

5. Negative lines. A discount expressed as a line of −EUR 200 violates the non-negative price rule and poisons the tax breakdown. Fix: discounts live in allowance fields; value given back after invoicing lives in a credit note (381). The model has a place for every negative idea — it is just never a line.

6. Credit note coded 380. The duplicated-template trap: perfect data, wrong verb — the client's system books a second charge instead of a credit. Fix: the one-sentence substance test before conversion ('this document gives value back → 381'), with the type code reviewed like the invoice number.

Mistakes 7–9: codes and structure

7. Currency as a word. 'Euro', 'euros', a lowercase code in a data import — BR-04 accepts only the supported ISO codes (EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK, NOK). Fix: currency is a constrained field in the template, chosen from the list, never typed freehand.

8. Blended lines. Two treatments in one line — goods at one rate, services reverse-charged, averaged into a fiction — corrupts the tax breakdown's grouping and the client's booking. Fix: one treatment per line, always; the breakdown can only group what lines truthfully declare.

9. The line-less invoice. A document of totals and prose with BG-25 empty fails BR-16 outright. It survives in the wild as the 'summary invoice' PDF. Fix: the lines are the invoice; if the supply cannot be itemised, it cannot yet be invoiced — itemise it, even as one honestly-described line.

Mistake 10: the right invoice, the wrong artefact

10. Sending the PDF alone into a mandate country. The invoice data is perfect, the conversion clean — and then someone emails the readable PDF (or worse, a scan of it) to a Belgian or Italian client whose system requires the structured document. The failure is logistical, not documentary: the operative file never travelled. Fix: the pair is the deliverable — UBL for the system or channel (Peppol via Qvalia, platform routes per client), Factur-X PDF for the humans — sent together, filed together, every time.

Notice the pattern across all ten: none requires tax genius. Each is a habit — of templates, records or sending routines — and each dies permanently when its habit is replaced. That is the encouraging arithmetic of the list: ten mistakes, ten one-time fixes, and a billing process that has quietly stopped producing them.

Building the mistake-proof template

Harvest the fixes into one artefact: a template (and client-record standard) in which totals are always derived, category is a deliberate choice with its rate paired, identifiers are pre-filled from verified records, currency and type code are constrained selections, lines are structured per item and treatment, and the sending step names both files of the pair. Convert one maximally-complex invoice through it — mixed treatments, an allowance, a prepaid amount — and keep the passing configuration as the firm's reference.

Then let the exception log audit you: every failure that still occurs names its rule, and a rule appearing twice names a template gap the harvest missed. Within a quarter, the log should bore you. Boredom, in invoicing, is the sound of a system working — the mistakes on this page become stories about other people's invoices.

The mistake sweep in 5 steps

  1. Search your template for typed totals and free-text coded fields (currency, type code) — constrain or derive each one.
  2. Pair every category with its rate rule in the template: S above zero; Z, E, AE at exactly zero.
  3. Pre-fill identifiers from verified records: seller's in the template, buyers' in client records gated at onboarding.
  4. Rebuild lines per item and per treatment; move every discount into allowances and every credit into a 381 document.
  5. Make the pair the sending unit — UBL plus Factur-X — and file delivery evidence with both files.

Worked example: four mistakes in one small invoice

A EUR 940.00 invoice arrives for correction practice: its payable is typed as EUR 940.00 while its lines (2 × EUR 400.00 plus a EUR 100.00 line) compute EUR 900.00 (mistake 1, BR-CO); its main line is S at 0% though the supply is cross-border reverse charge (mistakes 2 and 8's cousin); the buyer's VAT identifier is absent (mistake 3, BR-AE-02); and it was originally emailed as a lone PDF to a Belgian client (mistake 10).

Corrected: lines recoded AE at 0% as three honest lines totalling EUR 900.00… plus the missing EUR 40.00 item found and added as its own line — the typed total had been concealing a lost line all along — buyer identifier added from the client record, totals derived (payable EUR 940.00, now earned rather than asserted), and the pair sent with the UBL going through Qvalia. One invoice, four lessons, each retired into the template the same afternoon.

Frequently asked questions

Which mistake is most common?

In conversion practice here, the VAT family (category-rate mismatch, especially S at 0%) and missing cross-border identifiers vie with typed totals. All three are template-level, so all three are permanently fixable.

Why can't I use a negative line for a discount?

Line prices must be non-negative; the model gives discounts their own home (allowance fields) where the tax arithmetic can treat them correctly. Negative lines corrupt the breakdown.

My totals are off by one cent — is that really a failure?

Yes: BR-CO compares exactly. One cent means a rounding-method difference or a stale figure; derive totals in the converter and the cent takes care of itself.

Is sending the Factur-X PDF alone also mistake 10?

The Factur-X PDF carries the structured XML, so it is not a 'plain PDF'. But where the client's channel wants the UBL itself (Peppol, platform intake), send the XML through that channel — the pair, routed properly, is the safe unit.

How do I find mistakes before the client does?

Convert through validation and read the exception list as a template audit: a repeated rule is a template defect. The converter is the cheapest place any mistake can surface.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back