Accounts receivable automation: collections, cash application and what stays human

Accounts receivable automation uses software to run the repeatable steps between sending an invoice and applying the cash: reminders, remittance matching, dispute routing and status reporting. An agent can chase and match. People keep the decisions that put a relationship or money at risk, such as credit holds and write-offs.

Follow one invoice and the split is easy to see. The table traces it from the day it goes out, and the sections after it take each step in turn.

#One invoice, start to finish

#Billing comes first

Collections problems often start on the invoice. A missing PO number or a line the customer doesn't recognize adds days to the payment, and nobody sees the delay until the due date passes.

Billing automation means building the invoice from source data (the signed order, the contract schedule, approved timesheets) and checking it before it goes out. The check matters more than the generation. Confirm the PO number the customer demands is on it and the amount matches the contract rate. Confirm it is going to the contact who actually pays. A rule can run all of that in milliseconds. We usually add these checks first, because they remove disputes before they start.

Recurring invoices need the same care. An auto-recurring invoice that keeps billing after a contract ends creates a credit note and an awkward call. Tie recurrence to the contract end date.

#Reminders that sound like your company

Many overdue invoices aren't disputed. They're sitting in a customer's approval queue or got lost in an inbox. A friendly reminder with the invoice attached clears many of them.

A sensible schedule runs in stages: a short note before the due date, a polite reminder a few days after, a firmer message with a named contact, then a phone call from a person. The timing, tone and stopping rules are yours to set, and they should differ by customer. A new customer on net 30 and a ten-year account that always pays on day 45 shouldn't get the same sequence.

An agent can draft each message from the invoice data and the history ("this is the second reminder; they replied on the 12th promising payment by the 20th"). For key accounts we'd have the account manager see the draft first. Never let an agent threaten legal action or late fees on its own. Late-payment terms are contractual, and in some countries they are set by law: UK businesses, for example, can charge statutory interest of 8% plus the Bank of England base rate on late commercial payments unless the contract sets something else, according to GOV.UK (opens in a new tab). Applying it is a commercial call, so a person decides.

Our use case for chasing overdue invoices shows the pattern in more detail.

#Cash application is the hard part

Applying cash means matching incoming money to the invoices it pays. When customers pay one invoice with one transfer and quote the invoice number, it takes no effort. It rarely stays that simple.

An agent handles the first row well, because reading a remittance PDF and tying each line to an open invoice is a document task. We also like it for the "no reference" case, strictly as a suggestion. Applying a payment to the wrong invoice does damage: the customer gets a dunning email for something they paid, and your DSO report shifts.

Set a rule for unapplied cash. Anything unmatched after two business days goes to a named person, and the age of unapplied cash is reported weekly. Our use case for applying incoming payments to open invoices walks through the flow.

#Disputes and deductions

When a customer disputes an invoice, the clock matters. Each week the dispute sits, the invoice ages and the reminders keep firing unless you pause them.

An agent can read the customer's reply, tag the reason (pricing, quantity, delivery, duplicate, missing PO), attach the order, delivery note and invoice, and send the case to the owner: sales for pricing, operations for delivery, billing for a clerical error. It should also pause the dunning sequence for that invoice. A person then decides whether to credit, re-invoice or hold the line.

Track disputes by reason. If "wrong price" is your top reason, the fix lives in how quotes become contracts, and no collections tool will repair that.

#What stays human

Some decisions shouldn't be delegated, even partly:

• Putting a customer on credit hold. It stops their orders, and sales will have a view.
• Agreeing a payment plan or a settlement.
• Writing off a balance. Approval limits for write-offs should sit in a written policy, and every write-off should name who approved it.
• Contacting a customer you know is in financial difficulty.
• Anything where the customer has complained about the company, not just the invoice.

Key point: Let the agent read, match and draft. A named person makes every decision that changes what a customer owes or whether they can keep buying.

#Measuring receivables

DSO, or days sales outstanding, is the number everyone tracks, and it is useful as a trend. It is also noisy. A few large invoices or a change in payment terms can move it with no change in collections performance.

Add a few measures that show cause:

• Percentage of receivables past due, by age bucket (1 to 30 days, 31 to 60, and so on).
• Age of unapplied cash.
• Dispute count and average days to resolve, by reason.
• Share of payments applied without a human touch.
• Promise-to-pay kept rate.

Measure these before you automate. Without a baseline you can't tell whether the project helped.

#Where it connects to your ERP

AR automation sits in front of your ERP and writes back to it: posting payments against invoices and creating credit memos. In NetSuite, for example, that means working with customer payments and credit memo records, applied to open invoices. Our NetSuite integration page covers what we connect to. Whatever your system, attach the remittance to the payment record and log who approved any manual allocation.

For the wider process behind this, including orders, credit checks and fulfillment, read our order to cash process guide.

#When it isn't worth it

If you invoice twenty customers and know them all by name, a spreadsheet with an owner and a weekly review will probably serve you better than software. Automation pays off when you have many invoices, many payers, remittances in messy formats or a team stuck on cash application every month-end.

If that sounds like your finance team, talk to us. We'll look at a sample of your invoices and remittances and tell you which steps are worth automating.

#Frequently asked questions

#What is accounts receivable automation?

It's the use of software to handle the repeatable steps of getting paid: building and checking invoices, sending reminders, matching payments to invoices, routing disputes and reporting. People still decide credit holds, payment plans and write-offs.

#What is cash application automation?

It matches incoming payments to open invoices without manual keying. It reads the remittance advice, ties each line to an invoice, posts the payment to the ERP and flags anything unclear, such as short pays or missing references, for a person.

#Can AI send collection emails on its own?

It can draft them and, for routine reminders under rules you set, send them. We recommend a human review for key accounts and for any message that mentions fees, legal action or a payment plan.

#How does automation affect DSO?

It can lower DSO when the delay starts on your side: errors on invoices, slow cash application, disputes that sit. The effect depends on why your customers pay late. If the cause is slow approvals on their side or poor terms, reminders alone won't change much.

#Do we need to replace our ERP or billing system?

No. Automation reads from and writes to the systems you already use. Your ledger and customer records stay where they are.