A multilingual Peppol construction invoice in Belgium: separate structured data from display text

A Belgian project can involve a Dutch-speaking contractor, French-speaking client contact and English-speaking procurement team. Creating separate invoice versions for each reader can introduce different totals, references or tax descriptions. The safer design keeps one structured invoice dataset and manages display language deliberately.

Start with the current official rule

The Belgian e-invoicing FAQ explains the structured B2B requirement and the role of Peppol-BIS. The semantic fields must remain consistent regardless of the language used for readable descriptions. Check the actual recipient identifier, tax treatment and required references; language does not change the underlying transaction.

Turn the rule into a bounded decision

Choose the legally and contractually appropriate invoice language, then add translations only where they help the recipient and the format supports them. Preserve quantities, units, totals, order numbers and payment references from one source. Do not send three independently edited financial documents that look like originals.

Build an auditable workflow

Review terminology for project stages, variations and retention amounts with the team. Validate the structured file after text changes, then keep one transport reference and delivery status. A human-readable PDF can accompany the invoice when appropriate, but it must not diverge from the structured record.

Handle exceptions explicitly

Test the workflow with a realistic exception: a missing company identifier, duplicate record, unclear role or temporarily unavailable source. The process should stop with a focused question. Keep the source, review date, owner and decision without copying more personal data than needed. Escalate legal, tax, labour or safety uncertainty to the competent person.

Repeat the check when a payment, party, invoice action, site arrangement or official instruction changes. An earlier result is context, not automatic permission for the next action. Define who can reverse an error, notify affected people and decide that the exception is genuinely closed.

Make the status readable to someone who did not prepare the record. That person should find the checked input, consulted source, remaining uncertainty and next permitted action. Avoid relying on a free-text note as the only evidence. Use stable fields for identity, date, outcome and owner, then add only the explanation needed for the exception.

Connect context to controlled execution

Enfin can connect the customer, supplier, project, document, task and invoice in one record. Alfie can prepare information and propose a governed action within available permissions; the official service and competent owner remain responsible for the decision. Explore Enfin, review pricing, or discuss your workflow.