Peppol self-billing software tolerance until 30 June 2026: keep the construction invoice controlled

A contractor may have agreed that a customer prepares invoices on its behalf, while one party's software still cannot send or receive the structured self-billing message. Treating that technical gap as permission to improvise indefinitely creates duplicate invoices and unclear acceptance. The temporary Belgian tolerance needs a bounded fallback and a clear return to the normal structured route.

Start with the current source and the right identity

The Belgian authority's B2B e-invoicing FAQ states that flexibility for technically unavailable structured self-billing runs until 30 June 2026 when the business can show that its software provider is implementing the function. It also says automatic processing itself is not a legal obligation. Recheck the official answer before relying on the end date.

Turn the source into one bounded decision

Confirm the self-billing agreement, both legal entities, the invoice issuer, the unavailable function and the software provider's implementation evidence. Choose one secure alternative format and delivery method for the temporary period. Do not let the customer and subcontractor each issue a document for the same approved work.

Keep evidence without hiding the next step

Link the approved site quantities, alternative invoice, delivery evidence and acceptance to one project record. Mark why the fallback was used and who will retest structured exchange. Before 30 June, schedule a controlled Peppol test and define the cutover date; do not resend earlier fallback invoices retroactively unless the competent adviser identifies a separate correction need.

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.