What the receiving obligation since 1 Jan 2025 actually means
Unlike the staggered issuing obligation (which phases in through 2028), the receiving obligation applies without a transition period: since 1 Jan 2025, every business based in Germany must be able to accept an e-invoice from another domestic business. That affects you as a Shopify merchant the moment you purchase B2B services, from agencies, suppliers or software vendors.
Crucially, the receiving obligation does not depend on your turnover. Even small businesses under Section 19 VAT Act and companies still in the issuing transition period must be able to accept e-invoices. We cover the exact issuing timeline in our article on the e-invoice mandate and the 2025–2028 phased plan.
An e-invoice is not the same as a PDF
A legal e-invoice is a structured, machine-readable data set per the European standard EN 16931, not a scanned or emailed PDF. Two formats are common in Germany: XRechnung (pure XML) and ZUGFeRD (a PDF/A-3 with embedded XML, so both human- and machine-readable).
For receiving this means: you must be able to read, validate and archive the embedded XML in a tamper-proof way, not just the PDF view. We compare which format makes sense when in ZUGFeRD vs XRechnung.
- XRechnung: pure XML format, common in the public-sector (B2G) space.
- ZUGFeRD: PDF/A-3 with embedded XML, ideal for mixed B2B workflows.
- Standard EN 16931: shared European basis for both formats.
- Classic PDF or paper: does not meet the e-invoice definition.
How to set up receiving cleanly
Technically the entry barrier is low: for pure receiving, an email inbox to which suppliers send their e-invoices is enough to start. The real effort lies in processing: the XML must be validated, the mandatory details under Section 14 VAT Act checked, and the original archived unchanged.
This is exactly where GoBD applies: e-invoices must be stored tamper-proof, complete and traceable for the statutory period. What counts is the original XML, not the visual rendering. Simply storing a PDF in the file system is not enough for audit-proof retention.
The B2B workflow: receiving and sending in one flow
In Shopify B2B you need both directions. On the sending side you generate e-invoices for your business customers from the order data, including correct tax logic. If you sell to EU business customers with a valid VAT ID, reverse charge at 0 % applies; we show how to map that cleanly in the shop in Reverse charge for Shopify B2B sales.
With belegio, e-invoices (ZUGFeRD/XRechnung) are created automatically from every Shopify order, hosted in Frankfurt, GDPR-compliant. If you also want to pass the documents into accounting, connect Shopify directly to sevdesk or Lexware Office. For how automatic document delivery works in general, see create Shopify invoices automatically.
Mapping B2B tax logic correctly
An e-invoice is only correct if the tax details are right. In B2B there are three typical cases: domestic sales at 19 % (or 7 % reduced), intra-community B2B supply with a valid VAT ID as reverse charge at 0 %, and EU B2C distance sales above the OSS threshold of €10,000 at the local tax rate of the destination country.
This logic does not belong in a manual spreadsheet but in an automated workflow. We compare how to book orders without media breaks in automate Shopify accounting. Austrian and Swiss shops have their own thresholds too, such as the small-business limit of €55,000 gross in Austria or the VAT obligation from CHF 100,000 turnover in Switzerland.
Avoiding common pitfalls
Most mistakes happen not when sending, but when receiving and archiving. Discarding the original XML and only keeping the PDF violates GoBD. Ignoring incoming e-invoices on the grounds that "we don't issue any yet" is also risky; the receiving obligation is independent of that.
- Archiving only the PDF instead of the original XML: a GoBD breach.
- Ignoring the receiving obligation because no issuing obligation applies yet.
- Not verifying the VAT ID for EU B2B: reverse charge becomes contestable.
- Not validating mandatory details under Section 14 VAT Act before booking.
