Update a construction invoice due date with Alfie

A customer may receive an agreed extension after a certification delay or administrative correction. Changing the date is easy; preserving the reason and the effect on reminders is the important part. Alfie can prepare the update, while Enfin resolves the invoice, checks permission and executes the confirmed action.

Identify the exact invoice

Use the invoice number and customer name where possible. If several documents match, Alfie should request clarification. Check the current due date, open amount and document status before proposing a change.

Do not update a cancelled, credited or already settled invoice simply because its reference was mentioned in conversation.

Record the new agreement

Enter the new due date and a concise reason. Link the client message, project certification issue or internal decision when relevant. A date without context is difficult to explain later and may hide a recurring collection problem.

Keep the original due date in history. The new date is a controlled amendment, not a rewrite of what was first agreed.

Separate interpretation from authority

The current Alfie action registry includes update_invoice_due_date as a medium-risk finance action. It requires invoice-write permission. A language model can understand “give them until next Friday”, but it does not decide whether the user is allowed to change the invoice record.

Enfin supplies organisation context, permission checks and the action handler that applies the specific date.

Review downstream effects

Before confirming, check whether scheduled reminders, cash forecasts or collection tasks rely on the old date. Decide whether they should move, remain or be cancelled. Do not assume the due-date update silently repairs every dependent workflow.

The confirmation summary should show invoice, customer, old date and new date.

Follow up the amended commitment

Once confirmed, notify the relevant team and client through the appropriate process. Set a follow-up for the new date and record any partial payment separately. If the date changes repeatedly, escalate the underlying dispute instead of continuing to postpone it.

Test the guardrails before rollout

Try one ambiguous invoice reference, one invoice without an open balance and one user without invoice-write permission. The workflow should ask for clarification or refuse the action. A successful happy path is useful, but these negative cases demonstrate that voice or chat convenience does not bypass document state and authority.

Meet Alfie and its governed actions, and see how Enfin connects invoicing, projects and payment follow-up.