How do XRechnung and ZUGFeRD get into ERP?
Receipt, validation, approval, and posting without media breaks: what mid-market companies and finance IT must clarify for e-invoicing in ERP.
XRechnung and ZUGFeRD belong in ERP when receipt, validation, approval, and posting should run on the business transaction instead of in mailboxes and desktop tools. XRechnung delivers structured XML data for the public sector. ZUGFeRD combines machine-readable data with a PDF view for B2B. Technical format alone is not enough. What decides is the end-to-end process without media breaks, including audit-proof archiving.
What is the difference between XRechnung and ZUGFeRD?
XRechnung follows EN 16931 and delivers structured XML data. Toward public contracting authorities it is the governing standard. Systems must be able to receive, validate, and assign it to the transaction.
ZUGFeRD combines XML data with a PDF view. People read the document; systems read the structured data. In B2B the format is widespread because it serves both worlds.
Both formats need the same process steps: receipt, validation, assignment, approval, posting preparation, archiving. Teams that can only “store files” have touched the format obligation technically but missed the benefit.
What should the flow in ERP look like?
- Receive the inbound invoice and assign it to the transaction (purchase order, goods receipt, project)
- Check plausibility (amount, tax, references, duplicates)
- Approval and posting preparation in finance
- Audit-proof archiving on the dataset, not in a folder beside it
This path is also a GoBD topic: documents on the transaction, history, export capability. Deeper: GoBD and ERP. Integrations to DATEV and archive: ERP integrations.
Why do island solutions beside the ERP fail?
Because every separate e-invoice portal creates a second truth. Approvals run by mail, posting later by hand, archiving somewhere. In audits the continuous path is missing. Operationally, delays and double work appear exactly where volume and deadlines rise.
Nuclos embeds e-invoicing as an extension into existing order and finance processes, including DATEV and further integrations. Technical configuration and release status: Nuclos wiki on XRechnung and ZUGFeRD.
What do you clarify before the switch?
- Which formats actually arrive from customers and suppliers?
- Which deadlines and volumes apply in the next 12 months?
- Who approves functionally, who posts, who archives?
- Which systems stay (DMS, DATEV), and who operates the interface?
- How do you test validation, duplicates, and error cases before go-live?
A focused 48-hour prototype for inbound invoicing makes scope and effort tangible before the overall project starts. That is not a substitute for compliance advice, but a way to see process and system fit early.
Which decisions come next?
Inventory today’s receipt paths and media breaks. Prioritize one end-to-end inbound process (receipt to archive) instead of many parallel tools. Clarify DATEV, archive, and approval paths in parallel with format choice.
System fundamentals: What is ERP?. Compliance frame: GoBD and ERP. Integration: ERP integrations.