Documents

Commercial Invoice Discrepancy: Expired or Stale Document

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

Introduction

A commercial invoice presented under a letter of credit must be issued within the timeframe required by the credit. An expired or stale invoice—one presented after the credit's expiry or outside the document presentation period—creates a compliance gap that the examining bank must assess. The distinction between an invoice that is stale and one that is merely old is important: the credit's terms define what constitutes staleness.

Google News RSS surfaced reporting on LC compliance and documentary discrepancies, including a Dentons analysis of strict compliance and a Business Standard expert opinion on LC documentation. These provide the live context for this guide.

Failure Mode Analysis

Failure Mode 1: Treating the invoice's age as the compliance criterion

The invoice's age relative to the credit's issuance is not the compliance criterion. The criterion is whether the invoice was presented within the timeframe required by the credit. An old invoice may still comply if it is presented on time.

Failure Mode 2: Assuming an invoice issued before the credit is automatically stale

An invoice issued before the credit is not automatically stale. The credit's terms define the required timeframe for presentation. The examiner must assess compliance against the credit, not against general assumptions.

Failure Mode 3: Failing to distinguish between invoice date and presentation date

The invoice date and the presentation date are different. The invoice may have been issued early but presented late, or issued late but presented on time. The examiner must assess both dates against the credit's requirements.

Failure Mode 4: Rejecting an invoice without checking the credit's specific terms

The credit's terms define what constitutes staleness. The examiner must read the credit's requirements before rejecting an invoice. A general assumption that old invoices are non-compliant is incorrect.

Deterministic Resolution Architecture

  1. Extract the credit's requirements for invoice timing, including any stipulated presentation period.
  2. Identify the invoice date, the shipment date, and the presentation date.
  3. Determine whether the invoice was presented within the credit's required timeframe.
  4. Assess whether the invoice's age, relative to the credit's terms, creates a discrepancy.
  5. If the invoice is stale, request a corrected invoice or an amendment to the credit.
  6. If the invoice is not stale, assess whether other discrepancies exist.
  7. Preserve the documentary record of the assessment.

Conclusion

An expired or stale commercial invoice is a discrepancy only when it fails to comply with the credit's specific timing requirements. The examiner must assess the invoice's date, the shipment date, and the presentation date against the credit's terms. General assumptions about invoice age do not replace the credit's specific requirements.

FAQ

What makes a commercial invoice "stale"?

A commercial invoice is stale when it is presented outside the timeframe required by the credit. The credit's terms define what constitutes staleness.

Can an invoice issued before the credit comply?

Yes, if the invoice is presented within the credit's required timeframe. The invoice's issue date relative to the credit's issuance is not the compliance criterion.

What is the standard presentation period under UCP 600?

UCP 600 Article 14(c) provides that presentation must be made not later than 21 days after the date of shipment, unless the credit stipulates otherwise.

Can a bank reject an invoice based on its age alone?

No. The bank must assess the invoice against the credit's specific terms. Age alone is not a basis for rejection.

What should the exporter do if the invoice is stale?

The exporter should request a corrected invoice or an amendment to the credit before presentation.

Source Notes

Did You Know?

UCP 600 Article 14(c) provides that a presentation must be made not later than 21 days after the date of shipment, unless the credit stipulates otherwise.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 6Availability, Expiry Date and Place for PresentationBinary 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
Treating the invoice's age as the compliance criterionThe invoice's age relative to the credit's issuance is not the compliance criterion. The criterio...
Assuming an invoice issued before the credit is automatically staleAn invoice issued before the credit is not automatically stale. The credit's terms define the req...
Failing to distinguish between invoice date and presentation dateThe invoice date and the presentation date are different. The invoice may have been issued early ...
Rejecting an invoice without checking the credit's specific termsThe credit's terms define what constitutes staleness. The examiner must read the credit's require...

← 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 Commercial Invoice Discrepancy — 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