Delivery terms get treated as logistics shorthand. A three-letter code goes on the purchase order, the freight is arranged accordingly, and nobody examines it again until something is damaged, delayed or stopped at a border. At that point the agreement is read properly for the first time, and the three provisions that should have agreed with each other often do not.
The root of the confusion is a widespread belief that the delivery term settles ownership. It does not. Incoterms rules allocate delivery, risk of loss, cost and clearance responsibilities, and they are explicit that title transfer is left to the sale contract and the governing law. An agreement with a delivery term and no title clause has not addressed ownership at all.
This datasheet sets out the three provisions that have to be reconciled, the fields worth holding per supply agreement, and the checks that find the mismatches before a loss does. It is written for contract and sourcing teams rather than for freight specialists, because the failures are contractual rather than operational.
Five fields that define the delivery position
A supply agreement’s delivery position is not one value. Recorded as five fields it becomes queryable across a portfolio, which is what makes a portfolio-level insurance or customs review possible.
- Delivery term and version, the three-letter code and the Incoterms edition referenced, since terms have changed between editions and an unversioned reference is ambiguous.
- Named place, the specific location at which delivery occurs, without which the term has no operative content and risk transfer cannot be located.
- Title transfer point, when ownership passes, which is a separate decision and frequently tied to payment rather than to physical delivery.
- Insurance responsibility, which party insures which leg, written to the risk transfer point rather than assumed from the delivery term label.
- Duty and clearance allocation, who performs export clearance, who performs import clearance, and who bears duty and import taxes under the chosen term.
Holding these five as fields turns a set of questions that currently require reading an agreement into a report. That matters most when something systemic changes, such as a new Incoterms edition, a tariff change or an insurance programme renewal, and someone has to know the position across hundreds of agreements at once.
The most common and most expensive mismatch is an insurance obligation that does not align with where risk actually passes. Draft the insurance clause by reference to the risk transfer point established by the delivery term and named place, not by reference to the term’s informal reputation. Then check that the party obliged to insure is the party with an insurable interest at that point, because an obligation on a party with no interest produces cover that will not respond.
The checks that find the mismatches
Five checks cover almost all of it. None require specialist knowledge beyond the terms themselves, and all of them are faster against structured fields than against documents.
- Term against named place completeness. Every agreement must carry both. A blank or vague named place is a finding in its own right, because it leaves the operative content of the clause undefined
- Risk point against insurance obligation. Compare where risk passes with who is obliged to insure which leg, and flag any agreement where the insuring party has no insurable interest at that point
- Title clause presence and basis. Confirm a title clause exists and record whether title passes on delivery, on payment or on another event, since silence defaults to the governing law
- Clearance allocation against capability. Check that the party responsible for import clearance is operationally able to perform it in that jurisdiction, which is frequently not the case for smaller suppliers
- Order level deviation from agreement. Compare the terms on recent purchase orders against the governing agreement, and treat unapproved deviations as a process finding rather than a data correction
A five-step roadmap for getting delivery terms under control
Step 1, extract the five fields across the supply base
Pull delivery term, version, named place, title basis and insurance responsibility from the agreement population. Extraction handles the standard cases; agreements with the term buried in an annex or varied by side letter need human review and are usually where the problems sit.
Step 2, run the five checks and triage the findings
Expect three clusters: missing or vague named places, insurance obligations misaligned to risk, and absent title clauses. Triage by shipment value and route, since a mismatch on a high-value international lane matters considerably more than one on a domestic collection.
Step 3, align the insurance programme to the portfolio position
Share the extracted position with the risk or insurance function. Programmes are frequently bought on an assumed pattern of delivery terms that the actual portfolio does not match, which produces both gaps and duplicated cover
Step 4, standardise the clause set in the template
Draft delivery term, title transfer and insurance as a linked set in the standard agreement, with the named place as a required field rather than a blank to be completed later. Give reviewers a short decision rule for when title should follow payment
Step 5, close the order-level deviation path
Where purchase orders can carry terms different from the agreement, require an approval and record it. This is usually a system configuration change rather than a policy change, and it stops the position drifting away from the signed agreement
Query the delivery position, don't read it
Aavenir holds delivery term, named place, title basis, insurance responsibility and duty allocation as fields across the supply agreement portfolio.
Why this surfaces as a finance problem
Delivery terms reach the financial statements through inventory. Where title passes determines who recognises goods in transit, and an agreement whose title clause is absent or contradicted by practice produces inventory that both parties count or neither does. Auditors find this during cut-off testing, usually at a period end, and the remediation involves reading agreements under time pressure. The same data also drives customs valuation and transfer pricing documentation, which means the five fields earn their keep in three functions rather than one. Teams that already hold cost pass-through terms as structured data will recognise the pattern.
Provision, what it governs and what it does not
The table separates the three provisions and names the failure each one produces when it is left to the others. Use it when reviewing a template rather than an individual agreement.
| Provision | Governs | Does not govern | Failure if omitted |
|---|---|---|---|
| Delivery term and place | Risk, cost, carriage, clearance | Ownership | Risk point undefined, insurance mispriced |
| Title transfer clause | Ownership and timing | Risk of loss | Inventory double counted or unrecognised |
| Insurance clause | Who insures which leg | Risk allocation itself | Uninsured transit or duplicated cover |
| Duty and tax allocation | Clearance and duty cost | Risk of loss | Shipments held, unexpected duty cost |
| Order level terms | Shipment specifics | The framework position | Position set by order entry, not agreement |
The useful summary is that three provisions do three different jobs and none of them covers for the others. A supply agreement that names a delivery term, locates it precisely, states when title passes and obliges the party with an insurable interest to insure has resolved the whole question in four sentences. One that names a term and stops has resolved the easy part and left the expensive part to be discovered during a claim, an audit or a border hold. Holding the five fields as data is what lets a team answer the question before any of those three arrive, and manufacturers running obligation management for manufacturing already have the record to hold them on.
For related guidance, see IATF 16949 supplier agreements built for audit day, ESG and supply chain due diligence clause tracking and Background IP and license-back in supply deals.
