Accounts Receivable Process: The Full AR Cycle, Steps and Procedures

The accounts receivable process is the sequence a business follows to turn a credit sale into cash in the bank. It runs in eight steps: approve credit, deliver the goods or service, issue the invoice, record the receivable, follow up before the due date, chase the invoice once it is late, apply the payment, and reconcile. Most companies do the first four well and the last four badly, which is exactly why their cash arrives later than their terms say it should.

This guide walks the full AR cycle step by step, sets out the procedures that keep each stage clean, and points at the three places the process reliably breaks.

What is the accounts receivable process?

Accounts receivable is money customers owe you for goods or services you have already delivered but not yet been paid for. The accounts receivable process is everything that happens between the moment you agree to sell on credit and the moment that money is collected, applied to the right invoice and reconciled against your bank.

It sits inside a wider cycle that finance teams call order to cash, which starts earlier, at the quote or the order. The AR process is the back half: the part that begins once you have something to bill for, and only ends when the cash is in the account and the ledger agrees with the bank.

Two ideas make the rest of this easier to follow. First, a receivable is an asset, and like any asset it loses value with age; a 90 day old invoice is worth measurably less than a fresh one because the odds of collecting it drop. Second, almost every AR problem is a process problem, not a customer problem. Customers who pay late are usually responding to a process that let them.

What are the steps in the accounts receivable process?

Here is the full cycle, with the procedure each step needs and what goes wrong without it.

#	Step	The procedure that keeps it clean
1	Establish credit terms	Run a credit check, set a limit, put terms in writing before the first order
2	Deliver the goods or service	Capture proof of delivery or acceptance, since disputes start here
3	Issue the invoice	Invoice same day, to the right AP contact, with a PO number and a pay link
4	Record the receivable	Post to the ledger so the aging report is accurate from day one
5	Confirm before the due date	A short pre-due check that the invoice was received and approved
6	Chase once it is overdue	An escalating sequence: email, then SMS, then a phone call
7	Apply the payment	Match the deposit to the invoice the day it lands, not at month-end
8	Reconcile and report	Tie AR to the bank, then read the aging report and your DSO

1. Establish credit terms

Before you sell on credit, decide whether this customer should get it and how much. That means a credit application, a check against a bureau or trade references for larger accounts, a credit limit, and written terms: net 30, what happens if they pay late, who to contact. Skipping this is how a business ends up with its largest receivable sitting with its least creditworthy customer. The limit matters as much as the check, because it caps how much damage a single account can do.

2. Deliver, and capture the proof

Delivery is where disputes are born. A signed delivery note, a timestamped acceptance, a completed work order: whatever your business produces, capture it and attach it to the account. When an invoice is disputed at day 50, the argument is almost never about the amount. It is about whether the thing was delivered, when, and to whose satisfaction. Having the proof filed against the invoice turns a two week dispute into a two minute reply.

3. Issue the invoice, same day

This is the highest-leverage step in the whole process, and the most commonly fumbled. An invoice sent five days late is paid five days late; the clock does not start until it arrives. Three details decide whether an invoice gets paid on time:

• It reaches the right person. Sending to your sales contact rather than accounts payable is the single most common cause of a "we never received it" at day 45.
• It carries what AP needs to process it. PO number, correct legal entity, itemized lines, clear due date. Anything missing means it sits in someone's exception pile.
• It is easy to pay. A pay link beats making a controller hunt for wire details. Every step of friction adds days.

4. Record the receivable

Post the invoice to the ledger as it goes out, so the receivable exists in your books the moment it exists in the world. This is what makes the AR aging report trustworthy. If invoices are posted in batches days later, your aging is wrong, your DSO is wrong, and you are managing collections off a picture of last week.

5. Confirm before the due date

Most teams treat follow-up as something that starts after an invoice is late. That is a mistake. A short, friendly check a few days before the due date, confirming the invoice was received and approved for payment, catches the failures that cause most late payments: it went to the wrong inbox, it is stuck waiting on an approver, the PO number is wrong. Fixing those at day 27 costs nothing. Discovering them at day 45 costs you three weeks.

6. Chase, and escalate as it ages

Once an invoice is past due, the process needs to intensify on a schedule rather than depend on someone remembering. The pattern that works mirrors the aging buckets:

• 1 to 30 days over: a polite reminder. Most of this bucket is oversight and clears with one email.
• 31 to 60 days over: firmer, more frequent, and now asking for a specific payment date rather than a vague acknowledgment.
• 61 to 90 days over: stop emailing. The third identical email is ignored by definition. This is phone call territory, and a call is what produces a promise to pay.
• 90+ days over: final notice, payment plan, credit hold, or escalation. Debt this old is the least likely to ever be collected, so the decision itself is the priority.

The dunning sequence is the formal name for this ladder. Its effectiveness comes almost entirely from consistency, which is precisely what a busy AR team cannot supply by hand during close week.

7. Apply the payment

When money lands, match it to the right open invoice and post it. It sounds mechanical, and it is, until a customer pays six invoices with one ACH and no remittance advice, or short-pays by $340 for a credit nobody logged. Unapplied cash is worse than no cash: it keeps the invoice open, so your aging is wrong, your team chases people who already paid, and your DSO reads high for no reason. Detail on the mechanics sits in the cash application process.

8. Reconcile and report

Finally, tie your AR sub-ledger to the bank and to the general ledger, then read the numbers: the aging report for which accounts to work, DSO for how the process is trending, and the AR turnover ratio for the board pack. If reconciliation is a painful monthly event rather than a continuous background task, that is a signal that step 7 is not working.

Where does the accounts receivable process usually break?

In three specific places, and none of them are exotic:

Invoicing latency. The gap between delivering and invoicing is pure, unrecoverable delay, and it is invisible in every metric except DSO. Nobody gets blamed for invoicing on Thursday instead of Monday, so it keeps happening.

Follow-up that depends on a human having a quiet week. Collections is the first thing dropped when close, audit or a system migration lands. The invoices do not stop aging while your team is busy, and the accounts that go quietest are the ones that most need the call.

Cash application backlog. When applying cash slips, everything downstream corrupts. The aging report lies, reminders go to paid customers, and trust in the numbers goes with it.

Notice what those three have in common: they are all steps 3, 6 and 7. The AR process breaks in the middle, where the work is repetitive and relentless, not at the ends where the decisions are interesting. This is also why the mirror-image function on the buying side has been automated for years, since AP teams hit the same wall of repetitive matching and approval work and largely handed it to software that processes the invoices for them.

How do you automate the accounts receivable process?

You automate it by removing the human from steps 5, 6 and 7 while keeping them firmly in steps 1 and 8. Credit decisions and reconciliation review need judgment. Sending the fourth reminder and matching an ACH batch to six invoices do not.

In practice that means an accounts receivable automation system that sits on top of QuickBooks, Xero, NetSuite or Sage and takes over the middle of the cycle: confirming before due dates, running the full escalating chase across email, SMS and live AI phone calls, applying incoming payments to the right invoices, and keeping reconciliation continuous instead of monthly. Your team keeps the credit policy, the exceptions and the customer relationships. The process stops depending on anyone having a quiet week.

The measure of whether it worked is not activity. It is the gap between your stated terms and your actual DSO. If you sell on net 30 and collect in 46 days, the 16 day difference is what the process is costing you, and closing it is the entire point.