UCP 600

Best Practices for UCP 600 Article 23 Air Transport Document Compliance

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

Introduction

Air transport documents under UCP 600 Article 23 present a distinct compliance challenge. Unlike maritime bills of lading, air waybills are not documents of title — they are receipts for carriage that evidence a contract of carriage governed by the Montreal Convention (1999). This fundamental difference means exporters cannot apply the same procedures they use for ocean freight. Article 23 demands specific data elements, particular authentication methods, and a compliance architecture that accounts for air-specific operational realities.

This guide provides a systematic compliance framework for Article 23, maps every requirement to concrete verification steps, and identifies the failure modes that generate discrepancies in practice.

Failure Mode Analysis

Failure Mode 1: Air Waybill Missing "Accepted for Carriage" Notation

The air waybill states "received for shipment" but lacks the "accepted for carriage" notation. Article 23(b) requires the document to indicate goods have been accepted for carriage. "Received for shipment" does not satisfy this requirement. The notation must confirm the carrier has accepted the goods for carriage on a specific flight.

Failure Mode 2: Airport Names Do Not Match the Credit

The air waybill shows "PVG" (Shanghai Pudong) but the credit states "Shanghai." Article 23(c) requires airports of departure and destination as stated in the credit. IATA codes may differ from the credit's city names. The exporter must confirm the credit accepts IATA codes or use full city names.

Failure Mode 3: Flight Number and Date Missing

The air waybill does not show the flight number or the date of acceptance for carriage. Article 23(f) requires both. Without a flight number, the bank cannot verify the routing. Without a date, the bank cannot confirm the shipment date.

Failure Mode 4: Air Waybill Number Format Non-Standard

The air waybill number does not follow the standard 13-digit format (3-digit airline code + 10-digit serial number). While UCP 600 does not mandate a specific format, non-standard numbers may indicate a non-standard document that raises authenticity concerns.

Failure Mode 5: Dangerous Goods Declaration Omitted for Hazardous Cargo

The air waybill covers hazardous cargo but does not include a dangerous goods declaration under IATA Dangerous Goods Regulations (DGR). While UCP 600 does not specifically require this, the absence creates a compliance gap that extends beyond UCP 600 to regulatory requirements.

Deterministic Resolution Architecture

  1. Verify Montreal Convention compliance. Confirm the air waybill contains the data elements required by the Montreal Convention: carrier name, place of departure and destination, weight, and package count.
  2. Check AWB number format. Verify the air waybill number follows the standard 13-digit format. Non-standard formats may indicate a non-standard document.
  3. Verify "accepted for carriage" notation. Locate the acceptance notation and confirm it is dated per Article 23(b). The date must not exceed the latest shipment date.
  4. Match airport names. Compare the airport of departure and destination against the credit. Confirm exact matches — IATA codes or full city names as the credit requires.
  5. Verify chargeable weight. Confirm the air waybill shows the chargeable weight (higher of actual or volumetric weight). Cross-reference with the commercial invoice and packing list.
  6. Check dangerous goods declaration. If the goods are hazardous, verify the dangerous goods declaration is present and complete under IATA DGR.
  7. Examine all originals. Confirm all originals are presented per Article 23(d).
  8. Verify flight number and date. Confirm the flight number and date of acceptance for carriage appear on the document per Article 23(f).
  9. Cross-reference with other documents. Compare the goods description, quantity, and value against the commercial invoice and packing list per Article 14(d).

Conclusion

Article 23 compliance requires air-specific knowledge that differs fundamentally from maritime document examination. The "accepted for carriage" notation, IATA airport codes, flight number requirements, and Montreal Convention data elements create a compliance architecture unique to air transport. Exporters who apply maritime procedures to air waybills encounter discrepancies that are predictable and preventable with the right framework.

Frequently Asked Questions

Q1: Is an air waybill a document of title?
No. Under the Montreal Convention (Article 8), an air waybill is not a document of title. This differs from maritime bills of lading, which can function as documents of title. The air waybill is a receipt for carriage and evidence of the contract of carriage.

Q2: Can a credit require both an air waybill and a bill of lading?
Yes. A credit may require both documents for different legs of the journey. Each is examined under its applicable article: the air waybill under Article 23, the bill of lading under Article 20.

Q3: What does "accepted for carriage" mean?
"Accepted for carriage" means the carrier has accepted the goods for transport on a specific flight. It is the air transport equivalent of "on board" notation. The date of acceptance is the shipment date.

Q4: How does transshipment work under Article 23?
Article 23 does not prohibit transshipment. ISBP 745 Paragraph E28 states transshipment is permitted unless the credit expressly prohibits it. The air waybill may show multiple routing points.

Q5: What ISBP 745 paragraphs apply to Article 23?
Paragraphs E26 (document type determination), E27 ("accepted for carriage" equivalence), E28 (transshipment), and E29 (issuance date as shipment date) all apply to Article 23 examination.

Source Notes

Did You Know?

Article 23(b) requires the document to indicate goods have been accepted for carriage.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 23Air Transport DocumentBinary determination (compliant/discrepant)
UCP 600Article 5Documents v. Goods/Services/PerformanceBinary determination (compliant/discrepant)
UCP 600Article 8Confirming Bank UndertakingBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 20Bill of LadingBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 7 completed
Bank Expectations vs Common Beneficiary Mistakes
✓ What Banks Expect✗ What Beneficiaries Often Do Wrong
Air Waybill Missing "Accepted for Carriage" NotationThe air waybill states "received for shipment" but lacks the "accepted for carriage" notation. Ar...
Airport Names Do Not Match the CreditThe air waybill shows "PVG" (Shanghai Pudong) but the credit states "Shanghai." Article 23(c) req...
Flight Number and Date MissingThe air waybill does not show the flight number or the date of acceptance for carriage. Article 2...
Air Waybill Number Format Non-StandardThe air waybill number does not follow the standard 13-digit format (3-digit airline code + 10-di...
Dangerous Goods Declaration Omitted for Hazardous CargoThe air waybill covers hazardous cargo but does not include a dangerous goods declaration under I...

← Scroll horizontally to see all columns

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 Best Practices for UCP 600 Article 23 Air Transport Document Compliance — 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