Germany E-Invoicing Readiness Assessment

⚖️

Section 1 of 5

Regulatory Awareness

Q1

Since January 2025, all businesses must be able to receive structured e-invoices (XRechnung, ZUGFeRD). How far has your organisation progressed on both reception and the 2027 issuance obligation?

Minimal progress — inbound processing is not automated and 2027 issuance preparation has not started.

We can receive structured invoices but rely on manual processing; issuance has not been formally scoped.

Inbound processing is being automated; our 2027 issuance programme is underway with format, ERP, and supplier plans in development.

Inbound is automated and tested; 2027 issuance is in pilot with key customers, and a supplier readiness programme is running in parallel.

Q2

Germany's mandate applies only to domestic B2B transactions between German-established entities. Have you formally defined what is in scope — including EDI arrangements, foreign subsidiaries, and low-value invoice exemptions?

Not scoped — we have assumed all invoices are in scope without reviewing entity structure or exemption conditions.

We have a general understanding but have not reviewed establishment status for each entity or assessed EDI and low-value exemptions.

Scope defined for main entities; some edge cases (foreign-established group companies, specific EDI flows) are still under legal review.

Fully documented — establishment status confirmed per entity, EDI arrangements assessed, exemptions flagged, and B2C and intra-EU exclusions validated across all entities.

🖥️

Section 2 of 5

Technical Infrastructure

Q3

Have you finalised your format strategy (XRechnung vs ZUGFeRD) and transmission channel (Peppol, EDI, or other) for different customer segments?

Not decided — we have not evaluated format trade-offs or assessed which transmission channel fits each customer segment.

We have a provisional format preference but have not validated it against customer reception capabilities at scale.

Format strategy defined — XRechnung for structured flows, ZUGFeRD where a human-readable layer is needed; Peppol connectivity is being assessed.

Finalised and operational — format selection is automated by customer segment, Peppol with GEBA addressing is configured as the primary channel, and fallback protocols are tested.

Q4

How are your AR and AP workflows being adapted to handle the transition from PDF exchange to mandatory structured e-invoicing data?

Not started — our AR and AP workflows are unchanged; we are treating e-invoicing as a format change, not a process change.

We have identified that workflows need to change but redesign has not started; current plan is to manually handle structured invoices within existing processes.

AR and AP workflows are being redesigned — automated posting rules, validation triggers, and exception queues are defined but not fully tested.

Fully redesigned and tested — structured invoice data drives automated three-way matching, real-time posting, and exception routing in both AR and AP with minimal manual intervention.

Q5

From January 2027, issuing non-compliant invoices (including PDFs) will invalidate your customers' right to deduct VAT. Have you quantified this risk and built controls to prevent non-compliant issuance?

Not assessed — we have not modelled the VAT deduction impact on customers from non-compliant invoices after 2027.

We are aware of the risk but have no controls or quantified exposure analysis in place.

Risk quantified; pre-submission validation is being implemented to flag non-compliant invoices; customer communication is planned.

Fully mitigated — automated validation blocks non-compliant issuance; customers notified of transition timeline; dispute resolution process documented and tested.

Q6

Germany's GoBD rules require e-invoices to be archived in their original structured format — unaltered — for 10 years. Does your archiving infrastructure meet this for all inbound and outbound flows?

No — we archive PDFs or ERP exports; original XRechnung or ZUGFeRD XML files are not preserved separately.

Digital archiving exists but we have not validated that original structured formats are preserved unaltered or that GoBD integrity requirements are met.

GoBD-compliant archiving covers most flows; gaps remain for some legacy EDI formats and email-delivered invoices where XML attachments are not always captured.

Fully compliant — original structured formats preserved unaltered and tamper-proof across all channels, retrievable within hours for any period in the 10-year window.

⚙️

Section 3 of 5

Process Maturity

Q7

Have you documented and tested compliant workflows for complex transaction types — structured credit notes, intercompany invoices, self-billing, and FX invoices?

Not addressed — compliance work has focused on standard invoice flows; complex types have not been scoped.

We know these have specific requirements but workflows are undocumented and testing has not been planned.

Most types are documented and tested; a few edge cases (self-billing in specific business units, multi-currency flows) remain open.

All types fully documented, tested against EN 16931, and owned — including structured credit notes, self-billing, FX invoices, and intercompany corrections.

Q8

Your suppliers and customers across Europe will send e-invoices in different formats — XRechnung, ZUGFeRD, Factur-X, Peppol UBL, and others. Do you have a single, consolidated view of all inbound and outbound e-invoice flows across formats and markets?

No — each format and country is handled in isolation; there is no consolidated view.

We have visibility within Germany but no unified view across other markets or formats.

A centralised view is being built; Germany and one or two other markets are connected but coverage is incomplete.

Full consolidated view in place — all formats and markets flow into a single platform with unified tracking, exception management, and compliance monitoring.

Q9

Have you assessed which of your suppliers will be unable to issue compliant e-invoices by January 2027 — and do you have a plan to manage AP disruption during the transition?

Not started — we have not identified non-compliant suppliers or assessed the AP impact.

We are aware of the supplier risk but have not contacted suppliers, assessed readiness, or planned contingency AP handling.

Supplier risk segmentation done; high-volume suppliers are being supported with format guidance; a small-supplier strategy is in development.

Proactive programme underway — all material suppliers assessed, compliance support in place, and AP can handle a defined residual volume of non-compliant flows post-2027.

🏢

Section 4 of 5

Organisational Readiness

Q10

Has a fully scoped budget been approved — covering ERP development, format testing, Peppol connectivity, GoBD-compliant archiving, supplier communication, and post-go-live support?

No budget — e-invoicing is being absorbed within existing IT and finance capacity; no formal cost assessment has been done.

Budget is under discussion but not approved; the full scope and true costs of ERP changes, archiving, and supplier management have not been assessed.

Fully scoped budget approved for both the 2025 reception and 2027 issuance phases, with a named programme owner.

Fully funded with C-level sponsorship — implementation underway with clear milestones, post-go-live support budgeted, and a quantified automation ROI agreed.

Q11

How confident are you that your ERP vendor and e-invoicing platform will keep pace with ongoing BMF clarifications and technical updates to the mandate?

Not confident — our vendor has not demonstrated a track record on German mandate updates; we are considering alternatives.

Uncertain — we have not assessed our vendor's responsiveness to mandate changes or established contractual compliance update obligations.

Cautiously confident — our vendor has responded to BMF updates to date and is committed to ongoing compliance; SLAs are being negotiated.

Fully confident — vendor contractually committed to continuous compliance updates with defined SLAs and a validated response track record on prior BMF clarifications.

🔭

Section 5 of 5

Future Readiness

Q12

Germany currently has no real-time government clearance or e-reporting requirement. How is your organization preparing for the upcoming EU "VAT in the Digital Age” ViDA reporting mandates?

Not on our radar — we are focused solely on meeting the January 2027 issuance deadline.

We are aware of ViDA but have not built any architectural flexibility for future reporting into our current implementation.

Our architecture is ViDA-aware — our ERP and format strategy can extend to a reporting layer without a full rebuild.

ViDA-aligned roadmap in place — structured data, master data governance, and vendor strategy are all designed to absorb digital reporting obligations as they are confirmed.

Q13

Post-2027 tax audits are expected to incorporate structured invoice data — checking format integrity, GoBD archiving, and VAT consistency. How prepared is your organisation for this more data-driven audit environment?

Not prepared — we have focused on go-live compliance; the audit implications of structured invoice data have not been assessed.

We know audits will be more data-driven after 2027 but have not reviewed our controls, VAT positions, or archiving integrity against this.

Initial audit readiness review done — data quality issues and GoBD gaps are being addressed; a VAT consistency check is planned before the 2027 deadline.

AI-powered audit readiness in place — continuous automated checks across format integrity, GoBD archiving, and VAT consistency flag anomalies before they become audit findings.

Q14

Has your organisation planned to capture the operational gains from structured e-invoicing — touchless AP processing, automated three-way matching, and reduced manual reconciliation?

No — our programme is compliance-only; operational efficiency benefits have not been assessed.

We recognise efficiency gains are possible but have not quantified them or built them into our programme objectives.

Benefits quantified — reduced AP workload, faster processing, and lower exception rates are targeted; tooling is being evaluated.

Operational transformation is a core objective — quantified business case for touchless AP, AI-assisted exception management, and automated reconciliation, tracked against post-go-live metrics.

Response Scale: L1 = Early Stage L2 = Developing L3 = Progressing L4 = Advanced

Germany E-Invoicing Readiness Assessment

Your Details