E-invoicing in SAP: Send & receive compliant e-invoices 

Your finance team is running out of runway on e-invoicing compliance. Germany already requires every business to receive structured e-invoices, and mandates are accelerating fast across France, the UK, and the rest of the EU.

If your SAP system isn't ready to send and receive compliant e-invoices in the right formats and channels, you're exposed to rejected invoices and blocked payments.

According to Deloitte's 2026 Global Tax Policy Survey, the share of finance leaders who expect e-invoicing to simplify compliance fell from 59% in 2024 to just 36% in 2026. Fragmented national mandates and formats are outpacing what most finance teams feel ready to handle.

This guide explains what e-invoicing in SAP actually involves: the formats, the channels, and where SAP's job ends and the e-invoicing layer begins. It covers both directions, sending and receiving, so you know exactly what your setup needs to stay compliant.

Key takeaways

• E-invoicing in SAP means transforming, routing, and dispatching structured invoice formats (XRechnung, Factur-X, Peppol, and others) directly from your SAP data
• SAP creates the invoice, but it doesn't natively handle format conversion, channel routing, or delivery tracking for every country mandate
• Outbound e-invoicing (sending) runs through billing and accounts receivable; inbound e-invoicing (receiving) runs through accounts payable and the P2P process
• Compliance mandates are staggered globally: Germany already requires reception, France starts September 2026, the UK follows in 2029, and the US has no federal mandate yet, while ViDA extends cross-border requirements EU-wide by 2030
• Most e-invoicing vendors handle only one direction and sit outside SAP in a separate portal, which creates a second system for finance teams to manage
• Doxis embeds e-invoicing for both directions directly inside SAP, with format and channel configuration handled by the business, not IT

What is e-invoicing in SAP?

E-invoicing in SAP means exchanging invoices with customers and suppliers in a structured, machine-readable format, not as a PDF or paper document. In practice, that means converting invoice data into a mandated format like XRechnung or Peppol BIS, sending it through the required channel, and tracking its status through acceptance or payment.

Why e-invoicing in SAP is no longer optional

E-invoicing has moved from a competitive advantage to a legal requirement, and the timeline is arriving in waves rather than on a single deadline. Here's where the pressure is coming from right now:

Germany

Germany already requires every business to be able to receive e-invoices. Sending is phased in by company size:

• From January 2027: Mandatory issuance for businesses above the €800,000 turnover threshold
• From January 2028: Mandatory issuance for all businesses
• Accepted formats: Any format compliant with the EN 16931 standard, commonly XRechnung or ZUGFeRD

France

France introduces both e-invoicing and e-reporting together, rolling out by company size:

• From September 2026: Reception mandatory for all businesses; issuance mandatory for large and mid-sized companies
• From September 2027: Issuance mandatory for small and medium businesses
• Format and platform: Factur-X, transmitted through certified private platforms or the Chorus Pro platform for public-sector invoices

The rest of the EU

Germany and France aren't isolated cases. Most other EU member states are already live or moving through their own phased rollouts:

• Status: National mandates in force or in active rollout across the majority of member states
• Formats: Vary by country, though nearly all align with the EN 16931 standard
• Horizon: ViDA requires standardized cross-border e-invoicing and near-real-time digital reporting across every member state by July 2030

United States

The US takes a different approach, with no government mandate driving adoption yet:

• Status: No federal B2B e-invoicing mandate; adoption remains voluntary
• B2G exception: Federal procurement invoicing runs electronically through the Treasury's Invoice Processing Platform, per OMB Memorandum M-15-19
• Market trend: The Digital Business Networks Alliance is building a voluntary, Peppol-based exchange network

Any US business selling into the EU or working with EU subsidiaries still needs to send and receive compliant e-invoices for those transactions.

United Kingdom

The UK doesn't have a live mandate yet, but the timeline is set:

• Status: No mandate today; mandatory e-invoicing confirmed for all VAT invoices from 2029
• Model: Expected to follow a Peppol-based four-corner exchange, without real-time reporting to HMRC in its initial phase
• Roadmap: Full implementation details due at Budget 2026

For a business running SAP across multiple countries, this means handling several formats and channels at once as new mandates come into force. Non-compliant invoices get rejected outright, which delays payment, and some jurisdictions attach direct penalties on top.

How e-invoicing works in SAP: formats, channels, and compliance

Hey Doxi, how does e-invoicing work within SAP?

Sending compliant e-invoices from SAP (outbound)

Outbound e-invoicing starts where SAP's Billing process ends. Doxis O2C for SAP picks up the invoice SAP already generated and handles everything mandate compliance requires from there.

Format conversion and dispatch

Once SAP generates the invoice, Doxis converts the document into the correct format for the customer's country and transmits it through the right channel automatically:

• Peppol for a Belgian customer
• Factur-X through Chorus Pro for a French public-sector client
• XRechnung for a German counterpart

None of this requires your accounts receivable team to touch the format logic themselves. The routing decision is made based on the customer's country and the mandate that applies to them.

Status tracking

Every outbound invoice needs a visible trail showing whether it was sent, accepted, rejected, or paid, and finance teams need that trail inside the system they already work in rather than a separate portal.

With Doxis O2C for SAP, send status and payment status show up directly in the SAP monitor, so your accounts receivable team sees exactly where every invoice stands without switching tools.

This matters directly for cash flow. Rejected or delayed e-invoices push out payment timelines, and every manual correction step adds days to a receivables cycle that mandates are supposed to be speeding up, not slowing down.

Receiving e-invoices into SAP (inbound)

Inbound e-invoicing is the accounts payable side of the same challenge, and it's handled by a different part of the process: the Doxis Invoice Automation for SAP module within P2P.

Capture across every channel

Suppliers don't all send invoices the same way. Doxis captures each of these channels and handles them according to what they are:

• Structured formats: XRechnung, ZUGFeRD, and FatturaPA are processed directly, with data read straight from the embedded XML
• EDI and Peppol: Captured through the corresponding network connection
• PDFs and paper: Read through AI-powered OCR for SAP when a supplier hasn't moved to a structured format yet

Validation and posting

Once captured, the invoice is validated and automatically checked against the corresponding purchase order and goods receipt in SAP. Where the amounts, quantities, and vendor details align, the invoice posts straight through to accounts payable.

Where something doesn't match, it's flagged for review with the relevant SAP data already attached, so your AP team isn't starting from a blank screen.

Every inbound invoice, structured or not, lands in a central Invoice Monitor with its status shown directly in SAP, giving your team one place to see what's been received, what's pending, and what needs attention.

This inbound side is what most people mean when they talk about invoice automation, but it's only compliant e-invoicing if it actually reads and processes the structured formats your suppliers are increasingly required to send, not just digitizes PDFs.

Why most e-invoicing solutions only solve half the problem

Search for an e-invoicing solution for SAP and you'll find plenty of capable vendors on the market. Most of them do the underlying plumbing well: format conversion, network connectivity, delivery confirmation. Where they fall short is scope and location.

The typical setup

Most e-invoicing vendors share the same limitations:

• One direction: Most often outbound sending, with inbound receiving left to a separate software or manual process
• A separate portal: Nearly all run in a web interface outside SAP, managed by IT rather than finance
• A second vendor relationship: On top of whatever you're already running for invoice automation or archiving in SAP

That split creates real friction. Your accounts receivable team works in one interface, your accounts payable team works in another, and neither is the SAP screen they already use every day.

IT ends up owning the vendor relationship for a workflow that's fundamentally a finance process, and finance loses direct visibility and control over format and channel configuration.

What embedded, two-way e-invoicing gets you

Doxis takes a different approach: e-invoicing embedded directly inside SAP, covering both inbound and outbound in a single platform. Here's what that changes in practice.

One system, not two

There's no separate portal to log into and no second vendor relationship to manage. Your accounts receivable and accounts payable teams both work from the same SAP screens they already use every day, with e-invoicing status, configuration, and monitoring built directly into them.

Configured by finance, not locked to IT

Format and channel settings, which standard to use for which country and which network to route through, are configured by the business inside SAP. There's no need to file a ticket or wait on an IT project every time a customer or supplier's country requirements change.

No dependency on SAP DRC

Doxis covers the e-invoicing layer without requiring SAP's own Document and Reporting Compliance (DRC) add-on, so you're not paying for and maintaining a separate SAP module on top of your existing SAP investment.

Built to adapt as mandates change

New country mandates come into force every year, and your setup adapts along with them rather than triggering a new IT project each time a government changes its requirements.

Get compliant, two-way e-invoicing built into SAP with Doxis

Chasing e-invoicing compliance one mandate at a time, with separate tools for sending and receiving, is a slow way to lose control of your invoicing process. Doxis solves both sides from inside SAP itself.

E-invoicing runs on the same Doxis Intelligent Content Automation platform that handles your SAP archiving, contract management, and compliance retention. One system covers your invoices, contracts, and records instead of a separate tool for each.

With Doxis embedded e-invoicing, you get:

• Outbound dispatch through the Billing module, with automatic format transformation and channel routing for each customer's country
• Inbound capture and validation through the P2P Invoice module, covering structured formats, EDI, and PDF alike
• Real-time send, payment, and processing status visible directly in the SAP monitor, not a separate portal
• Business-configurable format and channel settings, so finance controls compliance logic without depending on the SAP DRC add-on
• SAP-certified integration, built to extend your existing SAP investment rather than sit alongside it
• One platform for invoicing, archiving, and contract compliance across SAP, instead of a vendor per workflow

Doxis has been recognized as a Leader in the Gartner® Magic Quadrant™ for Document Management 2026, reflecting the same platform depth that powers its e-invoicing capabilities inside SAP.

Ready to see compliant, two-way e-invoicing running inside your own SAP system? Request a free demo with Doxis below.

FAQs about e-invoicing in SAP