E-Commerce Nov 19, 2026

B2B E-Invoicing Mandates: Is Your Webshop's Invoice Flow Ready?

B2B E-Invoicing Mandates: Is Your Webshop's Invoice Flow Ready?

Time to read: 11 minutes

Content

  1. What changed: Germany's B2B e-invoicing timeline
  2. Who issues the invoice for a webshop order today?
  3. Trace one order: the EN 16931 data an invoice needs
  4. Shop extension, ERP or e-invoicing service: choose one issuing owner
  5. Partial deliveries, returns and credit notes: the cases that break numbering and totals
  6. Selling into other EU countries: national mandates and ViDA
  7. Acceptance tests before you switch on structured invoices
  8. What Dinarys case pages show, and what they don't
  9. Your next step
  10. FAQ
Bookmark

A structured e-invoice for a webshop order should come from one system, and that system can only be as complete as the order data the shop hands it.

In Germany, every business established in the country has had to be able to receive e-invoices since 1 January 2025. From 1 January 2027, domestic B2B invoices must be structured e-invoices. Two exceptions remain until the end of 2027, for supplies made in 2027: paper or PDF for sellers whose total turnover in the previous calendar year was no more than EUR 800,000, and EDI in another agreed format. A plain PDF is not an e-invoice; XRechnung and ZUGFeRD from version 2.0.1 qualify, except the ZUGFeRD profiles MINIMUM and BASIC-WL.

So which system should issue it? For most B2B webshops, not the shop. Choose one issuing owner: usually the ERP that books the invoice, its e-invoicing module, or an e-invoicing service fed by the ERP. The shop's job is to capture the data the invoice needs (purchase-order reference, buyer reference, buyer VAT ID where required, VAT category per line, payment terms), pass it on without loss, and stop sending any document that competes with the real invoice.

This guide gives heads of ecommerce and ERP owners a data trace, an issuing-owner decision and acceptance tests. It is not tax advice: dates and scope come from the German VAT Act (UStG) and the Federal Ministry of Finance (BMF) FAQ as checked on 19 November 2026, and your tax adviser decides how they apply to you.

What changed: Germany's B2B e-invoicing timeline

Under § 14 UStG, an electronic invoice is issued, transmitted and received in a structured electronic format that enables electronic processing. The format must follow the European standard EN 16931, or be agreed between the parties if the required data can be extracted correctly and completely into a format that complies or is interoperable with it. Paper and PDF are "other invoices" (sonstige Rechnung).

Supplies madeWhat the seller may sendSource
1 Jan 2025 to 31 Dec 2026E-invoice; paper, or another electronic format such as PDF if the buyer agrees, only if sent by 31 Dec 2026§ 27(38) no. 1 UStG
1 Jan 2027 to 31 Dec 2027E-invoice. Paper, or PDF if the buyer agrees, only if sent by 31 Dec 2027 and the seller's prior-year total turnover was no more than EUR 800,000; EDI in another agreed format if issued by 31 Dec 2027§ 27(38) no. 2 and 3 UStG
From 1 Jan 2028E-invoice for every domestic B2B supply in scopeBMF FAQ, question 11

Four details matter for a webshop:

Public-sector buyers follow their own e-invoicing rules, and an invoice to an authority needs its Leitweg-ID. In B2B, the BMF says a placeholder such as "-" in the buyer reference field (BT-10) is enough for VAT purposes.

Who issues the invoice for a webshop order today?

Count the documents first: for one recent B2B order, list what the buyer received, which system produced each document and which assigned the invoice number. § 14(4) UStG requires a sequential number that the issuer assigns once. Two systems numbering invoices for the same order is the first defect to remove.

Commerce platforms have their own invoice object. Adobe Commerce's documentation describes its invoice as a record of payment for an order, notes that "Multiple invoices can be created for a single order", and says that with a purchase-order payment method or an Authorize and Capture payment action, "the order is invoiced and payment is captured during checkout." That is not necessarily the VAT invoice your ERP books on shipment, and if both reach the buyer, they hold two documents with two numbers.

Order-to-invoice flow with one issuing point Five steps from top to bottom: 1 the buyer orders with a PO number; 2 the webshop captures PO and VAT ID; 3 the ERP records order, delivery and invoice number; 4 an e-invoicing service or Peppol access point sends the file; 5 the buyer's accounts payable receives and books it. Red markers show that today the webshop sends PDF invoice number 1 and the ERP issues invoice number 2. A green marker beside the ERP shows the target: one issuing point. 1 Buyer Orders with PO no. 2 Webshop Captures PO, VAT ID 3 ERP Order, delivery, invoice number 4 E-invoicing service or Peppol access point 5 Accounts payable Buyer receives, books Today: PDF invoice no. 1 Today: ERP invoice no. 2 Target: one issuing point
Illustrative flow for one B2B order. Today the shop and the ERP each create an invoice (red). The target is one issuing point in the ERP (green), fed by the data the shop captures and sent on by an e-invoicing service or Peppol access point where buyers need one.

If orders already fail before they reach the ERP, start with why orders fail between the store and the ERP.

Trace one order: the EN 16931 data an invoice needs

Take one real order, ideally with a partial delivery, and fill this trace with each system's owner, writing "unknown" rather than leaving a cell blank. The rows are EN 16931 business terms (BT) most webshop orders touch; the KoSIT and FeRD mapping table of mandatory UStG items gives the full list.

Fictional, illustrative example. A Hamburg fasteners distributor with about EUR 30 million turnover sells through Adobe Commerce B2B, mostly in Germany and partly to other EU countries. A PDF extension emails an invoice when the order is placed; the ERP books the invoice when the goods ship. Its trace:

Business termCaptured atStored inReaches the issuing system?Gap and owner
Seller VAT ID (BT-31)ERP company masterERPYesNone
Buyer VAT ID (BT-48)Company account formShop onlyNoRequired on its intra-EU supply invoices (§ 14a(3) UStG); map to the ERP customer. Ecommerce lead
Purchase-order reference (BT-13)Optional checkout fieldShop order commentNo, lost as free textMake it required for company accounts; map to the ERP order. Ecommerce lead, ERP owner
Buyer reference (BT-10)Not capturedNoneNoCapture where a buyer asks; otherwise "-". ERP owner
Invoice number and date (BT-1, BT-2)Shop PDF and ERPBothTwo numbersERP only. Finance
Actual delivery date (BT-72)ERP shipmentERPYesNone
Line net amount, VAT category and rate (BT-131, BT-151, BT-152)Shop price, ERP tax codeERPYes, but shop and ERP round differentlyCalculate in the ERP only. ERP owner
Allowances and charges (BG-20, BG-21)Shipping fee, account discountShop orderDiscount only as a reduced priceAgree how each is shown. Finance
Payment terms, IBAN (BT-20, BT-84)ERP customer and bank masterERPYesNone
Document questionTodayTarget
Which system creates the invoice?Shop (PDF at order) and ERP (on shipment)ERP only
Format and channelPlain PDF by emailXRechnung or a qualifying ZUGFeRD profile; email, or Peppol where a buyer requires it
What the shop sends"Invoice" PDFOrder confirmation, clearly not an invoice
Credit notesManual PDF from financeERP correction referencing the original invoice

The trace showed that the PO number typed at checkout never reached the ERP, and buyer VAT IDs existed only in shop accounts. Decision: the shop sends an order confirmation, not an invoice; PO reference and VAT ID become required for company accounts and are mapped to the ERP; the ERP's e-invoicing module issues the e-invoice. Where buyers order from their own procurement system, the PO arrives from there instead; PunchOut or a B2B portal covers that flow.

The trace decisionIllustrative decision for the fictional distributor: the shop sends an order confirmation, the PO reference becomes required, the buyer VAT ID is mapped to the ERP, and the ERP's e-invoicing module issues the e-invoice.The trace decisionFictional distributor, illustrativeShop sends an orderconfirmationClearly not an invoice, so nothingcompetes with the real onePO reference becomesrequiredFor company accounts, mapped to theERP orderBuyer VAT ID reaches theERPCaptured in the company accountform, mapped to the ERP customerThe ERP's e-invoicingmodule issuesOne issuing point: invoice numberand date from the ERP only

Shop extension, ERP or e-invoicing service: choose one issuing owner

The issuing owner numbers invoices and credit notes, produces the structured file, sends it and keeps it. Under § 14b(1) UStG a copy of every invoice is kept for eight years, and the BMF says an e-invoice's structured part must be kept unaltered in its original form.

OptionFits whenWatch forRules it out
Shop extensionThe shop is the system of record for orders, invoices and refundsNumbering, credit notes and archive all live in the shopAn ERP already books invoices, or partial deliveries are invoiced outside the shop
ERP e-invoicing moduleThe ERP books invoices and credit notes on shipmentThe ERP needs the shop's PO reference, buyer reference and VAT IDYour ERP version lacks the formats your buyers need
E-invoicing service or Peppol access point fed by the ERPSeveral countries, formats or channelsIt converts and transmits but cannot add data the ERP never had; agree who fixes rejectionsOne country, low volume, email delivery the ERP already covers

For most webshops connected to an ERP, the second or third row is the realistic answer. If a marketplace or service issues invoices in your name, which § 14(2) UStG allows a third party to do, it is the issuing owner for those orders and the shop sends nothing that competes.

Partial deliveries, returns and credit notes: the cases that break numbering and totals

Selling into other EU countries: national mandates and ViDA

The German duty covers domestic supplies only; other countries run their own mandates. The European Commission's country factsheets, last updated 19 October 2026, state:

The VAT in the Digital Age (ViDA) package, including Directive (EU) 2025/516, was adopted on 11 March 2025. According to the Commission, member states may introduce mandatory e-invoicing under specific conditions since 14 April 2025, and digital reporting requirements for cross-border B2B transactions apply from 1 July 2030. Pick an issuing owner that can add a format, channel or country without changes to the shop.

Acceptance tests before you switch on structured invoices

Validate every generated file: the BMF recommends validation at creation and dispatch, though it is not a condition for tax recognition. Validate against the rules of the format you issue: for XRechnung, KoSIT's open-source validator with its XRechnung configuration, which checks against EN 16931 and the XRechnung rules; for ZUGFeRD, the EN 16931 rules of the profile you use.

CaseExpected resultEvidence
Complete order, all lines shippedOne e-invoice from the issuing owner, none from the shop; no validator errorsValidator report, ERP invoice list
Two of three lines shippedInvoice covers shipped lines with their delivery date; totals of both invoices equal the orderBoth invoices against the order
One line returnedCorrection references the original invoice (BT-25); VAT per rate matchesCorrection file, validator report
Company buyer leaves PO emptyCheckout requires it, or the order is flagged before invoicingCheckout rule or exception log
ZUGFeRD invoice generatedXML and PDF show the same totalsSide-by-side check
Last month's invoice retrievedStructured file unchanged, found by invoice numberArchive search

How to check your result: fill the trace for one real order with a partial delivery and one credit note, name a single issuing system and every missing field with its owner, and run one generated sample through a validator without errors. If any of the three fails, the trace is your gap list.

Check your resultThree checks before switching on structured invoices: fill the trace for one real order with a partial delivery and a credit note, name one issuing system and every missing field's owner, and validate one sample without errors.Check your resultBefore you switch on structured invoicesFill the trace for one realorderWith a partial delivery and onecredit noteName a single issuingsystemAnd every missing field with itsownerValidate one generatedsampleNo errors; for XRechnung, KoSIT'svalidator with its XRechnungconfigurationIf any of the three failsThe trace is your gap list

What Dinarys case pages show, and what they don't

CaseWhat the public page statesLimit
Flash Style: automated invoices and tax documents on a Magento platformAutomated final and advance invoices, tax documents, cash-register receipts and VAT documents; document generation verified each sprintCzech market; no mention of EN 16931, XRechnung, ZUGFeRD or Peppol
Mon Tresor Bebe: wholesale site on Magento 2Invoice editing with totals recalculation, shipment creation from an invoice, QuickBooks synchronizationInvoice handling in Magento, not structured e-invoicing
SanMar: ERP integrationReal-time exchange of catalog, order fulfillment and availability data between the B2B and B2C websites and the client's ERPNo invoicing scope stated

None of these pages describes an XRechnung, ZUGFeRD or Peppol integration.

Your next step

Fill the trace for one order with your ERP owner and finance lead, and decide which system issues the invoice. If you offer pay by invoice among your B2B payment methods, include payment terms and IBAN. If the gaps sit between shop and ERP, Dinarys can review the trace with you as part of ecommerce and ERP integration: which fields need mapping, which document the shop should stop sending and which acceptance cases to run before your switch date.

FAQ

Is a PDF invoice still allowed for German B2B orders?

For supplies made and invoiced by 31 December 2026, yes, if the buyer agrees. For supplies made and invoiced in 2027, only if your 2026 total turnover was no more than EUR 800,000, again with the buyer's agreement. From 1 January 2028, domestic B2B invoices in scope must be e-invoices.

Is ZUGFeRD enough, or do we need XRechnung?

For B2B, the BMF names both XRechnung and ZUGFeRD from version 2.0.1 as meeting the requirements, except the ZUGFeRD profiles MINIMUM and BASIC-WL.

Do we need Peppol in Germany?

No channel is prescribed for B2B. The BMF lists email, an electronic interface and portal download among the options, agreed between the parties. Peppol matters where a buyer requires it or another country's mandate uses it.

Can the webshop issue the e-invoice itself?

Yes, if the shop books, numbers, corrects and archives invoices. If an ERP books them on shipment, let the ERP or a service it feeds issue them.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon