Finance Index
What do vendor payment terms like net 30 and 2/10 net 30 mean?
Reference guide to vendor payment terms explained, including vendor records, onboarding requirements, compliance checks, fraud controls, and payment readiness.
Payment terms define when an invoice is due and any early-pay incentive. Net 30 means payment is due 30 days from the invoice (or agreed start) date; net 60, 60 days. "2/10 net 30" means take a 2% discount if you pay within 10 days, otherwise the full amount is due in 30. Terms govern your cash timing and your vendor relationships, which is why they belong on a controlled field, not in someone's memory.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| What do vendor payment terms | Payment terms define when an invoice is due and any early-pay incentive. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Net 30 is the broad default; some sectors run shorter (net 15 for smaller services) and others longer (net 60 - 90 in retail and some manufacturing). | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Where should payment terms | The contract is the governing source; the vendor master holds the default for convenience; the PO and invoice should reflect it. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Vendor impact | Follow the contract (net 45) as the governing agreement, confirm with the vendor to avoid a dispute, and correct the vendor master to match so future invoices default correctly. | Keeps vendor records and payment decisions reliable. |
| Run a payment-terms standardization | Segment vendors by leverage and relationship: standardize the long tail to your default, negotiate extensions where you have leverage, and explicitly exempt the small or critical vendors you should never push. | Reduces payment errors, timing issues, and reconciliation cleanup. |
What are standard payment terms by industry?
Net 30 is the broad default; some sectors run shorter (net 15 for smaller services) and others longer (net 60 - 90 in retail and some manufacturing). What's "aggressive" is relative - pushing a small vendor from net 30 to net 60 strains them, while net 60 is unremarkable for a large supplier. Norms are a starting point, not a rule.
Where should payment terms live, and which wins when they conflict?
The contract is the governing source; the vendor master holds the default for convenience; the PO and invoice should reflect it. When they conflict, the contract generally controls legally - but the practical fix is reconciling them so they agree. A terms mismatch across systems is a process gap to close, not a puzzle to re-solve each time.
Invoice says net 15, vendor record says net 30, contract says net 45 - which do we follow and how do I fix the record?
Follow the contract (net 45) as the governing agreement, confirm with the vendor to avoid a dispute, and correct the vendor master to match so future invoices default correctly. The invoice's stated term doesn't override your agreement - but persistent mismatches mean your master data is wrong and should be fixed at the source.
How do I run a payment-terms standardization or extension project?
Segment vendors by leverage and relationship: standardize the long tail to your default, negotiate extensions where you have leverage, and explicitly exempt the small or critical vendors you should never push. Use clear comms, give notice, and don't extend terms on suppliers whose cash flow you'd damage - the goodwill cost outweighs the DPO gain.
How do I update payment terms in bulk and ensure open invoices pick up the right terms?
Update the vendor-master default in bulk, but check how your system applies terms to *existing* open invoices - many lock the term at invoice entry, so a master change only affects new invoices. You may need to adjust open items individually. Verify the behavior before assuming a bulk change rippled through.
What's the cash-flow impact of moving average terms from net 30 to net 45?
Extending terms increases your days payable outstanding (DPO), holding cash longer - a one-time working-capital benefit roughly equal to 15 days of the affected spend. Size it as (additional days ÷ 365) × annual spend on the affected vendors. It's real cash, but it's a one-time shift in timing, not recurring savings.
Should new vendors default to a standard term with approval for exceptions?
Yes - default every new vendor to your standard term at onboarding and require approval to deviate. Terms governance at the front door prevents the slow drift toward whatever each vendor asked for, which is how AP ends up with hundreds of inconsistent terms nobody decided on.
A small vendor is begging for net 15 because of cash flow - when do I flex and who approves?
Flex when the vendor is small or critical and the cost to you is minor relative to the relationship - but route it through a defined exception approval so it's a decision, not a default. Document the reason. Compassion for a struggling vendor can be good business; uncontrolled term exceptions are not.
What are stage/progress payment terms and how do they differ from net terms?
Stage or progress payments tie disbursement to milestones or percentage-of-completion (common in construction and large projects) rather than to a flat number of days after invoicing. They protect both sides on long engagements - you pay for work delivered, the vendor isn't financing the whole project - and they require milestone verification, not just an invoice date.
Stampli perspective
Stampli's position is that payment controls work best when the payment is tied to the invoice, the vendor record, and the approval trail that made the liability payable. That connection gives finance a clearer way to review who approved the spend, which payment method is being used, and what changed before money moves.