Receiving e-invoices: a practical readiness check for small businesses

For German domestic B2B transactions, businesses have had to be able to receive e-invoices since 1 January 2025. An email inbox can be enough as the receipt channel. Operationally, though, an inbox is only the start: the original file needs to be found, read, checked and retained without alteration.

This is a practical guide to the German VAT context, not tax or legal advice.

What is arriving in your inbox?

An e-invoice is structured data that can be processed electronically; it is not simply an attractive PDF. Under the German definition in force since 2025, a plain PDF is a “different invoice,” not an e-invoice. See the German Ministry of Finance (BMF) FAQ and section 14 of the German VAT Act.

EN 16931 defines the common European invoice data model. KoSIT explains XRechnung as the German implementation used for public contracting authorities. FeRD explains ZUGFeRD’s hybrid PDF/A-3 and XML approach. Where a ZUGFeRD PDF and XML disagree, the BMF says the structured data are authoritative.

Check an incoming e-invoice directly

Unsure whether an XML or PDF file really contains structured invoice data? The quick check below recognizes XRechnung, UBL, CII and embedded ZUGFeRD/Factur-X data. It extracts key details without uploading the file.

A 10-minute intake self-check

This is not validation, certification or a legal assessment. It simply exposes process gaps:

Has a B2B e-invoice arrived?
│
├─ No / unsure → Define a shared invoice address and tell suppliers.
│
└─ Yes
   ├─ Is the original XML or hybrid file retained?
   │  ├─ No → Define the storage location and owner.
   │  └─ Yes
   │     ├─ Can someone read and review the data?
   │     │  ├─ No → Test a viewer or accounting import.
   │     │  └─ Yes
   │     │  ├─ Can it be matched to an order, job or goods receipt?
   │     │  │  ├─ No → Add a reference number to purchasing.
   │     │  │  └─ Yes → Define how exceptions are handled.

A file sitting in an individual mailbox does not pass the practical test. Assign an owner for new invoices, a home for originals, a matching reference and an escalation route for errors.

A lean workflow for field service and retail

1. Name one intake channel. A shared mailbox or controlled document intake reduces missed supplier invoices.
2. Keep the original first. Save XML, hybrid files and relevant attachments in the intended archive. A printout, screenshot or extracted PDF is not a replacement for the structured original.
3. Make it readable, then compare it. Use a viewer or import test. Compare supplier, invoice number, service period, amounts, tax and payment details against the purchase order, work order or goods receipt.
4. Record the link. An order, job or cost-centre reference gives the team a repeatable matching step.
5. Make exceptions visible. Duplicate invoices, changed bank details, implausible tax or a missing order should enter a clear clarification path before payment.

Worked example: A repair shop orders a part for job 4582. A ZUGFeRD hybrid file arrives. The office retains that original with the job, reads the structured data through its normal tool and compares item, quantity and amount with the order and delivery. A quantity mismatch goes to clarification before approval. Nobody has to retype values from a PDF.

Receiving is not the same as issuing

Do not merge the two timelines. There are transitional rules for issuing German domestic B2B invoices: issuers can generally still use other invoices through the end of 2026; where the prior-year turnover is up to €800,000, the relevant transition can extend through the end of 2027. Scope exceptions also exist. The BMF FAQ gives the current conditions, including the position for small businesses.

Set up receipt now even if your outgoing invoices are still in a transition period. Public customers can additionally require XRechnung and a specified delivery channel.

Retention: finish the process, not just the download

At least the structured component of an e-invoice must be retained in its original, unaltered form. The VAT retention period is eight years; see section 14b UStG and the BMF FAQ.

Run one controlled test this week: send a safe test file to the intake, store the original, open it, match it to a job and simulate an error. Five clear owners are more valuable than a vague promise of compliance.