E-invoicing
E-invoicing is the issuing, sending and receiving of an invoice in a structured data format that software can read and process automatically, rather than as a PDF or paper document that a person has to open and key in by hand; many markets now require it for some or all business transactions.
Submit a project Find your market's e-invoicing ruleReviewed by Huy Nguyen (David), CEO · Updated 18 Oct 2026 · 3 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while building software for a regulated market.
Why does e-invoicing matter?
A PDF emailed as an invoice looks electronic but is not a structured invoice: a person still has to read it and type the figures into another system, which is exactly the manual step e-invoicing removes. OutsourcingVN is operated by Netbase JSC, and for a product selling into a market with an e-invoicing mandate, the requirement usually reaches into the data model itself, not just the checkout screen, because the invoice has to carry specific fields in a specific machine-readable format before it can be issued at all.
What is an example of e-invoicing in practice?
A business selling to public-sector buyers in the European Union issues an invoice as a structured electronic document built to the European standard EN 16931, rather than as a PDF attachment. The buyer's own system reads the file directly, matches it automatically against the purchase order, and posts it without anyone retyping a line item. The European Commission's own description of the underlying directive states plainly that an electronic invoice is one "issued, transmitted and received in a structured data format which allows for its automatic and electronic processing" — a PDF, however neatly formatted, does not meet that description.
What are the common misreadings of e-invoicing?
E-invoicing is not the same as simply emailing an invoice instead of posting it; the format, not the delivery channel, is what makes an invoice an e-invoice, and a PDF sent by email is not a structured invoice under any mandate that requires one. It is also not one single global standard: formats, fields and reporting routes differ by country and sometimes by transaction type, so a product built for one market's mandate cannot be assumed to satisfy another's without checking. And e-invoicing is not only a public-sector concern; a growing number of markets extend a structured-invoice requirement to business-to-business transactions as well as to government buyers.
Plan the next step for your project
Common questions
Not necessarily. Many e-invoicing formats can still be rendered as a readable document; what matters for the mandate is the structured data underneath, not the visual layout.
No. A buyer scoping a product for more than one market needs to check each market's own format and reporting route rather than assuming one implementation covers all of them.
Which decisions does e-invoicing affect?
Finding which countries require e-invoicing, and what each one's format and reporting route looks like, is the subject of the software delivery by market guide, which indexes the country guides that cover a specific mandate in detail. When you know which markets your buyers are in, describe them and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.