Cancel an invoice or issue a credit note with Alfie after the right check

“Cancel this invoice” can mean stopping an unfinished draft, correcting an issued document, or reversing a posted amount. Those are not interchangeable events. The right route depends on the invoice state, whether it reached the customer, and whether the accounting history must remain visible. Alfie can help frame the choice, but the record and authorised user decide the action.

Establish the document state

Identify the invoice number, legal customer, issue date, amount, delivery status and any payment or reminder activity. Check whether it is still a draft, finalised but unsent, transmitted through Peppol, or already part of an accounting period. A screen label alone should not erase the event history.

Also check whether another corrective document already exists. Duplicate reversals are especially easy when customer support, finance and the project manager act from separate conversations.

Choose between cancellation and credit

Cancellation is appropriate only when the system and company process allow the invoice state to be withdrawn without misrepresenting an issued transaction. When an issued invoice must be corrected, a linked credit note commonly preserves the original and records the reversal. Partial errors may require a partial credit rather than undoing valid work.

Do not infer legal or accounting treatment from a casual phrase. Escalate unusual cases to the company's accountant and keep the reason attached to the document chain.

Review the proposed Alfie action

The preview should state the selected invoice, current state, proposed operation, credit amount when relevant, reason and resulting balance. It should warn about payments, reminders and previous corrections. Alfie interprets the request, while Enfin remains the governed execution layer. The current action catalogue defines what can be done, organisation context limits which records are visible, and a preview makes the real effect reviewable. The model does not receive independent authority to change company data. Missing or conflicting evidence should stop the flow for clarification.

The confirmation boundary matters because “explain my options” is not permission to create a credit document or change a financial status.

Preserve the customer and project trail

After the action, keep the original reference, corrective link, approver and customer communication together. Update open balances and reminders only from the resulting ledger state. If new work is invoiced later, create it from the agreed scope instead of recycling the corrected document.

See the focused Alfie credit-note confirmation workflow and Alfie in Enfin for governed financial actions.

Final control before closure. For “Cancel an invoice or issue a credit note with Alfie after the right check”, review four points together. Is the source current and attached to the correct customer, quote, invoice or project? Does the user have authority for this exact change? Are uncertain fields, conflicts and missing evidence still visible? Does the result name an owner for the next step? Record exceptions in the business file, not only in a separate conversation. Another colleague should be able to distinguish what was proposed, what was confirmed and what was deliberately left unknown. Test the flow with a wrong record, a duplicate document and a withdrawn instruction as well. A governed action should stop before execution in each case and let the user correct the proposal safely.