Compliance & Digital Accounting

E-invoicing rules & formats for German Businesses

Structured e-invoices cut manual work across accounting, auditors, and public-sector buyers—as long as you roll out XML-based formats like XRechnung and usable hybrid PDF/XML like ZUGFeRD before obligations reach your counterparties or supply chain.

Invoicing & XRechnung in cashwerk View pricing

What counts legally & operationally as an e-invoice?

In modern German bookkeeping, “e-invoice” means structured invoice data—not just emailing a PDF attachment. Authorities and large buyers increasingly expect schemas aligned with EU standard EN 16931, implemented domestically via XRechnung, optionally embedded in readable PDF wrappers (Factur-X/ZUGFeRD). SMEs must ensure invoices ingest automatically into purchaser systems without re-keying tax amounts, identifiers, payment metadata, while still satisfying GoBD immutability, audit trails, and retention. cashwerk originates quotes, deliveries, hourly data, and project costs in one ledger-style workflow so invoice payload fields stay coherent with downstream DATEV pipelines and archiving. Public-sector programs often require routing IDs, contract references, and cost-type metadata to stay aligned with purchase orders over multi-year engagements—structural rejections spike when customer master data differs from the buyer portal. Front-load validation on tax rates, discounts, service periods, and payment terms before issuance, then freeze approved artifacts so archival copies cannot be silently overwritten. A disciplined state machine (draft → approval → transmission → dunning) preserves defensible histories for tax examiners and commercial disputes alike.

XRechnung

XRechnung encodes taxable line metadata, totals, identifiers, routing, and referenced contracts in validated XML—it is Germany’s flagship profile atop EN 16931 for machine processing.

ZUGFeRD / Factur-X

ZUGFeRD / Factur-X pairs human-readable PDF/A-3 with embedded XML payloads so bookkeeping tools can OCR-free parse totals while reviewers keep a printable view.

Related modules in cashwerk

Connecting quotes, deliveries, tax lines, and exports without brittle copy/paste hops.

Invoices & templates Accounting integrations Guides & glossary

Timeline: escalating expectations

2017–2022

B2G mandate & profiling

Public-sector buyers tightened electronic submission rules across Germany while XRechnung operationalized EU EN 16931. Anyone invoicing administrations learned early how XML validation, routing IDs, and buyer portals behave—establishing competencies that migrate into private-sector supply chains.

2025 (platform & B2G focus)

Adoption tipping point

Large retailers and platforms widen electronic invoice intake. Counterpart clauses and technical gateways make unstructured PDF invoicing brittle even when no single SME deadline grabs headlines. Submission rejections slow cash flow.

2026+

Validation-heavy networks

Expect broader connectivity (e.g., Peppol-style routing) alongside stricter archival evidence. Produce hybrid ZUGFeRD plus pure XML payloads, pair them with GoBD-compliant immutability, clear booking references, and reproducible histories for tax audits.

Where cashwerk reduces invoice risk

Maintain coherent linkage between quotes, time, deliverables and tax payloads; automate exports; preserve audit traces.

Unified source fields

Avoid divergent narratives between CRM, delivery proof, hourly burn, statutory IDs before XML payloads render.

GoBD-aligned trails

Guard immutability: documented adjustments instead of silent overwrites.

Exports & gateways

Orchestrate DATEV-aligned paths and deterministic delivery timestamps.

E-invoice FAQ

How is an e-invoice different from “just a PDF”?

Plain PDFs are visual; XRechnung XML encodes mandatory tax/line metadata for automated validation. ZUGFeRD embeds that XML in PDF/A-3 for hybrid human + machine flows.

When must my company act?

Pressure comes from buyer portals, platform SLAs, and public-sector tech gates—not a single universal SME calendar date. Early structured exports prevent payment friction.

Who owns tax field accuracy?

Issuers remain liable for VAT accuracy. Software supplies guardrails, not legal substitution—source systems must stay coherent.

Do I need both XRechnung and ZUGFeRD?

Often buyers demand pure XML; internal approvers prefer hybrid PDF/XML. Originate once, emit variant artifacts without double entry.

How does cashwerk help GoBD-facing audits?

Post-finalization invoices stay locked; deltas become explicit corrections with rationale. Tie hours/approvals/reminders into one reproducible dossier.

What operational risks linger without readiness?

Buyer rejections stretch DSO; finance shared services bleed manual rework; auditors surface timing/tax inconsistencies when sources disagree.

Ready to stage XRechnung / ZUGFeRD payloads?

Because cashwerk keeps CRM, hourly data, approvals, and tax lines coherent, invoicing payloads stay reproducible across DATEV-compatible exports and archiving.

Explore the invoicing module

Laden...