German §14 UStG e-invoicing in NetSuite: what changes and how to prepare

Germany's move to mandatory business-to-business e-invoicing is one of the larger compliance shifts NetSuite users with a German entity will face this decade. The headline date has passed — from 1 January 2025 every German business must be able to receive a structured electronic invoice — but the phased issuing obligations are still rolling in. If you run a German subsidiary on NetSuite, here's what actually matters.

What is changing, and when

Under the reform of §14 UStG, a compliant e-invoice in Germany is a structured electronic format, not a PDF. The receive capability became mandatory for all domestic B2B from 1 January 2025. Issuing obligations phase in afterwards by company size and turnover over the following years, so the practical priority for most groups right now is being able to receive and process structured invoices correctly.

The formats: XRechnung and ZUGFeRD

Two formats dominate. XRechnung is a pure-XML structured invoice (the standard for public-sector B2G). ZUGFeRD 2.x is a hybrid — a human-readable PDF/A with the structured XML embedded inside it. Both conform to the European semantic standard EN 16931, which is the thing your validation should actually check against.

What it means for NetSuite

NetSuite doesn't do all of this out of the box for Germany, so the work is in configuration and a structured-data pipeline:

• Receiving. Extract the XML from inbound XRechnung and ZUGFeRD 2.x invoices, validate against EN 16931, and map cleanly onto NetSuite vendor bills — rejecting non-conformant documents loudly rather than silently.
• Issuing. Generate structured output for the formats your counterparties require, with gapless invoice numbering as required under §14 UStG and §146 AO.
• Tax. SuiteTax codes covering 19% / 7%, EU intra-community supplies and §13b reverse charge, posting to the correct control accounts.
• Hand-off and archive. DATEV-format export for the external Steuerberater, and GoBD-conformant archiving of every issued and received e-invoice for the full ten-year retention period.

A practical preparation checklist

Confirm your German entity can receive and parse XRechnung and ZUGFeRD 2.x today. Check your chart of accounts (SKR03 or SKR04) and SuiteTax mapping are clean. Make sure invoice numbering is gapless. Agree the DATEV export format with your Steuerberater. And confirm archiving meets GoBD before, not after, an audit asks.

The bottom line

German e-invoicing is a data-quality and configuration exercise as much as a compliance one. Get the receive pipeline, tax mapping and archiving right, and the issuing obligations become a straightforward extension rather than a scramble.

Working on something similar? Book a free call and we'll talk it through — no obligation.