Net 30 is a credit term requiring the invoice's net amount to be paid within 30 calendar days of the agreed starting date. The contract or invoice should clarify whether the period begins on the invoice date, receipt date, delivery date, or acceptance date.
What Net 30 controls in practice
Net 30 belongs in the order, invoice, approval, payment and reconciliation evidence. Give it a named finance operations owner, a source document and a clear handoff. Otherwise finance has to reconstruct the transaction after an exception appears.
| Checkpoint | What the record should show |
|---|---|
| Source | Identify the order, contract or delivery event behind the amount |
| Control | Check the document against the relevant approval and transaction record |
| Exception | Record the difference, owner and resolution |
| Close | Link the payment or adjustment back to the open balance |
Related terms and distinctions
- Payment terms: Payment terms state when and how a buyer must pay a seller.
- Invoice: An invoice is a document a seller issues to request payment for supplied goods or services.
The boundary worth keeping clear
The definition matters because nearby terms can describe a different document, event or responsibility. Use Net 30 only when the record matches the conditions above. A familiar label attached to the wrong stage creates cleaner-looking data and worse decisions. That discipline also makes reports comparable across teams, systems and reporting periods.
The trade-off
More controls add work at the start. That cost is visible. The cost of weak records arrives later as rework, delayed approval, margin leakage, a payment investigation or a delivery dispute. Set the control depth according to the amount, risk and reversibility of the decision.
Related Quotable resources
Continue with Payment terms, Invoice and payment acceptance. These pages cover the commercial workflow and the records that connect Net 30 to the next transaction step.
