The speed at which your organization pays suppliers affects more than individual invoices. It shapes cash flow, influences financial planning, and determines how suppliers view you as a customer. Days payable outstanding (DPO) is the metric that captures all of this in a single number — and understanding it is one of the most practical things an AP team can do to improve how the business runs.
This guide covers how to calculate DPO correctly, what affects it, common mistakes to avoid, and how to improve it.
Key highlights:
- DPO measures the average number of days an organization takes to pay suppliers after receiving an invoice
- It is calculated by dividing average accounts payable by cost of sales and multiplying by 365
- Organizations improve DPO by reducing invoice processing delays, automating approvals, and aligning payments with cash flow forecasts
- ExFlow for Microsoft Dynamics 365 reduces DPO by eliminating AP bottlenecks and giving finance teams real-time visibility into payables
What Is Days Payable Outstanding (DPO)?
Days payable outstanding measures how many days, on average, it takes your organization to pay suppliers after receiving an invoice. The formula is: average accounts payable divided by cost of sales, multiplied by 365.
The result tells you how long cash stays in the business before being paid out.
A high DPO means you're holding cash longer, which supports working capital and short-term liquidity. A lower DPO means you're paying suppliers faster, which can strengthen relationships but reduces available cash.
Neither is inherently good or bad. The right DPO depends on your industry, supplier mix, and financial strategy.
Why DPO Matters for AP Teams
Every payable decision has consequences beyond the immediate invoice. Here's why AP teams need a clear, real-time picture of DPO.
Working Capital
Working capital is current assets minus current liabilities. DPO determines how long cash tied to payables stays available before leaving the business. If your organization collects from customers faster than it pays suppliers, that gap creates a cash window you can use for operations, payroll, or debt service.
Finance teams should set DPO targets, audit inputs like AP aging reports and supplier master data, and monitor results against budget assumptions.
Supplier Relationships
According to a SAP survey, 51% of suppliers report that buyers are typically late with payments. Delays beyond contracted terms damage vendor relationships and can result in stricter credit conditions, prepayment demands, or higher costs over time.
Paying on time demonstrates reliability, builds trust, and can secure benefits like better pricing or priority on limited inventory. Consistently stretching DPO beyond agreed terms creates the opposite effect.
Financial Planning
Accurate DPO helps finance teams understand when cash actually needs to leave the business. Mapping payables into short-term forecasts — such as a 13-week cash flow — gives AP visibility into when invoices convert to payments. Factoring in delays from invoice coding errors, missing purchase orders, or exception queues improves forecast accuracy.
Benchmarking
According to data from the American Productivity & Quality Center (APQC), the average DPO across all industries is around 40 days. Individual results vary widely by sector. Manufacturers with large supplier bases often sustain longer payment terms than service businesses with fewer vendors.
Benchmarking against peers gives context for whether your DPO reflects sound management or signals risk.
Factors That Affect DPO
| Factor |
Impact on DPO |
| Payment terms and policies |
Longer contractual terms increase DPO; shorter terms decrease it |
| Supplier relationships |
Strong vendor trust can allow extended payment cycles; weak relationships often shorten them |
| Industry standards |
Industries with slower turnover, like manufacturing, typically show higher DPO than fast-cycle sectors |
| Company size |
Larger firms often negotiate longer terms; smaller companies typically face shorter ones |
| Seasonal fluctuations |
Busy seasons may extend payables and raise DPO; slow periods usually shorten them |
How to Calculate DPO
The formula is: (Average Accounts Payable ÷ Cost of Sales) × 365
To see it in action: Apple reported accounts payable of about 69.0 billion USD in 2024 and 62.6 billion USD in 2023, giving an average of 65.8 billion USD. Dividing by roughly 210.4 billion USD in cost of sales and multiplying by 365 gives a DPO of about 114 days. For context, other major PC and hardware vendors such as Lenovo, Dell, and HP show materially different DPO levels in their latest filings, underlining how approaches to managing payables can vary significantly even within the same industry
Common DPO Calculation Mistakes
1. Using the wrong data
DPO is only as reliable as the numbers feeding it. Common errors include using total operating expenses instead of cost of sales, or failing to average accounts payable across two periods. To avoid this: confirm cost of sales is used in the denominator, calculate average AP using at least two consecutive periods, and reconcile data with audited financial statements before running the calculation.
2. Mismatched time periods
Comparing quarterly payables data against annual cost of sales distorts the result. Match the reporting periods for both inputs, standardize when you run the calculation, and document the chosen period so results are consistent over time.
3. Misreading the result
A high DPO isn't automatically bad, and a low one isn't automatically good. A high figure might reflect a deliberate working capital strategy — or it might mean invoices are stuck in exception handling. Always benchmark against peers in your industry, factor in your negotiated supplier terms, and use DPO as one of several inputs when evaluating payables performance.
4. Ignoring seasonal patterns
DPO often shifts during high-demand periods. Retailers may extend payables during peak seasons and shorten them in slower months. Calculate DPO for the same seasonal period year over year, and segment results by quarter or business cycle to surface real trends.
How to Reduce DPO
For AP teams looking to shorten their payment cycle and improve DPO:
Streamline approval processes. Sign-off bottlenecks are one of the most common causes of extended DPO. Setting clear thresholds — for example, auto-approving invoices below a defined amount while routing higher-value items to the right approver — keeps invoices moving without creating risk.
Automate invoice processing. Manual processes introduce delays and errors at every stage. Accounts payable automation captures invoice data, validates it against purchase orders and vendor master data, flags discrepancies, and schedules payments without manual intervention.
Negotiate better payment terms. Vendors may be willing to adjust terms in exchange for consistent, on-time payments. Early payment discount programs, volume agreements, or loyalty arrangements can shorten settlement windows while strengthening the supplier relationship.
Implement strategic payment schedules. Coordinating disbursements with cash flow forecasts prevents unnecessary delays. Standard pay runs, payment dates aligned with receivables, and early approval processes keep DPO at targeted levels.
DPO Best Practices
Set the right targets
Targets should reflect your industry norms, company size, and supplier mix. Benchmark against peers to keep targets realistic. Factor in your bargaining power with suppliers — larger organizations can often negotiate extended terms, while smaller ones may need more conservative targets. Revisit targets regularly as supplier terms or market conditions shift.
Balance DPO with supplier relationships
Monitor how often payments meet agreed terms. Persistent delays erode vendor trust and can result in tighter credit conditions. Offer early payments selectively where discounts or strategic benefits are available. Be transparent about changes to payment cycles — predictability builds trust even when adjustments aren't in the supplier's favor.
Monitor regularly
DPO should be tracked alongside other working capital metrics. Dashboards should display DPO alongside invoice processing timelines, exception rates, and approval bottlenecks. Conduct monthly or quarterly reviews to catch shifts early, and benchmark against external peers to understand whether your results reflect efficiency or signal problems.
Align DPO with financial strategy
DPO policies should serve long-term goals, not just short-term cash needs. Embed targets into budgets and forecasts so they align with the organization's financial strategy. Evaluate how DPO affects credit agreements and borrowing capacity. And test whether current payables policies enable the business to scale — practices that work for stability may need adjusting in growth mode.
Improve DPO with AP Automation for Microsoft Dynamics 365
Truvio AP Automation powered by Exflow offers a direct path to improving DPO by eliminating the bottlenecks that slow AP processing. Fully embedded in Microsoft Dynamics 365 Finance & Operations and Business Central, it gives finance teams real-time visibility into payables and cash forecasts, so payment schedules can be managed proactively rather than reactively.
Key capabilities that directly affect DPO:
- Automated invoice data capture and validation that removes manual errors and accelerates processing
- Workflow-driven approvals that speed internal reviews and ensure payments are released on time
- E-invoicing and payment integration that simplifies settlements and shortens the overall payment cycle
- Vendor statement reconciliation that resolves discrepancies quickly and prevents payment delays
- Real-time reporting that gives AP teams the data to align payables strategy with cash flow management
Book a demo to see how Truvio AP Automation can help your organization reduce days payable outstanding.
Frequently Asked Questions
What is the difference between DSO and DPO? Days sales outstanding (DSO) measures how quickly a company collects payments from customers, while DPO measures how long it takes to pay suppliers. Together they reveal the timing gap between inflows and outflows, which shapes working capital efficiency and the overall cash conversion cycle.
How often should I calculate DPO? At least quarterly to align with financial reporting, though monthly reviews provide more actionable insight. Frequent tracking helps identify shifts caused by seasonality, policy changes, or supplier terms.
What is a good DPO? There is no universal answer. Appropriate values depend on industry norms, company size, and supplier agreements. The APQC cross-industry average is around 40 days, but manufacturing or technology firms often sustain much higher figures without signaling financial risk or supplier strain.
.svg "truvio_logo"){kind=small}
