Send a construction invoice email with Alfie after checking recipient and attachment

Emailing an invoice is an external action that deserves a final review. The current Alfie action exists on web and WhatsApp, and the WhatsApp route requires confirmation. That confirmation should show the exact invoice, recipient and attachment rather than a vague instruction such as “send the latest one.”

Resolve the invoice before composing the email

Check the invoice number, customer, project, status and amount. Make sure it is the intended document and not a draft, cancelled invoice or earlier version. If two projects have similar names, use the customer and invoice number to disambiguate.

Do not infer that email is the legally sufficient delivery method for every transaction. Belgian structured-invoicing rules may require Peppol for the relevant B2B invoice. Email can still have a different role, such as sending a readable copy, depending on the transaction and process.

Verify the recipient from trusted customer data

Use a reviewed billing contact, not an address copied from an unverified message. Check whether the customer asked for a central accounts address, a project contact or both. Avoid exposing one customer's invoice to another party through autocomplete or an old thread.

If the recipient is missing or ambiguous, stop. Creating or updating customer details is a separate governed action and should not happen invisibly as part of sending an invoice.

Inspect the attachment and message together

Open the attachment and compare invoice number, customer and total with the action preview. Keep the email concise and avoid adding unsupported claims about payment status or contractual acceptance. Include a project reference only when it belongs to this invoice.

For an invoice subject to Belgian Peppol rules, check the official delivery requirement before treating email as the primary channel. A readable PDF copy does not automatically replace the structured invoice.

Record the outcome without overstating it

After confirmation, verify that the action reports execution against the expected invoice and recipient. An email sent event does not prove delivery, acceptance or payment. Keep follow-up states separate.

Alfie is Enfin's governed construction execution layer. A language model can interpret a request; Enfin supplies organisation context, permissions and the verified send action. The user remains responsible for the selected target and external effect.

Define a stop condition

Do not send when the billing contact is uncertain, the attachment cannot be opened, the invoice status is unclear or the transaction should first follow a structured channel. Record the reason and assign it. A visible stop protects the customer relationship better than an automatic retry. When the issue is resolved, repeat the recipient and attachment check rather than relying on the earlier preview.

See how Enfin connects construction administration, review pricing, or discuss your workflow with us.