First occupation of a Belgian building and Peppol: qualify the VAT transaction before invoicing

The first occupation of a building can trigger VAT questions that differ from an ordinary progress invoice for works. If the billing team copies the previous project's Peppol treatment, it may use the wrong parties, tax category or supporting explanation. The construction record therefore needs a tax qualification before anyone maps values into the structured invoice.

Start with the current source and the right identity

The Belgian authority's specific e-invoicing questions include transactions referred to in Articles 12 and 19 of the VAT Code, including disposals and first occupations. The answer must be read with the current VAT rules and the facts of the property. The FAQ is a source for scope, not a substitute for project-specific tax advice.

Turn the source into one bounded decision

Identify the building, legal owner, customer, event, occupation date, contract and VAT capacity of each party. Ask the competent adviser to qualify the transaction and document the applicable invoice obligation. Only then choose the tax code, exemption or reverse-charge wording and the structured delivery route.

Keep evidence without hiding the next step

Connect the legal decision to the building record and every resulting invoice. Preserve the source facts so that a later correction explains what changed. Do not infer the tax point from the Peppol send date, and do not reuse the qualification for another unit or party without a fresh review.

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.