
How to reduce DSO: the guide to getting paid faster, from invoice to reminder
DSO is not reduced at collection first. It is reduced at the invoice.
DSO (days sales outstanding) measures the average number of days between a sale and the cash reaching the bank. It is one of the indicators finance teams watch most closely, because it weighs directly on cash and on working capital requirements.
In France, the topic is anything but theoretical. According to the 2025 report of the Observatoire des délais de paiement published by the Banque de France, late payments averaged 13.4 days at the end of 2025, and small and micro businesses would have around €13 billion of additional cash if legal payment terms were respected. The same report notes that fewer than one large company in two complies with the 60-day limit.
When DSO is too high, the reflex is often to step up collection. That helps, but it comes late. A large share of delays starts upstream: an invoice sent too late, a disputed amount, a missing purchase order number, a wrong billing address, a customer who does not understand what they are being charged for. Each of these defects adds days before the first reminder is even sent.
That is why reducing DSO starts with the invoice. This guide explains how to calculate and read DSO, what drives it up and what the law says, then sets out the concrete levers, from accurate invoicing to payment and dunning, and a 90-day action plan.
For the overall framework, see our guides to order to cash and quote-to-cash.
Contents
What is DSO?
DSO (days sales outstanding) is the average number of days it takes a company to collect payment after a sale. It combines four delays: the contractual payment term, the time to issue the invoice, the customer's late payment and disputes. Reducing DSO means acting on all four.
DSO expresses outstanding receivables as a number of days of revenue. A DSO of 55 days means that, on average, it takes 55 days to turn a sale into money in the bank account.
It differs from two related notions:
- the contractual payment term: the due date agreed with the customer, for example 45 days end of month;
- late payment: the number of days beyond the due date. DSO in effect adds the two together, plus the time lost before the invoice is issued when it is measured from the sale.
| Indicator | What it measures | Who controls it |
|---|---|---|
| Contractual term | The due date granted to the customer | Sales and finance, within legal limits |
| Time to invoice | The time between delivery or the service period and sending the invoice | Billing |
| Late payment | Days beyond the due date | The customer, dunning and dispute handling |
| DSO | Outstanding receivables relative to revenue, in days | The whole cycle, from order to cash |
DSO has a very concrete consequence. Each day of DSO represents roughly one day of revenue tied up with customers. For a company that bills €36.5 million a year, or €100,000 a day on average, cutting DSO by ten days frees up around one million euros of cash. The example is illustrative, but the order of magnitude explains why finance leaders and investors watch it so closely.
How to calculate DSO
The simple method divides receivables by revenue for the period and multiplies by the number of days. The countback method allocates receivables to the most recent months' revenue and is more accurate when sales are seasonal or growing.
The simple method
The most common formula is:
DSO = (accounts receivable ÷ revenue including tax for the period) × number of days in the period
Receivables include tax, since that is what the customer has to pay; revenue must therefore also be taken including tax for the ratio to make sense. Discounted bills not yet due and receivables sold but still at risk are usually added back, so as not to flatter the indicator artificially.
Example: €2.4 million of receivables at the end of March, €4.5 million of revenue including tax over the 90-day quarter. DSO = (2.4 ÷ 4.5) × 90 = 48 days.
The countback method
The simple method smooths out variations in activity. When sales are seasonal or growing fast, the countback method is more faithful: you start from month-end receivables and "consume" the revenue of previous months, going backwards, until receivables are fully covered. The number of days counted back gives the DSO.
Example: €2.4 million of receivables. March generated €1.8 million of revenue including tax (31 days), February €1.2 million (28 days). March covers €1.8 million; €0.6 million remains, half of February, so 14 days. DSO = 31 + 14 = 45 days.
Calculation pitfalls
- Comparing different scopes: a consolidated DSO mixes businesses, countries and customers with very different practices. It must be broken down by entity, segment and customer.
- Forgetting the time to invoice: if invoices go out ten days after month end, a DSO calculated on issued invoices underestimates the real time between sale and cash.
- Ignoring credit notes and disputes: a disputed receivable stays in the balance. A stable DSO can hide a rise in disputes offset by faster collection elsewhere.
- Changing method during the year: comparisons lose their meaning.
What drives DSO up
DSO rises for commercial reasons (long terms granted, weak credit checks), customer reasons (cash difficulties, complex approval processes) and billing reasons (late, wrong or unreadable invoices, missing references, unmatched payments). The billing causes are the ones the company fully controls.
The causes of a high DSO fall into three families. The third, billing quality, is often the least measured and the easiest to fix.
Commercial causes
- long payment terms granted to win a contract,
- special conditions negotiated customer by customer, poorly known by the billing team,
- a heavy weight of large accounts, whose approval circuits are long,
- an international customer base, with different payment habits.
Customer causes
- a tight financial situation, which pushes the customer to delay payments,
- a heavy internal payment process: mandatory purchase order, approval by several people, payment runs on fixed dates,
- a supplier portal on which the invoice must be uploaded in a specific format.
Billing causes
- the invoice goes out late: manual preparation, usage collected late, internal approval too long, a monthly close that blocks invoicing;
- the invoice is wrong: wrong price, forgotten discount, badly calculated proration, wrong usage, incorrect VAT rate;
- the invoice is incomplete: missing purchase order number, wrong legal entity billed, wrong address or contact, mandatory mentions missing;
- the invoice is hard to understand: the customer cannot find their contract, does not understand the usage detail, does not know what a line refers to;
- the invoice does not reach the right recipient, or gets lost in a generic mailbox.
Each of these errors has the same effect: the customer does not pay, or pays only part, and waits for a correction. The corrected invoice or credit note goes through a new approval cycle. A few days of delay at invoicing easily turn into several weeks of delay in collection.
Payment terms and late payment rules
In France, B2B payment terms are capped at 60 days from the invoice date or 45 days end of month, with late payment interest and a €40 fixed recovery fee per late invoice. At EU level, the Late Payment Directive sets a similar framework. Terms and penalties must be known to the customer to be effective.
In France, payment terms between businesses are governed by the Commercial Code (articles L441-10 and following). According to Bpifrance Création, the main rules are:
| Rule | What the law provides |
|---|---|
| Default term | 30 days after the service is performed or the goods are received, if nothing is agreed |
| Maximum agreed term | 60 days from the invoice date, or 45 days end of month |
| Periodic invoices | 45 days maximum from the invoice date |
| Late payment interest | The ECB's latest refinancing rate plus 10 points, or another rate that cannot be lower than three times the legal interest rate |
| Fixed recovery fee | €40 per invoice paid late |
| Sanctions | Administrative fine of up to €2 million for a company, €4 million for repeat offences |
At EU level, the Late Payment Directive (2011/7/EU) sets a default term of 30 days, limits agreed B2B terms to 60 days unless expressly agreed and not grossly unfair to the creditor, and provides for statutory interest and a minimum €40 compensation per late invoice. National laws may be stricter, as in France. In the US, payment terms are mostly contractual, with specific prompt payment rules for public sector buyers.
Three practical consequences for DSO:
- The invoice date matters. The legal term runs from the date the invoice is issued. An invoice issued late pushes the due date back by as much.
- The terms must appear on the invoice or in the terms and conditions. Late payment interest and the fixed recovery fee only work if they are stated and known to the customer.
- The law does not do everything. Few companies systematically apply penalties to their customers, for fear of damaging the relationship. The legal lever mainly serves as the framework for a clear credit policy.
These rules apply between businesses. Sales to consumers, public contracts and international sales follow different rules. When in doubt, legal advice remains necessary.
Lever 1: invoice right and immediately
The fastest DSO gains come from invoicing as soon as the right to bill exists, making invoices impossible to dispute and making them easy to read. These actions depend entirely on the company.
This is the most powerful lever, and the one most often under-used. It acts on two components of DSO: the time to invoice and the time lost in disputes.
Invoice as soon as the right to bill exists
- One-off sales: trigger the invoice at delivery or activation, automatically, rather than at month end.
- Subscriptions: bill in advance when the contract allows it, and generate invoices on fixed dates, without manual intervention.
- Usage: collect and rate usage data continuously, so you can invoice as soon as the period ends, not after several days of processing. That is the role of billing mediation and usage-based billing.
- Project milestones: link approved milestones to the invoice trigger.
Every day gained at invoicing is a day gained on DSO, without asking anything of the customer.
Make the invoice indisputable
An accurate invoice relies on accurate upstream data: a single offer and price catalog, up-to-date contracts, dated discounts, checked usage. Price errors and forgotten discounts are also a cause of revenue leakage: fixing them improves both revenue and DSO.
A few simple checks before sending prevent a large share of disputes:
- comparison of the amount with the previous invoice, with an alert above a threshold,
- presence of the purchase order number when the customer requires it,
- check of the billed entity, the address and the billing contact,
- check of discounts and promotion end dates,
- consistency between billed usage and measured usage.
Make the invoice readable
The customer must be able to find what they bought: contract reference, period covered, usage detail, explanation of proration and discounts. A clear invoice is approved faster on the customer side, especially when it passes through several hands.
Lever 2: make payment easy
Offer the payment method that fits each customer, match incoming payments quickly and handle payment failures automatically.
Offer the right payment method
Direct debit almost entirely removes late payment on recurring invoices: payment happens on the due date, without any action from the customer. For subscriptions, in B2B as in B2C, it is often the most effective lever. Card payments and payment links embedded in the invoice or the email make small invoices easier to settle.
| Payment method | Effect on DSO | What to watch |
|---|---|---|
| Direct debit | Payment on the due date, no action needed from the customer | Up-to-date mandate, handling of rejections |
| Card and payment link | Immediate payment possible | Fees, expired cards |
| Bank transfer | Depends on the customer's discipline | Matching payments without references |
| Customer supplier portal | Depends on the invoice being uploaded correctly | Formats, purchase order numbers, approval times |
Match payments quickly
A payment received but not allocated to the right invoice remains, in the books, an open receivable. DSO looks higher than it is, and reminders go out by mistake to customers who have paid. Automatic cash application, based on payment references and matching rules, avoids both effects.
Handle payment failures
Rejected direct debits, expired cards, partial transfers: each failure must trigger an immediate, automatic action, such as a new attempt or a request to update the payment method, rather than waiting for the monthly review of the aged balance.
Lever 3: chase at the right time
Replace case-by-case reminders with a dunning journey: a courtesy reminder before the due date, a reminder the day after, escalation one to two weeks later, then a formal notice. Segment journeys by customer profile and prioritize the team's work by amount and risk.
A dunning journey, not case-by-case reminders
Effective dunning is planned, progressive and automatic. A typical journey looks like this:
| Timing | Action | Channel |
|---|---|---|
| A few days before the due date | Courtesy reminder, with the invoice and the payment link | |
| The day after the due date | First reminder | |
| One to two weeks after | Second reminder, call to the billing contact | Email and phone |
| Three to four weeks after | Firm reminder, mentioning late payment interest and the fixed recovery fee | Letter or formal email |
| Beyond | Formal notice, service suspension if the contract allows it, legal collection | Registered letter |
The timings are guidelines, to be adapted to customers and contractual conditions.
Segment journeys
A single scenario for all customers is rarely optimal. A large account that always pays ten days late because of its internal circuit does not need a formal notice, but a contact in its accounts payable department. A small customer paying by card needs an automatic reminder and a payment link. Journeys are built by segment: size, payment history, amount, seniority, criticality.
Prioritize the team's work
Collection teams have limited time. They must spend it on the receivables that matter: large amounts, delays that are getting longer, customers whose payment behavior is deteriorating. The aged balance gives an overview; each customer's payment history lets you go further and anticipate delays. This is where artificial intelligence is starting to provide concrete help, as our guide to AI agents for billing shows.
Suspend service as a last resort
For subscription services, progressive suspension of service in case of non-payment is a powerful lever, provided it is set out in the contract, announced to the customer and applied automatically with judgment. It must be lifted as soon as payment is received.
Lever 4: resolve disputes quickly
Every disputed invoice is a blocked payment. Record each dispute and its cause, set a resolution deadline, and fix causes at the source so they do not recur. E-invoicing statuses make disputes visible faster.
A disputed invoice does not get paid. As long as the dispute is not resolved, the receivable ages, reminders become pointless and the relationship gets tense.
Record every dispute and its cause
Each dispute must be recorded with its reason: price, quantity, discount, purchase order, entity, service not delivered. This information is used twice: to suspend reminders on the invoice concerned, and to fix the cause at the source.
Set a resolution deadline
An unresolved dispute is a payment term that keeps growing. An owner, a target deadline and a weekly review of open disputes are often enough to shorten their duration significantly.
Fix the cause at the source
If the same error comes back every month, the problem is not the customer but the process. A discount entered by hand, a badly configured proration rule, a catalog that differs between the CRM and billing: these causes must go back to the teams that manage the catalog, contracts and subscription management.
What e-invoicing changes
France's e-invoicing reform directly affects this lever. According to impots.gouv.fr, every company must be able to receive electronic invoices since September 1, 2026; issuing them has been mandatory since that date for large and mid-sized companies, and will be from September 1, 2027 for small and micro businesses.
Invoices then flow between approved platforms, as structured data, with lifecycle statuses. Four statuses are mandatory, according to Pennylane: submitted, rejected, refused and collected. For DSO, this is progress: a rejected or refused invoice is known immediately, instead of being discovered at the due date. These statuses still need to flow back into the billing system and trigger an action. Our guide to e-invoicing in France explains what this implies upstream of the invoice.
KPIs and a 90-day plan
Track DSO by entity, segment and customer, time to invoice, aging buckets, disputed invoice rate and causes, dispute resolution time, share of direct debit payments, unmatched payments and best possible DSO. Then run a 90-day plan: measure, fix causes, automate.
The KPIs
DSO alone does not tell you where to act. It must be complemented by indicators that point to each cause:
| KPI | What it reveals |
|---|---|
| DSO by entity, segment and customer | Where credit days are concentrated |
| Time to invoice | The time lost before the invoice is even sent |
| Aged balance (not due, 0-30, 31-60, 61-90, over 90 days) | The structure of delays |
| Disputed invoice rate and reasons | Billing quality |
| Average dispute resolution time | How effective dispute handling is |
| Share of direct debit payments | The potential for payment automation |
| Unmatched payment rate | Cash application quality |
| Best possible DSO | DSO if every customer paid on the due date |
Best possible DSO is particularly useful: it is calculated on receivables not yet due only. The gap between actual DSO and best possible DSO measures the share due to late payment; best possible DSO itself measures the share due to the payment terms granted.
A 90-day plan
| Period | Actions |
|---|---|
| Days 1 to 30: measure | Calculate DSO by segment, time to invoice and best possible DSO; analyze overdue invoices by reason; identify the twenty customers that weigh most in receivables |
| Days 31 to 60: fix the causes | Remove the manual steps that delay invoicing; add pre-send checks; fix recurring catalog and contract errors; appoint a dispute owner |
| Days 61 to 90: automate | Set up segmented dunning journeys; extend direct debit to subscriptions; automate cash application; track the KPIs every week |
This plan does not require changing everything. It requires treating DSO as an outcome of the whole cycle, not as a problem for the collection team alone.
Frequently asked questions about DSO
What is DSO?
DSO, or days sales outstanding, is the average customer payment time expressed in days of revenue. It measures the time needed to turn a sale into cash.
How do you calculate DSO?
The simple method divides accounts receivable by revenue including tax for the period, then multiplies by the number of days in the period. The countback method, more accurate when sales are seasonal, goes back through revenue month by month until receivables are covered.
What is a good DSO?
There is no universal value. A good DSO is compared with the average contractual payment term, the industry and the company's own history. The gap between actual DSO and best possible DSO is often more telling than the absolute value.
What is the difference between DSO and late payment?
Late payment counts the days beyond the due date. DSO also includes the contractual term granted to the customer, and therefore all the credit granted.
How can you reduce DSO quickly?
The fastest gains often come from billing: issue invoices as soon as the right to bill exists, fix the errors that cause disputes, offer direct debit and automate dunning.
What are the maximum payment terms in France and in Europe?
In France, between businesses, the agreed term cannot exceed 60 days from the invoice date, or 45 days end of month; failing agreement, it is 30 days after delivery or service. Under the EU Late Payment Directive, B2B terms should not exceed 60 days unless expressly agreed and not grossly unfair.
Will e-invoicing reduce DSO?
It can help: the invoice arrives faster, in structured form, and lifecycle statuses quickly flag a rejection or refusal. It does not, however, fix an invoice that is wrong or incomplete.
Cash is won at the invoice
Reducing DSO is not just about chasing harder. It means shortening every step between the sale and the cash: invoicing earlier, billing accurately, making payment easy, chasing at the right time and resolving disputes quickly.
Key takeaways:
- DSO measures receivables in days of revenue,
- it breaks down into time to invoice, contractual term, late payment and dispute time,
- French law caps B2B terms at 60 days or 45 days end of month,
- billing errors are a major, and avoidable, cause of delays,
- direct debit and automatic cash application reduce delays and false receivables,
- a segmented dunning journey beats a single scenario,
- e-invoicing speeds up the detection of rejections, not the quality of invoices.
The best reminder is the one you never need to send.
Go further with Opencell
Opencell is an agile, open source monetization platform that automates quote-to-cash, from quote to cash collection, for subscription and usage-based services. It covers the offer and price catalog, orders, subscriptions, usage rating, invoicing, payments and dunning journeys with the Dunning module. On the Opencell AI roadmap, Cash Collection Optimizer will help collection teams prioritize their actions based on each customer's payment history. Born in telecoms in 2007, it manages €14 billion in revenue for around fifty customers.
Want to cut DSO by fixing invoices at the source?



