Days sales outstanding (DSO) measures how long it takes to collect payment after an invoice is raised. It is commonly calculated as accounts receivable divided by credit sales for a period, multiplied by the number of days in that period. When it climbs, the standard response is to push harder on collections: earlier reminders, more follow-up calls, a dedicated person on overdue accounts. For many Indian B2B companies the real cause sits at the invoice. Collections can only work on a clean invoice. An invoice that contains an error gives the buyer a legitimate reason to hold payment until it is corrected.
What High DSO Costs
High DSO means revenue on the books that is not yet in the bank. The invoice is raised, the amount is owed, and the sale is counted. But until payment arrives and is posted, that cash is not available to use. Finance teams bridging the gap either draw on a credit line or delay their own payments to suppliers. Both carry a cost. The AR balance still shows the invoice as outstanding rather than signaling the problem clearly. The cash position does.
Why Collections Effort Alone Does Not Fix It
When DSO goes up, most teams respond by sending reminders earlier, following up more frequently, and escalating faster. That approach works when the invoice was correct to begin with.
An invoice that contains an error gives the buyer a legitimate reason to hold payment. The buyer raises a dispute. The AR team investigates. The invoice is corrected and reissued, which means it goes through an internal approval process, gets sent back to the buyer, and waits for the buyer's AP team to review it before payment is scheduled. The process takes three to five days minimum, often longer. The payment clock restarts from the date of the corrected invoice, not the original.
There is also a relationship cost. When a customer paid the correct amount and the AR team follows up anyway because the invoice had the wrong TDS rate or an incorrect payment term, the customer has to spend time explaining that they paid correctly. That conversation happens because of an error on the supplier's side. It rarely improves the relationship.
More follow-up calls do not fix a broken invoice. The invoice has to be right before collections has anything to work with.
How to Tell If Your DSO Problem Starts at the Invoice
Before investing more in collections, check two things.
Pull the invoices your team disputed or reissued in the last quarter. Count how many were corrected and resent. Then look at the reasons: wrong payment terms, GST portal rejections, TDS discrepancies, escalation rates that did not match the contract. If those reasons appear more than occasionally, the problem is upstream.
The second check is simpler: look at how long it takes between the invoice being raised and the buyer confirming it is correct. If that gap is consistently two to four days, the invoice is not landing clean. Collections starting after that gap carries a built-in delay that no amount of follow-up removes.
Where DSO Problems Usually Start
Three causes account for most of the DSO drag in Indian B2B companies:
- Contract terms not translating to the invoice. The contract says 30-day payment terms. The invoice goes out with 45 days because someone typed it manually. Or an escalation clause applies from month three but the invoice is raised at the original rate. The buyer receives an invoice that does not match what was agreed. Payment stalls while both sides investigate and the invoice is corrected. To check for this: compare the payment terms on your last 20 invoices against the corresponding contracts. A mismatch rate above zero is a process gap.
- GST errors restarting the AR clock. A missing HSN or SAC code, an invalid GSTIN, a wrong place of supply. The IRP rejects the invoice. It has to be corrected, re-approved internally, and resubmitted. Two to three days pass before the AR clock even starts. Meanwhile the buyer's AP team will not process an invoice without a valid IRN because they cannot claim input tax credit against it. The buyer is not late. The invoice was not ready. To check for this: look at how many invoices were resubmitted to the IRP in the last month and what errors triggered the rejection.
- TDS rate mismatches creating false short-payment flags. The contract specifies TDS at one rate. The invoice shows a different rate. The buyer deducts at the contracted rate and pays the net amount. The payment does not match the invoice total. Collections flags it as a short payment and begins follow-up. The buyer is not in default. The invoice was wrong. To check for this: pull the short-payment disputes from the last quarter and check how many were closed without recovery because the deduction turned out to be correct.
What Changes When the Invoice Is Right
When invoicing is clean, three things shift that collections effort alone cannot produce.
The AR aging report becomes reliable. When invoices go out correct and clear the portal on the first submission, the overdue column reflects accounts that are genuinely late, not accounts that are waiting for a corrected invoice. The collections team works a list that means something.
Cash flow forecasting improves. A disputed invoice sitting in the ledger as outstanding distorts the forecast. Finance leaders working from a forecast built on clean invoices make better decisions about credit lines, supplier payments, and working capital deployment.
The collections worklist shrinks to real work. When TDS rates are correct and payment terms match the contract, the follow-up queue contains accounts that are overdue, not accounts that paid correctly and are waiting for the AR team to realize it. That is the difference between a collections function and a dispute resolution function. The first is productive. The second is a cost of invoicing errors.
DSO comes down when the time between invoice raised and invoice accepted shrinks. Collections cannot shrink it. The invoicing process can.
Alfred for Finance
The three problems this article covers trace back to the same gap: contract terms that do not reach the invoice correctly, GST errors that restart the AR clock, and TDS rates that generate disputes no one needs. The invoice should reflect the contract. In practice it usually reflects whoever filled it in last.
Alfred AR closes that gap at the invoice. Alfred reads the signed contract directly and builds the invoice from it: payment terms, escalation clauses, minimum charges, TDS rates, and GST. Alfred checks every figure against the printed document before it lands on an invoice. An escalation clause that applies from month three applies on its own. Alfred confirms an unusual payment term once and carries it forward for every invoice that follows.
GST pre-checks run on every draft before it reaches approval, so the errors the IRP would reject are caught before the invoice goes out, and the buyer can process it without raising a dispute.
When invoicing is right and receipts post to the ledger on the day they arrive, the cash position stays accurate. Alfred works above Tally, writing every action back to it as the system of record, so payments flow back to the ERP the team already uses without double entry.
If DSO is climbing and collections is not the lever that moves it, the invoice is worth looking at first. Book a meeting to explore Alfred for Finance as your first AI Chief of Staff.
