Issued
The approved invoice exists with the correct entity, scope, amount, currency, due terms, and internal owner.
Invoice follow-up field guide
Fix the handoff from sent to settled.
An invoice can be correct and still disappear between delivery, acknowledgement, questions, disputes, promised payment, provider settlement, and reconciliation. This guide maps one invoice follow-up workflow without sending messages, accessing accounts, or treating an open balance as revenue.
The finish line is not “reminder sent” or “customer said paid.” Use a provider-confirmed settled transaction, reduced by confirmed refunds, then reconcile it to the correct invoice and business record.
Separate the states people often collapse.
A safe workflow distinguishes commercial approval, invoice creation, verified delivery, acknowledgement, open questions, dispute, promised payment, processing, settlement, refund, and reconciliation. Combining them into “open” or “paid” makes ownership and evidence disappear.
Delivered
The approved channel reports a successful destination event. A generated email or queued message is not delivery evidence.
Actionable
No dispute, wrong contact, missing document, duplicate, legal hold, or other exception blocks normal follow-up.
Settled and reconciled
The payment provider confirms settlement and the transaction is matched to the invoice; confirmed refunds remain visible and reduce gross.
The seven-stage invoice follow-up map.
Trace one real invoice from approval to reconciliation. At every stage, name the owner, allowed action, required evidence, exception route, and stop condition.
01
Approved invoice
Confirm entity, recipient, scope, amount, USD currency, due terms, and the current invoice version.
- Who approved the invoice?
- Which version is authoritative?
02
Verified delivery
Send through an approved channel and record the destination system's delivery evidence when available.
- Was the recipient correct?
- What proves the handoff?
03
Owner and next date
Assign one accountable role and one visible decision date, not an endless timer.
- Who checks context first?
- Who is the fallback?
04
Eligibility check
Exclude settled, refunded, disputed, duplicated, cancelled, wrong-contact, opted-out, legally restricted, and already-answered cases.
- What stops contact?
- Who resolves ambiguity?
05
Permitted next action
Choose a truthful reminder, question, call task, intentional wait, or human escalation using current context and an approved channel.
- Is contact permitted now?
- Does the action avoid pressure?
06
Reply and exception route
Stop routine automation on replies and route disputes, price or scope questions, hardship, complaints, legal issues, and sensitive cases to an authorized person.
- Who may make a commitment?
- What suspends reminders?
07
Settlement and reconciliation
Confirm settled provider evidence, match the invoice and amount, subtract confirmed refunds, and close only the reconciled state.
- What is the provider record?
- Does the ledger match?
Use evidence that matches the claim.
Different evidence supports different statements. Keep the source and timestamp visible internally, minimize retained personal information, and never make a stronger claim than the source proves.
| Claim | Useful evidence | What it does not prove |
|---|---|---|
| Invoice exists | Approved invoice record and current version. | Delivery, acceptance, payment, or settlement. |
| Invoice was delivered | Destination-system delivery event or acknowledged receipt. | That the invoice is correct, accepted, or paid. |
| Payment is processing | Provider processing state tied to the expected transaction. | Settlement or available funds. |
| Payment settled | Direct provider-confirmed settled record. | That it was matched to the correct invoice or remains unrefunded. |
| Revenue reconciled | Settled record matched to the invoice and ledger, less confirmed refunds. | Profit, future revenue, or a business outcome caused by automation. |
A screenshot, message, invoice status label, hash, click, promise, or model-generated success statement is not provider-confirmed settlement evidence.
Measure the workflow without inventing financial impact.
Time to verified delivery
Approved invoice timestamp to destination delivery evidence.
Time to first exception
Delivery timestamp to the first question, dispute, wrong-contact signal, or missing-item finding.
Open actionable count
Invoices eligible for the next permitted action after exclusions and context checks.
Exception age
Time a dispute or blocked case remains without a named decision owner.
Time to settlement
Verified delivery timestamp to direct provider-confirmed settlement.
Refund-adjusted settled total
Provider-confirmed settled USD less provider-confirmed refunds in the same reporting boundary.
These measures describe operations. They do not prove automation caused faster payment, higher revenue, lower cost, or any other commercial result without a valid baseline and comparable evidence.
A 15-minute control audit.
- Write the exact invoice approval, delivery, settlement, refund, and reconciliation events.
- Name one owner for the normal queue and one authorized exception owner.
- Confirm the correct entity, recipient, amount, USD currency, terms, and invoice version.
- Define which source proves delivery and which provider proves settlement.
- Exclude settled, refunded, disputed, cancelled, duplicate, wrong-contact, opted-out, restricted, and already-answered cases.
- Use one permitted purpose, one useful next action, and a finite stop condition.
- Stop routine automation on every reply and route material questions to a person.
- Keep passwords, payment credentials, identity records, banking instructions, and unrelated personal data out of ordinary follow-up.
- Reconcile provider-confirmed settlement and confirmed refunds before reporting revenue.
Safe automation prepares, checks, routes, and reconciles. It does not harass, impersonate, threaten, or make financial commitments.
Keep human authority for disputes, hardship, complaints, legal issues, collections decisions, price or scope changes, payment instructions, refunds, write-offs, and any exception the system cannot verify. Follow applicable laws, contracts, opt-outs, quiet hours, and channel rules.
Invoice follow-up workflow questions.
When should an invoice follow-up happen?
Use the agreed terms, verified delivery date, prior conversation, current status, approved channel, and business policy. There is no universal timer that overrides a dispute, wrong contact, opt-out, legal restriction, or other stop signal.
Can AI send invoice reminders automatically?
AI may prepare a draft from controlled facts after eligibility and context checks. A person or approved policy must still determine whether contact is permitted, verify every claim, stop on replies, and retain authority for disputes, commitments, payment instructions, refunds, write-offs, and sensitive cases.
When should an invoice count as revenue?
For the ARIIA operating ledger, only provider-confirmed settled USD is counted and confirmed refunds are subtracted. An issued invoice, due balance, processing transaction, screenshot, message, or hash alone is not verified revenue.
Does this guide replace legal, tax, accounting, or collections advice?
No. It is an operations-design guide. Use qualified advice for legal, tax, accounting, collections, insolvency, consumer-protection, and jurisdiction-specific requirements.
What does the paid ARIIA audit cover?
The separate USD $497 AI Operations Audit covers one agreed workflow, its as-is handoff map, one priority blueprint, measures, and a 30-day action plan. Implementation is separate, scope and timing are confirmed before payment, and no payment-speed, savings, or revenue outcome is guaranteed.
Put one invoice handoff on a visible operating board.
The free tracker has 100 editable rows, formulas, dropdowns, stop signals, and separate provider-settlement and refund fields. It sends no messages, moves no money, and requires no account or email gate. The local calculator submits none of its three assumptions and does not predict faster payment, savings, or ROI.
Original educational guide, templates, and workbook, not legal, tax, accounting, or collections advice; not a client result, testimonial, case study, recovery or savings claim, or revenue promise.