Insights
Paperless Trade Fails at the Border: Why Electronic Documents Need Portable Legal State
APEC is moving paperless trade from policy language into cross-border pilots through the APEC Centre of Excellence for Paperless Trade. Its initial work focuses on electronic bills of lading, certificates of origin, invoices and customs bonds, with real transactions intended to expose where legal recognition, technical standards and operational workflows still break between jurisdictions. The deeper lesson is that a digital trade document is useful only when its authority, control, current...
This starts a temporary private draft. It is not public, listed for sale or shared automatically.
International trade has been “going paperless” for decades.
Invoices became PDFs.
Bills of lading were scanned.
Certificates were emailed.
Customs declarations moved online.
Portals replaced fax machines.
Yet the world still moves extraordinary amounts of paper.
On 1 September 2026, APEC said around four billion paper documents continue to circulate through global trade each year and that less than one percent are fully digitalised.
The reason is not simply slow technology adoption.
The harder problem appears when a document crosses a border.
APEC’s Centre of Excellence for Paperless Trade, or ACCEPT, is now trying to address that problem through practical pilot programmes. Its initial work focuses on four document types:
- electronic bills of lading;
- certificates of origin;
- invoices; and
- customs bonds.
APEC: Paper Trail Holds Back Digital Trade Processes as APEC, ABAC Push Practical Fixes
The pilots are intended to test electronic trade documents in real transactions and identify where legal, technical and operational barriers remain.
That is more important than another digitisation initiative.
It asks a different question:
Can an electronic document remain legally meaningful when it leaves the system, company or jurisdiction that created it?
That is a market-infrastructure problem.
A PDF is digital but not necessarily a digital trade instrument
Consider an invoice.
A supplier creates it electronically.
It is stored as a PDF.
The supplier emails it to the buyer.
The buyer uploads it into an accounts-payable system.
No paper was used.
The workflow is digital.
But little has changed about the legal structure.
The PDF can still be:
- copied;
- duplicated;
- renamed;
- forwarded;
- modified;
- re-exported;
- or uploaded into several systems.
It does not inherently tell the next party:
- whether it is authoritative;
- whether the buyer accepted it;
- whether a credit note later reduced it;
- whether the receivable is still outstanding;
- whether the seller still owns the receivable;
- or whether another financier already has rights over it.
The file is digital.
The asset state may still be analogue.
An electronic trade document needs more than content
A useful electronic trade document can require several layers.
At minimum:
Content
+
Identity
+
Authority
+
Current state
+
Provenance
For transferable records, another layer becomes essential:
Control
And in cross-border use:
Recognition by another legal system
The difference is profound.
A digital invoice can be evidence.
A legally recognised electronic bill of lading can potentially perform functions that historically depended on possession of an original document.
Those are not the same digitalisation problem.
The bill of lading exposes the real challenge
The bill of lading is one of the clearest examples.
Traditionally, it can perform several functions.
Depending on the transaction and law, it may serve as:
- receipt for goods;
- evidence of the contract of carriage;
- and, for negotiable bills, a document whose possession can be connected to rights relating to delivery of the goods.
That last function is difficult to reproduce electronically.
A paper original has a useful physical property:
only one person can physically possess that original at a time.
A digital file does not have that property.
It can be copied perfectly.
That creates the control problem.
Digital possession needs a legal equivalent
UNCITRAL’s Model Law on Electronic Transferable Records, or MLETR, addresses this concept using control rather than pretending that electronic files can be physically possessed.
The model is intended to enable electronic transferable records to perform functions equivalent to transferable paper documents where legal requirements are satisfied.
APEC’s 2026 Ministers Responsible for Trade explicitly encouraged economies to work toward aligning legal frameworks with MLETR principles, while recognising different levels of readiness and capacity.
APEC: 2026 APEC Ministers Responsible for Trade Joint Statement
This creates a much stronger digital object than:
bill-of-lading.pdf
The relevant record may need to know:
Current controller
Previous controller
Transfer event
Effective time
Integrity status
Authoritative record
Surrender / cancellation state
That is a lifecycle.
Cross-border recognition is the missing bridge
A company can build a perfect electronic-document system inside one jurisdiction.
Its trading partner may operate under another legal framework.
The first system may recognise electronic control.
The second may still require paper.
One authority may accept an electronic certificate.
Another may require a particular signature or verification method.
One carrier platform may recognise a transfer.
Another platform may not interoperate.
This is why APEC says the larger challenge increasingly appears when documents must move between economies.
The problem is not:
Can we create an electronic document?
It is:
Will the next institution recognise its legal and operational state?
That difference is critical.
Portability is not the same as interoperability
A file is portable if it can be sent.
A trade instrument is interoperable if another system can understand and act on it.
Suppose an electronic bill of lading moves from Platform A to Platform B.
Platform B needs more than text fields.
It may need to know:
- which carrier issued it;
- which shipment it represents;
- whether it is transferable;
- who currently controls it;
- whether it has already been transferred;
- whether it has been surrendered;
- whether the goods have been delivered;
- whether the record is authentic;
- and which legal regime recognises it.
If that context is lost, interoperability is cosmetic.
ACCEPT is moving from principles to transactions
APEC’s announcement says ACCEPT intends to use pilot programmes involving real trade transactions.
That is important.
Policy documents can say:
Electronic records should be recognised.
A real shipment forces much harder questions.
For example:
Exporter in Economy A
->
Electronic bill of lading
->
Bank in Economy B
->
Importer in Economy C
->
Carrier / port in Economy D
Now the same record must survive:
- different legal frameworks;
- different technical platforms;
- different compliance rules;
- different identity systems;
- and different operational processes.
A pilot reveals where the chain breaks.
Four document types mean four different legal-state models
APEC’s initial focus is deliberately practical.
But the four document types should not be forced into one generic schema.
Electronic bill of lading
May require:
- issuer;
- shipment;
- goods;
- current controller;
- transferability;
- endorsement or transfer history;
- surrender;
- delivery;
- and legal recognition.
Certificate of origin
May require:
- exporter;
- producer;
- goods;
- origin criteria;
- issuing or certifying authority;
- verification;
- validity;
- amendment;
- and customs acceptance.
Invoice
May require:
- seller;
- buyer;
- commercial transaction;
- amount;
- tax;
- due date;
- credit notes;
- buyer acknowledgement;
- current outstanding receivable;
- and financing history.
Customs bond
May require:
- principal;
- surety;
- customs authority;
- obligation;
- amount;
- effective period;
- claim state;
- release;
- and jurisdiction.
All four are “trade documents”.
They are not the same asset.
An invoice is not automatically a transferable record
This distinction matters for DaDepo.
An invoice can evidence an amount claimed by a seller.
The underlying receivable is the legal right to payment.
The invoice itself may not be the object that is assigned or financed.
A structured record should distinguish:
Electronic invoice
->
Evidence of commercial amount
Receivable
->
Underlying payment right
Assignment / financing
->
Change in ownership or security over that right
Paperless trade can improve the evidence chain.
It does not erase the difference between document and right.
A bill of lading can be closer to an asset-state object
An electronic bill of lading can carry a richer control function.
The record may need to answer:
Who currently controls it?
That is very close to a depository question.
If control changes from Seller A to Bank B and then to Buyer C, the lifecycle may be:
Issued
->
Controlled by exporter
->
Transferred to financing bank
->
Transferred to importer
->
Surrendered
->
Goods released
Every transition matters.
A static PDF cannot represent that sequence reliably by itself.
Control needs exclusivity
A transferable record cannot safely have two contradictory current controllers.
If Platform A says:
Controller: Bank X
and Platform B says:
Controller: Importer Y
the electronic-document market has a double-spend problem.
This is conceptually similar to:
- duplicate invoice finance;
- double pledging;
- duplicate title records;
- and conflicting collateral claims.
The technical implementation may differ.
The underlying market problem is the same:
There must be one current authoritative state for the right being transferred.
Electronic documents need event history
A current record is necessary.
History is equally important.
For a trade document, events can include:
- issued;
- amended;
- accepted;
- rejected;
- transferred;
- endorsed;
- financed;
- pledged;
- surrendered;
- replaced;
- cancelled;
- expired;
- presented to customs;
- verified;
- and closed.
The document is not simply:
Status: Active
It is a sequence of state transitions.
Amendments are especially dangerous in disconnected systems
Suppose an exporter issues an invoice for $500,000.
Then:
- a credit note reduces it by $20,000;
- shipment quantity changes;
- customs classification changes;
- the buyer accepts $480,000;
- and the receivable is financed.
If one party has version 1 and another has version 3, the trade is digitally fragmented even if all files are electronic.
A portable state model needs:
Version
Effective date
Supersedes
Source
Author
Reason
Current authoritative state
That is document provenance.
The authority behind a document matters
A certificate of origin is valuable because a recognised authority or process stands behind it.
A customs bond is valuable because a surety stands behind an obligation.
An invoice is created by the seller.
A bill of lading is issued by or on behalf of a carrier.
Those assertions have different authority.
A structured trade record should therefore preserve:
Who asserted this field?
and:
Under what authority?
For example:
Country of origin
Source: Certificate of origin
Issuer: Authorised chamber
Verified: Customs authority
is stronger than:
Origin: China
with no provenance.
Customs digitalisation adds another verification layer
On 3 September, APEC reported that customs authorities and businesses were accelerating work on:
- AI-enabled customs systems;
- paperless trade;
- electronic certification;
- data-driven border processes;
- and cross-border interoperability.
APEC: Customs and Businesses Join Forces to Tackle Trade Bottlenecks
Customs is not merely another recipient of the document.
Customs can create authoritative events.
For example:
Declaration received
->
Certificate verified
->
Goods cleared
That event can become part of the asset’s provenance.
Trusted upstream systems can strengthen financeability
Trade finance often begins after commercial documents already exist.
A financier may receive:
- invoice;
- bill of lading;
- certificate;
- purchase order;
- and customs documents.
If those records came from trusted electronic systems, the financier may be able to rely on stronger provenance.
For example:
Purchase order
Source: Buyer procurement system
Bill of lading
Source: Carrier electronic platform
Origin certificate
Source: Authorised issuing body
Customs clearance
Source: Customs system
Invoice
Source: Seller ERP
This is stronger than five PDFs uploaded manually by the borrower.
Paperless trade can reduce duplicate financing
Invoices and trade receivables are vulnerable to duplicate financing.
A seller can present the same economic receivable to multiple financiers.
Electronic-document infrastructure does not automatically eliminate that risk.
But it can make stronger identity possible.
A receivable can be linked to:
- seller;
- buyer;
- invoice;
- purchase order;
- shipment;
- current balance;
- current holder;
- and financing state.
That creates a durable economic object.
If financing infrastructure can query that state, duplication becomes easier to detect.
A document hash is not enough
A cryptographic hash can prove that a digital file has not changed.
It cannot prove:
- that the issuer had authority;
- that the goods shipped;
- that the buyer owes the amount;
- that control was legally transferred;
- that another authoritative record does not exist;
- or that another jurisdiction recognises the document.
Hash integrity is useful.
Legal-state integrity requires more.
Electronic signatures solve only one part
Electronic signatures can help establish:
- signer identity;
- intention;
- document integrity;
- and time.
But a transferable electronic record needs more than a signature.
It can also require:
- uniqueness;
- control;
- transfer;
- current holder state;
- and cancellation or surrender.
A digitally signed PDF bill of lading is not necessarily equivalent to a fully functional electronic bill of lading.
The architecture matters.
The same record may have several identifiers
Cross-border trade can create identifier overload.
A shipment may have:
- purchase-order number;
- invoice number;
- booking number;
- bill-of-lading number;
- container number;
- customs declaration number;
- certificate number;
- bank reference;
- financing reference;
- and platform ID.
The goal should not be to replace all of these with one number.
The goal is to connect them.
An Asset Passport can act as a relationship layer.
A trade-document Asset Passport should preserve authority and state
For DaDepo, the ACCEPT initiative suggests a useful model.
Commercial transaction
- seller;
- buyer;
- contract;
- purchase order;
- goods or services;
- value;
- currency;
- governing law;
- and commercial references.
Shipment
- carrier;
- booking;
- vessel or transport;
- origin;
- destination;
- goods;
- quantity;
- container;
- loading date;
- and delivery state.
Electronic bill of lading
- issuer;
- bill number;
- record identifier;
- current controller;
- transferability;
- control history;
- endorsement or transfer events;
- surrender status;
- replacement status;
- and legal framework.
Certificate of origin
- issuer;
- exporter;
- producer;
- goods;
- origin criteria;
- issue date;
- validity;
- amendment;
- verification state;
- and customs acceptance.
Invoice
- invoice number;
- seller;
- buyer;
- original amount;
- due date;
- credit notes;
- accepted amount;
- current outstanding amount;
- dispute status;
- financing state;
- and settlement state.
Customs bond
- principal;
- surety;
- customs authority;
- bond number;
- amount;
- obligation;
- effective period;
- claim status;
- and release.
Cross-border recognition
- originating jurisdiction;
- receiving jurisdiction;
- applicable legal framework;
- recognised / not recognised / pending;
- platform compatibility;
- signature or identity requirements;
- and evidence of acceptance.
Provenance
- source system;
- issuer;
- authority;
- digital signature;
- timestamp;
- version;
- verification event;
- external registry;
- reviewer;
- and last updated date.
This is much closer to portable trade infrastructure than a document folder.
Legal recognition needs jurisdictional provenance
A field saying:
Legally valid: Yes
is dangerous.
The right answer may be:
Recognised for purpose X
In jurisdiction Y
Under statute Z
As of date T
Cross-border digital trade requires legal conclusions to be scoped.
The same electronic record may be:
- fully recognised in one economy;
- recognised only for evidential purposes in another;
- and not recognised as a transferable record in a third.
That difference should remain visible.
Platform interoperability should not erase legal difference
Technical standards can make systems communicate.
They cannot harmonise law by themselves.
Two economies can exchange the same data format and still disagree about:
- title;
- control;
- signatures;
- negotiability;
- evidential weight;
- customs acceptance;
- or transfer.
That means an interoperability layer should preserve differences rather than hide them.
AI can reconcile documents—but should not create legal control
AI can help trade-document workflows by:
- classifying documents;
- extracting parties;
- matching invoice and purchase-order numbers;
- comparing quantities;
- identifying shipment references;
- detecting credit notes;
- matching certificate information;
- spotting missing documents;
- and identifying inconsistent versions.
Across jurisdictions, AI can also help flag:
- unsupported assumptions about legal recognition;
- different terminology;
- missing signatures;
- expired certificates;
- and discrepancies between customs and commercial records.
That is useful.
AI should not independently determine:
- legal ownership;
- valid transfer of an eBL;
- current legal controller;
- customs acceptance;
- enforceability of a receivable;
- validity of a customs bond;
- or equivalence under a foreign legal system.
Those are legal and institutional decisions.
What DaDepo can contribute
DaDepo does not need to become an eBL platform or customs network.
The opportunity is to preserve the relationship between:
Commercial right
->
Electronic document
->
Authority
->
Current control / ownership state
->
Financing
->
Cross-border recognition
->
Settlement
That is precisely where many private assets become difficult to transfer.
An Asset Passport can help users keep:
- document identity;
- asset identity;
- version;
- provenance;
- transfer history;
- jurisdiction;
- financing state;
- and current status
connected.
External platforms can then perform their specialised roles.
What DaDepo does—and does not do
Creating or reviewing an electronic trade-document Asset Passport does not mean that DaDepo has:
- issued a bill of lading;
- acted as carrier;
- established legal control of an electronic transferable record;
- determined legal equivalence under MLETR;
- authenticated every electronic signature;
- issued or verified a certificate of origin;
- operated customs systems;
- issued a customs bond;
- confirmed goods were shipped or delivered;
- verified invoice enforceability;
- assigned a receivable;
- financed a trade;
- moved settlement money;
- determined cross-border legal recognition;
- or provided legal, customs, shipping, trade-finance, regulatory, tax, accounting, investment or valuation advice.
Important: DaDepo provides technology and information tools. It does not provide legal, customs, shipping, trade-finance, banking, factoring, securities, settlement, regulatory, tax, accounting or valuation advice or services unless a specific service is expressly identified and lawfully provided. Electronic trade documents can have different legal effects depending on document type, governing law, jurisdiction, platform, transaction structure and the legal framework applicable to electronic records and signatures.
A practical cross-border electronic-document checklist
Before an electronic trade document is relied on across borders, ask:
- Document type: Is this an invoice, eBL, certificate, customs bond or another instrument?
- Underlying right: What legal or commercial right does the document evidence or control?
- Issuer: Who created or issued it?
- Authority: What gives the issuer authority?
- Identity: Can the exact electronic record be uniquely identified?
- Integrity: Can changes to the record be detected?
- Version: Which version is current?
- Control: If transferable, who currently controls the record?
- Transfer history: Can every control or ownership transition be reconstructed?
- Uniqueness: Can two parties claim conflicting current control?
- Jurisdiction: Which law governs the electronic record?
- Cross-border recognition: Will the receiving jurisdiction recognise its intended legal effect?
- Platform: Can the receiving system understand the record and its state?
- Signatures: Are electronic signatures or authentication methods accepted?
- Underlying transaction: Is the document linked to the correct shipment, contract or receivable?
- Financing: Has the underlying right already been assigned, pledged or financed?
- Customs: Has the relevant authority accepted or verified required documentation?
- Settlement: Has payment or delivery changed the current state?
- Closure: Has the document been surrendered, cancelled, replaced, expired or otherwise closed?
- Provenance: Can every material field be traced to its issuing system, authority and version?
If the document can cross the border but its legal state cannot, the trade is only partially digital.
The future of paperless trade is portable state
APEC’s ACCEPT initiative matters because it is moving the conversation away from a simple objective:
Remove paper
and toward a more demanding one:
Make electronic trade records work across institutions and jurisdictions
That requires more than digitisation.
It requires:
Identity
+
Authority
+
Integrity
+
Control
+
Recognition
+
Interoperability
+
Lifecycle
+
Provenance
The real asset is not the PDF.
It is the legal and commercial state that the document carries.
Paper trade worked partly because physical originals, signatures, stamps and institutional processes created practical signals of authority.
Digital trade needs equivalent signals that can move at machine speed without losing legal meaning.
That is why cross-border pilots matter.
They test whether the state can travel with the document.
Further reading
- APEC: Paper Trail Holds Back Digital Trade Processes as APEC, ABAC Push Practical Fixes
- APEC: 2026 APEC Ministers Responsible for Trade Joint Statement
- APEC: Customs and Businesses Join Forces to Tackle Trade Bottlenecks
- APEC: 2025 APEC Ministers Responsible for Trade Joint Statement
- UNCITRAL: Model Law on Electronic Transferable Records