Short answer: The accounts receivable process is the repeatable set of steps a business uses to turn a completed sale into cash in the bank: set credit terms, deliver, invoice, record what is owed, apply incoming payments, and chase anything late. Run well it protects both cash flow and the customer relationship. Run badly it produces disputes, surprise collection calls, and slow payment that quietly trains good customers to pay late.
Last updated: July 2026.
Accounts receivable (AR) is the money your customers owe you for goods or services they have already received. The accounts receivable process is how that money actually gets collected without wrecking the relationship in the meantime. It is easy to think of AR as a pure accounting function, but the person on the other end of every invoice and reminder is a customer, and how you handle billing is a real part of their experience. A clean, predictable AR process is one of the least glamorous and most valuable pieces of back-office customer experience there is.
What is the accounts receivable process?
The accounts receivable process is the workflow that starts the moment you agree to sell on credit and ends when the payment clears and the account is reconciled. It sits on the customer-facing side of the ledger, opposite accounts payable, which is the money you owe your suppliers. Every business that invoices rather than collecting cash at the point of sale runs some version of this process, whether it is written down or living in one person's head.
The goal is not simply to get paid. It is to get paid on time, in full, with an accurate record, and without giving the customer a reason to hesitate before buying again. That last part is what separates a mature receivables operation from a collections boiler room.
What are the steps in the accounts receivable process?
The accounts receivable process has seven core steps. Each one has an owner and a clear goal, and a breakdown at any step shows up later as slow cash or an angry customer.
| Step | What happens | Goal |
|---|---|---|
| 1. Set credit terms | Decide who gets credit, how much, and on what terms (net 30, net 60, deposit required) | Sell to customers who will actually pay, on terms you can fund |
| 2. Deliver and confirm | Fulfill the order or service and confirm the customer accepts it | Remove any excuse to dispute the invoice later |
| 3. Invoice | Send an accurate, itemized invoice with terms, due date, and payment options | Start the clock cleanly, on the first try |
| 4. Record the receivable | Log the open invoice in your ledger and aging report | Know exactly what is owed and by when |
| 5. Apply payments | Match incoming payments to the right invoices (cash application) | Close paid invoices and stop chasing money you already have |
| 6. Follow up on overdue | Send reminders and escalate politely as invoices age past due | Recover late cash without damaging the relationship |
| 7. Reconcile and report | Reconcile AR to the bank, close the period, and report on aging and DSO | Keep the books accurate and spot problems early |
The two steps teams most often skip are the first and the fifth. Skipping credit terms means you sell happily to customers who were never going to pay. Skipping disciplined cash application means payments arrive but sit unmatched, so you keep dunning customers who already paid, which is the fastest way to lose a good account over a clerical error.
The accounts receivable process flow
Zoom out and the AR process is the back half of what finance teams call order to cash: the full journey from a customer placing an order to the cash landing and being recorded. The order and fulfillment happen first; invoicing, collection, and reconciliation are the receivable half. Drawing this as a flow chart is worth the ten minutes because it exposes the handoffs where things stall, usually between sales (who set the terms) and finance (who has to collect on them).
A simple flow reads: quote and terms agreed, order fulfilled, invoice issued, invoice recorded as open AR, payment received or not. If paid, apply the payment and close. If not paid by the due date, enter the follow-up sequence: reminder, second reminder, a personal outreach, and only then a formal escalation. The healthiest flows make the paid path effortless (multiple easy payment options) and the unpaid path gradual (a series of increasingly direct but still human reminders) rather than jumping straight from silence to a collections threat.
What is the accounts receivable cycle?
The accounts receivable cycle is the same process viewed as a repeating period rather than a single invoice: the recurring monthly rhythm of issuing invoices, applying the payments that come in, aging the ones that do not, and closing the books. Most teams run this cycle monthly and measure how long, on average, it takes an invoice to convert to cash. That average is your days sales outstanding, and it is the single most useful number for judging whether the cycle is healthy. If you want the formula and industry benchmarks, see the guide to days sales outstanding and how to reduce it.
Where the accounts receivable process breaks
Most receivables problems are not collection problems. They are upstream problems that only surface as slow cash. The common failure points:
- Wrong or late invoices. An invoice with the wrong amount, a missing PO number, or the wrong contact is a built-in payment delay. The customer is not refusing to pay; they literally cannot process it. Getting the first invoice right is the cheapest speed-up available.
- No clear terms. If the due date and terms are not on the invoice and in the contract, "when are we paying this" becomes a negotiation every single time.
- Unmatched payments. Cash arrives but nobody applies it, so the aging report says overdue and the customer gets a reminder for money they already sent. This erodes trust fast.
- Reminders that read as threats. A first overdue notice that sounds like a final demand punishes your best customers for a two-day slip. Escalation should be graduated.
- No owner. When AR is "whoever has time," follow-up is inconsistent and the oldest, hardest invoices get ignored precisely because they are unpleasant.
Automating the accounts receivable process
Receivables automation is worth it because most of the AR process is rules, not judgment. Invoicing on a schedule, sending the first and second reminders, flagging invoices as they cross 30, 60, and 90 days, and matching straightforward payments are all tasks software does more reliably than a person juggling a spreadsheet. That frees your team to spend judgment where it matters: the genuinely stuck invoices, the disputes, and the relationships worth a phone call.
The highest-leverage piece to automate first is cash application, because manual matching is both tedious and error-prone. When payments land in the bank as a statement or export, you can import the payment file straight into your accounting system instead of keying each line by hand, which closes paid invoices faster and stops the false-overdue reminders that annoy good customers. Automate the reminders next, then the aging reports. Keep a human on anything that involves a dispute or a payment plan; those need a person, not a template. For the collection side specifically, a well-designed sequence of reminders matters more than the tool, which is covered in the guide to recovering failed and late payments with dunning emails.
Metrics that tell you the process is working
Three numbers tell you whether your receivables operation is healthy. Days sales outstanding measures the average time to collect. The accounts receivable turnover ratio measures how many times you collect your average receivables in a year. And the aging report breaks open invoices into buckets (current, 1 to 30 days late, 31 to 60, 61 to 90, over 90) so you can see where risk is concentrating. If DSO is climbing and the over-90 bucket is filling, the process is slipping regardless of how busy the team looks. For the broader set of operational numbers worth watching across billing and support, see how to measure customer experience operations.
What is the difference between accounts receivable and accounts payable?
Accounts receivable is money owed to you by customers; accounts payable is money you owe to suppliers. AR is an asset because it is cash you expect to collect; AP is a liability because it is cash you will have to pay out. They are mirror images of the same transaction: your accounts receivable is your customer's accounts payable. The full comparison, including which side of the balance sheet each sits on and how they connect, is in the breakdown of accounts payable vs accounts receivable.
Make getting paid part of the experience
The best receivables operations are almost invisible to the customer. Invoices are accurate and arrive on time, terms are clear, paying is easy, payments are applied the day they land, and the rare reminder is polite and correct. That is not an accounting achievement; it is a customer experience one. A customer who never has to argue about a bill, never gets dunned for money they already paid, and never has to hunt for how to pay you is a customer who buys again without friction. Treating accounts receivable as part of the experience, and not just a ledger to reconcile, is a hallmark of mature back-office customer experience operations.