There are seven jobs in our catalog and we could have started with any of them. Month end close is bigger. Cash forecasting is more strategic. Payables touches more transactions. We started with invoice reminders, and it was not a coincidence. Accounts receivable is the most agent shaped job in finance, and understanding why tells you what to automate next.
It is unambiguous
An invoice is either paid or it is not. It is either overdue or it is not. The outcome, cash in the bank, is measurable to the cent and to the day. There is no debate about whether the agent did the job. DSO, days sales outstanding (the average number of days your customers take to pay you), went down or it did not.
Compare that to reporting, where 'good' is a matter of taste, or planning, where you will not know if the forecast was right for a year. An agent's first job should have an outcome you can put on one line.
Everyone already hates the current number
Ask a founder what their overdue receivables are and watch their face. Nobody is happy with it. Nobody thinks it is being handled well. There is no incumbent process to defend. Usually the process is 'someone remembers to send an email', so there is nothing to displace except a bad feeling.
The best first job is the one the customer is already embarrassed about.
It requires judgment, but bounded judgment
Pure rules fail at invoice reminders quickly. 'Send a reminder at day 7, 21 and 35' breaks the moment a customer replies 'we're processing it' or 'your invoice has the wrong PO number' or 'call me'. Each reply needs to be read, understood, and acted on differently. That is judgment, and it is why accounts receivable has resisted automation.
But the judgment is bounded. There are perhaps a dozen kinds of reply. The decisions are: send, wait, escalate, ask a human. A language model handles the reading and classifying well; the agent handles the sequencing; the human handles the small number of real decisions. The shape of the work fits the shape of the tools.
The blast radius is small
The worst a receivables agent can do, inside our guardrails, is send a reminder that was slightly too firm or slightly too early. That is fixed with an apology. It cannot move money, cannot write off a balance, cannot offer a discount, and cannot contact an account you have marked as sensitive. A first agent should fail softly, and invoice reminders do.
It teaches the agent your customers
This is the reason that matters most for what comes next. Running invoice reminders means learning, customer by customer, who pays when and why. That knowledge, the judgment layer, is exactly what the cash agent needs to forecast and what the close agent needs to match receipts.
- Receivables learns that your largest customer pays on day 12. Cash uses it to forecast.
- Receivables learns that a customer disputes every third invoice over a PO mismatch. Close uses it to expect the short pay.
- Receivables learns which accounts are relationship critical. Every agent respects the hold.
Start with the job that builds the most useful knowledge, and every subsequent agent starts smarter.
Where most businesses start
Most businesses start with receivables, for all of these reasons. Payables is a good second choice for the same reasons in mirror image: unambiguous, universally disliked, bounded judgment, and it teaches the agent your vendors. Close works best once receivables and payables are running, and a cash forecast is sharpest when all three are. Wherever you start, every later job is only as good as the ledger and the judgment beneath it.
Is the outcome measurable? Is the current process embarrassing? Is the judgment bounded? Is the worst case easy to undo? Does doing it teach the agent something the next job needs? Accounts receivable is five for five.