Himalaya Clause — Protection of Subcontractors and Limitation of Liability under B/L
What Is a Himalaya Clause?
A Himalaya Clause is a provision that extends the exemption and limitation of liability benefits granted to the carrier under a Bill of Lading (B/L) to the carrier’s employees, agents, subcontractors, stevedores, terminal operators, CFS operators, inland carriers, and similar parties.
In Japanese, this is sometimes referred to as the "Himalaya Clause."
The contract of carriage evidenced by a Bill of Lading fundamentally exists between the shipper and the carrier. However, in actual international transport, numerous parties handle the cargo—not only the shipping company but also stevedores, CFS operators, CY facilities, terminal operators, trucking companies, warehouse operators, overseas agents, and others.
When cargo incidents occur, the shipper, cargo owner, or cargo insurance company may attempt to bring direct claims for damages not only against the carrier but also against the parties that physically handled the cargo. The Himalaya Clause is established to enable these non-carrier parties to assert the same exemptions and limitations of liability as those granted to the carrier under the B/L.
Terminology Used in This Article
In this article, “carrier” is used as a general term when considering the party responsible under the Bill of Lading (B/L). The “Contracting Carrier” refers to the party held contractually responsible to the shipper or claimant under the contract of carriage. The “Actual Carrier” means the party actually performing the vessel transport or carriage.
“Shipping line” primarily refers to the ocean carrier that issues the Master B/L or Ocean B/L. The terms “subcontractor,” “agent,” and “performing assistant” cover entities involved in the carrier’s performance of transport, including port stevedores, terminal operators, CFS operators, inland carriers, warehouse operators, and overseas agents.
“Shipper” denotes the party on the shipment side who issues shipping instructions, cargo information, packing details, and dangerous goods declarations. “Cargo owner” is used when referring to the party holding the economic interest in the cargo, the insured party receiving insurance proceeds, or the party bearing loss entitling subrogation claims.
Scope Covered in This Article
This article organizes the basic meaning of the Himalaya Clause, why it is needed, who it aims to protect, and how it becomes relevant in cargo incidents, subrogation claims, and NVOCC practical matters.
| Item | Content Covered in This Article | Content Covered in Other Articles |
|---|---|---|
| Basic Structure of the Himalaya Clause | The mechanism by which exemption and limitation of liability clauses on the B/L are extended to parties other than the carrier | The overall structure of B/L reverse side terms is covered in “What Are the Terms and Conditions on the Back of a Bill of Lading” |
| Scope of Protected Parties | Confirmation of employees, agents, subcontractors, stevedores, terminal operators, CFS operators, inland carriers, and others | Individual contractual liabilities of these operators are covered in cargo incident response and logistics contract-related articles |
| Contractual Liability and Tort Liability | Why the Himalaya Clause becomes an issue when claims are made under tort liability against parties without direct contracts | The legal requirements for tort liability itself are handled in specialized legal fields |
| Relationship with Limitation of Liability | The concept of extending Package Limitation and Weight Limitation to subcontractors and others | The calculation methods for limitation of liability are covered in “What Is Package Limitation” and related articles |
| House B/L and Master B/L | In NVOCC practice, the approach to separating shipper claims and claims against the Actual Carrier | A full overview of House B/L and Master B/L is covered in specific B/L-related articles |
| Subrogation Claims | Key points when marine cargo insurers pursue direct subrogation claims against subcontractors or related parties | Details of insurance claims and subrogation are covered in marine cargo insurance-related articles |
| Gap Risk | The risk that the amount NVOCC pays to the shipper differs from the recoverable amount from the Actual Carrier side | Overall subrogation practice is covered in claim points to watch when reviewing B/L clauses and cargo incident response articles |
| Points for Initial Response | The approach of giving responses assuming liability is undetermined, terms are still being checked, and rights are reserved | Detailed responses to Claim Letters are covered in damage notification and claims management articles |
Why the Himalaya Clause Is Necessary
In cases of cargo incidents, the shipper, cargo owner, or insurance company may seek to make direct claims not only against the carrier but also against parties who actually handled the cargo.
For example, in incidents such as cargo dropping during port stevedoring, damage during CFS operations, water damage within the terminal, accidents during container movements, or damage during inland delivery, there may be a tendency to claim against the party closest to where the damage occurred.
However, if the shipper or cargo insurer could bypass the carrier’s liability limitations by claiming directly against subcontractors or agents, the liability restrictions established by the B/L terms and maritime transport liability rules could effectively lose their meaning.
The Himalaya Clause is introduced to prevent such circumvention of liability limits and to ensure that the carrier and its performing parties remain within a defined scope of liability.
Parties Protected by the Himalaya Clause
The parties protected under a Himalaya Clause vary depending on the wording of the provision. Generally, the following stakeholders are commonly involved.
| Stakeholder | Typical Situations | Points to Confirm | Notes |
|---|---|---|---|
| Master and Crew | Claims related to cargo handling aboard the vessel or cargo management during the voyage | Whether servants, agents, crew, etc. are included as protected parties | Check whether direct claims against individual crew members are limited |
| Stevedores | Damage, dropping, or wetting during loading and discharge operations | Whether stevedores, subcontractors, and independent contractors are covered | Stevedores may be treated as independent contractors |
| Terminal Operators | Incidents during storage, movement, or container handling within the CY | Whether terminal operators are expressly named or included within the scope of carriage performance | Check whether it concerns port operations and whether it falls within the carrier’s responsibility period |
| CFS Operators | Damage during sorting, devanning, or gate-out operations of consolidated cargo | Whether CFS operations can be considered ancillary to the carrier’s performance | Scope may differ between House B/L and Master B/L |
| Inland Carriers | Incidents occurring during transport from port to warehouse or delivery location | Whether the B/L covers inland transport segments | May fall outside B/L carrier liability if beyond the port area |
| Warehouse Operators | Damage during temporary storage, pre-gate-out storage, or customs clearance waiting periods | Whether warehouse operations are part of carriage performance or governed by a separate contract | Warehouse terms and conditions may apply separately |
| Agents and Overseas Agents | Situations where agents act on behalf of the carrier regarding procedures, notifications, or cargo delivery | Whether terms include agents, servants, representatives, etc. | Agents may have independent liability issues |
| Sub-subcontractors | Accidents involving parties further subcontracted by the original subcontractor | Whether wording covers sub-subcontractors or any person employed by subcontractors | Narrow clause wording may exclude these parties |
The critical point is not just whether a Himalaya Clause exists, but to confirm the extent of parties that the clause protects based on its wording.
Relationship Between Contractual Liability and Tort Liability
The key point in the Himalaya Clause is whether claims by the shipper, cargo owner, or insurer are based on contractual liability or tort liability.
There is a contract of carriage between the shipper and the carrier under the Bill of Lading. However, it is often the case that there is no direct contractual relationship between the shipper and port stevedores, terminal operators, CFS operators, or inland carriers.
| Type of Claim | Main Claim Recipient | Relation to Himalaya Clause | Practical Considerations |
|---|---|---|---|
| Claims Based on Contractual Liability | Carriers named on the B/L, NVOCCs, shipping lines | Exemption and liability limitation clauses on the B/L are directly applicable | Confirm contracting carrier, liability period, and limitation of liability |
| Claims Based on Tort Liability | Port stevedores, CFS operators, terminal operators, inland carriers | Whether B/L defenses extend to parties with no direct contract is the key issue | Check Himalaya Clause wording and scope of parties covered |
| Subrogation Claims | Claims from insurer to carriers, subcontractors, agents | Since insurers assume the cargo owner’s position, the same defenses apply | Separate insurance payout amount from B/L liability amount |
| Concurrent Claims Against Multiple Parties | Carriers, subcontractors, warehouse operators, inland carriers | Whether total recovery exceeds the B/L liability limit is a concern | Clarify overall liability limit versus individual claim amounts |
| Claims Based on Separate Contracts | Warehouse companies, delivery companies, service providers | Separate contractual terms may apply instead of B/L clauses | Confirm if claim falls outside B/L liability period |
The Himalaya Clause aims to allow parties other than the carrier to invoke the same exemptions and liability limitations under the B/L even for direct claims based on tort liability.
Relationship with Limitation of Liability
The Himalaya Clause is closely related to limitation of liability.
On a Bill of Lading, a carrier’s liability may be limited by Package Limitations or Weight Limitations. However, if the shipper or the cargo insurance company can make direct claims against subcontractors or agents and bypass those liability limits, the carrier’s limitation system could be undermined.
| Comparison Item | If No Himalaya Clause | If Himalaya Clause Exists | Points to Confirm |
|---|---|---|---|
| Direct Claim Target | Claims may be made directly against subcontractors or agents | Subcontractors or agents may also invoke defenses under the B/L | Confirm the scope of protected parties |
| Use of Liability Limitation | Unclear whether parties other than the carrier may benefit from liability limits | Liability limitations may extend to employees, agents, and subcontractors | Check relationship with Package Limitation and Weight Limitation clauses |
| Total Recovery Amount | Claims against multiple parties may exceed the liability cap | May stipulate that total recovery does not exceed the B/L’s limit | Review wording related to aggregate limits |
| Indemnity Relationships | Indemnity claims may be passed from subcontractors back to the carrier | Direct claims against subcontractors may be limited within a certain range | Confirm subcontract agreements and indemnity provisions |
| Subrogation by Insurers | Insurers have broader scope to directly claim against operational parties | Operational parties may assert B/L exemptions and limitation defenses | Verify which defenses apply to each claimant |
The Himalaya Clause may be structured so that not only the carrier but also employees, agents, subcontractors, and other related parties can benefit from the exemptions and limitation of liability set out in the B/L.
Not Just a Clause to Protect Subcontractors
The Himalaya Clause is not solely intended to protect subcontractors.
From the carrier's perspective, there is a risk that subcontractors or agents may be directly claimed by the shipper or marine cargo insurance company, which could ultimately result in indemnity claims being returned to the carrier.
In other words, if direct claims against subcontractors are left unchecked, the carrier may end up bearing a burden that exceeds the liability limits stated on the Bill of Lading.
The Himalaya Clause serves to encompass the carrier, agents, subcontractors, and performing auxiliaries together within the liability limits set forth in the Bill of Lading.
Reasons for Checking Both House B/L and Master B/L
When NVOCCs are involved in transportation, it is important to review the Himalaya Clause on both the House B/L and the Master B/L.
In cases where claims arise from the shipper or cargo owner against the NVOCC, the Himalaya Clause on the House B/L is relevant. Conversely, when the NVOCC seeks recourse against the shipping line or the Actual Carrier, the Himalaya Clause on the Master B/L becomes the issue.
| Comparison Item | House B/L Side | Master B/L Side | Practical Notes |
|---|---|---|---|
| Main Contractual Relationship | Relationship between the shipper or cargo owner and the NVOCC | Relationship between the NVOCC and the shipping line or Actual Carrier | Different B/Ls should be referenced for the same cargo incident |
| Role of the Himalaya Clause | May function as a provision protecting the NVOCC’s subcontractors, agents, or Actual Carriers | May function as a provision protecting the shipping line’s employees, agents, or subcontractors | Confirm the scope of protected parties separately for each B/L |
| Responses to Shipper | Confirm defenses against claims from the shipper to the NVOCC | May not directly provide a basis for responses to the shipper | Prioritize clarifying House B/L terms |
| Recourse Handling | Check the extent of payments the NVOCC makes to the shipper | Check the extent the NVOCC can recover from the shipping line or Actual Carrier | Differences between payment and recovery amounts may arise |
| Limitation of Liability | Package Limitations or Weight Limitations on the House B/L become relevant | Limitation of liability clauses on the Master B/L become relevant | Limits and units may differ |
| Governing Law and Jurisdiction | Follow the clauses on the House B/L | Follow the clauses on the Master B/L | Differences in legal jurisdictions may affect recoverability |
Even if wide protection is provided under the House B/L, insufficient protection on the Master B/L side may leave a shortfall when the NVOCC seeks recourse after compensating the shipper.
Specific Example of the Risk of Shortfall
Consider a case where an NVOCC issues a House B/L and assumes liability as the Contracting Carrier toward the shipper.
Assume a cargo incident results in damages amounting to JPY 10 million claimed by the cargo owner. While the NVOCC and its subcontractors benefit from liability limitations under the House B/L terms, based on the incident circumstances and clause interpretation, the NVOCC is determined to pay JPY 3 million to the shipper or cargo owner.
Subsequently, the NVOCC seeks indemnity from the Actual Carrier, such as the vessel-operating carrier or terminal operator involved in the handling. However, if the Himalaya Clause on the Master B/L side is limited to crew and agents, excluding terminal operators or lower-tier subcontractors, or if liability limitations and exemptions on the Master B/L side apply, the NVOCC may only recover JPY 1 million from the Actual Carrier side.
| Item | Amount Example | Issue Arising | Points to Confirm |
|---|---|---|---|
| Damage Amount Claimed by Cargo Owner | JPY 10 million | Claim made by shipper or cargo owner | Verify cause of incident, applicable liability period, and liability limitations in House B/L |
| Amount Paid by NVOCC to Shipper/Cargo Owner | JPY 3 million | NVOCC responds as Contracting Carrier | Check Himalaya Clause, exemptions, and liability limits under House B/L |
| Amount Recoverable by NVOCC from Actual Carrier | JPY 1 million | Recovery limited by Master B/L liability limits and scope of protected parties | Review Himalaya Clause, liability limits, and governing law on Master B/L |
| Shortfall Remaining with NVOCC | JPY 2 million | Difference between amount paid to shipper and amount recovered from Actual Carrier | Manage potential for recovery and deadlines from the outset |
The key point in this example is that the NVOCC's liability to the shipper and the amount it can recover from the Actual Carrier may not always match.
Not Always Automatically Valid
Even if a Himalaya Clause is printed on the back of a Bill of Lading, it is not necessarily always effective as is.
Whether it applies can vary depending on the laws of the country where a lawsuit is filed, mandatory legal regulations, court rulings, the clause wording, the scope of subcontractors, the segment where the incident occurred, and how the clause is incorporated into the B/L terms.
| Items to Check | Conditions Favoring Application | Conditions Often Contested | Practical Considerations |
|---|---|---|---|
| Wording of Parties Protected | Explicit mention of servants, agents, subcontractors, and independent contractors | Limited to servants and agents only, with independent contractors not specified | Confirm who is included based on the exact wording |
| Treatment of Further Subcontractors | Includes sub-subcontractors and any persons employed by subcontractors | Mentions only subcontractors without further subcontracting | Especially verify if there is a re-subcontracting structure |
| Segment Where Incident Occurs | Incident occurs within the B/L’s period of responsibility | Incident occurs during inland delivery outside the port or during storage under a separate contract | Match the responsibility period with the incident segment |
| Type of Claim | Wording covers both contractual liability and tort liability | Wording covers only contractual liability | Check if claims include direct claims and tort claims |
| Incorporation of Terms | B/L reverse side terms are properly provided or referenced | Full text of terms is not shown or conflicts with front-side statements | Confirm if the terms are incorporated as part of the contract |
| Governing Law and Jurisdiction | Disputes arise under jurisdictions relatively accepting of Himalaya Clauses | Application limited by mandatory laws or court rulings | Confirm which country’s law and courts will decide |
Validity of a Himalaya Clause should not be judged solely by its title. It is necessary to review the actual wording, definitions on the B/L, the scope of parties protected, the incident segment, applicable law, and jurisdiction comprehensively.
Relationship with Cargo Insurance and Subrogation Claims
After paying insurance proceeds to the cargo owner, cargo insurers may pursue subrogation claims against carriers and other related parties.
In such cases, when a Himalaya Clause is present, the exemption and limitation of liability provisions on the Bill of Lading can apply even to direct claims against port stevedores, terminal operators, CFS operators, inland carriers, and similar parties.
Insurance companies and subrogation handlers typically review the segment where the incident occurred, the target of the claim, the Bill of Lading terms, the wording of the Himalaya Clause, and any applicable liability limits side by side.
Even when cargo insurance is in place, the Himalaya Clause can affect the amount recoverable, making it a crucial factor in subrogation assessments.
Common Practical Issues
The Himalaya Clause often presents challenges when claims are made directly against parties other than the carrier or when an NVOCC seeks recourse from the Actual Carrier.
| Case | Reason for Issue | Potential Disadvantage | Practical Measures |
|---|---|---|---|
| Claim made directly against a stevedore | Tendency to seek claims from the actual workers involved in cargo handling accidents | Possible assertion of B/L liability limitations under the Himalaya Clause | Verify whether stevedores or subcontractors are covered by the clause |
| Claim made against a CFS operator for damage during CFS operations | Damage often occurs during devanning or sorting of consolidated cargo | CFS operator may assert defenses as carrier’s auxiliary personnel | Check House B/L, CFS operation records, and applicable liability periods |
| Claim made against terminal operator for incidents inside terminal | Incidents may occur while cargo is moving or stored within CY | Terminal operator may invoke B/L liability limitations | Compare the incident location with the responsibility period under the B/L |
| Claim made against inland carrier for damage during inland delivery | Incidents during transport from port to warehouse or delivery site | Whether the B/L covers inland transport or a separate contract applies is often disputed | Confirm Door to Door terms, inland transport contracts, and B/L liability periods |
| Insurance company subrogates claim against subcontractors | After paying insurance claims, insurers seek recovery from the actual workers | Subcontractors may assert liability limitations under the Himalaya Clause | Check defenses, limitation clauses, and claim deadlines for each party |
| Recourse potential judged based only on House B/L | Master B/L terms become relevant when an NVOCC seeks recourse from the shipping line | Discrepancy between amounts paid to shippers and amounts recoverable from Actual Carriers | Review House B/L and Master B/L side by side |
| Assuming all subcontractors are included by referencing only “servants and agents” | Narrow clause wording may exclude independent contractors and subcontractors beyond the first tier | Misidentification of parties entitled to protection | Confirm the presence of subcontractors, independent contractors, and sub-subcontractors |
| Misunderstanding the clause as eliminating all liability | The Himalaya Clause primarily permits invoking exemption or limitation of liability | Failure to verify cause of incident and applicable liability period | Separate and organize exemptions, limitations, incident causes, and evidence |
Comparison Table of NVOCC and Freight Forwarder Involvement
NVOCCs and freight forwarders can assist with extracting the wording of the Himalaya Clause, identifying protected parties, verifying the accident segment, comparing House B/L and Master B/L, and organizing documentation with insurers. However, they should avoid making conclusive judgments on the final legal validity or liability solely on their own.
| Category | Support Provided | What Should Not Be Concluded | Practical Approach |
|---|---|---|---|
| Clause Wording Review | Extract whether Himalaya Clause exists and identify terms such as servants, agents, subcontractors | Concluding that all related parties are protected simply because the clause exists | Organize the scope of protected parties based on clause wording |
| Accident Segment Verification | Clarify where the accident occurred: port handling, CFS, CY, inland delivery, warehouse storage | Immediately deciding whether the incident is within the B/L liability period | Check B/L, EIR, POD, operation records, and delivery records |
| Identification of Claim Targets | Categorize carriers, subcontractors, agents, terminal operators, inland carriers | Concluding the presence or absence of liability for each claim target | Cross-check relevant clauses, contracts, and accident segments for each claim target |
| House/Master Comparison | Align Himalaya Clause, liability limitation, and exemption clauses between House B/L and Master B/L | Assuming that the recoverable amounts between House B/L and Master B/L sides will be identical | Manage shipper handling separately from claims against the Actual Carrier |
| Insurer Coordination | Organize subrogation materials, B/L clauses, accident documents, and possible claim targets | Recognizing insurance payout amounts as direct liability amounts of carrier or subcontractor | Respond separately regarding insurance payout, liability limits, exemptions, and statute of limitations |
| Initial Response | Prepare wording indicating liability is undetermined, clause confirmation pending, and rights reservation | Early conclusion on liability of carriers, subcontractors, or agents | Make clear that investigation is underway and avoid admission of liability |
Practical Scenario 1: Direct Claim Against the Stevedoring Company
Consider a case where cargo falls during unloading operations, and the cargo owner or marine cargo insurer makes a direct claim against the stevedoring company rather than the carrier.
In such cases, the stevedoring company may assert that they can invoke the exemptions and liability limitations granted to the carrier under the Himalaya Clause on the Bill of Lading. It is especially important to check whether the clause includes terms such as stevedores, subcontractors, or independent contractors.
The claimant should verify whether the incident occurred within the contractual liability period specified on the B/L, whether the stevedore was acting as an agent or auxiliary to the carrier, and whether the Himalaya Clause extends to tort liability. It is necessary to read not only the clause title but also the scope of protected parties and the relevant segment of carriage involved in the incident.
Practical Scenario 2: When an NVOCC Cannot Fully Recover from the Actual Carrier after Paying the Shipper
For example, the NVOCC, acting as the Contracting Carrier on the House B/L, may compensate the shipper or cargo owner for damages, then seek reimbursement from the shipping line or Actual Carrier based on the Master B/L.
In this case, while the Himalaya Clause on the House B/L broadly extends protection to subcontractors and agents of the NVOCC, the scope of protected parties under the Master B/L is often narrower, sometimes excluding terminal operators or secondary subcontractors explicitly. Additionally, liability limitations or exemptions under the Master B/L may restrict the amount the NVOCC can recover.
As a result, differences may arise between the amount the NVOCC pays the shipper and the amount it can recover from the Actual Carrier side. It is important for NVOCCs and freight forwarders to review, early in the claims process, the Himalaya Clauses, liability limits, exemptions, governing law, jurisdiction, and notification deadlines on both the House B/L and the Master B/L side side-by-side.
Practical Scenario 3: When a Marine Cargo Insurer Subrogates Against a CFS Operator
For example, in cases where cargo is damaged during devanning of import LCL shipments, and the marine cargo insurer has paid compensation to the cargo owner, the insurer may subrogate and seek recovery from the CFS operator.
If the CFS operator was acting as a performance auxiliary to the carrier, they may invoke the Himalaya Clause to assert the liability limitations or exemptions stated on the Bill of Lading. Conversely, if the CFS work was performed outside the carrier’s period of responsibility under the B/L and was done under a separate warehouse or service contract, the applicability of the Himalaya Clause could be disputed.
Insurance companies and subrogation handlers should verify the House B/L, Master B/L, CFS operation records, gate-in and gate-out logs, timing of the incident, survey reports, the Himalaya Clause wording, and the contractual position of the CFS operator. It is important to distinguish between the amount paid by insurance and the recoverable amount under the B/L or service contract.
Documents to Verify
When reviewing the Himalaya Clause, organize the following documents:
- House B/L front
- House B/L reverse side terms
- Master B/L front
- Master B/L reverse side terms
- Full text of the Himalaya Clause
- Definition clauses for Carrier, Merchant, Subcontractor, Servant, Agent, etc.
- Contract of carriage agreement, booking documents
- Contract documents with subcontracted carriers
- Work records with CFS, warehouse, delivery companies
- Claim Letter
- Survey Report
- Subrogation claim documents
- Documents identifying the section where the incident occurred
- Cargo receipt, POD, EIR, gate-in/out records
- Terminal work records, CFS operation logs, delivery records
- Cargo insurance policy, insurance payout documents
- Communication records with shipping company, overseas agents, and subcontractors
It is especially important to confirm during whose operation the damage allegedly occurred and whether the claim is directed to the carrier named on the B/L, the subcontractor, or the agent.
Four-Column Checklist
When reviewing the Himalaya Clause, organize the process by separating the situation, the party to verify with, the points to check, and the actions to take if issues arise.
| Situation | Party to Verify With | Points to Check | Actions if Issues Arise |
|---|---|---|---|
| When Reviewing B/L Terms & Conditions | NVOCC, Shipping Line, Overseas Agent | Presence of Himalaya Clause, wording on protected parties | Obtain full terms and confirm the scope of protected parties |
| When Claiming Directly Against Subcontractors | Subcontractors, Shipping Line, NVOCC, Insurance Company | Whether subcontractor, independent contractor, or agent are included | Confirm if the party being directly claimed is a protected party |
| When Identifying Incident Segment | Shipper, Warehouse, CFS Operator, Terminal, Inland Carrier | Location and timing of the incident, whether within the B/L liability period | If outside B/L liability period, review the relevant separate contract terms |
| When Checking Liability Limitations | NVOCC, Shipping Line, Insurance Company, Lawyer | Package limitation, weight limitation, total liability cap | Summarize total claims against carrier and subcontractors |
| When Matching House and Master B/L | NVOCC, Shipping Line, Overseas Agent | Protected parties, liability limits, and exemption clauses in House and Master B/L | Separate checks for shipper handling and subrogation claims against the Actual Carrier |
| When Handling Subrogation Claims | Insurance Company, Cargo Owner, NVOCC, Subcontractors | Amount of insurance payment, claim parties, Himalaya Clause, liability limits | Clearly separate the insurance payout amount from recoverable amounts under the B/L |
| When Preparing Initial Response | Shipper, Insurance Company, Shipping Line, Subcontractors | Expressions indicating acceptance of liability, reservation of rights, ongoing investigation | Explicitly state that liability is not yet determined |
| When Managing Deadlines | Shipping Line, Insurance Company, Lawyer, Overseas Agent | Damage notification deadlines, filing deadlines, time bar extensions | Consider extending deadlines while confirming the claim parties |
Points to Note in Initial Responses
In incidents involving the Himalaya Clause, it is important to avoid admitting liability in the initial response.
The defenses and limitations of liability that may apply can differ depending on whether the claim is directed at the carrier, NVOCC, subcontractor, or agent.
The initial response should clearly state receipt of the claim or notification, confirmation of the Bill of Lading terms and the Himalaya Clause, verification of the claimant and the liability relationship, that liability is currently undetermined, review of any applicable liability limits, exemptions, and time limits, and that the response does not imply an admission of liability.
Expressions for Confirmation in English
When confirming with overseas agents, shipping lines, or subcontractors, avoid admitting liability. Instead, focus on verifying the position under the B/L terms, the scope of protected parties, and the segment where the incident occurred.
| Situation | Sample English Phrase | Purpose | Notes |
|---|---|---|---|
| Request for full B/L terms | Please provide the full terms and conditions of the relevant B/L. | To review the complete terms including the Himalaya Clause | Request House B/L and Master B/L separately |
| Confirming the Himalaya Clause | We are reviewing the Himalaya Clause under the B/L terms. | To indicate that the Himalaya Clause is under review | Useful for initial inquiries |
| Confirming protection for subcontractors | Please confirm whether the subcontractor is covered by the Himalaya Clause. | To check if subcontractors are included as protected parties | This phrase does not admit liability |
| Confirming limitation of liability application | Please confirm whether the limitation of liability applies to the subcontractor or agent. | To verify if subcontractors or agents can invoke limitation of liability | Confirm separately for each claimant |
| Confirming scope of protected parties | Please confirm the scope of protected parties under the B/L terms. | To clarify the range of servants, agents, subcontractors, etc. | Check the exact wording of the clause |
| Confirming the incident segment | Please confirm where and when the alleged damage occurred. | To verify the location and timing of the incident | Used to compare with the B/L responsibility period |
| Clarifying liability not yet determined | This response shall not be construed as an admission of liability. | To avoid admitting responsibility | Useful in initial responses |
| Reservation of rights | We reserve all rights and defenses under the applicable B/L terms. | To reserve exclusions, limitation of liability, and defenses related to deadlines | Helpful when communicating with insurers and shipping lines |
Common Misconceptions
| Common Misconception | Actual Understanding | Practical Notes |
|---|---|---|
| If a Himalaya Clause exists, all subcontractors are protected | The scope of protection varies depending on the clause wording. | Check for the presence of servants, agents, subcontractors, independent contractors, and sub-subcontractors. |
| Any party handling the cargo is covered | Even if a party handled the cargo, it matters whether they are positioned as involved in performing carriage under the B/L. | Confirm the accident segment, contractual relationships, and B/L liability period. |
| A Himalaya Clause eliminates all liability | It mainly serves to invoke exemptions or liability limitations; it does not completely negate responsibility in all cases. | Separate verification of accident causes, exemption grounds, and liability limits is required. |
| It is sufficient to check only the House B/L | In NVOCC practice, the House B/L applies when dealing with the shipper, while the Master B/L is relevant for claims against Actual Carriers. | Review both House B/L and Master B/L side by side. |
| Claims based on tort can bypass the B/L terms | The Himalaya Clause seeks to extend B/L defenses even to direct claims based on tort liability. | Avoid drawing conclusions based solely on whether the claim is contractual or tortious. |
| Insurance payments can be fully recovered as is | The amounts paid by insurers and the recoverable sums under the B/L or from subcontractors are separate issues. | For subrogation claims, check liability limits, exemptions, and deadlines for filing suit. |
| If the accident occurs at the port or warehouse, the Himalaya Clause does not apply | If port handling, CFS, CY, or terminal operations fall within the B/L liability period or relate to carriage performance, they may be covered. | Confirm the liability period and role of the operation, not just the accident location. |
Practical Points to Note
- The Himalaya Clause relates to the risk of direct claims against subcontractors and agents.
- Confirm the scope of protected parties based on the clause wording.
- Verify the applicability not only to contractual liability but also to tort liability.
- Ensure that the total liability limit does not exceed the limit stated on the B/L.
- Match the segment where the incident occurred with the involvement of the parties protected.
- Check both the House B/L and the Master B/L.
- When subrogation claims come from marine cargo insurers, confirm whether the claim recipient can invoke the Himalaya Clause.
- Do not admit liability in initial responses; instead, limit verification to B/L terms and the incident segment.
- Along with identifying the claim recipient, confirm the applicable law, jurisdiction, and the deadline for filing a lawsuit.
Summary
The Himalaya Clause is a provision that extends the exemptions and limitations of liability granted to the carrier named on the Bill of Lading (B/L) to employees, agents, subcontractors, stevedores, terminal operators, CFS operators, inland carriers, and others involved in the carriage chain.
This clause serves to prevent shippers, cargo owners, and marine cargo insurers from bypassing the liability limits on the B/L by making direct claims against subcontractors or agents.
In practice, it is important to verify the scope of those protected under the clause, its applicability to tort liability, the segment of the voyage where the incident occurred, differences between House B/L and Master B/L, the status of the party subject to subrogation claims, and the risk of shortfall between recoverable amounts and actual losses.
The key point of this article is to understand the Himalaya Clause not merely as a "subcontractor protection clause" but as a provision that links carrier liability, subcontractor liability, subrogation claims, liability limitation, and the gap risk faced by NVOCCs.
Marine cargo insurance terms can vary more significantly based on conditions than on premiums. Choosing appropriate insurance terms and interpreting policy clauses should be consulted with specialized insurers or insurance agents.
