Inspection Certificate Date After Shipment: The Temporal Boundary Under UCP 600
Introduction: The Certificate That Arrives Too Late
An inspection certificate attests that goods were examined and found conforming before shipment. When the certificate's date falls after the actual shipment date (or after the on-board notation), the examining bank applies a binary determination under UCP 600 Article 14 and ISBP 745. The error is not a factual dispute about quality; it is a temporal inversion — the document claims inspection occurred after the goods were already loaded. The bank does not negotiate the inspector's sequence; it compares dates and rejects the inversion.
Failure Mode Analysis
Failure Mode 1: Plain Certificate Misread as Pre-Shipment
A credit requires an "inspection certificate" (no pre-shipment qualifier). The exporter dates it after shipment. Under A12(c) this is compliant — yet a presenter unfamiliar with A12 fears rejection and re-issues unnecessarily, delaying the drawing. The failure is a false-positive rework, not a discrepancy.
Failure Mode 2: Pre-Shipment Cert Lacks Evidencing
A credit requires a "pre-shipment inspection certificate." The issued certificate is titled merely "Inspection Certificate" and dated after shipment, with no content indicating pre-shipment occurrence. Under A12(b) the bank isolates the missing pre-shipment evidence and rejects. The failure was pre-compiled at the inspection-drafting layer.
Failure Mode 3: Title/Content Drift on a Pre-Shipment Requirement
The certificate is dated before shipment but titled generically, with content that does not reference inspection prior to loading. The bank, unable to confirm the pre-shipment event from title or content, treats the requirement as unmet under A12(b). The date alone does not rescue a mis-titled document.
Deterministic Resolution Architecture
- Compile the inspection wording before presentation. Parse field 46A for whether the credit requires a plain "inspection certificate" or a pre-shipment inspection certificate. The credit's text is the only binding specification.
- Isolate the pre-shipment qualifier at the compilation layer. If pre-shipment is required, flag any certificate that does not evidence it by title, content, or pre-shipment date. This flag is a pre-compiled failure mode that downstream verification cannot repair.
- Decouple certificate issuance from shipment timing. For a pre-shipment requirement, obtain a certificate whose title/content/date evidences pre-shipment before loading. A post-shipment correction races a deadline it cannot win.
- Do not over-correct plain certificates. A plain inspection certificate may be dated after shipment under A12(c); re-issuing it wastes the presentation window.
Conclusion
The inspection-certificate date question is a wording boundary problem, not a calendar problem. UCP 600 and ISBP 745 grant tolerance for a plain certificate dated after shipment (A12(c)) but demand pre-shipment evidence where the credit requires it (A12(b)). The moment the credit says "pre-shipment," compliance becomes a binary condition. Pre-compile the wording, isolate the evidence gap, and decouple timing — the only regime under which A12 functions as designed.
FAQ
Q1: Is an inspection certificate dated after shipment always discrepant?
No. Under ISBP 745 A12(c), a credit requiring merely an "inspection certificate" does not require a pre-shipment date; a later issuance date is compliant.
Q2: When is a post-shipment inspection date discrepant?
Only when the credit requires a document evidencing a pre-shipment event (e.g., "pre-shipment inspection certificate") and the certificate fails to evidence it by title, content, or date, per A12(b).
Q3: Can the applicant waive the missing pre-shipment evidence after a discrepancy notice?
The applicant may accept under Article 16, but that is a post-discrepancy remedy. The cost — delayed payment, impaired trust — is already incurred.
Q4: What if the credit does not require pre-shipment inspection?
Then A12(c) applies: a plain inspection certificate may be dated after shipment and is compliant. The certificate must still not conflict with other documents' dates under Article 14(d), but no pre-shipment evidence is required.
Article 14(g) requires documents to be presented within the period after shipment specified in the credit, and in any event not later than the expiry date.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 14 | Standard for Examination of Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 16 | Discrepant Documents, Waiver and Notice | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Plain Certificate Misread as Pre-Shipment | A credit requires an "inspection certificate" (no pre-shipment qualifier). The exporter dates it ... |
| Pre-Shipment Cert Lacks Evidencing | A credit requires a "pre-shipment inspection certificate." The issued certificate is titled merel... |
| Title/Content Drift on a Pre-Shipment Requirement | The certificate is dated before shipment but titled generically, with content that does not refer... |
← 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 generates compliant Inspection Certificate Date After Shipment — 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