Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Incoterms 2020 in Your ERP: Risk Transfer, Goods in Transit and Invoicing

Configure Incoterms in your ERP: model risk transfer, value goods in transit, set the revenue recognition trigger and secure period-end cut-off.

Incoterms 2020 in Your ERP: Risk Transfer, Goods in Transit and Invoicing

A container leaves Shanghai on 28 December, sold FOB. It reaches Rotterdam on 20 January. On 31 December, who carries the risk on those goods? You do. Where are they in your ERP? Nowhere: the stock has not been received, the supplier invoice is not booked, and your year-end balance sheet ignores an asset you own and could lose at sea.

This is not an exotic case. It comes from a setup that treats the Incoterm as a note at the bottom of the order, when it actually drives three management decisions: when stock moves onto your balance sheet, who pays for freight and insurance, and when a sale can be invoiced. This guide explains how to make your ERP carry those three decisions, without redoing customs or landed cost calculation, which are covered in other articles on this blog.

1. Why the Incoterm Is Management Data, Not a Contract Footnote

What an Incoterm fixes: transfer of risk and costs, not ownership

The International Chamber of Commerce (ICC) Incoterms rules define the place of delivery, the moment when the risk of loss or damage passes from seller to buyer, and how obligations are split between the parties (carriage, insurance, export and import formalities). The reference text is the ICC Incoterms 2020 edition, which contains 11 rules: seven usable for any mode of transport, four reserved for sea and inland waterway transport.

One point many teams overlook: Incoterms do not govern the transfer of title to the goods. That question belongs to the sales contract and the applicable law (including any retention-of-title clause), as the ICC reminds readers in its Q&A on Incoterms and commercial contracts. For the ERP, this changes everything: the event that triggers recognition of stock or revenue is a management decision you configure, based on the Incoterm and on your accounting and legal analysis, not an automatism deduced from the rule chosen.

No newer version of Incoterms has been published to date: the 2020 edition remains the one in force. Before putting any configuration into production, check the ICC website to confirm that no update has been announced since this article was written.

Symptoms of a poorly configured ERP

Three signals come up almost every time:

  • Phantom stock. Goods whose risk you carry (FOB, CIF) are at sea but absent from the ERP. If they are damaged or lost, there is no stock to write off and no insurance claim to record.
  • The orphan freight invoice. The forwarder bills freight that the seller should have paid (a CIF sale wrongly entered as EXW), or that you paid twice (included in the price and re-invoiced). With no link to the purchase order, the invoice ends up as an expense instead of a landed cost.
  • The wrong export margin. A DAP sale is calculated like an ex-works sale: the freight and insurance you paid do not appear in the cost of the sale, and the reported margin is too flattering.

2. The 11 Incoterms 2020 Rules Through the ERP Lens

The table below summarises what a configuration must capture. It is a synthesis of the rules: for any specific contract, the ICC text and the contract clause prevail.

RuleRisk transferMain carriageInsuranceImport / customsAccounting impact for the buyer
EXWAt the seller’s premises, goods made availableBuyerBuyer (free choice)BuyerEarly risk: goods in transit from pick-up
FCAHandover to the carrier named by the buyerBuyerBuyer (free choice)BuyerGoods in transit from handover
FASAlongside the vessel, at the port of shipmentBuyerBuyer (free choice)BuyerGoods in transit from the quayside
FOBOn board the vessel, port of shipmentBuyerBuyer (free choice)BuyerGoods in transit from loading
CPTHandover to the first carrierSellerFree choiceBuyerRisk with you, freight included in the price
CIPHandover to the first carrierSellerSeller (extended cover)BuyerRisk with you, insurance included in the price
CFROn board, port of shipmentSellerFree choiceBuyerRisk with you, freight included in the price
CIFOn board, port of shipmentSellerSeller (minimum cover)BuyerRisk with you, freight and insurance included
DAPAt the place of destination, before unloadingSellerFree choiceBuyerStock receipt on arrival at the agreed place
DPUAt the place of destination, after unloadingSellerFree choiceBuyerStock receipt after unloading
DDPAt the place of destination, before unloadingSellerFree choiceSellerStock receipt, import duties and VAT borne by the seller

Two observations matter for the ERP. First, CFR, CIF, CPT and CIP are misleading rules: the seller pays for carriage, but the risk passes to the buyer at handover or loading. An ERP that links “freight paid by the seller” to “stock still with the seller” gets it wrong. Second, DPU replaced DAT in the 2020 edition, and any reference table that still contains DAT must be updated.

3. Where to Store the Incoterm in the ERP

An Incoterm always comes with a named place (“FOB Shanghai”, “DAP Lyon, Saint-Priest warehouse”). A field holding only the code is not enough.

The data model that works in practice:

  • Business partner record (supplier, customer): default Incoterm and place, used to pre-fill documents.
  • Framework agreement or master contract: the Incoterm negotiated for a specific relationship, which takes precedence over the partner record.
  • Order header (purchase and sales): the effective value, editable and tracked in history. This is the value that drives accounting events.
  • Order line: an exceptional override, useful when an order mixes different shipments. Keep it for cases your business really requires: every extra level multiplies data entry errors.

The governance rule: inherited default, override allowed, history retained. An Incoterm changed after shipment must leave a trace, because it changes the analysis of risk and cut-off.

The ERP also needs a configurable link between the Incoterm and the posting event. A configuration table maps each rule (and, where needed, each combination of rule and flow type) to the event that brings stock in or takes it out: pick-up date, bill of lading date, delivery date at destination, unloading date.

Comparison box, to be validated against the documentation for your version:

  • SAP: Incoterms are maintained in customizing (list of rules) and entered on sales and purchasing documents with a second field for the named place. The link to posting runs through your goods receipt, shipping and transit processes, not through the Incoterm alone.
  • Odoo: an Incoterm field is available on orders and invoices. It documents the transaction but does not by itself trigger stock-in-transit entries: those require transit locations and stock rules to be configured.
  • Dynamics 365 Finance and Supply Chain / Business Central: delivery terms attach to orders. As in the two cases above, transit handling relies on the warehouses and statuses you define.

The finding is the same everywhere: the Incoterm is data carried by the document, and the accounting event is still yours to build.

4. Goods in Transit: When Stock Leaves the Seller, When It Enters the Buyer’s Books

Import purchases: FOB and CIF versus DAP

FOB, CIF and every rule where risk passes at shipment. You carry the risk during the voyage, so the asset must appear in your accounts. The standard pattern:

  1. At loading (bill of lading date), you record the goods as stock in transit (a dedicated inventory account, or a holding account linked to inventory), against a goods-received-not-invoiced accrual or a supplier liability.
  2. On arrival and receipt, the stock moves from the transit account to the physical stock account, with warehouse and lot recorded.
  3. Freight, insurance and customs costs are attached to the stock through the landed cost process, detailed in our guide to landed cost in the ERP.

DAP, DPU and DDP. Risk stays with the seller until delivery at the agreed place. There is nothing to record during transport: stock receipt and the payable arise at goods receipt. Freight is included in the price, so there is no transport landed cost to allocate (apart from import duties and charges if the buyer bears them, under DAP).

Valuation in transit follows the same logic as physical stock: purchase price converted at the rate on the event date, then adjusted for attached costs. Specify the currency conversion method in your procedures: it cannot be deduced from the Incoterm.

Export sales: EXW, FCA and DAP

Revenue recognition trigger. For a sale, the management rule generally follows the transfer of risk: under EXW or FCA, revenue is recognised on handover to the carrier or when the goods are made available; under DAP or DDP, on arrival at the customer. This reading depends on your accounting standards (IFRS or local GAAP) and on the contract: have it validated by your finance leadership and your auditors, and do not leave it to a default configuration.

Consequence for the ERP: a DAP sale shipped on 29 December and delivered on 4 January generates no revenue in the year just closed. The stock that left your warehouse stays on your balance sheet as stock in transit on your side. An ERP that invoices at shipment overstates the year. Conversely, the invoice may be issued at shipment for commercial reasons: the ERP must then distinguish invoice issue from revenue recognition, using deferred revenue or a cut-off mechanism.

5. Ancillary Costs: Freight, Insurance, Duties

Each rule allocates these costs differently, and the ERP must attach them to the right flow:

  • Purchases: freight, insurance, duties and forwarder fees that you bear enter the cost price through landed cost. Allocation by item is covered in the landed cost guide.
  • Sales: freight and insurance you pay to deliver under DAP, CIF or CIP go into the cost of the sale, not into overheads, so that margin by customer reflects reality.

A useful configuration tip: when an order is validated, generate the list of expected costs based on the Incoterm (freight, insurance, duties) and compare it with the invoices received. A freight invoice against an order where the seller was supposed to pay is an immediate warning sign.

For declaration aspects and customs regimes, point your teams to our article on customs compliance and international trade in the ERP.

6. VAT and Customs: The DDP Trap

Under DDP, the seller bears the formalities and duties on import into the destination country. In practice, this may require them to register for tax abroad in order to declare or recover import VAT, a compliance burden that escapes many sales teams.

An example in two sentences: an exporter sells DDP to a customer located in another country. They become the importer of their own goods, with a local filing obligation that their ERP, configured for domestic and intra-EU sales, cannot handle.

Good practice: block, or raise an alert on, entry of a DDP sale to a country where the entity has no tax registration or representative. Import VAT rules and registration obligations vary by country: validate them with your tax adviser and the official texts of the relevant authority before automating them.

7. Controls and Period-End Close

At each month-end and year-end close, three controls secure the treatment of Incoterms:

  1. Goods-in-transit order report. A list of purchase and sales orders where risk has passed but receipt or delivery is not yet recorded: this is the scope of stock in transit and of unrecognised revenue.
  2. Reconciliation with bills of lading. The loading and delivery dates on transport documents (bill of lading, waybill) serve as evidence of risk transfer. Reconcile them with the dates posted in the ERP.
  3. Cut-off accrual. For goods where risk has passed but the invoice has not arrived, record an accrual; for shipped sales where risk has not yet transferred, neutralise the revenue.

These controls extend the logic of our year-end stock cut-off checklist. For transactions backed by a documentary credit, see also our guide to letters of credit in the ERP: the Incoterm determines the documents the bank requires.

8. Setup Checklist and Common Mistakes

10-point checklist

  1. The reference table contains the 11 Incoterms 2020 rules (DPU, not DAT) and the named place.
  2. The Incoterm and place are carried by the partner record, the framework contract and the order header, with inheritance and override.
  3. Incoterm changes are tracked in history.
  4. A table maps each rule to a posting event (stock and revenue).
  5. A stock-in-transit account exists for import purchases where risk passes at shipment.
  6. DAP, DPU and DDP sales do not recognise revenue before the agreed delivery.
  7. Freight and insurance are attached to the right flow (landed cost or cost of sale).
  8. A control compares expected costs by Incoterm with invoices received.
  9. DDP sales are blocked or flagged for countries without a tax registration.
  10. The goods-in-transit report and the reconciliation with bills of lading are built into the close.

Common mistakes and countermeasures

MistakeCountermeasure
Incoterm entered as free textControlled list plus mandatory place
Equating Incoterm with ownershipSeparate the accounting event from the contractual transfer of title
Invoicing at shipment for every saleSeparate invoice issue from revenue recognition
Stock at sea missing from the ERPTransit account fed at the bill of lading date
Obsolete rule (DAT)Update the reference table
Line-level override with no controlRestrict to authorised profiles, with an alert

To validate this setup on your real flows, start from an inventory cut: take one closing, list the import and export orders straddling the two financial years, and compare, file by file, how the ERP treated them with what the Incoterm provides. The gaps define your configuration workstream.

Download our ERP evaluation grid: 30 criteria scored out of 100 points to benchmark 3 vendors side by side, including international trade management.