How to Automate Accounts Receivable: Seven Steps, Who Owns Each, and What to Automate First

Automate the collections queue and reply reading first. That is where a credit controller's day goes: deciding who to chase from an aged-debt export, writing the email, reading what comes back, and remembering who promised what. It is also where cash sits.

Leave the payment portal for later. A portal helps customers who already mean to pay; the invoices that are stuck usually have a reason. One finance lead described the work like this:

"My AR team is 3 people and they are absolutely drowning. We spend hours of emailing customers about overdue invoices, manually matching payments that came in overnight, chasing missing PO numbers, and dealing with short-pays."

r/ERP, finance lead at a $180M distributor, 2026

Every item in that list is a queue problem before it is a technology problem: nobody can see, in one place, which invoices are blocked, by what, and whose move it is. Fix that first. Cash application and portals come after.

The same seven steps work on any ERP. The owners are typical for a business with one credit controller or a small AR team.

Steps 1 to 3 are the dull ones, and they decide whether the rest works. As one commenter in the same r/ERP thread put it: "Messy data = the AI just creates a new exception queue."

Five things, read every day, read-only:

• Open items. Every unpaid invoice with its number, date, amount, currency and balance left.
• Due dates and terms. As the ERP holds them, including any changed after the invoice went out.
• Credit notes and payments. So the agent never chases an invoice that has been credited or paid since the last run.
• Contacts. The person who pays, not the person who ordered. A wrong contact is one of the commonest reasons an invoice sits.
• PO references. Many customers' AP teams cannot pay an invoice without their own PO number on it.

Read it directly, not as a weekly export or a snapshot. The top complaint about AR tools in reviews is exactly this: "the way it takes a snapshot of NetSuite invoices rather than syncing directly (in case the invoice changes)" (G2 review of YayPay, reproduced by Upflow). On Business Central we read through its API or through Microsoft Fabric; on Sage, NetSuite, Xero and QuickBooks through their APIs. More on AR automation on Business Central.

Set one cadence per customer group, not one for everyone. A starting point for 30-day terms:

Three rules sit on top. No customer gets more than one chase a week, whatever the number of invoices. A promise or a dispute stops the cadence. And every chase goes from your own mailbox. The equipment rental build runs almost exactly this: a reminder the day after due, an overdue notice at seven days, a final notice at fifteen, then escalation, with a second daily pass for missed promise dates.

Disputes are where cash sits longest. Billtrust reports that about 55% of AR professionals call dispute management their hardest task (a vendor figure). Give each kind a route and a named owner before you automate anything:

The rule that matters: nobody chases a disputed invoice until a person closes the dispute. If only part is disputed, ask for the rest at once. On a €96,400 hire invoice with €1,150 of delivery in dispute, the €95,250 nobody argued about should be paid now. The order-to-cash explainer walks through that example.

A promise to pay is a date and an amount from someone at the customer who can make it happen. "We'll look at it" is not a promise. "It's in Friday's payment run" is. Log each one against the invoice as a follow-up on the promised date plus two working days, for the bank to clear.

Track the promise kept rate: promises paid in full by the follow-up date, divided by promises that fell due. A customer below about 50% is telling you something, and their next promise should not stop the chase for as long. A broken promise moves the account up the queue at once. In the insurance services build, broken promises surface automatically after seven days instead of whenever someone remembers.

Escalate on rules, not on who shouts loudest. Score every customer each day on balance and days overdue together, so a large invoice at 60 days outranks a small one at 90. Then set tiers:

1. Tier 1, credit controller. Routine chasing on the cadence.
2. Tier 2, account owner. Over 30 days, a broken promise, or a balance over a limit you set. A call, not another email.
3. Tier 3, financial controller. Over 45 days or two broken promises. Stop supply, agree a plan, or prepare a hand-off.
4. Tier 4, agency or solicitor. A person decides. The full history of emails, replies, promises and disputes goes with it.

A US insurance services group we built for runs four tiers like this across 7,700 open invoices and $11.8M of receivables, with about $3M of the ledger at the executive tier. The collections platform case study shows the scoring.

Four numbers, read weekly against the baseline from step 1:

• DSO: (accounts receivable ÷ revenue for the period) × days in the period. On €30M of annual revenue one day is about €82,000 of cash. Work out yours with the DSO calculator.
• CEI, the collection effectiveness index: (opening receivables + credit sales − closing total receivables) ÷ (opening receivables + credit sales − closing current receivables) × 100. It shows how much of what could be collected was, and moves faster than DSO.
• Days to first chase: from due date to the first reminder. If it is more than a few days, the queue is not working.
• Promise kept rate, as above.

Add one housekeeping number: the share of overdue balance with a live next action. It should be close to 100%.

• Chasing disputed invoices. The fastest way to upset a good customer. "A lot of AR 'collections work' is fake work. The invoice is 'overdue,' so everyone treats it like a payment problem" (r/Accounting, 2026).
• Reminders from a vendor's address. Customers read them as spam; one Upflow user said so in a Software Advice review in 2020 ("my address is different: reminders@upflow.io").
• Notes only at invoice level. A Chaser user on Software Advice had to "duplicate the same note for multiple client invoices manually". Keep notes at customer level too.
• Automating sends before the data is clean. A wrong contact, sent automatically, is still a wrong contact.
• One cadence for every customer. A key account and a one-off buyer should not get the same third reminder.
• No owner for disputes. Without a named owner a dispute waits, and so does the rest of the invoice.

If you want an agent to do the drafting and reply reading, the rules for what it should do alone and what a person approves are in AI collections agents. To compare the tools that sit on top of each ERP, see the AR automation software comparison; to see what we build, the accounts receivable automation page.