Since 2025, e-invoicing has been mandatory for B2B in Germany. OXS.eco receives XRechnung and ZUGFeRD invoices, validates them against DIN EN 16931 and passes the structured data straight on into approval, the case file and the archive, with no duplicate data entry.
Google Cloud in Frankfurt · aligned with GoBD · EN 16931 · data processing agreement available · personally supported
XRechnung and ZUGFeRD now arrive alongside paper and PDF invoices. OXS.eco sorts that automatically and makes the structured data usable right away, so nobody has to retype anything.
The requirement is phased in. Receiving has been mandatory since the start of 2025, issuing follows in stages up to 2028. OXS.eco covers both sides on the same platform.
Since 1 January 2025
German companies must be able to receive e-invoices, small businesses included. For receiving there is no transition period.
From 1 January 2027
Companies with prior-year revenue above €800,000 must issue e-invoices to other companies (§ 27 (38) UStG).
From 1 January 2028
Issuing becomes mandatory for domestic B2B regardless of prior-year revenue. Small businesses under § 19 UStG remain exempt.
From 2027 · issuing becomes mandatory too
Soon you will not only have to receive e-invoices, you will have to issue them yourself. OXS.eco generates the ZUGFeRD format automatically from your outgoing invoices, and nobody has to fill in a form. The full path through to dispatch to the recipients is shown under Document dispatch.
Structured e-invoice in XML format. Especially relevant for public-sector clients and PEPPOL.
Hybrid format. A readable PDF with structured invoice data embedded in it.
The European standard that XRechnung and ZUGFeRD are technically validated against.
Via e-mail, upload, SFTP or PEPPOL. XRechnung and ZUGFeRD arrive automatically in the same inbox as paper and PDF invoices.
Checked against DIN EN 16931: schema, mandatory fields, format conformance. Errors become visible before your team approves.
Structured data plus a link to the document go into approval, the case file and the archive. No duplicate data entry, no change of ERP system.
OXS.eco reads every mandatory field out of the structured XML and checks it against DIN EN 16931. The result is visible before the invoice goes into approval.
From the inbound channel to hand-over into the workflow, in five traceable steps. Valid documents are prepared for the workflow together with their data, ZUGFeRD additionally as a readable PDF; invalid ones produce an error report.
E-invoices are taken in from e-mail, upload, SFTP or PEPPOL and recognized automatically as XRechnung or ZUGFeRD.
The XML structure is checked against DIN EN 16931: mandatory fields, schema and format conformance.
ZUGFeRD brings its own readable PDF, XRechnung files are displayed with their structured data. Fields such as supplier, amount and due date are available directly in the process.
If the XML is invalid, a traceable error report is generated that lists the validation problems in plain language.
Validated e-invoices are handed into the approval workflow and archived together with their validation result, traceably.
The real gain comes when the validated e-invoice flows straight into your existing workflows, with no duplicate data entry and no change of ERP system.
In the workflow
Validated XRechnung and ZUGFeRD invoices land in the same approval workflow as paper and PDF invoices. Multi-stage, with queries to colleagues, with deputies. The groundwork is laid by the Invoice Register (REB): classification, data capture, account assignment.
In the case file
Structured data flows into the digital case file. Supplier, amount, due date, document and validation result sit together and stay searchable. File management in detail under Digital Case Files.
In the archive
Invoice and XML original are stored together in an audit-proof way. In a Betriebsprüfung they are readily retrievable. How that stays audit-proof is shown under Archiving.
In your ERP
Validated XRechnung data goes to your accounting system like any other document: in production to Diamant, further systems project-based on request. The details are shown under Accounts payable.
From your system
You keep writing your outgoing invoices where you write them today. OXS.eco takes the invoice data or the PDF from your system, reads it and imports it.
In the workflow
Conversion into the ZUGFeRD format runs automatically in the workflow. Nobody types invoices into a form by hand, not even with hundreds of documents a month.
To your customers
The generated e-invoice goes to the recipients of your invoices. How dispatch is documented verifiably is shown under Document dispatch.
Timeline
From 2027, companies with prior-year revenue above €800,000 must issue e-invoices (§ 27 (38) UStG), from 2028 all remaining companies follow; small businesses under § 19 UStG remain exempt. The full timeline is shown under Mandatory e-invoicing at a glance.
Want a quick way in? Have an e-invoice checked free of charge, no sign-up required.
XRechnung is a pure XML format, ZUGFeRD a hybrid of a readable PDF with embedded XML; OXS.eco processes both in the same way.
OXS.eco validates against DIN EN 16931 and checks mandatory fields and structure. Faulty invoices are identified with a traceable error report before they enter the approval workflow.
OXS.eco receives e-invoices from the PEPPOL network; we set up the connection on a project basis. Incoming XRechnung files are validated against DIN EN 16931 and passed into the approval and archiving process by rules.
E-invoices are one inbound channel in the invoice workflow. OXS.eco connects e-invoice receipt directly with approval, the digital case file and archiving aligned with GoBD, no isolated special path.
In the online meeting we review your inbound e-invoices and show how OXS.eco receives XRechnung and ZUGFeRD, checks them and hands them into approval and the archive. On request we also show how OXS.eco outputs your outgoing invoices as ZUGFeRD. You will be talking to Hélène Tinet.
Related solutions
