How do I capture an early-payment discount before the deadline passes?
Get the invoice approved and payment-ready inside the discount window — for 2/10 net 30 terms, that means fully processed within 10 days of the invoice date, not the 30-day due date. The discount window starts on the invoice date regardless of how long approval takes, so a slow approval chain is what actually costs the discount, not the payment step itself.
Part of the accounts payable and invoice processing guide.
| Typical term shorthand | 2/10 net 30 — 2% off if paid within 10 days, full amount due in 30 |
|---|---|
| What starts the clock | The invoice date, not the date it reaches AP or gets approved |
| Effective annualized value | 2/(1-2%) x (360/(30-10)) ≈ 36.72% per AccountingTools' own formula |
| Most common reason discounts get missed | Approval taking longer than the discount window, not the payment step |
| What to track | Days from invoice date to approval-complete, not just days to payment |
Why the discount window is tighter than it looks
Under 2/10 net 30 terms, a company must pay within 10 days to obtain a 2% discount, or make a normal payment by day 30. The 10-day clock starts on the invoice date — not the date the invoice actually reaches AP, not the date approval begins. An invoice that sits unopened for three days before entering the approval queue has already lost 30% of its discount window before anyone has looked at it.
What the discount is actually worth
Using the standard formula — discount % / (1 - discount %) × (360 / (full payment days - discount days)) — a 2/10 net 30 discount works out to an effective annualized rate of roughly 36.72%. That's the return earned by paying 20 days earlier than otherwise required, which is why capturing it consistently is worth deliberate process design, not something to leave to whoever happens to process an invoice quickly.
Where the discount actually gets lost
The failure point is almost always approval, not payment execution — once an invoice is approved and payment-ready, actually issuing payment takes minutes. The real constraint is getting an invoice through matching, coding, and sign-off inside a 10-day window. That means the metric worth tracking isn't "days to pay" but "days from invoice date to approval-complete," since that's the number that actually determines whether the discount is even reachable.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Worked example
A missed discount, day by day
A $50,000 invoice arrives on 2/10 net 30 terms, dated Monday. It sits in a shared inbox until Thursday (day 3) before anyone logs it into AP. It takes until the following Monday (day 7) to route through a three-way match and reach the approver, who's traveling and doesn't sign off until Thursday (day 10) — the exact deadline. Payment is scheduled for the next business day, day 11, one day past the window. The $1,000 discount (2% of $50,000) is lost — not because anyone made an error, but because the total elapsed time from invoice date to payment exceeded 10 days, even though each individual step was reasonably fast.
Frequently Asked Questions
Sources
Related
Diagnostic
How do I shorten the close when AP reconciliation is the bottleneck?
Move AP-to-bank reconciliation to a rolling, weekly cadence instead of a single close-week event, so most of the matching work is already done by the time the period ends. Most AP bottlenecks at close aren't caused by close-week work itself — they're a backlog of sync gaps and unmatched payments that accumulated all month and only get discovered when someone finally looks.
Read moreTopic
AP & Invoice Processing
Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…
Read moreDiagnostic
Why does one vendor show two different balances in AP aging?
The vendor almost certainly exists as two separate records in your vendor master file — created under slightly different names (a typo, a rebrand, a merger, a re-onboarding) — so bills and credits are split across both. AP aging reports by vendor record, not by real-world vendor, so it shows two partial balances instead of one true balance.
Read moreComparison
Do I need a 2-way or 3-way match for this purchase?
A 2-way match (PO against invoice) is enough for low-risk, non-physical purchases like software subscriptions or professional services, where there's no separate delivery step to verify. A 3-way match (PO, receipt, and invoice) is the standard for physical goods, where confirming something actually arrived — and in what quantity — is the whole point of the extra step.
Read more