PEPPOL-EN16931-R001

Business process identifier is missing

Repaired automatically Field BT-23 PEPPOL UBL / CII

What it means

Peppol requires every invoice to declare which business process it belongs to (BT-23), even though base EN 16931 does not. Access Points and receiving ERPs use it to route the document to the right workflow. For ordinary billing the value is a fixed constant, so a document missing it is almost always a generator that never emitted the field rather than a business decision.

Can it be fixed automatically?

Nothing about your business is needed to fix this — the correct value is a constant, a code list entry, or is already present in the document.

This one can be repaired automatically. The API applies the fix, re-validates, and reports exactly what changed with before and after values.

How to fix it

Set the Peppol billing process identifier 'urn:fdc:peppol.eu:2017:poacc:billing:01:1.0'. No business data is involved.

Where it applies

CII/rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext/ram:BusinessProcessSpecifiedDocumentContextParameter/ram:ID
UBL/Invoice/cbc:ProfileID

Check your own invoice

curl -X POST https://einvoice.mgsoft.sk/v1/validate \
     -H 'Content-Type: application/xml' \
     --data-binary @invoice.xml

← All rules