Peppol BIS Self-Billing 3.0 Invoice
Peppol BIS Self-Billing 3.0 invoice (self-billed invoice)
A Peppol self-billed invoice, issued by the buyer in the seller's name, checked against the UBL 2.1 schema, the EN 16931 rules and the Peppol BIS Self-Billing 3.0 rules.
About
In self-billing the buyer issues the invoice in the name of the seller, from its own records of what it received, and sends it to the seller over Peppol. Article 224 of the VAT Directive (2006/112/EC) allows this only under a prior agreement and with a procedure for the seller to accept each invoice.
Peppol BIS Self-Billing 3.0 is the EN 16931 profile for it (business process P12): its specification identifier (CustomizationID) is urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:selfbilling:3.0 and its profile urn:fdc:peppol.eu:2017:poacc:selfbilling:01:1.0. An invoice takes type code 389 (self-billed invoice) or 527 (self-billed debit note).
Three layers are checked in order: the UBL 2.1 Invoice schema, the EN 16931 rules and the Peppol self-billing rules, which are those of Peppol BIS Billing 3.0 without the national rules, with the self-billing identifiers and type codes.
E-invoicing in Norway: the rules in short and how to check an invoice →
Good to know
- Rules run only when the document matches the schema. Documents over 50 MB are checked against the schema only.
- The rules and the example are published by OpenPeppol; the EN 16931 rules are the CEN 1.3.16 release OpenPeppol ships with it.
Files
14 files · 2.7 MB · Download all (.zip)-
maindoc/UBL-Invoice-2.1.xsd main
-
common/UBL-CommonAggregateComponents-2.1.xsd
-
common/UBL-CommonBasicComponents-2.1.xsd
-
common/UBL-CommonExtensionComponents-2.1.xsd
-
common/UBL-QualifiedDataTypes-2.1.xsd
-
common/UBL-UnqualifiedDataTypes-2.1.xsd
-
common/UBL-ExtensionContentDataType-2.1.xsd
-
common/CCTS_CCT_SchemaModule-2.1.xsd
-
common/UBL-CommonSignatureComponents-2.1.xsd
-
common/UBL-SignatureAggregateComponents-2.1.xsd
-
common/UBL-SignatureBasicComponents-2.1.xsd
-
common/UBL-xmldsig-core-schema-2.1.xsd
-
common/UBL-XAdESv132-2.1.xsd
-
common/UBL-XAdESv141-2.1.xsd
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Business rules
Schematron · run in this orderThe rules run after the schema check, only when the document matches the schema, and in your browser like the schema check (with SaxonJS by Saxonica). Each finding names its rule, such as BR-CO-15, and the line it points at; each rule has a page with what it checks.
Example document
SB-base-example.xml · 9 KB · passes the schema and the rules
In CI and from code
The same schema by its name, peppol-bis-sb-invoice, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema peppol-bis-sb-invoice
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: peppol-bis-sb-invoice
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document=@SB-base-example.xml \
-F schema=peppol-bis-sb-invoice
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups