Accounts receivable management is a six-stage cycle: set credit terms, invoice accurately, apply cash, collect, resolve deductions, and measure results. Finance teams run it well when every stage has an owner, a written rule, and a metric.
Most of the manual effort sits in matching payments and chasing follow-ups. That is where accounts receivable automation helps, with AI agents working inside your ERP while your team approves every action.
This guide is for CFOs and controllers who want the whole cycle on one page. We cover each stage, current US benchmarks, and where people, process, and systems each belong.
Quick Answer Accounts receivable management is how a company turns sales into cash. It sets credit terms, invoices accurately, applies incoming payments, follows up on late balances, resolves short pays and disputes, and tracks KPIs such as days sales outstanding. Done well, it makes cash predictable and keeps overdue balances small.
Good AR is boring in the best way. Customers get credit they can handle, invoices are right the first time, cash lands against the correct invoice the same day, and nobody learns about a problem account from the bank balance.
The problem is that AR usually breaks at the handoffs, not inside one step. Sales sets terms, billing sends invoices, treasury receives cash, and collections chases the gap. Nobody sees the whole line.
The QServices Framework AR Cycle = Credit → Invoice → Apply → Collect → Resolve → Measure
The order matters because each stage feeds the next: a loose credit decision creates a late invoice, a wrong invoice creates a dispute, and an unapplied payment looks like a past-due balance.
The accounts receivable process steps follow the same six stages in the framework above. Credit approves the customer, Invoice bills it, Apply matches the payment, Collect chases what is late, Resolve closes deductions and disputes, and Measure tells you which stage is leaking.
No regulator or standards body defines the cycle, so treat it as accepted practice rather than a rule.
The accounts receivable best practices for finance teams that hold up in the US are few and unglamorous:
The stakes are real. The Federal Reserve Banks’ Small Business Credit Survey 2024 Report on Payments found roughly four in five small firms face payment-related challenges. That is a survey of small firms, but the pattern shows up in larger companies too.
A credit policy for receivables is the cheapest AR control you have. It decides who gets terms, how much, and what happens when they pay late. Without it, collections inherits every risky decision sales made.
Here is how to write a credit policy in five steps:
Our view: keep the policy to two pages. A ten-page policy gets ignored.
A limit is a business decision, never a permanent one. Review accounts every 6 or 12 months, and quarterly for high-risk customers. Trigger an early review when a payment runs more than 30 days late, a promise to pay is broken, disputes pile up across several invoices, or the balance sits near the limit.
Your ERP can enforce this. Dynamics 365 Finance supports credit limits, temporary limits, risk-based blocking rules, and approval workflows for limit changes and order releases. The exact setup is in the Standards card further down.
An invoice that a customer cannot match to a purchase order does not get paid on time. It gets queried, and the clock stops while it waits in someone’s inbox.
Most invoice delays come from the same few errors: a missing or wrong PO number, a price that differs from the order, the wrong bill-to entity, or a missing remittance contact. Each one adds a round trip of emails.
Track the number of revised invoices each month. It is a plain signal of billing quality, and it points back to the Invoice stage when DSO creeps up.
Key Insight Every invoice you correct is a payment you delayed. Fixing the data at the source costs minutes; fixing it after the customer disputes it costs weeks.
Cash application is the step where a payment is matched to the open invoices it covers. When it fails, cash sits unapplied and the customer still looks past due, which triggers reminders to people who already paid.
The usual causes are thin remittance data, partial payments, and one payment covering many invoices. Our cash application process guide walks the six steps and where they break.
Payments arrive through ACH, wire, check, and lockbox, often with a remittance file that does not match your invoice numbers. If the file is a poor fit, someone matches by hand. Our guide to clearing an unapplied cash backlog covers the cleanup, and a good remittance advice prevents much of it.
Matching rules plus an agent can propose matches and route exceptions to a work queue. The measures to watch are the share of payments matched without touching, unapplied cash volume, and exception cycle time. Be skeptical of vendor claims of 90% or higher automation. Your rate depends on your remittance quality.
Unapplied cash also delays the close, as we explain in our month end close checklist.
The AR collections process is a scheduled, documented routine for contacting customers before and after an invoice is due. How to improve AR collections comes down to consistency: the same reminder, to the right person, on the same day, every time.
Split accounts by balance, risk, and payment behavior. A large customer who always pays on day 40 needs a different approach than a new account that just missed its first due date.
Send a friendly notice before the due date, a firm one just after, and a call at about two weeks late. Include a payment link and the invoice copy in every message, so the customer has no reason to wait.
Define who steps in and when: collector, controller, then sales leadership. Legal action timing is a business decision for your company, so set it in the credit policy instead of improvising per account.
Log each promise to pay with a date. A broken promise is a trigger for escalation and a credit review. Your AR aging report then shows which bucket needs action first.
A deduction is an amount a customer withholds from a payment, usually for a reason they believe is valid. Common causes include pricing errors, damaged goods, shortages, early-payment discounts, and promotions. Some are invalid, and you only know which by working each one.
How to manage customer deductions starts with treating each one as a case:
Some large retailers only accept disputes inside a fixed window, such as 60 days, so age matters. We cover the tracking in our short pay tracking guide.
Real-World Scenario A typical case we see: a controller at a US building-products distributor finds $18,000 in short pays sitting in unapplied cash across 14 customers, all older than 45 days. In the naive approach, collectors keep dunning the full invoice amounts and the customers get annoyed. The Resolve stage catches it: each short pay becomes a coded case, six turn out to be pricing errors the company fixes, and the rest are re-billed with proof.
The AR KPIs to track are the ones that tell you which stage is leaking. Start with five, in the same order every month.
The most recent Credit Research Foundation National Summary of Domestic Trade Receivables (Q2 2026) gives these median values for participating companies:
| KPI | What it tells you | Q2 2026 median |
|---|---|---|
| Days sales outstanding (DSO) | Average days to collect | 37.50 days |
| Best possible DSO | DSO if nothing were overdue | 34.00 days |
| Average days delinquent | DSO minus best possible DSO | 3.70 days |
| Collection effectiveness index | Share of collectible cash collected | 79.35 |
| Percent current | Receivables not yet past due | 87.92% |
| Over 91 days past due | Seriously aged balances | 0.40% |
These are medians of survey participants, not a universal target. Compare yourself against your own terms first.
Standards & References
- Credit Research Foundation: quarterly US trade receivables benchmarks, published since 1960
- Microsoft Learn: Dynamics 365 Finance accounts receivable: how an ERP handles credit, collections, and aging
A good DSO sits close to your payment terms. On Net 30 terms, a figure in the high 30s is a sensible target, and the gap between DSO and best possible DSO shows how much is overdue. Our days sales outstanding formula guide has the calculation and levers.
How to reduce days sales outstanding comes down to three levers: invoice faster, apply cash faster, and contact late accounts sooner. If your team is stretched, start with the lever that removes manual work, as we describe in reducing DSO with a stretched AR team.
Key Insight Average days delinquent is DSO minus best possible DSO. Q2 2026 median: 3.70 days. If yours is far above that, collections is your problem; if it is near zero but DSO is high, your terms or invoicing are.
People decide, process sets the order, and systems do the repetitive work. Problems appear when a team uses people for matching and chasing, which they do slowly, and systems for judgment, which they do badly.
Accounts receivable automation with ERP integration means the agent reads and writes where your records live: invoices, open items, customer credit, and collection notes. It avoids a spreadsheet side channel that drifts out of sync with the ledger. If you are moving ERPs, plan AR continuity first, as in our Dynamics GP to Business Central AR migration guide.
AR automation with human approval means an agent drafts the match, the reminder, or the credit memo, and a person approves before anything posts money or changes a system. We cover why in AI agent governance. Can AI agents handle AR follow-ups? They can draft and queue them. Your team still approves the send.
| Area | Manual AR | Agent-assisted AR with approval |
|---|---|---|
| Cash matching | Hand-keyed from bank files | Agent proposes, person approves |
| Follow-ups | Depend on who remembers | Drafted on schedule, reviewed in a queue |
| Exceptions | Found at month end | Surfaced the day they appear |
| Audit trail | Emails and spreadsheets | Every action logged with approver |
| Setup effort | None | Weeks of mapping rules and cleaning data |
| Ongoing review | None beyond the work | Someone must clear the approval queue daily |
The honest downside is the last two rows. Automation needs clean data to start and a person reviewing the queue every day. Skip that review and you only move the backlog.
We start at the Measure stage, because you cannot fix a stage you have not sized. Then we work forward through the cycle one workflow at a time, with agents running in your own Azure tenant and an approval queue before anything posts.
Implementation Checklist
- Written credit policy approved by finance and sales
- Credit limit review dates set for every active account
- Invoices carry the customer PO number
- Unapplied cash older than 10 days listed with an owner
- Every deduction has a case ID and reason code
- DSO, best possible DSO, and average days delinquent reported monthly
- An approver named for any action that posts money
Accounts receivable management improves fastest when you pilot the Collect stage on one customer segment for 60 days and measure DSO, average days delinquent, promises kept, and weekly hours spent on follow-ups. Agents can draft the reminders and propose the matches, and your team approves every action before it posts or sends. Book the AR Cash Assessment and we will size it against your own aging.
Written by Rohit Dabra
Co-Founder and CTO, QServices IT Solutions Pvt Ltd
Rohit Dabra is the Co-Founder and Chief Technology Officer at QServices, a software development company focused on building practical digital solutions for businesses. At QServices, Rohit works closely with startups and growing businesses to design and develop web platforms, mobile applications, and scalable cloud systems. He is particularly interested in automation and artificial intelligence, building systems that automate routine tasks for teams and organizations.
A good days sales outstanding is close to your payment terms. The latest US survey median we cite in this guide is 37.5 days (Q2 2026), but that is a median of participants, not a target. On Net 30 terms, aim for the high 30s and watch the gap between DSO and best possible DSO.
The accounts receivable process steps are credit approval, invoicing, cash application, collections, resolving deductions and disputes, and measuring KPIs. Each step feeds the next, so an error early on, such as a wrong invoice, shows up later as a dispute or a late payment.
To improve AR collections, segment customers by risk and balance, send reminders on a fixed schedule, include a payment link and invoice copy every time, and log every promise to pay. Escalate by rule when a promise is broken. Consistency matters more than tone.
AI agents can draft follow-up emails, queue them on schedule, and propose payment matches. A person should approve anything that sends to a customer, posts money, or changes a record in your ERP. That approval step is what makes the setup safe for CFOs and controllers.
In our experience, a two-week assessment comes first, and a pilot on one workflow follows within a few weeks after that, depending on data quality. Start by measuring your aging, unapplied cash, and DSO, then pick one workflow, such as late-account reminders, to automate with human approval.
Accounts receivable management explained for finance teams: credit, invoicing, collections and KPIs, plus where AI agents help and people approve.
Cash application software or a managed service? Compare cost, ERP fit and team time, and see when each wins for your AR team. Pick with a clear checklist.
Build a Power BI accounts receivable dashboard CFOs actually open: the six visuals that matter, the data model under them and how to feed it from your ERP.
Prophet 21 accounts receivable planning starts with two dates: 30 Jun 2029 and 31 Dec 2029. See what each means for Kinetic and P21 users and how to plan.
Learn the accounts receivable process step by step, and the questions a new CFO should ask the AR team in week one, plus which answers should worry you.
See the order to cash process in one diagram, with the eight stages and the hand-off points where cash gets delayed, and who owns each stage.
Accounts receivable management explained for finance teams: credit, invoicing, collections and KPIs, plus where AI agents help and people approve.
Cash application software or a managed service? Compare cost, ERP fit and team time, and see when each wins for your AR team. Pick with a clear checklist.
Build a Power BI accounts receivable dashboard CFOs actually open: the six visuals that matter, the data model under them and how to feed it from your ERP.
Prophet 21 accounts receivable planning starts with two dates: 30 Jun 2029 and 31 Dec 2029. See what each means for Kinetic and P21 users and how to plan.
Learn the accounts receivable process step by step, and the questions a new CFO should ask the AR team in week one, plus which answers should worry you.
See the order to cash process in one diagram, with the eight stages and the hand-off points where cash gets delayed, and who owns each stage.
Earning Global Recognition: A Testament to Quality Work and Client Satisfaction. Our Business Thrives on Customer Partnership
Every quote comes from a published review on GoodFirms, Clutch or our own site. Click a source to read the full review.
Trustpilot5.0★★★★★See reviewsGoodFirms5.0★★★★★45 verified reviews
G25.0★★★★★See reviewsClutch5.0★★★★★Quality 5.0 · Schedule 4.8
Google4.7★★★★★Mohali office“QServices was highly professional, knowledgeable, and approachable. We continue to work with them on other projects.”
“Quality assurance is often overlooked, but these guys take that very seriously. … their team of experienced, dedicated developers and highly skilled engineers quickly dissected and decomposed every problem and presented solutions and options that directly met my needs”
Erik BrownBusiness owner and software engineerClient review“The supplier delivered the application on time and was responsive to our needs. He was also flexible, which allowed us to make changes on the fly.”
Zoltan BodnarCFO, Yusen LogisticsGoodFirms“Thank you Sahil and team for wonderful collaboration right from day 0. … Highly recommend the developers.”
Ranbeer MakinClientClient review“They are always looking for new ways to improve their products and services and to deliver value to their customers.”
“I have had an excellent experience working with QServices. We have a highly collaborative relationship and I value them not just as contractors but as partners.”
Alex VanderElsClientClient review“Sahil undertakes every project with a high degree of professionalism. His communication style is unmatched and he is always available to resolve issues or just discuss the project.”
Philmore J.ClientClient review“Responsive, patient and professional. Consistent weekly attention to our project, and new ideas we hadn't asked for.”
Michael WilliamsonPresident and CEO, United Way of Southeast LouisianaGoodFirms“I have been working with them on a project for a year now … They have been able to solve problems that come up with bugs or development and able to communicate well with me.”
Steven LewisClientClient review“We had been working on the app for two years. QServices built it in two months.”
Brian WallerPresident, Technology Association of IowaGoodFirms“All projects were delivered on time and were fully completed upon delivery.”
“They had excellent quality. The hypercare they provided after the project went live is exceptional.”
Founder and CEO
Chief Sales Officer
