Files provided
- Invoice
- INV-2041
- Due date
- 1 September 2026
- Payment status
- Needs confirmation
Reminder draft
Our records show invoice INV-2041 was due on 1 September. Could you confirm its current status?
For finance to check
Match the ledger with the latest receipts and correspondence before using the draft.
Prepare an invoice reminder for review
An invoice reminder needs more than an overdue date. The reviewer needs to know whether a payment arrived, a credit note was issued, the amount is disputed or someone agreed an extension. A first test can use a ledger download and available messages to prepare a draft and show the records used.
Select the invoice
Use the agreed date and status rules on a current ledger extract.
Check the context
Match the customer, balance, payment history, dispute status and available reminder thread.
Prepare a draft
Reference the invoice and request the appropriate next step; flag uncertain or conflicting information.
Review before sending
The credit controller checks the current account position and decides whether to send, edit or hold.
For example, a reminder might say: 'Our records show invoice INV-2041 was due on 1 September. Could you confirm its current status?' Someone still needs to check for a recent payment. An old file can produce a well-written reminder for an invoice that is already settled.
Budget approval with the context attached
Omni can bring a purchase request, quote, budget reference and earlier approvals to the right reviewer. It should flag anything missing. When comparing quotes, check quantities, tax, delivery terms and what each supplier will provide; similar totals do not mean the offers are the same.
- Show the original request and the version being reviewed.
- Identify the supporting documents and when they were last updated.
- Separate calculated totals from explanations generated by a model.
- Record an unresolved question as a question, not an automatic rejection.
- Keep financial authority with the people designated by your organisation.
Measure preparation, review and operating effort
Judge the whole task, including time to prepare, check and correct the draft. Count mistakes and tasks completed. Include service charges, hosting, connections and staff support when you compare cost. A faster first draft is useful only if it does not take longer to fix.
Agree the run information finance needs to inspect. This can include source references, draft version, reviewer decision and the outcome of any approved action. The reporting method and retention policy are part of the implementation scope; a live console is not assumed.
Start with ERP and ledger exports
Begin with representative records from the accounting system: invoice identifiers, dates, balances, customer references and status fields. Confirm the meaning of each status with finance. A blank field may mean unknown rather than unpaid, and a single customer may have several billing entities.
We assess exports or available connections before building. Update frequency, read permissions and any system write-back must be confirmed for the actual account. The existing ledger remains the financial source of record. The implementation guide explains the steps.
Keep preparation and authorisation separate
| Activity | Who decides |
|---|---|
| Identify an invoice for review | Use finance-approved rules and show incomplete records. |
| Draft a reminder | The credit controller checks the latest payment and correspondence. |
| Prepare a spend-request package | The designated budget owner reviews the supporting evidence. |
| Send, update or commit | Only through an explicitly scoped and tested action path, with the required authority. |
Include disputed invoices, duplicate requests and changed balances in testing. Approval should refer to a specific output, and a retry should not repeat an external action. See security and governance for the access and control questions to settle.
Questions finance leaders ask
Can we start without sending reminders?
Yes. Prepare drafts and compare them with the credit controller's work. Sending can stay manual; adding it later requires a separate check of recipients, permissions, approval and retry behaviour.
What if our ledger and email do not match?
Show the mismatch to a person. Customer details and invoice numbers must match reliably before Omni uses messages about the account.
Will this reduce overdue debt?
That needs to be measured in your business. First check whether drafts are accurate and take less work to prepare and review. Payments also depend on disputes, customer behaviour and your wider process.
Where should sensitive records be processed?
State the requirement before sharing them. Hosting, model providers, storage, logs and support access are reviewed for the proposed implementation.
Talk through your taskDescribe how reminders or spend requests move through your team today.