Payment terms state when and how a buyer must pay a seller. They may specify a due date, credit period, deposit, instalments, accepted payment method, currency, early-payment discount, late charges, and responsibility for transfer or bank fees.
Review points before the transaction moves
- Confirm the party responsible for the transaction record.
- Keep the source data and approval with the transaction.
- Record exceptions instead of silently changing the original instruction.
- Make the downstream owner able to reconstruct what happened without an email search.
The boundary worth keeping clear
The definition matters because nearby terms can describe a different document, event or responsibility. Use Payment terms 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.
Related terms and distinctions
- Invoice: An invoice is a document a seller issues to request payment for supplied goods or services.
| 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 |
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 acceptance, international vendor payments and Invoice. These pages cover the commercial workflow and the records that connect Payment terms to the next transaction step.
