UBLExplain

Check common Peppol BIS invoice issues

Quick browser-based checks for Peppol BIS Billing 3.0: CustomizationID, ProfileID, endpoint IDs, currency, TaxTotal and attachments.

Paste or load UBL XML

This is not official Peppol network validation. Use official validator or access point validation for final compliance.

Rīki

UBL validators un kļūdu skaidrotājs

Atrodiet trūkstošos laukus, strukturālas problēmas un Peppol problēmas ar vienkāršiem skaidrojumiem.

UBL skatītājs

Parāda UBL XML rēķinu kā lasāmu kopsavilkumu.

Iegultā PDF pārbaudītājs

Pārbauda, vai rēķinam ir derīgs iegultais PDF pielikums.

UBL kopsummu pārbaudītājs

Pārbauda rindu, nodokļu un maksājamās summas pret LegalMonetaryTotal.

UBL PVN pārbaudītājs

Salīdzina deklarēto un aprēķināto PVN pa kategorijām.

UBL lauku skaidrotājs

Meklējiet UBL laukus un lasiet, ko nozīmē katrs XML ceļš.

Frequently asked questions

›Is this official Peppol validation?

No. This is a helper that runs in your browser. Use an official Peppol validator or your access point for final compliance checks.

›What does Peppol BIS Billing 3.0 require?

At minimum: a Peppol CustomizationID and ProfileID, supplier and customer EndpointIDs, a DocumentCurrencyCode, a structured TaxTotal with per-category TaxSubtotal, and complete LegalMonetaryTotal amounts in the document currency.

What this tool does

The Peppol BIS Billing checker focuses specifically on the Peppol BIS Billing 3.0 profile and flags issues that are valid UBL but invalid Peppol.

Common UBL and Peppol problems it detects

  • CustomizationID or ProfileID not set to the Peppol BIS Billing 3.0 values.
  • Missing or invalid EndpointID schemes for buyer or seller.
  • Allowance and charge totals not declared at the document level.
  • Tax categories not mapped to the EN 16931 UNCL5305 codes.

Why this matters

Peppol access points apply strict EN 16931 business rules on top of UBL. An invoice that passes a plain UBL validator can still fail Peppol BIS Billing 3.0.

Example: missing EndpointID scheme

AccountingSupplierParty/Party/EndpointID must carry a schemeID attribute such as 0088 (GLN) or 0192 (Norwegian organisation number). Missing schemeID is a frequent Peppol rejection.

How to fix the issue

  1. Set CustomizationID to urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0.
  2. Set ProfileID to urn:fdc:peppol.eu:2017:poacc:billing:01:1.0.
  3. Always include schemeID on EndpointID using a Peppol-approved code list.
  4. Re-run the Peppol BIS checker after each fix.

Frequently asked questions

›Is this official Peppol certification?

No. Run the Peppol checker as a development aid. Submit to your access point for final certification.

›Which Peppol profiles are covered?

Peppol BIS Billing 3.0 (urn:fdc:peppol.eu:2017:poacc:billing:01:1.0), plus basic recognition of NLCIUS, XRechnung and SI-UBL profiles.