A Peppol summary invoice for several construction deliveries: preserve each delivery date

A supplier may want to combine a month's deliveries into one invoice. The administrative shortcut is useful only when the customer can still reconcile every line to the correct site, delivery note, quantity and date. A single invoice date must not erase the underlying transaction evidence.

Start with the current source and the right identity

The Belgian authority's specific e-invoicing FAQ addresses summary invoices and the tax-event date for deliveries or services. Use the current answer with the applicable VAT and contractual rules. Peppol transports the structured document; it does not decide whether unrelated deliveries may be combined.

Turn the source into one bounded decision

Define the grouping period, legal entities, currency, site and purchase-order rules. Keep a separate line or supported reference for each delivery where the date or acceptance matters. If a delivery is disputed, returned or belongs to another customer entity, hold it out instead of forcing the total to reconcile.

Keep evidence without automating the next step

Match each invoice line to the delivery record before approval. Validate quantities, units, tax category, price and buyer reference, then keep the source list with the invoice. When a correction is required, preserve the original and use the supported credit or replacement process rather than editing history.

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.