
Accounts receivable KPIs: the 8 a controller should review weekly
Accounts receivable KPIs a controller can review weekly: eight metrics with formula, owner and the action to take when each moves, plus a one-page AR review.
Home » Accounts receivable KPIs: the 8 a controller should review weekly
A controller should review eight accounts receivable KPIs every week: DSO, average days delinquent, collection effectiveness index, past-due aging, percent current, dispute rate, promise-to-pay kept rate, and unapplied cash. Each has one formula, one owner and one trigger that says when to act.
A monthly close shows you a problem after the cash is already late. A weekly look catches the one customer who slipped from 30 to 60 days while the average still looked fine. If you’re building the routine around accounts receivable automation, these eight are the numbers the agents should prepare before you sit down.
This guide reflects how we run the review as of November 2026. Every number comes from one worked ledger, so the formulas reconcile.
Which AR number would you check first on Monday?
Bring your current AR report to a short call and we’ll walk through which of the eight metrics your ERP can already show and which it can’t.
Book a 30-min call →Quick Answer Accounts receivable KPIs a controller should review weekly are DSO, average days delinquent, collection effectiveness index, past-due aging, percent current, dispute rate, promise-to-pay kept rate and unapplied cash. Each is a formula run on the same ledger, with an owner and a trigger that says when to act. Review them in 30 minutes every Monday.
The right weekly set is small, and it’s ordered. You pull the numbers, flag what moved, explain why, assign an owner and confirm the action happened by next week. Most AR dashboards stop at the pull.
The QServices Framework Weekly AR Review = Pull → Flag → Explain → Assign → Confirm
Pull first so everyone argues about the same numbers. Confirm last, because a flag nobody follows up is only a report.
These are the AR KPIs for controllers that earn a seat in a weekly review, in the order we read them:
AR turnover is DSO restated, so it adds no new weekly action. Cost per collection and right-party-contact rate matter for staffing, but they move slowly. Put them on a monthly "also track" list, along with bad debt ratio, which we keep as a weekly watch item only when write-offs are rising.
This is the table to pin above the AR team’s desk. The worked company has $4.2M of monthly credit sales and $6.1M of open AR, and the figures come from that ledger.
| KPI | Formula | Worked result | Weekly red flag | First action |
|---|---|---|---|---|
| DSO | Open AR / credit sales x days | 6.1 / 4.2 x 30 = 43.6 days | Up more than 2 days vs your 12-week range | Read ADD to see if it’s late payers |
| ADD | DSO minus best possible DSO | 43.6 – 30.7 = 12.9 days | Gap widening two weeks running | Pull the top 10 overdue |
| CEI | See formula below | 68.4% | Falls week on week | Check collector activity |
| Past due over 60 | 61+ days past due / open AR | 0.45 / 6.1 = 7.4% | Any rise | Escalate named accounts |
| Percent current | Not-yet-due AR / open AR | 4.3 / 6.1 = 70.5% | Falls | Check invoicing delays |
| Dispute rate | Disputed AR / open AR | 0.21 / 6.1 = 3.4% | Backlog grows | Assign each dispute an owner |
| Promise kept rate | Kept / promises due | 29 / 40 = 72.5% | Below your baseline | Re-contact broken promises |
| Unapplied cash | Unapplied / open AR | 0.31 / 6.1 = 5.1% | Items older than 5 days | Match or request remittance |
Key Insight An average hides the problem. In this ledger DSO is 43.6 days, but only $0.18M, about 3% of open AR, is over 90 days, and that small slice is where the next write-off comes from.
Days sales outstanding is the average number of days it takes to turn a credit sale into cash. Pick one definition and never change it: open AR divided by credit sales for the period, multiplied by the days in that period. For the full formula variants, see our days sales outstanding formula guide.
Use a 30-day window for the weekly view and a 90-day window to smooth out spikes. With $6.1M of open AR and $4.2M of credit sales in the last 30 days, DSO is 6.1 / 4.2 x 30 = 43.6 days. If the 90-day figure is $12.9M of credit sales, DSO is 6.1 / 12.9 x 90 = 42.6 days, and the two are close enough that nothing is distorted by one big month.
Don’t mix this with a count-back method on the same slide. The two give different answers, and the argument that follows wastes the meeting.
Best possible DSO is the DSO you would have if every customer paid exactly on time. The best possible DSO formula uses only the current, not-yet-due balance: current AR / credit sales x days in period.
In our ledger, $4.3M of the $6.1M is not yet due. Best possible DSO is 4.3 / 4.2 x 30 = 30.7 days. A target DSO equal to best possible DSO is unrealistic, because some invoices are always mid-term. The useful number is the gap.
Average days delinquent is DSO minus best possible DSO, so 43.6 – 30.7 = 12.9 days. It isolates lateness from payment terms.
A widening gap can signal weaker collections even when DSO looks flat, for example when terms were lengthened at the same time. That is why ADD gets its own line in the weekly pack.
Collection effectiveness index measures the share of collectable receivables you actually collected in the period. It reads 100% when everything collectable was collected.
The standard form, as described by AccountingTools, is:
CEI = (beginning receivables + credit sales – ending total receivables) / (beginning receivables + credit sales – ending current receivables) x 100
On our ledger: beginning receivables $5.8M, credit sales $4.2M, ending total $6.1M, ending current $4.3M. The numerator is 5.8 + 4.2 – 6.1 = 3.9. The denominator is 5.8 + 4.2 – 4.3 = 5.7. CEI is 3.9 / 5.7 = 68.4%.
The common error is using total receivables in both places, which makes the number look better than it is. For how to calculate collection effectiveness index across several periods and why it catches what DSO misses, read collection effectiveness index vs DSO.
CEI ignores aging, doesn’t separate write-offs from payments, looks backward and covers credit sales only. Sources also disagree on what counts as current, and some use 60 days or fewer. Set your own definition once and write it on the report.
These two metrics explain most surprises in DSO. Aging tells you who is late. Unapplied cash tells you whether the ledger is even telling the truth.
No standards body defines the aging over 60 days target, so it is a house metric: AR 61 or more days past due divided by total open AR. In our ledger it’s 0.27 + 0.18 = 0.45, or 7.4%. Age from the due date, not the invoice date, and tag disputed items so they aren’t dunned like ordinary late invoices. Our AR aging report guide shows how to read each bucket.
| Past-due bucket | Amount | Share of open AR |
|---|---|---|
| 1-30 days | $0.90M | 14.8% |
| 31-60 days | $0.45M | 7.4% |
| 61-90 days | $0.27M | 4.4% |
| 90+ days | $0.18M | 3.0% |
| Total past due | $1.80M | 29.5% |
Percent current is not-yet-due AR over total open AR: 4.3 / 6.1 = 70.5%. It’s the simplest early warning, because it falls before the older buckets rise. If it drops while sales are flat, look at late invoicing before you blame customers.
Unapplied cash as a percentage of receivables is unapplied payments divided by open AR: 0.31 / 6.1 = 5.1%. Track the oldest item’s age too, which is your cash application lag.
Unapplied cash inflates DSO. A customer who paid 45 days ago can look both current and 61-90 days past due. Apply the $0.31M and open AR drops to $5.79M, so DSO falls from 43.6 to 41.4 days with no collections work at all. Our guide to clearing unapplied cash covers the backlog.
Key Insight Before you chase a customer on a 61-90 day invoice, check the unapplied list. In our worked ledger, unapplied cash alone moves DSO by 2.2 days.
Dispute days and deduction days in AR measure how long a contested amount stays stuck. They matter because disputed invoices can’t be collected, and standard dunning on them annoys the customer.
Track three numbers. Dispute rate is disputed AR over open AR, here 0.21 / 6.1 = 3.4%. Resolution days is total days to resolve closed disputes divided by the number closed: 96 days across 12 closed disputes is 8 days. Resolution rate is closed over opened, so 12 closed against 15 opened is 80%, which means the backlog is growing.
If you see recurring short payments, a short pay tracking guide helps tag the reason codes.
Deduction days outstanding is the same idea applied to customer deductions. Vendor sources quote conflicting benchmarks for it, so quote none and build your own baseline.
Promise-to-pay kept rate is the share of promised payments that arrived by the promised date. In our ledger 29 of 40 promises were kept, so 72.5% were kept and 27.5% were broken. It tells you whether your collectors’ follow-up is working, and none of the three pages that rank for this topic covers it. A broken promise needs a call within a day, so pair it with a dunning sequence.
Is aging over 60 days quietly growing in your ledger?
Book a call to see how an approval-first agent can flag stale invoices and unapplied cash, while your team approves anything that posts money.
Book a 30-min call →Set targets from your own payment terms and your own history. Published averages conflict on definitions, such as ending versus average AR and credit sales versus total revenue, so treat them as context only. Don’t repeat the 45-day rule as fact. We haven’t found a source that proves it for your industry.
Pull 12 months of weekly values for each KPI. Use the median as the baseline and the range as the normal band. A red flag is a move outside that band, or a trend in one direction for three weeks.
Compare with the same weeks last year as well as the last four weeks. A distributor that bills heavily in Q4 will see DSO and percent current swing for reasons that aren’t collections problems.
| Cadence | KPIs | Owner | Purpose |
|---|---|---|---|
| Weekly | All 8 | AR manager | Act on what moved |
| Monthly | Trend lines, write-off ratio, cost per collection | Controller | Spot drift, staffing |
| Quarterly | Targets, terms, credit limits | CFO and controller | Reset baselines |
For Dynamics 365 Business Central, the data comes from a few places. Business Central offers an Aged Receivables (Back Dating) report with customizable buckets by document, due or posting date, an Average Collection Period Power BI report, Data Analysis on Customer Ledger Entries, and a Reminder report.
Standards & References
- Microsoft Learn: collect outstanding balances in Business Central: reminders, aged balances and customer collection in Business Central
| KPI | Business Central source | Usual pitfall |
|---|---|---|
| DSO and ADD | Customer Ledger Entries, plus the Average Collection Period Power BI report | Unapplied payments leave invoices open |
| CEI | Customer Ledger Entries by posting and due date | Posting date versus due date mix-ups |
| Aging, percent current | Aged Receivables (Back Dating) | Bucketing by posting date, not due date |
| Disputes | Customer Ledger Entries with an on-hold marker or a dispute code | Disputed items still dunned |
| Promise to pay | Notes or a custom field on the ledger entry | Not captured unless you add it |
| Unapplied cash | Open payment entries in Customer Ledger Entries | Multi-currency rounding and suspense postings |
A Power BI report on top of this data turns the table above into a weekly Power BI accounts receivable dashboard your CFO will open. Larger shops on Dynamics 365 Finance can build the same AR dashboard from its customer transactions. If you’re still on Dynamics GP, the report names differ, but the formulas don’t.
The weekly review is one page and 30 minutes. That page is the output of the Pull and Flag stages, and the meeting covers Explain, Assign and Confirm.
This weekly accounts receivable review checklist is the Monday agenda:
Real-World Scenario A typical case we see: a controller at a distributor reads DSO of 43.6 days and thinks collections are slipping. The aging report shows 7.4% over 60 days, which is unremarkable. The unapplied list shows $0.31M of payments sitting in suspense, and the oldest is 9 days. The naive approach sends dunning letters to customers who have already paid. The Explain stage catches it, because the unapplied check comes before any outreach.
Most of this review is preparation. The agents do the pull, the flags and the draft messages, and a person decides.
We start with the Pull stage, because agreed definitions matter more than any dashboard. Our agents run inside your Business Central tenant and your CRM, and a person approves anything that posts money or changes a system.
With a manual review, someone spends a morning pulling reports before the meeting starts. With an agent-prepared pack, the meeting time goes to decisions. The same team that builds the agents runs them.
Implementation Checklist
- One written definition for DSO, ADD and CEI, signed off by the controller
- Aging calculated from due date, not posting date
- Disputed invoices tagged so dunning skips them
- Unapplied payments listed daily with age
- 12 months of weekly baselines stored for every KPI
- A named owner on each of the eight KPIs
- A Monday slot booked for the 30-minute review
- Every proposed posting goes through an approval queue
Start with the one-page pack and one baseline, and run it for four Mondays. Pilot it on your largest customer segment and measure unapplied cash age, ADD, promise kept rate and the time the pack takes to prepare. When you’re ready, book a 30-min call and we’ll walk through your ledger.

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.
There’s no single good DSO. Published industry averages use different definitions, so treat them as context. Compare your DSO with your own payment terms and your own 12-month baseline, and read it with best possible DSO. In our worked ledger, DSO is 43.6 days against a best possible DSO of 30.7 days.
DSO is the average days to collect cash from all receivables. Average days delinquent (ADD) is DSO minus best possible DSO, so it isolates lateness from payment terms. In the worked example, 43.6 – 30.7 = 12.9 days of delinquency.
CEI = (beginning receivables + credit sales – ending total receivables) / (beginning receivables + credit sales – ending current receivables) x 100. With $5.8M beginning, $4.2M sales, $6.1M ending total and $4.3M ending current, CEI is 3.9 / 5.7 = 68.4%.
Review the eight accounts receivable KPIs weekly, in a 30-minute Monday meeting. Move trend lines, write-off ratio and cost per collection to a monthly review, and targets and credit limits to a quarterly one. To start, run the one-page pack for four Mondays and set baselines from 12 months of history.
No standard body sets one, so use your own baseline. In the worked ledger, 29.5% of open AR is past due, 7.4% is over 60 days and about 3% is over 90 days. Watch the trend and the over-60 share, because they predict write-offs better than the total.

Accounts receivable KPIs a controller can review weekly: eight metrics with formula, owner and the action to take when each moves, plus a one-page AR review.

Remittance matching rules for payments with no invoice detail: 7 steps in order, tolerance limits and an exception queue your team can clear fast.

Automated bank reconciliation in Business Central: see what Copilot adds to automatch, where it errs, and how to keep a person approving every posting.

What is unapplied cash? It’s a credit held as a liability until matched. See the journal entries and when to apply, refund or write it off in your ERP.

An AI service desk agent triages tickets and drafts first answers from your knowledge base. See the hand-over rule that keeps a person in charge of changes.

Integration monitoring for ERP, CRM, bank and store syncs: what to watch, how to alert, and how an agent drafts the incident note before anyone looks.
Next step
Ready to turn the weekly AR review into a habit?
Talk to our team about agents that sit inside your ERP and CRM, prepare the work behind these metrics, and leave every posting to your approval.
Book a 30-min call →
Accounts receivable KPIs a controller can review weekly: eight metrics with formula, owner and the action to take when each moves, plus a one-page AR review.

Remittance matching rules for payments with no invoice detail: 7 steps in order, tolerance limits and an exception queue your team can clear fast.

Automated bank reconciliation in Business Central: see what Copilot adds to automatch, where it errs, and how to keep a person approving every posting.

What is unapplied cash? It’s a credit held as a liability until matched. See the journal entries and when to apply, refund or write it off in your ERP.

An AI service desk agent triages tickets and drafts first answers from your knowledge base. See the hand-over rule that keeps a person in charge of changes.

Integration monitoring for ERP, CRM, bank and store syncs: what to watch, how to alert, and how an agent drafts the incident note before anyone looks.
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
Thanks, we’ve got your details. A named member of our team will reply within one business day.