All articles
Trade Finance & LCPractical guide

From PI to LC: make the document handover easier to follow

A clear version history, named reviewers and a correction log can make a busy import team's PI-to-LC handover easier to manage.

Containers and cranes in winter at the Eimskip terminal in Reykjavík, Iceland
Eimskip container terminal, Reykjavík, Iceland · 8 February 2025. Context photograph, not evidence of a news event.
Photo: Quintin Soloviev · CC BY 4.0 · Thumbnail resized; display may crop the frame. No other edits by Xenzlab.

Create one agreed starting point

The commercial conversation often starts across email, calls and WhatsApp. Before the LC handover, collect the agreed PI and give it a clear file name and version. Record the parties, the quoted goods, the commercial terms and the shipment dates that the team needs to review.

Separate the signed PI from earlier offers. Keep a short note of any point still awaiting confirmation, and name the person who will resolve it. The goal is not a larger folder; it is a working file in which the next reviewer can immediately find the right document.

Treat corrections as a conversation with a history

When the buyer receives an LC draft, share that exact version with the designated agent or supplier reviewer. Log each requested change beside the relevant clause, the reason for the request and the person who raised it. Do not quietly overwrite the draft while several people are discussing different versions.

A requested correction is not yet a bank-confirmed correction. Record the bank's response separately: accepted, revised, not accepted or awaiting clarification. If another draft arrives, give it a new version and compare it against the request log before circulating it again.

Sunset over cranes and containers at Pasir Panjang Container Terminal, Singapore
Pasir Panjang Container Terminal, Singapore · 10 January 2026. Context photograph, not evidence of a news event.
Photo: Icepinner · CC BY 4.0 · Source photograph colour-corrected and sharpened by its author. Thumbnail resized; display may crop the frame.

Keep issued documents separate from planning notes

After the transmitted LC is available, store it separately from drafts and record when the supplier acknowledged it. Shipment planning, booking updates and document preparation can then be linked to that file without making the draft look like an issued bank document.

ICC publishes guidance on issues around UCP 600, including strict compliance and on-board notations. It is a useful reference point for questions to discuss with your bank. A software checklist does not replace the applicable credit terms, the relevant rules or the bank's examination.

Make follow-ups specific

A good follow-up names the document, version, question and requested response date. For example: confirm whether the attached draft includes the correction requested against the shipment clause. This is easier to answer than a general request to check everything again.

Use Xenzlab to organise the file, prepare a review and assign the next task. Authorised people must confirm the LC, any discrepancy response and any payment instruction. An automated reminder should never be presented as a bank approval or proof that payment has been released.

Sources & editorial notes

AI-assisted original explainer. This is an evergreen working guide, not a live news report. Photographs show the locations identified in their captions; they do not verify an event or a customer’s shipment. This article provides general information, not bank, legal, customs or investment advice.

Editorial policy and corrections