The accounts receivable process explained: from invoice to cash
The accounts receivable process is the cycle from issuing an invoice to collecting and applying the cash. Here is each step, where teams lose time, and how AI changes it.
The accounts receivable process is the cycle a business runs from issuing an invoice to collecting the cash and recording it against the right account. It covers invoicing, payment reminders, collections, cash application, dispute resolution, and reconciliation. Done well, it keeps cash moving in on time. Done badly, it traps working capital in unpaid invoices and ties up the finance team in follow-up.
Most teams know the steps. What they underestimate is how much of the work is repetitive, how easily a handoff between steps stalls, and how much cash leaks while invoices sit in an aging bucket nobody touched this week. This is a look at the full process, where the hours and the cash go, and how agentic AI now does the parts people used to grind through by hand.
What the accounts receivable process actually covers
The AR process starts before an invoice goes out and ends after the cash is reconciled. It usually breaks into these stages.
- Credit and terms. Deciding whether to extend credit, setting a limit, and agreeing payment terms before the sale.
- Invoicing. Generating an accurate invoice and delivering it through the channel the customer accepts, including portals that require a manual upload.
- Payment reminders. Nudging the customer before and after the due date so the invoice does not quietly go past due.
- Collections. Following up on overdue invoices, escalating tone as they age, and negotiating where a customer cannot pay in full.
- Cash application. Matching incoming payments to open invoices, including partial payments and remittances that arrive separately from the funds.
- Dispute and deduction handling. Investigating why a customer short-paid or withheld, and resolving it to closure.
- Reconciliation and reporting. Tying the subledger to the general ledger and keeping DSO, aging, and the forecast current.
Each stage feeds the next. A late invoice delays the reminder. A misapplied payment makes a collector chase a bill that was already paid. The process is only as fast as its slowest handoff.
The end-to-end AR workflow step by step
Walk a single invoice through the cycle and the work becomes concrete.
- The customer is approved for credit and net 30 terms.
- The order ships and the system generates an invoice for $12,000.
- The invoice goes to the customer's AP portal. The clock starts.
- Three days before the due date, a reminder goes out.
- The due date passes with no payment. A first overdue notice follows.
- At day 40 the customer pays $9,000 and notes a $3,000 deduction for a damaged shipment.
- The $9,000 is applied to the invoice. The $3,000 deduction is logged and routed for investigation.
- The deduction is validated as a genuine claim. A credit memo clears the balance.
- The invoice is closed, the cash is reconciled to the GL, and the aging report updates.
Nine steps for one invoice. Multiply that across a ledger of thousands and the volume is the real problem, not the difficulty of any single action.
The workflow also splits into a pre-due-date half and a post-due-date half, and they call for different work. Before the due date the job is gentle, scheduled reminders that keep the invoice top of mind. After it, the job becomes active collection: following up, escalating, and resolving whatever is holding the payment back. Teams that blur the two either pester customers who were always going to pay on time or go soft on accounts that need a firmer hand.
Where AR teams lose time and cash today
The process leaks in predictable places. Knowing them is half the fix.
- Manual follow-up. Reminders and collection emails get sent one at a time, so accounts slip through when the team is busy or short-staffed.
- Slow cash application. When payments are matched by hand, collectors end up chasing invoices that customers already paid, which burns goodwill and time.
- Aging that nobody works. The 60 and 90 day buckets fill up because the team firefights the loudest accounts and ignores the quiet ones drifting toward write-off.
- Disputes that stall. A deduction sits unresolved for weeks because no one owns it, and the whole invoice ages with it.
- Reconciliation crunch. Month-end becomes a scramble to tie everything out, because the matching was never kept current day to day.
The common thread is volume meeting manual effort. The work is not hard, but there is too much of it for a small team to stay on top of every account, every day.
Key AR metrics: DSO, CEI, and aging
Three numbers tell you whether the process is working.
Days sales outstanding (DSO) measures how long, on average, cash sits in receivables before you collect it.
DSO = (Accounts receivable / Total credit sales) × Number of days
If you have $600,000 in receivables on $1.8m of credit sales over 90 days, DSO is ($600,000 / $1,800,000) × 90 = 30 days. Lower is better, but read it against your terms. A 30-day DSO on net 30 terms is healthy; the same DSO on net 15 means invoices are routinely a fortnight late.
Collection effectiveness index (CEI) measures how much of what was collectible you actually collected in a period. It rewards working the whole book, not just the easy accounts, and a CEI near 100% means very little is slipping.
The aging report buckets every open invoice by how overdue it is: current, 1 to 30, 31 to 60, 61 to 90, and 90-plus. It is the worklist. Balances drifting into the older buckets are the early signal that the process is falling behind.
How agentic AI changes each stage
For most of AR's history, automation meant scheduling reminders on a fixed cadence. Agentic AI is different. An AI agent reads the state of each account, decides the next best action, and takes it across your systems, escalating only the cases that need a human call. That changes the work at every stage.
- Invoicing and reminders. The agent sends reminders tuned to each account's behavior, and pauses outreach when there is an open dispute or a promise to pay, so customers do not get chased after they have already engaged.
- Collections. It works the entire aging report continuously, not just the accounts a person had time for, so the quiet balances in the 60 and 90 day buckets get the same attention as the loud ones.
- Cash application. It matches payments to open invoices, reads remittance data, handles partial and short payments, and writes the result back, so collectors stop chasing paid bills.
- Disputes. It detects a deduction, categorizes it, gathers the context, and drives it toward resolution instead of letting it sit in a queue.
- Reporting. DSO, aging, and the forecast stay current because the underlying actions are being recorded as they happen, not reconstructed at month-end.
The point is not that the steps get faster. It is that the manual handoffs between them disappear, because the same system that read the dispute also paused the reminder and routed the case.
Building a modern AR process
A strong AR process is not a longer checklist. It is fewer manual handoffs and tighter feedback between steps. Start by mapping where invoices stall today, then put consistent, continuous effort on the two stages that consume the most hours, usually collections follow-up and cash application. Keep the ledger current so the aging report is a live worklist rather than a month-end snapshot. The foundation here is the same idea behind accounts receivable automation, and it pairs naturally with a clear plan to reduce manual data entry across the workflow.
How Rex runs the AR process end to end
Rex is an agentic AI accounts receivable agent. It works the whole process continuously: sending reminders tuned to each account, chasing every overdue invoice in the aging report, applying incoming cash to the right invoices, and resolving the disputes and short pays that would otherwise stall collections. It does this across the entire ledger at once, not just the accounts a person had time to reach this week.
The cases that genuinely need a human, like whether to extend credit to a struggling customer or how hard to push a strategic account, get escalated with the full context attached. Everything else, the volume that used to eat the team's days, just gets done. See how Rex runs the accounts receivable process from invoice to cash.
Frequently asked questions
- What are the main steps in the accounts receivable process?
- The process runs from credit approval and invoicing through payment reminders, collections, cash application, and dispute resolution, then closes with reconciliation and reporting. Each step hands off to the next, and a delay anywhere pushes out the day you get paid.
- What is the difference between the AR process and the order-to-cash process?
- Order to cash is the wider cycle that starts when a customer places an order. The accounts receivable process is the back half, from the moment you invoice through to collecting and applying the cash.
- How do you measure if your AR process is working?
- Track DSO to see how long cash sits in receivables, CEI to see how much of what was due you actually collected, and the aging report to see where balances are stuck. Read the three together, not in isolation.