The digital documents pilot for imports: aims, scope and principles

I-1 introduces a pilot framework for the digital processing of trade documents. Let's take it piece by piece.

• What it covers: both export and import transactions under documentary collections and LCs.
• How: through approved trade corridors. A corridor is a route between two countries or regions that has been approved for the pilot. I-4 explains how a corridor gets started.
• Why: to take digitalisation in cross-border trade further, and to make trade finance work with more efficiency (faster, less waste), transparency (easier to see what happened) and resilience (able to keep going when something goes wrong).

I-1 also says what kind of electronic documents the framework aims to support. They should be:

• interoperable, meaning they work across different systems;
• secure; and
• legally reliable.

These include Electronic Transferable Records (ETRs), the electronic versions of documents such as bills of lading and bills of exchange. And all of it should stay in line with evolving international standards.

Note the word pilot: a trial on a controlled scale before wider use. Shabnam compares it to a new flyover. "They open one lane first, watch the traffic, and only then open the rest."

I-1 speaks of both exports and imports. The export room teaches a matching pilot from the exporter's side (Part F there); this room follows the import text.

I-2 sets the scope: which import deals these instructions apply to. There are three groups.

(a) Import collections. Import transactions under documentary collections, on either DP (Documents against Payment) or DA (Documents against Acceptance) terms, governed by the latest URC and the eURC Supplement.

(b) Import LCs. Import transactions under documentary credits, governed by the UCP in force and the applicable electronic presentation rules, that is, eUCP, where applicable.

(c) Related trade financing. Trade financing activities that involve electronic trade documents and sit within approved pilot arrangements.

So the import deals in (a) and (b) stand on a familiar rule book. Collections stand on URC, with its electronic add-on, eURC. LCs stand on UCP, with its electronic add-on, eUCP, where it applies.

Shabnam puts it in everyday terms: "It's the same wedding. The invitation has simply gone digital, so there's one extra page explaining how to RSVP online."

Notice the two conditions in (c): the financing must involve electronic trade documents, and it must be within approved pilot arrangements. The circular doesn't list which kinds of trade financing count under (c).

I-3 sets five core principles. All participants under the framework must follow them.

(a) Interoperability. Electronic trade documents must be capable of being issued, transmitted, received and verified across different systems, without depending on any single platform. Think of a mobile number you can call from any operator. Nobody wants an invoice that opens only on one company's software.

(b) Technology neutrality. No specific technology, platform or vendor is made compulsory, provided minimum security and functional standards are met. The bar is set; each bank chooses how to clear it.

(c) Decentralised verification. Anyone relying on a document must be able to check that it is authentic (genuine) and where it came from (its provenance), independently of the system that issued or sent it. This is done with cryptographic or equivalent mechanisms. It is like checking the security thread on a banknote yourself, instead of phoning the people who printed it.

(d) Data privacy by design. Sensitive trade data stays under the control of the document owner. It shall not be mandatorily stored in centralised or shared systems. Privacy is built in from the start, not added later.

(e) Legal functional equivalence. Electronic trade documents, including ETRs, are treated as functionally equivalent to paper documents, meaning they do the same job, where they meet the applicable legal and operational requirements. The condition matters: an e-document earns paper's standing by meeting those requirements, not simply by existing.

Shabnam sums it up: "Works everywhere, favours no vendor, anyone can check it, the owner keeps the data, and a good e-document counts like paper." So, Lamia: yes, a file can stand like an original, if it meets the requirements.

How does a bank start a pilot corridor? I-4 sets out four points.

(a) Ask first. An AD must approach Bangladesh Bank for concurrence in principle, that is, agreement in principle, to take part in the pilot framework and use digital trade document processing arrangements.

(b) Say what you plan. The request must specify:

• (i) the proposed trade corridor(s), given as a country/region pair;
• (ii) the counterparty banks and institutions;
• (iii) the type of transactions: LC, collection, or mixed;
• (iv) the technology approach and its interoperability features; and
• (v) the risk management and compliance arrangements.

(c) Approval comes with conditions. Bangladesh Bank grants approval subject to readiness, safeguards, and compliance with this framework.

(d) Why corridors at all? Trade corridors are identified to enable a pilot that is controlled, legally aligned and operationally testable in cross-border settings.

That last point is the heart of the idea. Shabnam explains: "When the route, the partners and the rules are known in advance, everyone knows which law and which contract apply. If something goes wrong, you know exactly where to look."

Notice how item (iv) links back to I-3: the request must show the interoperability that the principles call for. Notice too that it is the AD, not the importer, who approaches Bangladesh Bank. The circular doesn't give a form, a format or a time limit for the request, or for Bangladesh Bank's reply.

I-5 lays the legal and contractual base for e-documents in the pilot. This is Shabnam's home ground. It has four parts.

(a) Write it down. Sales contracts, LCs and collection instructions must explicitly provide for the electronic issuance, transmission and acceptance of trade documents. "Explicitly" means in clear words. Silence, or a vague hint, is not enough.

(b) Agree what e-documents count for. The parties must agree that electronic documents are:

• (i) operationally valid and binding; and
• (ii) acceptable for settlement, acceptance and delivery purposes within the pilot framework.

In plain words, everyone agrees in advance that an e-document counts: for paying, for accepting a bill, and for handing over the goods.

(c) Choose the rule books. The applicable rules, URC 522, UCP 600, eURC and eUCP, govern the transactions to the extent mutually agreed among the parties. So the parties decide together which rules apply, and how far.

(d) Look to international standards for ETRs. ADs must ensure that ETRs comply, to the extent practicable, with principles consistent with internationally recognised legal frameworks for electronic transferable records. "To the extent practicable" means as far as can reasonably be done. The circular doesn't name any particular framework.

Shabnam puts it simply: "A contract is a promise both sides wrote down. If the e-document isn't in the promise, someone can later say, 'I never agreed to a file.'"

For Lamia, that means her sales contract with the supplier, the LC her bank opens and any collection instruction must all say it clearly.