How to Track Letter of Credit (LC) Expiry Dates

LC expiry tracking: why teams get this wrong

Most teams track only one date: the LC expiry date.

That is not enough.

In practice, an LC has multiple deadlines that can fail the deal earlier:

• Latest shipment date (your forwarder misses it, you cannot “fix” it later)
• Document presentation timeline (you ship on time but present documents too late)
• Document issuance constraints (on-board notation, transport doc dates, certificate issuance timing)
• Amendment cutoffs (banks and counterparties need time to approve an amendment)

If you want a system that works, you need to treat the LC as a timeline and track every gate that can block payment.

If you need a full primer first, start here: /resources/what-is-letter-of-credit.

Step 1: Extract the four dates that control 90% of outcomes

For every LC, extract these into a single record (a spreadsheet row is fine; a system is better):

1. LC issue date
2. Latest shipment date (sometimes called latest date of shipment)
3. Expiry date (and expiry place, if stated)
4. Presentation window: last date the bank will accept a compliant presentation

Important: the “presentation window” is not always explicitly written as a date. It can be expressed as a number of days after shipment.

Step 2: Build an LC timeline from the shipment date backward

Operationally, your clock is driven by the shipment.

Use this timeline pattern:

• T0: On-board / shipment event (depends on mode and LC wording)
• T0 + N days: presentation deadline (if the LC specifies a period)
• before shipment: docs you must secure before goods move (certificates, inspection, permits)

A practical way to compute internal deadlines

Set internal deadlines earlier than the bank deadlines.

Example (illustrative):

• Latest shipment date: 30 Apr
• Presentation period: 21 days after shipment
• Your internal rule: keep a 5 business day buffer

Internal targets:

• Latest shipment date (internal): 25 Apr
• Presentation to bank (internal): shipment date + (21 days - 5 business days)

This buffer is what absorbs real-world delays: courier cutoffs, document rework, signatures, or last-minute wording issues.

Step 3: Track document gates (the hidden deadlines)

In most LC workflows, the “date miss” is not the LC expiry. It is an upstream document gate.

Track these as checklist items tied to a due date:

• Commercial invoice ready and matches LC fields (names/addresses, descriptions, currency, Incoterms if stated)
• Packing list ready and consistent with invoice
• Transport document issued (B/L or AWB) with required notations
• Insurance evidence (only if the credit requires it)
• Certificates required by the LC (e.g., certificate of origin, inspection certificate)

ICC guidance materials cover common documentary credit practices and topics such as on-board notation and strict compliance in document examination, which is why small date and wording mismatches matter in real life.

Related reference: /glossary/bill-of-lading

Step 4: Treat amendments as a workflow, not an email

You cannot “wish” an amendment into existence the day before a deadline.

When a date is at risk, you need a controlled amendment workflow:

1. Identify the failing gate (shipment date, presentation period, document wording)
2. Propose the smallest change that resolves it
3. Get applicant approval
4. Get issuing bank issuance
5. Confirm all banks in the chain have advised it (and, if confirmed, confirming bank acceptance)

Track amendments as their own items with status and timestamps.

Step 5: Implement alerts that match how teams work

Alerts should fire on the dates that matter operationally, not only on expiry.

Minimum alert schedule:

• 30 days before latest shipment date
• 14 days before latest shipment date
• 7 days before latest shipment date
• 3 days before latest shipment date
• 7 days before presentation deadline
• 3 days before presentation deadline
• 1 day before presentation deadline

Add separate alerts for any “must-have” certificate whose issuance time is uncertain.

Step 6: Use a single source of truth for LC fields

Expiry tracking breaks when data is scattered across:

• email threads
• PDF scans
• multiple spreadsheets
• “final_final_v3” documents

Make one LC record the authority for:

• all dates
• all parties (applicant/beneficiary/banks)
• required documents
• key wording constraints (partial shipment allowed, transshipment allowed, etc.)

Generate documents from that record or at least validate documents against it.

Step 7: Run a pre-presentation checklist (strict compliance mindset)

Documentary credits are operationally unforgiving. Treat presentation as a controlled release.

Pre-presentation checklist:

• Every required document exists
• Names/addresses match LC text (including punctuation and legal forms)
• Dates are consistent with the credit and with each other
• Quantity/weights/marks are consistent across invoice, packing list, and transport document
• Any on-board or shipment notations required are present

If you consistently fail this step, your issue is not “tracking”. It is that your docs are not produced from a controlled dataset.

How Tijara helps

Tijara links your LC record, shipment milestones, and documents so you can:

• store all LC deadlines in one place,
• auto-alert the real deadlines (shipment and presentation, not only expiry),
• keep amendments tracked as their own workflow,
• generate or validate documents from a single source of truth.

Related reading:

• /resources/what-is-letter-of-credit
• /resources/how-to-open-letter-of-credit