Several construction deliveries on one Peppol invoice: retain the tax-point date per line

A monthly invoice can contain concrete, rental, labour and transport delivered on different dates. Replacing those dates with one convenient invoice date makes site reconciliation harder and may hide the evidence used for the tax treatment. The structured invoice should preserve the meaning of each transaction.

Start with the current source and the right identity

The Belgian authority's specific e-invoicing FAQ addresses whether the tax-event date can be included for each delivery or service. Apply the current official answer and obtain tax advice for the actual transaction. Do not infer a rule from what one software screen happens to display.

Turn the source into one bounded decision

Identify which lines belong together, the delivery or service date, acceptance evidence, quantity, unit and tax category. Where the structured format supports a line-level reference, populate it consistently from the source record. Escalate a missing or conflicting date rather than inventing one to pass validation.

Keep evidence without automating the next step

Reconcile delivery notes and approved site records before creating the invoice. Keep the invoice date, transaction dates and payment due date as separate concepts. If a line is corrected later, preserve the original document and use the recognised correction flow with references back to the affected delivery.

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 can correct 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.