---
title: "How to reduce days sales outstanding: Intelligent Contacts guide"
url: "https://intelligentcontacts.com/how-to-reduce-days-sales-outstanding/"
type: "post"
published: "2026-11-18T13:44:35-06:00"
modified: "2026-11-18T13:44:37-06:00"
author: ""
---

Sending more reminders isn't a reliable answer to how to reduce days sales outstanding (DSO). A collector can't fix an undelivered invoice, an unresolved billing error or a payment waiting to be matched. Intelligent Contacts publishes this guide for the collections and payment work it supports, with a practical priority: work more of the right accounts, collect more cash and reduce pressure on staff without mistaking a better dashboard for better collections.

## Table of Contents

- [Calculate DSO the right way before you change anything](#calculate-dso-the-right-way-before-you-change-anything)
    - [Choose the measure that answers the operating question](#choose-the-measure-that-answers-the-operating-question)
- [Fix the leaks in the order that pays back](#fix-the-leaks-in-the-order-that-pays-back)
    - [Repair the upstream work first](#repair-the-upstream-work-first)
    - [Automate follow-up without automating mistakes](#automate-follow-up-without-automating-mistakes)
- [Which payment options actually shorten cycles](#which-payment-options-actually-shorten-cycles)
    - [Price the acceleration before offering it](#price-the-acceleration-before-offering-it)
- [Prioritize collection contacts and track the right KPIs](#prioritize-collection-contacts-and-track-the-right-kpis)
    - [Make contact policy a system constraint](#make-contact-policy-a-system-constraint)
    - [Keep the operating scorecard small](#keep-the-operating-scorecard-small)
- [Where an AI collection agent fits](#where-an-ai-collection-agent-fits)
    - [Define the boundary before assigning the work](#define-the-boundary-before-assigning-the-work)
    - [Judge the handoff, not just the conversation](#judge-the-handoff-not-just-the-conversation)
- [Run a 90-day pilot before you scale the changes](#run-a-90-day-pilot-before-you-scale-the-changes)
    - [Review execution before declaring success](#review-execution-before-declaring-success)
    - [Make the scale decision explicit](#make-the-scale-decision-explicit)

## Calculate DSO the right way before you change anything

**DSO equals accounts receivable divided by revenue, multiplied by the days in the period.** For an annual calculation, use 365 days. In a hypothetical business with $100 million in annual sales, each DSO day represents approximately $274,000 in receivables ($100 million divided by 365).

That calculation estimates gross working-capital opportunity, not guaranteed incremental collections. The trap is the numerator: ending receivables can jump when a large invoice is issued just before the reporting cutoff, even if customer payment behavior hasn't changed.

![Intelligent Contacts guide to reducing days sales outstanding: reviewing receivables and invoices](https://intelligentcontacts.com/wp-content/uploads/2026/11/how-to-reduce-days-sales-outstanding-financial-analysis.jpg)

### Choose the measure that answers the operating question

The controller needs a consistent working-capital trend. The collections supervisor needs an actionable queue. Those aren't the same report.

**DSO and related measures, and what each one is for**

| Metric | Formula | Best use |
| --- | --- | --- |
| Ending-balance DSO | Accounts receivable ÷ revenue × days in period | Tracking the trend in working capital |
| Average DSO | Average receivables ÷ annual revenue × 365 | Comparing periods without month-end spikes |
| Aging by bucket | Open balance grouped by days past invoice or due date | Choosing which invoices to work this week |
| Average days delinquent | Sum of overdue balance × days past due ÷ total overdue balance | Judging how overdue accounts behave |
| Cohort cash forecast | Cash received by days since invoice, per segment | Forecasting cash for the next quarter |

Average receivables soften cutoff effects, but they don't eliminate seasonality or changes in payer mix. Invoice aging measures elapsed time since billing; due-date aging measures lateness against the actual agreement. Teams should label both explicitly instead of treating them as interchangeable.

A utility billing run, an insurance adjustment and a healthcare payer dispute can produce similar aging balances for very different reasons. Comparing them against a single target can push collectors toward accounts they can't meaningfully advance.

> **Measurement rule:** A lower DSO counts as cash acceleration only when receipt timing supports that conclusion.

Pair every reported improvement with **cash collected, past-due share, dispute cycle time and write-offs**. A write-off removes a receivable without collecting it, and a larger revenue denominator can lower DSO without changing payment timing.

This week's diagnostic should identify DSO by customer segment and aging bucket, then name the three segments holding the largest open balances. Separate collectible debt, disputed balances and unapplied receipts before assigning work.

## Fix the leaks in the order that pays back

Start with the aging report and collector notes, not an automation purchase. Match each visible symptom to a cause that someone can verify.

**Receivable symptoms, likely causes and the fix for each**

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Invoices reach customers days after shipment | Batch billing or manual invoice runs | Issue invoices at shipment, milestone or contract start |
| Disputes stay open for weeks | No owner and no reason codes | Route disputes by reason with a cycle-time target |
| Cash is received but stays unapplied | Manual posting and matching lag | Automate matching and post remittances daily |
| Large balances age past 90 days | One collection cadence for every account | Segment by balance and age, then prioritize by expected cash yield |
| Customers pay by mail or check when they want to pay online | Payment channel friction | Add self-service online and interactive voice response (IVR) payment options |
| Reported DSO falls but cash does not move | Billing timing or denominator changes | Pair DSO with cash collected, past-due share and write-offs |

### Repair the upstream work first

**Confirm delivery before demanding payment.** Issue the invoice when the contract permits billing, verify the destination and capture delivery failures. A sent status isn't proof that the correct accounts-payable team received an acceptable invoice.

Next, review billing errors by reason and value. Missing purchase-order references, incorrect responsibility assignments and unsupported adjustments need correction, not another reminder. A [proactive billing strategy](https://intelligentcontacts.com/proactive-billing-strategy/) should assign those errors to the department able to fix them.

Then address cash application. Post remittances daily, match them to open items and route uncertain matches to a person rather than forcing a match. **Applying received cash improves account accuracy; it doesn't mean new money arrived.**

In an [Association for Financial Professionals (AFP) case study](https://www.financialprofessionals.org/training-resources/resources/articles/Details/overcoming-the-loss-of-receivables-transaction-data) on recovering lost remittance data, Shearer's Foods reported lowering its DSO by three days.

### Automate follow-up without automating mistakes

Once billing and account status are dependable, the operating sequence should continue:

- **Schedule reminders around the due date.** Use pre-due, due-date and post-due stages, subject to approved channel, consent and contact policies.
- **Give disputes an owner.** Route by payer, reason and deadline, with a documented next action and escalation path.
- **Preserve human review.** Keep unusual balances, ambiguous responsibility and compliance-sensitive accounts out of routine unattended treatment.

For calls and texts, document the applicable consent or other approved legal basis before activating the workflow. A reminder schedule must never override a suppression, dispute restriction or customer communication preference.

Use the next billing cycle to inspect delivery and reminder execution. Allow a full quarter to evaluate whether dispute routing and segmentation improve aging, rather than promising immediate DSO movement.

## Which payment options actually shorten cycles

**Start with the cost-to-cash test:** estimate the cash brought forward, then account for discounts, processing fees, staff effort and the controls needed to accept payment. Cash released from receivables isn't profit, and a faster payment can still be an expensive payment.

The right option fits the customer's obstacle. A customer who accepts the balance but can't reach an agent needs a different path from someone who disputes responsibility or can't afford the full amount.

**Payment options compared on cash effect and cost**

| Intervention | Cash effect | Cost or friction | Best fit |
| --- | --- | --- | --- |
| Self-service portal payments | Faster receipt on balances customers already accept | Potentially low handling cost, plus processing and card fees | Consumer and small-balance accounts |
| IVR payment capture | Settles calls that would otherwise need an agent | Setup work and a Payment Card Industry Data Security Standard (PCI-DSS) scope review | High-volume inbound accounts |
| Installment payment plans | Turns stalled balances into scheduled cash | Longer collection tail and administration for missed plans | Balances the customer cannot pay in one sum |
| Early-payment discount | Pulls cash forward | Discount cost can exceed the cost of funding | Only customers who would otherwise pay late |
| Shorter payment terms | Shortens the cycle on new contracts | Can raise disputes or strain the relationship | New customers with strong credit |

### Price the acceleration before offering it

Under **2/10 net 30**, a customer receives a discount for paying early; the annualized cost is roughly **37%**, calculated as 2 ÷ 98 × 365 ÷ 20, as illustrated in [Stripe's working-capital guidance](https://stripe.com/resources/more/working-capital-optimization). That rate deserves comparison with the organization's actual funding cost, not automatic approval because collections improved.

Discounts are particularly wasteful when offered to customers who would have paid on time anyway. Shorter terms also require commercial judgment: changing an established agreement can create resistance without changing the customer's payment run.

> Payment convenience addresses willingness to act. It doesn't establish ability to pay or resolve a disputed balance.

Portals and IVR let customers settle accepted balances without waiting for an agent. Installments fit affordability problems, but the team must define missed-payment handling and distinguish an active plan from a broken promise.

Payment flows should be **built to meet PCI-DSS standards**, with sensitive payment information kept out of ordinary notes and recordings. Healthcare balances, governed by the Health Insurance Portability and Accountability Act (HIPAA), need HIPAA-ready infrastructure and appropriate access controls; the [operational case for healthcare payment portals](https://intelligentcontacts.com/more-healthcare-companies-have-access-to-the-benefits-of-payment-portals/) should include those safeguards, not convenience alone.

Channel selection should start with the channels late payers already use successfully. New options should reduce effort rather than require another registration process that customers abandon.

## Prioritize collection contacts and track the right KPIs

Rank accounts by **expected cash yield**, using balance, probability of payment, delinquency age and dispute status. A large disputed account isn't automatically a better assignment than a smaller accepted balance ready for settlement.

Deadline-sensitive work needs a separate priority override. Healthcare claims approaching appeal deadlines, government accounts requiring specific documentation and insurance balances awaiting a responsibility decision need action matched to the obstacle, not repeated demands for payment.

### Make contact policy a system constraint

Agents shouldn't have to remember every restriction while handling a queue. Before a contact is placed, pacing logic should evaluate the account's approved channels, local contact window, consent status, suppressions and recent attempts.

For United States operations, legal review should determine how the Telephone Consumer Protection Act (TCPA), the Fair Debt Collection Practices Act (FDCPA) and Regulation F apply to the organization, debt and communication method. HIPAA, the Fair Credit Reporting Act (FCRA) and payment-security obligations address different risks and shouldn't be treated as interchangeable contact rules. Canadian operations need jurisdiction-specific policies rather than copied United States settings.

A single universal call cap isn't a complete compliance design. Applicable restrictions can involve the person, debt, channel, conversation history and state or provincial requirements.

### Keep the operating scorecard small

A useful [contact center key performance indicator (KPI) scorecard](https://intelligentcontacts.com/6-game-changing-kpis-elite-contact-center-leaders-swear-by/) should explain what happened after the team worked the account:

- **Cash collected:** Reconciled receipts, separated from accounting adjustments.
- **Past-due percentage:** Overdue receivables divided by the relevant open balance.
- **Promise-to-pay kept rate:** Promises fulfilled under a consistently defined rule.
- **Dispute cycle time:** Elapsed time from dispute opening to documented resolution.
- **Cash application lag:** Time between receipt and posting to the correct account.
- **Write-offs:** Balances removed without collection, shown separately from recoveries.

The [Hackett Group's 2025 Working Capital Survey announcement](https://www.thehackettgroup.com/2025-working-capital-survey-payables-rebound-receivables-inventory-lag/) reports an **18-day DSO gap** between top-performing and median-performing companies, representing an estimated **$600 billion** in excess receivables working capital. That's a survey-level opportunity, not a promise that an individual collections team can close the same gap.

The sensible initial target is a defensible improvement in the team's own collectible segments. Supervisors should reward resolved obstacles and reconciled cash, not attempts alone.

## Where an AI collection agent fits

**Grace, the AI collection agent from Intelligent Contacts, is in production and collecting today**, operating within each client's configured compliance policy. Its appropriate role is routine balance conversations within that policy, with complex disputes, hardship statements and requests for a person escalated to a live agent.

Deployment should begin with policy configuration, not a contact list upload. Contact windows, attempt limits, consent records and permitted channels need clear owners and approval before outreach begins.

### Define the boundary before assigning the work

Compliance belongs in the architecture: checks should occur before a call or message goes out, rather than relying only on a review afterward. Configuration still requires governance, testing and updates when the underlying account status or applicable requirements change.

- **Routine conversation:** Keep the agent within approved balance information, payment paths and response boundaries.
- **Dispute or hardship:** Transfer the issue with its context rather than continuing a collection script.
- **Human request:** Route to a live agent without making the customer justify the request.

> An automated conversation isn't a resolved account if the handoff leaves the customer waiting in another queue.

The receiving agent needs the reason for escalation, the relevant conversation context and a clear next action. Otherwise, automation shifts work instead of reducing it.

### Judge the handoff, not just the conversation

Track **escalation rate** and **dispute cycle time after escalation** against a human-only pilot baseline. Escalation rate shows how much work still requires a person, but a lower rate isn't automatically better if legitimate disputes aren't being recognized.

Dispute cycle time reveals whether the receiving team can act on the handoff. Review sampled conversations alongside those measures, including cases where customers repeated a concern or abandoned the interaction.

The staffing question is whether routine work receives appropriate coverage while people retain capacity for judgment-heavy cases. A conversation count alone can't answer it.

## Run a 90-day pilot before you scale the changes

Select a payer segment with enough consistent activity to compare treatment and control groups. Keep account age, balance distribution, payment history and dispute mix reasonably comparable, and document which workflow changes the treatment group receives.

A **90-day pilot** is an operating design, not a guaranteed payback period. Its baseline should include cohort DSO, invoice-delivery rate, days to pay, dispute frequency and collector productivity, with definitions frozen before launch.

### Review execution before declaring success

Use planned reviews at days **30, 60 and 90** to separate implementation problems from treatment results. These checkpoints are management choices, not performance benchmarks.

- **Day 30:** Confirm that delivery, routing and posting work as designed. Investigate missing events, duplicate contacts and incorrect account statuses.
- **Day 60:** Compare receipt timing and staff effort between groups. Check whether disputes are resolving or merely moving into a different queue.
- **Day 90:** Record the DSO change alongside net cash, past-due share, write-offs and dispute cycle time, then decide whether to keep, adjust or stop.

Normalize the comparison for seasonality and revenue mix. A different payer population or billing pattern can make an ineffective workflow look successful.

Self-service payments should let customers resolve balances, establish payment plans and complete transactions independently. Pilot evaluation should distinguish completed payments from abandoned sessions, scheduled installments and plans that subsequently fail.

### Make the scale decision explicit

**Keep** a change when reconciled cash and customer outcomes support the improvement at an acceptable operating cost. **Adjust** it when the underlying process works but a channel, segment or handoff creates avoidable friction. **Stop** it when apparent DSO gains come from adjustments, shifted balances or unacceptable risk.

Before expansion, verify role-based access, auditable account changes and approved consent and contact settings for each channel. Assign an owner to exceptions rather than leaving them in an unattended report.

The final decision should include actual cash figures next to the DSO movement. If the team can't explain where the money came from, it hasn't established a repeatable collections improvement.

---

Intelligent Contacts brings contact center communication and self-service payments into one configurable platform, helping teams connect account outreach with a practical path to payment. Visit [Intelligent Contacts](https://intelligentcontacts.com) to discuss a controlled pilot built around the organization's payer segments, contact policies and cash-collection measures.
