ISBP 745

ISBP 745 §N: Weight List Compliance Architecture Under Documentary Credits

📅 2026-07-20 5 min read UCP 600 / ISBP 745

Introduction

The illusion that a weight list is a mere logistical byproduct of the shipping process systematically mutates into a binary failure mode at the examination stage. Practitioners often treat weight data as incidental, failing to isolate the specific compliance requirements of ISBP 745 §N and the non-conflict principles of UCP 600 Article 14(d). This perception leads to discrepancies where data conflicts between the weight list and other stipulated documents—specifically the commercial invoice or bill of lading—violate the deterministic examination standards, decoupling the beneficiary from payment and truncating the transaction’s compliance architecture.

This guide compiles the operative rules, isolates the failure modes, and provides a deterministic resolution architecture for weight list compliance.

Failure Mode Analysis

1. The "Data Conflict" Violation

Failure Mode: The total weight shown on the weight list conflicts with the total weight on the commercial invoice or bill of lading.

Mechanism: Under §N6, banks examine totals to ensure no conflict exists. A weight list showing "1,000 MT" while the invoice states "998 MT" is a discrepancy, even if the credit allows for a tolerance, because the documents themselves violate the non-conflict rule of 14(d). The tolerance in the credit applies to the transaction, not to internal document inconsistencies.

2. The "Issuer Identity" Violation

Failure Mode: The weight list is issued by the beneficiary despite the credit requiring issuance by an "independent surveyor," "SGS," or another named entity.

Mechanism: Violation of §N2 occurs when practitioners assume any certificate issued by a third party suffices. If the credit names a specific issuer (e.g., "issued by an independent surveyor"), only that entity's certificate complies. A weight list issued by the beneficiary in this context is a binary failure.

3. The "Non-Beneficiary Issuer" Misinterpretation

Failure Mode: Presenting a weight list with a different invoice number or routing than other documents, when the weight list was issued by the beneficiary.

Mechanism: Practitioners often misinterpret §N5, believing that any weight list can show different invoice data. In reality, §N5 is a conditional permission: it only applies when the issuer is not the beneficiary. If the beneficiary issues the weight list, it must align with the other documents to avoid a conflict under 14(d).

Deterministic Resolution Architecture

To eliminate these failure modes, follow this numbered architecture:

  1. Isolate the Issuer Requirement (§N2/N3). Verify if the credit specifies an issuer. If not, identify that any entity—including the beneficiary—may issue the list.
  2. Truncate Extraneous Data (§N4). Ensure the weight list contains only weight data or data that does not conflict with the credit’s specific weight requirements.
  3. Compile the Total Value Cross-Check (§N6). Compare the total weight, quantity, and measurement on the weight list against the commercial invoice, bill of lading, and packing list. Ensure all figures are consistent.
  4. Verify Non-Beneficiary Status for Flexible Data (§N5). If the weight list shows a different invoice number or routing than other documents, confirm the issuer is not the beneficiary. If the beneficiary is the issuer, the data must align.
  5. Sign and Date the Document. Ensure the document is signed and, if required by the credit or the nature of the document, dated to satisfy the general principles of ISBP 745 §A4 and §A11.

Conclusion

The weight list is a deterministic compliance artifact. By isolating the issuer requirements of §N2/N3 and truncating potential data conflicts through cross-referencing totals under §N6, practitioners eliminate the systemic failure modes that lead to refusal. Weight list compliance is not a matter of logistical convenience but of strict adherence to the non-conflict principle and the functional fulfillment rule.

FAQ

Q1: If a credit requires a "Weight Note" but does not specify who issues it, can the beneficiary issue it?
A: Yes. Under ISBP 745 §N3, when a credit does not indicate the name of an issuer, any entity—including the beneficiary—may issue the weight list.

Q2: Can a weight list be untitled?
A: Yes. ISBP 745 §N1 states that a weight list is satisfied by a document titled as called for, bearing a similar title, or being untitled, provided it fulfils its function by containing weight information.

Q3: If the weight list shows a different invoice number than the commercial invoice, is it discrepant?
A: It depends on the issuer. Under ISBP 745 §N5, a weight list may indicate a different invoice number, provided the issuer is not the beneficiary. If the beneficiary issues the weight list, it must align with the other documents to avoid a conflict under UCP 600 Article 14(d).

Q4: How does a bank examine the weight list if the credit specifies a tolerance for weight?
A: The bank examines the weight list on its face against the credit and other documents. While the credit may allow a tolerance (e.g., +/- 5%), the weight list itself must not conflict with the totals shown on other stipulated documents (§N6). Internal document inconsistency is a discrepancy regardless of the credit's tolerance.

Q5: Does a weight list need to be signed?
A: Under ISBP 745 §A3, when a certificate, certification, declaration, or statement is required by a credit, it is to be signed. While a "weight list" is not explicitly called a "certificate," it functions as a declaration of weight and should be signed to satisfy general practice and avoid discrepancies.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 5 completed

Get the Full LC Compliance Checklist

15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.

No spam. Unsubscribe anytime.

DraftLC Compliance Engine

DraftLC generates compliant ISBP 745 §N — so you never face this failure mode.

DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.

No credit card required · See how DraftLC drafts compliant credits