eUCP Version 2.1 Articles Explanation

eUCP Version 2.1 Article e14: Force Majeure Clauses Explained – CDCS Guide

by

Article e14: Force Majeure

“A bank assumes no liability or responsibility for the consequences arising out of the interruption of its business, including but not limited to its inability to access a data processing system, or a failure of equipment, software or communications network, caused by Acts of God, riots, civil commotions, insurrections, wars, acts of terrorism, cyberattacks, or by any strikes or lockouts or any other causes, including failure of equipment, software or communications networks, beyond its control.”

Explanation and Examples

1. “A bank assumes no liability or responsibility for the consequences arising out of the interruption of its business”

  • Explanation: This clause means that if a bank’s operations are disrupted, it will not be held responsible for any negative outcomes that result from such interruptions. This protection is crucial for banks, as their operations are highly sensitive to disruptions.
  • Example: Suppose a bank is unable to process transactions due to an unexpected power outage. According to this clause, the bank would not be liable for any issues that arise from the inability to complete transactions during the outage.

2. “Including but not limited to its inability to access a data processing system”

  • Explanation: This phrase extends the bank’s liability protection to situations where it cannot access its data systems, which are critical for its operations.
  • Example: If a bank’s data processing system is offline due to a cyberattack, and the bank is unable to provide services such as account management or fund transfers, the bank will not be liable for the resulting inconveniences or losses.

3. “Or a failure of equipment, software or communications network”

  • Explanation: This clause covers any failures in the bank’s equipment, software, or communications infrastructure, which could impact its ability to perform its functions.
  • Example: If a bank’s server crashes, preventing customers from accessing their accounts online, the bank is not responsible for any issues or losses that occur as a result of this failure.

4. “Caused by Acts of God”

  • Explanation: Acts of God refer to natural events that are beyond human control, such as natural disasters. The bank is not liable for disruptions caused by these events.
  • Example: During a major earthquake, if a bank’s operations are disrupted due to damage to its facilities, it will not be held liable for any inconvenience or losses experienced by customers.

5. “Riots, civil commotions, insurrections, wars, acts of terrorism”

  • Explanation: This clause includes various forms of social and political unrest that could disrupt banking operations. The bank is not responsible for issues arising from these events.
  • Example: If a bank’s services are interrupted due to a war or a riot near its branch, it will not be liable for any delays or losses that customers might face as a result.

6. “Cyberattacks”

  • Explanation: This covers attacks on the bank’s digital systems, such as hacking or malware, which can disrupt services. The bank will not be held liable for issues resulting from these attacks.
  • Example: If a bank’s systems are compromised due to a cyberattack, causing a temporary loss of online banking services, the bank is not responsible for any resulting financial losses or service disruptions.

7. “Or by any strikes or lockouts”

  • Explanation: This part addresses labor disputes that could affect the bank’s operations. If a strike or lockout impacts the bank, it will not be liable for the consequences.
  • Example: If bank employees go on strike and the bank cannot process transactions or provide customer service, the bank will not be held liable for any disruptions or financial losses incurred by customers.

8. “Or any other causes, including failure of equipment, software or communications networks, beyond its control”

  • Explanation: This clause is a catch-all for any other unforeseen or uncontrollable events that disrupt the bank’s operations, not explicitly listed in the previous clauses.
  • Example: If a sudden and severe network outage prevents the bank from processing transactions, and this issue is beyond the bank’s control, the bank will not be responsible for any problems resulting from this outage.

eUCP Version 2.1 Article e13: Additional Disclaimer of Liability for Electronic Records – CDCS Guide

by

Article e13: Additional Disclaimer of Liability for Presentation of Electronic Records under eUCP

a. By satisfying itself as to the apparent authenticity of an electronic record, a bank assumes no liability for the identity of the sender, source of the information, or its complete and unaltered character other than that which is apparent in the electronic record received by the use of a data processing system for the receipt, authentication, and identification of electronic records.

Explanation: This clause outlines that a bank is responsible for verifying the apparent authenticity of an electronic record it receives. However, the bank’s responsibility does not extend beyond the visible aspects of the record. In other words, the bank does not need to verify the identity of the sender, the origin of the information, or ensure that the electronic record has not been altered beyond what is apparent in the record itself. The bank’s responsibility is limited to what it can see and verify using its data processing systems.

Example: Suppose a bank receives an electronic invoice from a supplier. The bank checks the invoice’s authenticity based on its content and the sender’s details visible in the record. However, the bank does not investigate the actual identity of the person who sent the invoice or verify if the invoice was altered before reaching them. As long as the invoice appears authentic within their data processing system, the bank accepts it at face value and assumes no further liability regarding the sender’s identity or the record’s integrity.

b. A bank assumes no liability or responsibility for the consequences arising out of the unavailability of a data processing system other than its own.

Explanation: This clause states that a bank is not liable for issues or consequences that arise from the unavailability or malfunction of data processing systems that are not under its control. In essence, the bank is only responsible for its own systems and cannot be held accountable for problems caused by systems operated by other entities.

Example: Imagine a situation where a bank is supposed to process an electronic record from a transaction partner. If the transaction partner’s data processing system is down and the record cannot be transmitted or processed as expected, the bank is not responsible for this issue. The bank’s liability is confined to its own systems and operations. If the bank’s system is functioning properly, it cannot be held accountable for failures or issues that occur because of the partner’s system being unavailable.

eUCP Version 2.1 Article e12: Handling Data Corruption of Electronic Records – CDCS Guide

by

Article e12: Data Corruption of an Electronic Record

a. “If an electronic record that has been received by a nominated bank acting on its nomination or not, confirming bank, if any, or the issuing bank, appears to have been affected by a data corruption, the bank may inform the presenter and may request it to be re-presented.”

Explanation: This clause addresses the scenario where an electronic record, such as a digital document related to a letter of credit, becomes corrupted or otherwise compromised during its transmission or receipt. If the nominated bank, confirming bank, or issuing bank detects such data corruption, they have the right to notify the party who presented the record. The bank can then request that the presenter provide a new, uncorrupted version of the electronic record.

Example: Imagine a nominated bank receives an electronic bill of lading from the presenter, but upon review, it is found that some data is garbled due to a transmission error. The bank can notify the presenter of this issue and ask for a fresh copy of the electronic bill of lading to be sent. This ensures that the bank can process the document correctly and without errors.

b. If a bank makes such a request:

i. “the time for examination is suspended and resumes when the electronic record is re-presented;”

Explanation: When a bank requests a re-presentation of an electronic record due to data corruption, the period allocated for examining the document is temporarily halted. This means the bank does not count the time spent waiting for the re-presented record against the presentation deadline. The examination time clock only resumes once the corrected document is received.

Example: Suppose the original electronic record was supposed to be examined within 10 days. If the bank requests a re-presentation on the 5th day due to data corruption, the remaining 5 days for examination will pause until the new record is received. If the new record arrives after 3 days, the bank then has 5 days from the receipt of the new document to complete its examination.

ii. “if the nominated bank is not a confirming bank, it must provide any confirming bank and the issuing bank with notice of the request for the electronic record to be re-presented and inform it of the suspension;”

Explanation: If the nominated bank is not acting as a confirming bank, it is responsible for informing both any confirming bank involved and the issuing bank about the request for re-presentation and the suspension of the examination period. This ensures all relevant parties are aware of the situation and any changes to the timeline.

Example: If a nominated bank discovers data corruption and requests a re-presentation of the document, and it is not a confirming bank, it must notify the confirming bank and the issuing bank about the corruption issue and the resulting pause in the examination period. This keeps everyone in the loop and avoids confusion or delays.

iii. “if the same electronic record is not re-presented within 30 calendar days, or on or before the expiry date and/or last day for presentation, whichever occurs first, the bank may treat the electronic record as not presented.”

Explanation: Should the presenter fail to provide the corrected electronic record within 30 calendar days or before the expiration of the presentation deadline (whichever is sooner), the bank has the right to consider the electronic record as not having been presented. This means that the record would be treated as though it was never submitted, potentially affecting the processing of the related transaction.

Example: If the presentation deadline for a document is 15 days, but the presenter fails to send the corrected electronic record within this period or within 30 days of the original request, the bank can disregard the document as though it was never received. This ensures that the transaction remains on schedule and maintains the integrity of the process.

eUCP Version 2.1 Article e11: Transport – Explanation and Examples – CDCS Guide

by

Article e11: Transport

Clause: “If an electronic record evidencing transport does not indicate a date of shipment or dispatch or taking in charge or a date the goods were accepted for carriage, the date of issuance of the electronic record will be deemed to be the date of shipment or dispatch or taking in charge or the date the goods were accepted for carriage.”

Explanation: This clause addresses situations where an electronic transport record lacks specific dates for shipment, dispatch, or taking in charge of goods. In such cases, the date when the electronic record itself is issued is used as a substitute for these dates. Essentially, if no other date is mentioned, the issue date of the document is considered the relevant date for transport.

Example: Imagine a shipment of goods where the electronic transport document does not specify when the goods were dispatched. If the document was issued on August 10, 2024, then for all purposes of the transaction, August 10, 2024, will be considered the date of dispatch.

Clause: “However, if the electronic record bears a notation that evidences the date of shipment or dispatch or taking in charge or the date the goods were accepted for carriage, the date of the notation will be deemed to be the date of shipment or dispatch or taking in charge or the date the goods were accepted for carriage.”

Explanation: This clause allows for an exception to the general rule. If the electronic record contains a specific notation that clearly states the date of shipment, dispatch, or taking in charge, then this noted date overrides the issue date of the document. The noted date is then used for all purposes related to transport dates.

Example: Suppose the electronic transport record includes a notation stating “Goods dispatched on August 15, 2024.” Even if the record was issued on August 10, 2024, the date August 15, 2024, as noted on the document, will be used to determine the actual date of dispatch.

Clause: “Such a notation showing additional data content need not be separately signed or otherwise authenticated.”

Explanation: Notations providing additional information, such as dates of shipment or dispatch, do not require separate signatures or authentication to be valid. This clause ensures that the presence of a date notation is sufficient without needing additional verification.

Example: If an electronic transport record has a note indicating “Goods accepted for carriage on August 20, 2024,” this date does not need to be signed or otherwise authenticated separately. The notation itself is sufficient to establish the date of acceptance for carriage.

eUCP Version 2.1: Articles e9 and e10 Explained – CDCS Guide

by

Article e9: Originals and Copies

Clause: “Any requirement for presentation of one or more originals or copies of an electronic record is satisfied by the presentation of one electronic record.”

Explanation: Article e9 addresses the handling of electronic records in trade transactions. Traditionally, physical documents such as bills of lading, certificates of origin, or invoices had to be presented in multiple originals or copies. In the electronic format, however, this requirement is streamlined. According to this article, the presentation of a single electronic record fulfills any requirement that would traditionally call for multiple originals or copies.

Example: Imagine a company is shipping goods and needs to present a bill of lading. Under traditional rules, they might have to submit several copies of the bill of lading to different parties involved (e.g., the bank, the consignee, and the customs authorities). With eUCP Article e9, presenting one electronic version of the bill of lading satisfies all these requirements. The electronic document is considered an official and sufficient representation, eliminating the need for multiple physical copies.

Article e10: Date of Issuance

Clause: “An electronic record must provide evidence of its date of issuance.”

Explanation: Article e10 focuses on ensuring that electronic records include clear evidence of when they were issued. This is crucial in trade finance because the timing of documents can impact the validity and execution of transactions. The date of issuance helps in establishing the timeline of the transaction and ensuring that all parties have access to this crucial piece of information.

Example: Consider a situation where a company receives an electronic invoice for payment. According to Article e10, the electronic invoice must contain a date that clearly indicates when it was issued. This allows the payer to verify the timing of the invoice and ensures that any payment terms related to the issuance date are accurately followed. If the invoice is issued on August 1, 2024, the electronic record will include this date, confirming that the invoice was created and sent on that specific day.

eUCP Version 2.1 Article e8: Notice of Refusal Explained – CDCS Guide

by

Article e8: Notice of Refusal

“If a nominated bank acting on its nomination, a confirming bank, if any, or the issuing bank, provides a notice of refusal of a presentation which includes electronic records and does not receive instructions from the party to which notice of refusal is given for the disposition of the electronic records within 30 calendar days from the date the notice of refusal is given, the bank shall return any paper documents not previously returned to that party, but may dispose of the electronic records in any manner deemed appropriate without any responsibility.”

Explanation and Example

Clause: “If a nominated bank acting on its nomination, a confirming bank, if any, or the issuing bank, provides a notice of refusal of a presentation which includes electronic records”

Explanation: This clause refers to a situation where a bank involved in the letter of credit process (either a nominated bank, a confirming bank, or the issuing bank) issues a notice of refusal. This refusal pertains to a presentation made under the letter of credit that includes electronic records.

Example: Imagine a scenario where a nominated bank receives a presentation from the beneficiary, which includes both electronic records and paper documents. If the bank finds issues with the presentation and decides to refuse it, it must notify the beneficiary of this refusal.

Clause: “and does not receive instructions from the party to which notice of refusal is given for the disposition of the electronic records within 30 calendar days from the date the notice of refusal is given”

Explanation: Once the bank has issued the notice of refusal, it waits for instructions from the party (usually the beneficiary or the presenting party) on how to handle the electronic records. If no instructions are provided within 30 calendar days from the date of the notice, the bank will proceed according to the article’s provisions.

Example: The nominated bank sends a notice of refusal to the beneficiary on January 1st. If the beneficiary does not respond with instructions on how to handle the electronic records by January 31st, the bank will take action as described in the next part of the article.

Clause: “the bank shall return any paper documents not previously returned to that party”

Explanation: The bank is required to return any physical paper documents that were part of the presentation and have not yet been returned to the presenting party. This ensures that the presenting party receives all physical documents related to the refused presentation.

Example: If the presentation included a shipment invoice and a bill of lading, and these paper documents were not yet returned to the beneficiary after the refusal, the bank must send them back once the 30-day period has elapsed.

Clause: “but may dispose of the electronic records in any manner deemed appropriate without any responsibility”

Explanation: For the electronic records, if the presenting party does not provide instructions within the 30-day period, the bank is free to handle the electronic records as it sees fit. The bank does not bear any responsibility for how these records are disposed of.

Example: Suppose the bank receives no instructions from the beneficiary on what to do with the electronic records after 30 days. The bank might choose to delete or archive these records according to its policies. The bank is not held liable for any consequences arising from its disposal of the electronic records.