Payment terms

Net 30 means the full invoice amount is due 30 calendar or business days after the invoice date or goods receipt, depending on the contract. Net 45 and Net 60 extend that float. Terms appear on the PO, contract, and supplier invoice; AP systems calculate due dates and discount cutoffs automatically when terms codes are consistent.

Mismatch between PO terms and invoice terms is a frequent exception. If the contract says Net 45 but the invoice prints Net 30, payers need a rule: trust the contract master, reject the invoice, or accept supplier terms only when a buyer approves.

Terms like 2/10 Net 30 offer a 2% discount if paid within 10 days, otherwise full amount at 30 days. Treasury compares the annualized return of taking the discount against cost of capital. On a $100,000 invoice, 2% is $2,000 for paying 20 days early—roughly a 36% annualized yield, which often beats idle cash returns.

AP automation should compute both the discount deadline and the net due date on every invoice so early-pay programs do not miss windows.

Invoice dated March 1 for $50,000 on Net 45 posts with due date April 15 (if calendar days). A partial three-way match hold until March 10 does not usually reset the invoice date, but late receipt posting can push the payable into the next cash forecast week—another reason to clear match exceptions quickly.

Standard terms by supplier category reduce negotiation friction. Strategic suppliers may negotiate longer terms for working capital; critical suppliers may require shorter terms for supply security. Document the authoritative source (contract vs PO) so match and payment batching stay consistent.

Store authoritative terms on the supplier master and contract, not only on individual POs. Automate due-date calculation with explicit rules for calendar vs business days.

Treasury should publish when early-pay discounts are mandatory versus optional. Align terms negotiation with sourcing awards so AP is not surprised at first invoice.

Review metrics quarterly with procurement, finance, and business owners who feel process pain—adjust rules when data shows a control is cosmetic or a bottleneck is upstream.

Internal audit samples payment terms by tracing transactions from requisition or contract through payment, looking for missing evidence and override patterns. Findings are usually systemic—stale catalogs, receivers not trained, or tolerances set too wide—rather than one rogue approver. Remediation plans should name a process owner outside AP when the root cause is upstream.

Leading indicators for payment terms include open exceptions, unposted receipts, contracts past notice windows, and classification backlog; lagging indicators include paid-after-due volume, duplicate hits, and price variance dollars. Review the same dashboard weekly with procurement during a transformation, not only at quarter close, so fixes land before suppliers escalate.

Pilot changes to payment terms on one company code or region with documented before-and-after samples on the same supplier mix. Parallel-run old and new rules until match or classification variances fall below an agreed threshold, then cut over with a rollback plan. Executive sponsors should see cycle time and touch-per-document, not only license go-live dates.

Technology helps payment terms only when master data, contracts, and receiving discipline keep pace. Budget for content stewardship—catalog updates, clause playbooks, screening lists—alongside software. Tie savings claims to redirected spend, captured discounts, and avoided overbill with line-level examples auditors can reproduce.

Stakeholder alignment matters: publish a one-page RACI for payment terms that names who sets policy, who operates the process, and who approves exceptions. Exception approvals should expire automatically after 90 days unless renewed with business justification, preventing "temporary" tolerances from becoming permanent holes in control.

Training should use live examples from your ERP, not generic slides—walk receivers and buyers through one held document and show which fields they can change to clear payment terms issues. Reinforce that fixing upstream data beats overriding match or approval rules downstream, because overrides rarely scale across thousands of transactions per month.