E-invoicing guides
How structured invoicing actually works — the EN 16931 rules, the formats (UBL 2.1, Factur-X, Peppol BIS), every mandate country’s dates, and the day-to-day workflows of converting, validating, sending and archiving invoices that systems accept. Every guide is written from what EInvoice Translator does: convert one invoice free, check acceptance, and send with confidence.
Start with the free tool
Convert one invoice free · Acceptance checker · Pricing · About
When an invoice fails validation
- Invoice exception-resolution workspace
The workspace where a rejected invoice’s validation errors are worked through field by field until it validates.
EN 16931 & validation
- What is EN 16931 and why does your invoice need to follow it?
EN 16931 is the European standard that defines a structured electronic invoice. What it contains, which business rules it enforces, and how to produce an invoice that follows it. - EN 16931 business rules explained: what BR codes mean when validation fails
A plain-language guide to the EN 16931 business rules (BR) an invoice validator checks — required fields, VAT category rules and the BR-CO totals arithmetic — and how to fix each failure. - How to validate an e-invoice before you send it (and read the errors)
Validation checks an invoice against the EN 16931 business rules before your client's system does. The checks that run, the order to fix failures in, and how the exception workspace helps. - VAT categories explained: S, Z, E, AE, K, G and O on an e-invoice line
Every e-invoice line carries a VAT category code and a rate, and the two must agree. What each category means, when to use it, and the validation rules that bind category to rate. - Invoice type codes 380, 381, 384 and 389: what each one means
The invoice type code (BT-3) tells receiving systems what kind of document they hold: 380 invoice, 381 credit note, 384 corrected invoice, 389 self-billed invoice. Choosing wrong books money in the wrong direction. - My e-invoice was rejected: how to read the error and fix the real cause
A rejected e-invoice comes back with rule codes, not explanations. How to triage rejections by family — presence, codes, VAT agreement, identifiers, totals — fix the source, and stop the same rejection recurring. - Invoice totals and the BR-CO rules: how e-invoice arithmetic must reconcile
The BR-CO rules force an invoice's stated totals to equal the totals computed from its lines — line extensions, tax per category and rate, allowances, charges, prepaid. How the computation runs, line by line. - Reverse charge VAT on e-invoices: category AE, 0%, and the identifier rule
Reverse charge moves the VAT accounting to the buyer: your lines carry category AE at 0%, and across borders the buyer's VAT identifier must be on the invoice. How reverse charge validates and where it applies. - Cross-border invoices: when seller and buyer VAT identifiers are required
Cross-border B2B e-invoices carry two identifier duties: the seller's VAT identifier is always required, and the buyer's is required when any line uses reverse charge (AE). The rules, and the onboarding habit that satisfies them. - Allowances, charges and prepaid amounts on an e-invoice, explained
Discounts belong in allowance fields, surcharges in charge fields, and deposits in the prepaid field — where the totals arithmetic can see them. How the three adjustments work inside the BR-CO computation. - Structured invoice fields: every field an EN 16931 invoice needs, checked
A field-by-field tour of the structured invoice: number, dates, type code, currency, both parties in full, lines with VAT treatment, allowances, charges, prepaid — and the business term (BT) each field answers to. - 10 common e-invoice mistakes — and the rule that catches each one
Typed totals, S at 0%, missing VAT identifiers, negative lines, credit notes coded as invoices, currencies written as words: the recurring mistakes of the PDF-to-structured transition, each with its fix. - Self-billed invoices (type code 389): when the buyer issues your invoice
Self-billing flips the pen: the buyer creates the invoice in the seller's name, coded 389, under a prior arrangement. How it works, what must be agreed first, and what the seller must still check. - VAT categories K, G and O: intra-EU goods, exports and outside-scope lines
Beyond S and AE: category K for intra-EU supplies of goods, G for exports outside the EU, O for supplies outside VAT's scope — plus L and M. When each applies, and how the validator treats them.
Formats & conversion
- What is a UBL 2.1 invoice and when do you need one?
UBL 2.1 is the XML syntax that carries EN 16931 invoices and Peppol BIS invoices. How it is structured, how it differs from a PDF, and how to create one from an ordinary invoice. - What is a Factur-X invoice? The PDF with the invoice inside it
Factur-X is a PDF invoice with the EN 16931 structured invoice embedded as XML, so people can read it and systems can book it. How it works, where it is used, and how to create one. - PDF invoice vs e-invoice: why a PDF is no longer an invoice in much of the EU
A PDF invoice is a picture of an invoice; a structured e-invoice is data a system can book. The legal and practical difference, country by country, and how to move from one to the other. - What is a CIUS? How countries tailor the EN 16931 core invoice
A CIUS (Core Invoice Usage Specification) is how a country or sector publishes its exact application of the EN 16931 core model — like Portugal's CIUS-PT and Germany's XRechnung. What a CIUS can and cannot change. - XRechnung vs ZUGFeRD: Germany's two e-invoice formats compared
XRechnung is Germany's pure-XML EN 16931 profile; ZUGFeRD is the hybrid PDF with structured data embedded — the counterpart of Factur-X. Which clients want which, and what to send. - How to convert a PDF invoice to XML (UBL) that validates
Converting a PDF invoice to XML is not a file-format trick: the data must be re-expressed as a structured EN 16931 invoice and validated. The reliable workflow, step by step. - Multi-currency e-invoices: currency codes, totals and what validation checks
An e-invoice's currency is a code (BT-5) from the ISO list — EUR, USD, GBP, CHF, PLN and more. How currency flows through lines, tax breakdowns and totals, and the mistakes that fail validation. - How to verify a Factur-X PDF really contains its XML invoice
A Factur-X PDF's claim rests on its embedded factur-x.xml. How the attachment works, how to check it is present and identical to the structured invoice, and how this product proves it in its own test suite.
Country mandates
- Belgium's Peppol e-invoicing mandate: what B2B suppliers must do from 2026
Belgium requires structured B2B e-invoicing via Peppol from 1 January 2026. What that means if you invoice Belgian clients, how to build a compliant invoice, and how guided Peppol sending works. - Poland's KSeF e-invoicing mandate: dates, phases and what suppliers must send
Poland's KSeF becomes mandatory in phases: large taxpayers from February 2026, all others from April 2026. How the phase-in works, what the acceptance checker reports, and how to prepare your invoice data. - France's e-invoicing reform: receive from September 2026, SMEs issue from 2027
France's reform splits into two duties: every business must receive structured invoices from 1 September 2026, and SMEs must issue them from 1 September 2027. What suppliers need to know, and where Factur-X fits. - Germany's e-invoicing rules: receiving since 2025, issuing phased 2027–2028
Germany already requires businesses to receive structured e-invoices (since January 2025) and phases in issuing: January 2027 above EUR 800k turnover, January 2028 for all. XRechnung and ZUGFeRD explained for suppliers. - Spain's B2B e-invoicing mandate: October 2027 for large firms, 2028 for the rest
Spain phases in B2B structured e-invoicing: 6 October 2027 for turnover above EUR 8M, October 2028 for everyone else. The timetable, the checker verdicts, and how suppliers prepare their invoice data now. - Italy's SdI e-invoicing: the mandate that has run since 2019
Italy requires B2B invoices to pass through SdI in structured form — and has since 2019, the longest-running mandate in Europe. What that means for suppliers, and why a plain PDF is not an invoice in Italy. - ViDA 2030: intra-EU B2B e-invoicing becomes mandatory on 1 July 2030
The EU's VAT in the Digital Age programme sets the backstop: from 1 July 2030, structured e-invoicing is mandatory for intra-EU B2B trade. What ViDA means for countries without a mandate yet, and how to be ready early. - E-invoicing in the Netherlands: no B2B mandate yet, Peppol widely used
The Netherlands has no domestic B2B e-invoicing mandate yet, but Peppol is widely used voluntarily — and the ViDA backstop lands 1 July 2030. What Dutch-facing suppliers should do now. - E-invoicing in Portugal: B2G structured, B2B PDF with ATCUD — for now
Portugal requires structured invoicing for B2G (CIUS-PT) while B2B still accepts PDFs carrying ATCUD. The mandate table position, the 2030 ViDA backstop, and how suppliers should prepare. - E-invoicing in Austria, Ireland, Sweden and Denmark: voluntary today, backstopped by ViDA
Four countries, one pattern: no domestic B2B issue mandate yet, Peppol in voluntary or B2G use, and the 1 July 2030 ViDA backstop behind them. The position of each country in the mandate table, and what suppliers should do. - EU e-invoicing mandates timeline: every country's date in one place
The complete timetable from this product's mandate table: Italy 2019, Belgium January 2026, Poland February–April 2026, France 2026–2027, Germany 2027–2028, Spain 2027–2028, and the ViDA backstop on 1 July 2030. - E-invoicing vs e-reporting: two different obligations that share a decade
E-invoicing governs the document between seller and buyer; e-reporting governs data sent to the tax authority. Portugal's SAF-T, Spain's VeriFactu and platform models blur the line — here is the distinction and why suppliers meet both.
Peppol
- What is Peppol? The network that delivers e-invoices between businesses
Peppol is the network and rulebook for exchanging structured invoices between businesses through certified access points. How it works, what a Peppol invoice is, and how sending works from this product. - Peppol ID explained: your business address on the Peppol network
A Peppol ID is the registered address that routes invoices to and from your business on the Peppol network, tied to your VAT or organisation number. How to get yours, and how to handle clients' IDs. - How to send a Peppol invoice free with Qvalia: the guided step-by-step
The six guided steps for sending a Peppol invoice: download the validated UBL file, create a free Qvalia account, verify your business, register your Peppol ID, upload and send, and keep the confirmation. - What is a Peppol access point? The certified carrier behind every send
A Peppol access point is a certified provider that connects your business to the Peppol network: it registers your Peppol ID, sends and receives your documents, and holds your delivery confirmations. - Peppol BIS Billing 3.0 explained: the profile your Peppol invoice must fit
Peppol BIS Billing 3.0 is the invoicing profile of the Peppol network: the EN 16931 core invoice, written in UBL 2.1, tightened with Peppol's own rules so any access point can process any invoice. - Qvalia Connect Free: how the free Peppol sending account works
Qvalia Connect Free is the access point account this product's guided Peppol flow uses: free plan, email verification, business KYC, Peppol ID registration, then upload-and-send. What to expect at each stage. - Peppol vs national platforms: network countries and portal countries compared
Belgium routes invoices through the Peppol network; Poland (KSeF), Italy (SdI) and France (PDP/PPF) route them through platforms. The two architectures, what differs for suppliers, and what stays the same.
How-to & workflow
- Convert your first invoice free: a walkthrough of the one-invoice job
The free tier converts one invoice completely: enter it, validate it against the EN 16931 rules, check acceptance for your client's country, and download UBL XML plus a Factur-X PDF. Here is the whole job, step by step. - How to issue a credit note as an e-invoice (type code 381)
A credit note is an e-invoice with type code 381, its own number and issue date, negative in effect but never in its lines. How credit notes validate, how totals work, and how they differ from corrected invoices (384). - Bulk invoice conversion: turning a whole billing run into validated e-invoices
Pro converts up to 200 invoices per job, each validated against the EN 16931 rules with per-invoice exceptions. How bulk conversion changes the workflow — and what to fix in your data before the run. - Monitored clients: tracking each client's e-invoicing mandate status as dates move
Monitored clients are Pro's tracking layer: each client's acceptance verdict is re-checked as mandate dates approach and pass, so a client who accepts PDFs today flags themselves before they start requiring structured invoices. - The acceptance checker explained: how a verdict is computed from date, country and size
The acceptance checker answers 'will my client accept this invoice?' by computing a verdict from three inputs — invoice date, buyer country, buyer size — against the mandate table for 12 countries. Inside the computation. - Will my client accept a PDF invoice? How to know before you send
Whether a PDF invoice will be accepted depends on the client's country, their size, and your invoice date. How to get a computed answer in seconds — and why 'they accepted it last year' is not evidence. - Country rule packs: the per-country layer on top of EN 16931 validation
Core EN 16931 validation proves an invoice is well-formed; country rule packs add the specific requirements of the country you are invoicing — its specification, identifiers and mandate position. How the layers fit. - Exporting converted invoices to Xero, QuickBooks and CSV
Pro's accounting exports carry a converted, validated invoice run into Xero, QuickBooks or CSV — so the structured invoice your client receives and the entry in your books are the same data, entered once. - Invoice numbers and dates on an e-invoice: the rules that keep your sequence clean
Every e-invoice needs a unique number (BT-1) and a real ISO issue date (BT-2); credit notes get their own numbers, corrections reference their originals. Numbering discipline, date discipline, and the mistakes that break both. - Invoice line items: how to write lines that validate and get approved
Lines are where invoices succeed or fail: one item per line, one VAT treatment per line, real quantities, meaningful names. The line-writing discipline behind clean validation and fast client approval. - Due dates and payment terms on an e-invoice: stating them where systems read them
A structured invoice's due date is data the client's payables system schedules by. How due dates sit with issue dates, why terms belong inside the document, and how clear terms interact with getting paid. - Archiving e-invoices: which files to keep, and why the XML is the record
In the structured era the operative record of an invoice is its structured file — the UBL XML — with the Factur-X PDF as its readable twin, plus delivery evidence where a channel provides it. How to archive so audits, queries and credits all resolve in minutes. - Switching from spreadsheet invoicing to structured e-invoices: a migration guide
Spreadsheet invoices fail structured validation in predictable places: typed totals, free-text codes, blended lines, missing identifiers. A migration path that keeps your pricing logic and replaces only the document layer.
Freelancers & business
- Freelancers invoicing EU clients: the e-invoicing playbook
For a freelancer, EU e-invoicing mandates arrive as client requirements: reverse charge discipline, identifiers at onboarding, validated conversions, Peppol when Belgium calls. A complete playbook for solo suppliers. - Team workspaces for agencies: running client e-invoicing as a shared operation
Team ($49/month) adds team workspaces for agencies and higher limits on top of Pro's bulk conversion, rule packs, monitoring and exports. How an agency organises multi-client, multi-country invoicing without it living in one person's head. - E-invoicing for small businesses: a no-drama adoption guide
Small firms do not need an e-invoicing project — they need five habits: complete client records, validated conversion, the pair sent by default, verdicts checked per client, and channels set up before deadlines. The adoption guide. - What to ask a new EU client before your first invoice: the supplier's onboarding questions
Ten minutes of questions at onboarding prevent every invoicing failure later: Peppol ID, VAT identifier, size class, channel, specification, due-date terms. The exact questions, and why each one exists. - E-invoicing and your accountant: who decides what, and what to hand over
The converter validates consistency; your accountant decides treatments. The clean division of labour — VAT categories, corrections vs credits, country specifics — and the exports that make handovers painless. - Do structured e-invoices get paid faster? The mechanisms, honestly stated
No magic — mechanisms: automatic booking removes queues, validation removes queries, delivery confirmations remove disputes, and clear lines remove approval friction. How structured invoicing shortens the path from invoice to payment. - Selling digital services to EU businesses: invoicing remote work across borders
SaaS, design, development, consulting, content — digital services sold B2B across the EU share one invoicing shape: reverse charge lines, identifiers as evidence, structured files for clients in mandate countries. The remote seller's guide. - Invoice fraud and payment safety: what structured invoicing changes — and what it doesn't
Invoice fraud thrives on unverifiable documents and changed bank details. Verified network identities, delivery confirmations and exact identifier discipline shrink the attack surface; the remaining risks still belong to your process.