Written by: Andrew Cohen, CFA, CPA, Managing Partner, Condesa Financial Group | Last updated: October 17, 2026

Key Takeaways For SME AR Teams

• Most SME AR functions fail because invoices are late or inaccurate, disputes sit in the general queue, cash is never matched to invoices, and no one reviews the aging report weekly.
• Effective AR relies on a documented credit policy, invoicing on delivery, a seven-stage collections cadence, separate dispute triage, daily cash application, and segregation of duties that reduces fraud risk.
• Track core AR metrics weekly and trend them monthly to spot problems early and protect cash flow.
• Automation handles mechanical tasks well, while humans handle disputes, credit decisions, write-offs, and escalation calls with decision-makers.
• Condesa Financial rebuilds broken AR functions for SMEs using ex-Big 4 professionals and a fractional CFO to install credit policy, invoicing discipline, collections cadence, dispute triage, cash application, KPIs, and internal controls.

Get A Free AR Assessment

Accounts Receivable Best Practices In Order-To-Cash Sequence

The following numbered list presents accounts receivable best practices in order-to-cash sequence. Each practice has a named owner and a definition of what good looks like.

1. Credit Policy And Customer Onboarding. Owner: finance or controller. Good: every customer has a documented credit limit, written payment terms, and a defined hold trigger before the first invoice is issued.
2. Invoicing Accuracy And Timing. Owner: AR specialist or billing coordinator. Good: invoices go out on delivery, contain the correct PO number, tax treatment, and due date, and are reviewed before transmission.
3. Documented Collections Cadence. Owner: AR specialist, escalating to controller and then management. Good: every overdue invoice follows a written schedule of contacts with defined channels, tones, and escalation triggers at each stage.
4. Dispute And Short-Payment Triage. Owner: named dispute owner outside the general collections queue. Good: every dispute is logged, assigned, and tracked to resolution within a defined SLA, with automated reminders paused on the disputed portion.
5. Cash Application. Owner: AR operations, reconciled by controller. Good: receipts are matched to invoices daily, unapplied cash is cleared within 48 hours, and the AR subledger agrees to the general ledger at month-end.
6. AR KPIs. Owner: controller or fractional CFO. Good: core AR metrics are reviewed weekly and trended monthly to guide decisions.
7. Internal Controls And Segregation Of Duties. Owner: controller or fractional CFO. Good: credit approval, cash receipt, write-off authorization, and reconciliation sit with separate individuals or receive independent review.

Credit Policy And Customer Onboarding Standards

As the first practice in the sequence, credit policy is the entry point of the order-to-cash cycle. Before a customer is invoiced, finance, not sales, should approve a credit limit based on documented criteria: a credit report, trade references, financial statements where available, and the customer's payment history. The credit limit should be system-enforced, and changes to it should be logged and require authorization independent of sales.

Payment terms should be set in writing at onboarding and captured in the customer record. The SME-specific failure is terms set verbally by sales and never documented, so collections has nothing to enforce when an invoice goes past due. Serrala's June 2026 credit and collections guide recommends risk-tiered credit limit review cadences: high-risk accounts reviewed quarterly, mid-tier accounts semi-annually, and low-risk accounts annually with passive monitoring.

Define a credit hold trigger in the policy, for example, any invoice more than 30 days past due or any account exceeding its credit limit, and apply it consistently. Because releasing a hold effectively extends credit, that authority should rest with finance, not sales. A credit limit that anyone can raise inside the billing system is not a real limit; the authority to change credit terms and limits should be explicitly assigned and restricted.

For a deeper treatment of AR management practices, see How To Apply Accounts Receivable Management Best Practices.

Invoicing Accuracy And Timing Discipline

Once credit terms are set, invoicing becomes the next critical step and it is the most common root cause of late payment. Invoice errors, such as a wrong PO number, missing cost center, or incorrect quantity, send an invoice straight into the customer's dispute queue, so the seller chases payment while the buyer waits for a corrected document and DSO keeps accruing. Pricing errors are the root cause of 35% of invoice disputes at the industry average, with missing or incorrect purchase order numbers a second major cause, a class of dispute that can be eliminated by capturing PO numbers at contract signing rather than at invoicing.

A clean invoice contains the correct customer legal name and billing address, a unique sequential invoice number, the PO number or contract reference, a description of goods or services delivered, the delivery date, the amount, applicable tax treatment, the due date, payment instructions including remittance address or ACH details, and a named contact for billing queries. A second person should review the invoice before transmission for any invoice above a defined threshold.

Timing matters as much as accuracy. Businesses that send invoices the same day as service delivery have DSO averaging 12 days lower than those that batch invoices weekly. The discipline of invoicing on delivery rather than at month-end is the single highest-leverage invoicing practice for SMEs. The AR specialist or billing coordinator owns this step and should trigger invoicing on the same day as delivery or a project milestone. Success means zero invoices held for batch processing and every invoice reviewed before transmission.

Accounts Receivable Collections: A Documented Cadence

A documented collections cadence converts ad hoc chasing into a repeatable sequence applied consistently to every invoice. Businesses that follow up on 100% of their overdue invoices are 76% more likely to be paid within a week than those that do not, making consistent follow-up the single highest-leverage action in collections. 31% of businesses leave some invoices unchased every month.

The table below presents a seven-stage cadence for net-30 payment terms. Adjust intervals for longer terms or high-risk accounts.

The 90-Day Escalation Ladder: Collections Agency Versus Write-Off. At 90 days past due, the decision is a policy call made in advance, not a judgment call made under pressure. The probability of collecting an account drops to roughly 68.9% at 90 days past due, 51.3% at six months, and 21.4% at one year. The criteria for each path:

• Refer To A Collections Agency when the balance is material, the customer has not responded to the final demand, no dispute is open, and the customer relationship has no strategic value worth preserving. For B2B commercial claims, most collection agencies decline accounts below roughly $2,500, and claims under $1,500 are typically better handled internally or in small claims court, though some sources note agency economics can become competitive up to around $5,000. Collection agencies typically charge contingency fees of 25–30% of recovered amounts for standard (90–180 day) commercial debt, with overall ranges of 15–40% depending on debt age and complexity. The 25–40% bracket applies to older or disputed accounts, so the economics must be weighed against the balance.
• Write Off As Bad Debt when the customer has filed for bankruptcy, the balance is below the cost of further pursuit, legal action is not cost-effective, or the account has been with a collections agency without recovery. A write-off recognizes collection is unlikely but does not erase the customer's obligation; any later payment requires reversing the write-off entry and recording the cash. Write-offs require documented collection efforts and approval independent of the person who applied the cash.

AR Collections: Fix The Process, Get Paid Faster covers the collections process in greater depth.

Dispute And Short-Payment Triage Workflow

A disputed invoice is a separate workflow from a late invoice. A disputed invoice is waiting on a decision rather than on a payment, so aging it alongside ordinary receivables misstates both the collections picture and the resolution problem. Treating disputes as collections events by sending the same dunning sequence to a customer who has flagged a billing error escalates a disagreement into a relationship problem and produces more emails and fewer payments.

Every dispute should be logged at the point of receipt with a unique case ID, the disputed amount, the uncontested balance, the invoice and PO references, the customer's stated reason, a reason code such as pricing, quantity, tax, delivery, duplicate charge, or missing document, a named owner, and a target resolution date. Assigning a department rather than a person is the most common reason disputes age, because departments have no calendar and no accountability for an individual case.

A practical dispute SLA is to acknowledge within 24 hours, investigate routine issues within 48–72 hours, agree a remedy within three to seven days, and close or escalate within seven to 14 days. Automated collection reminders should be paused on the disputed portion immediately upon logging. The undisputed balance continues through the standard cadence.

Ownership follows the dispute type. Finance may not be able to fix a shipment issue and sales may not be able to correct tax coding, so AR owns intake and customer communication, billing owns invoice-accuracy issues, operations owns shipment and proof-of-delivery issues, and sales or account management provides commercial context when the customer relationship requires it.

Short payments follow the same triage logic. Identify the exact amount deducted, compare it with the invoice and supporting documents, classify the reason, and route it to the function able to validate or approve the adjustment. Once a dispute is resolved, restart collections promptly on any remaining balance rather than waiting for the next scheduled cycle. Dispute data is one of the richest sources of AR process improvement: if many disputes relate to purchase orders, the order setup process may need attention; if pricing disputes are common, contract data may not be flowing correctly into billing.

Cash Application And Unapplied Cash Control

Cash application is the process of matching incoming customer payments to the correct open invoices and posting those receipts to the AR subledger and general ledger. A payment has not completed the AR process merely because cash reached the bank. Until it is applied, the invoice still shows as outstanding, DSO is overstated, and collectors may chase customers who have already paid.

The standard operating model is that receipts are matched to invoices daily from remittance information. When remittance arrives separately from funds, which is common with ACH and wire payments, the AR team should request it from the customer's AP contact with a deadline rather than waiting. Invoices should tell customers exactly which invoice number, account ID, and remittance address to use, because clear instructions upstream prevent exceptions downstream.

Unapplied cash, a received payment not yet allocated to specific invoices, should be tracked as a named, owned, aged queue rather than a suspense account. Unapplied cash inflates DSO artificially and corrupts the AR aging report. It also overstates the allowance for doubtful accounts, triggers dunning to customers who have already paid, and causes credit holds to fire against accounts that are actually current, which blocks legitimate orders. Every payment that stays unmatched for more than 48 hours should be assigned to a named owner with a clear resolution deadline. The unapplied cash subledger should be reconciled against bank accounts on a documented schedule, and unapplied cash should be reviewed weekly to identify recurring process problems before they compound.

Short payments in cash application are a disposition decision rather than a matching failure. Code the variance by reason such as dispute, rebate, credit note, damage claim, or settlement discount, and route it to the owner who can resolve that category. AR operations own matching, and the controller owns reconciliation to the GL. What good looks like is zero items in unapplied cash older than 48 hours and an AR subledger that agrees to the GL at month-end.

For month-end reconciliation procedures, see How To Reconcile Accounts Receivable At Month-End.

AR KPIs An SME Should Track

The table below presents the core AR KPI set with formulas and what each metric signals. For a full treatment, see Accounts Receivable KPIs: The Essential Metrics Guide and How To Reduce Accounts Receivable Days: A Guide For SMEs.

DSO Worked Example. A business with $90,000 in average accounts receivable and $540,000 in credit sales over a 90-day quarter has a DSO of ($90,000 ÷ $540,000) × 90 = 15 days. If average receivables rise to $150,000 with sales unchanged, DSO rises to ($150,000 ÷ $540,000) × 90 = 25 days. This 10-day deterioration is worth approximately $27,400 in tied-up working capital on $1 million in annual revenue.

Internal Controls And Segregation Of Duties

Internal controls are the section of accounts receivable management that automation vendors rarely describe, and they are where SME AR functions are most exposed. The foundational principle is to separate authorization, custody, recordkeeping, and reconciliation so that no single person controls all four for the same transaction.

Four control points require separation in AR:

• Credit Approval. Approved by finance or controller, independent of sales. Limits are system-enforced, and changes are logged and authorized.
• Cash Receipt. The person who receives and deposits customer payments should not also apply those payments to customer accounts. An employee with access to customer payments generally should not also have the ability to post credits or write off the related receivable without independent approval. This combination enables lapping, which conceals a stolen payment by applying a later customer's payment to the first account.
• Write-Off Authorization. Write-offs should require documented collection efforts, approval independent of sales and cash application, and CFO approval above a specified threshold; written-off accounts should remain on a watch list for later receipts.
• Reconciliation. The AR subledger should be reconciled to the general ledger monthly by someone independent of cash application. Bank deposits should be reconciled to cash-application batches. Unapplied cash should be aged and escalated at 30 days.

For SMEs where full separation is impractical, compensating controls are required. An owner or outsourced controller may independently review the completed bank reconciliation and related bank activity where the bookkeeper also performs the reconciliation. The practical test asks whether one employee could both initiate an improper transaction and conceal it through control of the accounting records. If that is possible, an independent review must be introduced at a meaningful point in the process.

Warning signs of AR control failure include unusual increases in bad debt write-offs or credit memos, frequent manual adjustments to customer accounts, payments repeatedly reversed and reapplied, growing unapplied or unidentified cash receipts, and differences between the AR subledger and the general ledger.

Automation Versus Human Judgment In AR

Modern automation handles the mechanical layer of AR well, including invoice delivery, payment reminders, aging report generation, and cash-application matching for clean, high-confidence receipts. These tasks are appropriate candidates for automation because they are rules-based, repetitive, and volume-sensitive.

Human judgment should be retained for dispute negotiation and resolution, escalation calls with customer decision-makers, credit decisions and limit changes, write-off authorization, and any exception where the matching confidence is low. Automating the reminder rungs but keeping a person for the final decision rung is sound practice, since that is a judgment call about whether a customer is worth keeping. Process discipline must precede automation; otherwise, automation accelerates existing confusion.

AR And AP As One Cash System

Receivables and payables work best when managed as a single cash system. The timing of collections inflows should inform the scheduling of payables outflows, and the credit terms a business extends to customers should be benchmarked against the terms it receives from suppliers. For a full treatment, see How To Manage AR And AP As One Cash-Protection System.

On the accounting side, AR journal entries, including recognizing revenue on delivery, recording cash receipts, posting write-offs, and maintaining the allowance for doubtful accounts, should be reconciled to the GL at month-end as a non-negotiable close step. See How To Reconcile Accounts Receivable At Month-End for the reconciliation procedure. For aging analysis methodology, see How To Do An Accounts Receivable Aging Analysis.

Why Condesa Financial Group For AR Transformation

If your AR function shows any of the failure modes described above, Condesa Financial Group can rebuild it. Condesa Financial Group takes over AR functions that look exactly like these: terms set verbally, disputes absorbed into the collections queue, cash received but never applied, no weekly aging review, and no segregation of duties. The firm rebuilds those functions as the operating system sequenced above, covering credit policy, invoicing, collections cadence, dispute triage, cash application, KPIs, and internal controls, staffed with ex-Big 4 professionals (EY, PwC) nearshore at below-US-market prices, with a fractional CFO directing the work and answering the harder strategic, tax-structuring, and forecasting questions.

The delivery model runs on standard, recognizable tooling such as QuickBooks Online, Ramp, and Gusto. The team is English-fluent and time-zone aligned. Condesa is industry-agnostic and geographically agnostic, targeting SMEs in high-cost-of-living US markets such as New York, Chicago, and San Francisco, where the nearshore price arbitrage is largest, as well as multinational founders operating across Latin America, Europe, and Asia.

Condesa does not compete on price alone and focuses on quality-to-price ratio. Clients receive ex-Big 4 caliber work at well-below-US-market rates, delivered by a warm, empathetic team that treats finance as a strategic function. Clients typically recognize the difference within three weeks of onboarding. The firm's documented outcomes include financial models that supported a $20 million and an $80 million real estate raise for Ecuador's largest real estate developer. Both raises closed successfully.

If your AR function has any of the failure modes described in this article, a free consultation is the right next step.

Schedule Your Free Consultation

Frequently Asked Questions

Here are answers to common questions about implementing these AR best practices.

How Quickly Can A Broken AR Function Be Fixed?

The foundational layer, a written credit policy, an invoicing standard, and a documented collections cadence, can be installed in a matter of weeks, though timelines vary with data quality and incumbent process documentation. For example, Billtrust's Collections Quickstart, which covers credit and collections configuration including default procedures and document statuses, can be live in 45 days or less. Cash application discipline and dispute triage workflows typically follow in weeks two through eight as the team maps existing payment channels and remittance patterns. KPI reporting and internal controls require a full month-end cycle to validate. Implementation timelines for a full AR operating system vary by tool tier and ERP. Small-business tools on QuickBooks or Xero can go live in a day to a week, mid-market AR platforms typically take two to eight weeks, and enterprise suites on NetSuite, SAP or Oracle take two to six months, with full invoice-to-cash coverage sometimes extending to 12–20+ weeks. The constraint is usually data quality and incumbent process documentation, not the practices themselves.

What Should A Collections Cadence Look Like In Practice?

A practical cadence for net-30 terms runs seven stages. These stages are a pre-due reminder at three to five days before the due date, a due-date notice, a soft follow-up by email and phone within the first week past due, a firmer follow-up referencing contractual consequences between days 8 and 30, an escalation notice with a call to the customer's finance leadership between days 31 and 60, a formal demand letter between days 61 and 90, and a write-off or collections agency decision at 90 days. Each stage specifies a channel, a tone, and a named owner. The most common failure is starting the cadence at the soft follow-up stage, which trains customers that invoices are flexible deadlines. The pre-due reminder is the cheapest stage to add and the one most businesses skip.

How Should An SME Handle A Customer Who Simply Will Not Pay?

First, confirm the account is genuinely delinquent and not subject to a dispute or administrative error. Then follow the documented escalation ladder, including final demand, credit hold, and a decision between collections referral and write-off based on balance size, relationship value, and likelihood of recovery.