Payment terms: separating billing triggers from payment deadlines

Payment terms answer when the customer must pay and, for more complex contracts, how billing is divided. Days-based terms suit ordinary credit sales. Advance terms require money before fulfillment. Progress terms bill agreed milestones. Mixed terms combine an advance with progress billing.

DNA Customer Payment Terms supports these four models. Progress and Mixed templates can include milestones, work packages, retention and account mappings. When every milestone is percentage-based, the payment-term editor requires their total to equal 100%. Plans containing fixed amounts or quantities need the corresponding amount and quantity checks; the percentage rule must not be generalized to every plan. The template becomes the starting point for the sales order's billing plan.

Two questions inside a commercial agreement

When may the supplier issue an invoice, and when must the customer pay it? These questions are often confused. A payment period such as 30 days can establish a deadline after an invoice, but it does not necessarily explain which event makes the work billable.

For stocked goods, the arrangement may follow normal delivery-based billing. For a longer contract, the customer and supplier may agree specific milestones. An advance introduces an earlier funding event, while retention reserves part of collection for a later condition.

DNA's four customer-term models provide different structures for those arrangements. Their usefulness depends on matching the actual agreement rather than choosing the most familiar name.

Selecting the arrangement

A stocked item delivered tomorrow may use Net 30. A made-to-order item may need a 30% advance to fund materials. A six-month installation can use design, delivery and commissioning milestones. Choosing Net 30 alone for the installation would specify the due date after an invoice, but not when each milestone becomes billable.

The choice changes the operational expectations. An advance condition can affect release of goods. A milestone plan determines the basis of progress invoices. Days-based terms establish the settlement period for the billed amount.

Templates and individual contracts

A template supports consistency when the company repeatedly uses a similar arrangement. It is especially useful for standard milestone patterns or recurring commercial policies. The specific order still needs to reflect the contract's value, milestones, and applicable conditions.

For a plan expressed entirely as percentages, the milestones should represent the full agreed billing basis. A total below 100% leaves part of that basis unallocated; above 100% allocates more than that basis. The percentage total alone does not establish that the milestones are commercially meaningful.

Work-package relationships and account mappings connect the plan to the business structure. They help distinguish the kind of work being billed and its intended financial destination. Those settings should be coherent with the company setup and the actual scope.

A useful commercial description

A good payment arrangement can be explained in ordinary language: what the customer must pay before work, which events support later bills, how long each bill may remain unpaid, and whether any amount is withheld for later release.

If that description is unclear, a technically complete term record will not resolve the underlying ambiguity. DNA should express the agreement, while the business remains responsible for agreeing a workable arrangement.