Free tier

← All guides · Country mandates

E-invoicing vs e-reporting: two different obligations that share a decade

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

E-invoicing is about the invoice itself: a structured document (EN 16931) that the buyer's system can book. E-reporting is about the tax authority: transaction data reported to the state, as in Portugal's SAF-T accounting files or the verification layer in Spain's 'VeriFactu / EN 16931' channel. Platform mandates (KSeF, SdI) fuse the two — the state sees the invoice as it travels. Your duty as supplier starts with the invoice; reporting rides on data quality.

What is the difference?

E-invoicing defines the document exchanged between trading parties — here, the EN 16931 structured invoice this product builds and validates. E-reporting defines data flows to the tax administration about transactions. This product's mandate table contains both species: channels that are document networks (Peppol), platforms where the state is in the path (SdI, KSeF), and pairings like Portugal's 'CIUS-PT / SAF-T' and Spain's 'VeriFactu / EN 16931', where the invoice standard and the reporting/verification system are named together.

Two audiences for the same transaction

An invoice has always had two readers: the buyer, who must book and pay it, and the state, which taxes the activity it records. Paper and PDF served the first reader directly and the second only on demand — audits, returns, spot checks. The digital decade serves both by design: the structured invoice satisfies the buyer mechanically, and the same data, reported or platform-mediated, satisfies the state continuously rather than retrospectively.

Keeping the audiences distinct clarifies your obligations. As a supplier you issue invoices; reporting duties typically attach through your own accounting (your returns, your SAF-T-style files where your jurisdiction requires them) and through the platforms your transactions pass. Confusing the two produces the classic error of believing a platform submission was 'just reporting' — in SdI and KSeF countries the platform step is the invoicing itself, with the state's visibility built in.

Where the models fuse: platforms

Italy's SdI is the fusion archetype: the invoice is issued into the state-run exchange, validated there, and delivered to the buyer from there — invoicing and reporting are one act, which is how Italy's mandate (since 2019) produced its celebrated visibility over VAT. Poland's KSeF follows the platform pattern in its 2026 phases. In such countries there is no private moment where an invoice exists between seller and buyer alone; the document is born reported.

France's PDP/PPF design sits between: approved private platforms and the public platform carry the invoices, with the administration's data flowing from that layer. Belgium's Peppol model is the contrasting pole: a private network carries the document, and the state's interest is served by the parties' reporting rather than by sitting in the invoice's path. Same decade, same destination — continuous visibility — different plumbing philosophies.

Where they stay separate: SAF-T and VeriFactu

Portugal pairs its invoice specification (CIUS-PT) with SAF-T — the standard audit file format in which accounting data is reported or produced for the tax authority. The invoice can be a B2B PDF with ATCUD today, while the reporting layer already digitises the ledger behind it: e-reporting advancing on a separate track from e-invoicing, in the same country, at the same time. Spain's channel pairing tells a similar story: VeriFactu (the invoicing-systems verification regime) named alongside EN 16931 — the integrity of the records, reported and verifiable, next to the document standard.

For suppliers the practical lesson is that 'the mandate' in any country may be a bundle: document duties, reporting duties, and system-integrity duties arriving on related but distinct timetables. The mandate table here tracks the invoicing side — channels, phases, verdicts — which is the side that decides your documents. Your accountant tracks the reporting side for your own establishment. Knowing the bundle exists prevents the surprise of satisfying one layer and meeting another.

Why the distinction protects you

Suppliers who grasp the distinction make cleaner decisions. They do not expect a Peppol send to discharge a domestic reporting duty in their home country (different audience). They do not dismiss a platform country's process as 'just their reporting' (it is the invoice's legal path). And they keep their own house aligned: the same validated, reconciled invoice data feeds their books, their exports and their filings — so the story told to the buyer and the story told to the state are one story, derivable from one dataset.

That unity is, ultimately, what both obligations are converging on: a world where the invoice, the ledger and the report are views of a single structured truth. Every habit in these guides — derived totals, exact identifiers, complete archiving — serves that convergence. Build the truth once, in the invoice, and both audiences read it without translation.

Your action list, by audience

For the buyer audience: convert and validate every invoice; send it by the client's channel; keep the readable twin for their humans. For the state audience — yours, in your jurisdiction: keep the complete structured archive, export the period's population to your accounting faithfully (credits and corrections included), reconcile the numbering sequence, and let your accountant map the population onto whatever reporting your establishment owes. For platform-country clients: follow their specified route exactly, because there the two audiences share a doorway.

None of this requires the supplier to become a reporting specialist. It requires the supplier to stop maintaining two versions of the truth — the invoice version and the books version — which was the paper era's quiet corruption. Structured invoicing's deepest reform is not the XML; it is that the document, the ledger and the report finally agree, because they are finally the same data.

Handling both obligations in 5 steps

  1. Name the audience for each duty you meet: buyer-facing (the invoice) versus authority-facing (reporting) — never assume one discharges the other.
  2. For platform-country clients (SdI, KSeF), treat the platform step as the invoicing itself and follow the client's route exactly.
  3. Keep one dataset: the validated conversions feed your books and exports, so buyer story and state story cannot diverge.
  4. Archive the complete structured set and reconcile numbering monthly — reporting quality is archive quality.
  5. Give your accountant the reporting map for your own establishment; keep your own focus on document excellence.

Worked example: one transaction, two audiences, one dataset

A Portuguese supplier issues a EUR 4,600.00 invoice to a domestic business client. Buyer audience: the invoice as the client requires it today — per the table, B2B PDF with ATCUD accepted, with the supplier sending the validated structured pair anyway. State audience: the transaction enters the supplier's accounting population, exported completely at period-end, available to the SAF-T-style reporting their accountant prepares — the same figures, from the same conversion, with the same totals.

No second version of the invoice exists anywhere: not a 'client copy' with one total and a 'books copy' with another. When either audience asks a question, the answer is the same EUR 4,600.00 document with the same breakdown. That singleness — not any single mandate — is the destination both e-invoicing and e-reporting are travelling toward, and this supplier has already arrived.

Frequently asked questions

If I send via Peppol, have I reported to the tax authority?

No — Peppol is a document network between businesses. Your reporting duties in your own jurisdiction are separate and remain yours (via your accounting and accountant). Do not let one audience's satisfaction masquerade as the other's.

Is KSeF invoicing or reporting?

Both fused: Poland's platform is the channel through which structured invoices are issued — the state is in the invoice's path, which is the platform model's defining trait.

What is SAF-T?

A standard audit-file format for accounting data, named in Portugal's channel ('CIUS-PT / SAF-T'): the reporting layer that digitises the ledger behind the invoices. Your accountant owns its production for your establishment.

What is VeriFactu's relation to e-invoicing?

Spain's channel is listed as 'VeriFactu / EN 16931' — the verification regime for invoicing records named alongside the document standard: integrity/reporting and invoicing advancing as a pair.

Why does the distinction matter to a small supplier?

Because duties arrive bundled and are easy to half-satisfy: a platform route mistaken for mere reporting, or a network send mistaken for a filing. Knowing the two audiences keeps both satisfied deliberately.

Keep going

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

Related guides

← Back