Days Payable Outstanding Formula for Finance Teams

The days payable outstanding formula helps finance teams understand how long the business takes to pay suppliers, contractors, vendors, and other creditors. It is simple to calculate, but easy to misread. A higher number can mean the company is preserving cash effectively. It can also mean invoices are stuck, suppliers are waiting too long, or payment approvals are not working.

For finance operators, the useful question is not only “What is our DPO?” The better question is “What does our DPO say about supplier terms, invoice intake, approvals, payment runs, and cash forecasting?” This guide explains the formula and the operating system behind the number.

What’s in this article?

• The days payable outstanding formula and a simple example
• What a high or low DPO usually means
• How DPO connects to cash flow and the cash conversion cycle
• A practical workflow for reviewing and improving DPO
• Common mistakes finance teams should avoid

Days payable outstanding formula

Days payable outstanding measures the average number of days a company takes to pay suppliers after receiving goods or services. A common version of the formula is:

DPO = Average accounts payable divided by cost of goods sold, multiplied by number of days in the period.

Allianz Trade describes DPO in similar terms: accounts payable divided by cost of goods sold, multiplied by the number of days in the period. Some companies use purchases or cost of revenue instead of COGS when that better matches the business model. Pick the denominator that reflects the spend base you manage, then use it consistently.

Example: if average accounts payable is $600,000, annual cost of goods sold is $4,800,000, and the period is 365 days, DPO is 45.6 days. In plain English, the business is taking about 46 days to pay suppliers on average.

Why DPO matters for finance operations

DPO is part of working capital management. J.P. Morgan explains that DSO and DPO both affect cash flow because they show how quickly cash comes in from customers and how quickly cash goes out to suppliers. DPO also feeds into the cash conversion cycle.

That does not mean the best DPO is always the highest DPO. Stretching payments can preserve cash, but it can also create late fees, supplier escalation, service disruption, damaged vendor relationships, and missed early-payment discounts. A low DPO may show supplier discipline, or it may show the company is paying too quickly.

The right DPO depends on supplier terms, industry norms, cash position, growth stage, and vendor concentration. APQC’s accounts payable benchmarking resources are useful because AP metrics should be compared against process maturity and peer context, not treated as universal targets.

How to interpret high and low DPO

A monthly DPO review workflow

A useful DPO review is a workflow, not a spreadsheet ritual. Finance should run it monthly, and faster-growing teams may need a weekly view during tight cash periods.

1. Calculate DPO consistently. Use average AP and the same spend base each period.
2. Segment by vendor group. Separate contractors, strategic suppliers, software vendors, agencies, logistics providers, and one-time vendors.
3. Compare DPO to payment terms. A 45-day DPO is healthy if most suppliers are net 45. It is risky if key suppliers are net 15.
4. Review stuck invoices. Identify invoices waiting on intake data, PO match, manager approval, dispute resolution, or bank-detail verification.
5. Check payment-run timing. Confirm whether payment batches align with due dates, cash forecasts, discount windows, and vendor priority.
6. Investigate exceptions. Look for duplicate invoices, missing POs, receiving questions, tax documentation gaps, or supplier master data issues.
7. Decide the policy change. Improve terms, change approval thresholds, automate reminders, split payment runs, or create a tighter escalation path.

How finance teams can improve DPO

Improving DPO does not mean making every vendor wait longer. The stronger approach is to make payment timing intentional.

Negotiate clear supplier terms. Finance cannot manage DPO well if supplier terms live in email threads. Keep terms in the vendor record and connect them to invoice due dates.

Centralize invoice intake. Invoices that arrive through individual inboxes create timing noise. A shared intake route makes it easier to timestamp receipt, catch duplicates, and route approvals.

Automate approvals without removing judgment. The goal is not blind payment automation. It is faster routing for ordinary invoices and visible escalation for exceptions. Payment risk remains real: the AFP 2026 Payments Fraud and Control Survey page highlights continuing concern around business payment fraud and controls.

Use payment runs instead of ad hoc payments. Scheduled payment runs help treasury manage cash while keeping suppliers informed. Emergency payments should be rare, documented, and reviewed.

Review discount tradeoffs. Sometimes a lower DPO is better if the business earns meaningful early-payment discounts or protects a critical supplier relationship.

Common DPO mistakes

• Chasing a higher DPO without context. Delayed payments can look efficient while damaging supplier reliability.
• Using inconsistent inputs. Switching between COGS, purchases, and cost of revenue makes trends unreliable.
• Ignoring vendor segments. Contractor payments, inventory suppliers, agencies, and software vendors often need different timing rules.
• Confusing approval delays with payment strategy. Late approvals are not working-capital management.
• Leaving exceptions invisible. The most important DPO changes often come from disputed invoices, missing receipts, and stale vendor data.

Where Workhint fits

Workhint helps teams turn DPO management into an operating workflow. A finance team can structure vendor intake, supplier terms, invoice routing, approval thresholds, payment-run readiness, exception handling, and reconciliation in one system. DPO improves when invoice work is visible: who owns the approval, what is missing, whether payment is blocked, and when finance should release funds.

For teams paying contractors, vendors, agencies, or marketplace participants across locations, Workhint can connect operational approvals to payment status and documentation. It gives finance, operations, and approvers a shared workflow so payment timing is deliberate instead of accidental.

FAQ

What is a good days payable outstanding number?

A good DPO depends on your industry, supplier terms, cash position, and vendor relationships. Compare your DPO to agreed payment terms and peer benchmarks rather than chasing one universal target.

Should DPO be high or low?

Neither is automatically better. Higher DPO can preserve cash, but too high may mean late payments. Lower DPO can protect suppliers or capture discounts, but too low may weaken working capital.

How often should finance calculate DPO?

Most teams should review DPO monthly. Teams with tight cash, rapid growth, large supplier bases, or marketplace payouts may need weekly operational reviews alongside monthly financial reporting.

Can payment automation improve DPO?

Yes, when automation reduces invoice delays, standardizes approvals, flags exceptions, and schedules payments around due dates. Automation should strengthen controls, not simply speed every payment.

Conclusion

The days payable outstanding formula is useful because it turns supplier payment timing into a measurable finance signal. But the number only becomes valuable when finance can explain why it moved. Strong teams connect DPO to supplier terms, invoice intake, approvals, payment runs, exceptions, fraud controls, and cash forecasting. That is how DPO becomes more than a ratio. It becomes a practical lever for healthier finance operations.