Skip to main content

Accounts Receivable

Accounts Receivable is money customers owe a company for goods or services already delivered. It is a current asset on the balance sheet and a direct driver of cash flow. It is a current asset on the balance sheet, and the gap between recognising it and collecting it is what working capital management is about.

Category: AR Automation SoftwareBest AR Automation Software

Your revenue grew 40% last year, and your days sales outstanding went from 34 days to 52 days. The cash from that extra revenue arrived more slowly than the revenue itself, because the collections process didn't scale with billing volume. Sales reps closed deals, billing sent invoices, and finance watched the AR balance grow while cash inflows lagged the income statement. AR is where revenue becomes cash, and how fast that happens depends on process quality. Accounts receivable is the money customers owe a company for goods or services that have been delivered but not yet paid for. When you invoice a customer, you record the invoice amount as a receivable, an asset on the balance sheet that represents a future cash inflow. When the customer pays, the receivable is closed and cash increases. The gap between invoicing and collection is the accounts receivable cycle. Managing it well means issuing accurate invoices promptly, following up on time through systematic outreach, resolving disputes quickly, and applying payments to the right invoices without delay. Each step is simple on its own. At scale, across hundreds or thousands of invoices and customers with different payment behavior, terms and dispute rates, AR management becomes one of the finance processes with the biggest effect on cash.

How accounts receivable flows from invoice to cash

The accounts receivable cycle starts at invoice creation. An invoice is generated, ideally automatically from a completed sales order or delivery confirmation, and sent to the customer. The customer reviews it, approves it internally, and routes it through their AP process for payment. On or before the due date, they initiate payment. The payment arrives by check, ACH, wire, or card and has to be matched to the specific invoice or invoices it covers, a process called cash application. Once matched, the invoice is marked paid and drops out of AR. The failure points at scale are predictable. Invoice accuracy: invoices with wrong amounts, wrong billing contacts, or missing PO numbers get rejected or disputed instead of processed, which adds days or weeks to the collection cycle. Dispute resolution: when a customer disputes line items, the invoice sits unpaid until the dispute is resolved, and without a defined dispute process it can sit there indefinitely. Collections timing: without systematic outreach tied to due dates, follow-up on overdue invoices is reactive and inconsistent. Cash application delays: when incoming payments can't be matched to invoices automatically (because remittance information is incomplete, the amount doesn't match exactly, or nothing connects bank receipts to the AR system), the AR balance shows invoices as open after the payment has already arrived.

Invoice accuracy, customer payment behavior

AR management is a customer experience function as much as a finance function. Customers who get accurate invoices on time, with clear payment instructions and the right contact details, pay faster than customers who get invoices with errors or unclear remittance details. Invoice accuracy rate, the percentage of invoices that go out correct the first time, predicts dispute rates and, through dispute rates, DSO. A company with a 95% invoice accuracy rate and a 5% dispute rate has a different AR profile from one with an 85% accuracy rate. Customer mix matters too. Enterprise customers on net-60 terms with multi-step AP approvals pay differently from small business customers on net-30. A single large customer on extended terms can move aggregate DSO materially even if everyone else pays on time. Segmenting AR by customer size, terms, and payment history lets collections teams allocate effort proportionally, prioritizing large, slow-paying accounts instead of spreading equal effort across every overdue balance. AR connects to cash forecasting through DSO. If revenue is $10M per month and DSO is 45 days, there is roughly $15M in AR at any given time. Changes in DSO, whether from billing improvements, shifts in customer payment behavior, or economic conditions, flow straight into cash flow. A 10-day DSO reduction at $10M monthly revenue means $3.3M collected sooner, and the AR automation cash flow calculator runs the same math on your own figures.

How platforms handle it

Demos of AR automation software usually show invoice creation and payment receipt. The areas that tell you more about daily operation are cash application and dispute management. Cash application: how does the platform match incoming payments to open invoices? Does it match automatically using bank remittance data, or does it require manual matching? When a customer pays a rounded amount that doesn't match any single invoice, does the system suggest a match or drop it into an exception queue? Dispute management: when a customer disputes a line item, is there a workflow that flags the invoice, routes it to the right internal owner, and tracks resolution, or does dispute handling happen in email outside the system? Collections workflow: does the platform have built-in collections sequences, or does it only show aging and leave outreach to the AR team? Integration depth: does it connect to the CRM (so account managers can see AR status for their accounts) and to the GL (so cash application hits the right revenue and AR accounts automatically)? Companies that treat AR as a standalone billing function, cut off from collections workflow and cash forecasting, give up most of what an integrated AR process delivers.

Questions to ask when evaluating your AR process

  • What is the current invoice accuracy rate, and what are the most common dispute reasons by category?
  • How is cash application handled: automated matching using remittance data, or manual matching by the AR team?
  • Is collections outreach systematic and tied to invoice due dates, or reactive when customers are already past due?
  • How is the AR portfolio segmented for collections priority: by balance, by days overdue, or by customer risk?
  • How does the AR team track and resolve invoice disputes: in the AR system, or in email outside it?
  • How frequently is DSO calculated, and is it tracked by customer segment or only in aggregate?

How AR process gaps compound as revenue scales

Running collections reactively (reaching out only after customers are overdue, escalating only once a balance has aged past 60 days) works worse than proactive collections. Proactive AR reaches out before the due date to confirm the invoice was received, clear up potential disputes before they delay payment, and agree on expected payment timing with the customer's AP contact. By the time a customer is 30 days past due, the invoice has already dropped down their AP queue. Getting it back to the top, and spending the relationship capital that takes, costs more effort than a check-in before the due date would have. The second common failure is treating AR as one undifferentiated queue. Overdue invoices don't all deserve the same response. A $250K invoice from a key customer that's 15 days overdue needs different handling from a $1,200 invoice from a small customer that's 90 days overdue. Segmenting AR by balance, relationship tier, payment history, and dispute status, then building a collections process that responds in proportion, is how AR teams spend limited time on the outreach with the most impact.

Receivable against payable

Accounts receivable is money owed to you for goods or services already delivered. Accounts payable is money you owe suppliers for goods or services already received. One is an asset, the other a liability, and they are mirror entries across a transaction: your receivable is your customer's payable for the same invoice.

Comparing AR automation

AR tools separate on remittance handling, because a payment with no readable remittance advice becomes manual work no matching engine removes. Once accounts receivable is settled as a requirement, read the AR Automation Software category guide for how the market splits, then weigh the HighRadius profile against the Versapay profile on that requirement rather than on the feature list. Our HighRadius pricing breakdown records what the vendor publishes and what is quote-based. The HighRadius against Versapay comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the AR automation cash flow calculator so the business case is written down before a vendor writes it for you.

Accounts Receivable questions

How is accounts receivable different from deferred revenue?

Accounts receivable is money owed to your company for goods or services already delivered. Deferred revenue is money already received from customers for goods or services not yet delivered. They sit on opposite sides of the revenue recognition question: AR represents earned revenue not yet collected as cash; deferred revenue represents collected cash not yet earned as revenue. A company can have both at the same time: AR for delivered work not yet paid, and deferred revenue for prepaid subscriptions or advance payments for future delivery.

Why does DSO increase when revenue grows, even if payment terms don't change?

DSO increases when billing volume grows faster than the processes that support collections. More invoices mean more follow-ups, more disputes to resolve, and more cash to apply. If collections headcount, automation, or invoice accuracy don't scale with billing volume, the average time to collect gets longer. High-growth periods often expose AR process gaps that weren't visible at lower volume, because billing adds capacity faster than collections does.

What is the difference between gross AR and net AR on the balance sheet?

Gross AR is the total of all outstanding invoices billed to customers. Net AR is gross AR minus the allowance for doubtful accounts, a reserve for invoices estimated to be uncollectible. Net AR is the balance sheet figure and represents the estimated realizable value of the receivables. The allowance is based on aging analysis and historical collection rates. GAAP requires companies to report net AR, not gross, because gross overstates the economic value of the receivables if a portion is unlikely to be collected.

AR Aging Report, Bad Debt Write-Off, and Cash Application come up in the same workflow as accounts receivable, and the rest of the AR automation cluster is indexed in the finance operations glossary.