Days payable outstanding is one of the three levers of working capital, and the one finance teams most often misunderstand. The instinct is to maximize it, pay as late as possible to hold onto cash, but that instinct is wrong as often as it is right, because paying late can forfeit early-payment discounts worth more than the cash held and can damage supplier relationships that matter. DPO is not a number to maximize; it is a number to optimize. Here is what DPO is, the real trade-offs in managing it, and how AI helps optimize payment timing rather than just stretch it.
TL;DR
Days payable outstanding (DPO) measures the average number of days a company takes to pay its suppliers after receiving an invoice. It is a key working-capital metric: a higher DPO means the company holds onto its cash longer, effectively using supplier credit to finance operations, which improves working capital, while a lower DPO means it pays faster. DPO is one of the three components of the cash conversion cycle (CCC = DSO + DIO − DPO), and the only one that is subtracted, because deferring supplier payment offsets the cash tied up in receivables and inventory.
DPO is calculated as (average accounts payable / cost of goods sold) × number of days. A higher DPO generally improves working capital, but, crucially, maximizing DPO is not the goal. Extending payment too far carries real costs: forfeiting early-payment discounts (which can be worth more than the cash retained), damaging supplier relationships and your standing as a customer, and risking late-payment penalties or supply disruption. So DPO should be optimized, paying at the right time for the best overall outcome, not simply maximized by paying as late as possible.
The optimal DPO balances several factors: the value of holding cash longer, the value of early-payment discounts when offered (which can have a high effective annualized return), the importance of the supplier relationship, and the agreed payment terms. The right payment timing differs by invoice and supplier, which is what makes DPO optimization a decision problem, not just a matter of paying late.
AI helps optimize DPO by enabling deliberate, informed payment-timing decisions rather than paying whenever invoices happen to clear a manual process. AI-driven AP automation processes invoices efficiently so payment timing becomes a choice, surfaces early-payment-discount opportunities and their economics, and supports paying each invoice at its optimal time, capturing discounts where they pay and extending payment where they do not. This turns DPO from an accidental outcome of how fast AP happens to work into a managed working-capital lever.
This post covers what DPO is, how to calculate it, why maximizing it is the wrong goal, and how AI optimizes it. For the full working-capital context, see What Is the Cash Conversion Cycle, and How Does AI Improve It?
What days payable outstanding is
Days payable outstanding measures, on average, how many days a company takes to pay its suppliers after receiving their invoices. It captures the company's payment behavior on the spend side: a high DPO means the company takes a long time to pay (holding cash longer), and a low DPO means it pays quickly.
DPO matters for working capital because the time between receiving goods or services and paying for them is, in effect, free financing from suppliers. While an invoice is unpaid, the company has the use of that cash, so extending the time to pay (a higher DPO) keeps more cash in the business for longer, reducing the working capital the company needs to fund its operations. This is why DPO is one of the three levers of the cash conversion cycle, and the one that is subtracted: deferring supplier payments offsets the cash that is tied up waiting for customers to pay (DSO) and waiting for inventory to sell (DIO). A company that pays suppliers slowly, collects from customers quickly, and turns inventory fast has a short, even negative, cash conversion cycle.
It sits opposite DSO on the cash cycle: DSO is how long the company waits to be paid by customers, DPO is how long the company makes its suppliers wait to be paid. Both affect working capital, but in opposite directions, lower DSO and higher DPO each improve it, which is why the two are often discussed together as the receivables and payables levers of working capital. The relationship between the two, and with inventory, is detailed in What Is the Cash Conversion Cycle.
How to calculate DPO
The formula is:
DPO = (Average accounts payable ÷ Cost of goods sold) × Number of days
Average accounts payable is the average balance of what the company owes suppliers over the period (often the average of beginning and ending AP). Cost of goods sold (COGS) represents the purchases the payables relate to (some calculations use total purchases instead of COGS for a closer match). The number of days is the period length (365 for a year, 90 for a quarter).
A worked example: if average accounts payable is $2 million, COGS is $16 million, and the period is a year (365 days):
DPO = ($2M / $16M) × 365 = 45.6 days
The company takes about 46 days, on average, to pay its suppliers.
Interpreting the number: a higher DPO means the company takes longer to pay (holding cash longer, generally better for working capital, within limits), and a lower DPO means it pays faster. DPO is most meaningful compared to the company's own trend over time and to industry peers, since typical payment terms and norms vary by industry. A DPO that is rising over time means the company is paying more slowly (extending its supplier financing), while a falling DPO means it is paying faster. The DPO should also be read against the company's agreed payment terms: a DPO well above the standard terms the company has negotiated may indicate it is paying late (beyond terms), which carries the costs discussed next.
Why maximizing DPO is the wrong goal
The intuitive view of DPO is that higher is always better: pay as late as possible to hold onto cash. This is the most common DPO misconception, and it is wrong, because extending payment too far carries real costs that can outweigh the benefit of holding cash.
Forfeiting early-payment discounts. Many suppliers offer discounts for early payment (for example, 2% off for paying within 10 days instead of 30). These discounts often have a high effective annualized return: taking a 2% discount to pay 20 days early is equivalent to a very high annual rate of return on the cash, far higher than the company would earn holding the cash. Maximizing DPO by always paying late forfeits these discounts, which is frequently a worse financial outcome than paying early to capture them. So a high DPO achieved by skipping valuable discounts can actually cost money.
Damaging supplier relationships. Suppliers notice how they are paid. A company that consistently pays slowly, or stretches payments beyond agreed terms, becomes a less attractive customer, which can lead to worse terms, lower priority during shortages, reluctance to extend credit, or strained relationships that matter when the company needs supplier flexibility. The value of being a good customer, especially with key suppliers, can exceed the working-capital benefit of paying slowly.
Late-payment penalties and disruption. Paying beyond agreed terms can incur late fees or interest, and in the extreme can prompt suppliers to withhold goods or services, disrupting operations. Stretching DPO past what terms allow turns a working-capital tactic into an operational risk.
The result is that DPO should be optimized, not maximized. The goal is to pay each invoice at the time that produces the best overall outcome, weighing the value of holding cash against the value of any discount, the importance of the supplier relationship, and the agreed terms. Sometimes that means paying early (to capture a worthwhile discount or support a key supplier); sometimes it means paying at the full term (to hold cash without cost); rarely does it mean paying late beyond terms. Maximizing DPO blindly ignores these trade-offs and often produces a worse result than thoughtful optimization.
What optimal DPO looks like
Because DPO should be optimized rather than maximized, the optimal DPO is not a single high number but the result of paying each invoice at its best time, which varies by invoice and supplier.
The factors that determine the optimal timing for a given invoice: the value of holding the cash longer (higher when cash is constrained or has high alternative use), the value of any early-payment discount offered (often high on an annualized basis, favoring early payment when a good discount is available), the importance and leverage of the supplier relationship (favoring timely or early payment for key or sensitive suppliers), and the agreed payment terms (which set the boundary of paying on time versus late). Weighing these, the optimal action might be to pay early (capture a strong discount or support a key supplier), pay at term (hold cash at no cost when no worthwhile discount applies), or, only deliberately and within terms, pay at the latest allowed date.
At the portfolio level, optimal DPO management means making these decisions systematically across all invoices: capturing the discounts worth capturing, holding cash where it pays to, protecting the key supplier relationships, and not paying late beyond terms unless deliberately chosen. The resulting blended DPO reflects optimized timing across the payables, which is generally healthier than either a low DPO (paying everything early, giving up cash unnecessarily) or an indiscriminately high DPO (paying everything late, forfeiting discounts and straining relationships). Optimal DPO is a managed outcome of good payment-timing decisions, not a target number to push as high as possible.
How AI optimizes DPO
AI improves DPO management by making payment timing a deliberate, informed decision rather than an accident of how fast invoices happen to move through AP. The contributions:
Making payment timing a choice, not an accident
In a manual AP process, payment timing is often determined by how long invoices take to process: an invoice that sits in an exception queue gets paid late not by choice but by delay, while others get paid whenever they happen to clear. AI-driven AP automation processes invoices efficiently and predictably (including the exceptions that otherwise stall, such as non-PO invoices and mismatches), so the company can pay each invoice when it chooses to, turning payment timing from an accidental outcome into a managed decision. This is the foundational contribution: you cannot optimize DPO if you cannot control when invoices are ready to pay.
Surfacing discount opportunities and their economics
AI can identify which invoices carry early-payment discounts and surface the economics, the effective return of taking the discount versus holding the cash, so the company captures the discounts worth capturing and skips the ones that are not. Manual processes often miss discounts simply because the invoice was not processed in time to take them, which AI prevents by processing promptly and flagging the opportunity.
Supporting optimal timing decisions
AI can help determine and execute the optimal payment timing per invoice, weighing the factors above (discount value, cash value, supplier importance, terms), and schedule payments accordingly, so the payables portfolio is paid on an optimized schedule rather than a haphazard one. This operationalizes DPO optimization across the volume of invoices.
Enabling cash-aware payment timing
Because AI can connect AP to the broader cash picture, payment timing can be made cash-aware, accelerating or extending payments (within terms) in light of the company's cash position and forecast, which links DPO management to liquidity management. For a fuller view of how AI connects working-capital metrics, see The Top AI Cash Flow Forecasting Tools for Treasury Teams.
The net effect is to turn DPO from an accidental byproduct of AP processing speed into a deliberately managed working-capital lever, capturing the discounts worth capturing, holding cash where it pays to, and paying on time, rather than paying late by default or early by accident. AI does not decide the company's payment strategy, that is a business decision about how the company wants to balance cash, discounts, and relationships, but it enables the strategy to be executed deliberately and consistently across all invoices.
This is where AP automation connects to DPO: the efficient, reliable invoice processing that AP automation provides is the precondition for deliberate payment timing, which is the precondition for optimized DPO. Kognitos contributes here through the AP exception processing that makes invoice timing controllable, handling the exceptions that otherwise leave invoices stuck and paid late by delay rather than choice, so payment timing becomes a decision. Kognitos is not a treasury or working-capital management tool and does not set payment strategy; its relevance is the AP processing layer that makes deliberate payment timing possible, connected to the broader AP picture in Accounts Payable Automation: The 2026 Guide. The honest framing is that optimizing DPO is a business decision enabled by efficient, controllable AP, and the AP processing layer is what makes the optimization executable.
Book a working session with a Kognitos solutions engineer → Or try Kognitos free →
Putting it together
Days payable outstanding measures how long a company takes to pay its suppliers, calculated as (average accounts payable / COGS) × days, and it is a key working-capital lever: a higher DPO holds cash longer and improves working capital, which is why it is the subtracted term in the cash conversion cycle. But maximizing DPO is the wrong goal, because paying too late forfeits valuable early-payment discounts, damages supplier relationships, and risks penalties and disruption. DPO should be optimized, paying each invoice at the time that produces the best overall outcome given the discount value, the cash value, the supplier relationship, and the agreed terms, which varies by invoice. AI optimizes DPO not by deciding the payment strategy but by making payment timing a deliberate, informed choice: processing invoices efficiently (including the exceptions that otherwise cause accidental late payment) so timing is controllable, surfacing discount opportunities and their economics, and supporting optimal, cash-aware payment timing across the payables. The result is DPO managed as a working-capital lever rather than left as an accidental byproduct of how fast AP happens to run, with the AP processing layer being what makes the optimization executable.