SAP describes invoices internally with the INVOIC02 IDOC — comprehensive, but not itself a valid e-invoice for public administrations.
To meet German and European requirements, invoices must be sent as XRechnung (UBL), Peppol BIS 3.0 or ZUGFeRD 2.x (CII). Invoice Portal provides a ready-made mapping between INVOIC02 and these formats, validates the result and dispatches it via Peppol.
User posts an invoice; SAP generates the INVOIC02 IDOC.
IDOC is passed to Invoice Portal via interface or file transfer.
Substitution or transformation into the required e-invoice format.
Schema and business rules are checked before dispatch.
Delivered through Peppol or the relevant national platform.
Sent / accepted / rejected is synced back into SAP.
When source and target share the same syntax (both UBL-based), only the envelope changes. All fields stay intact. Used for IDOC → XRechnung and IDOC → Peppol BIS 3.0.
When syntaxes differ (EDIFACT-based IDOC → CII), conversion is performed by transformation. Tax and totals remain unchanged; output is validated. Used for IDOC → ZUGFeRD / Factur-X.
Substitution · 100% data integrity
XRechnung 3.0.2
German public-sector standard, ready for submission via Peppol or national portals.
Substitution · 100% data integrity
Peppol BIS Billing 3.0
Cross-border invoicing across the Peppol network within Europe
Transformation
95%, fiscal data preserved
ZUGFeRD / Factur-X
EN 16931 CII profile, with optional PDF/A-3 carrying the embedded XML.
Additional converters such as IDOC → Factur-X or other national formats available on request.
Each IDOC segment is mapped to the corresponding element in the target standard. Below are simplified examples for both syntaxes — the actual mapping covers the full INVOIC02 scope.
XRechnung, Peppol BIS and ZUGFeRD are covered out of the box — no custom coding or mapping tables on your side.
Invoice creation, conversion and status monitoring remain in the familiar SAP environment — no parallel tools for accounting.
Manual rekeying disappears — sending, validation and status updates run automatically, shortening time to payment.
Additional mappings such as IDOC → Factur-X or further national formats can be added as regulations evolve.
Substitution preserves 100% of the data for UBL targets; transformation keeps all fiscal data for CII. Every output is validated.
Native integration via Business Central E-Document Workflow
OAuth 2.0 / API Key
Outgoing invoices and credit notes (sending)
HTTPS / UBL XML
Peppol BIS 3.0, XRechnung (XML)
Test and Production
Enterprise-grade information security management system in place
Seamless, standardized e-invoicing across 35+ European countries
End-to-end data processing adheres to EU privacy regulation
All data hosted within GDPR-aligned EU facilities
