Belgian Peppol software can be notified, but it is not government-approved

What the source actually says

FPS Finance states that listing an application is not a content assessment, quality evaluation, certification or government recommendation; suppliers may use notified, not approved or acknowledged. This page does not turn that source into an automatic conclusion; it translates the verified boundary into a construction workflow that can still stop on uncertainty.

The practical value comes from applying the boundary consistently to every relevant person, document and project rather than remembering it only when an exception appears.

Data to capture before action

The primary source makes several boundaries explicit: 1. the published list helps end users find applications; 2. listing is based on information submitted and checked for irregularities or ambiguity; 3. the list is not exhaustive; 4. government logos and approval language are not allowed. Keep the official page with the operational rule so a later reviewer can see which wording and date supported the decision.

Record both the source value and the normalised value used by the workflow. Preserve later corrections as additions so the original evidence remains understandable.

A usable decision route

Turn the rule into a repeatable sequence: 1. verify sending and receiving of EN 16931 structured invoices; 2. test Peppol-first behaviour and invoice responses; 3. review project references, attachments and exception handling; 4. document the vendor claim and the evidence behind it. Give every step an owner, a timestamp and the relevant project or counterparty, rather than storing only the final status.

Before any external message, payment, status change or import, show the affected entity, amounts, dates and consequences. Require a fresh confirmation when those inputs change.

Where the workflow can fail

The most important failures appear when context or timing is lost: 1. equating notification with certification; 2. selecting on a logo rather than a workflow test; 3. assuming every listed product processes incoming data structurally. Use a visible exception state instead of guessing. A blocked item should explain what evidence is missing and who can resolve it.

Test at least one normal case, one ambiguous case and one late correction. The safe outcome for missing evidence is a question or escalation, not a confident default.

Control and ownership

Assign one authorised owner, keep the source, date, inputs and decision in one record, and send exceptions to a qualified adviser. Software can structure evidence, but it does not replace legal, tax or employment advice.

Review the procedure when the official source, contract, channel or product capability changes. Track prevented errors as well as speed so governance produces visible value.

Official or primary guidance: Official or primary guidance.

Explore Enfin, review pricing, or discuss your workflow.