Electronic Bills of Lading Under China's Revised Maritime Law

China's revised Maritime Law took effect on May 1, 2026. One of its most commercially important changes is the new statutory treatment of electronic transport records.

The legal question is no longer whether the shipping industry can experiment with electronic documentation. The statute expressly recognizes electronic transport records that satisfy legal conditions and gives them the same effect as transport documents in specified circumstances.^[1]

The high-value issue is narrower:

The specific issue#

When a cargo delivery dispute occurs, what must a carrier, shipper or cargo claimant be able to prove about the creation, control, transfer, integrity and conversion of an electronic transport record?

This is not an abstract digitization issue. It affects misdelivery claims, title control, documentary trade, fraud, letters of indemnity, platform evidence and litigation strategy.

1. Article 82 creates the statutory bridge between paper and electronic records#

Article 82 of the revised Maritime Law defines an electronic transport record as information issued by a carrier through electronic communication under a contract of carriage by sea, evidencing the contract and the carrier's receipt or loading of the goods. It distinguishes transferable and non-transferable electronic transport records.^[1]

The same article provides that an electronic transport record satisfying conditions prescribed by law and administrative regulations has the same effect as a transport document and cannot be denied legal effect merely because it is electronic.^[1]

This matters because a litigant should no longer frame the dispute as “paper versus digital.”

The key question becomes:

Did the electronic record and the system using it satisfy the statutory requirements?

2. Consent still matters#

Article 83 states that the carrier and shipper may issue and use an electronic transport record by agreement.^[1]

That means the digital system should preserve evidence of consent.

A carrier should not assume that a customer using a web portal once has agreed to substitute an electronic record for a bill of lading in all future shipments.

The contract architecture should identify:

• whether electronic records are permitted;
• which platform will be used;
• when the record is deemed issued;
• how the holder is identified;
• how transfer occurs;
• how notice is delivered; and
• what happens if the platform is unavailable.

Consent should be tied to the specific legal mechanism, not merely to “electronic communications.”

3. Article 84 establishes minimum record requirements#

Article 84 requires an electronic transport record to contain the information required by the relevant transport-document rule and be available for retrieval and use; the information must be complete and accurate; the issuer must be identifiable; and the holder must be able to prove its identity.^[1]

Each requirement has evidentiary consequences.

Retrievable and usable#

A screenshot created after the dispute may not be enough. The platform should be able to demonstrate that the record existed in an accessible form during the transaction.

Complete and accurate#

The system should preserve the operative version. If fields can be altered without an audit trail, the evidentiary value of the record can be attacked.

Identifiable issuer#

The platform should link issuance to the carrier or authorized person.

Identifiable holder#

The system should demonstrate why a particular person had legal control of the record at a particular time.

These are system-design questions as much as legal questions.

4. Transferable records face a higher threshold#

Article 85 requires a transferable electronic transport record to contain information concerning transferability and transfer procedures. It also requires use of a reliable method or reliable transaction system to ensure singularity and integrity of the record and to protect the holder's exclusive control.^[1]

The statutory concepts of singularity, integrity and exclusive control are central.

In paper commerce, physical possession of the original bill of lading can perform a control function.

In an electronic environment, the system must create the functional equivalent.

A dispute will therefore ask:

• Can more than one person appear to hold the same transferable record?
• Can the record be duplicated?
• Can it be altered after transfer?
• Does the system log each transfer?
• Can a former holder still exercise control?
• How is a compromised account handled?

The platform design becomes evidence.

5. The law anticipates further standards for reliability#

Article 85 states that standards for transfer, exclusive control, conversion and the determination of reliable methods or systems will be formulated by the national cyberspace authority together with the State Council's transport authority.^[1]

This creates a compliance-monitoring obligation.

Carriers and platforms should not treat their 2026 system design as permanently sufficient. They need to monitor subsequent standards and adjust technical and contractual controls.

The legal department should therefore assign responsibility for tracking implementing rules.

6. Conversion between paper and electronic records is legally significant#

Article 86 allows conversion between an electronic transport record and a transport document with agreement of the carrier and shipper or document holder. The conversion must state information concerning the conversion and keep the recorded content consistent before and after conversion.^[1]

Conversion creates a particularly dangerous fraud window.

Imagine:

• a paper bill is issued;
• it is converted to an electronic record;
• the paper original is not effectively neutralized;
• the electronic record is transferred;
• someone later presents the paper document for delivery.

The legal and operational system must prevent competing control claims.

A conversion protocol should therefore address:

• surrender or cancellation of prior form;
• timestamp;
• identity of requesting party;
• exact content comparison;
• system notation;
• notification to relevant parties;
• prevention of duplicate use; and
• audit logs.

7. Misdelivery claims will turn on the control history#

The cargo-delivery problem is simple in business terms: the carrier released goods to the wrong party.

In an electronic-record case, the court may need to reconstruct the control history.

The carrier should be able to produce:

• issuance log;
• holder identity;
• transfer records;
• authentication events;
• conversion events;
• release instruction;
• terminal message;
• account-security alerts; and
• final delivery confirmation.

If the carrier cannot show who controlled the record when delivery occurred, it may face difficulty defending the release.

8. Account security becomes part of maritime risk#

Electronic control often depends on user accounts, keys, authentication credentials or platform permissions.

A compromised account can create a dispute resembling forged endorsement on paper, but the evidence will be digital.

The platform's security framework should include:

• multi-factor authentication;
• role-based permissions;
• login anomaly detection;
• device logs;
• credential-reset controls;
• transaction confirmation;
• audit logs; and
• incident response.

The maritime legal team and cybersecurity team must therefore coordinate.

9. “Holder identity” must be more precise than an email address#

Article 84 requires the holder to be able to prove identity.^[1]

For corporate users, the system should distinguish:

• legal entity;
• authorized employee;
• representative capacity;
• transfer authority; and
• beneficial control of the account.

An email address may identify a user but not establish the user's legal authority to transfer a transport record.

Corporate authority should be embedded into onboarding and authorization controls.

10. Documentary trade adds another layer#

Electronic bills of lading may interact with trade finance.

Banks, buyers and sellers need confidence that the electronic record can support documentary transactions.

The legal analysis should consider:

• whether bank systems accept the platform;
• how control transfers to and from financing banks;
• whether pledge or security interests can be reflected;
• how release occurs after payment;
• how discrepancies are handled; and
• how conversion to paper affects bank control.

A carrier should not design its record system only around shipper-to-consignee transfers if banks routinely enter the control chain.

11. Freight forwarders and NVOCCs need separate identity controls#

Shipping chains may involve:

• ocean carrier;
• NVOCC;
• freight forwarder;
• booking agent;
• shipper;
• consignee;
• notify party.

The electronic system should make clear who is issuing what legal instrument.

A forwarder's house bill is not the same record as the ocean carrier's master document.

The digital platform should not blur issuer identity or make it appear that one record controls another unless the contractual architecture supports that result.

12. Letters of indemnity do not cure every digital-release problem#

Commercial pressure sometimes leads carriers to release cargo against a letter of indemnity where original transport documentation is unavailable.

Electronic records may reduce certain paper-document delays, but they do not eliminate misdelivery risk.

If the system indicates that another party has exclusive control of a transferable record, a private indemnity from the requesting party should not automatically override the legal rights associated with the record.

The carrier should have an escalation protocol for delivery requests that conflict with the platform's control status.

13. Evidence preservation after a disputed release#

When a misdelivery allegation arises, the carrier should immediately preserve:

• full platform logs;
• user-account history;
• IP/device records where lawful;
• email and messaging;
• conversion records;
• release instructions;
• terminal records;
• customs release information;
• payment records;
• security alerts; and
• internal approvals.

Do not allow routine log retention to overwrite the evidence.

The litigation hold should include the platform vendor if a third party operates the system.

14. Platform contracts should allocate evidentiary responsibilities#

If a carrier uses a third-party electronic transport platform, the service agreement should address:

• data retention;
• audit logs;
• access to evidence;
• system uptime;
• cybersecurity;
• incident notification;
• record export;
• regulatory compliance;
• subcontractors;
• liability; and
• post-termination evidence access.

A carrier should not discover during litigation that the vendor retains only 30 days of detailed logs.

15. The revised Maritime Law also modernizes the broader liability framework#

The 2025 revision did more than add electronic transport records. Official legislative explanation notes modernization of maritime rights and obligations and the addition of a dedicated ship-source oil pollution liability regime, among other changes.^[2]

That broader modernization matters because electronic documentation may be used in casualty, cargo and pollution claims as well as routine delivery.

Claims procedures should therefore integrate digital evidence into the wider incident-response framework.

16. Case study: electronic record converted to paper#

Assume:

• carrier and shipper agree to use a transferable electronic transport record;
• the shipper transfers control to a bank;
• the buyer arranges payment;
• a system issue leads the parties to convert the record to paper under Article 86;
• the paper bill is couriered;
• meanwhile a terminal employee receives an electronic release message generated before conversion;
• cargo is released before the paper holder presents the document.

The litigation issues may include:

• Was conversion valid?
• Was the prior electronic control terminated?
• Did the system clearly record the conversion?
• Was the terminal notified?
• Who had legal control at release?
• Was the release message stale?
• Did the carrier's internal procedure treat conversion as a critical event?
• What loss was caused?

The most important evidence may be system logs rather than witness recollection.

17. A legally defensible electronic-record system should pass six tests#

Test 1: identity#

Can the issuer and holder be reliably identified?

Test 2: integrity#

Can unauthorized alteration be detected?

Test 3: singularity#

Can there be only one operative transferable record?

Test 4: exclusive control#

Can the system show which holder had control at each moment?

Test 5: transfer#

Is the transfer process clear, logged and irreversible from the prior holder's perspective?

Test 6: conversion#

Can paper/electronic conversion occur without duplicate rights?

These tests map directly to Articles 84–86.^[1]

18. Contract amendments carriers should make#

Carriers using electronic records should update standard terms to address:

• agreement to electronic use;
• governing platform;
• identity and authority;
• record issuance;
• transfer rules;
• conversion;
• cybersecurity;
• account compromise;
• notice;
• evidence;
• system outage;
• fallback to paper; and
• dispute handling.

The contract should not attempt to waive mandatory statutory rights.

19. Cargo interests should also conduct platform diligence#

Shippers and consignees should not assume all electronic platforms are equivalent.

Before accepting a transferable electronic record, a cargo interest should ask:

• Is the system designed around exclusive control?
• What happens if credentials are compromised?
• Can records be exported for evidence?
• Can the system demonstrate transfer history?
• What is the conversion process?
• Which law governs the platform relationship?
• Is the system recognized by financing banks?

A digital bill is not merely a PDF version of a paper bill.

20. Claims protocol for the first 24 hours after suspected misdelivery#

• stop further delivery if cargo remains;
• freeze platform records;
• identify current and historic holders;
• preserve conversion records;
• preserve terminal instructions;
• identify any letter of indemnity;
• notify insurers;
• inspect security alerts;
• obtain cargo disposition evidence;
• assess ship/arrest/security exposure if relevant.

The speed of digital systems makes delay especially dangerous.

21. What not to do#

Do not:

• rely on screenshots as the only record;
• allow manual alteration without audit trail;
• allow several corporate users to share one credential;
• convert from electronic to paper without neutralizing prior control;
• assume the platform vendor will retain litigation-grade evidence;
• release cargo based solely on a stale email;
• treat electronic documentation as an IT project separate from maritime claims.

22. Conclusion#

The revised Maritime Law gives electronic transport records a clear legal foundation, but statutory recognition does not eliminate disputes.

Articles 82–86 place practical emphasis on:

• agreement;
• complete and accurate information;
• identifiable issuer;
• provable holder identity;
• singularity;
• integrity;
• exclusive control;
• reliable transfer systems; and
• controlled conversion between electronic and paper forms.^[1]

These are not abstract legal standards. They are system and evidence requirements.

For carriers, cargo interests and platforms, the central compliance question is:

If a delivery dispute arose tomorrow, could we prove exactly who controlled the electronic transport record at every relevant moment?

If the answer is no, the system is not litigation-ready.

23. The carrier should distinguish legal control from operational release authority#

One of the most important implementation points is that the person with operational ability to release cargo should not be able to override the legal control status of the electronic transport record.

In many shipping organizations:

• documentation team controls the transport record;
• customer service communicates with consignee;
• terminal receives release instruction;
• finance confirms payment;
• operations prioritizes vessel or yard efficiency.

If those systems are not integrated, a terminal may release cargo based on a service email even though the transferable electronic record remains under another holder's exclusive control.

The carrier should therefore define a single source of release authority.

Operational release should require system confirmation that:

• the correct party holds the record;
• any surrender process is complete;
• no conversion conflict exists;
• no legal hold exists;
• required payment conditions are met.

The confirmation should be logged.

24. “Reliable method” should be documented before courts have to interpret it#

Article 85 refers to reliable methods or reliable transaction systems that ensure singularity and integrity and protect exclusive control.^[1]

Until implementing standards become fully mature, businesses should document why their selected system is reliable.

The evidence file should include:

• architecture;
• authentication model;
• audit trail;
• duplicate-prevention controls;
• transfer logic;
• conversion logic;
• cybersecurity testing;
• access controls;
• incident response;
• business continuity;
• external certifications where applicable.

If litigation occurs, the company should not need to reverse-engineer this explanation after the event.

25. System outage clauses need more than a generic force majeure provision#

An electronic transport platform can fail at the moment cargo is ready for release.

The contract should specify:

• what constitutes system unavailability;
• who certifies the outage;
• whether paper fallback is allowed;
• how current holder status is verified;
• how duplicate records are prevented;
• whether shipment/delivery deadlines extend;
• how the parties communicate during outage.

A generic force-majeure clause does not answer these operational questions.

26. Fraud controls should be designed around control transfer#

Electronic records reduce some paper risks but create cyber-enabled fraud risk.

Potential attacks include:

• credential theft;
• social engineering;
• fraudulent account-reset requests;
• unauthorized change of corporate administrator;
• malicious transfer instruction;
• compromised email used to request cargo release.

The legal system should require enhanced verification for high-risk events such as:

• first transfer to a new corporate user;
• change of bank;
• record conversion;
• emergency release;
• credential reset;
• change of company administrator.

These controls can later become central evidence that the carrier used a reliable system.

27. A shipper should preserve evidence of authority when transferring the record#

A corporate shipper may have many employees with platform access.

The platform should show whether the person initiating transfer had authority.

Internal controls can include:

• named administrators;
• dual approval for transfer;
• transaction limits;
• segregation of duties;
• role-based permissions.

This protects both the shipper and carrier against disputes where an employee acts outside authority.

28. Banks should be involved in platform design for financed trades#

Where documentary trade finance is significant, the bank may become the commercial holder or control intermediary.

The platform should support:

• bank onboarding;
• secured control;
• release after payment;
• transfer to buyer;
• evidence of pledge or financing interest where applicable.

A carrier that designs a digital system without considering banks may find that customers convert back to paper for financed transactions, increasing conversion risk.

29. Arbitration clauses in platform terms can create unexpected fragmentation#

There may be two contracts:

• contract of carriage;
• platform services agreement.

If the carriage contract selects a maritime court but the platform agreement selects foreign arbitration, a dispute about electronic control may straddle both.

The carrier and platform provider should align dispute clauses where possible or clearly allocate issues.

Otherwise a cargo claimant may litigate misdelivery in one forum while the carrier arbitrates system failure against the platform vendor elsewhere.

30. Platform vendors should be treated as critical litigation vendors#

The vendor contract should require cooperation with:

• evidence preservation;
• expert testimony;
• log extraction;
• court orders;
• incident investigation;
• cybersecurity forensics.

The carrier should also have the right to obtain data in a usable format if the vendor becomes insolvent or the contract terminates.

This is analogous to a bank retaining payment records or a terminal retaining gate logs: evidence access is part of the legal infrastructure.

31. Cargo owners should run their own evidence process#

Cargo interests should preserve:

• purchase contract;
• payment documents;
• electronic record history;
• transfer notices;
• platform screenshots and exports;
• bank communications;
• delivery instructions;
• communications with carrier;
• loss evidence.

A claimant should not depend entirely on the carrier's system records.

32. The revised law increases the importance of technical expert evidence#

A dispute over singularity, integrity or exclusive control may require technical explanation.

The parties may need an expert to explain:

• system architecture;
• hashing or integrity mechanisms;
• access logs;
• authentication;
• duplicate prevention;
• timestamping;
• transfer sequence.

Legal counsel should identify potential experts early and preserve system versions used at the time of the transaction.

33. A digital record should have a version history that can survive years#

Shipping claims may arise long after a record is issued.

The platform's retention period should therefore be tested against:

• limitation periods;
• contractual claims;
• insurance recovery;
• regulatory investigations.

A system optimized only for current operational data may not preserve enough evidence for later litigation.

34. Internal audit should test one cargo-release transaction end to end#

A carrier should periodically select a real shipment and reconstruct:

• shipper agreement to electronic use;
• issuance;
• holder identity;
• each transfer;
• any bank involvement;
• conversion;
• release instruction;
• terminal delivery;
• retention of evidence.

If internal audit cannot reconstruct the chain, neither will litigation counsel.

35. Special attention is required during conversion#

Conversion is the moment when duplicate control is most likely.

A defensible procedure should require:

• request by authorized holder;
• validation of current record;
• cancellation/neutralization of prior form;
• creation of replacement;
• record of identical substantive content;
• notification to carrier, holder and terminal;
• post-conversion system lock;
• audit confirmation.

Article 86's requirement that conversion be noted and content remain consistent should be treated as a workflow requirement, not merely a document statement.^[1]

36. Incident response should classify the dispute immediately#

When a release problem occurs, classify it as one or more of:

• identity failure;
• unauthorized transfer;
• platform compromise;
• conversion failure;
• stale release instruction;
• internal human error;
• fraudulent document;
• contractual misunderstanding.

Each category requires different evidence.

Cybersecurity specialists should be involved early where account compromise is suspected.

37. Insurers should receive digital evidence, not only a narrative report#

Cargo insurers, liability insurers and P&I interests may need to evaluate coverage and recovery.

The insured should provide:

• record chain;
• platform logs;
• delivery evidence;
• notices;
• security incident details.

The insurer may later pursue subrogation, so evidence preservation benefits both insured and insurer.

38. The legal team should issue an electronic-document playbook#

The playbook should state:

• approved platforms;
• required contract clauses;
• onboarding standards;
• holder verification;
• transfer process;
• conversion process;
• release controls;
• incident response;
• retention;
• evidence export.

This turns the revised Maritime Law into operational control.

39. Final practical test#

Before relying on an electronic transport record, ask one question:

Could an independent court reconstruct the complete control chain from system evidence without relying on the memory of employees?

If not, the process needs redesign.

That is the practical meaning of building around integrity, singularity and exclusive control.

Legal sources#

^[1] Maritime Law of the People's Republic of China (2025 Revision), effective May 1, 2026, especially Articles 82–86 on electronic transport records: https://www.npc.gov.cn/npc/c2/c30834/202510/t20251028_449061.html

^[2] National People's Congress, legislative explanation of the Maritime Law revision, including electronic transport records and ship-source oil pollution changes: https://www.npc.gov.cn/npc/c2/c30834/202510/t20251031_449196.html

This article is general legal information, not legal advice on a specific shipment or dispute.