Accounts receivable collection process: the step-by-step sequence that gets invoices paid

The accounts receivable collection process is the fixed sequence a business runs on every invoice, from the moment it is issued to the moment it is either paid, placed with an agency, or written off. A working process has five stages: invoice and confirm receipt, remind before the due date, follow up on a schedule after it, escalate the contact and put the claim in writing, then decide whether to sue, place or write off. Most companies have the first stage and improvise the rest, and that is where the money goes.

The reason to formalize it is arithmetic rather than tidiness. Invoices still inside 90 days past due are typically recovered at rates above 70 percent. Once an invoice passes 180 days, recovery commonly falls below 15 percent. Nothing about the customer changes across those months. What changes is whether anyone followed up on schedule.

What is the AR collection process?

It is the operational half of accounts receivable. The other half, order to invoice, is about getting a correct bill to the right person. Collection is everything after that: confirming the invoice landed, reminding before it is due, chasing when it is not paid, escalating when reminders stop working, and deciding what to do with what is left.

Two things distinguish a real process from a habit. The first is that it is triggered by dates rather than by someone noticing. The second is that it is written down, so the person covering vacation runs the same sequence as the person who owns it. If your answer to "what happens on day 45" depends on who you ask, you have a habit.

Accounts receivable collection process steps

Step 1: invoice cleanly and confirm it arrived (day 0 to 3)

A surprising share of what looks like non-payment is an invoice sitting in the wrong inbox, missing a purchase order number, or addressed to somebody who left. Before you build an escalation ladder, fix the boring things: invoice the same day the work completes, send it to a named person and the AP address, include the PO or reference the customer's system requires, and state the due date as a date rather than as terms.

Terms themselves are worth being precise about. Net 30 means 30 calendar days from the invoice date unless your contract says otherwise, with day one being the day after the invoice date. Because month lengths vary, the due date rarely lands on the same calendar date each month, which is exactly the kind of ambiguity that produces a two week argument. Our guide to net 30 payment terms covers the wording that removes it.

Step 2: remind before the invoice is due (day -5 to 0)

The single highest-return message in the whole sequence is a short courtesy note a few days before the due date. It is not a collection message and should not read like one. It confirms the invoice is in their system, confirms the amount, and gives them a chance to raise a problem while there is still time to pay on time.

This one email moves a meaningful share of invoices from "late" to "on time" for a reason that has nothing to do with willingness. Most AP departments pay in batches on a cycle. Landing in the right batch is often the whole game.

Step 3: follow up on a fixed schedule (day 1 to 30 past due)

Set the cadence once and apply it to every account. A workable default is a first follow-up within a week of the due date, a second around day fifteen, and a statement of account rather than another invoice copy around day thirty. Change the tone across those three, not the facts.

Ask for something specific every time. "Please advise" invites nothing. "Can you confirm the invoice is approved for payment and the date it will be released?" gets either a date or an objection, and both are useful. Log whatever comes back.

Step 4: escalate the person and put it in writing (day 30 to 60)

When AP has gone quiet, the problem is usually not AP. Move to the person who ordered the work, then to their manager. They have a commercial relationship with you and an internal route to get an invoice released that an AP clerk does not.

Around day 60, put the claim in writing formally: the invoice numbers, the amount, the contract provision you rely on, and what happens next. That document matters later. It is what makes an escalation credible, and in several states presenting the claim is a precondition to recovering attorney fees if you end up suing.

Step 5: decide, and actually decide (day 60 to 120)

The failure mode here is drift. An account nobody has decided about is an account quietly aging into the sub-15-percent band. At this point pick one of four:

• Payment plan. Best where the customer is solvent but cash constrained and you want to keep them. Get it in writing with dates and amounts.
• Legal action. Worth it where the customer can pay and is choosing not to. Small claims limits vary by state, and many states let a business file for amounts well into five figures.
• Place with an agency. Sensible on genuinely stuck accounts, at a real cost: commercial contingency runs 25 to 50 percent of what is recovered, with the worst rates on the smallest claims, and most agencies will not take a balance under $500 to $1,000. See how much collection agencies charge.
• Write it off. The IRS treats a debt as worthless when there is no reasonable expectation of repayment, and it is deductible only in the year it becomes worthless. Note that a cash-method taxpayer generally cannot deduct an unpaid invoice at all, because the income was never recognized.

Who should own the accounts receivable collection process?

One named person, with a defined escalation path to sales or account management. Splitting collection across whoever invoiced is the most common structural reason follow-up stops: everyone assumes someone else sent the reminder.

The awkward part is the relationship. Sales usually resists chasing, because they own the account and do not want the conversation. That instinct is worth respecting up to about day 45 and worth overriding after it. The compromise that works is that scheduled reminders go out automatically from finance regardless of what anyone feels, and sales gets involved only in the escalation conversations where the relationship genuinely matters.

What metrics tell you the process is working?

Three, and only one of them is a collections metric in the obvious sense.

Days sales outstanding is the headline: the average time from invoice to cash. It reacts to process changes within a quarter, which makes it a decent feedback loop. We cover the levers in how to reduce DSO.

The aging profile matters more than the total. A hundred thousand dollars of receivables sitting mostly in the 0 to 30 bucket is a healthy business; the same total sitting in 90-plus is a problem the total does not show. Build the report and read it monthly, as described in the accounts receivable aging report.

Percentage of invoices contacted on schedule. This is the leading indicator, and almost nobody tracks it. DSO and aging tell you what already happened. This tells you whether the process ran at all, which is the thing you can still fix.

How do you automate the accounts receivable collection process?

Automate the parts driven by dates and leave the parts driven by judgment to a person. The date-driven parts are the pre-due reminder, the day 7, 15 and 30 follow-ups, the statement of account, and the escalation trigger that flags an account for human attention. The judgment parts are the disputes, the payment plan negotiations, and the decision at day 90.

Cash application is worth a mention because it quietly breaks otherwise good processes. If a customer pays three invoices in one lump sum with no remittance advice, and nobody matches the payment to the invoices, your system keeps chasing invoices that are already paid. That is the fastest way to lose credibility with a customer who did the right thing. Where remittance detail is thin, pulling the raw transactions from the bank statement into a spreadsheet and matching on amount and date is usually quicker than asking the customer to reconstruct what they paid.

The broader point is that this is a consistency problem, not a skill problem. Collections goes wrong because the third reminder did not go out during a busy week, not because someone chose the wrong sentence. That is why first-party collections software tends to beat both a manual process and an early agency placement across the 0 to 120 day window: it runs the same sequence on all 400 invoices, in your own name, whether or not anyone remembers. The wider workflow it sits inside is covered under accounts receivable automation.

Getting started without rebuilding everything

You do not need a project. Write down what should happen on day -3, 7, 15, 30 and 60. Pick the person who owns it. Send the pre-due reminder on every invoice for one month and watch what happens to the 0 to 30 bucket. Then automate the parts that turned out to be purely mechanical.

The businesses that collect well are rarely the ones with the best letters. They are the ones where the second and third follow-up reliably happen, on accounts nobody is thinking about, in a month when everyone is busy.