Office workflows
What an invoice follow-up needs to know
A balance, a recent reply and the last thing we sent can point to three different next steps.
An open invoice is a reason to look. Before I send anything, I want to know what the customer last heard from me, whether they already replied, and what QuickBooks says about the balance today. Those facts used to live in different windows.
Put the facts in one place
For a collection review, I want the invoice number, the current balance, and a short history of contact. If I mailed a copy, that belongs in the history alongside an email. If the customer said they mailed a check, I want to see that before I send another reminder.
This is where exact identifiers earn their keep. Two invoices for the same customer can have different histories. A thread that names both needs a closer look before it becomes evidence for either one.
Give the draft a clear job
A draft should do the next thing the evidence supports. Sometimes that's attaching the invoice again. Sometimes it's answering a question. Sometimes the right next step is waiting for a payment to post. When the facts are incomplete, I'd rather see what needs checking than open a polished draft built on a guess.
The language model is useful once those facts are in front of it. A few plain sentences in the existing conversation are usually enough. I can review them against the invoice and the thread in the same sitting.
Keep a record of what happened
When I follow up, I want to see that attempt on the next review. Otherwise the next run is back where I started, guessing from the inbox and asking the same questions. A reliable follow-up process needs a way to record a mailed copy, an email or a decision to wait.
The measure for me is simple. When I sit down tomorrow, can I tell what happened yesterday and what needs my attention now?