Countries · Germany

Put structured invoices into controlled finance workflows

Your Peppol access point transmits; InvoiceDX does not. A received XRechnung or ZUGFeRD file still needs checks, approval and posting; InvoiceDX gives each exception an owner and an ERP outcome.

Demo / test-readyThis badge shows e-invoicing exchange readiness; reporting and return support have their own status below.
  • SAP, Tally and ERPNext connectors, plus client-specific connectors
  • Any GSP or ASP you run
  • TaxGenie, a GSTN-empanelled GSP — GST compliance since 2017
  • ISO/IEC 27001 certified

Legal mandate

E-Rechnung (XRechnung / ZUGFeRD)

Dated sources and legal status are shown per obligation block below. Mandate status is the authority's; readiness is ours.

E-invoicing mandates, dated and sourced →

Authorised-provider role

Your Peppol access point or e-invoice provider — or one we recommend — transmits. Germany has no clearance platform: you must receive EN 16931 invoices since 2025 and issue them from 2027. A received XRechnung or ZUGFeRD file still needs supplier checks, PO variance, approval and posting. InvoiceDX gives each exception an owner, a rule and an ERP outcome — in a test environment today.

Does not transmit: InvoiceDX does not generate outbound XRechnung or ZUGFeRD invoices and does not transmit to any authority.

Who uses the Germany workflow

Each role sees the same exception, its owner and its evidence — never a direct line to a tax authority.

CFO and shared services

Exception visibility across entities without replacing the financial system.

CFO and finance leadership →

AP manager

Field mismatches, PO/GRN discrepancies and posting failures routed to accountable owners.

AP exception management →

Tax and VAT

Source documents, corrections and VAT treatment preserved for the UStVA review.

VAT reconciliation workpapers →

ERP systems integrators

Format parsing, accounting interfaces and controlled posting tested per connector; InvoiceDX never owns the ERP project.

ERP systems integrators →

Three obligations, three statuses

E-invoicing exchange, transaction reporting and periodic return support

Each block shows the law on the left and InvoiceDX's readiness on the right. A country's legal mandate never establishes InvoiceDX's availability.

Obligation timeline for one month: invoice, exchange, reporting and return. Your authorised provider owns exchange and reporting on the regulated channel; InvoiceDX matches, resolves exceptions, approves, acts in the ERP and verifies with evidence retained; your filer reconciles and files the return.START OF MONTHRETURN WINDOWInvoiceissued or receivedExchangevalidated · transmittedReportingto the authorityReturnreconciled · filedexchange obligationreporting obligationreturn obligationYour providerGSP / ASP / access pointExchange and reporting on the regulated channelInvoiceDXControl · Command CentreMatch · exception → owner → rule → approval → ERP action → verified · evidence keptYour filertax team / adviserReconciles and files the returntax-ready datahanded overGeneric month; the dated milestones for this country are in the mandate table below.
One month of obligations and who holds each stretch. InvoiceDX hands tax-ready data to your filer; it never files or pays.
E-invoicing exchange / clearance

XRechnung / ZUGFeRD reception and issuance

In law

Under §27(38) UStG, businesses must be able to receive e-invoices for domestic B2B supplies since 1 January 2025. From 1 January 2027, issuers with prior-year turnover above €800,000 must issue domestic B2B e-invoices; EDI formats are tolerated until 31 December 2027. From 1 January 2028 the issuing obligation applies to all domestic B2B issuers. Accepted formats include XRechnung and ZUGFeRD (Factur-X) profiles conforming to EN 16931.

Instrument: §27(38) UStG · Source

Checked 2026-10-20Next review 2027-01-15Reviewer: local tax practitioner (review in progress)
Where InvoiceDX standsDemo / test-ready

Inbound reception and validation of XRechnung and ZUGFeRD (Factur-X) invoices into controlled ERP workflows; outbound generation stays with your e-invoice provider or ERP.

  • Outbound XRechnung and ZUGFeRD generation stays with your e-invoice provider or ERP.
  • Format profiles are supported as each is tested; the tested profiles are listed in the Conformance centre.
  • EDI tolerance to 31 December 2027 is the law's provision for your existing EDI flows; InvoiceDX handles the structured invoices you receive.
Transaction reporting

Transaction reporting

In law

No domestic transaction-reporting obligation is in force today; EU ViDA cross-border digital reporting applies from 1 July 2030 (Directive (EU) 2025/516).

Instrument: Directive (EU) 2025/516 (ViDA) · Source

Checked 2026-10-20Next review 2027-01-15Reviewer: local tax practitioner (review in progress)
Where InvoiceDX standsConcept

Not applicable today: Germany has no domestic transaction-reporting obligation in force.

  • Cross-border digital reporting under ViDA applies from 1 July 2030; InvoiceDX support for it is stated as a concept until then.
Periodic return support

Umsatzsteuer-Voranmeldung and annual return

In law

The Umsatzsteuer-Voranmeldung (advance VAT return) is filed monthly or quarterly and the annual VAT return yearly under §18 UStG; both remain separate obligations from e-invoice reception and issuance.

Instrument: §18 UStG · Source

Checked 2026-10-20Next review 2027-01-15Reviewer: local tax practitioner (review in progress)
Where InvoiceDX standsDemo / test-ready

Review workpapers and reconciliation evidence between received invoices, the ledger and the return; filing stays with your return tool or tax adviser.

  • Your return tool or tax adviser files the advance VAT return (UStVA) and the annual return from the workpapers InvoiceDX prepares.

Demonstrable workflow

Illustrative workflow — not a connected live transaction. Sample company names only.

  1. 1

    Sample Werke GmbH receives an XRechnung through its provider; InvoiceDX validates the structure

  2. 2

    A PO price variance is found; InvoiceDX raises an exception with the variance value

  3. 3

    Delegation of authority routes the exception to the accountable buyer

  4. 4

    The approved post or hold instruction goes to the ERP through the supported connector

  5. 5

    The ERP response is read back and the evidence is retained for the UStVA workpaper

Illustrative workflow with sample company names; not a connected live transaction. Last checked 2026-10-20. Review by a local tax practitioner is in progress; each statement is shown with its source and check date. General information, not tax or legal advice.

Not ready for a demo yet?

Tell us your country and work email. We will send the relevant workflow and what is ready there — no call needed.

Request a scoped walkthrough