IFRS 15CoreLogistics & Transport

Multi-modal transport: single versus multiple performance obligations

IFRS 15 · Revenue from Contracts with Customers

Applies to: Freight & logistics services

In plain words

A forwarder sells a door-to-door move covering sea freight, customs clearance and inland trucking for one price. Is that one service or several? If the forwarder provides a significant integration service combining the legs, it is one performance obligation recognised over the whole journey. If the legs are distinct, the price is allocated using standalone selling prices and each leg's revenue is recognised as that leg is performed.

Why it matters

A door-to-door contract bundling sea/air line-haul with inland trucking, customs clearance and last-mile delivery may be a single integrated logistics service or a series of distinct performance obligations, and the answer changes both the pattern and timing of revenue recognition across the legs of the journey. Getting this judgment wrong can materially shift revenue between periods (single obligation recognized evenly over the whole journey vs. distinct legs recognized as each is performed) and misstate margins by leg.

Diagnostic questions

Is each leg of a door-to-door movement (line-haul, customs clearance, inland transport, last-mile) capable of being distinct, i.e., could the customer benefit from it on its own or with readily available resources? Are the legs distinct within the context of the contract, or does the carrier provide a significant integration service that combines them into a single, combined output the customer is actually purchasing? Where legs are distinct, how are standalone selling prices estimated for legs (such as embedded customs clearance) that are never sold separately?

Recognition

1) List each leg of the door-to-door service (line-haul, customs clearance, inland transport, last-mile) and assess whether each is capable of being distinct (the customer could benefit from it on its own or with readily available resources). 2) Assess whether the legs are distinct within the context of the contract, i.e. whether the forwarder provides a significant integration service that combines the legs into a single combined output, or whether the legs are highly interdependent/interrelated. 3) If the integration service is significant (legs are not separately identifiable in context), treat the bundle as one performance obligation recognized over the total transit time using an appropriate progress measure. 4) If the legs are distinct, identify or estimate a standalone selling price (SSP) for each leg. 5) Allocate the total transaction price to each distinct leg in proportion to relative SSPs (ensuring the allocated amounts sum exactly to the transaction price). 6) Recognize revenue for each leg as it is performed (point in time or over time, as appropriate to that leg).

Measurement

Where legs are distinct, estimate standalone selling prices for legs not sold separately (e.g. customs clearance embedded in a through rate) using an adjusted market assessment approach or an expected cost-plus-margin approach; allocate the transaction price using the relative SSP method, which by construction always reconciles the sum of allocated amounts to the total transaction price. Where the bundle is a single performance obligation, measure progress over time using an output method (e.g. total transit distance/time across all legs) that faithfully depicts the integrated service.

Presentation & disclosure

Disclose: (1) the judgment made in identifying performance obligations for bundled multi-modal contracts (single integrated service vs. distinct legs); (2) the method used to allocate transaction price where multiple obligations are identified, including how standalone selling prices were estimated; (3) the timing of revenue recognition for each leg or for the combined obligation; (4) disaggregation of multi-modal revenue by leg/mode where material to understanding performance.

Common mistakes

  • Defaulting to recognizing all door-to-door revenue only on final delivery regardless of whether legs are distinct, which understates revenue during earlier legs of a genuinely distinct-obligations contract
  • allocating transaction price using contract line-item prices that do not reflect standalone selling prices (e.g. arbitrary or negotiated bundle line-items that do not sum correctly or do not reflect market value)
  • failing to ensure allocated amounts reconcile exactly to the total transaction price when estimating standalone selling prices
  • treating every multi-modal contract identically without assessing the integration-service indicator contract-by-contract.

Simple example

A forwarder sells a door-to-door container move (ocean freight, customs clearance, inland trucking) for a lump sum of SAR 47,000. Concluding the legs are distinct, standalone selling prices are estimated at SAR 30,000 (ocean), SAR 5,000 (customs) and SAR 12,000 (inland), totaling SAR 47,000, matching the contract price exactly, so no further scaling is needed. Revenue is allocated and recognized as each leg is performed: Dr Contract asset/Trade receivable 30,000 / Cr Revenue (ocean) 30,000 on completion of the ocean leg; Dr Contract asset/Trade receivable 5,000 / Cr Revenue (customs) 5,000 on completion of clearance; Dr Trade receivable 12,000 / Cr Revenue (inland) 12,000 on final delivery, the three entries together recognize the full SAR 47,000 contract price with no reconciling difference.

Professional judgment

Assessing whether an integration service is significant enough to combine legs into one obligation, versus treating them as distinct, is a significant judgment that can vary by trade lane and service design, a forwarder that merely subcontracts each leg with minimal coordination looks different from one that actively manages routing, consolidation, and risk across the whole journey. Judgment is also needed in estimating standalone selling prices for legs never sold separately, and in ensuring the allocation methodology is applied consistently across similar contracts rather than reverse-engineered from a desired revenue pattern.

Source basis

IFRS 15 · Revenue from Contracts with Customers

Paragraph references

IFRS 15.22IFRS 15.22(b)IFRS 15.27–29

Verified against the official standard texts used in the IFRS Expert skill.

IFRS 15 Revenue from Contracts with Customers
Issued: 28 May 2014 · Effective: 1 January 2018

Related issues

Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.