Send a Peppol invoice with Alfie after checking participant and destination

A valid invoice can still reach the wrong legal recipient when a trade name, VAT identity or Peppol participant is ambiguous. Transmission should begin only from the final invoice and verified customer record.

Start from the exact record and source

The current Alfie product page presents Alfie as a governed construction execution layer. Current application source registers send_invoice_peppol and classifies this workflow as high risk and WhatsApp confirmation. This article does not claim an external integration, autonomous outcome or roadmap capability.

Review one bounded proposal

Resolve the invoice, customer legal identity, destination and current send state. Present totals, VAT, due date and any validation errors, and block the proposal when the participant or document version is uncertain.

Keep confirmation and execution separate

Keep the confirmer and delivery result with the invoice. A Peppol send does not email a duplicate, correct the invoice, create a credit note or mark payment; each requires its own reviewed action.

Test failure and correction paths

Before daily use, test an absent identifier, two records with the same name, insufficient rights, stale source data and a temporarily unavailable service. Alfie should stop with a focused question or an unexecuted proposal. Keep the original request, chosen record, relevant source fields, user, timestamp and confirmation without copying more personal or payment data than the decision needs.

Repeat the check whenever the party, amount, scope, schedule, recipient or document version changes. An earlier answer is context rather than standing permission. Define who can correct a mistake, which dependent records must be reviewed and when the exception is genuinely closed.

Make the result readable to a colleague who did not prepare it. They should be able to reconstruct what was known, which uncertainty remained and whether an action was proposed, confirmed, executed or blocked. A free-text note can explain evidence but cannot replace identity, source, permissions or a deliberate confirmation.

Rehearse correction as carefully as success. Record how an incorrect selection is found, who may reverse or repair it and which quote, project, planning or invoice records need a follow-up check. This keeps one error bounded to its dossier instead of silently propagating it.

Connect the action to the construction record

Enfin links customers, suppliers, quotes, projects, tasks, items, cost items and invoices in one construction record. Alfie can interpret context and prepare a governed action within available permissions; a competent user confirms consequential steps. Explore Enfin, compare pricing or discuss the workflow.