Skip to main content
BlogOctober 23, 2026

How to extend days payable outstanding without losing early-payment discounts

Extend days payable outstanding and still take early-payment discounts: the 2/10 net 30 math, a payment-run calendar and the controls behind it.

Zuny FesterBy Zuny Fester, Head of Operations and Marketing
Reviewed by Zuny Fester
Published Editorial policy

Part of the accounts payable and invoice processing guide.

Two payment timelines: on one a coin sits at the far edge of a blue discount window, on the other a coin sits just before the due-date marker.

To extend days payable outstanding (DPO) without losing early-payment discounts, pay every bill on its due date unless the vendor offers a discount worth more than your cost of funds. Pay those bills on the last day of the discount window instead. A 2/10 net 30 discount is worth about 37.2% a year, so it almost always wins. Then run payments often enough that bills are not released days ahead of their target date, with separate people approving and releasing each run.

Paying every bill the moment it is approved shortens DPO and buys nothing. Paying every bill on the due date maximizes DPO but quietly gives up discounts worth more than the float. The answer is a rule per bill, not a single policy for all of them. This post works through that rule on a hypothetical vendor set. The DPO formula itself lives in how to calculate days payable outstanding.

Key takeaways

  • Pay on the due date, not on approval. That is the main DPO lever, and it pays no vendor late.
  • Skipping 2/10 net 30 costs about 37.2% a year on a 365-day basis. Take any discount whose annualized rate beats your cost of funds.
  • In the worked example, the rule raises the spend-weighted payment day from 20 to 27.1 and captures $1,400 of discounts a month.
  • Payment-run frequency sets how early bills go out. One weekly run can pay up to six days early; two runs a week, at most three.
  • Speed matters as much as timing. The discount window starts at the invoice date, so slow intake and approval lose discounts before the run ever sees them.

What does extending days payable outstanding mean?

Extending DPO means holding cash until each bill is due, within the terms you agreed, not paying vendors late. DPO rises when your average payables balance rises relative to cost of goods sold.

The usual leak is not late payment but early payment. Many AP teams release every approved bill in the next payment run. A net 30 bill approved on day eight and paid on day 10 leaves 20 days of float unused. Across a whole vendor base, those early payments are where DPO goes.

There is a limit on the other side. Stretching payments past terms is not extending DPO; it is paying late. It strains vendor relationships and can trigger late fees or lose you the discount terms you have. The strategy here never pays a bill after its due date.

When is an early-payment discount worth more than the float?

An early-payment discount is worth taking when its annualized rate is higher than your cost of funds. Your cost of funds is what you pay to borrow short term, or what your cash earns, whichever applies.

Terms like 2/10 net 30 mean a 2% discount if the invoice is paid within 10 days of the invoice date, otherwise the full amount is due in 30 days, as OpenStax's Principles of Finance describes. Skipping the discount means paying 2% more to hold the money 20 extra days.

The annualized cost of skipping a discount is:

(discount % ÷ (100 - discount %)) × (365 ÷ (net days - discount days))

For 2/10 net 30: (2 ÷ 98) × (365 ÷ 20) = 0.0204 × 18.25 = 37.2%. OpenStax works the same terms on a 360-day year and gets 36.73%. If you skipped the discount every 20 days all year, the compounded rate is about 44.6%. The small differences come from the day count and compounding; every version is far above typical borrowing costs.

TermsExtra days heldAnnualized cost of skipping (365 days)Take it at a 10% cost of funds?
2/10 net 302037.2%Yes
2/10 net 453521.3%Yes
1/10 net 302018.4%Yes
1/10 net 60507.4%No

The 10% cost of funds is a hypothetical hurdle rate for this example. Use your own: your revolver rate if you borrow, or your yield on cash if you do not.

The rule for each bill is simple: if the discount's annualized rate beats your hurdle, pay on the last day of the discount window; if not, pay on the due date. The US federal government applies a similar test. Under its Prompt Payment rules, an agency "may take the discount if economically justified," and "payment will be made as close as possible to, but no later than, the discount date" (5 CFR 1315.7).

A worked example: five vendors, one hurdle rate

This hypothetical company pays five vendors a total of $260,000 a month. Every figure is invented for illustration, and the hurdle rate is 10%.

VendorTermsMonthly spendRule resultPay on day
A: cloud hostingNet 30$120,000No discount, pay on due date30
B: implementation contractor2/10 net 30$50,00037.2% beats 10%, take discount10
C: hardware supplier1/10 net 30$40,00018.4% beats 10%, take discount10
D: software resellerNet 45$30,000No discount, pay on due date45
E: facilities1/10 net 60$20,0007.4% is below 10%, skip discount60

Compare three payment policies

The spend-weighted payment day is a simple proxy for DPO: each bill's payment day weighted by its amount. Reported DPO uses balances and cost of goods sold, but it moves in the same direction because paying later raises the average payables balance.

PolicySpend-weighted payment dayDiscounts captured per month
Pay each bill in the next weekly run after approval (about day 20)20.0$0 (every day-10 window missed)
Pay every bill on its due date34.0$0
Due date, except discounts that beat the hurdle27.1$1,400

The calculations:

  • Due date for all: (120,000 × 30 + 50,000 × 30 + 40,000 × 30 + 30,000 × 45 + 20,000 × 60) ÷ 260,000 = 8,850,000 ÷ 260,000 = 34.0 days.
  • Rule-based: (120,000 × 30 + 50,000 × 10 + 40,000 × 10 + 30,000 × 45 + 20,000 × 60) ÷ 260,000 = 7,050,000 ÷ 260,000 = 27.1 days.
  • Discounts: 2% × $50,000 + 1% × $40,000 = $1,000 + $400 = $1,400 a month, or $16,800 a year.

Is the rule really better than paying everything on the due date?

Yes. Paying vendors B and C 20 days early costs $485 a month in float and earns $1,400 in discounts, a net gain of about $915 a month in this model.

  • Vendor B: paying $49,000 20 days early at 10% costs $49,000 × 10% × 20 ÷ 365 = $268.49. The discount is $1,000.
  • Vendor C: paying $39,600 20 days early costs $39,600 × 10% × 20 ÷ 365 = $216.99. The discount is $400.
  • Vendor E, the discount skipped: taking it would mean paying $19,800 50 days early, which costs $19,800 × 10% × 50 ÷ 365 = $271.23 in float to save $200. Skipping is better by $71.23 a month.

Against the company's current habit of paying on approval, the rule wins on both counts: the weighted payment day rises from 20.0 to 27.1, and $1,400 a month in discounts that were being missed are captured. That is the trade the title promises: longer DPO and the discounts.

How do you set a payment-run calendar that hits both dates?

Give every bill a target date, then schedule it into the last payment run on or before that date. The target date is the discount date for bills that pass the hurdle and the due date for everything else.

  1. Set the target at intake. When the bill is entered, record its terms, discount date, due date and the rule result. The vendor master should hold the terms, not the person entering the bill.
  2. Subtract settlement time. If the vendor's terms count from when the payment arrives, move the target earlier by the payment method's settlement time.
  3. Schedule to the last run on or before the target. Never to the next run after approval.
  4. Choose a run frequency that limits early payment. With one run a week, a bill can go out up to six days before its target. With runs on Tuesday and Friday, at most three.
Run frequencyMost days a bill can be paid ahead of target
Weekly6
Twice weekly3
Daily (business days)0 to 2, around weekends

How you build the batch itself, and when to use ACH, check or virtual card, is covered in how to run an AP payment batch. For a system-specific setup, see how to set up a Sage Intacct AP payment run.

Why do discounts get missed even with the right rule?

Discounts are usually lost before the payment run, in intake and approval, because the 10-day window starts at the invoice date, not the day AP sees the bill. A bill that arrives on day four and waits five days for approval has one day left.

Which controls keep the schedule from becoming a fraud gap?

A schedule that pays automatically on target dates needs release controls that do not depend on anyone remembering. Timing rules decide when money moves; controls decide whether it should.

  • The approver never releases. One person approves bills, another releases the run. The reasons are set out in why the person approving a vendor payment should never release it.
  • Release the run against a total and a list. The releaser sees the number of payments, the total, and every payee before sending.
  • Verify bank-detail changes out of band. Any vendor bank account changed since the last run is held until someone confirms it through a known contact, not the email that requested it.
  • Lock terms in the vendor master. Changing a vendor's terms or discount rule needs its own approval, so no one can move a payment date by editing a bill.
  • Log every exception. Early payments outside the rule and missed discounts are recorded with a reason.

What this looks like as a workflow

The whole strategy is a set of fixed rules, which is why it runs well as a deterministic workflow. Nothing here needs a model's judgment; it needs the same rule applied to every bill.

Loopfour, the deterministic finance workflow automation platform, builds it on your AP stack:

bill received → terms and discount date read from the vendor master → hurdle rule applied → target date set → approval routed in Slack with the deadline shown → bill scheduled to the last run on or before target → run total and payee list sent to a separate releaser → payments released → posted to NetSuite, QuickBooks, Xero or Sage Intacct → execution tree records every date, rule and approver

The workflow behaves the same on the first bill and the ten-thousandth, and the execution tree shows an auditor who approved, who released and why each bill was paid when it was. Loopfour is SOC 2 Type II certified and SOC 1 Type I certified. We build, run and maintain the workflow. If your team pays on approval and misses discount windows, book a workflow review and we will map your vendor terms against these rules.

Frequently asked questions

How do you increase days payable outstanding without hurting vendors?

Pay each approved bill on its due date instead of in the first payment run after approval. That extends DPO without paying anyone late. Do not stretch payments past the agreed terms, which damages vendor relationships and can trigger late fees.

Is it better to take a 2/10 net 30 discount or hold the cash?

Usually take the discount. Skipping a 2/10 net 30 discount costs about 37.2% a year on a 365-day basis (36.7% on a 360-day basis), because you give up 2% to keep the money 20 more days. Few companies earn or borrow at anything close to that rate.

How do you calculate the cost of not taking an early-payment discount?

Divide the discount percentage by 100 minus the discount, then multiply by 365 divided by the number of extra days you hold the cash (the net days minus the discount days). For 2/10 net 30, that is 2 / 98 x 365 / 20, or about 37.2%.

Does paying early lower DPO?

Yes. Paying a bill before its due date reduces the average payables balance, which lowers DPO. Paying early only makes sense when the vendor offers a discount worth more than your cost of funds.

How often should we run vendor payments to protect DPO?

Often enough that bills are not paid far ahead of their target date. With one weekly run, a bill can go out up to six days early; with two runs a week, at most three. Schedule each bill into the last run on or before its due date or discount date.

Who should approve and release a vendor payment run?

Two different people. One person approves the bills and another releases the payment run, so no single person can both authorize and send a payment. Changes to vendor bank details should be verified independently before the next run.

Conclusion

To extend days payable outstanding without losing early-payment discounts, apply one rule to every bill: pay on the due date, unless the discount's annualized rate beats your cost of funds, in which case pay on the last day of the discount window. Schedule to target dates, run payments often enough to hit them, and keep approval and release in separate hands. In the worked example, that moves the weighted payment day from 20 to 27.1 and captures every discount worth taking.

Tell us the one workflow your team dreads. We will show it running. Book a demo.

Sources