Days deductions outstanding (DDO): definition and formula

Days deductions outstanding (DDO) is the average number of days a deduction stays open before it is resolved. It is the deductions equivalent of DSO: where DSO tracks how long invoices take to collect, DDO tracks how long short pays, chargebacks, and disputes linger before they are cleared or written off.

DDO matters because unresolved deductions are stuck cash. Every open deduction is a piece of an invoice that someone disputed and no one has closed out. Until it is resolved, it sits on the aging report, drags on DSO, and consumes analyst hours. A rising DDO is an early warning that the deduction backlog is growing faster than the team can work it.

DDO formula

DDO follows the same shape as DSO, applied to deductions instead of total receivables.

DDO = (Average open deductions / Total deductions in the period) x Number of days in the period

Use the average of beginning and ending open deduction balances for a cleaner read across the period.

A worked example

Suppose a company tracks deductions for the quarter (90 days):

• Open deductions at start: 180,000
• Open deductions at end: 220,000
• Total deductions raised in the quarter: 900,000

Average open deductions:

(180,000 + 220,000) / 2 = 200,000

DDO = (200,000 / 900,000) x 90 = 20 days

A 20-day DDO means deductions clear in about three weeks on average. If that number were 50 days instead, deductions would be sitting more than seven weeks, signaling a backlog and a meaningful chunk of cash held up in unresolved disputes.

Why DDO matters

DDO is easy to ignore because deductions feel like a side issue next to headline collections. They are not.

• It inflates DSO. Open deductions are open receivables. A growing deduction backlog pushes DSO up even when the core collections process is healthy.
• It hides recoverable cash. Many deductions are invalid, the wrong amount, an expired promotion, a duplicate claim. Left unresolved, invalid deductions quietly become write-offs.
• It drains capacity. Researching deductions is slow, manual work. A backlog means analysts spend their days on aging cases instead of new ones.
• It strains customers. Deductions that drag on unanswered frustrate the customers who raised them and the ones waiting on credits.

How to lower DDO

DDO drops when deductions are triaged and resolved fast instead of piling up.

1. Code deductions at intake. Categorize each one by reason as it arrives, so similar cases can be batched and resolved with the right backup.
2. Validate against the source. Check each deduction against the contract, pricing, and shipment records to separate valid from invalid quickly.
3. Route to the right owner. Pricing disputes, shipping claims, and promotional deductions often belong to different teams. Get each to the right desk on day one.
4. Resolve valid ones fast, recover invalid ones. Clear legitimate deductions with a credit memo and pursue invalid ones before they age out of reach.
5. Track the backlog by age. Watch open deductions by aging bucket so the oldest cases get worked, not buried.

How Rex brings DDO down

Deductions inflate DDO because they sit in a queue waiting for an analyst with time to research them. Rex works that queue continuously. As each deduction arrives, it codes the reason, validates the claim against the contract and shipment data, and routes it to the right owner, so cases get triaged on day one instead of aging in a backlog. Valid deductions get cleared quickly, and invalid ones get pursued before they slip toward write-off.

Rex handles the high-volume, repetitive deductions on its own and escalates the genuinely ambiguous cases to a person, while keeping the rest of the backlog moving across the whole ledger. Fewer aged deductions means a lower DDO and less cash trapped in unresolved disputes. See how Rex runs collections end to end.