Belgian Peppol technical-means fines: document readiness before the EUR 1,500, 3,000 and 5,000 steps

A failed invoice and a business that lacks the required technical means are not automatically the same offence. A contractor needs evidence of sending and receiving readiness, but should not turn headline fine amounts into an automatic penalty prediction. The administration establishes an infringement in its legal context and different invoice failures can fall under different provisions.

Start with the current source and the right identity

The official Belgian specific e-invoicing FAQ lists a separate non-proportional fine for lacking technical means: EUR 1,500 for a first offence, EUR 3,000 for a second and EUR 5,000 for following offences. It explains that a later infringement counts only when established no earlier than three months after the previous one. Existing invoice penalties also remain relevant.

Turn the source into one bounded decision

Inventory the software, legal entities, Peppol access, incoming route, outgoing route and responsible people. Distinguish a temporary message rejection from an absence of capability. If readiness is uncertain, record the exact failing test and corrective owner instead of marking the company compliant from a vendor logo or a single successful PDF email.

Keep evidence without hiding the next step

Keep dated send and receive tests, participant identity, acknowledgements, errors and remediation together. Map each supplier and customer exception to the same readiness register. A tax adviser should assess any alleged infringement or fine; the operational file should provide facts and dates, not make a legal conclusion.

Test exceptions before making the workflow routine

Test at least a missing company number, an ambiguous party, a duplicate and a temporarily unavailable source. The workflow should stop with a focused question and name an owner. Keep the source, review date, input, outcome and confirmation without copying more personal data than needed. Escalate tax, legal, labour or safety uncertainty to the competent person.

Repeat the check when the amount, party, invoice action, site, schedule or official instruction changes. An earlier result is useful context, not automatic permission. Define who corrects an error, who informs affected people and when the exception is genuinely closed.

Make the status readable to a colleague who did not prepare the file. They should see what was checked, what remains uncertain and which next action is allowed or blocked. Use stable fields for identity, date, source and decision; a free-text note can explain the evidence but should not be the only evidence.

Connect the record to controlled execution

Enfin can connect the customer, supplier, quote, project, task, document and invoice in one record. Alfie can prepare information and propose an action within available permissions; an authorised user confirms consequential actions. Explore Enfin, compare pricing or discuss your workflow.