Software guides · SAP · Peppol BIS 3.0

Peppol BIS 3.0 in SAP

SAP offers two Peppol paths: the integrated SAP Business Network (Ariba-based) or third-party Access Point integration via Document Compliance. This guide covers both approaches, with specific focus on EndpointID schemeID configuration—the #1 cause of Peppol transmission failures from SAP systems.

Prerequisites
  • SAP S/4HANA with Document Compliance (DOCCP) license, OR
  • SAP Business Network subscription with Peppol Access Point feature
  • Your company Peppol Participant ID registered with an Access Point
  • Trading partners discoverable in SML/SMP (Peppol directory lookup)
  • SAP Note 3156847 for latest Peppol BIS 3.0.17 schema
Step-by-step setup
  1. 01

    Choose integration path: SAP Business Network vs Document Compliance

    SAP Business Network offers a turnkey solution with built-in Peppol Access Point—best for companies already using Ariba. Document Compliance (/DOCCP) integrates with any third-party Access Point via REST/SOAP—better for flexibility. This guide covers Document Compliance; for Business Network, see SAP note 2919280.

  2. 02

    Configure your company Peppol Participant ID in company master

    Transaction SPRO → Enterprise Structure → Definition → Financial Accounting → Define Company. Add "Peppol Participant ID" in custom fields (requires SAP Note 2904195). Format: schemeID::identifier, e.g., "0088::5798000000001" (GLN) or "9930::DE123456789" (German VAT). The schemeID is critical—incorrect scheme = PEPPOL-EN16931-R010/R020 error.

  3. 03

    Add customer Peppol EndpointIDs in BP transaction

    Transaction BP → Customer → "E-Invoice" section → "Endpoint ID" and "Endpoint Scheme ID" fields. Common schemeIDs: 0088 (GLN), 0106 (NL KVK), 0190 (NL OIN), 9925 (BE VAT), 9930 (DE VAT). Look up correct scheme at Peppol Directory (directory.peppol.eu). Wrong schemeID = document not routable.

  4. 04

    Configure Access Point connection in /DOCCP/CONFIG

    Transaction /DOCCP/CONFIG → Communication Settings → Peppol. Enter Access Point endpoint URL, authentication credentials (certificate or API key), and participant ID. Test connectivity via /DOCCP/AP_TEST. For SAP Business Network: configuration is automatic once you enable Peppol in BN settings.

  5. 05

    Test the 4-corner model with your own participant ID

    Create a test billing document (VF01) addressed to your own company Peppol ID. This sends through corners 1→2→3→4 and back to your inbox. Check /DOCCP/EINV_LOG for transmission status. Green = delivered, Yellow = pending, Red = rejected. Download XML to validate with Invoice Navigator before real trading partner tests.

Common SAP errors

PEPPOL-EN16931-R001Missing Business Process

Why in SAP

SAP Document Compliance requires explicit ProfileID configuration. When copying configurations between systems or using custom output types, the Peppol profile identifier may not transfer correctly.

How to fix it

In Document Compliance configuration, set ProfileID = urn:fdc:peppol.eu:2017:poacc:billing:01:1.0. Verify in /DOCCP/CONFIG > Peppol Settings.

Full guide

PEPPOL-EN16931-R010Invalid Buyer Endpoint Identifier

Why in SAP

SAP stores Peppol participant IDs in various formats across customer master, but the schemeID attribute may be incorrect or missing. Common issue when importing customer data from external systems.

How to fix it

Add buyer EndpointID with correct schemeID in BP master data: 0088 for GLN, 9925 for Belgian VAT, 0106 for Dutch KVK, 0190 for NL:OIN.

Full guide

BR-CO-18Rounding Discrepancy

Why in SAP

Complex SAP pricing procedures with multiple condition types (discounts, surcharges, freight) can cause €0.01-0.02 differences between sum of line amounts and document total.

How to fix it

Review pricing procedure (V/08). Ensure consistent decimal places across all condition types. Use BAPI_BILLINGDOC_CREATEMULTIPLE with explicit totals.

Full guide

Pre-export checklist for SAP

Before exporting Peppol BIS 3.0 from SAP, verify these items:

  1. 01
    Verify customer Peppol participant ID is set with correct schemeID
  2. 02
    Confirm company Peppol ID is registered with your Access Point
  3. 03
    Check ProfileID is configured in Document Compliance
  4. 04
    Ensure all mandatory fields map correctly (AccountingSupplierParty, AccountingCustomerParty)
  5. 05
    Test 4-corner model with your own Access Point first
  6. 06
    Verify invoice totals match sum of line amounts
Testing your setup

Use SAP Business Network sandbox environment for Peppol testing. Create a test billing document and send to your own participant ID.

SAP provides Peppol test utilities via SAP Business Network. Contact your SAP account team for sandbox access credentials.

Validate your output

Validate your SAP Peppol output with Invoice Navigator before transmission. The Peppol BIS 3.0 validator checks all EN16931 and Peppol-specific business rules.

Check a Peppol BIS 3.0 file

FAQ
Do I need SAP Business Network for Peppol?

No, you can use any certified Peppol Access Point. SAP Business Network simplifies integration but is not required. Many customers use Basware, Pagero, or regional Access Points.

Can SAP receive Peppol invoices?

Yes, with Document Compliance or Business Network, SAP can receive and process incoming Peppol invoices. Inbound invoices are converted from UBL to SAP invoice documents.

Related guides

Have a Peppol BIS 3.0 invoice from SAP that came back rejected? Check it here.

Checking is free. The first verified download every 30 days is free. After that €1.90 per invoice, or €9 a month for all of them.