Peppol BIS Billing decides whether an invoice can travel on the Peppol network. An access point checks every document against it before sending. This guide is for developers who build or check those documents. It explains the rules that BIS adds to EN 16931 and how to read the findings when a file fails. For the difference between the document and the transport, read Peppol API integration. For the UBL syntax itself, read the UBL format overview. This guide does not repeat them.
What Peppol BIS Billing is
Peppol BIS Billing is the specification for invoices and credit notes on the Peppol network. OpenPeppol publishes it, together with the rules that check it.
- It is a CIUS of EN 16931. A CIUS (core invoice usage specification) keeps the European data model and adds its own rules. Every BIS invoice is also a valid EN 16931 invoice. Not every EN 16931 invoice is a valid BIS invoice.
- It uses the UBL syntax. An invoice is a UBL
Invoicedocument. A credit note is a UBLCreditNotedocument. - It declares itself. Every document carries the BIS CustomizationID (BT-24) and the billing ProfileID (BT-23). The CustomizationID reference shows both values.
- Other specifications build on it. Norwegian EHF and Dutch NLCIUS add national rules on top. The Peppol API page lists the specifications the API covers.
What BIS adds to EN 16931
Most BIS rules make an optional EN 16931 field mandatory or restrict a code list. These are the rules that a generic EN 16931 invoice fails most often:
| Rule | What it requires | Why the network needs it |
|---|---|---|
PEPPOL-EN16931-R001 | The business process (BT-23, cbc:ProfileID) must be present. | Receivers register the processes they accept. Routing needs it. |
PEPPOL-EN16931-R003 | A buyer reference (BT-10) or a purchase order reference (BT-13). | The buyer must be able to match the invoice to an order or a person. |
PEPPOL-EN16931-R004 | The CustomizationID must start with the BIS identifier. | It tells every system which rules apply. |
PEPPOL-EN16931-R020 and R010 | An electronic address for the seller (BT-34) and the buyer (BT-49). | These are the network addresses of the two parties. |
PEPPOL-EN16931-CL008 | The address scheme must come from the Peppol EAS list, such as 0088 or 9930. | Only these identifier types can be looked up on the network. |
PEPPOL-EN16931-P0100 and P0101 | Invoice and credit note type codes from a restricted list, such as 380 and 381. | Receivers know every code they can get. |
PEPPOL-EN16931-R008 | No empty elements anywhere in the document. | An empty element is ambiguous for the receiver. |
PEPPOL-EN16931-R051 | All amounts in the invoice currency, except the VAT total in the accounting currency. | One currency per document keeps the totals clear. |
PEPPOL-EN16931-R044 | No charges on the price of an item, only allowances. | The net price must follow from the gross price in one way. |
PEPPOL-EN16931-F001 | Dates in the format YYYY-MM-DD. | Every receiver reads the same date format. |
The rules about the electronic address fail first for most new senders. An ERP that never sent over Peppol has no field for the endpoint ID. Add both addresses to your master data before you build the first document.
How to read a Peppol rule ID
A finding from a Peppol validator carries a rule ID. The ID tells you which rulebook the rule comes from and what kind of check failed:
| ID pattern | Source | What it checks |
|---|---|---|
BR-xx, BR-CO-xx, BR-CL-xx | EN 16931 | The European core rules: required fields, sums, code lists |
PEPPOL-EN16931-Rxxx | Peppol BIS | Business rules that BIS adds |
PEPPOL-EN16931-CLxxx | Peppol BIS | Code lists that BIS restricts |
PEPPOL-EN16931-Pxxxx | Peppol BIS | Codes and VAT categories allowed in this profile |
PEPPOL-EN16931-Fxxx | Peppol BIS | Formats, such as the date format |
PEPPOL-COMMON-Rxxx | Peppol BIS | Identifier formats, such as the check digit of a GLN or the format of a national company number |
DE-R-xxx, NO-R-xxx, SE-R-xxx and others | A national rule pack | Rules of one country, inside BIS |
So BR-CO-15 means the totals do not add up, which every EN 16931 invoice must get right. PEPPOL-EN16931-R010 means the buyer has no network address, which only matters on Peppol. The reference section explains the most common rules one by one, with the fix.
National rule packs inside BIS
Peppol BIS contains rule packs for eight countries: Denmark, Germany, Greece, Iceland, Italy, the Netherlands, Norway and Sweden. Each pack applies to documents that involve its country. A document between parties in other countries is not affected.
The German pack is a good example. It applies when both the seller and the buyer are German. Its rules match the German XRechnung rules. For example, DE-R-001 requires payment instructions, just as BR-DE-1 does for XRechnung. A German supplier who invoices a French buyer over Peppol never sees these rules.
You do not choose a pack. The validator reads the country codes in the document and applies the packs that match. Your job is to put the correct country codes in the seller and buyer addresses.
The three layers a validator runs
A complete Peppol BIS check has three layers. A file must pass all three:
- The UBL schema (XSD). Is the XML well-formed, with the right elements in the right order?
- The EN 16931 rules. Are the required fields there, do the sums add up, are the codes valid?
- The Peppol BIS rules. The rules from this guide, including the national packs.
The InvoiceXML validator runs all three and labels each finding with its layer: xsd, en16931 or cius. A finding with the layer cius comes from the Peppol rules. Errors make the file invalid. Warnings are listed separately and do not change the verdict.
Create a BIS invoice with one call
POST /v1/create/ubl takes the invoice as JSON and returns a Peppol BIS UBL file. The API sets the CustomizationID and the ProfileID, calculates the totals and validates the result against all three layers. If the data cannot produce a valid document, you get HTTP 400 with the findings instead of a file.
curl -X POST https://api.invoicexml.com/v1/create/ubl \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"invoice": {
"invoiceNumber": "INV-2026-1104",
"issueDate": "2026-11-16",
"currency": "EUR",
"buyerReference": "PO-77812",
"seller": {
"name": "Northwind Supplies GmbH",
"vatIdentifier": "ATU12345678",
"electronicAddress": { "identifier": "9012345000004", "schemeId": "0088" },
"postalAddress": { "line1": "Mariahilfer Straße 10", "postCode": "1070", "city": "Wien", "country": "AT" }
},
"buyer": {
"name": "Contoso Distribution GmbH",
"vatIdentifier": "ATU87654321",
"electronicAddress": { "identifier": "9012345000011", "schemeId": "0088" },
"postalAddress": { "line1": "Herrengasse 5", "postCode": "8010", "city": "Graz", "country": "AT" }
},
"lines": [
{
"quantity": 10,
"unitCode": "H87",
"item": { "name": "Pallet wrap, 500 mm" },
"priceDetails": { "netPrice": 18.50 },
"vatInformation": { "rate": 20, "categoryCode": "S" }
}
]
}
}' \
--output invoice-ubl.xml
Three fields in this request exist only because of BIS: buyerReference for R003, and the two electronicAddress objects for R020 and R010. Both addresses are GLNs (scheme 0088), so their check digits must be correct. Both parties are Austrian, and Austria has no national pack, so only the general BIS rules apply. The UBL samples show complete BIS files for other cases.
Validate a file you already have
For a file from your ERP, from another generator or from a supplier, POST /v1/validate/ubl runs the same three layers. It reads the CustomizationID and applies the matching rule set, including the national packs.
curl -X POST https://api.invoicexml.com/v1/validate/ubl \
-H "Authorization: Bearer YOUR_API_KEY" \
-F "[email protected]"
A file without a buyer address fails like this:
{
"valid": false,
"errors": [
{
"rule": "PEPPOL-EN16931-R010",
"layer": "cius",
"line": null,
"message": "Peppol needs the buyer electronic address. Enter it together with its scheme. If the invoice is not meant for Peppol, use the EN 16931 profile instead.",
"btCodes": ["BT-49"],
"fields": ["buyer.electronicAddress"]
}
],
"warnings": []
}
Each finding names the rule, the layer, the business term and the field in the invoice JSON. Your code can show the message next to the right input field. Add the form field validationLanguage with de or fr for German or French messages. For a printable result, call /v1/validate/ubl/report to get the same check as a PDF report.
Run the check in two places. In your build, over a folder of sample invoices, so a mapping change cannot break your output unnoticed. And as the last step before you hand a file to your access point, so nothing the access point would reject leaves your system.
How rule updates work
OpenPeppol updates the BIS rules twice a year, in spring and autumn. Each release has a date from which it is mandatory on the network. Between releases, OpenPeppol may publish a small fix to a release.
The CustomizationID does not change with a release. It names the specification, not the rule version. So a file from last year and a file from today carry the same identifier, and the validator decides which rules apply by the date of the check.
The API applies each release on its mandatory date. Your code sends the same request before and after, with no library to update and nothing to redeploy. The reference page lists the rule sets in force today.
Get started
Peppol BIS Billing is EN 16931 with a set of clear additions: a business process, a buyer reference, two network addresses, restricted code lists and national packs. The API builds and checks all of it in one call. Create an account to get an API key and start a free trial. No credit card is needed. The pricing page shows what the trial includes.
Related guides:
- Peppol API integration: what your access point checks and what it does not.
- Belgium Peppol mandate: addressing Belgian buyers and the rejections they hit.
- UBL format explained: the syntax under every BIS document.
- Peppol UBL in C# .NET: the same calls from a .NET application.