Days Sales Outstanding Won't Drop Until You Fix What Happens Before the Invoice

Most finance teams respond to a high days sales outstanding figure the same way: they lean on collections. More calls, earlier reminders, a stricter dunning schedule, maybe a new collections tool. Sometimes the number moves a little. Often it doesn't, and the team is left wondering why customers who seem willing to pay are still paying late.

The reason is that a large share of DSO is decided before an invoice exists. An order entered with the wrong bill-to party, a discount that was never approved, a delivery nobody can prove, a job finished on Tuesday and billed the following month: each adds days that no collector can recover. By the time the invoice reaches the customer, the clock has been running for a while and the dispute is already built in.

This article argues that to reduce DSO you have to treat it as an order to cash problem, not an accounts receivable problem. We cover the upstream causes, how to diagnose them, what they cost, and where to intervene. Then we explain how The Ninjaz Group approaches the work for multi-location companies.

Collections can only fix what collections can see

Collections starts when an invoice is past due. By then, one of three things has usually already gone wrong. The invoice was issued late, so the payment clock started late. The invoice contains something the customer disagrees with, so payment is on hold whatever the terms say. Or the customer's payables team cannot match the invoice to a purchase order, a receipt or a signed delivery, so it sits in a queue.

Collectors are effective at chasing a clean invoice that is simply overdue. They are poor at repairing an invoice that should never have gone out in its current state. Left to do it anyway, they become human middleware between sales, operations and finance, asking the same questions again and again: where is the proof of delivery, who approved this price, which PO does this belong to?

Here is a useful test. Take last month's late-paid invoices and sort them into two groups: late because the customer was slow, and late because something was wrong, missing or delayed on your side. The second group is usually larger than leaders expect, and none of it is a collections problem.

The four upstream causes of accounts receivable delays

The same four causes show up again and again in the order to cash process. They are easy to describe and surprisingly hard to see from inside any single system.

• Incomplete orders. The order is accepted without a valid PO number, correct bill-to, tax details, agreed terms or an invoicing contact. Everyone downstream finds out only when the invoice is rejected.
• Missing approvals. Special pricing, discounts, credit exceptions or change orders were agreed verbally or by email and never recorded where billing can see them. Finance invoices at list price, the customer disputes it, and the invoice stalls.
• No delivery proof. Goods were delivered or work was completed, but the signature, photo, timesheet or completion note is stuck on a driver's phone, a paper form or a technician's inbox. Customers will not pay for what they cannot verify.
• Late billing. The work is done, but the invoice waits for a weekly batch, a manager's sign-off, or someone to chase missing information. Every day of lag is a day added directly to DSO.

Notice that none of these sits in accounts receivable. They sit in the CRM, the order system, the field and the billing run.

How fragmented systems create the delay

Consider a group with twelve locations. Sales quotes in the CRM. Each location re-keys the won deal into the ERP or an order management system, in its own way. A negotiated discount lives in an email thread. The technician or driver records completion in a field app, or on paper. The billing system runs invoices from the ERP in a weekly batch, and the collections tool reads from billing.

Now follow one order. The CRM says the customer is on net 30, but the ERP defaulted to net 15 because someone skipped a field. The discount never made it out of the email, so the invoice carries list price. The field app shows the job closed on the 3rd, but the ERP only learns of it when an administrator updates it on the 6th, and the batch runs on the 10th. The invoice reaches the customer on the 12th, without a PO number, at the wrong price, with no completion proof attached. The customer's payables team rejects it. The collector sees a rejected invoice with no explanation on file.

No single system failed. Each did what it was told. The delay lives in the gaps between them, where no one owns the record end to end, which is why fixing one tool in isolation rarely moves DSO. Multiply this by twelve locations that each handle the gaps differently, and the group average hides wide differences that nobody can see.

What the delay really costs

The obvious cost is cash. Every extra day of DSO is revenue you have earned but are financing on the customer's behalf, which limits how you pay suppliers, fund growth and absorb a slow quarter. Cash is only part of the bill, though.

Time goes first. Skilled people in finance and operations spend hours rebuilding order history, hunting for signatures and reissuing corrected invoices. Mistakes follow: credit memos, rebills and write-offs that exist only because the first invoice was wrong. Inventory is affected too. Teams that cannot count on timely cash may hold orders, delay replenishment or carry buffers they would not otherwise need, while delivered-but-unbilled goods blur what is actually on hand.

Deals suffer. Credit holds triggered by old disputes block new orders from good customers, and salespeople lose selling time mediating billing arguments. Customers feel it as friction: reminders for invoices they already consider wrong, and several people at your company asking them for the same information. For the collections team, the result is burnout. They absorb the frustration of customers over problems they did not create and cannot fix.

How to diagnose where your DSO is actually made

You do not need new software to start. You need to break one number into stages and look at it by location.

1. Split DSO into stages. Measure days from order to fulfilment, fulfilment to invoice, invoice to due date, and due date to cash received. The first two are upstream, and most teams have never measured them.
2. Tag root causes on late invoices. Sample fifty or a hundred late-paid invoices and record why each was late: missing PO, price dispute, no proof of delivery, billed late, customer slow, other.
3. Measure first-time-right. What share of orders reach billing with every required field and approval in place? Even a rough manual count is revealing.
4. Track billing lag. Count the days between completion or delivery and invoice issue, and list completed work that has not been invoiced at all.
5. Compare locations. If one site bills in two days and another in nine for the same product, the difference is process, not customers.
6. Trace one order by hand. Follow a single order through every system and note each re-keying, email and wait. The trace usually explains the numbers.

Where to intervene, system by system

Once you know which stage is leaking, the fixes are mostly about making the right thing the default in the systems you already own.

CRM. Require PO, bill-to, terms and approved pricing before a deal can be marked won. Route discount approvals inside the CRM so the approval is a record, not an email.

ERP and order management. Add a validation gate: an order that lacks required data or exceeds a credit limit is held before fulfilment rather than discovered at invoicing. Make terms inherit from the customer record, not from whoever keys the order.

Field tools. Make completion a structured event: signature, photos, parts and hours captured on site and linked to the order. If a job cannot be closed without proof, proof stops being a billing-stage problem.

Billing system. Invoice on the completion event, not on a weekly batch, and attach the proof and PO to the invoice itself. Send a daily list of completed-but-unbilled work to someone who owns it.

Collections tools. Capture dispute reason codes and feed them back upstream. Route follow-up by cause, so a missing PO goes to the order desk instead of into another dunning cycle.

Reporting dashboards. Show DSO by stage and by location, plus billing lag, unbilled completed work, first-time-right rate and disputes by cause. Review them weekly with operations and sales in the room, not only finance.

How The Ninjaz Group addresses it

These interventions cross five or six systems, which is exactly why they stall: no team owns the whole path. Ninjaz works on that gap for multi-location enterprises through three layers: Managed Transformation (strategy, design, build), Managed Link (the integration layer we build, own and maintain between your existing systems) and Managed Business Operations (managed IT and day-to-day running after go-live).

Engagements start with a Blueprint. We map the operation and find where work is done twice, data goes stale or money leaks. For DSO, that usually means tracing order to cash across locations. You keep the map whether or not we build anything. Build & Link follows, with no rip-and-replace: software you have already paid for stays, and we connect it. Then we operate it.

The technical backbone is the Ninjaz Operating Platform, the integration hub we deploy and run. It has connectors to the systems you already have, including CRM, ERP, CMMS and finance, and a unified data layer with one record per customer, asset and order. Because order, approval, completion and invoice status sit on the same record, workflow automations can hold incomplete orders, route approvals, and alert someone when completed work has no invoice. The Command Center shows live KPIs and alerts across locations, so a site with slow billing is visible in days, not at quarter close. Team chat boards tied to records keep a dispute conversation attached to the order, and roles and an audit trail show who approved what.

One caveat: a platform does not decide your policy. What counts as complete, who can approve a discount, how quickly work must be billed: those are business decisions, and we help you make them explicit. The platform then enforces and monitors them. It will not fix a customer that is genuinely slow to pay, but that becomes a much smaller problem once the rest is clean.

Start with the path to the invoice

If you are asking how to improve cash flow and DSO has resisted your collections efforts, look earlier. Map the path from quote to invoice, measure each stage by location, and fix the handoffs that create incomplete orders, unrecorded approvals, missing proof and late billing. Collections works best when it receives invoices that are right and on time.

If you want help seeing where your own order to cash process loses days, book a consultation and we will talk through your systems and locations. If you would rather see how the pieces fit together first, take a look at the platform demo.