Finance Index
What is e-invoicing, and why is a PDF emailed to AP technically not an e-invoice?
Reference guide to e invoicing fundamentals, including invoice workflow, coding, approvals, ERP impact, and AP controls.
E-invoicing means exchanging invoices as structured, machine-readable data - not a document a human or OCR has to interpret. A PDF emailed to AP is a digital picture of an invoice; an e-invoice is the invoice as data (XML and similar formats) that systems exchange and validate directly. The distinction matters because true e-invoicing removes the extraction step entirely, and because a growing number of countries now mandate the structured form for tax compliance.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| E-invoicing | E-invoicing means exchanging invoices as structured, machine-readable data - not a document a human or OCR has to interpret. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Related terms | All three move an invoice from supplier to buyer; they differ in structure and reach. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| ERP alignment | They're agreed data schemas for invoices: UBL and PEPPOL BIS are widely used XML standards; Factur-X is a hybrid that embeds structured XML inside a human-readable PDF. | Keeps accounting records aligned with the ERP. |
| What is the peppol network | PEPPOL is an international framework for exchanging structured business documents, widely used in Europe and beyond. | Helps finance decide what to do next. |
| E-invoicing mandatory in the united | There is no broad US B2B e-invoicing mandate today, and the US has historically favored voluntary, market-driven adoption over clearance-model mandates. | Helps finance decide what to do next. |
E-invoicing vs EDI vs PDF capture - what's the difference and where is the world heading?
All three move an invoice from supplier to buyer; they differ in structure and reach. EDI is established point-to-point structured exchange between trading partners, common for high-volume relationships. E-invoicing is standardized structured invoicing, increasingly routed over networks or government platforms and increasingly mandated. PDF-over-email is unstructured but universal, which is why AI capture exists - to get structured data out of the channel most vendors actually use. The trajectory is more structured exchange where it's mandated or networked, with AI capture covering the long tail that will never standardize.
What are structured e-invoice formats like xml, ubl, factur-x, and peppol bis in plain English?
They're agreed data schemas for invoices: UBL and PEPPOL BIS are widely used XML standards; Factur-X is a hybrid that embeds structured XML inside a human-readable PDF. The point of each is that two different systems read the same fields the same way, with no interpretation.
What is the peppol network, and does a US company need to care?
PEPPOL is an international framework for exchanging structured business documents, widely used in Europe and beyond. A purely domestic US company can largely ignore it today; a US company with European or Asia-Pacific entities or trading partners may need to receive PEPPOL e-invoices where local rules require it.
Is e-invoicing mandatory in the united states, and is a US mandate coming?
There is no broad US B2B e-invoicing mandate today, and the US has historically favored voluntary, market-driven adoption over clearance-model mandates. Pilot exchange frameworks exist, but US companies should track developments rather than assume an imminent requirement.
What is the dbnalliance and the US e-invoicing exchange framework?
The Digital Business Networks Alliance (DBNAlliance) is an industry body that established a US exchange framework for interoperable e-invoicing - a voluntary network-of-networks approach rather than a government mandate. It signals where US e-invoicing may head, without (as of now) requiring participation.
Should our AP automation roadmap include structured e-invoice receiving even before any US mandate?
If you have entities or major suppliers in mandate countries, yes - build the capability where it's already required. For a domestic-only US operation, prioritize AI capture for today's channels and treat structured e-invoice receiving as a watch item, not an urgent build.
Stampli perspective
Stampli's intake is channel-agnostic by design - the goal is one consistent, ERP-aligned invoice record regardless of how the invoice arrives, with the same coding, matching, approval, and validation downstream. AI extraction turns unstructured channels (emailed PDFs, scans, uploads) into structured records, while high-volume structured feeds can enter through supported system paths.