Peppol check

Will the Peppol network accept this invoice?

An access point does not answer “almost”. It accepts the invoice or it refuses it, days later, for a rule nobody read — no buyer reference, no electronic address, a scheme code that was guessed. Put the invoice in here and you get the refusals now, each one named by its official rule identifier, quoted, and with the fix. Free, no account, nothing stored.

Free · no account · nothing is stored

This is a filled-in EXAMPLE: invented companies, invented amounts. It is the invoice a business really sends — and the Peppol network refuses it. Clear it and put your own invoice in.

Invoice numberIssue dateCurrency

Buyer referenceWhat your customer told you to put on the invoice, so their system can match it.Purchase order referenceOne of these two is mandatory — neither is a refusal.

You, the sender

Company nameCountryTwo letters.Peppol addressThe electronic address the network delivers to. Missing, the invoice has nowhere to go.Scheme codeFour digits saying what kind of identifier that is: 0106 a Dutch KvK number, 0208 a Belgian enterprise number.

Your customer

Invoice lines

DescriptionQuantityUnit priceVAT %

Totals

Leave these empty and the arithmetic rules are reported as not checked — never as passed.

Total without VATVAT totalTotal with VAT

What this does not prove

This checks 21 of the published Peppol BIS Billing 3.0 rules, named above by their official identifiers. The full set is far larger, and we are not the official validator: a clean result here means nothing among these rules is wrong, not that the network will accept the document. It also says nothing about whether your customer will agree with the invoice, whether the VAT treatment is correct for your situation, or whether you are registered to send on Peppol at all.

It checks 21 rules of the published Peppol BIS Billing 3.0 set, each by its official identifier, read on 2026-09-19 from https://docs.peppol.eu/poacc/billing/3.0/rules/. Every finding quotes the rule text as published, so you can check us against the source rather than take our word for it.

What it is, and what it is not

It does

Name every broken rule by its official identifier and quote the rule text, so a reader can look it up.
Catch the three that refuse most first invoices: no electronic address for either party, and neither a buyer nor a purchase order reference.
Check the scheme code against the electronic address schemes it knows — a well-formed address under the wrong scheme is delivered, to somebody else, with no error.
Add the lines up in cents and compare them with the totals you state, so a rounding difference is found here and not at the receiver.
Judge the invoice DATA, before it becomes XML — which is where a person can still fix it.

It does not

Replace the official validator, or promise acceptance. A clean result means nothing among these rules is wrong.
Pass a rule it could not check. A figure you did not supply is reported as not checked, never as fine.
Look anybody up. It makes no network call of its own and does not verify that an electronic address exists.
Send, register or file anything. Nothing leaves this page except the invoice you press the button on.
Keep your invoice. It is judged in memory and gone with the answer; what you type stays in this browser tab until you close it.

For your AI agent and for developers

An agent never has to open this page. The same check is POST https://jithox.com/api/peppol-ready/v1/check — anonymous, free, no key, nothing stored — and a GET on the same path returns the whole rule catalogue: every identifier this check covers, its published text and its fix, so a caller can see what is and is not covered before sending anything. Connect your AI · everything you can get done.