← All guides · Peppol
Peppol BIS Billing 3.0 explained: the profile your Peppol invoice must fit
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
Peppol BIS Billing 3.0 is the specification a Peppol invoice must satisfy: it takes the EN 16931 core invoice model, binds it to UBL 2.1 XML, and adds Peppol-specific rules so that invoices are processable by every access point and receiving system on the network. The UBL file you download from a conversion here is described in the guided-send steps as exactly that: 'your Peppol BIS invoice, validated against the EN 16931 rules'.
What is Peppol BIS Billing 3.0?
Peppol BIS (Business Interoperability Specifications) Billing 3.0 is Peppol's invoicing profile: the EN 16931 core invoice expressed in UBL 2.1, with additional Peppol business rules for network exchange. EInvoice Translator generates UBL 2.1 invoices validated against the implemented EN 16931 core rules; the guided Peppol flow treats that validated UBL file as the Peppol BIS invoice you upload and send from your Qvalia account.
Why a profile on top of a standard?
EN 16931 deliberately leaves room: optional elements, national usage specifications (CIUS), choices a receiving system must somehow absorb. A network cannot run on 'somehow'. Peppol BIS removes the ambiguity for its own rails by fixing the choices: this syntax (UBL 2.1), these cardinalities, these code lists, these extra rules. The result is that an invoice accepted anywhere on the network is processable everywhere on it.
Think of it as the difference between a language and a form. EN 16931 is the language of European invoicing; BIS Billing is the network's form — same words, fixed boxes. When a client or a mandate says 'Peppol invoice', the form is what they mean, and it is why conversion here validates before it generates: the form forgives nothing the language might have.
The layers, once more, with feeling
Layer one, the model: EN 16931 business terms (BT-1 the invoice number, BT-27 the seller name, BT-151 a line's VAT category) and business groups. Layer two, the syntax: UBL 2.1 elements — cbc:ID, cac:InvoiceLine, cac:TaxTotal — carrying those terms. Layer three, the profile: BIS rules about which terms must appear, in what shape, for a Peppol exchange.
An invoice failure can live at any layer, and the error tells you which: a missing seller name is a model failure (BR rules); a malformed file is a syntax failure; a missing Peppol-required element is a profile failure. This product's engine implements the EN 16931 core rule layer and re-validates the generated XML — the foundation the BIS profile stands on — and the network adds its own intake checks at the access point.
What BIS discipline means for your data
The practical demands are the familiar ones, enforced without exceptions: both parties fully identified with their identifiers, lines itemised with VAT categories and rates that agree, allowances and charges in their proper fields, totals computed from the lines and reconciled. On paper-era invoices these were courtesies; in a BIS document they are schema-level facts, present or absent, valid or rejected.
Two habits cover nearly everything. First, collect identifiers at onboarding — VAT numbers, Peppol IDs — because BIS documents carry them structurally, not as footnotes. Second, never type totals: the BR-CO arithmetic is re-derivable by every system the invoice meets, and a typed total that disagrees with the lines is the profile era's most preventable rejection.
BIS and the Factur-X question
Newcomers often ask whether a Factur-X PDF is a Peppol invoice. It is not: Peppol carries the pure structured document (the UBL BIS file) through access points; Factur-X is a hybrid for document-based processes, embedding its XML in a PDF. The two share the EN 16931 core — the same invoice data — but travel by different vehicles to different intake machinery.
The conversion here equips you for both vehicles from one validated dataset: download the UBL for the Peppol route, and the Factur-X PDF for the humans and document workflows. If a client migrates from emailed PDFs to Peppol — the standard direction of travel — your process changes only in the sending step, because the invoice itself was already built to the shared core.
Reading a BIS rejection
If an access point or receiving system rejects a Peppol invoice, treat the message like a validator's: it names a rule, and the rule names a field. Fix the data at the source — in your invoice and, if the cause is structural, in your template — then regenerate and resend. Do not patch the XML by hand: a hand-edited file can pass one check while breaking the parse-back consistency that keeps the document trustworthy.
Rejection at the network edge is also, quietly, the system working. The alternative world — invoices silently misbooked, VAT treatments guessed, totals retyped — is the one mandates are abolishing. A named failure today is a same-day fix; a silent misbooking is next quarter's reconciliation. BIS's strictness is the price of invoices that need no apologies.
BIS-ready invoices in 5 steps
- Build the invoice on complete data: parties, identifiers, addresses — no field left for the network to guess.
- Give every line its own VAT category and agreeing rate; keep discounts in allowance fields, not negative lines.
- Let totals be computed from lines and pass the BR-CO checks before the file exists.
- Download the UBL XML as the Peppol payload; keep the Factur-X PDF as the human copy.
- If a send is rejected, fix the named rule in the data, regenerate, and resend — never hand-edit the XML.
Worked example: one dataset, two vehicles
A EUR 1,950.00 reverse-charge invoice — training services, category AE, tax EUR 0.00, payable EUR 1,950.00 — is converted once. The UBL file travels Peppol: uploaded in Qvalia, routed by Peppol ID, booked by the client's system against the BIS profile. The Factur-X PDF, generated from the same data with the identical XML embedded, goes to the client's project manager, who reads and approves it as a document.
One validation, one dataset, two satisfied audiences. That is the BIS profile's role in a working business: not an extra burden on the invoice, but the guarantee that its structured life and its human life never diverge.
Frequently asked questions
Is Peppol BIS the same as EN 16931?
BIS Billing 3.0 is built on EN 16931: it adopts the core model, binds it to UBL 2.1, and adds Peppol's own rules for network exchange. Complying with the core is the foundation; BIS is the network's tightening of it.
What file do I upload to send a Peppol invoice?
The UBL 2.1 XML from your conversion — the guided steps describe it as your Peppol BIS invoice, validated against the EN 16931 rules.
Can I send a Factur-X PDF over Peppol instead?
Peppol carries the structured BIS document, not the hybrid PDF. Send the UBL via Peppol and the Factur-X PDF wherever a readable document is wanted.
Who checks BIS rules — the converter or the network?
This engine validates the EN 16931 core rules and re-checks the generated XML; access points and receiving systems apply the Peppol profile checks at intake. Passing cleanly here is the preparation; the network verifies.
What is the most common BIS-era rejection cause?
Data habits from the PDF era: missing identifiers, VAT category-rate mismatches, and totals typed instead of computed. All three are caught by conversion-time validation.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- What is Peppol? The network that delivers e-invoices between businesses
- What is a UBL 2.1 invoice and when do you need one?
- What is a Peppol access point? The certified carrier behind every send
- How to send a Peppol invoice free with Qvalia: the guided step-by-step
- What is a CIUS? How countries tailor the EN 16931 core invoice