Accounts receivable best practices are usually written for the wrong half of the cycle. The advice starts once an invoice is overdue, by which point most of the useful options have already closed.
Whether an account ever goes past due is decided earlier, by the terms you agreed, the invoice you issued, the reminder that did or did not go out, and the cash you applied. Each of those has a control point and an owner. In a small finance function they tend to collapse onto one desk, which is where both the collection problem and the fraud risk begin.
Why Accounts Receivable Best Practices Fail After the Due Date
An overdue invoice is a symptom with several possible causes, and a collection call treats all of them the same way. The customer may never have agreed the terms you are enforcing. The invoice may be wrong, or may have arrived somewhere nobody approves invoices. The payment may already have arrived and be sitting unapplied. The balance may be disputed rather than unpaid.
None of those four is a collections problem. The first three are failures of the order-to-cash cycle, the sequence that runs from agreeing credit to applying cash, and the fourth belongs to whoever can settle the dispute. Each of the four has a control point that sits before the due date.
A collection call is the right response only to the case the list leaves out: a customer who agreed the terms, got a correct invoice, has raised no dispute, and has simply not paid. Whether to run the order-to-cash cycle yourself or hand it to a vendor is a separate decision, worked through in how to tell accounts receivable outsourcing companies apart.
Set Credit Terms and Limits in Writing, and Name Who Can Change Them
Terms that live in a salesperson's memory are not terms. Write the payment period, the due date convention, the credit limit, and what happens when the limit is reached, then record which of those the customer actually agreed to before the first invoice leaves.
Then decide who may change them. The federal internal control standards list authorization of transactions among the common categories of control activity and describe it plainly: transactions are authorized and executed only by persons acting within the scope of their authority, which the standards call the principal means of assuring that only valid transactions to exchange, transfer, use, or commit resources are initiated or entered into (GAO, Standards for Internal Control in the Federal Government, paragraph 10.04 and table 1). A credit limit anyone can raise inside the billing system is not a limit.
Loosening terms is also an accounting event before it is a collections event, because expanding credit to weaker customers feeds straight into the allowance for credit losses. What that costs, and how the buckets drive the estimate, is set out in how to read an accounts receivable aging report.
Invoice Accuracy and Time to Issue Decide the Rest of the Cycle
An invoice that goes out late, or goes out wrong, has already spent part of the payment period. Issue it when the work is finished rather than when the month closes, and check the fields that make it payable before it leaves.
Washington's accounting manual sets a minimum worth borrowing. Upon completion of transactions, invoices are to be prepared and sent to debtors, and invoices are to contain at a minimum a description of the goods or services provided, the date or dates provided, the amount of the debt, and the invoice due date (Washington State Administrative and Accounting Manual, subsection 85.54.60.a). The same subsection requires sequentially numbered billing documents and files that include a means of sequentially accounting for them. That is a completeness control rather than a filing preference, because a gap in the sequence is how a delivered job goes unbilled and how a credit memo, the document that reduces what a customer owes, leaves no trace.
Accuracy also wants a second pair of eyes before the invoice is sent. The state auditor's segregation of duties guide treats billing as a duty that can go wrong quietly, and one of its suggested controls is to periodically review invoices for accuracy before your employee mails them (Office of the Washington State Auditor, Center for Government Innovation, Segregation of Duties). A review after the customer complains is a different and much more expensive control.
Your customer has its own definition of a payable invoice, and it is usually stricter than yours. The federal version of that definition, and the clock it starts, is itemized in what an accounts payable case study has to report. Read it from the seller's side and it becomes a list of the reasons your invoice is sitting in someone's exception queue instead of their payment run.
Write the Reminder Cadence Down, With a Named Owner Per Account
A cadence that exists only as good intentions produces contact when somebody has time, which is never the week that matters. Write the schedule instead: what goes out before the due date, what goes out on it, what goes out after, and who sends each one.
Washington requires written procedures to be developed and followed so that past due receivables are followed up promptly and in a manner that is cost-effective for the overall collection program (Washington State Administrative and Accounting Manual, subsection 85.54.50.b). The same manual requires a written record to be kept, by account, on collection efforts, though it allows general system documentation to support billing and past due notices produced by automated systems (Washington State Administrative and Accounting Manual, subsection 85.54.60.e). That record, however it is produced, is what lets a second person pick the account up without repeating the first person's call.
The state's own collection guidance is blunter about ownership than most commercial advice. It separates the practices the accounting manual requires from the many it calls discretionary, and it recommends that agencies clearly define account ownership, since each receivable should be the responsibility of a specific person, establish reasonable caseloads, and, once an account is overdue, contact the debtor within 30 days of the due date (Washington Office of Financial Management, Receivable Collection Best Practices).
Read that last one as an outer bound rather than a plan. A ledger worked on the weekly rhythm set out in the bookkeeping checklist between closes reaches the account well inside it, and which of those contacts a firm keeps for itself is drawn in which accounting tasks to outsource.
A written policy does one more thing that is easy to miss. It gives you something to measure the person against, which is why the auditor's guide pairs a collection policy with periodic monitoring of whether the clerk's actions on past due accounts actually comply with it.
Apply Cash the Day It Lands, or the Aging Stops Being Evidence
Cash that has arrived but has not been matched to an invoice sits in a suspense or unapplied account, and for as long as it sits there the aging report overstates what customers owe you. Work an overstated aging and the first thing you do is make an avoidable call to a customer who already paid. What that does to the report, and to everything downstream of it, is covered in how to read an accounts receivable aging report.
The record that prevents it is dull and specific. Daily receipts applicable to receivables are to be entered in detail to a daily cash record, with detail listings supporting summary totals, and that detail is to disclose the name of the payee or account number, the amount received, the invoice number if available, the mode of payment, and the check number if applicable (Washington State Administrative and Accounting Manual, subsection 85.54.60.b). The phrase to notice is "if available". Remittance detail is the field that goes missing, and when it does somebody has to rebuild the match from the amount alone.
The fix belongs on the invoice rather than in the cash-application queue. Washington's collection guidance asks agencies to prepare and send clear and complete billing statements that include contact information and remittance information (Washington Office of Financial Management, Receivable Collection Best Practices). An invoice that tells the payer which reference to quote is the cheapest cash-application control you own.
Three kinds of arrival are worth a written rule before they happen.
- A lump payment covering several invoices with no remittance advice needs a stated order of application, usually oldest first, so the answer is not invented one payment at a time.
- A short payment needs a threshold below which it clears as a rounding difference and above which it becomes a logged deduction, meaning an amount the customer has taken off the invoice and now owes an explanation for.
- A payment from a legal entity whose name does not match the customer record needs a named person allowed to confirm the link, because guessing wrong moves cash onto the wrong account and creates two errors instead of one.
Delay here is also the cover for a specific fraud. Lapping means stealing one customer's payment and concealing it by applying a later customer's payment to the first account, and the auditor's guide names it as the risk when the person who handles cash also applies payments to customer accounts. Its suggested detection is ordinary: spot-check how payments were applied and compare the payment date to the account posting date (Office of the Washington State Auditor, Center for Government Innovation, Segregation of Duties). A backlog of unapplied cash makes that comparison meaningless, which is the second reason to clear it daily.
Log Disputes and Deductions as a Routing Problem
A short payment is not a collections event. It is a question that belongs to somebody, and the job is to get it to that person the same day with the reason attached.
Route it to one of three places.
- A price or quantity difference goes back to whoever built the invoice, because the fix is a corrected document rather than a conversation.
- A service complaint goes to the person who owns the engagement or the delivery, because the customer is disputing value and no billing clerk can settle that.
- A refusal with no stated reason goes to whoever owns the credit decision, because it is a credit event and it should change the limit before it changes the aging.
Whichever way it routes, the adjustment itself is controlled. Any adjustment increasing or decreasing a receivable is to be supported by a revised billing document, a credit memorandum, or other appropriate documentation, and written procedures are to be developed and followed so that only authorized adjustments are recorded (Washington State Administrative and Accounting Manual, subsection 85.54.60.c). The auditor's guide asks for the same thing in operational terms: supporting documentation for all customer account adjustments, and secondary authorization for adjustments, or at least for those above a set threshold.
The reason is not tidiness. An adjustment anyone can raise is how a stolen payment gets covered, because reducing what the customer appears to owe hides the fact that the money never arrived.
The timing consequence lands downstream too. A forecast that dates collections off the aged ledger and each customer's payment history, the method behind a cash flow forecast, inherits whatever the dispute log does or does not say.
Segregate Duties Over Cash and Customer Accounts
The receipts side of a small finance function collapses into one person more easily than any other process, and the auditor's guide describes the failure in one sentence: when the same person takes in a customer's cash payment, writes out the deposit ticket, walks it to the bank and balances the bank statement at month's end, the opportunities for undetected error, fraud or theft increase (Office of the Washington State Auditor, Center for Government Innovation, Segregation of Duties).
The guide's worked example splits receipts four ways, and the four labels are worth keeping because they survive translation to any size of business. Custody is the person who receives the cash and check payments. Recording is the person who maintains the general ledger and controls how revenue is recorded. Reconciliation is a third person who ties the daily deposit back to the supporting system records to confirm it was made intact and on time. Authorization is a fourth who approves any reversal of a customer payment.
For the receivables seat specifically, one boundary matters more than the rest. An employee who handles customer accounts and collections should not also have custody of cash or checks, including acting as a backup cashier, handling deposits, or having access to mailed payments. That combination is what makes lapping possible, along with over-posting, where someone who can mark customer accounts as paid records more payments than actually arrived, and the concealment of a theft behind a write-off. The guide's table for that seat also asks for periodic review of account write-offs, credits or refunds for reasonableness, validity and the presence of supporting documentation, beyond the secondary approval already covered above.
A small firm cannot staff four roles, and pretending otherwise is worse than admitting it. The honest answer is to name the compensating control and actually run it. The manual requires that, prior to or promptly after a write-off occurs, the write-off is subject to management review, and that any account determined to have been inappropriately written off is returned to the accounting records by reversing the write-off entries (Washington State Administrative and Accounting Manual, subsection 85.54.55.d). A review that cannot reverse anything is a reading exercise. The equivalent split on the payables side, including what to write into a job description so the boundary survives the next hire, is worked through in an accounts payable job description and the duties that cannot share it.
One monitoring habit ties the whole section together. Watching the aging report for changes is listed among the compensating controls against lapping, since concealing one theft with a later payment leaves more accounts showing past due. The report you already produce is a fraud detector as well as a worklist, but only if somebody compares it to last month's.
How DSO Is Computed, and What a Move in It Should Force
Days sales outstanding (DSO) estimates how long a sale takes to turn into cash. Two firms can both report it and mean different things, which is why the formula has to travel with the number and why a provider's reporting pack has to name it.
The common method divides the receivable balance at the end of a period by credit sales for that period, then multiplies by the number of days in the period. A countback method instead works backwards from the balance, subtracting each recent month's sales in turn until the balance is used up, and counts the days consumed. The first is stable and easy to audit, and it distorts when sales are seasonal because it spreads a spike across the whole period. The second tracks a seasonal book more closely and is harder to reproduce. Neither is wrong. Comparing one against the other is.
Treat a move in DSO as a routing question rather than a verdict. If it rose while the aging buckets barely moved, look at cash application and unbilled work before anyone calls a customer. If it rose because one large account slipped, that is a credit and relationship question. If it rose across the whole book, the terms or the invoice timing changed.
DSO is also not the number the allowance is built from. That estimate is typically built off past due status bucket by bucket, which is a different reading of the same ledger, and DSO sits on top of it as a management summary. Metrics for the firm itself are a different set again, and they sit in accounting firm KPIs.
Where to Start
Pull the aging and the unapplied cash balance on the same day and read them together. If unapplied cash is material, the aging is not yet evidence, and neither is any call you were about to make from it. If the aging is clean and the balances are still old, work backwards through the cycle: were the terms agreed, was the invoice right and on time, did the reminder go out, was the dispute routed to someone who could settle it.
Then write down who owns each step, by name, and mark every place where the same name appears twice. A receivables problem in a small function is often not an effort problem. It is unassigned work and unsplit duties, and the fix is a schedule with names on it rather than more chasing.
Accountably places trained offshore accountants and tax preparers inside US CPA and EA firms, ramped on your software and SOPs in about 3 to 4 weeks. Since 2022 that is 20+ US firms and 30+ placements. Don't trust us. Test us. Run the Free 40-Hour Proof Pilot on a real block of your own receivables work and let your reviewer grade the output before it touches a client ledger.