What is a letter of credit?
A letter of credit (LC) is a trade finance instrument where a bank undertakes to pay a seller, provided the seller presents the required documents that comply with the credit’s terms.
ICC’s trade finance guide summarizes it simply as a bank guarantee that ensures the seller receives payment provided agreed-upon terms are met.
In real operations terms:
- You are not “proving you shipped”.
- You are presenting documents that match what the LC asked for, within the required timelines.
If you want to avoid surprises, treat the LC as a spec.
LC meaning (simple definition)
If you're searching for “LC meaning” or “what is LC”, this is the most practical definition:
An LC is a bank’s promise to pay the seller if the seller presents compliant documents on time.
That means your “product” to the bank is the document set, not the physical shipment.
LC full form
LC full form: Letter of Credit.
In trade, “LC” usually refers to a documentary letter of credit (a bank-backed, document-driven payment instrument), not a generic bank transfer.
Why letters of credit exist
International trade has two core risks:
- the seller worries about getting paid;
- the buyer worries about paying for the wrong goods or non-shipment.
An LC sits between the two and shifts the payment mechanism to a document-driven process that banks can examine.
This is why letters of credit are often used for new counterparties, unfamiliar jurisdictions, or deals where assurance of payment is crucial.
The parties in a letter of credit
Most LCs have at least these roles:
- Applicant: the buyer who requests the LC
- Beneficiary: the seller who will be paid if they present compliant documents
- Issuing bank: the applicant’s bank that issues the LC
- Advising bank: the bank that advises the LC to the beneficiary (often in the seller’s country)
Sometimes you also have:
- Confirming bank: adds its own undertaking to pay (useful when the seller wants to reduce issuing-bank or country risk)
How an LC works (the real workflow)
The clean mental model is a three-stage workflow:
-
Issuance The buyer applies; the issuing bank issues the LC text.
-
Execution Seller produces and ships goods, then obtains documents (invoice, transport doc, certificates, etc.) matching LC requirements.
-
Presentation and examination Seller presents documents to the nominated bank; banks examine for compliance; payment/acceptance/negotiation happens based on the LC’s availability.
The important part is stage 3.
The LC process in 10 lines (operator version)
- Buyer and seller agree commercial terms (price, Incoterm + named place, shipment window).
- Seller shares a proforma/commercial terms sheet for the LC draft.
- Buyer applies to the issuing bank; collateral/limits are arranged.
- Issuing bank issues the LC text; advising bank advises it to the seller.
- Seller checks LC text against the deal and requests amendments if needed.
- Seller produces/ships goods and collects documents.
- Seller presents documents within the allowed presentation period.
- Banks examine documents for compliance (UCP 600 if incorporated).
- If compliant: payment/acceptance/negotiation happens per LC availability.
- If discrepant: waiver/amendment/rejection workflow begins.
LC issuance, LC payment, and LC fees (what those phrases mean)
If you see these terms in search or in your bank workflow, here’s the practical meaning:
- LC issuance: when the issuing bank releases the LC text (and the seller receives an advised LC).
- LC payment: what happens after compliant presentation (payment at sight or at a deferred/usance tenor).
- LC fees / LC charges: bank charges across issuing/advising/confirmation, amendments, examination, and discrepancy handling.
Start here if you’re new:
- Opening an LC: /resources/how-to-open-letter-of-credit
- Bank charges: /resources/lc-bank-charges-guide
The strict-compliance principle (why tiny mismatches hurt)
Documentary credits are run on a compliance mindset. That is why “almost right” can still be treated as discrepant.
ICC publishes guidance materials for practitioners around UCP 600 usage, including discussion areas like strict compliance, on-board notations, and documentary credit formats.
Operational takeaway:
- build documents from a single source of truth;
- validate every document against the credit text before presentation.
Key LC dates you must track
If you track only one date, you will eventually lose money.
At minimum track:
- Latest shipment date
- Expiry date (and where the credit expires)
- Presentation deadline (can be a date or a period after shipment)
This is why LC operations teams implement a deadline tracker.
Related how-to: /resources/track-letter-of-credit-expiry
The “required documents” section is where deals break
An LC usually specifies what must be presented. Common examples:
- commercial invoice
- packing list
- transport document (bill of lading or airway bill)
- certificate of origin
- insurance document (only if required)
- inspection certificate (only if required)
If your business ships by sea, the bill of lading is often the most operationally sensitive document. See: /glossary/bill-of-lading
LC documents checklist (what teams actually control)
Most LC failures are controllable if you run a standard checklist:
- Document templates: invoice, packing list, certificates (standardized wording)
- Party names and addresses: applicant/beneficiary/consignee (exact match)
- Product description control: consistent SKU descriptions across all docs
- Dates and deadlines: shipment date, expiry, presentation period
- Version control: only one “final” PDF per document type in circulation
Common LC types (the ones you see in practice)
Your bank will structure specifics, but teams usually encounter these patterns:
- Sight vs deferred/usance: whether payment is at presentation or later
- Confirmed vs unconfirmed: whether another bank adds its payment undertaking
- Transferable: whether the beneficiary can transfer rights to another party
- Standby LC: often used more like a guarantee in certain contexts
Do not guess your obligations based on the “type” label. Always operate off the actual text and timelines.
Common LC problems (and the pages that fix them)
- Discrepancies: /resources/common-lc-discrepancies
- Discrepancy handling and amendments: /resources/lc-discrepancies-amendments
- Bank charges: /resources/lc-bank-charges-guide
- Sight vs usance: /resources/sight-lc-vs-usance-lc
- Opening an LC: /resources/how-to-open-letter-of-credit
- Red clause LC: /glossary/red-clause-letter-of-credit
- Documentary credit: /glossary/documentary-credit
Digital presentation and eUCP (when documents are electronic)
Some LCs involve electronic presentation or digitally handled documentary credit workflows.
ICC’s eUCP is positioned as a supplement and digital companion to UCP 600 for a digital environment.
Operationally: if your LC references eUCP/electronic presentation rules, you need to treat file formats, submission methods, and receipt timestamps as part of compliance.
When should you use an LC?
LCs introduce cost and operational overhead. Use them when you need the risk control.
Common triggers:
- first deal with a new overseas buyer/seller
- large ticket sizes relative to your working capital
- jurisdictions/banks you want risk protection against
- when the buyer requires bank-driven documentation controls
If you trade frequently with a trusted partner, other instruments (or open account terms) may be more efficient.
How Tijara helps
Tijara helps LC-driven teams run predictable operations by:
- storing LC terms and dates as structured data,
- tracking shipment and presentation deadlines,
- keeping documents aligned to one dataset,
- flagging discrepancies before you present.
Next reads: