Accounts Receivable and Collections: A Small Business Guide

A business can be profitable on paper and still run out of cash, and the accounts receivable ledger is usually where the gap hides. Every invoice you send is a loan to your customer until it's paid. The longer it sits open, the longer that loan runs, and the less cash you have to cover payroll, rent and your own vendor bills.

Most owners notice a cash problem only after it shows up in the bank balance. By then the invoices behind it are often 60 or 90 days old, and the customer has moved on to other priorities. The fix isn't a better spreadsheet after the fact. It's a routine: clear terms up front, a weekly look at what's aging, and a follow-up sequence that starts before an invoice is even late.

This matters more for service and project-based businesses than for retail, because there's rarely a deposit or card on file forcing payment at the point of sale. The invoice is the only lever you have, so how you write it and how you chase it decides how fast you get paid.

The terms printed on the invoice set the clock. Vague terms produce vague payment behavior.

• Net 15 or net 30, not "due on receipt": a specific number of days gives the customer's AP team something concrete to schedule against.
• A stated due date on the invoice itself, not just "net 30" in small print. Most late payments aren't defiance, they're a missed line on a busy AP desk.
• An early-pay discount, commonly 1-2% for payment inside 10 days (sometimes written 2/10 net 30). It costs you a small margin and buys faster cash, which is often worth more than the discount.
• A late fee or interest clause, stated in the contract and on the invoice, so it isn't a surprise if you ever need to apply it. Whether and how much you can charge varies by state and by what your contract says, so this belongs in your engagement letter or master services agreement, not invented on the fly.
• Partial upfront payment or a deposit for new customers or large one-off projects, so you're not fully exposed on unproven relationships.
• Recurring, automatic billing (ACH or card on file) wherever the relationship is ongoing. The best collections process is the one you never have to run because payment is already automated.

Whichever terms you pick, put them in the contract, repeat them on every invoice, and don't grant exceptions quietly. A customer who talks you into net 60 once will expect it every time.

A credit policy is the set of rules that decides who gets terms, how much, and what happens if they don't pay. Without one, credit decisions get made customer by customer, under pressure, usually by whoever answers the phone.

A workable policy for a small business covers:

• Who gets terms at all. New customers pay upfront or on delivery until they've paid on time a few times; established customers earn net 30.
• A credit limit per customer, tied to how much you can afford to have outstanding to any one buyer if they went dark tomorrow.
• A basic check before large exposure. For a big new contract, a quick look at how long the company has been operating, a reference from another vendor, or a credit report from a business bureau is a cheap safeguard against a large write-off later.
• Who owns the follow-up. One person, not "whoever notices," should own the aging report and the reminder cadence. Split ownership is how invoices sit for 90 days unchased.
• A stated escalation path. At what day does a reminder become a phone call, and at what day does a phone call become a hold on further work.

Write it down, even if it's one page. The point isn't bureaucracy, it's that the same rule applies the second time a customer is late, not just the first.

The AR aging report is the single most useful tool for managing receivables, and every accounting platform (QuickBooks Online, Xero, and most invoicing tools) generates it automatically. It buckets every open invoice by how long it's been outstanding.

A standard aging report groups invoices into:

• Current: not yet due.
• 1-30 days past due: normal follow-up territory, usually a friendly nudge.
• 31-60 days past due: a real problem; this is where a phone call, not just an email, belongs.
• 61-90 days past due: escalation. Consider a hold on new work for that customer.
• 90+ days past due: high risk of never collecting. This is the bucket you review for possible write-off.

Run the aging report weekly, not monthly. A weekly cadence catches an invoice sliding from current into the 31-60 bucket while there's still a good chance of a quick, friendly resolution. By the time it's caught in a monthly close, you've lost three or four weeks of follow-up time.

Watch the shape of the report over time, not just the total. If the 61-90 and 90+ buckets are growing as a share of total AR, your collections process is losing ground even if total revenue is up.

Days sales outstanding (DSO) measures, on average, how many days it takes you to collect payment after a sale. It is the single clearest early-warning number for collections health, because it moves before the cash-flow statement does.

The standard formula:

DSO = (Ending accounts receivable / Total credit sales for the period) x Number of days in the period

A business with $600,000 in credit sales over a 90-day quarter and $60,000 in ending AR has a DSO of (60,000 / 600,000) x 90, which works out to 9 days. See the full worked example below for a second version of this same math using daily average sales instead, which some owners find easier to follow.

Compare your DSO against your own stated terms, not against a generic industry number pulled from somewhere else. If your terms are net 30 and your DSO is running at 45, something in your invoicing or follow-up process is leaking days. If DSO is climbing quarter over quarter while terms haven't changed, that's the earliest signal that collections discipline is slipping, usually before anyone notices a cash crunch.

"Dunning" is the sequence of reminders that runs from before an invoice is due through escalation if it goes unpaid. The cadence works because it's consistent and automatic, not because any single message is persuasive.

A cadence that fits most B2B small businesses, measured against the due date:

• 3 days before due: automated friendly reminder, invoice attached, no action needed if already scheduled to pay.
• Due date: automated "payment due today" notice.
• 7 days late: personal (not automated-looking) email from the account owner, polite, assumes an oversight.
• 15 days late: phone call, not just an email. Ask directly when payment will be made and get a specific date.
• 30 days late: written notice referencing the contract terms and any late fee that applies; a manager or owner, not just the AR clerk, sends it.
• 45-60 days late: hold on any new work or delivery for that customer until the balance clears.
• 90 days late: formal demand letter, and a decision point on whether to send it to a collection agency, pursue small claims, or begin write-off review.

Automate the first two steps inside your invoicing software (QuickBooks Online, Xero and most AR tools support scheduled reminders). Keep the human steps human. A form email at day 30 reads as an oversight; a phone call at day 15 reads as attention, and attention is what usually gets a stalled invoice paid.

The tone should shift with each stage: assume good faith early, get specific in the middle, get formal at the end.

Stage 1, friendly reminder (3 days before or on the due date): Subject: Invoice #1042 due [date] "Hi [Name], just a quick note that invoice #1042 for $[amount] is due on [date]. Let me know if you need anything from us to process it, otherwise no action needed. Thanks."

Stage 2, first follow-up (7-10 days late): Subject: Invoice #1042, now past due "Hi [Name], invoice #1042 for $[amount] was due on [date] and I don't see payment yet on our end. Could you let me know the status, or the date we should expect payment? Happy to resend the invoice or answer any questions about it."

Stage 3, firmer follow-up (30 days late): Subject: Invoice #1042, 30 days past due, action needed "Hi [Name], invoice #1042 for $[amount] is now 30 days past due. Per our agreement, a late fee of [X]% applies to balances over 30 days. I'd like to get this resolved this week. Can you confirm a payment date, or let me know if there's a dispute I should know about?"

Stage 4, final notice (60-90 days late): Subject: Final notice, invoice #1042 "Hi [Name], invoice #1042 for $[amount], originally due [date], remains unpaid. This is a final notice before we [pause further work / refer this to collections / pursue other remedies available under our agreement]. Please contact me by [date] to resolve this."

Keep every message factual and specific: invoice number, amount, original due date, days late. Vague reminders are easy to ignore. Specific ones are harder to.

Writing off a receivable means accepting, formally, that you don't expect to collect it, and removing it from your active AR so your books reflect reality. It should happen only after a documented process, not as a quiet decision to stop chasing an invoice.

Reasonable triggers for review:

• Multiple documented follow-up attempts (email and phone) with no response or no payment commitment kept.
• The invoice is 180+ days past due with no realistic path to payment (customer disputes it in bad faith, has gone out of business, or is unreachable).
• The customer has filed for bankruptcy or formally dissolved.
• The cost of continued collection (a collection agency's cut, legal fees, staff time) exceeds what you'd realistically recover.

The tax treatment depends on your accounting method, and this is where owners most often get it wrong. If you're a cash-basis taxpayer, you generally never recognized the income from that unpaid invoice in the first place, so there is nothing to deduct as a bad debt: the write-off is a bookkeeping cleanup, not a tax deduction. If you're an accrual-basis taxpayer, you did recognize the income when you billed it, so a business debt that becomes wholly or partially worthless can generally be deducted as an ordinary business bad debt in the year it becomes worthless, under the rules in Internal Revenue Code Section 166. Documentation matters here: keep the invoice, the collection correspondence, and the basis for concluding it's worthless. This is general information, not tax advice for your specific facts; confirm the treatment with your credentialed tax preparer before it goes on a return.

The right setup depends on invoice volume and how much time the follow-up steps are already costing you.

• DIY spreadsheet: Works below roughly 20-30 invoices a month. Cheapest option, but reminders are manual, aging is a snapshot you build by hand, and it's the first thing to slip when you're busy.
• Built-in AR tools (QuickBooks Online, Xero): Automated aging reports and scheduled reminder emails come standard. Fits most businesses once volume passes what a spreadsheet can track reliably, with no extra software cost since you're likely already paying for the platform.
• Dedicated AR software (like automated dunning or invoicing add-ons): Adds multi-channel reminders, payment portals and better reporting. Worth it once collections is a real time sink, typically past 50-100 open invoices at once.
• Outsourced AR support: A person (or team) owns the aging report, runs the cadence, and makes the phone calls, so it stops depending on whoever in the office has time that week. Fits businesses where AR has become a part-time job nobody signed up for, or where the owner is the one currently making collection calls.

Take a service business with $600,000 in annual credit sales, invoiced evenly across the year, and $60,000 in accounts receivable outstanding on any given day.

Daily credit sales = $600,000 / 365 days = about $1,644 per day.

DSO = $60,000 (ending AR) / $1,644 (average daily credit sales) = about 36.5 days.

If that business's stated terms are net 30, a DSO of 36.5 means customers are, on average, paying about a week past terms, a manageable gap that a tighter dunning cadence (starting the reminder before the due date rather than after) would likely close.

Now suppose DSO climbs to 55 over the next two quarters with terms unchanged. AR at that new DSO would sit around $1,644 x 55 = about $90,400, roughly $30,000 more cash tied up in unpaid invoices than before, cash that would otherwise be available for payroll or growth. That's the concrete cost of a slipping collections process, and it's exactly the kind of shift a weekly aging review catches early, while a quarterly or annual review catches only after the cash is already gone.

A handful of habits account for most of the slow-pay problems small businesses run into:

• Invoicing late. If the invoice goes out two weeks after the work is done, the clock on "net 30" already started later than it should have, and so did your cash.
• No specific due date on the invoice, relying on the customer to calculate it from terms buried in a contract they haven't reread since signing.
• Letting one customer set a precedent. Granting net 60 informally, once, because a good customer asked, makes it awkward to hold every other customer to net 30.
• Treating every late invoice the same. A first-time, three-days-late payment from a longtime customer needs a different tone than a repeat 60-day-late payment from someone new.
• No one clearly owns the aging report. If it's "whoever has time," it gets reviewed only when cash is already tight, which is too late to matter.