— SAP e-Invoice Solution
Issue, receive and archive e-invoices directly from SAP
The OXORY SAP e-Invoice Solution keeps the whole invoice lifecycle inside your SAP system — generation, format determination, validation, dispatch, status feedback and audit-proof archiving — without manual portals or media breaks.
Definition
What an e-invoice actually is
The legal definition is narrower than everyday use of the term — and that difference decides whether your process is compliant.
- A structured electronic document that carries the invoice data in a machine-readable syntax — not a scan and not a plain PDF attachment.
- Legally equivalent to a paper invoice when authenticity of origin, integrity of content and readability are ensured throughout the retention period.
- Processable end to end: the recipient's system can post it without re-keying, and every step leaves a traceable record.
- Based on the European semantic standard for electronic invoicing, expressed in national or network-specific formats such as XRechnung, ZUGFeRD or Peppol BIS.
Which formats and mandates apply in each country is covered on our compliance & e-invoicing overview. This page focuses on how the solution works inside SAP and how documents are archived.
How it works
The e-invoice process inside SAP
Five steps, all triggered from your existing billing process.
- Step 01
Document selection in SAP
The solution picks up billing documents from your existing SAP invoicing run — no parallel invoicing process, no separate front-end for the accounts-receivable team.
- Step 02
Automatic format determination
Recipient master data and country rules decide the target format per document: XRechnung, ZUGFeRD, Peppol BIS or a country-specific format where a national mandate applies.
- Step 03
Validation
Each document is checked against the schema and business rules of the target format before it leaves the system, so rejections are caught while the invoice can still be corrected cheaply.
- Step 04
Dispatch
Delivery runs via direct integration with the buyer, a certified Peppol access point, a national portal or an e-mail fallback — chosen per recipient, not per company.
- Step 05
Status and error feedback in SAP
Acknowledgements, rejections and retries are written back to the SAP document, so the invoice status is visible where the finance team already works.
Archiving
Audit-proof archiving without a media break
Structured invoices have to stay unchanged, complete and retrievable for the full statutory retention period — in the system where they were created.
- Unalterable storage of the structured original together with its visual rendition and technical protocols.
- Retention driven by configurable rules rather than a hard-coded number of years, so a change in statutory retention periods is a configuration change.
- GoBD-oriented documentation: procedural documentation, logging and traceability of every processing step.
- Full-text search and filtering directly in SAP — by customer, amount, document number, date or delivery status — instead of paper files or a separate archive front-end.
- One archive for outbound and inbound documents, so audits and tax reviews can be served from a single source.
Retention periods for invoices are set by tax law and have been adjusted repeatedly in recent years. We configure the archive against the period that currently applies to your entities and confirm it with your tax advisors — this page is information, not legal or tax advice.
Advantages
What changes once invoicing is structured
End-to-end traceability
Lower process cost
No print, paper or postage
Immediate archive access
One process across countries
FAQ
e-Invoice questions we get asked
Ready to move invoicing into your SAP system?
Tell us your countries, document volumes and current formats — we will map the process, the archive requirements and the roll-out steps against your target date.
SAP is a registered trademark of SAP SE. The OXORY SAP e-Invoice Solution is an independent OXORY solution and has no partnership or affiliation with SAP SE.
