Keep invoice decisions with the people responsible.

Choose the level of control deliberately

Draft-only means preparing a suggested message for a person to review and handle. It does not send anything. Approval-controlled sending would require a separate dispatch step after an authorised reviewer approves the exact action. Rule-based sending would require tested eligibility rules, permissions, limits and monitoring, not just a template and a timer. These are distinct operating models; this public section does not advertise any of them as a live invoice service.

For a future pilot, start by agreeing which actions can be prepared, which need individual approval and which are excluded. A small review queue can reveal how often invoice data changes and where exceptions arise before broader automation is considered. Existing accounting-software reminders must be included in that discussion. One person's approval should not unintentionally enable a second, competing reminder sequence.

Show exactly what the reviewer is deciding

A review item should show the recipient, business sender, exact message, invoice reference, remaining balance, source version or last update, proposed time and approval requirement. Include current pauses, related replies and any previous attempt. The reviewer should be able to open the supporting invoice context without hunting through a separate inbox. A general label such as ‘reminder approved’ is not enough to show what was agreed.

Review is a decision, not a confirmation habit. The owner may approve the presented action, reject it with a reason, request a correction or take over the case. Rejection should preserve the proposed text and explanation so the next person knows what changed. A revised draft needs fresh review where required; editing after approval must not silently leave the old approval attached to new wording.

Changed facts invalidate stale approval

EX-101 illustrates why this matters. A draft might correctly show £900 remaining after the £300 applied payment. If the customer then claims to have paid the rest, the case moves to Awaiting verification. The older approved reminder should not continue merely because its scheduled time arrives. If a verified payment subsequently settles the invoice, there is no unpaid balance to chase. A changed recipient also requires fresh checks and review.

Before any future dispatch, the process would need to check that the invoice is still eligible, the balance and recipient match the reviewed action, the source is sufficiently current and permission is still valid. Approval of a message is not permanent permission to send under any circumstances. If a check fails, hold the action and give the owner a clear reason instead of treating a failed send as a completed task.

Give each exception an owner and a review date

Assign a named person to missing documents, payment checks and disputes, with a task due date that fits the work. A task deadline is an internal review date; it is not a new invoice due date or a change to the customer's terms. Record who can approve communications, correct accounting records or decide commercial questions. Those responsibilities may sit with different people, and access should reflect that difference.

For EX-102, the £650 dispute belongs with an authorised owner who can inspect the relevant work record. Another team member may gather documents without deciding the outcome. When somebody takes over, preserve the previous assignment and reason, then confirm the new owner. Tasks needing attention should remain visible rather than disappearing into a colleague's private inbox. Restrict financial information to people who need it for their role.

Make pauses and decisions explainable

A pause should show its scope, reason, owner and next review. It might apply to one disputed invoice, a customer whose contact needs correction or a wider sequence with stale source data. A pause is not settlement, and completing a related task should not automatically resume messaging. The responsible person needs to confirm that the reason has been resolved and the next action still fits.

An activity history should distinguish draft creation, editing, approval, rejection, sending, reply receipt and verified source changes. A draft is not a sent message, and an approval is not delivery confirmation. Clear records help a new owner understand the case without relying on memory. Discuss your review responsibilities, absence cover and existing approval process before a pilot; the controls should fit how your business actually makes decisions.

Explore the example