Give invoice questions an owner—not another reminder.

Find the question before choosing the response

A customer asking for an invoice copy may simply be missing a document. An incorrect purchase-order reference may prevent their finance team from processing it. A duplicate-invoice concern needs a comparison with the original record. An incomplete-work claim needs the person responsible for delivery. Treat these as distinct issues, and keep the customer's words available so a suggested category does not replace the actual meaning of the reply.

The first proposed action is to pause the routine sequence for the affected invoice. Record the reply, reference and received time, then identify what information is missing. Ask for clarification when the invoice cannot be identified or several invoices are mentioned. Do not send a reply containing invoice details to an unverified address merely because it appears in a new message.

Turn the reply into a specific owner task

The proposed sequence is: reply received, follow-up paused, issue classified, context collected, task assigned, owner resolves, record checked before resuming. The task should say what needs a decision, which invoice is affected, what the customer said and when the owner will review it. Attach relevant internal context without exposing unrelated financial information. A named owner and review date keep a pause from becoming an invisible backlog.

AI assistance could suggest whether a reply concerns a missing document, a payment claim or a disputed amount. The owner must be able to correct that suggestion and read the original reply. Classification is an aid to routing, not an adjudication. The proposed service does not authorise AI to waive balances, issue credits, approve new terms, settle a legal dispute or change a contract.

Worked example: EX-102 needs investigation

EX-102 has £650 remaining and is 30 days overdue as of 3 October 2026. In the illustrative branch, the customer says: ‘The work described on this invoice is not complete. Please ask the project owner to check before sending another reminder.’ The next action is not to intensify the sequence. It is to pause it and assign a task to the business's authorised project or accounts owner.

The owner task records EX-102, the customer's exact concern, the paused status and the information to review, such as the agreed scope and completion record. The £650 remains within the outstanding and overdue totals while the issue is unresolved; it is a flagged subset, not another amount. Resolution might require a document, a correction by an authorised person or an agreed response. The public example does not choose a commercial outcome for either party.

A payment claim needs verification

‘Already paid’ is useful information, but it is not the same as an applied payment in the ledger. Ask the accounts owner to check the amount, date and reference against the authorised source. Remittance advice describes a payment; it may help find it without proving that the funds have arrived or been allocated. Keep follow-up paused while checking rather than sending a contradictory message asking the customer to pay again.

For EX-101, the customer's payment claim moves the case to Awaiting verification while the remaining balance stays £900. The public demonstration settles it only when you select a clearly labelled simulated verified payment of £900. In an operational process, a confirmed source record would be required. If the payment covers only part of the balance or another invoice, the owner must resolve the allocation before the next action is agreed.

Keep promises, arrangements and settlement separate

A promise to pay is a customer statement about a future action. An instalment arrangement is a separately approved agreement with amounts, dates and responsibilities. Verified payment is money confirmed and applied to the record. Do not label any of these as another. The proposed workflow can explain what an owner should review, but it does not autonomously negotiate payment terms or grant credit. A customer request needs a human decision within the business's authority rules.

Before resuming reminders, check that the issue was actually resolved, the accounting record is current and the proposed message fits any agreed next step. Document why the pause ended. A closed task without a corrected invoice should not automatically restart contact. Discuss the questions your team receives most often and who can resolve them; that defines useful routing and controls for a future pilot.

Explore the example