Accounts Payable Days (DPO): Formula, Examples, Benchmarks

Accounts payable days (also called Days Payable Outstanding, DPO) measures how many days, on average, your company takes to pay suppliers. The quick formula is DPO = (Average Accounts Payable ÷ Cost of Goods Sold) × Number of days (e.g., 365). A healthy DPO typically aligns with your vendor terms and industry norms—higher preserves cash but risks supplier strain; lower strengthens relationships and can capture discounts.

Use it to see how efficiently you manage payables, plan cash needs, and benchmark against peers. A quick read of your vendor terms tells you whether your accounts payable days are too high (potential late fees or vendor friction) or too low (you might be tying up cash and missing interest or alternative uses). If you change DPO by 1 day, the cash impact is roughly your daily spend times that day change.

Accounts payable days (DPO): the 2‑minute answer

Here is the fast, finance-team way to get value from DPO without diving into a long accounting manual.

Definition: accounts payable days estimates the average time you take to settle trade payables. It is commonly labeled Days Payable Outstanding in dashboards and filings.

Standard formula: DPO = (Average Accounts Payable ÷ Cost of Goods Sold) × Period Days. Average Accounts Payable is usually (Beginning A/P + Ending A/P) ÷ 2. Period Days are typically 365 for a full year, 366 in leap years, the exact count of days for a quarter, or the exact days in a month.

One‑line example: if Average A/P is 500,000, annual COGS is 6,000,000, and you use 365 days, then DPO = (500,000 ÷ 6,000,000) × 365 ≈ 30.4 days.

What “good” looks like: aim to be in line with supplier terms and your industry’s normal range. A higher DPO preserves cash and can be a deliberate working capital strategy, but push it too far and you may face strained relationships, fewer allocations in tight markets, late fees, or reduced fill rates. A lower DPO builds trust and can earn discounts, but it consumes more cash up front.

Quick impact math: Cash impact of a DPO change ≈ Daily purchases (or daily COGS) × change in days. Example: if daily purchases average 20,000 and you raise DPO by 5 days, you may free roughly 100,000 of cash; if you lower DPO by 5 days to capture discounts, plan for that temporary 100,000 cash use.

How to calculate accounts payable days step by step

Follow these steps to calculate DPO accurately and in a way that matches your business rhythm.

1. Choose the period. Annual is most common for external reporting, but quarterly or monthly DPO helps operators see changes sooner.
2. Collect beginning and ending Accounts Payable (trade payables only). Exclude non-trade items such as accrued payroll or taxes if they are not part of supplier purchases.
3. Compute Average A/P = (Beginning A/P + Ending A/P) ÷ 2. If your balances are volatile, consider a rolling average (e.g., monthly averages across the quarter) to avoid distortion.
4. Select the denominator. Start with COGS for inventory-heavy firms. If you have reliable data for total credit purchases from suppliers, that is often a better denominator. Pure service firms may use operating expenses that flow through A/P.
5. Select the number of days in the period. Use 365 or 366 for a year, about 90 or the exact count for a quarter, and the exact day count for a month.
6. Calculate DPO = (Average A/P ÷ chosen denominator) × period days.
7. Sanity-check against vendor terms and industry benchmarks. If your main suppliers have Net 30 terms and you show 62 days, investigate why.
8. Note special situations like early-payment discounts or late fees so you interpret DPO in context.

Worked annual example: Beginning A/P = 420,000; Ending A/P = 580,000; Average A/P = 500,000. Annual COGS = 6,000,000. DPO = (500,000 ÷ 6,000,000) × 365 = 30.4 days. If your largest suppliers are on Net 30, that result aligns with terms.

Back-of-the-envelope monthly example: Ending A/P this month is 610,000; last month’s ending A/P was 590,000; take a quick average ≈ 600,000. If you estimate monthly credit purchases at 2,400,000, your daily purchases are roughly 2,400,000 ÷ 30 = 80,000. DPO ≈ (600,000 ÷ 2,400,000) × 30 = 7.5 days for the month. Note how monthly DPO can look low if purchases spiked late in the month or if invoices have not yet hit A/P.

Seasonality and practicality: If your business is highly seasonal, quarterly DPO (or a 3‑ or 6‑month rolling view) is less distorted than a single month. Always match the period of A/P to the period of your denominator; do not mix a monthly A/P average with a full-year COGS in the same calculation unless you are explicitly computing an annualized DPO.

Choosing the right denominator: COGS vs purchases vs operating spend

Textbooks use COGS in the DPO formula, but one size does not fit all. Here is how to choose and what to watch.

Business type / use case	Formula	Data required	Pros	Cons	When not to use
Inventory-heavy (retail, wholesale)	DPO = Avg A/P ÷ COGS × days	Average A/P; COGS for the same period	Simple, widely understood; aligns to P&L	COGS reflects what you sold, not what you bought; inventory swings can distort	When inventory levels are changing rapidly or you had large buy-ahead
Manufacturing with stable BOMs	DPO = Avg A/P ÷ Total credit purchases × days	Supplier purchase ledger or AP subledger with credit purchases	Most direct link to A/P; avoids inventory timing effects	Harder to source consistently; needs clean purchasing data	When credit purchase data is unreliable or incomplete
Services / SaaS (minimal COGS)	DPO = Avg A/P ÷ Operating expenses paid via A/P × days	Operating expense detail tied to A/P (exclude payroll/benefits run outside A/P)	Better reflection of what actually flows through A/P	Requires careful exclusions; less comparable to product companies	When a large share of expenses bypasses A/P (e.g., payroll, card)
Project-based firms	DPO = Avg A/P ÷ Purchases for projects × days	Job-cost purchase data and A/P mapping	Aligns DPO to project cash realities	More work to maintain mappings by project	When projects run on prepayments that do not hit A/P

Common pitfalls while choosing a denominator:

• Freight, taxes, and duties: include them only if they flow through A/P and are part of supplier invoices. If they sit in accruals, keep them out.
• Capital purchases: do not put CapEx into the denominator unless your intent is to study total payables days across all vendors; typical DPO focuses on operating trade payables.
• Expenses not routed through A/P: card charges or payroll run elsewhere do not belong in the denominator.

Estimation tip: If you cannot easily extract total credit purchases, many operators use COGS as a practical proxy, then add commentary on inventory changes. A short footnote such as “Inventory increased by 900,000 this quarter” helps readers interpret COGS‑based DPO.

Interpreting high vs low accounts payable days

High DPO can be good or bad depending on context. Use the trade‑offs below to set a smart target.

• Benefits of a higher DPO: more on‑hand cash, flexibility for growth investments, stronger liquidity ratios, and a buffer during demand dips.
• Risks of a higher DPO: strained supplier relationships, late fees, missed allocations in constrained markets, potential hold on shipments, and lower service levels.
• Benefits of a lower DPO: access to early‑payment discounts, stronger vendor trust, better allocation priority, and potentially better pricing over time.
• Risks of a lower DPO: more cash tied up in operations, higher working capital needs, and less flexibility for opportunities or shocks.

Benchmarks vary by sector and by your specific supplier mix. Use the following ranges only as directional signposts.

Sector	Typical DPO range	Notes
Retail (multi-category)	30–60 days	Common Net 30–Net 60 terms; large chains may secure longer terms
Wholesale distribution	40–65 days	Mix of Net 30–Net 60; rebates and dating can shift effective DPO
Manufacturing	40–70 days	Often aligns to production cycles and supplier bargaining power
Food and beverage	20–40 days	Perishables and fast turns lead to shorter DPO
Construction	35–75 days	Project billing cycles and retainage rules matter
Services / SaaS	15–35 days	Limited COGS; many expenses routed via card or payroll
Healthcare providers	45–75 days	Complex payor cycles and large vendor bases
Utilities	30–50 days	Stable supplier contracts and regulated environments

Link to the cash conversion cycle (CCC): CCC = DSO + Inventory Days − DPO. A higher DPO reduces CCC and often lowers the cash needed to run the business, all else equal. Adjust DPO targets in concert with receivables and inventory initiatives so the whole system improves together.

Improve DPO without hurting suppliers

Optimizing DPO is about discipline, not delaying payments blindly. Start with terms alignment, then fix process bottlenecks, and finally use the right payment tools.

Negotiate terms ethically:

• Anchor to lead times, reliability, and order size. For a high‑volume, forecastable item, asking to move from Net 30 to Net 45 may be reasonable.
• Offer value in return: provide longer purchase commitments, faster dispute resolution, or consolidated orders for better logistics.
• Consider tiered terms by vendor criticality. Strategic suppliers may keep shorter terms while long‑tail vendors move to standard longer terms.

Process fixes that reduce friction and errors:

• Adopt three‑way match for POs, receipts, and invoices to eliminate disputes.
• Use no‑PO‑no‑pay for categories that should always require a purchase order.
• Set clear approval SLAs so invoices do not age internally while waiting for sign‑off.
• Batch payment runs on predictable cycles. Predictability helps both sides plan cash.
• Standardize vendor master data and require electronic invoices to accelerate capture.

Automation and payment methods:

• Implement invoice capture and workflow tools that integrate with your ERP. For managers exploring broader process efficiency, see the Business Process Optimization playbook and our guide on Business Process Management.
• Use ACH batching to run weekly or semi‑monthly payments. Consider virtual cards for eligible invoices that can add rebates while keeping predictable timing.
• Explore dynamic discounting or supply chain finance so suppliers who want early cash can get it at transparent rates without compressing your standard terms.

Discount breakeven math: When a vendor offers 2/10, Net 30, the implied annualized rate for taking the discount is approximately:

APR ≈ (Discount ÷ (1 − Discount)) × (365 ÷ (Full term − Discount term)). For 2/10, Net 30, APR ≈ (0.02 ÷ 0.98) × (365 ÷ 20) ≈ 37 percent. If your alternative use of cash cannot exceed that effective return (after factoring risk and fees), paying on day 10 to take the discount may be the better choice even though it lowers DPO.

Cash planning tip: If you extend average DPO by 5 days across 12,000,000 in annual credit purchases (about 32,877 per day), you may free about 164,385 of cash. If you shorten DPO by 5 days to capture discounts, plan and approve the incremental working capital draw in advance.

For a broader finance toolkit that pairs well with DPO decisions, review Mastering Financial Management Strategies for Entrepreneurs.

Examples: retailer, manufacturer, and services business

Each sector uses DPO slightly differently because the denominator and timing differ.

Retailer example (COGS‑based): A chain sells consumer goods with annual COGS of 48,000,000. Beginning A/P is 3,800,000 and Ending A/P is 4,600,000; Average A/P = 4,200,000. Annual DPO = (4,200,000 ÷ 48,000,000) × 365 ≈ 31.9 days. Typical retail ranges are 30–60 days, so 31.9 days is within norms. If the chain negotiates select Net 45 agreements and tightens invoice approvals, moving DPO to 36 days could free roughly 48,000,000 ÷ 365 × 4.1 ≈ 539,726 of cash.

Manufacturer example (purchases‑based): A mid‑market manufacturer shows total credit purchases from suppliers of 60,000,000 this year. Beginning A/P is 6,000,000 and Ending A/P is 8,400,000; Average A/P = 7,200,000. DPO = (7,200,000 ÷ 60,000,000) × 365 ≈ 43.8 days. If inventory grew materially due to a new product launch, COGS would have understated purchases and overstated DPO if used as the denominator, which is why the purchases-based approach is preferred here. The firm might target 50 days by standardizing Net 45 across non‑critical suppliers and using supply chain finance to give strategic vendors early‑payment options without compressing standard terms.

Services / SaaS example (operating‑spend‑based): A SaaS company routes vendor invoices for cloud hosting, marketing, and professional services through A/P; payroll and card expenses sit outside A/P. Operating expenses through A/P total 24,000,000. Beginning A/P is 1,200,000 and Ending A/P is 1,500,000; Average A/P = 1,350,000. DPO = (1,350,000 ÷ 24,000,000) × 365 ≈ 20.5 days. This fits common service‑industry ranges. The business could push to 25 days by moving from weekly to semi‑monthly payment runs and by adopting standard Net 30 for long‑tail vendors while keeping critical suppliers at Net 15 or Net 30.

Common mistakes and how to avoid them

• Mismatched periods. Using monthly Average A/P with annual COGS in the same calculation gives an annualized value that is easy to misread. Match periods or explicitly label the result as annualized.
• Not averaging A/P. Relying on ending A/P only can overstate or understate DPO depending on cutoff timing.
• Using COGS when purchases swing heavily. If you bought ahead of a promotion and inventory rose sharply, COGS‑based DPO will look inflated. Use purchases if available.
• Including non‑A/P items. Exclude payroll, card expenses, and accruals that do not pass through A/P from the denominator.
• Counting calendar vs business days inconsistently. DPO is calendar‑day based; do not switch between the two without noting it.
• Ignoring seasonality. A single month’s DPO can look odd after large inventory movements; use rolling averages or quarterly views to smooth.
• Confusing due dates with liability classification. A payable due in 30 days is a current liability by definition because it is due within a year; that classification is separate from DPO.
• Not separating discounts and late fees when interpreting DPO. A low DPO might be good if you consistently earn discounts; a high DPO might be bad if it includes late charges.

Related metrics: DSO, inventory days, and the cash conversion cycle

DPO is one leg of a three‑part working capital story. Track all three for a coherent picture.

• Days Sales Outstanding (DSO): average time to collect cash from customers. A common formula is DSO = (Average A/R ÷ Revenue) × period days. If you want a quick refresher on designing process improvements around receivables, see our Operational Excellence framework.
• Inventory Days (DIO): average days inventory sits before sale. A common formula is DIO = (Average Inventory ÷ COGS) × period days.
• Cash Conversion Cycle (CCC): CCC = DSO + DIO − DPO. Lower is generally better because it means fewer days of cash tied up.

Mini example across metrics: Suppose DSO = 42 days, DIO = 58 days, and DPO = 36 days. CCC = 42 + 58 − 36 = 64 days. If you can improve DPO by 5 days while also reducing DIO by 3 days via better replenishment, CCC drops to 56 days, reducing working capital needs and interest expense exposure.

Quick answers to common questions

• What does “days in accounts payable” mean? It is the same concept as DPO: the average number of calendar days you take to pay suppliers.
• How do you calculate DPO for a month or quarter? Use the exact days in the month or quarter, average the A/P over that same period, and use period purchases or COGS for the same period. You can display a monthly figure or an annualized figure; label clearly.
• Is a payable due in 30 days a current liability? Yes, payables due within a year are classified as current liabilities in standard accounting.
• Should I use COGS or purchases to calculate DPO? Use purchases if your system can reliably report credit purchases; use COGS as a practical proxy when purchase data is not clean, noting any inventory swings.
• How do I calculate days outstanding accounts receivable (DSO)? DSO ≈ (Average Accounts Receivable ÷ Revenue) × period days; many firms also compute a collections effectiveness index for nuance.