Work out your days sales outstanding the way finance teams report it. Pick a method, enter your receivables and credit sales, and see how long customers really take to pay you.
Uses receivables at period end. This is the most common way DSO is reported.
Enter any two and we work out the third. Average receivables is calculated for you.
Countback walks back through recent months until receivables are fully covered. It handles seasonal or growing sales better than an average.
One-time cash released into the business, based on your average daily credit sales.
Your inputs stay in your browser. Nothing is stored.
Days sales outstanding measures the average number of days it takes to collect cash after a credit sale. Divide receivables by credit sales for the period, then multiply by the number of days in that period.
Money customers still owe you for invoices already raised. Take the trade receivables (sundry debtors) balance from your balance sheet or the AR ageing report on the last day of the period.
Example: unpaid invoices on 31 Dec total ₹4.2 croreSales billed on credit during the same period, excluding cash, card and UPI sales. Take it from the sales register or revenue ledger, net of returns and credit notes. If you cannot split it, total revenue works as an estimate.
Example: invoices raised from 1 Oct to 31 Dec total ₹7.5 croreThe length of the period you picked for credit sales. Use 30 for a month, 90 for a quarter or 365 for a year, so receivables and sales cover the same window.
Example: October to December quarter = 90 daysUses closing receivables. Simple and widely used in board packs, but a big sale in the last week can push DSO up.
AR at close ÷ credit sales × daysAverages opening and closing receivables, which smooths out a single unusual month-end balance.
((Opening AR + Closing AR) ÷ 2) ÷ credit sales × daysTakes receivables and subtracts each month's credit sales, working backwards. The most accurate choice when sales are seasonal or growing.
Full months covered + part of the next month| Receivables at quarter end | ₹4,20,00,000 |
| Credit sales in the quarter | ₹7,50,00,000 |
| Days in the period | 90 |
| DSO | 50.4 days |
A good DSO sits close to your payment terms. A useful rule of thumb is that DSO should be no more than one third above your standard terms. Across industries, typical ranges look very different, so compare yourself with peers rather than one universal number.
| Industry | Typical DSO | Why it lands there |
|---|---|---|
| Retail and eCommerce | 5 to 25 days | Most sales are card, UPI or marketplace settlements, with few credit customers |
| FMCG and consumer goods | 20 to 45 days | Distributor credit is short, but modern trade can stretch it |
| Enterprise SaaS | 40 to 65 days | Annual invoicing, procurement approvals and net-30 to net-60 terms |
| Logistics | 45 to 75 days | Freight invoices often wait on proof of delivery and rate reconciliation |
| Manufacturing | 50 to 80 days | Longer B2B terms and dispute-heavy invoices |
| Pharma and healthcare | 60 to 100 days | Hospital and institutional buyers pay slowly |
| Construction and infrastructure | 90 to 150 days | Milestone billing, retention money and government payers |
Indicative ranges based on published industry DSO studies. Your own terms and customer mix matter more than any benchmark.
Get a one-page report with your DSO, days beyond terms, best possible DSO and the cash you can release.
Most DSO gaps come from a handful of process leaks, not from customers who cannot pay. Fix these in order and the number usually moves within one or two quarters.
Every day between delivery and invoice adds a day to DSO. Automate invoice generation from your ERP and send e-invoices with the IRN the same day.
Prioritise the large and slipping accounts first. A short daily worklist beats a long monthly call list.
Short payments and deductions sit in receivables until someone owns them. Route each dispute to an owner the day it appears.
Unapplied receipts make paid invoices look overdue. Match payments to invoices automatically from bank and remittance data.
Review terms for chronic late payers and new customers. Shorter terms on a few accounts often move DSO more than any policy change.
Watch best possible DSO next to actual DSO. The gap between them is the part your collections team can win back.
DSO is calculated by dividing accounts receivable by credit sales for the same period and multiplying by the number of days in that period. For example, ₹4.2 crore of receivables against ₹7.5 crore of quarterly credit sales gives 0.56 × 90 = 50.4 days.
Use the receivables balance at the end of the quarter, divide it by total credit sales for those three months, and multiply by 90 (or the exact number of days in the quarter). If sales changed a lot across the three months, the countback method gives a more accurate answer.
Annual DSO is receivables divided by credit sales for the last 12 months, multiplied by 365. Many teams use average receivables for the year, (opening plus closing) divided by 2, to avoid a single month-end balance skewing the result.
Best possible DSO uses only current, not-yet-due receivables in the formula. It shows the DSO you would have if every customer paid exactly on terms. The gap between actual DSO and best possible DSO is the part your collections process can recover.
Credit sales is the correct base because cash and card sales never create receivables. If your ERP does not split credit sales, total revenue is a common substitute, but it will make DSO look lower than it really is for businesses with a large cash or UPI share.
Not always. A high DSO can reflect long but agreed terms, such as milestone billing in infrastructure. What matters is DSO relative to your terms and whether it is rising. Days beyond terms is the better warning signal.