How to cut days sales outstanding without annoying your customers

Most late payments are not caused by customers who will not pay. They are caused by invoices that went out five days late, to the wrong email, with a PO number missing, on terms nobody agreed to in writing. By the time you are chasing, the damage is already three weeks old.

The fix is boring and it works. Invoice faster and cleaner, agree terms before the work starts, remind on a schedule that begins before the due date, and make paying take one click instead of five. Escalation matters, but it is the last lever, not the first.

Calculate your DSO first, in plain terms

Days sales outstanding is the average number of days it takes to collect after a sale. Take your accounts receivable balance at the end of a period, divide it by the credit sales in that period, and multiply by the number of days in the period.

Say you invoiced $300,000 on credit over a 90-day quarter, and you were sitting on $150,000 in receivables at the end of it. That is (150,000 ÷ 300,000) × 90 = 45 days. On net-30 terms, you are running 15 days behind your own stated policy.

Track it monthly, not once a year. A single number tells you little; the trend line tells you whether anything you changed actually worked. Pair it with an aging report: a 45-day average made of mostly-current invoices plus two ancient ones is a very different problem from everything drifting to 45.

The sequence

1. Invoice the day the work is done, not at month end

Batching invoices to the last day of the month adds up to 30 days of delay for free, before the customer has done anything wrong. If your billing cycle is monthly by necessity, at least make it the first business day rather than whenever someone gets to it.

Verify: pull last month's invoices and compare the invoice date to the date the work completed or shipped. If the average gap is over three days, that gap is yours to close.

2. Get the invoice right the first time

A rejected or queried invoice does not restart at day 30. It restarts at day zero, plus however long it took someone to tell you. The usual culprits are a missing PO or reference number, the wrong billing contact, a line description that does not match what the buyer approved, and a total the buyer cannot tie to anything.

Verify: count how many invoices last quarter were re-issued, credited, or queried. That percentage is your accuracy rate, and it maps almost directly onto your DSO.

3. Agree terms in writing before the work starts

Terms live in the engagement letter, the quote, and the invoice, the same terms in all three. Name the due date as a date, not a duration: "due 14 October" beats "net 30" because nobody has to do arithmetic or argue about when the clock started.

Also agree the mechanics: who receives the invoice, which portal it must be uploaded to, whether a PO is required, and what happens if payment is late. Larger customers have AP processes you must satisfy. Find out at the start, not at day 40.

4. Run a reminder cadence that starts before the due date

This is the highest-leverage change most businesses have not made. A polite note before money is due is not chasing: it is service. It catches the missing PO, the wrong contact, and the invoice stuck in someone's approval queue while there is still time to fix it.

A cadence that holds up:

The point is that it runs every time, on every invoice, without anyone deciding whether today is the day. Consistency is what stops it feeling personal.

5. Make paying take one click

Every step between "I should pay this" and "paid" is a place to lose days. Put a payment link in the invoice email and in the invoice itself. Accept ACH. Store payment details for repeat customers who agree to it. If you invoice the same customers monthly, offer autopay.

Verify: pay one of your own invoices as the customer would. Count the clicks and the logins. If it takes more than two minutes, fix that before you write another reminder email.

6. Escalate on a ladder, not on a mood

Write the ladder down once: reminder, call, formal notice referencing terms, stop-work or credit hold, then third-party collection. Then follow it. The relationship survives escalation when it is visibly procedural rather than a reaction. What damages relationships is silence for 60 days followed by a furious email.

Two things to build in. First, separate the commercial relationship from the collection conversation: your buyer should hear from you about the work, and their AP team should hear from your books about the invoice. Second, decide in advance which customers get a credit hold and at what threshold, so the decision is not made under pressure.

7. Give one person the cadence

Reminder cadences fail because the person running them also does sales, or delivery, or everything. Week one is diligent. Week five, an invoice slips. By week ten there is no cadence, just occasional chasing.

This is a real role: owning the aging report, running the cadence, reconciling payments, and telling you which accounts are actually at risk. It is also one of the cleanest things to hand to a dedicated accounts payable and receivable operator, because the work is rule-based and the results are visible weekly on the aging report.

What good looks like

Within a quarter of doing the above properly, expect the invoicing gap to fall to a day or two, query rates to drop, and DSO to move toward your stated terms rather than sitting fifteen days past them. You will not get to zero. You should get to predictable, which is what actually matters for planning payroll.

The number to watch alongside DSO is the percentage of receivables over 60 days. If DSO improves while that bucket grows, you are collecting well from good customers and quietly accumulating bad debt from a few. Different problem, different fix.