Peppol

Your customer cannot be reached on Peppol: what happens to the invoice?

10 March 2026Updated on 29 September 20262 min readCleero

You want to send an invoice, but your software cannot find the customer on Peppol or returns an error. Investigate the cause. This does not immediately prove that the customer has no obligations or that you have nothing further to do.

Step 1: check the recipient and legal scope

Compare the enterprise number, name and legal entity with your customer details. Check support for the correct document type. The Peppol ID guide explains the lookup.

Also establish whether the invoice falls under Belgium’s B2B requirement. A consumer, a foreign business without a Belgian fixed establishment or an excluded transaction may be a different case. Missing registration is not itself a legal exception.

Step 2: establish what is technically missing

Contact the customer and your software supplier. Is the cause a wrong number, incomplete registration or a receiving failure? Retain the error, time and response. This gives you a practical record of the cause and your actions.

Also ask whether a third party can receive in the customer’s name and on their behalf. The official fallback measure concerns technical inability to receive directly or through such a third party.

Step 3: use fallback in the appropriate circumstances

Where the recipient cannot receive an electronic invoice for technical reasons, FPS Finance accepts another form under the fallback measure, such as paper or PDF. The supplier’s obligation to issue an invoice remains. The recipient must take steps without delay to enable receiving.

This is not a general option to bypass Peppol because email is more convenient. An automatic PDF feature does not demonstrate that the legal conditions are met either. Have unclear cases assessed.

Agree a safe alternative; electronic issue requires the customer’s consent. According to the general official FAQ, an invoice correctly issued using this fallback does not need to be resent retrospectively in structured form once the customer is ready.

Step 4: prevent duplicate processing

If you subsequently send through Peppol, agree which version the customer should process. Keep the invoice number and document history together. The official FAQ on duplicates emphasises that an invoice must not be booked or reported twice.

When changing software, use the switching checklist to check your own receiving setup too.

Frequently asked questions

Can I always send a PDF if Peppol fails?

No. Official fallback concerns technical inability to receive directly or through a third party. The invoice duty remains and the recipient must enable receiving without delay.

Does a missing search result mean the customer is exempt?

No. Check identity, document type, registration and legal scope first. A missing result does not establish an exception.

Should I watch for duplicates after sending again through Peppol?

Yes. Agree how the documents are processed and retain their history to prevent the same invoice being booked twice.

Tags:Peppolunreachable customerfallback