Bill of Lading Missing On-Board Notation: The Vessel-Loading Boundary Under UCP 600

Introduction: The Notation That Determines Title

A bill of lading is not a receipt for goods; it is evidence of a contract of carriage and, when made out "to order," a document of title. The single datum that converts a transport receipt into a clean ocean B/L is the on-board notation — the carrier's explicit statement that the goods were loaded on the named vessel on a stated date. When that notation is absent, the examining bank treats the document as a received-for-shipment B/L and applies UCP 600 Article 20 strictly. The failure mode is not ambiguity in the data; it is the binary absence of a loading statement where the credit demands an on-board B/L.

Failure Mode Analysis

Failure Mode 1: Pre-Printed "Shipped on Board" Absent on a Received-for-Shipment Form

Forwarders routinely issue received-for-shipment B/Ls because the vessel is not yet loaded at document issuance. The exporter presents this form without obtaining the carrier's on-board stamp. At examination, the bank finds no loading statement and transmits a discrepancy notice. The failure was pre-compiled at the freight-forwarder layer, before the document reached the bank.

Failure Mode 2: On-Board Notation Missing Vessel Identity

A carrier stamps "on board" with a date but omits the vessel name. Article 20(a)(ii) requires the notation to identify the vessel. The examining bank treats the partial notation as non-compliant. The exporter assumed a date alone satisfied the condition — it does not.

Failure Mode 3: Notation Date Exceeds the Latest Shipment Date

The on-board date becomes the de facto shipment date. If that date falls after the latest shipment date in field 44C, the presentation violates the credit regardless of the notation's presence. The authentication correction competes with the shipment deadline — and the deadline wins under Article 14.

Deterministic Resolution Architecture

1. Compile the B/L type before presentation. Parse field 46A for whether an on-board B/L or received-for-shipment B/L is required. The credit's text is the only binding specification.
2. Isolate the notation at the compilation layer. Flag any B/L lacking a vessel-named on-board stamp where the credit demands on-board. This flag is a pre-compiled failure mode that downstream verification cannot repair.
3. Decouple notation date from the shipment deadline. Obtain the on-board stamp before the presenting bank receives the set. A post-presentation correction races a clock it cannot win.
4. Verify vessel identity in the notation. The stamp must name the vessel exactly as in field 47A/44E. A missing or mismatched vessel is a boundary violation.

Conclusion

The missing on-board notation is an authentication boundary problem, not a data problem. UCP 600 Article 20 grants acceptance only when the loading statement is explicit and vessel-identified. The moment the credit demands on-board, flexibility collapses to a binary condition. Pre-compile the requirement, isolate the notation gap, and decouple timing — the only regime under which Article 20 functions as designed.

FAQ

Q1: Is a received-for-shipment B/L always discrepant?
No. It is acceptable when the credit permits it or when an on-board notation is added that names the vessel and date. Without that notation where on-board is required, it is discrepant.

Q2: Can the applicant waive the missing notation after a discrepancy notice?
The applicant may accept discrepant documents under Article 16, but that is a post-discrepancy remedy. The cost — delayed payment, impaired trust — is already incurred.

Q3: Does the on-board date control the shipment date?
When no separate shipment date is evidenced, the on-board notation date is the date of shipment. If it exceeds the latest shipment date, the presentation violates the credit.

Q4: What if the vessel name in the notation differs slightly from field 44E?
ISBP 745 requires consistency. A mismatched vessel identity is a data-consistency discrepancy independent of the notation's presence.