Back to the error catalogue
PEPPOL-EN16931-R001BT-23
input

The business process is not provided

`Business process type` (BT-23) must be provided. The XRechnung package takes this rule from the Peppol CIUS, which it embeds.

Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.

The message your validator prints

Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.

Business process MUST be provided.

Quoted from schematron-xrechnung 3.0.2, licensed under Apache-2.0.

Common searches around this code

These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.

PEPPOL-EN16931-R001 The business process is not providedPEPPOL-EN16931-R001 XRechnung Schematron package (KoSIT)PEPPOL-EN16931-R001 BT-23Business process MUST be provided.PEPPOL-EN16931-R001 correction

Test your file with this error in mind

Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.

To automate this check in an ERP flow, call the validation API and link every returned code to its public page.

Why this error happens

The prefix is surprising inside a German base: the KoSIT embeds the Peppol CIUS in its validation configuration, so its rules bind an XRechnung issuer exactly as the `BR-DE-*` ones do. BT-23 names the exchange process — for an invoice, the Peppol billing URN — and it is what decides downstream handling.

How to fix it

Have your generator declare the process. Factlint does not write it: the process URN is a statement about how the document travels, not something derivable from its content.

XML correction example

BEFORE (invalid)
<!-- ram:BusinessProcessSpecifiedDocumentContextParameter absent -->
AFTER (compliant)
<ram:ID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</ram:ID>