SAP S/4HANA Cloud E-Invoicing — What Finance Teams Need to Know (2026)

If your organisation runs SAP S/4HANA Cloud and operates across Europe, you are facing a compliance gap that SAP itself does not close. Italy's FatturaPA clearance has been mandatory since 2019. Poland's KSeF system is now enforced for large taxpayers. Romania's ANAF eFactura has been mandatory since 2024. Germany requires B2B e-invoicing from 2027. France goes live in September 2026. Belgium's Peppol mandate is already active.

SAP S/4HANA Cloud is an excellent ERP for managing accounting documents, general ledger entries, and financial reporting. But none of the EU e-invoicing mandates are satisfied by creating a well-structured document in SAP. They require live API submission to government clearance systems, real-time status confirmation, and legally binding authority responses. That is a separate technical layer that SAP does not provide out of the box.

This guide explains the gap, what it means for SAP finance teams, and how to connect SAP S/4HANA Cloud to Clearvo in about 30 minutes — without any SAP development work.

What SAP S/4HANA Cloud Does (and Does Not Do)

SAP S/4HANA Cloud handles your accounting well. When a sales order is completed in SD, it creates an FI accounting document. That document captures the correct amounts, tax codes, counterparty, and general ledger assignment. The document types you care about for e-invoicing are:

• DR — Customer Invoice (direct FI entry)
• RV — Billing Transfer (SD-generated FI invoice, from VBRK/VBRP)
• DG — Customer Credit Memo (FI direct)
• RG — Customer Credit Note (SD-generated)

What SAP does not do: it does not generate country-specific e-invoice XML (FatturaPA, KSeF FA(3), XRechnung, UBL BIS 3.0), submit those documents to government clearance systems, poll for clearance status, return authority-issued reference numbers (like Italy's SdI protocol number or Poland's KSeF number), or handle rejection and resubmission workflows.

For countries where clearance is a legal prerequisite to issuing an invoice — Italy, Poland, France from September 2026 — this is not a reporting gap. It is a legal one. An invoice that has not cleared SDI in Italy is not legally issued, and you cannot collect payment on it.

The Communication Arrangement Architecture

SAP S/4HANA Cloud Public Edition controls all external API access through a framework called Communication Arrangements. Unlike traditional SAP where you might use direct RFC connections or SOAP web services, the Public Edition requires that every external integration be set up through three configuration objects:

1. Communication User — a technical user account (not a named employee) that authenticates inbound API calls
2. Communication System — registers the external system (in this case Clearvo at app.clearvo.io)
3. Communication Arrangement — links the Communication System to a specific set of APIs and generates OAuth 2.0 client credentials

This architecture is secure and auditable. Every API call made using the credentials appears in SAP's security and audit logs. The credentials grant read-only access to the specific OData services enabled in each arrangement — nothing more.

For a Clearvo connection, you need three arrangements covering three scenarios:

• SAP_COM_0303 (Finance – Accounting Analytics Integration) — grants access to API_OPLACCTGDOCITEMCUBE_SRV, the OData service that exposes posted FI accounting document line items. This is the primary data source for e-invoicing.
• SAP_COM_0120 (Billing Documents) — grants access to API_BILLING_DOCUMENT_SRV for SD billing document headers and line items. Needed if your invoice flow goes through Sales & Distribution rather than direct FI posting.
• SAP_COM_0008 (Business Partner Integration) — grants access to API_BUSINESS_PARTNER, which Clearvo uses to look up buyer name, address, and VAT registration number from your customer master records.

A note on a common mistake: the scenario SAP_COM_0009 is for product master data replication (MATMAS IDocs) — not finance or accounting data. It is sometimes cited in third-party integration guides but is the wrong scenario for e-invoicing purposes. Similarly, API_JOURNALENTRYITEMBASIC_SRV is designated by SAP for use with SAP Analytics Cloud only (via SAP_COM_0087/SAP_COM_0241) and should not be used as a general-purpose journal entry API.

OAuth 2.0 and How the Credentials Work

SAP S/4HANA Cloud Public Edition uses the OAuth 2.0 client_credentials grant type for inbound API authentication. This is important to understand because it differs from how many SaaS integrations work.

There is no redirect flow, no user login, and no browser involved. Clearvo holds a Client ID and Client Secret (generated in your Communication Arrangement), and uses them to request a bearer token directly from your SAP system's token endpoint:

POST https://<your-tenant>-api.s4hana.ondemand.com/sap/bc/sec/oauth2/token
Content-Type: application/x-www-form-urlencoded
Authorization: Basic base64(clientId:clientSecret)

grant_type=client_credentials

SAP returns a short-lived bearer token. Clearvo uses that token for subsequent OData API calls and automatically refreshes it before it expires. Your credentials remain encrypted in Clearvo's database — the plain-text secret is never logged.

Two URL formats to be aware of:

• UI URL: https://my12345.s4hana.ondemand.com — this is the Fiori Launchpad URL your users access in a browser
• API Gateway URL: https://my12345-api.s4hana.ondemand.com — this is the correct URL for OData API calls. Note the -api subdomain.

The API Gateway URL is what Clearvo needs. Using the UI URL for API calls is a common setup error — if you see "hostname not found" or SSL errors after entering credentials, check that you have the -api subdomain variant.

The Field Mapping

When Clearvo reads a SAP accounting document, it reconstructs an invoice from the line items in A_OperationalAcctgDocItemCube. Each row in this entity set is a line item — Clearvo groups rows by CompanyCode + FiscalYear + AccountingDocument to reconstruct the document header.

The key field mappings:

• Document date (BLDAT) → invoice issue date (preferred over posting date)
• Net due date → payment due date
• Transaction currency (WAERS) → invoice currency
• Document reference (XBLNR) → invoice number (falls back to the SAP document number)
• Amount in transaction currency (WRBTR) → line item amount
• Tax amount (HWBAS) → VAT amount per line
• SAP tax code (MWSKZ) → EN16931 tax code (S for standard, Z for zero, E for exempt)
• Customer number → triggers a Business Partner API lookup for buyer name, address, and VAT number

SAP document types map to e-invoice document types: DR and RV become invoice (document type 380); DG and RG become credit note (document type 381). This mapping follows the EN16931 European e-invoicing standard that underlies all EU country formats.

What the Setup Looks Like

The SAP side of the setup takes about 30 minutes for an administrator who has access to the Communication Management apps in SAP Fiori. There is no SAP development required — no ABAP, no transports, no BAdIs. All three configuration objects (Communication User, Communication System, three Communication Arrangements) are created through the standard Fiori UI.

The Clearvo side takes about two minutes: enter four values (System URL, Token URL, Client ID, Client Secret) in Settings → Integrations → SAP S/4HANA. Clearvo immediately tests the connection by requesting a token from your SAP system. If the token request succeeds, the connection is live.

Full step-by-step instructions — with the exact screen names, field values, and troubleshooting steps — are available in the SAP integration page and inside the Clearvo dashboard.

What Happens After Connection

Once connected, Clearvo reads accounting documents incrementally — starting from the last processed posting date and advancing the watermark on each sync. For each accounting document:

1. Clearvo fetches the document line items from SAP
2. It looks up the customer's name, address, and VAT number from the Business Partner API
3. It generates the country-appropriate XML format (FatturaPA for Italian buyers, XRechnung for German buyers, KSeF FA(3) for Polish buyers, and so on)
4. It submits the document to the relevant tax authority
5. It polls for clearance status and records the result in your Clearvo dashboard

If an invoice is rejected by the authority, it appears in your Clearvo dashboard with the rejection reason translated into plain English. You can correct the issue and resubmit without logging into any tax authority portal.

Every document processed includes the original SAP document number, company code, and fiscal year as metadata — so you can always trace a Clearvo invoice submission back to its source document in SAP.

Country Coverage from SAP

Once your SAP system is connected to Clearvo, all e-invoicing countries become available automatically — there is no per-country configuration required on the SAP side. Clearvo determines the correct authority and format based on the buyer's country on each invoice.

Current live coverage includes: Italy (SDI/FatturaPA), Poland (KSeF), Germany (XRechnung), Spain (VeriFactu), Portugal (SAFT-PT/ATCUD), Romania (ANAF eFactura), Greece (myDATA), Hungary (NAV), and 20+ countries via the Peppol network including Belgium, Netherlands, Denmark, Norway, Sweden, Finland, and more.

If your SAP system issues invoices across multiple EU countries, Clearvo handles the routing automatically — you do not need a separate connector or credential set per country.

Getting Started

The fastest path is to sign up at app.clearvo.io, navigate to Settings → Integrations, and follow the SAP setup guide there. The guide includes the exact SAP app names, field values, and troubleshooting steps for the three Communication Arrangements.

If you have questions during the SAP configuration, contact support@clearvo.io. We can also provide a PDF version of the setup guide to share with your SAP basis team.