Accounts receivable automation: where cash stalls

A customer pays a $48,000 bank transfer on the 3rd. The remittance reference reads “INV 2381 + 2390 less credit.” Nobody matches it until the 9th, because the payment covers two invoices and a credit note, and matching is done by hand. On the 6th, the customer gets a reminder for an invoice they’ve paid. On the 8th, their account manager sends a renewal proposal without knowing about either.

Accounts receivable is where order-to-cash turns into cash. It covers two stages of order-to-cash: collecting what’s owed, and applying payments to the invoices they pay. Collections gets most of the attention, but a lot of the delay sits in applying the cash.

What is accounts receivable automation?

Accounts receivable (AR) is the money customers owe for what they’ve been invoiced. AR automation covers the work between sending an invoice and closing it: aging balances, sending and escalating reminders, matching incoming payments to open invoices, handling disputes, and keeping the CRM and the ledger in step. The aim is fewer days between invoice and cash, and no customer chased for money they’ve already paid.

Where collections stall

1. Aging is per invoice. Four small invoices 30 days late get four separate reminders on the same morning, to the same person.
2. Reminders never check for a reason to stop. A customer who paid yesterday, raised a dispute or is mid-renewal gets the next email anyway.
3. The account owner hears last. A firm reminder reaches a customer whose renewal is on the table, and the account manager finds out from the customer.
4. The sequence never hands off. It sends a fifth email instead of passing the account to a person with the history attached.

Where cash application stalls

1. The remittance doesn’t match the invoice. One payment covers several invoices, a credit, a short payment or a bank fee, and the reference is free text.
2. Payments arrive in more than one place. Card payments land in Stripe, transfers in the bank and checks in a lockbox, and each is matched separately.
3. Unmatched cash drops out of view. A payment that can’t be matched sits as unapplied cash, the invoice stays open, and collections keeps chasing.
4. Status never reaches the CRM. The invoice is paid in the ledger, and the account team still sees it as overdue.

What it costs

Late payment is common. It affects seven in ten North American companies, and overdue invoices average 23% of B2B receivables, according to Atradius’s 2026 Payment Practices Barometer. The leading cause is customers’ own cash flow, which no integration fixes. The part you control is the gap between a customer paying and your books saying so, and every reminder sent inside it.

Unapplied cash also distorts what finance reports. Days sales outstanding looks worse than it is, and the close waits while someone works through the unmatched list.

What to fix first

1. Age balances per customer. Keep one view of what each customer owes, and have one conversation about it.
2. Check for a reason to stop before every reminder. Paid, disputed, on a payment plan, in an active renewal, or held by the account owner. These change mid-sequence, so check before each send.
3. Tell the account owner before anything firm goes out. They may already know why the invoice is late.
4. Escalate tone and channel with age, then hand off. Send a reminder, then a firmer one, then create a call task, then pass the account to a person with the full history.
5. Bring every payment source into one matching step. Bank, card processor and lockbox payments go through the same rules.
6. Match on more than the invoice number. Use the amount, the customer and the date, allow for fees and short payments within a tolerance, and send anything uncertain to a review queue.
7. Write payment status back to the CRM. When cash is applied, the account team sees it the same day.

The guides to building collections and dunning and bank reconciliation automation have the prompts for each step.

Where AI agents fit

Remittance text is where matching rules run out. An agent can read “INV 2381 + 2390 less credit” and propose the match, sort a dispute out of a support ticket, or draft a collections email for review. Anything that changes an amount still goes to a person to approve.

Where accounts receivable fits

AR is only as clean as the invoices it collects on. If the booked order differs from the signed contract, the invoice is disputed and the payment comes in short. If account teams can’t see invoice status, nobody stops a reminder going to a customer mid-renewal. Once cash is applied, revenue recognition and the close pick up the rest.

For the wider case for automating order-to-cash, see Accelerate revenue growth with order-to-cash automation. For the whole process, from quote to close, see the order-to-cash process.

Payables run on the same ERP with the problem reversed. For supplier invoices that arrive by email and get keyed by hand, see the accounts payable process.