# Loamist: the full site in markdown > Every page of https://www.loamist.com, one after another. Index: https://www.loamist.com/llms.txt --- URL: https://www.loamist.com/ # Loamist: agents for the physical economy Canonical URL: https://www.loamist.com/ ## Order, from the ground up. The physical economy runs on paper, maps, and judgment. Loamist turns it into decisions agents can make, and proves every one. ## Fig. 01 · Live: the goods, documents and data flow 1. As it arrives: goods, documents, data. 2. Read and decide: Loamist. 3. Proven: organized decisions. Goods, documents and data arrive from ports around the world and flow into Loamist. Each one leaves as an organized decision that passes an evals gate; 98.5% pass in the illustration. ## § 01 · How Loamist works Every Loamist agent does three things. - **Read.** Bills of lading, site surveys, rate cards, inboxes. Agents read what your people read, in the form it arrives. - **Decide.** Each reading becomes a decision: compliant or not, build here or not, route this way or that. - **Prove.** Every decision is checked by evals, and the evals are checked again. That is how accuracy holds at 98%. ## § 02 · What makes us different ### Reliability where no one had reached it. Loamist applies proprietary techniques to reach reliability thresholds in verticals no one had solved, and holds 98%+ accuracy, run after run. 1. **We know how to build a rigorous eval system.** We set the accuracy a decision has to reach before we build the agent that makes it. 2. **Multi-step evals are required; we build them.** Evals, and evals of those evals, that find and remove variance, not just errors. 3. **In prod, at enterprise scale.** 98%+ across repeated runs in production, not one good result on a good day. Fig. 03 · 32 runs each, same task (comparison illustrative): Loamist holds 99.0% to 99.45% on every run, above the 98% threshold. A typical agent varies between about 76% and 94%. Have a problem that needs reliability? Trust us with it. [Book a working session](https://www.loamist.com/contact.html) ## § 03 · One team ### One team. A product for every vertical. We learned how to make language models work reliably on real operations. Each vertical gets its own product, built by the same people. 1. [Loamist Trade Finance](https://www.loamist.com/trade-finance): L/C document examination for banks and corporates. 2. [Loamist Geospatial](https://www.loamist.com/geospatial): Site and cost decisions, compared on one map. 3. [Loamist Evals](https://www.loamist.com/evals): Evals and nested evals that hold agents above 98%. 4. [Loamist Services](https://www.loamist.com/services): Our team, building agents inside yours. ## Loamist in numbers - $1B on platform - 98%+ accuracy, run after run - PG&E: case study, wildfire siting (https://www.loamist.com/geospatial) - USFS: fiscal agent, federal audit passed (https://www.loamist.com/services) ## Enterprise-level security - **SOC 2 Type II certified.** Independently audited for security, availability, and confidentiality. - **Zero Data Retention AI.** Model providers keep none of your data, and none of it trains their models. [Read the cybersecurity whitepaper](https://www.loamist.com/cybersecurity-whitepaper.html) ## § 04 · Start ### Bring the hardest problem you have. [Book a working session](https://www.loamist.com/contact.html) More: [Blog](https://www.loamist.com/blog/) · [Guides](https://www.loamist.com/resources.html) · [About](https://www.loamist.com/about.html) · [Contact](https://www.loamist.com/contact.html) --- URL: https://www.loamist.com/evals # Loamist Evals > Agents that hold 98%+, run after run. Reliability for enterprise agents. Canonical: https://www.loamist.com/evals Loamist builds evals and nested evals that make agents work inside your enterprise. Our techniques beat variance, reach your reliability threshold, and hold 98%+ accuracy consistently. - **98%+**: Accuracy, run after run - **Nested**: Multi-step evals - **Threshold**: Set before we build - **In prod**: Enterprise scale ## Fig. 01 · Same task, run after run: Variance is the problem. Nested evals remove it. An illustrative dot-column chart of repeated runs of the same task against a 98% threshold. Each eval depth narrows the run-to-run spread. | Eval depth | Mean accuracy | Spread, run to run | |---|---|---| | Single agent (off-the-shelf model) | 81.2% | ±11 pts | | + Evals (checks on every output) | 90.4% | ±6 pts | | + Nested evals (evals of the evals) | 96.1% | ±2.6 pts | | + Customer-tuned preferences (Loamist knowledge base graph) | 99.0% | ±0.5 pts | ## § 01 · What makes it work: Reliability is measured, not hoped for. 1. **We know how to build a rigorous eval system.** We define the threshold a decision has to reach, then build the evals that prove it, before the agent ships. 2. **Multi-step evals are required; we build them.** Evals, and evals of those evals, that find and remove variance, not just errors. 3. **In prod, at enterprise scale.** 98%+ held across repeated runs on live work, not one good result on a good day. ## Start Have a problem that needs reliability? Trust us with it. - [Talk to the evals team](https://www.loamist.com/contact.html) - [About Loamist](https://www.loamist.com/) Loamist products: [Loamist Trade Finance](https://www.loamist.com/trade-finance) · [Loamist Geospatial](https://www.loamist.com/geospatial) · [Loamist Evals](https://www.loamist.com/evals) · [Loamist Services](https://www.loamist.com/services) --- URL: https://www.loamist.com/geospatial # Loamist Geospatial > Compare land and logistics on one map. Multicriteria siting, from carbonizers to data centers. Canonical: https://www.loamist.com/geospatial A geospatial decision platform that combines multicriteria site analysis with cost modelling. Teams compare complex scenarios side by side, from carbonizer sites to data centers, with every assumption traceable to its source and access set by role. - **PG&E, USFS**: Clients include - **Multicriteria**: Site analysis - **Traceable**: Every assumption - **Role-based**: Access ## Fig. 01 · Siting a mobile carbonizer: Where to build, and whether it beats current practice. A dot map of Northern California with seven candidate sites for a mobile carbonizer, the selected site, and the route to disposal. From the Loamist Geospatial tool. | Transport footprint | Miles driven | Transport CO₂e | |---|---|---| | Carbonize @ site | 326.3 mi | 0.5 t | | Haul to disposal | 1,384.9 mi | 2 t | **+1,059 mi** and **+1.50 t CO₂e** saved by carbonizing at this site. Each figure traces to its source: route distances, vehicle factors, and the site inputs your team approved. ## Fig. 02 · Multicriteria analysis: Four criteria, one answer. Four criterion maps merge into one combined suitability map. Each criterion has a weight from 0 to 10, and the map re-scores as the weights change. The top 5% of cells form the shortlist. Protected or too-steep ground is excluded. The inputs shown on the page are illustrative. - **Slope under 15%** (default weight 5): gentler ground scores higher - **Road access** (default weight 7): closer to a usable road - **Fire-risk buffer** (default weight 6): further from high-risk areas - **Feedstock within 5 mi** (default weight 8): more treatable material nearby ## Case study · PG&E · Mobile carbonizers: Preventing catastrophic wildfires. Thinning removes the fuel that turns ground fire into crown fire. Treating that material where it lies is what makes thinning affordable at scale. A data-driven animation shows the 2021 Antelope Fire reaching an untreated stand (dense, with low crowns) and a thinned and burned stand (treated 20 and 10 years earlier). The untreated crowns burn; the treated crowns survive. - **60 pts**: lower probability of tree mortality in thinned and burned stands - **86 pts**: less crown volume consumed by the fire - **5 to 7×**: fewer trees per hectare after thinning - **20 yrs**: thinning still limited crown fire two decades later Source: Brodie, E. G., E. E. Knapp, W. R. Brooks, S. A. Drury, and M. W. Ritchie. 2024. Forest thinning and prescribed burning treatments reduce wildfire severity and buffer the impacts of severe fire weather. *Fire Ecology* 20: 17. [doi.org/10.1186/s42408-023-00241-z](https://doi.org/10.1186/s42408-023-00241-z) A randomized, replicated 1,200 ha experiment on the Klamath National Forest, burned by the 2021 Antelope Fire. Figures compare thinned-and-burned stands with untreated controls. Stand drawing to scale: crown base 3 m on pole trees, 11 m on large trees. - **The question**: PG&E clears hazardous vegetation to reduce the risk of catastrophic wildfire. Where should a mobile carbonizer go, and does treating that material on site beat hauling it to disposal? - **What we modelled**: Candidate sites scored on slope, road access, fire-risk buffer, and nearby feedstock. Each site then carried its own transport and cost model against current practice. - **What it showed**: At the selected site, carbonizing in place meant 326 miles of driving against 1,385 to haul the same material to disposal. Saved at the selected site: **1,059 mi** fewer miles driven, **1.50 t** less transport CO₂e. From the Loamist Geospatial tool. Every figure traces to its route, vehicle factor, and site input. ### Same method, any siting question. Including data centers. Multicriteria analysis + cost model. 1. **Data centers.** Grid capacity, water, fiber, land cost, permitting, and hazard exposure, weighed together. 2. **Mobile carbonizers.** Where to treat material, and whether it beats hauling to disposal. 3. **Energy and storage.** Interconnection, resource quality, land use, and environmental constraints. 4. **Logistics facilities.** Drive times, labor, road access, and lease cost against demand. ## § 01 · What it does: Every answer shows its work. 1. **Multicriteria site analysis.** Weigh terrain, access, risk, and feedstock together, then see how the ranking moves when priorities change. 2. **Cost modelling.** Each scenario carries its own cost model, compared directly against current practice. 3. **Traceable assumptions.** Every number links to the dataset, rate card, or study it came from. 4. **Role-based access.** Planners, analysts, reviewers, and sub-contractors each contribute data at their own permission level. Every tenant sees only what it is allowed to see, and nothing more is shared. ## Start Bring a siting question. We will model it with you. - [Book a scenario session](https://www.loamist.com/contact.html) - [About Loamist](https://www.loamist.com/) Loamist products: [Loamist Trade Finance](https://www.loamist.com/trade-finance) · [Loamist Geospatial](https://www.loamist.com/geospatial) · [Loamist Evals](https://www.loamist.com/evals) · [Loamist Services](https://www.loamist.com/services) --- URL: https://www.loamist.com/services # Loamist Services > Our engineers, inside your operations. Forward-deployed engineering. Canonical: https://www.loamist.com/services Loamist Services is the team behind every Loamist product, working directly on your hardest decision. We scope it, build agents with evals from day one, and run them in production. Then we hand them to your team, or stay embedded and send you the answers as reports. - **One team**: Behind every product - **Evals**: From day one - **In prod**: Not a pilot - **Your choice**: Hand over, or keep us ## Fig. 01 · From our team to yours: Hand it to your team, or keep us embedded. Two lanes over the life of an engagement: Loamist engineers taper off as your team grows. The handover path is shown. 1. Find the decision 2. Build with evals 3. Run in production 4. Hand over, or keep us ## § 01 · How we work: One decision, built to hold. 1. **Find the decision.** We start from one decision your operation makes every day, and the accuracy it has to reach. 2. **Build with evals.** Agents and their evals are built together, so reliability is measured from the first run. 3. **Run in production.** We run it on live work, at enterprise scale, alongside your people. 4. **Hand over, or keep us.** Your team can own it, with the eval system that keeps it honest. Or we stay embedded for as long as you like, run the agents ourselves, and deliver the answers as reports. ## In practice · US Forest Service: Fiscal agent for the USFS. Loamist acts as a fiscal agent for the US Forest Service, managing program funds on the agency's behalf and accounting for every dollar. **Passed federal audit.** Our fiscal management of the program has been independently audited. 1. **Funds, administered.** We receive, manage, and disburse program funds under the agency's rules. 2. **Reporting the agency relies on.** Clear, regular, traceable reports on where every dollar went and what it delivered. 3. **Built on our own tools.** The same agents and evals we deploy for clients keep the books accurate and the reports on time. HFTA program, funds disbursed: **$4M**. Every dollar reconciled, federal audit passed. ## § 02 · Acquisitions: We are buying services businesses. Loamist acquires small services businesses and brings our agents and evals to the work they already do well. Your team, your clients, and your name stay. The operations get faster and more reliable. Areas we are looking at: 1. Trade finance 2. Document compliance 3. Logistics Run a small services business in one of these areas? We would like to talk. [Reach out to us](https://www.loamist.com/contact.html). Conversations are confidential. ## Start Bring the decision you cannot get wrong. - [Book a working session](https://www.loamist.com/contact.html) - [About Loamist](https://www.loamist.com/) Loamist products: [Loamist Trade Finance](https://www.loamist.com/trade-finance) · [Loamist Geospatial](https://www.loamist.com/geospatial) · [Loamist Evals](https://www.loamist.com/evals) · [Loamist Services](https://www.loamist.com/services) --- URL: https://www.loamist.com/trade-finance # Loamist Trade Finance: export LC validation and document examination Canonical page: https://www.loamist.com/trade-finance Loamist Trade Finance validates export letters of credit against UCP 600, examines document sets for discrepancies, and monitors freight fees. 99% pre-check accuracy on live transactions. ## Export LCs, checked at 99%. Purpose-built AI that checks letters of credit against UCP 600, examines documents for discrepancies, and monitors export fees. 99% pre-check accuracy, measured on live transactions with existing customers. - [Check your LC, free](https://www.loamist.com/lc-check.html) - [Book a demo](https://www.loamist.com/contact.html) Key numbers: - 99% pre-check accuracy, live - 70% less effort per LC - UCP 600 compliant - SOC 2 Type II certified Sample examination (fictional LC-2026-0847): UCP 600 articles validated (47 rules checked); invoice, B/L and packing list cross-referenced; REACH and TSCA documentation aligned; one advisory, an Incoterms mismatch with the carrier B/L. Result: clean, confidence score 99.8%. ## How a Letter of Credit works, and where Loamist checks it 1. Agree the sale: you and the buyer agree to pay by Letter of Credit. 2. L/C issued: the buyer's bank promises to pay. 3. Ship goods: the goods sail and you prepare the documents (invoice, bill of lading, certificates). 4. Check first: Loamist checks every document against the credit before the bank does. Without Loamist, 65 to 80% of first presentations are refused for discrepancies, with at least 5 banking days of delay per refusal plus the buyer's waiver decision and extra bank fees. With Loamist, you find and fix discrepancies before you present; the bank decides within 5 banking days and pays. Sources: ICC Banking Commission, Technical Advisory Briefing No. 3 (2022); UCP 600, Article 14(b). ## 01 · The challenge: 70% of LC presentations contain discrepancies. For large chemical and commodity exporters, that means delayed payments, re-rated freight, and eroded margins on every shipment. - **30 to 45 days: delayed cash cycles.** Discrepancies extend payment cycles by 30 to 45 days. Manual examination takes 30+ minutes per LC, and errors compound across hundreds of monthly shipments. - **3 to 8%: freight spend lost to billing errors.** Mis-declared weights, incorrect Incoterms, and inconsistent documents drive re-rating, demurrage, and storage fees. Industry benchmark. - **8+ documents per shipment, all aligned.** REACH, TSCA, CEPA, CSCL, and GHS documentation must match commercial and transport documents. One mismatch triggers rejections and customs holds. Built for: - **Exporters:** check LC terms before production and present clean documents the first time. - **Issuing and advising banks:** examine presentations faster, with every finding traced to its rule. - **Confirming banks:** assess documentary risk before adding your undertaking. - **Forwarders and customs brokers:** prepare shipping instructions and declarations that match the credit. ### Before and after: the same six documents | Document | Before, as presented (4 discrepancies) | After, checked by Loamist (clean) | |---|---|---| | Commercial invoice | Goods description differs from 45A | Corrected before shipment | | Bill of lading | Consignee not to order of issuing bank | Corrected before shipment | | Packing list | Gross weight 24,690 kg vs 24,960 kg on B/L | Corrected before shipment | | Certificate of origin | Matches | Matches | | Insurance certificate | Cover 100%, credit requires 110% | Corrected before shipment | | Bill of exchange | Matches | Matches | Before: rejected at the bank. Amendments, re-presentation, and 30+ days of delay. After: caught before shipment. Presented once, paid on schedule. ## 02 · How it works From upload to bank presentation in 3 minutes. 1. **Ingest.** Push LC and sales order data from your ERP or export documentation system. Loamist gathers the unstructured documents and structures them for validation. 2. **Validate.** Proprietary models cross-reference every document against UCP 600, ISBP, bank-specific conditions, and your internal playbook, then flag discrepancies and suggest amendments. 3. **Present.** Validated, structured data flows to your ERP and banking rails, with LC-compliant document drafts and instructions to third parties. ## 03 · Ways to work with us: three ways to run it. The same examination engine and the same 99% accuracy, delivered the way your team works. 1. **Platform: the full-featured L/C app.** Your team works in the Loamist app: upload a document set, review findings with the rule behind each one, draft compliant documents, and track every LC to presentation. Examination, drafting, and fee monitoring in one workspace; findings cite the document, field, and rule; role-based access for your trade team. 2. **API: headless, via our API.** Call the same examination engine from your own systems. Send documents from your ERP or TMS, get structured findings back, and keep your existing workflow. REST endpoints with structured JSON findings; connects to ERP, TMS, and banking rails; webhooks when an examination completes. 3. **Full service: run for you, by us.** Send us the documents. Our team runs the examination, reviews the findings, and returns a clear report, so nothing reaches the bank unchecked. Loamist examiners run and review every set; reports returned on an agreed turnaround; no software for your team to adopt. ## 04 · Platform capabilities: examination, screening, drafting, and fees, in one workspace. Built for chemical and commodity exporters. Trade finance expertise and logistics validation, side by side. ### Pre-shipment LC analysis Validate whether LC terms are achievable before committing production. Flags impossible conditions: tight shipment dates, unworkable document requirements, and conflicting clauses. - Classifies LCs as clean or unclean, with amendment suggestions - Cross-checks sales order data against LC terms - Identifies the top 10 discrepancy families before bank presentation ### Post-shipment document examination Examines invoices, bills of lading, packing lists, and certificates for consistency and UCP 600 compliance after shipment, before anything reaches the bank. - Detects name mismatches, date issues, and quantity discrepancies - Validates document completeness against LC requirements - Cross-document consistency checks across full document sets ### Traceable findings and audit trail Every finding cites the document, the field, the UCP 600 or ISBP rule, and your own practice. The full record is kept for compliance review and dispute resolution. - Click through from any finding to its source field - Log of every check, edit, and approval - Exportable record for auditors and counterparties ### Examiner review workflow Loamist proposes, your examiners decide. Each discrepancy can be confirmed, overridden, or annotated, and every decision is logged. - Queue by deadline and priority - Confirm, override, or annotate each finding - Four-eyes approval before presentation ### Sanctions, AML, and dual-use screening Parties, vessels, ports, and goods are screened as part of examination, alongside the discrepancy check. - Parties and vessels checked against global sanctions lists - Trade-based money laundering red flags, including price and route anomalies - Dual-use goods flagged by description and HS code ### Freight fee monitoring Track and audit freight invoices against shipment data. Catch re-rated charges, unexpected accessorials, and billing discrepancies before they compound. - Compares billed weights and counts against validated documentation - Flags Incoterms misalignment and carrier billing anomalies - Builds evidence packages for freight dispute resolution ### Integrations Loamist fits into the systems you already run, so documents arrive and results leave without rekeying. - ERP and export documentation systems - SWIFT MT700 and MT707 intake - Email and shared-inbox ingestion - API and webhooks for downstream booking ### Languages and formats Scans, photos, PDFs, and structured messages, in the languages your counterparties use. - Scanned and photographed documents - Multilingual document sets - Structured data out, in your schema ## 05 · Document drafting: drafted to match the credit, before anyone signs. Loamist drafts the full document set from the LC and your sales order. Every field that the credit governs is filled to match it, and flagged where it cannot. Examples use a fictional transaction: Kestrel Industries to Meridian Polymer Trading, LC-2026-0847. 1. Draft L/C application: the credit your buyer should open, with terms you can actually meet. 2. Commercial invoice: values, descriptions, and Incoterms that mirror the credit word for word. 3. Packing list: packages, weights, and marks consistent with the invoice and B/L. 4. Bill of lading instructions: shipping instructions that produce a clean, compliant B/L from the carrier. 5. Bill of exchange: the draft drawn under the credit, with tenor and amount in agreement. 6. Certificate of origin: origin and HS details ready for chamber certification. 7. Insurance certificate: cover, clauses, and claims location exactly as the credit requires. 8. Beneficiary certificate: statements the credit asks the beneficiary to certify, worded to comply. 9. Export customs declaration: declaration data aligned with the commercial set and the credit. 10. Regulatory pack: SDS, REACH, TSCA, and GHS documents aligned to the commercial set. 11. Instructions to third parties: clear instructions for forwarders, carriers, inspectors, and insurers. ## 06 · Return on investment: present clean the first time. Get paid on schedule. - 70% less effort per LC, measured with a live client - 3 to 8% of freight spend lost to billing errors, industry benchmark - 99% pre-check accuracy on live transactions - Less than 4 weeks to production deployment ### Discrepancy cost calculator For exporters processing 100+ LCs a month, Loamist typically pays for itself within the first quarter through fewer discrepancy delays and recovered freight costs. Inputs and defaults: | Input | Default | Range | |---|---|---| | Export LCs per year | 200 | 20 to 1,000, step 10 | | Presentations per LC | 1.2 | 1.0 to 2.0, step 0.1 | | Average LC value | $300,000 | $50,000 to $1,500,000, step $25,000 | | Discrepancy rate | 40% | 0 to 100% | | Annual working capital rate | 8% | 0 to 20%, step 0.5 | Formula, per discrepant presentation: - Direct bank and documentation = $500 (discrepancy fee $150 + amendment fee $150 + SWIFT $50 + re-documentation $150) - Financing cost of delayed payment = LC value × working capital rate × 21 / 365 (21 days to cure) - Commercial and operational = LC value × 1.0% buyer concession × 30% of discrepancies + 1 staff hour × $65 Discrepant presentations = round(LCs per year × presentations per LC × discrepancy rate). Total annual discrepancy cost = discrepant presentations × cost per discrepant presentation. With the defaults: 96 discrepant presentations × $2,846 each ($500 + $1,381 + $965) = **$273,199 a year**. With 99% pre-check accuracy, most of this cost never reaches the bank. [Run a free LC check](https://www.loamist.com/lc-check.html). ## 07 · Security and compliance: security, just the facts. - **SOC 2 Type II.** Audited by an independent third party for security, availability, and confidentiality. - **Zero data retention AI.** Model providers keep none of your documents, and none of them train their models. - **Client logic, fenced (1:1).** What Validator learns from you is assigned to you and never trains the general model. - **Role-based access (RBAC).** Your team sees what their role allows, with every action logged for audit. [Read the cybersecurity whitepaper](https://www.loamist.com/cybersecurity-whitepaper.html). ## 08 · From the blog - [70% less time per letter of credit: what a documentation team does with the hours back](https://www.loamist.com/blog/seventy-percent-less-time-per-letter-of-credit/) (8 Oct 2026) - [Client logic, fenced and owned: whose data is it, and where does it go?](https://www.loamist.com/blog/client-logic-fenced-and-owned/) (6 Oct 2026) - [Explainability means credibility: an L/C finding you cannot trace is one you cannot trust](https://www.loamist.com/blog/explainability-means-credibility-lc-automation/) (24 Sep 2026) - [All posts](https://www.loamist.com/blog/) ## 09 · Start: see it on your own LC. A 30-minute walkthrough on your own documents. No commitment. - [Check your LC, free](https://www.loamist.com/lc-check.html) - [Book a demo](https://www.loamist.com/contact.html) --- URL: https://www.loamist.com/developers.html # Loamist API for developers and AI agents | Loamist > Send letters of credit and documents to the Loamist API and get structured findings back, with webhooks when an examination completes. Source: https://www.loamist.com/developers.html Developers Partner API · REST and webhooks # The Loamist examination engine, by API. Send a letter of credit and its documents from your ERP, TMS or your own agent. Get structured findings back, each one tied to the document, the field and the rule. It is the same engine and the same 99% pre-check accuracy as the Loamist app. How it works ## Three calls, one decision. - 01 ### Send the documents Create a project from an L/C and its document set with POST /v1/projects:import . PDFs and images are accepted. - 02 ### Loamist examines them Every term is extracted and checked against UCP 600, ISBP and your own rules, and the documents are checked against each other. - 03 ### Get structured findings A webhook fires when the examination completes. Findings come back as JSON, with the severity, the document, the field and the rule for each one. Access ## Built for production integrations. ### Workspace tokens Each integration uses its own API token, scoped to one workspace, so access stays inside your team's data. ### Sandbox first Start in a sandbox workspace with sample documents, then move to production with the same calls. ### Secure by default SOC 2 Type II certified. Model providers keep none of your documents, and none of them train their models. The full API reference is shared with partners during onboarding. [Request API access](https://www.loamist.com/contact.html) and we will set up a sandbox workspace with you. For AI agents ## This site, in a form agents can read. - [llms.txt](https://www.loamist.com/llms.txt): an index of every page, guide and blog post, with a one-line summary of each. - [llms-full.txt](https://www.loamist.com/llms-full.txt): the whole site as one markdown file. - Every page has a markdown version at the same address ending in .md , for example [/trade-finance.md](https://www.loamist.com/trade-finance.md). Blog posts use /blog//index.md . - Try the examination without the API: [the free L/C check](https://www.loamist.com/lc-check.html). --- URL: https://www.loamist.com/lc-check.html # Free L/C check: upload your export letter of credit | Loamist > Upload your export letter of credit and receive a detailed extraction and risk analysis. Free L/C check powered by Loamist AI. Source: https://www.loamist.com/lc-check.html Free L/C check Workability against UCP 600 # Get an AI-powered analysis of your letter of credit Upload your export letter of credit and enter your work email. We will send you a detailed extraction and risk analysis. - 01 ### Upload the credit One letter of credit, as a PDF or an image. - 02 ### We read it against UCP 600 Each term is extracted and checked for workability risk. - 03 ### Results here and by email Findings show on this page, and we email you a link to keep them. End-to-end encrypted Document deleted after processing --- URL: https://www.loamist.com/bill-of-lading-letter-of-credit-compliance.html # Match a Bill of Lading to LC Terms: UCP 600 Guide | Loamist > Match your bill of lading to LC terms without discrepancies. Covers UCP 600 Articles 20–23, freight terms, endorsement, B/L errors, and recovery steps. Source: https://www.loamist.com/bill-of-lading-letter-of-credit-compliance.html Guide · Bill of lading [Back to guides](https://www.loamist.com/resources.html) # How to match your bill of lading to letter of credit terms: a step-by-step guide Match your bill of lading to LC terms without discrepancies. Covers UCP 600 Articles 20–23, freight terms, endorsement, B/L errors, and recovery steps. Published 25 March 2026 9 min read ## Why B/L discrepancies are among the most costly The bill of lading (B/L) is both a transport document and a document of title. Under a letter of credit, it performs a unique function: when endorsed and transferred to the bank, it gives the issuing bank security over the goods in transit. Banks take this seriously. The entire collateral value of the LC, the bank's ability to control the cargo if the applicant defaults, rests on the B/L being compliant with LC terms. This is why B/L discrepancies carry disproportionate consequences. They are not merely administrative errors. A B/L showing the wrong consignee means the bank's security interest may be compromised. A claused B/L means the cargo may be damaged. A late shipped-on-board date means the exporter violated a material term. Any of these can result in outright refusal of the entire document set, not just a query. ICC Banking Commission data indicates that B/L-related discrepancies are among the top three most frequently cited in LC refusals worldwide. Typical cost of a B/L discrepancy: $300–$800 in re-examination fees, 7–15 business days of payment delay, and, in time-sensitive shipments, potential demurrage charges if the original B/L cannot reach the consignee before vessel arrival. ## Key B/L fields banks examine under UCP 600 UCP 600 Articles 20–23 govern transport documents. Article 20 specifically covers Bills of Lading. Banks examine the following fields in strict sequence: ### 1. Shipper name The shipper on the B/L must be either the beneficiary of the LC, or, where the LC permits or requires a third party, a named third party. Under **UCP 600 Article 14(k)**, if the LC does not specify the shipper, any entity may appear as shipper, but in practice most LCs require the beneficiary to be the shipper. **Common failure:** A parent company or freight forwarder appears as shipper instead of the beneficiary legal entity. Even where a forwarder is used, the shipper field on the B/L (sometimes called the "shipper/exporter" box) should reflect the beneficiary unless the LC explicitly allows a different shipper. If your freight forwarder issues a House B/L in their own name, this distinction becomes critical: see the section on House B/L vs. Master B/L below. ### 2. Consignee and notify party Under **UCP 600 Article 20(a)(i)**, a complying B/L must indicate the name of the carrier and be signed. It must also show the consignee as required by the LC. There are three typical consignee structures: - **"To Order"** or **"To Order of Shipper":** The B/L is an order B/L, negotiable by endorsement. Required when the LC calls for a negotiable B/L. - **"To Order of [Named Bank]":** Issued to the order of the issuing or nominated bank, giving the bank direct control over title. The most bank-preferred structure under LC transactions. - **"Consigned to [Named Party]":** A straight (non-negotiable) B/L. Acceptable only when the LC explicitly authorizes a straight B/L, otherwise it may not provide adequate security to the bank. The notify party (typically the applicant or their customs broker) must match the LC requirement exactly. A notify party named differently from the LC applicant, even a minor discrepancy, creates a discrepancy. ### 3. Port of loading and port of discharge Under **UCP 600 Article 20(a)(iv)**, the B/L must show the port of loading and port of discharge as stated in the LC. There is no tolerance for geographic substitution: - If the LC states "Port of Loading: Houston, TX, USA," a B/L showing "Bayport Terminal, Texas" is a discrepancy unless both refer to the same port in a manner that an examining bank will accept, which they typically will not without additional documentation. - If the LC states a named airport for air freight but the exporter shifts to ocean freight for cost reasons, the B/L cannot satisfy the LC requirement for an air waybill, and vice versa. - Geographic range clauses (e.g., "any European port") in the LC give flexibility, but the B/L port must still fall demonstrably within that range. ### 4. Description of goods Under **ISBP 745 paragraph E7(a)**, a transport document may describe goods in general terms not inconsistent with the LC description. A B/L does not need to reproduce the full goods description from the LC, "20,000 MT of Chemical Bulk Cargo" is acceptable when the invoice says "Monoethylene Glycol (MEG), CAS 107-21-1, 20,000 MT", but the B/L description must not *contradict* the LC or invoice. **Common failure:** The shipping line's B/L template auto-populates the goods description from the shipper's booking note. Booking note descriptions are often abbreviated or generalized by freight operations staff who are not aware of LC requirements. Always review the draft B/L goods description field before confirming the B/L for issue. ### 5. Freight terms (Prepaid vs. collect) Freight terms on the B/L must match the Incoterms in the LC. This is a logical relationship, not just a formatting requirement: | LC Incoterms | Required B/L freight notation | Rationale | | --- | --- | --- | | FOB, FCA, EXW | Freight Collect (or "Freight Payable at Destination") | Buyer pays freight; prepaid B/L would indicate seller paid: contradiction | | CIF, CFR, CIP, CPT | Freight Prepaid | Seller pays freight; collect B/L would indicate buyer pays: contradiction | | DAP, DDP, DPU | Freight Prepaid | Seller bears all costs to destination; freight must be prepaid | Under **UCP 600 Article 20(a)(vi)**, if the LC requires "freight prepaid" evidence on the B/L, the B/L must contain a notation to that effect. A B/L that is silent on freight terms will be treated as freight collect by most banks, which may create a discrepancy if the LC requires freight prepaid evidence. ### 6. Shipped on board date The on-board notation is the most legally critical date in the entire LC document set. **UCP 600 Article 20(a)(ii)** requires a B/L to indicate that goods have been shipped on board a named vessel at the port of loading stated in the LC. This date: - Must be on or before the latest shipment date stated in the LC - Is used to calculate the presentation period (under UCP 600 Article 14(c), if not specified, 21 days from the on-board date, but not beyond LC expiry) - Must appear as an explicit on-board notation if the B/L is a received-for-shipment B/L that has been stamped on board: the stamp must show the vessel name and date **Common failure:** The B/L is issued with an "apparent" date matching the booking date, but the actual on-board notation stamp is applied days later and postdates the LC's latest shipment date. Always verify the on-board date, not just the B/L issue date. ### 7. Number of originals Under **UCP 600 Article 17(b)**, if a document requires a full set of originals, all originals must be presented. The standard ocean B/L is issued in a set of three originals ("3/3"). If the LC requires "full set of original bills of lading," all three originals must be presented to the bank. Presenting 2 of 3 is a discrepancy. If only one or two originals are issued (as is increasingly common with express B/Ls and some carrier-specific practices), the B/L face should state how many originals were issued, and the LC requirement must be satisfiable with that number. ### 8. Clean vs. claused B/L Under **UCP 600 Article 27**, banks will only accept a clean transport document, one that bears no clause or notation expressly declaring a defective condition of the goods or packaging. A "claused" B/L (also called "dirty" or "foul") that contains a notation such as "bags torn," "drums dented," "short-shipped: 5 drums missing," or "cargo received in apparent poor condition" will be refused regardless of all other complying aspects. **Prevention:** Inspect all packaging before the shipping line's receipt inspection. Any discrepancy between the B/L cargo description and actual cargo condition will result in the shipping line inserting a clause. If a clause is unavoidable (e.g., minor packaging imperfection), you must obtain an LC amendment specifically allowing a claused B/L for the described defect, which buyers rarely grant, or remedy the packaging before loading. ### 9. Endorsement requirements Order B/Ls require endorsement by the shipper (beneficiary) to transfer title. If the LC requires a B/L "endorsed in blank" or "endorsed to [bank name]," the original B/L must bear a valid endorsement on the reverse. Endorsement failures include: - Endorsement signed by a party other than the shipper named on the B/L face - Rubber-stamp endorsement without a wet ink signature where a signed endorsement is required - Conditional endorsement ("endorsed in favor of X, for collection only") when a blank or unconditional endorsement is required - Missing endorsement entirely on an order B/L ## Step-by-step matching process ### Step 1: extract LC requirements before booking Before engaging your freight forwarder or shipping line, extract the following from the LC and create a B/L instruction sheet: - Consignee instruction ("To Order of [Bank]", "To Order", straight consignee) - Notify party name and address (copy exactly from the LC) - Port of loading and port of discharge (exact names as stated in the LC) - Latest shipment date - Freight terms (derive from Incoterms in LC) - Number of originals required - Any special clauses (e.g., "Charter Party B/L not acceptable," "Freight prepaid to appear on B/L") - Whether transhipment is allowed (UCP 600 Article 20(b) requires the B/L to show transhipment as prohibited or permitted per the LC) Send this instruction sheet to your freight forwarder with the booking and require them to obtain a draft B/L before the B/L is finalized. ### Step 2: review the draft B/L against the instruction sheet Request the draft B/L from the carrier or forwarder at least 48 hours before the shipment date (72 hours for complex shipments). Check field by field against your LC instruction sheet: - Shipper: Does it match the LC beneficiary exactly (legal entity name, not trading name)? - Consignee: Exact match to LC consignee instruction? - Notify Party: Character-for-character match? - Port of Loading / Port of Discharge: Exact match to LC? - Vessel name and voyage number: Plausible and consistent with booking confirmation? - Goods description: Not contradicting the invoice and LC? - Freight terms: Consistent with Incoterms? - Special clauses required by the LC: Present? - Transhipment notation: If the LC prohibits transhipment, does the B/L show no transhipment? ### Step 3: verify the final B/L after on-board stamp After the cargo is loaded and the shipping line applies the on-board stamp, obtain the final B/L and re-verify: - On-board date: On or before latest shipment date in the LC? - Vessel name on the on-board stamp: Matches the vessel on the B/L face? - Port of loading on the stamp: Matches the B/L and the LC? - Number of originals issued: Matches what was requested and what the LC requires? - Cleanliness: No clauses or reservations added during loading? - Endorsement: Applied correctly on the reverse of each original? ## Common B/L errors and their consequences | Error | Example | Consequence | | --- | --- | --- | | Wrong consignee | LC: "To Order of Northbridge Bank" / B/L: "To Order of Meridian Polymer Trading GmbH" | Bank loses title security; hard refusal. Amendment or new B/L required. | | Late on-board date | LC latest shipment: Sep 15 / On-board stamp: Sep 17 | Hard discrepancy. Payment delayed pending waiver; buyer must authorize acceptance. | | Freight collect on CIF shipment | LC: CIF Rotterdam / B/L: Freight Collect | Discrepancy: Incoterms require prepaid; seller clearly has not fulfilled freight obligation per LC. | | Transhipment not permitted, B/L shows transhipment | LC: "Transhipment not allowed" / B/L shows Port Klang as transhipment port | Discrepancy under UCP 600 Art. 20(b). Routing must change or LC amended. | | Claused B/L | Shipping line stamps: "5 drums leaking, received in damaged condition" | Refused under UCP 600 Art. 27. No waiver possible without LC amendment. | | Missing on-board notation on received B/L | B/L is a received-for-shipment type; no on-board stamp applied | Discrepancy under UCP 600 Art. 20(a)(ii). Carrier must apply on-board stamp before presentation. | ## What to do when you discover a B/L discrepancy Time matters. Act in the following sequence: - **Assess correctability.** Can the B/L be corrected before presentation? Shipping lines will often issue a corrected B/L (surrendering the originals) if the correction is minor and the cargo has not been released. Contact your freight forwarder immediately, within hours of discovery, not days. - **Check presentation timing.** Calculate how many days remain until LC expiry and how many days you have left within the presentation period. If the presentation period is at risk, a corrected B/L with fewer days remaining may still meet the deadline. - **Assess amendment necessity.** If the discrepancy cannot be corrected at source (e.g., the shipment was genuinely late), a formal LC amendment from the buyer/issuing bank is required. Initiate the amendment request in writing immediately, stating the specific field and the corrected value required. - **Consider presenting under reserve.** If the amendment cannot arrive before expiry, banks may accept a presentation with a signed indemnity from the presenter (presentation "under reserve" or "under protest"), acknowledging the discrepancy and accepting liability if the issuing bank ultimately refuses. This is a last resort and transfers risk back to the exporter. - **Document everything.** Keep records of when the discrepancy was discovered, what communications were sent to the freight forwarder and buyer, and what remediation was taken. This documentation is essential if the dispute escalates. ## House B/L vs. master B/L: LC considerations When a freight forwarder acts as a consolidating carrier (NVOCC), they issue a House B/L to the shipper while the actual ocean carrier issues a Master B/L to the forwarder. From an LC perspective: - **The LC will typically specify "Ocean Bill of Lading" or "Marine Bill of Lading."** A House B/L issued by a freight forwarder (NVOCC) is acceptable under **UCP 600 Article 20** only if the NVOCC is acting as a carrier, i.e., the House B/L is issued on the carrier's behalf or the NVOCC is identified as the carrier. A House B/L issued "as agent" rather than "as carrier" will be refused. - **"Freight Forwarder's B/L" is not acceptable** unless the LC explicitly permits it. Banks examine whether the B/L is issued by or on behalf of a carrier, not an agent. - **Master B/L is generally not required** under the LC: the House B/L from the NVOCC-as-carrier is sufficient if it meets all other UCP 600 Article 20 requirements. - **FIATA FBL (Forwarder's Bill of Lading):** Acceptable under UCP 600 only if the LC explicitly allows it or if the FIATA FBL is presented as a multimodal transport document under UCP 600 Articles 19–21 and satisfies the applicable article's requirements. ## How Loamist cross-references your B/L against LC terms automatically Loamist automates the B/L-to-LC matching process, checking shipper name, consignee, notify party, port pair, freight terms, on-board date against latest shipment date, transhipment permissions, and endorsement requirements in a single pass. Discrepancies are surfaced with the specific UCP 600 article reference so your team knows the precise rule at issue, not just a vague flag. Export coordinators using Loamist catch B/L discrepancies before the documents leave their desk, eliminating the most expensive category of LC refusal. [See a live demo](https://www.loamist.com/contact.html) to watch Loamist validate a full B/L set against real LC terms in under three minutes. ### Automate your LC checks Loamist validates export LCs and documents in under 3 minutes, catching discrepancies before bank presentation. [Check your LC, free](https://www.loamist.com/lc-check.html) [Schedule a demo](https://www.loamist.com/contact.html) Related guides ## Keep reading. [Guide · 7 min read How to review an export letter of credit before shipment Read guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) [Checklist · 8 min read The complete export LC document checklist: prevent discrepancies before bank presentation Read guide](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) [Guide · 9 min read Top 10 letter of credit discrepancies and how to prevent each one Read guide](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html) --- URL: https://www.loamist.com/chemical-export-documentation-reach-tsca-ghs-lc.html # Chemical Export Documents for LCs: REACH, TSCA, GHS | Loamist > How to align REACH, TSCA, CEPA, CSCL, and GHS regulatory documents with LC requirements. Practical guidance for chemical export compliance teams. Source: https://www.loamist.com/chemical-export-documentation-reach-tsca-ghs-lc.html Guide · Chemical exports [Back to guides](https://www.loamist.com/resources.html) # Chemical export documentation guide: aligning REACH, TSCA, CEPA, CSCL, and GHS with letter of credit requirements How to align REACH, TSCA, CEPA, CSCL, and GHS regulatory documents with LC requirements. Practical guidance for chemical export compliance teams. Published 25 March 2026 10 min read ## The unique documentation challenge for chemical exporters Chemical companies operate at a difficult intersection: every shipment must satisfy both the regulatory requirements of the importing country and the documentary requirements of the issuing bank's letter of credit. These two systems were designed independently and do not speak the same language. A Safety Data Sheet prepared under GHS Rev. 9 uses IUPAC nomenclature; an LC may describe the same substance by its commercial trade name. A TSCA export notification references an EPA inventory accession number; the LC references only a goods description negotiated in a sales contract. The consequence of misalignment is two-fold: regulatory non-compliance (which can halt the shipment at customs, trigger fines, or void the export license) and LC discrepancies (which can delay payment by weeks or cause outright refusal). Unlike most exporters, chemical companies can suffer *both* in the same transaction. This guide maps each major regulatory framework to its LC documentation touchpoints, identifies the common failure modes, and provides a working alignment checklist your export team can apply to every chemical shipment. ## Regulatory frameworks: what each requires at export ### REACH (EU): Regulation (EC) No 1907/2006 REACH (Registration, Evaluation, Authorisation and Restriction of Chemicals) governs chemical substances manufactured in or imported into the European Economic Area. For chemical exporters shipping *to* the EU, the key obligations are: #### Registration Substances exported to EU importers in quantities of 1 tonne per year or more must be registered with ECHA (European Chemicals Agency) by the EU importer (known as the "Only Representative" arrangement for non-EU manufacturers, under REACH Article 8). While the registration obligation falls on the EU side, exporters are frequently required to provide registration data, particularly the REACH registration number, on the commercial invoice or in an attached declaration. If your LC requires a REACH registration number, obtain the current registration number from your EU importer or Only Representative and validate it against the ECHA dissemination portal before finalizing documents. #### Safety data sheets (SDS) Under REACH Article 31 and Annex II (as updated by Commission Regulation (EU) 2020/878), suppliers must provide a 16-section SDS in the official language(s) of the EU member state(s) of destination. Many LCs, particularly from EU buyers, require the SDS as a mandatory LC document. When this is the case: - The substance identification in SDS Section 1 (product identifier, CAS number, EC/List number, REACH registration number) must correspond to the goods description on the commercial invoice - The SDS must be dated and bear the supplier's name and address as the issuing entity; this must match the LC beneficiary if the SDS is issued by the exporting company - ISBP 745 paragraph B8 notes that if a document is required but its issuer is not specified in the LC, any entity may issue it, but the content must satisfy LC requirements; if the LC says "Supplier's SDS," the document must be issued by the beneficiary #### Authorisation and restriction Substances on REACH Annex XIV (Authorisation List) or Annex XVII (Restrictions) require authorisation or are subject to use/import restrictions. If your substance appears on either annex, the EU importer's authorisation reference number may be required on the import entry and may need to appear in the supporting documentation bundle. Check ECHA's REACH Authorisation List before every shipment of SVHCs (Substances of Very High Concern). ### TSCA (US): Toxic Substances Control Act, 15 U.S.C. §2601 et seq. TSCA governs chemical substances in US commerce. For US-based chemical exporters, two TSCA provisions directly affect export documentation: #### TSCA inventory status Substances must be listed on the TSCA Chemical Substance Inventory to be manufactured or imported into the US. For exporters, the inventory status matters because if a substance is *not* on the inventory, its export may trigger PMN (Pre-Manufacture Notification) obligations for the receiving US importer if they plan to re-import. More practically, if your LC requires a TSCA compliance certificate or inventory status letter, the substance's EPA accession number on that certificate must match the substance identified in the commercial invoice. #### TSCA Section 12(b) export notifications Under TSCA Section 12(b) and 40 CFR Part 707, US exporters must notify EPA before exporting substances that are subject to: - A final or proposed TSCA Section 4 test rule - A TSCA Section 5 order (Significant New Use Rules, SNURs) - A TSCA Section 6 action (risk management rule) - A TSCA Section 7 court order The first export notification in any calendar year triggers a reporting obligation. EPA must be notified at least 30 days before export, and the notice must include the chemical identity, quantity, destination country, and exporter information. The export notification receipt (EPA Form 7710-56) is sometimes required as a supporting document under an LC. If your LC requires proof of TSCA compliance, confirm whether a Section 12(b) notification is applicable; if it is, the notice must be on file before the shipment date and its details must align with the LC-described shipment. #### TSCA Section 13 import certification While Section 13 applies to US importers, US exporters should be aware that foreign buyers may request a TSCA certification letter confirming that the exported substance is not in violation of TSCA. This is distinct from an export notification and is often required by sophisticated buyers as a condition of the sales contract, which then flows into the LC document list as a "TSCA compliance certificate" or "TSCA letter." ### CEPA (Canada): Canadian Environmental Protection Act, 1999, S.C. 1999, c. 33 Canada's CEPA governs the assessment and management of chemical substances. For chemical exporters shipping into Canada, the critical documentation framework is the **Domestic Substances List (DSL)** and **Non-Domestic Substances List (NDSL)**. #### DSL/NDSL status Substances on the DSL may be imported into Canada without pre-notification. Substances not on the DSL but present on the NDSL may be imported subject to reporting requirements under the New Substances Notification Regulations (NSN Regs). Substances on neither list require a full New Substance Notification (NSN) before import. If your LC involves a Canadian buyer and requires a CEPA compliance declaration, the exporter typically provides a letter confirming the substance is listed on the DSL (or NDSL with the applicable SIN number) and is not subject to prohibitions under CEPA Schedule 1 (List of Toxic Substances). This letter must identify the substance by the same name, CAS number, and description as the commercial invoice: a mismatch creates both a regulatory and an LC discrepancy. #### Export of prohibited or restricted substances Under CEPA Part 5, certain substances controlled under international agreements (Rotterdam Convention, Stockholm Convention) require an export notification to Environment and Climate Change Canada (ECCC) at least 30 days before export. The notification reference number is sometimes required on the export permit and may appear as a required document in the LC. ### CSCL (China): Chemical Substance Control Law, Order No. 7 (2020) China's Measures for the Environmental Management of New Chemical Substances (Order No. 7 of the Ministry of Ecology and Environment, effective January 2021) replaced the previous Order No. 7 of 2010. For exporters shipping chemical substances *to* China: #### IECSC: Inventory of Existing Chemical Substances in China Substances on China's IECSC (Inventory of Existing Chemical Substances Produced or Imported in China) may be imported without registration. Substances not listed require a New Chemical Substance (NCS) registration from MEE (Ministry of Ecology and Environment) before import. Chinese buyers frequently request an IECSC confirmation letter or MEE registration certificate as a pre-shipment document, which may then appear as a required document in the LC. The IECSC search is conducted through MEE's official chemical substance database. The substance identity used in the IECSC lookup (CAS number, IUPAC name, molecular formula) must be consistent with the commercial invoice description: a discrepancy between the registered name and the invoice name can cause the document to fail both Chinese customs clearance and LC compliance checks simultaneously. ### GHS: Globally Harmonized System of Classification and Labelling of Chemicals GHS is not a single regulation but a UN framework ("Purple Book," 10th revised edition as of 2023) that individual jurisdictions implement via their own legislation. The EU implements GHS through the CLP Regulation (EC) No 1272/2008; the US through OSHA's Hazard Communication Standard (29 CFR 1910.1200, revised 2012 and 2024); Canada through WHMIS 2015; China through GB/T 17519 and GB 13690. #### SDS format requirements A GHS-compliant SDS must follow the 16-section format and include, at minimum: - **Section 1:** Chemical identifier (substance name, CAS No., EC No., REACH registration number if applicable), supplier details - **Section 2:** Hazard classification and labelling elements (signal word, hazard statements, precautionary statements per GHS revision applicable to the jurisdiction) - **Section 3:** Composition/information on ingredients (CAS numbers, weight percentages for mixtures) - **Section 14:** Transport information (UN number, proper shipping name, hazard class, packing group, environmental hazards, EMS) When an SDS is a required LC document, the version presented must be current (within the last 3 years in most jurisdictions, or as otherwise specified by the LC) and prepared in the language required by the LC. A Section 1 identifier that contradicts the invoice goods description is a discrepancy regardless of its regulatory compliance. ## How regulatory documents interact with LC requirements The following diagram describes the four interaction points where regulatory compliance and LC compliance can conflict: - **Substance identity:** The chemical name, CAS number, and specification used in the regulatory certificate must correspond to the LC goods description. IUPAC names, common names, and trade names must be reconciled. - **Document issuer:** Regulatory certificates issued by a government body, notified body, or inspection agency must be issued to the party the LC specifies. If the LC requires "Beneficiary's TSCA Certificate," a certificate issued by the US importer will not satisfy the requirement. - **Dates:** Regulatory certificates must be valid at the date of LC presentation. Pre-dated certificates that have expired, or post-dated certificates issued after the presentation date, may be refused. Some LCs specify certificate validity windows (e.g., "SDS issued within 12 months of shipment date"). - **Language and format:** Regulatory certificates prepared in a language not specified or accepted by the LC must be accompanied by a certified translation if the LC requires it. Banks do not translate documents; they compare what is presented against what is required. ## Common failures: regulatory certificate mismatching LC description | Failure mode | Example | Result | | --- | --- | --- | | Trade name on invoice, IUPAC name on SDS | Invoice: "Glacial Acetic Acid, 99.8%" / SDS Section 1: "Ethanoic acid, CAS 64-19-7" | Bank queries inconsistency; not a hard discrepancy under ISBP 745 if CAS matches, but creates examination delay | | TSCA cert describes different purity grade | Invoice: "Sulfuric Acid 98% Technical Grade" / TSCA letter: "Sulfuric Acid 93%" | Discrepancy: documents conflict; bank refuses under UCP 600 Art. 14(d) | | REACH registration number missing when required | LC field 46A requires "Invoice showing REACH Reg. No."; invoice omits the number | Invoice discrepancy; requires amendment or re-issue of invoice | | Expired SDS presented | LC: "Current SDS"; SDS is dated 4 years prior | Discrepancy if "current" is defined in the LC or by jurisdiction standard (EU: 3 years); bank may refuse | | CSCL IECSC confirmation uses different CAS number | Invoice: CAS 7647-01-0 (Hydrochloric acid) / IECSC letter: CAS 7664-93-9 (incorrect: that is sulfuric acid) | Hard conflict between documents; regulatory non-compliance AND LC discrepancy | ## Document alignment checklist for chemical shipments Apply this checklist to every chemical LC presentation before submitting to the bank: - **Extract the "anchor" substance description** from LC field 45A. Note: chemical name(s), CAS number(s), purity/grade, HS code if specified. - **Verify SDS Section 1** substance identity (product name, CAS No., EC No.) corresponds to the LC anchor description. Any synonym or trade name used in the invoice should appear in SDS Section 1 or be cross-referenced. - **Check REACH registration number** against ECHA dissemination portal if an EU destination is involved and the number is required. Confirm the registrant matches your company or your EU Only Representative. - **Confirm TSCA inventory status** via EPA's TSCA Chemical Substance Inventory if shipping from the US. Prepare and retain the Section 12(b) notification receipt if applicable; include it in the LC document bundle if required. - **Verify DSL/NDSL status** for Canadian destinations. If not on DSL, confirm NSN filing status and include the notification reference number in any CEPA compliance declaration. - **Confirm IECSC listing** for Chinese destinations. If not listed, verify MEE NCS registration status and obtain the registration certificate for inclusion. - **Check GHS SDS version currency:** Is the SDS within the validity period required by the LC or by the destination country's regulation? Is it in the correct language? - **Cross-check UN number and proper shipping name** on the Dangerous Goods Declaration (DGD) against SDS Section 14. Confirm they match the goods description on the commercial invoice. - **Verify issuing entity** on each regulatory document matches what the LC specifies (beneficiary, seller, supplier, etc.). - **Check dates:** All regulatory certificates must be issued before the presentation date, must not be post-dated relative to the shipment date, and must be within any validity window specified in the LC. ## Special considerations: hazardous cargo and DG declarations For chemicals classified as dangerous goods under IMDG (sea), IATA DGR (air), or ADR/RID (road/rail), the Dangerous Goods Declaration (DGD) is frequently a required LC document. The DGD must comply with the applicable transport regulation's format requirements and must be signed by a certified dangerous goods signatory. From an LC perspective: - The DGD proper shipping name and UN number must be consistent with SDS Section 14 and the commercial invoice description - The shipper named on the DGD must be the LC beneficiary (or consistent with the shipper identified in the LC if specified) - The DGD packing group and hazard class must match the GHS classification in SDS Section 2; inconsistencies signal a documentation integrity problem - The quantity on the DGD (gross weight per package, total net quantity) must reconcile with the commercial invoice and packing list Some LCs for controlled substances (precursor chemicals, dual-use items) also require export authorization documents issued by the national export licensing authority. In the US, this is the Bureau of Industry and Security (BIS) Export Control Classification Number (ECCN) determination letter or an actual Export License (EAR99 designation letter) under 15 CFR Parts 730–774. If required by the LC, these documents must be current, applicable to the specific shipment, and identify the substance in a manner consistent with the invoice. ## How Loamist validates regulatory documentation alignment Loamist automates the cross-document consistency check between regulatory certificates (SDS, TSCA letters, REACH declarations, CEPA compliance confirmations) and your LC requirements, flagging substance name discrepancies, expired certificates, missing registration numbers, and issuer mismatches before your documents reach the bank. For chemical exporters managing REACH, TSCA, CEPA, and GHS compliance across multiple concurrent shipments, Loamist eliminates the manual reconciliation step that creates both LC discrepancies and regulatory risk. [Book a demo](https://www.loamist.com/contact.html) to see how Loamist handles your specific chemical export document stack. ### Automate your LC checks Loamist validates export LCs and documents in under 3 minutes, catching discrepancies before bank presentation. [Check your LC, free](https://www.loamist.com/lc-check.html) [Schedule a demo](https://www.loamist.com/contact.html) Related guides ## Keep reading. [Guide · 7 min read How to review an export letter of credit before shipment Read guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) [Checklist · 8 min read The complete export LC document checklist: prevent discrepancies before bank presentation Read guide](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) [Guide · 9 min read Top 10 letter of credit discrepancies and how to prevent each one Read guide](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html) --- URL: https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html # LC-Compliant Commercial Invoice: UCP 600 Guide | Loamist > Prepare an LC-compliant commercial invoice correctly. Covers UCP 600 Art. 18 required fields, discrepancy examples, and chemical export considerations. Source: https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html Guide · Commercial invoice [Back to guides](https://www.loamist.com/resources.html) # How to prepare a compliant commercial invoice under a letter of credit Prepare an LC-compliant commercial invoice correctly. Covers UCP 600 Art. 18 required fields, discrepancy examples, and chemical export considerations. Published 25 March 2026 8 min read ## Why the commercial invoice is the most-rejected LC document Of all the documents presented under a letter of credit, the commercial invoice generates the highest rate of discrepancies. ICC Banking Commission surveys consistently show that invoice errors account for 30–40% of all first-presentation refusals. The reason is structural: the invoice is the anchor document against which banks cross-check every other paper in the package. If the invoice is wrong, the entire presentation unravels. Under **UCP 600 Article 18**, a commercial invoice must be made out in the name of the applicant, issued by the beneficiary, and must describe the goods, services, or performance in a way that corresponds to the description in the LC. Banks do not apply a "close enough" standard: any deviation that a bank determines to be a discrepancy entitles it to refuse the documents and withhold payment under UCP 600 Article 16. The stakes are concrete. A rejected first presentation typically costs 5–10 business days of delay, bank re-examination fees of $150–$500 per re-presentation, and, in worst-case scenarios, missed payment deadlines that push settlement past the LC expiry date entirely. ## Required fields for LC invoice compliance The following fields must appear on the commercial invoice and must align precisely with the LC terms. Work through these in order before finalizing any invoice draft. ### 1. Beneficiary name and address Your company name and address on the invoice must be an exact character-for-character match with the beneficiary field in the LC. This is not a judgment call; it is a mechanical comparison. Common failure modes include: - Using a trading name instead of the registered legal entity name stated in the LC (e.g., "Kestrel Chemicals" vs. "Kestrel Industries Ltd.") - Abbreviating a state or province that the LC spells out in full ("ON" vs. "Ontario") - Including a suite number the LC omits, or omitting one the LC includes - Using a comma or period that differs from the LC format **ISBP 745 paragraph A18** clarifies that an address of the beneficiary need not be the same as the one stated in the LC, provided it is in the same country. However, when the LC specifies an address, exact conformity is safest practice; deviations invite refusal even when technically debatable. ### 2. Applicant details The invoice must be addressed to the applicant (the buyer / importer). Under UCP 600 Article 18(a)(ii), the invoice must be made out in the name of the applicant. Use the exact applicant name as it appears in the LC field 50 (Applicant). Do not substitute a parent company, affiliate, or abbreviated name without a corresponding LC amendment. ### 3. Description of goods This is the most litigated field in invoice disputes. UCP 600 Article 18(c) states: "The description of the goods, services or performance in a commercial invoice must correspond with that appearing in the credit." The word *correspond* is critical: it does not mean identical verbatim, but it does mean no contradictions, no material omissions, and no additions that create ambiguity. Practical rules: - Copy the exact goods description from LC field 45A into your invoice template as the baseline - You may add technical or commercial detail that does not conflict with the LC description - Do not include goods not covered by the LC on the same invoice - Do not use a trade name if the LC specifies a chemical name, or vice versa, unless the LC explicitly allows both **Example discrepancy:** An LC for "Polyethylene Terephthalate (PET) Resin, virgin grade, CAS 25038-59-9" was presented with an invoice describing "PET Resin, Industrial Grade." The bank refused on the grounds that "industrial grade" was not equivalent to "virgin grade" and the CAS number was absent. Re-presentation delay: 8 business days. ### 4. Quantity, unit price, total amount, and currency All four elements must reconcile precisely: - **Quantity:** Must not exceed the LC-stated quantity unless the LC or UCP 600 Article 30 tolerances apply (±5% for bulk goods unless the LC states otherwise). For packaged goods with a stated unit count, there is zero tolerance. - **Unit price:** Must match the contract price reflected in the LC. If the LC states a unit price cap, the invoice must not exceed it. - **Total amount:** Must not exceed the LC credit amount. Under UCP 600 Article 18(b), a bank will refuse an invoice that exceeds the LC value even if a partial drawing is permitted. - **Currency:** Must exactly match the LC currency code. USD and US$ are technically the same but some banks flag the difference; use the ISO 4217 code (USD, EUR, GBP) that appears in the LC. ### 5. Incoterms The Incoterms rule on the invoice must match the LC exactly, including the year version. "FOB Shanghai" and "FOB Shanghai (Incoterms 2020)" are different; if the LC specifies a year, include it. Mismatched Incoterms create a discrepancy because they imply different risk-transfer and freight-responsibility obligations, which affects the consistency test across the invoice and transport document. ### 6. LC reference number Always quote the LC number (field 20 of the SWIFT MT700) on the invoice. While UCP 600 does not explicitly mandate this, ISBP 745 paragraph A29 notes that the LC number must appear on the invoice in many LCs as an explicit requirement. Even when not required, its absence creates unnecessary cross-referencing difficulty for the examining bank and may trigger a query. ### 7. Marks and numbers If the LC or the packing list references shipping marks, those marks must appear consistently on the invoice, packing list, and transport documents. Under ISBP 745, shipping marks on the invoice need not be identical to those on the B/L, but any marks shown must not conflict. A zero-marks invoice is acceptable if no marks are required, but if you show marks, they must be consistent throughout the document set. ### 8. Country of origin Many LCs require the invoice to state the country of origin. If required, the origin declared on the invoice must match any Certificate of Origin presented. Origin statements such as "Made in USA" are acceptable; formal preferential origin declarations should be left to the Certificate of Origin unless the LC specifically requires the statement on the invoice face. ## Common invoice discrepancies with examples | Discrepancy type | Real example | Consequence | | --- | --- | --- | | Goods description mismatch | LC: "Sodium Hydroxide Flakes, 98% min purity" / Invoice: "Caustic Soda Flakes" | Refused: common name ≠ chemical name without LC authorization | | Amount exceeds LC value | Invoice total USD 502,000 against LC ceiling of USD 500,000 | Refused under UCP 600 Art. 18(b); requires amendment or reduced invoice | | Beneficiary name abbreviated | LC: "Kestrel Industries GmbH" / Invoice: "Kestrel GmbH" | Discrepancy: legal form suffix matters | | Missing LC reference | Invoice omits LC number when LC field 46A requires it | Minor but citable discrepancy; bank may query or refuse | | Incoterms year mismatch | LC: "CIF Hamburg Incoterms 2020" / Invoice: "CIF Hamburg Incoterms 2010" | Discrepancy: different liability regime | | Quantity tolerance exceeded | LC: 500 MT; Invoice: 512 MT (2.4% over), but goods are bagged, not bulk | Refused: 5% tolerance under Art. 30(b) applies only to credit amount and quantity in bulk; packaged goods have zero tolerance | ## Invoice vs. other documents: consistency rules Under ISBP 745 and UCP 600 Article 14(d), data in a document need not be identical to but must not conflict with data in any other document. For the commercial invoice, this means performing cross-checks against: - **Bill of Lading:** Shipper name, description of goods (need not be identical to LC description, B/L can use a general description, but must not contradict the invoice), port of loading, and vessel name should be consistent where both documents show the detail. - **Packing List:** Total quantity, number of packages, net/gross weights, and marks must reconcile with the invoice line items. - **Certificate of Origin:** Consignee details and country of origin must align. - **Insurance Certificate:** Insured amount, goods description, and voyage route must be consistent with the invoice. - **Inspection Certificate:** If the inspection certificate references a specific quantity or quality specification, it must not contradict what the invoice states. The safest workflow is to prepare the invoice first (as the anchor document) and then populate all other documents from the invoice, rather than preparing each document independently and hoping they reconcile. ## Special considerations for chemical exports Chemical exporters face additional invoice requirements that sit at the intersection of trade finance and regulatory compliance: ### HS codes Many LCs for chemical shipments require the Harmonized System (HS) code to appear on the invoice. If an HS code is required, it must be the correct 6-digit international code (or extended national code as required by the importing country). An incorrect HS code on the invoice may not only create an LC discrepancy; it can trigger customs delays, anti-dumping duty issues, or import licensing problems in the destination country. Cross-check the HS code against the goods description every time, as a single transposition (e.g., 2905.11 vs. 2905.12 for methanol vs. ethanol) can have significant consequences. ### REACH references When shipping chemical substances to EU buyers under an LC, the invoice frequently needs to either incorporate or align with REACH registration data. Some LC terms require the invoice to reference the REACH registration number (EC/REACH No.) for the substance. If your LC includes such a requirement, the registration number on the invoice must match your REACH dossier exactly. A mismatch, or absence of the number when required, constitutes an invoice discrepancy independent of any regulatory consequence. Additionally, where a Safety Data Sheet (SDS) is a required LC document, the substance identification data on the SDS (CAS number, IUPAC name, EC number) should mirror the goods description on the invoice. Inconsistencies between the SDS header and the invoice description are a common source of bank queries on chemical presentations. ### Dangerous goods notation For hazardous chemicals subject to IMDG, ADR, or IATA dangerous goods regulations, some LCs require the invoice to reference the UN number, proper shipping name, hazard class, and packing group. If your LC requires this, place it in a clearly labeled section of the invoice, typically below the goods description line, and ensure it matches the Dangerous Goods Declaration or MSDS presented alongside. ## Template and format recommendations Format discipline prevents discrepancies before they start: - **Create a per-LC invoice template.** When an LC is received, extract the beneficiary name, applicant name, goods description, currency, and Incoterms from the LC directly and lock them into a template. Do not rely on retyping these fields from memory. - **Use a four-eyes check.** One person prepares; a second person performs a character-by-character comparison of the invoice against LC fields 46A (Documents Required), 45A (Description of Goods), and the applicant/beneficiary fields. Do not skip this step under deadline pressure: that is exactly when errors occur. - **Version-control your invoice drafts.** If an LC amendment is issued after you have begun invoice preparation, explicitly update your template. Presentations against amended LCs using pre-amendment invoice templates are a common and avoidable error. - **Avoid auto-populated fields from ERP systems without validation.** ERP master data for customer names, addresses, and goods descriptions may not exactly match LC wording. Never trust an ERP output for LC compliance without a manual comparison to the LC text. ## How Loamist automates invoice compliance checks Loamist automates the field-by-field comparison of your commercial invoice against the LC, checking beneficiary name, applicant, goods description, currency, Incoterms, quantity tolerances, and 30+ additional data points in under three minutes. When a mismatch is detected, Loamist flags it with the specific UCP 600 article or ISBP 745 paragraph that applies, so your team knows exactly what to fix before bank presentation. Export teams using Loamist reduce commercial invoice discrepancies by over 85% on first presentation, eliminating re-examination fees and payment delays. [Request a demo](https://www.loamist.com/contact.html) to see how Loamist validates your invoice stack against live LC terms. ### Automate your LC checks Loamist validates export LCs and documents in under 3 minutes, catching discrepancies before bank presentation. [Check your LC, free](https://www.loamist.com/lc-check.html) [Schedule a demo](https://www.loamist.com/contact.html) Related guides ## Keep reading. [Guide · 7 min read How to review an export letter of credit before shipment Read guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) [Checklist · 8 min read The complete export LC document checklist: prevent discrepancies before bank presentation Read guide](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) [Guide · 9 min read Top 10 letter of credit discrepancies and how to prevent each one Read guide](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html) --- URL: https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html # Export LC Document Checklist: Prevent Discrepancies | Loamist > A master LC document checklist covering commercial invoice, B/L, packing list, certificate of origin, insurance, and inspection documents. UCP 600 aligned. Source: https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html Checklist · Document set [Back to guides](https://www.loamist.com/resources.html) # The complete export LC document checklist: prevent discrepancies before bank presentation A master LC document checklist covering commercial invoice, B/L, packing list, certificate of origin, insurance, and inspection documents. UCP 600 aligned. Published 28 March 2026 8 min read A documentary credit presentation is not graded on a curve. Banks examine documents strictly on their face, against the precise terms of the LC, with no allowance for good intent or commercial context. Under UCP 600 Article 14(a), the standard is compliance on the face of the documents, and compliance is binary. One missing signature, one weight discrepancy, one invoice line that does not correspond to the LC goods description: any of these is sufficient for a bank to refuse payment on a first presentation. The data on first-presentation discrepancy rates is sobering. ICC Banking Commission surveys have consistently placed them between 60% and 70% for many years. Institutions that implement systematic pre-presentation review protocols, however, report rejection rates closer to 25–35%. The difference is almost entirely process: specifically, whether a structured checklist is applied to every document set before submission. This checklist is designed for documentation clerks and export coordinators who prepare LC presentations. It covers the six core document types required in the majority of documentary credit presentations, organized as a working checklist you can apply document by document, followed by cross-document and timing checks. ## Before you start: gather your reference documents Before checking any individual document, have the following on your desk: - The original LC (or the most recent amendment, if amendments have been issued) - All previous presentation documents, if this is a partial shipment drawing - Your freight forwarder's confirmed B/L draft - The final commercial invoice and packing list - Any regulatory certificates required (SDS, inspection certificates, phytosanitary) Work from the LC, not from the sales contract, not from a previous shipment's documents. The LC is the controlling document for this presentation. ## Commercial invoice checklist | Check item | UCP 600 reference | Notes | | --- | --- | --- | | Beneficiary name matches LC exactly | Art. 14(j) | Abbreviations, punctuation, and capitalization must be identical | | Beneficiary address matches LC | Art. 14(j) | Additional contact details are permitted if address matches | | Applicant name and address present | Art. 18(a)(ii) | Must appear on invoice; need not match LC exactly per ISBP 745 para. C5 | | LC reference number included | Best practice | Not strictly required but expected by most issuing banks | | Goods description corresponds to LC | Art. 18(c) | Must not conflict: does not need to be word-for-word identical on other docs | | Currency matches LC | Art. 18(a)(iii) | USD vs. US$ vs. U.S. Dollars: confirm bank's acceptable notation | | Invoice amount does not exceed LC amount | Art. 18(b) | Partial drawings permitted if LC allows; amount must not exceed LC value | | Quantity matches B/L and packing list | Art. 14(d) | Cross-document consistency requirement | | Unit price present and consistent with total | Best practice | Some LCs specify unit price; verify arithmetic | | Incoterms rule and named place match LC | Art. 14(d) | e.g., "CIF Rotterdam" not just "CIF": named place is required | | Invoice is signed if LC requires signature | Art. 18(a) | Many LCs require "signed commercial invoice"; verify requirement | | Invoice date is not later than presentation date | Art. 14(i) | Invoice may be pre-dated but not post-dated relative to presentation | ## Bill of lading checklist | Check item | UCP 600 reference | Notes | | --- | --- | --- | | Shipper name matches LC beneficiary (or as specified) | Art. 20(a)(i) | Some LCs specify the shipper must be a named third party | | Consignee field matches LC instruction | Art. 20(a)(i) | "To order," "to order of issuing bank," or named party: must match LC exactly | | Notify party matches LC | Art. 20(a)(i) | Often the applicant; additional notify parties are generally acceptable | | Port of loading matches LC | Art. 20(a)(ii) | No abbreviations that differ from LC: "CNSHA" vs. "Shanghai" if LC specifies the full name | | Port of discharge matches LC | Art. 20(a)(ii) | Including any named terminal if LC specifies one | | On-board notation present with date | Art. 20(a)(ii) | "Shipped on board" stamp with vessel name and date; received-for-shipment B/L not acceptable unless LC permits | | Shipped on board date is on or before LC's latest shipment date | Art. 20(a)(ii) | This is the shipment date; the invoice date is irrelevant for this check | | Freight terms (prepaid/collect) match LC Incoterms | Art. 20(a)(v) | CIF/CIP/CPT/CFR = freight prepaid; FOB/FCA/EXW = freight collect or as agreed | | B/L is clean (no adverse clauses) | Art. 27 | Claused B/L (e.g., "packaging defective") is a discrepancy unless LC expressly accepts it | | Number of originals stated and presented as required | Art. 20(a)(iv) | LC will specify "full set" (typically 3/3) or a specific number | ## Packing list checklist | Check item | Notes | | --- | --- | | Beneficiary name matches LC (and invoice) | Consistency with commercial invoice required | | Applicant name present | Standard field; must not conflict with LC | | Goods description not inconsistent with LC | Need not mirror invoice exactly, but must not conflict | | Total gross and net weights match B/L | Weight discrepancies between packing list and B/L are a common rejection cause | | Number of packages matches B/L and invoice | Cross-document consistency; even minor differences ("12 drums" vs. "12 x 200L drums") can be flagged | | Marks and numbers match invoice | LC sometimes specifies required shipping marks; verify | | Measurements (if required) consistent with other docs | Some LCs or commodity types require cubic measurement | | Signed if LC requires signature | Less common for packing lists but verify LC requirement | ## Certificate of origin checklist | Check item | Notes | | --- | --- | | Issuing body matches LC requirement | LC may specify "Chamber of Commerce" or a specific body; verify it matches exactly | | Country of origin stated matches LC expectation | Important for preferential tariff schemes (EUR.1, Form A, GSP) | | Goods description not inconsistent with LC and invoice | Abbreviated descriptions acceptable if not conflicting | | Consignee/importer details match LC if required | Some CO formats include buyer details; verify against LC | | Certificate is certified/stamped by issuing body | An uncertified draft is not an acceptable document | | Date of certificate is consistent with shipment date | CO issued after shipment date requires explanation; some banks flag this | ## Insurance document checklist Insurance documents are only required when the LC's Incoterms place insurance responsibility on the seller (CIF, CIP). If the LC is FOB or CFR, skip this section, but note that presenting an unsolicited insurance document can still cause problems if it contains conflicting information. | Check item | UCP 600 reference | Notes | | --- | --- | --- | | Document type matches LC (policy vs. certificate) | Art. 28(a) | LC should specify; insurance certificate is acceptable unless LC specifically requires a policy | | Insured party is correct (typically beneficiary or bank) | Art. 28(i) | Blank endorsement acceptable if required for negotiation | | Coverage amount is at least 110% of CIF/CIP invoice value | Art. 28(f)(ii) | This is the UCP 600 minimum; LC may require higher percentage | | Currency matches invoice and LC currency | Art. 28(f)(ii) | Coverage in a different currency is a discrepancy | | Risks covered match LC requirement | Art. 28(f)(i) | LC may specify "all risks," "Institute Cargo Clauses (A)," or named perils | | Coverage period begins no later than date of shipment | Art. 28(e) | An insurance document dated after the B/L on-board date is non-compliant | | Signed or authenticated by insurer or underwriter | Art. 28(a) | A pro-forma or draft insurance document is not acceptable | ## Inspection certificate checklist | Check item | Notes | | --- | --- | | Named surveyor/inspection body matches LC | Some LCs name SGS, Bureau Veritas, Intertek, or another specific inspector; no substitution | | Goods description consistent with LC and invoice | Inspection certificate often contains detailed product specs; ensure HS code and chemical name are consistent | | Inspection date is on or before shipment date | Inspection after loading is unusual and will be questioned | | Certificate confirms the specific parameters required by LC | LC may require purity %, weight verification, or compliance with a specific standard | | Signed and stamped by authorized inspector | An unsigned certificate is not compliant; confirm title and authority of signatory | ## Cross-document consistency checks Individual document compliance is necessary but not sufficient. UCP 600 Article 14(d) requires that documents, when read together, must not be inconsistent with each other. Banks will read all documents as a set, and a conflict between two documents, even if each is internally correct, is grounds for refusal. Run these cross-document checks after completing the individual checklists: - **Goods description:** The commercial invoice description must correspond to the LC. Other documents (B/L, packing list, CO) need not match word-for-word but must not conflict. Flag any document where the goods description differs in a material way. - **Quantities and weights:** Total quantity, gross weight, and net weight must reconcile across invoice, packing list, and B/L. Even a 1 kg discrepancy in gross weight between the packing list and B/L is a discrepancy. - **Beneficiary name:** Must appear identically on all documents that reference the seller/exporter. Watch for name variants introduced by third-party certificate issuers (chambers of commerce, inspection bodies) who may abbreviate your company name. - **Port details:** Port of loading and discharge on the B/L must match any reference to port in the invoice or packing list, and must match the LC. - **Incoterms:** The Incoterms rule should be stated consistently across invoice, insurance document (if applicable), and any document that references trade terms. ## Timing checks Timing errors are among the most common, and most painful, discrepancies because they cannot be corrected retroactively. Before submitting your document set, confirm: - **Shipment date ≤ Latest shipment date in LC:** Read directly from the B/L on-board notation. If the on-board date exceeds the LC's latest shipment date by even one day, you have a discrepancy that requires a waiver from the applicant (which they may refuse). - **Presentation date ≤ Expiry date of LC:** The date you submit documents to your nominated bank must be on or before the LC expiry date. - **Presentation date ≤ Shipment date + Presentation period:** Under UCP 600 Article 14(c), documents must be presented within 21 calendar days of the date of shipment unless the LC specifies a shorter period. A short-period LC (7 or 10 days) combined with complex document requirements is a common trap. Calculate all three dates when you receive the B/L and calendar them with reminders. If the latest achievable presentation date is uncomfortably close, escalate immediately; do not absorb the risk quietly. ## Final sign-off protocol Before submitting the document set to your bank, require a formal sign-off step: - A second reviewer (not the person who prepared the documents) runs through this checklist independently. - Both reviewers sign a cover sheet confirming the checklist was completed and all items passed. - The cover sheet is filed with the presentation record for audit purposes. - If any item failed and was resolved, the resolution is documented (e.g., "B/L shipper name corrected via carrier amendment dated [date]"). The second-reviewer step is not bureaucracy; it is the single highest-value action you can take to catch the discrepancies that the preparer is too close to see. Fresh eyes catch transposition errors, weight mismatches, and signature omissions that the document preparer has normalized out of their awareness. ## Run this checklist in 3 minutes with Loamist Loamist automates every check in this document checklist, parsing commercial invoices, bills of lading, packing lists, certificates of origin, insurance documents, and inspection certificates against LC terms in under 3 minutes. The platform flags each discrepancy with the specific UCP 600 article it violates and the field where the conflict occurs, so your team can correct issues before bank submission rather than after refusal. Export documentation teams at large chemical manufacturers use Loamist to eliminate the manual checklist process entirely, reducing first-presentation discrepancy rates by up to 85%. [See how Loamist works →](https://www.loamist.com/contact.html) ### Automate your LC checks Loamist validates export LCs and documents in under 3 minutes, catching discrepancies before bank presentation. [Check your LC, free](https://www.loamist.com/lc-check.html) [Schedule a demo](https://www.loamist.com/contact.html) Related guides ## Keep reading. [Guide · 7 min read How to review an export letter of credit before shipment Read guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) [Guide · 9 min read Top 10 letter of credit discrepancies and how to prevent each one Read guide](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html) [Guide · 8 min read How to prepare a compliant commercial invoice under a letter of credit Read guide](https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html) --- URL: https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html # How to Review an Export LC Before Shipment | Loamist > A 10-point pre-shipment LC review checklist for export coordinators. Catch discrepancies before they delay payment, with UCP 600 references. Source: https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html Guide · Pre-shipment review [Back to guides](https://www.loamist.com/resources.html) # How to review an export letter of credit before shipment A 10-point pre-shipment LC review checklist for export coordinators. Catch discrepancies before they delay payment, with UCP 600 references. Published 28 March 2026 7 min read Most letter of credit discrepancies are preventable, and most of them originate not at document preparation, but at the moment the LC arrives and nobody reads it carefully. ICC Banking Commission surveys consistently show that 60–70% of first presentations under documentary credits contain at least one discrepancy. The downstream cost is significant: a single discrepancy triggers a bank refusal, typically adds 5–10 business days to collection, and can cost $200–$500 in amendment or handling fees, before accounting for the working capital impact of delayed payment. The fix is a disciplined pre-shipment LC review: a structured examination of the LC terms before you commit to a shipment schedule, book freight, or issue a single document. Done properly, this review either confirms you can comply with the LC as issued, or surfaces the specific clauses that need amendment before goods leave the warehouse. ## Why pre-shipment review is your most powerful discrepancy-prevention tool Once goods are shipped, your options narrow dramatically. A late shipment date is irreversible. Freight already booked under the wrong Incoterms can cost thousands to reroute. A bill of lading already issued with the wrong consignee name requires a carrier correction, and carriers charge for that, sometimes significantly. By contrast, an LC amendment before shipment costs far less and preserves the commercial relationship. Most applicants will agree to reasonable amendments when asked early; they become much more resistant after discovering a discrepancy at presentation, when they may have already received the goods or lost negotiating leverage. The goal of pre-shipment review is simple: identify every clause in the LC that you cannot, or might not be able to, comply with, and request amendments for all of them in a single, consolidated request. ## The 10-point pre-shipment LC checklist ### 1. Verify your beneficiary name and address exactly Under UCP 600 Article 14(j), the beneficiary's name and address as they appear in the LC must appear identically on the commercial invoice (and on other documents that reference the beneficiary). Exactly means exactly: abbreviations, punctuation, and capitalization all count. If your company trades as "KESTREL Industries Ltd." but the LC reads "Kestrel Industries Limited," every invoice and packing list you issue will carry a discrepancy. Check: Does the LC beneficiary field match your company's registered legal name precisely? If not, request an amendment immediately; this is non-negotiable. ### 2. Check the LC expiry date against your realistic shipment timeline The expiry date is the absolute deadline for document presentation at the nominated bank. Work backwards from it: subtract your bank's typical examination time (5 business days is standard under UCP 600 Article 14(b)), subtract your internal document preparation time, and subtract any transit time for original documents mailed from overseas. What remains is your latest possible shipment date in practice, not the one printed in the LC. If that calculated date is already in the past, or is tighter than your production and logistics lead time can support, the LC needs an amendment before anything else moves forward. ### 3. Confirm the latest shipment date is achievable Many LCs specify a latest shipment date independent of the expiry. This is the on-board date on the bill of lading: the moment the carrier confirms the goods were loaded aboard the vessel. Check it against your production schedule, your freight forwarder's booking windows, and port congestion at your loading port. A two-day delay at the port due to weather or a vessel schedule change can push you past the latest shipment date with no recourse. If there is any doubt, request an extension before shipment. Amendment after the latest shipment date has already passed is pointless. ### 4. Validate the goods description against your sales contract Under UCP 600 Article 18(c), the description of goods in the commercial invoice must correspond with the description in the LC. This does not mean word-for-word identical on all documents, but the invoice must be precise. Other documents (packing list, B/L, certificate of origin) may use a general description, but it must not be inconsistent with the LC description. Watch for: abbreviated product names, HS code references included in the LC description, or chemical nomenclature that differs between your sales contract and what the buyer's bank has typed into the LC. A product sold as "sodium hypochlorite solution, 12% available chlorine" cannot be invoiced as "liquid bleach" without risking rejection. ### 5. Review Incoterms alignment The Incoterms rule in the LC determines which transport documents are required, who pays freight, and whether freight must appear as "prepaid" or "collect" on the bill of lading. These are not independent choices; they cascade across your entire document set. If the LC specifies CIF Rotterdam, the B/L must show freight prepaid, and you must present an insurance policy or certificate covering the CIF value plus 10% (per UCP 600 Article 28). If the LC specifies FOB Shanghai, an insurance document is not your responsibility, but the freight must appear as collect on the B/L. Incoterms mismatches between the LC and your freight booking are among the most expensive discrepancies to fix after shipment. ### 6. Check the required document list against what you can actually obtain The LC specifies exactly which documents are required for presentation: not approximately, but exactly. Go through each document type listed and ask: Can I obtain this document, in this exact form, from the issuing party named, within the required timeframe? Common problem areas include: inspection certificates from specific named surveyors who may not operate at your port; certificates of origin requiring a specific chamber of commerce when your goods qualify for a different issuing body; phytosanitary or fumigation certificates for goods that are not subject to those requirements; and clean report of findings from pre-shipment inspection agencies in the buyer's country. ### 7. Identify soft clauses and impossible conditions A soft clause is any condition in the LC that gives the applicant (buyer) unilateral control over whether the LC can be drawn upon, essentially converting an independent bank undertaking into a dependent one. Classic examples include: "Shipment date subject to buyer's written approval," "Inspection certificate to be signed by applicant's representative," or "Documents to be countersigned by named individual at buyer's company." These clauses are not compliant with the letter of credit's purpose as an independent payment undertaking. The ICC has addressed soft clauses repeatedly in its opinions. If you see one, escalate immediately: your bank's trade finance desk should review it, and you should seek its deletion via amendment before proceeding. ### 8. Verify port of loading and port of discharge The LC specifies the port of loading and port of discharge (and sometimes a named airport, if air freight is involved). These must match the B/L exactly. If your freight forwarder books cargo through a transshipment hub, say, loading at a feeder port not named in the LC, and the B/L reflects that routing, you have a discrepancy. Check whether the LC allows transhipment; if it does not and your routing requires it, you need an amendment or a different routing. Also confirm: if you are shipping from a country where multiple major ports are options (e.g., "any Chinese port" vs. a specific named port), that the LC language is broad enough to accommodate your actual loading point. ### 9. Check partial shipments and transhipment allowances UCP 600 Article 31 governs partial shipments. If they are prohibited and your production or logistics constraints mean you may need to ship in multiple lots, you need an amendment allowing them. Similarly, Article 20(b) addresses transhipment for ocean freight. Many LCs prohibit transhipment by default, which can create problems for certain trade lanes where direct service is unavailable or impractical. Be specific when requesting amendments: "Partial shipments: permitted" and "Transhipment: permitted via any port" are the precise additions needed. ### 10. Confirm payment terms and presentation period Finally, verify the payment mechanics. Is this a sight LC or a usance (deferred payment) LC? If usance, what is the tenor: 60 days from B/L date, 90 days from sight? Confirm this matches your commercial agreement. Then check the presentation period: under UCP 600 Article 14(c), the default is 21 calendar days after the date of shipment, but this can be shortened (some LCs specify 7 or 10 days). A short presentation window combined with complex document requirements is a recipe for a late presentation discrepancy. ## Red flags that require an amendment, not a workaround Some issues discovered during pre-shipment review cannot be solved by careful document preparation. These require formal LC amendments: - **Expired or near-expired LCs**: You cannot backdate documents. If the timeline is unworkable, request an extension. - **Wrong beneficiary name**: No document can correct this; only an amendment to the LC itself. - **Soft clauses giving the applicant veto power**: Delete them or decline the transaction. - **Documents that cannot be obtained**: An inspection certificate from a non-existent surveyor in your port cannot be produced. Request a substitution. - **Incoterms conflicts with your freight contract**: If you have already committed to FOB but the LC requires CIF, an amendment is the only clean solution. ## How to request an LC amendment effectively When requesting amendments, follow these principles to maximize the chance of quick approval: - **Consolidate all requests into one message.** Every amendment round takes time, typically 3–7 business days for the buyer to instruct their bank and for the amendment to transmit through SWIFT. Multiple rounds compound the delay and irritate the buyer. Review the entire LC before sending your first request. - **Be specific and provide the exact language.** Do not say "please extend the shipment date." Say: "Please amend latest shipment date from 15 April 2026 to 30 April 2026." Ambiguous requests go back and forth. - **Explain the commercial reason briefly.** Buyers are more cooperative when they understand why: "Our production schedule requires 10 additional working days; this does not affect the commercial terms." - **Track the amendment SWIFT message (MT 707).** An amendment is not effective until you receive and accept it at your nominated bank. Do not ship until the amendment is confirmed in your bank's system. ## Build pre-shipment review into your process The most effective teams treat LC review as a formal gate in the order-to-cash process, not an afterthought. Assign a named reviewer for each LC (not just whoever is available). Log the review date, findings, and any amendments requested. Set calendar reminders for expiry dates and latest shipment dates. Keep a template checklist that mirrors the 10 points above, adapted to your typical trade lanes and document sets. For chemical and commodity exporters, add a product-specific layer: verify that the goods description in the LC is compatible with the regulatory certificates you will be required to produce (SDS, REACH registration, TSCA certification). A description mismatch between the LC and a mandatory regulatory document creates a cross-document inconsistency under UCP 600 Article 14(d), and that is a discrepancy even if each individual document is internally correct. ## Automate your pre-shipment LC review Loamist automates the pre-shipment LC analysis described in this checklist, parsing every field of the LC against your shipment profile and flagging clauses that require amendment, are unachievable, or conflict with your document set. What typically takes an experienced trade finance specialist 30–45 minutes takes Loamist under 3 minutes, with a structured discrepancy report you can send directly to your buyer. Export teams at large chemical manufacturers use Loamist to eliminate the manual review bottleneck and catch soft clauses, impossible conditions, and timeline conflicts before a single document is prepared. [See how Loamist works →](https://www.loamist.com/contact.html) ### Automate your LC checks Loamist validates export LCs and documents in under 3 minutes, catching discrepancies before bank presentation. [Check your LC, free](https://www.loamist.com/lc-check.html) [Schedule a demo](https://www.loamist.com/contact.html) Related guides ## Keep reading. [Checklist · 8 min read The complete export LC document checklist: prevent discrepancies before bank presentation Read guide](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) [Guide · 9 min read Top 10 letter of credit discrepancies and how to prevent each one Read guide](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html) [Guide · 8 min read How to prepare a compliant commercial invoice under a letter of credit Read guide](https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html) --- URL: https://www.loamist.com/resources.html # Export LC Guides and Checklists | Loamist > Free guides, checklists, and how-to content for export coordinators, trade finance specialists, and documentation teams. UCP 600 compliant. Source: https://www.loamist.com/resources.html Resources · Guides UCP 600 · ISBP 745 # Export LC & trade documentation guides Practical how-to guides and checklists for export coordinators, trade finance specialists, and documentation teams. Built on UCP 600, ISBP 745, and real-world trade finance expertise. 6 guides and checklists [Read the blog](https://www.loamist.com/blog/) Guides and checklists ## Get the documents right the first time. [Guide · 7 min read How to review an export letter of credit before shipment A 10-point pre-shipment LC review checklist for export coordinators. Catch discrepancies before they delay payment, with UCP 600 references. Read guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) [Checklist · 8 min read The complete export LC document checklist: prevent discrepancies before bank presentation A master LC document checklist covering commercial invoice, B/L, packing list, certificate of origin, insurance, and inspection documents. UCP 600 aligned. Read guide](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) [Guide · 9 min read Top 10 letter of credit discrepancies and how to prevent each one The 10 most common LC discrepancies, with real examples, consequences, and prevention steps. Reduce first-presentation rejections in your export operation. Read guide](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html) [Guide · 8 min read How to prepare a compliant commercial invoice under a letter of credit Prepare an LC-compliant commercial invoice correctly. Covers UCP 600 Art. 18 required fields, discrepancy examples, and chemical export considerations. Read guide](https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html) [Guide · 10 min read Chemical export documentation guide: aligning REACH, TSCA, CEPA, CSCL, and GHS with letter of credit requirements How to align REACH, TSCA, CEPA, CSCL, and GHS regulatory documents with LC requirements. Practical guidance for chemical export compliance teams. Read guide](https://www.loamist.com/chemical-export-documentation-reach-tsca-ghs-lc.html) [Guide · 9 min read How to match your bill of lading to letter of credit terms: a step-by-step guide Match your bill of lading to LC terms without discrepancies. Covers UCP 600 Articles 20–23, freight terms, endorsement, B/L errors, and recovery steps. Read guide](https://www.loamist.com/bill-of-lading-letter-of-credit-compliance.html) For analysis of L/C workability, discrepancy cost and operations, read the [Loamist blog](https://www.loamist.com/blog/). --- URL: https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html # Top 10 LC Discrepancies and How to Prevent Them | Loamist > The 10 most common LC discrepancies, with real examples, consequences, and prevention steps. Reduce first-presentation rejections in your export operation. Source: https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html Guide · Discrepancies [Back to guides](https://www.loamist.com/resources.html) # Top 10 letter of credit discrepancies and how to prevent each one The 10 most common LC discrepancies, with real examples, consequences, and prevention steps. Reduce first-presentation rejections in your export operation. Published 28 March 2026 9 min read According to the ICC Banking Commission, between 60% and 70% of documentary credit presentations contain at least one discrepancy on first submission. That statistic has barely moved in two decades, not because the rules have changed, but because discrepancies are often a process problem, not a knowledge problem. The same errors appear, in the same documents, in the same order, across organizations and trade lanes. Understanding the top 10 discrepancy families, what they look like, what they cost, and specifically how to prevent them, is the most efficient path to improving your first-presentation acceptance rate. This guide covers each one with real-world examples drawn from common trade finance practice. ## 1. Inconsistencies between documents **What it is:** Under UCP 600 Article 14(d), documents presented under an LC must not be inconsistent with each other, even if each document is individually compliant with the LC. A bank examiner reading the full set must be able to reconcile every material detail across all documents. **Real-world example:** An exporter presents a commercial invoice showing gross weight of 24,800 kg and a bill of lading showing 24,600 kg. Each document may be internally correct, but the 200 kg discrepancy between them is sufficient for refusal under Article 14(d). Similarly: the packing list describes goods as "Sodium Hydroxide Solution (50%)" while the invoice reads "Caustic Soda Lye 50%": different names for the same substance, but to a bank examiner applying a documentary standard, this is a potential inconsistency. **Consequence:** Refusal of the entire document set. The bank will issue a notice of refusal listing all discrepancies, typically within 5 business days of receipt under Article 16(b). The documents cannot be re-presented as compliant without correction. **Prevention:** Complete a cross-document reconciliation before every presentation. Compare goods description, quantities, weights, party names, and port details across all documents as a set. Assign one person to own the reconciliation step; fragmented ownership is the most common reason cross-document errors slip through. ## 2. Late shipment **What it is:** The on-board date on the bill of lading falls after the latest shipment date specified in the LC. **Real-world example:** An LC specifies latest shipment date of 20 March. A vessel delay at the load port pushes the on-board date to 22 March. Even if the goods arrived at the discharge port on time, even if the buyer has already received the goods, the B/L date of 22 March creates a late shipment discrepancy that the presenting bank must note. The buyer can waive it, but they have no obligation to do so, and some buyers use this leverage to renegotiate. **Consequence:** Refusal unless the applicant waives the discrepancy. Waiver requests add 3–7 business days to the collection cycle. In practice, some applicants waive routinely; others refuse or use it as a negotiating tool, particularly in falling commodity price environments where they want to delay or reduce payment. **Prevention:** Build a 5–7 day buffer between your contractual latest shipment date and the LC's latest shipment date. Monitor vessel schedules from booking confirmation through loading. If a delay is imminent and the latest shipment date is at risk, escalate immediately and request an LC amendment before the date passes; an amendment after the fact is useless. ## 3. Late presentation **What it is:** Documents are presented to the nominated bank after the LC expiry date, or after the presentation period has elapsed (the number of calendar days after the shipment date within which documents must be presented). **Real-world example:** An LC specifies a 10-day presentation period and expires on 31 March. Goods ship on 20 March. The 10-day window closes on 30 March. Internal delays, document preparation, courier transit, bank submission, result in the set arriving at the nominated bank on 31 March. The documents are within the expiry date but outside the presentation period. This is a discrepancy. **Consequence:** Same as late shipment: refusal and applicant waiver required. If documents also arrive after the LC expiry date, there is no mechanism for compliant presentation at all under the LC, and you are dependent entirely on the applicant's and issuing bank's cooperation. **Prevention:** Calculate your latest presentation date the moment the B/L is issued. Subtract 2 days for bank processing and 1–2 days for internal submission delays. Put a hard deadline in your calendar. For shipments with short presentation periods (7 or 10 days), flag this during pre-shipment LC review and consider requesting an extension to 21 days, which is the UCP 600 Article 14(c) default. ## 4. Invoice amount or description mismatch with LC **What it is:** The commercial invoice amount exceeds the LC amount, or the goods description on the invoice does not correspond to the description in the LC. UCP 600 Article 18(b) prohibits the invoice amount from exceeding the LC value. Article 18(c) requires that the invoice description of goods correspond with the LC. **Real-world example:** An LC for USD 500,000 specifies "Polypropylene Homopolymer, natural, 500 MT at USD 1,000/MT." The exporter ships 502 MT and invoices USD 502,000. The invoice amount exceeds the LC by USD 2,000. Refusal. In a second example, the LC describes "Crude Soybean Oil, degummed" and the invoice reads "Degummed Soybean Oil, crude": same product, reversed adjective order. Many banks will flag this; some will pass it; the risk lies with the exporter. **Consequence:** Refusal. For amount exceedances, you can re-invoice for the correct amount, but this requires reprocessing the entire document set. **Prevention:** Copy the goods description from the LC verbatim into your invoice template. Do not rephrase, abbreviate, or reorder. Calculate the invoiced amount before preparing the invoice and confirm it does not exceed the LC value. If the shipment quantity differs from the LC quantity, verify whether the LC allows tolerance (Article 30 permits ±5% quantity tolerance for bulk goods unless the LC specifies "about" or prohibits tolerance). ## 5. Missing or incomplete documents **What it is:** A document required by the LC is either missing entirely from the presentation or present but incomplete (missing required fields, signatures, or certifications). **Real-world example:** An LC requires a "Certificate of Analysis issued by an independent laboratory." The exporter presents the certificate, but it is issued by their in-house quality control department, not an independent laboratory. The document is present but does not meet the LC's specification. In another case, the LC requires an "original insurance certificate in triplicate": the exporter presents two originals and a photocopy. Missing one original is grounds for refusal. **Consequence:** Refusal. Missing documents are among the most straightforward discrepancies to identify in advance but the hardest to fix quickly: obtaining a correct certificate of analysis from an accredited lab can take 5–10 business days. **Prevention:** During pre-shipment LC review, verify that every document required by the LC can be obtained in the exact form specified. For each required document, note: who issues it, how long it takes to obtain, whether the issuing body is available in your geography, and what format it will be in. Flag any document that cannot be obtained as required and request an amendment before shipment. ## 6. Bill of lading errors **What it is:** The B/L contains errors in freight terms, consignee, endorsement, or other fields examined under UCP 600 Article 20. B/L errors are among the most expensive to fix because corrections require carrier involvement and may not be possible after the vessel has departed. **Real-world example:** An LC requires freight prepaid (consistent with CIF terms), but the freight forwarder issues a B/L marked "freight collect" because the freight payment has not yet been processed. The bank refuses. In another case, the LC requires the B/L to be consigned "to order of Atlas Continental Bank" but the freight forwarder issues it consigned directly to the buyer. The bank can neither negotiate the document nor control the title transfer. **Consequence:** Refusal and potential loss of control over the goods. A B/L issued to the wrong consignee means the cargo may be released to the buyer without payment, depending on port practices in the destination country. **Prevention:** Issue written B/L instructions to your freight forwarder for every shipment, derived directly from the LC. Include: consignee wording (verbatim), notify party, freight terms, description of goods, port details, and endorsement requirements. Review the draft B/L against these instructions before the vessel sails. Carrier amendments after departure are possible but slow and expensive. ## 7. Missing signatures, stamps, or dates **What it is:** A document that requires a signature, official stamp, or issuance date is presented without one of these elements. Under UCP 600 Article 14(f), if a document appears to be issued by any person, it must identify the issuer and be signed. **Real-world example:** A certificate of origin is certified by the Chamber of Commerce but the exporter's authorized signatory forgot to sign the declaration section. The certificate has the Chamber stamp but is missing the beneficiary's signature. This is a discrepancy. In another case, an inspection certificate is dated but the date is illegible due to poor printing quality: the bank treats it as undated. **Consequence:** Refusal. Signatures and dates are easy to fix before submission but impossible to fix after presentation without reissuing the document. **Prevention:** Create a signature and stamp checklist for each document type that requires one. Include it as the final step before assembling the presentation. Physical review of each document, not just a digital scan, is the most reliable method for catching missing signatures, since digital scans of light or smudged stamps can appear acceptable on screen but be refused by the bank's examiner. ## 8. Insurance document issues **What it is:** The insurance document does not comply with UCP 600 Article 28: wrong coverage amount, incorrect risks, wrong currency, or coverage that does not begin before or on the shipment date. **Real-world example:** An LC requires coverage of 110% of CIF value in USD, covering Institute Cargo Clauses (A). The exporter's insurance certificate covers 100% of CIF value under ICC (C), which covers significantly fewer perils. Both the coverage percentage and the risk scope are non-compliant. In a second example, an insurance certificate is dated three days after the bill of lading on-board date, meaning the goods were uninsured for the first three days of the voyage as far as the LC is concerned. **Consequence:** Refusal. Insurance discrepancies are entirely avoidable with a standing instruction to your insurer that mirrors your LC requirements, but they require updating when LC terms change. **Prevention:** Maintain a template insurance instruction that includes the UCP 600 Article 28 minimum requirements: 110% of CIF/CIP value, currency matching the LC, risks as specified by the LC, and coverage effective from the date of shipment or loading. Confirm each insurance certificate against this template before presentation. ## 9. Incorrect port or routing details **What it is:** The port of loading or port of discharge on the B/L does not match the LC, or the routing involves transhipment that the LC prohibits. **Real-world example:** An LC specifies "Port of Discharge: Hamburg, Germany." Due to port congestion, the cargo is discharged at Bremerhaven and moved by road to Hamburg. The B/L shows Bremerhaven as the port of discharge. Refusal, even though Hamburg and Bremerhaven are in the same country and the cargo ends up in Hamburg. In another example, the LC prohibits transhipment, but the carrier's routing moves cargo via a feeder vessel from a smaller port to a hub, creating a transhipment, and the B/L reflects this. **Consequence:** Refusal. Port discrepancies often arise from a disconnect between the LC terms and the freight booking, particularly when logistics managers book freight without consulting the LC. **Prevention:** Include the LC's port of loading, port of discharge, and transhipment allowance in every freight booking instruction. Require the freight forwarder to confirm the routing before issuing the B/L. If port congestion or schedule changes require a routing modification, request an LC amendment before the vessel sails. ## 10. Spelling errors and typographical mistakes **What it is:** A typo, transposition, or other typographical error in a document that creates a discrepancy with the LC or with another document: wrong address, misspelled party name, incorrect LC reference number, transposed invoice amounts. **Real-world example:** The LC beneficiary is "Kestrel Industries Pte. Ltd." The commercial invoice reads "Kestrel Industry Pte. Ltd." ("Industry" singular instead of "Industries" plural). The bank refuses under Article 14(j). In another case, the invoice states the LC number as "LC/2026/04187" but the actual LC number is "LC/2026/04178", a transposition that makes the invoice appear to reference a different LC entirely. **Consequence:** Refusal. Typographical errors are entirely preventable and represent wasted effort: the entire document set must be corrected and resubmitted. **Prevention:** Use copy-paste, not manual retyping, for all critical fields: beneficiary name, applicant name, LC reference number, and goods description. Implement a second-reviewer step specifically tasked with comparing typed text against the LC for any field that was manually entered. Never retype the beneficiary name from memory; always copy from the LC. ## Prevention summary table | # | Discrepancy type | Most common cause | Primary prevention action | | --- | --- | --- | --- | | 1 | Cross-document inconsistencies | Fragmented document preparation | Cross-document reconciliation before presentation | | 2 | Late shipment | No buffer in LC timeline | Build timeline buffer; monitor vessel schedule actively | | 3 | Late presentation | Short presentation period not flagged | Calculate and calendar latest presentation date at B/L issuance | | 4 | Invoice amount/description mismatch | Description rephrased; quantity variance | Copy LC description verbatim; confirm amount ≤ LC value | | 5 | Missing/incomplete documents | Requirements not verified at LC receipt | Pre-shipment document obtainability check | | 6 | Bill of lading errors | Freight forwarder not given LC terms | Written B/L instructions derived from LC; draft B/L review | | 7 | Missing signatures/stamps/dates | No final signature checklist | Signature and stamp checklist; physical document review | | 8 | Insurance document issues | Standing instructions not updated to LC | Per-shipment insurance instruction templated to LC terms | | 9 | Port/routing errors | Freight booked without consulting LC | Include LC port terms in every freight booking instruction | | 10 | Spelling errors and typos | Manual retyping of critical fields | Copy-paste from LC; dedicated second reviewer | ## A note on discrepancy waivers When discrepancies occur, the presenting bank will typically contact the issuing bank and, through it, the applicant (buyer), to request a waiver. The applicant has no obligation to waive, and in practice, waiver decisions are influenced by commercial conditions at the time of presentation. In a falling price market, a buyer who has already received the goods may refuse to waive, triggering a formal dispute. The safest position is zero discrepancies, not a reliable waiver history. Banks charge discrepancy fees that typically range from USD 50–250 per discrepancy per presentation, in addition to the delay costs. For high-volume exporters presenting dozens of LCs per month, these fees can represent a material operating cost, and that is before accounting for the working capital impact of delayed payment on each discrepant presentation. ## Detect all 10 discrepancy families before presentation Loamist automatically detects all 10 discrepancy families described in this guide, cross-document inconsistencies, timing violations, description mismatches, signature omissions, and more, by reading your full document set against LC terms in under 3 minutes. Each flagged issue includes the specific document field, the conflicting LC clause, and the applicable UCP 600 article, so your team can fix issues in minutes rather than discovering them through a bank refusal days later. Large chemical manufacturers and commodity exporters use Loamist to reduce first-presentation discrepancy rates by up to 85% and cut the LC examination cycle from 30 minutes to 3. [See how Loamist works →](https://www.loamist.com/contact.html) ### Automate your LC checks Loamist validates export LCs and documents in under 3 minutes, catching discrepancies before bank presentation. [Check your LC, free](https://www.loamist.com/lc-check.html) [Schedule a demo](https://www.loamist.com/contact.html) Related guides ## Keep reading. [Guide · 7 min read How to review an export letter of credit before shipment Read guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) [Checklist · 8 min read The complete export LC document checklist: prevent discrepancies before bank presentation Read guide](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) [Guide · 8 min read How to prepare a compliant commercial invoice under a letter of credit Read guide](https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html) --- URL: https://www.loamist.com/about.html # About: The Team Behind Loamist > Meet the team behind Loamist: scientists, operators and builders making AI agents reliable for trade documents, letters of credit and land decisions. Source: https://www.loamist.com/about.html Our story About Loamist # Trust infrastructure for global trade finance. Cross-border trade still runs on paper. Letters of credit, bills of lading, certificates of origin, packing lists, inspection certificates, and compliance attestations move through email, courier, and manual review, at a cost the industry has quietly accepted for decades. UCP 600 governs the rules, ISBP 821E governs the practice, and yet the majority of LC presentations contain discrepancies on first review. The result: delayed payments, rejected presentations, and working capital trapped in transit. Loamist is rebuilding that layer. Our AI platform automates the examination of trade documents against letter of credit terms, applying UCP 600 articles, ISBP 821E paragraphs, and bank-specific practice in real time. Exporters, importers, and trade finance banks get discrepancy detection in minutes instead of days, with audit trails that hold up to compliance review. § 01 · Leadership ## Leadership Pete Christensen ### Pete Christensen Co-Founder & CEO · [LinkedIn](https://www.linkedin.com/in/prchristensen-phd) Sets vision and commercial strategy at Loamist. A repeat founder and PhD chemist whose career spans fundamental science to commercial deployment: doctoral and postdoctoral work on optical materials for solar cells and OLEDs at the University of British Columbia and Lawrence Berkeley National Laboratory, followed by the design of recyclable polymers and composites. Pete co-founded FLO Materials, a venture-backed advanced materials startup. At H2 Compliance, Pete spent years inside the world Loamist now automates: cross-border filings, chain-of-custody records, and audit-grade documentation. Activate Entrepreneurial Fellow (2021–2023) and Breakthrough Energy Innovation Fellow (2024–2025). Andy Miller ### Andy Miller Co-Founder & CTO · [LinkedIn](https://www.linkedin.com/in/andymill/) Andy leads engineering and the agent architecture. Bioengineer and full-stack technologist with 18 patents spanning medical devices, consumer health, and industrial design. Deep capabilities across hardware-software co-design, covering the full path from first-principles engineering to manufacturable product. Two decades commercializing technical innovations across regulated industries, with three Red Dot Design Awards and work covered in *Vogue*, CNN, *Wired*, and the *New York Times*. Former VP of Innovation at The Flex Company, Breakthrough Energy Fellow, and bioengineering training from Rice University. § 02 · Our thesis ## Our thesis Global trade still depends on document workflows that haven't fundamentally changed in decades. Fixing that requires both technology and trust infrastructure. Loamist builds both, so exporters, banks, and trade finance teams can finally operate with the speed and rigor that modern supply chains demand. --- URL: https://www.loamist.com/contact.html # Contact Loamist: questions, pricing or a demo > Get in touch with the Loamist team. Questions about L/C automation, pricing, or a demo? We will get back to you within 1 business day. Source: https://www.loamist.com/contact.html Get in touch Reply within 1 business day # How can we help you? Fill in the form and we will get back to you within 1 business day. - 01 ### Send the form A few lines on your workflow and team help us prepare. - 02 ### We reply The Loamist team answers within 1 business day. - 03 ### A working session If it is useful, we walk through your own documents. Work email required. We do not share your data. Response within 1 business day Have an L/C to hand? [Run the free L/C check](https://www.loamist.com/lc-check.html) while you wait. --- URL: https://www.loamist.com/cybersecurity-whitepaper.html # Privacy, Security, Data Governance, & Compliance: Loamist > Loamist cybersecurity whitepaper covering privacy, security infrastructure, data governance, compliance certifications, and AI processing practices. Source: https://www.loamist.com/cybersecurity-whitepaper.html Cybersecurity whitepaper Version 2.0 | February 2026 # Privacy, security, data governance, & compliance AI-powered supply chain validation with privacy-first design. ## Introduction Loamist Validator™ is an AI-powered platform that processes trade documentation and validates supply chain compliance for regulated industries. We integrate with Google's Gemini large language models (LLMs) to automate document processing while maintaining enterprise-grade security and privacy. This whitepaper explains how we handle your data, our security practices, and our approach to building AI tools for regulated supply chains. ## Core commitments ### Your data is your data **We process your data only according to your instructions.** When you upload trade documents, compliance certificates, or supply chain data to Loamist: - **Your data remains your data**: You control it, you own it, and you can delete it at any time - **Your data never trains our models**: We do not use your documents to improve our systems or train AI models - **Your data stays within your account**: Documents are never shared across organizations - **Delete anytime**: Remove documents via the interface or on request; upon account closure, all data deleted within 30 days ### What we will not do - **We will never sell your data**: Your documents and extracted data are never sold or monetized - **We will never train models on your data**: AI processing does not feed back into model training - **We will never share data across customers**: Complete isolation between organizations - **We will never use your data for advertising**: No ads, no tracking, no secondary use ### Enterprise-grade security and privacy - **Encryption everywhere**: TLS 1.3 in transit, AES-256 at rest - **Complete audit trails**: Immutable logs of every action, every user, every document - **Access controls**: Role-based permissions with SSO support - **Certifications**: SOC 2 Type II certified ## Privacy principles in detail ### Your data is your data **Customer data belongs to you and only you.** When you upload documents to Loamist: - Documents are processed using Google's Gemini models via their API: Google does not use Enterprise API customer data to train their models - Your data stays within your account and is not shared across organizations - You maintain complete control over retention and deletion ### Encryption and security **All data is encrypted at all times:** - **In transit**: TLS 1.3 encryption - **At rest**: AES-256 encryption - **During processing**: Documents remain encrypted throughout the validation pipeline **Access control:** - Role-based permissions control who can upload, review, and approve documents - Single Sign-On (SSO) support for Google Workspace (Microsoft Azure AD and SAML in roadmap for 2026) - All access logged with user attribution and timestamps ### Data retention **Your data is retained while your account is active:** - Delete documents at any time via the Loamist interface or on request - Upon account closure: all customer data deleted within 30 days **Audit logs retained for 7 years** to support regulatory audits: these are immutable records of every processing event, user access, and validation decision. ## Security infrastructure ### Cloud infrastructure on AWS **Enterprise-grade cloud security with multiple layers of protection:** - **Web Application Firewall (WAF)**: Protection against common web exploits - **DDoS protection**: AWS Shield for network and transport layer protection - **Network isolation**: VPC segmentation with private subnets for sensitive components - **Infrastructure monitoring**: CloudWatch for real-time monitoring and alerting - **Compliance foundation**: AWS maintains SOC 2, ISO 27001, GDPR, HIPAA, and FedRAMP certifications ### AI processing via Google Gemini API **Secure API integration with Google's enterprise AI:** - Document processing leverages Google's Gemini models via secure API calls - Google's enterprise commitment: API customer data is not used to train models - Benefits from Google's AI security infrastructure (prompt injection defenses, adversarial testing) ### Application security practices **Secure development and operations:** - Regular security updates and patch management - Secure development lifecycle with code reviews - Dependency scanning for vulnerabilities - Automated security testing in CI/CD pipeline **Authentication and access:** - Single Sign-On (SSO) support for Google Workspace (Microsoft Azure AD and SAML in roadmap for 2026) - Session management with automatic timeout **Monitoring and alerting:** - Continuous monitoring for suspicious activity - Automated alerts for failed authentication, unusual access patterns, or system anomalies - Integration with customer SIEM systems available ## Compliance and certifications ### Security certifications **SOC 2 Type II** (Certified) - Independent audit of security, availability, and confidentiality controls complete - Controls monitored continuously in Vanta (our compliance monitoring platform) - Validates responsible customer data management ### Industry-specific compliance support **Trade Finance and Letters of Credit:** - UCP 600 (Uniform Customs and Practice for Documentary Credits): ICC Publication No. 600, governing international letters of credit across 175+ countries - Strict compliance verification for letter of credit terms - Commercial invoice validation (description accuracy, amount verification) - Transport document verification (bills of lading, cleanliness requirements, signature validation) - ISBP 745 (International Standard Banking Practice): companion guide for document examination ### How Loamist supports compliance - Automated extraction of required data fields with strict compliance verification for letter of credit transactions - Geospatial validation for location-dependent compliance requirements - Document consistency checking across related documents (invoices, bills of lading, certificates) per UCP 600 Article 14(d) - Chain-of-custody audit trails for regulatory claims and certifications - Flagging of common discrepancies in documentation (invoice amounts, transport document issues, missing signatures) - Compliance reports with supporting documentation ## Deployment options ### Current: cloud deployment on AWS **Cloud-based SaaS platform in US regions:** - Load balancing across multiple availability zones within a region - Currently deployed in US AWS regions - Regional data residency options (including EU) planned for future expansion - AWS security features: WAF, Shield DDoS protection, VPC isolation - 99.9% uptime target - Automatic scaling ### Future: on-premises and air-gapped options **Aligned with Google's infrastructure roadmap:** Google is expanding Gemini availability to on-premises environments via **Google Distributed Cloud (GDC)**, enabling customers to run Gemini models entirely within their own data centers, including air-gapped environments for classified workloads. **Loamist's intent**: As Google makes these capabilities available, we plan to offer on-premises deployment options for customers with strict data residency requirements: - **On-premises**: Run Loamist Validator™ in your data center with GDC infrastructure - **Air-gapped**: Complete network isolation for sensitive environments - **Hybrid**: Process sensitive documents on-premises, leverage cloud for other workloads **Timeline**: Following Google's GDC roadmap (2025 and beyond) **Why this matters**: Customers in regulated industries (government, defense, critical infrastructure, financial services) will be able to use Loamist's AI capabilities without data leaving their premises. ## Data governance ### All customer data is confidential **No data classification tiers: everything is treated as confidential and restricted:** - Only users within your organization can access your documents - No cross-organization data sharing - No external use for training, advertising, or other purposes - Encryption applied uniformly to all data ### Audit and transparency **Chain-of-custody logging:** - Every document upload, processing event, and user action is logged - Logs include timestamps, user IDs, document IDs, and validation decisions - Immutable audit trail for regulatory compliance (cannot be altered after creation) **Confidence scoring:** - AI extractions include confidence scores (0-100%) for each data field - Low-confidence extractions flagged for human review - Complete visibility into what AI extracted and its certainty level **Data access and portability:** - Export all data at any time (documents, extracted data, audit logs) - Standard formats: JSON, CSV, PDF reports - No lock-in: you own your data ## Human review and validation **AI automation with human oversight for compliance decisions:** ### Confidence thresholds - **High confidence (>90%)**: Automatic approval for standard documents - **Medium confidence (70-90%)**: Flagged for human review - **Low confidence ( **Website**: [www.loamist.com](https://www.loamist.com) **Support**: [support@loamist.com](mailto:support@loamist.com) ## Summary **Loamist provides AI-powered supply chain validation for regulated industries with privacy and security built in from day one.** ### Core commitments - **Your data is your data**: You control it, you own it, and you can delete it at any time - **Your data never trains our models**: No model training, no secondary use, no data sharing across customers - **Enterprise-grade security**: Encryption everywhere (TLS 1.3, AES-256), complete audit trails, SOC 2 Type II certified - **Compliance-focused**: Purpose-built for international trade finance, sustainable materials, and regulated supply chains - **Transparent AI**: Confidence scoring and human review for all validation decisions - **Deployment flexibility**: Cloud today, on-premises options planned as Google enables them ### What we will not do - We will never sell your data - We will never train models on your data - We will never share data across customers - We will never use your data for advertising We're building Loamist with security, privacy, and compliance as foundational principles. As we grow, we're committed to maintaining these standards while expanding our capabilities to serve regulated supply chains worldwide. Contents - [Introduction](#introduction) - [Core commitments](#core-commitments) - [Privacy principles in detail](#privacy-principles-in-detail) - [Security infrastructure](#security-infrastructure) - [Compliance and certifications](#compliance-and-certifications) - [Deployment options](#deployment-options) - [Data governance](#data-governance) - [Human review and validation](#human-review-and-validation) - [Business continuity](#business-continuity) - [Frequently asked questions](#frequently-asked-questions) - [Contact us](#contact-us) - [Summary](#summary) --- URL: https://www.loamist.com/privacy-policy.html # Privacy Policy: Loamist > Privacy Policy explaining how Loamist collects, uses, discloses, and protects your information when you use our application and services. Source: https://www.loamist.com/privacy-policy.html Legal Last updated: October 29, 2025 # Privacy Policy How Loamist collects, uses, discloses, and protects your information when you use our application and services. ## 1. Introduction At Loamist ("we," "our," or "the Application"), we respect and value the privacy of our users ("you" or "user"). This Privacy Policy explains how we collect, use, disclose, and protect your information when you use our application and services. ## 2. Information We Collect When you use our application, we may collect and process the following types of information: ### 2.1 Personal Information - **Authentication Data:** When you log in using your Google account, we collect your email address, name, and profile picture. - **Other Information:** Any other information you provide directly through our application. ### 2.2 Non-Personal Information - **Usage Data:** Information about how you use the application, such as the pages you visit, session duration, and other usage statistics. - **Device Information:** Technical information about your device, such as device model, operating system, and unique device identifier. ## 3. Use of Information We use the information we collect for the following purposes: - **Provide and Improve Our Services:** We use your information to authenticate your account, personalize your experience, and enhance the functionality of our application. - **Communications:** We may use your contact information to send you updates, newsletters, and respond to your inquiries and requests. - **Security:** To protect our services and our users by detecting and preventing fraud, abuse, and other security issues. ## 4. Disclosure of Information We do not share your personal information with third parties, except in the following circumstances: - **With Your Consent:** We may share information with third parties if we have your consent to do so. - **Service Providers:** We may employ third-party companies and individuals to facilitate our service, provide the service on our behalf, perform service-related tasks, or help us analyze how our service is used. These third parties have access to your personal information only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose. - **Compliance with Law:** We may disclose your personal information when we believe in good faith that such action is necessary to comply with a legal obligation or to protect and defend the rights or property of our application. ## 5. Information Security We take the security of your information seriously and use reasonable security measures to protect it from unauthorized access, alteration, disclosure, or destruction. ## 6. Your Rights You have certain rights regarding your personal information, including the right to access, correct, or delete your personal information. If you wish to exercise any of these rights, please contact us at [andy@loamist.com](mailto:andy@loamist.com). ## 7. Changes to This Privacy Policy We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top. ## 8. Contact Us If you have any questions about this Privacy Policy, please contact us at: **Andy Miller** Loamist, Co. 1150 Arch St Berkeley, CA 94708 Email: [andy@loamist.com](mailto:andy@loamist.com) Contents - [1. Introduction](#introduction) - [2. Information We Collect](#information-we-collect) - [3. Use of Information](#use-of-information) - [4. Disclosure of Information](#disclosure-of-information) - [5. Information Security](#information-security) - [6. Your Rights](#your-rights) - [7. Changes to This Privacy Policy](#changes-to-this-privacy-policy) - [8. Contact Us](#contact-us) --- URL: https://www.loamist.com/terms-of-service.html # Terms of Service: Loamist > Terms of Service governing access to and use of Loamist's AI-powered export documentation and LC validation services. Source: https://www.loamist.com/terms-of-service.html Legal Last updated: November 27, 2025 # Terms of Service Terms governing access to and use of Loamist's AI-powered export documentation and LC validation services. ## 1. Introduction These Terms of Service ("Agreement") govern your access to and use of Loamist's services. By using our services, you agree to be bound by these terms. This Agreement includes and incorporates any Order Form accepted by you. "Loamist," "we," "our," or "us" refers to Loamist, Co. "Customer," "you," or "your" refers to you, the user of the Subscription Services. Your use of the Subscription Services is also subject to our Privacy Policy, which is incorporated into these Terms by reference. We may modify these Terms from time to time. We will notify you of material changes via email or through the Service. Your continued use of the Subscription Services after such changes constitutes acceptance of the modified Terms. ## 2. Definitions **"Loamist IP"** means the Subscription Services, the underlying software, algorithms, interfaces, technology, databases, tools, know-how, processes and methods used to provide or deliver the Subscription Services and Documentation, all improvements, modifications or enhancements to, or derivative works of, the foregoing (regardless of inventorship or authorship), and all intellectual property rights in and to any of the foregoing. **"Customer Materials"** means all information, data, content and other materials, in any form or medium, that is provided, or otherwise uploaded, by or on behalf of Customer through the Subscription Services or to Loamist in connection with Customer's use of the Subscription Services, but excluding, for clarity, any Loamist IP. **"Documentation"** means the operator, user, and technical manuals and documentation. **"Effective Date"** means the date on which Customer accepts these Terms of Service or creates an account, whichever occurs first. **"Order Form"** means a(n) (i) mutually executed order form or other mutually agreed upon ordering document; (ii) purchase order issued by Customer and accepted by Loamist in writing; (iii) online registration form made available by Loamist and accepted by Customer; or (iv) quote issued by Loamist and accepted by Customer, in each case which references this Agreement and sets forth the applicable Subscription Services to be provided by Loamist. **"Subscription Services"** means the services offered by Loamist to Customer pursuant to this Agreement, including proprietary data analysis and validation services, including document analysis, trade finance verification, letter of credit examination, and export documentation automation, as provided through the Loamist Validator™ platform, as more particularly described or identified in the applicable Order Form. **"Use"** means to use and access the Subscription Services in accordance with this Agreement and the Documentation. **"Authorized Users"** means Customer's employees or contractors that Customer authorizes to use the Subscription Services on its behalf. ## 3. Right to Use ### 3.1 License Grant Subject to Customer's compliance with the terms and conditions of this Agreement, Loamist hereby grants to Customer a limited, non-exclusive, non-transferable (except pursuant to Section 14) right to Use the Subscription Services during the applicable Term. ### 3.2 Ownership Loamist reserves and, as between the Parties will solely own, the Loamist IP and all rights, title and interest in and to the Loamist IP. No rights are granted to Customer hereunder (whether by implication, estoppel, exhaustion or otherwise) other than as expressly set forth herein. All intellectual property rights relating to any Loamist IP will vest solely in Loamist upon creation, and to the extent that sole ownership does not originally vest in Loamist, such intellectual property rights are hereby automatically and irrevocably assigned by Customer to Loamist. Customer will take all actions and execute all documents reasonably requested by Loamist to give effect to the preceding sentence. ## 4. Use Restrictions Customer will not and will not permit any person or entity (including, without limitation, Authorized Users) to, directly or indirectly: - (i) copy, modify or create any derivative work of any portion of the Subscription Services or the Documentation; - (ii) reverse engineer, decompile, decode, or disassemble or otherwise attempt to derive or gain improper access to any software component of the Subscription Services, in whole or in part; - (iii) frame, mirror, sell, resell, market, sublicense, publish, distribute, reproduce, assign, transfer, rent, lease or loan any portion of the Subscription Services to any other person or entity, or otherwise allow any person or entity to use the Subscription Services for any purpose other than for the benefit of Customer in accordance with this Agreement; - (iv) use the Subscription Services or Documentation in any manner or for any purpose that infringes, misappropriates, or otherwise violates any intellectual property rights or other right of any person or entity, or that violates any applicable law; or - (v) access or search the Subscription Services (or download any data or content contained therein or transmitted thereby) through the use of any engine, software, tool, agent, device or mechanism (including spiders, robots, crawlers or any other similar data mining tools) other than software or Subscription Services features provided by Loamist expressly for such purposes. ## 5. Authorized Users Customer will not allow any person or entity other than Authorized Users to use the Subscription Services. Customer may permit Authorized Users to Use the Subscription Services, provided that Customer is responsible for all acts or omissions by its Authorized Users in connection with their use of the Subscription Services and their compliance with the terms and conditions of this Agreement. ## 6. Customer Materials and Data ### 6.1 Ownership As between Customer and Loamist, Customer owns and retains all right, title and interest in and to all Customer Materials. ### 6.2 License to Loamist Customer agrees that Loamist may reproduce, display, perform publicly, modify and otherwise use the Customer Materials solely to provide and improve the Subscription Services during the Term. ### 6.3 Service Information Loamist may develop or derive data or insights in deidentified form from (i) any Customer Materials; or (ii) Customer's and/or its Authorized Users' use of the Subscription Services, including, without limitation, any usage data or trends with respect to the Subscription Services ("Service Information"). ### 6.4 Data Security Loamist will implement and maintain industry-standard administrative, physical, and technical safeguards designed to protect the confidentiality, integrity, and availability of Customer Materials, including encryption of data in transit and at rest, access controls, and authentication safeguards consistent with generally accepted industry practices. Loamist will comply with all applicable data protection and privacy laws in its performance of the Subscription Services. ### 6.5 Security Incidents In the event of any unauthorized access to or disclosure of Customer Materials (a "Security Incident"), Loamist will notify Customer without undue delay, and in no event later than seventy-two (72) hours after confirmation of the Security Incident, and will provide reasonable information and cooperation to support Customer's response. ### 6.6 Data Retention and Deletion Upon expiration or termination of this Agreement, Loamist will, upon written request, delete or return all Customer Materials in its possession within sixty (60) days, except as otherwise required by law. ### 6.7 Third-Party Service Providers Loamist may engage third-party service providers (including cloud hosting providers) in connection with the Subscription Services, provided that Loamist will remain responsible for the acts and omissions of such providers and will ensure they are subject to safeguards no less protective than those described herein. ## 7. Fees and Payment ### 7.1 Fees Customer will pay Loamist the fees set forth in the applicable Order Form ("Fees") in accordance with the payment terms set forth therein and without offset or deduction. ### 7.2 Fee Changes Loamist reserves the right to change the Fees or applicable charges and to institute new charges and Fees at the end of the Initial Term or then-current Renewal Term, upon thirty (30) days' prior notice to Customer. ### 7.3 Invoicing and Payment Except as otherwise provided in the relevant Order Form or agreed by the Parties, Loamist will issue monthly invoices to Customer during the Term, and Customer will pay all amounts set forth on any such invoice no later than thirty (30) days after the date of such invoice. ### 7.4 Automatic Billing If Customer has signed up for automatic billing, Loamist will charge Customer's selected payment method for any Fees on the applicable payment date, including any applicable taxes. If Loamist cannot charge Customer's selected payment method for any reason (such as expiration or insufficient funds), Customer remains responsible for any uncollected amounts. ### 7.5 Non-Refundable All payments are non-refundable, and Customer will not have the right to set off, discount or otherwise reduce or refuse to pay any amounts due to Loamist under this Agreement. ## 8. Term and Termination ### 8.1 Term The initial term of this Agreement begins on the Effective Date and expires at the end of the Initial Term specified in the relevant Order Form (the "Initial Term"). Following the Initial Term, this Agreement will automatically renew for additional periods of the same duration as the Initial Term (each, a "Renewal Term," and together with the Initial Term, the "Term"), unless either Party provides the other with at least thirty (30) days' written notice of its intent not to renew this Agreement prior to the end of the Initial Term or the then-current Renewal Term. ### 8.2 Termination for Cause Either Party may terminate this Agreement, effective on written notice to the other Party, if the other Party materially breaches this Agreement, and, if able to be cured, such breach remains uncured thirty (30) days after the non-breaching Party provides the breaching Party with written notice of such breach. ### 8.3 Immediate Termination Loamist may further terminate this Agreement immediately upon written notice to Customer in the event that Customer breaches Sections 4 or 5, or infringes or otherwise violates Loamist's intellectual property rights in and to the Subscription Services. ### 8.4 Effect of Termination Upon expiration or termination of this Agreement: - (i) Customer's and its Authorized Users' right to Use the Subscription Services will immediately terminate; - (ii) all Fees owed by Customer to Loamist will be immediately due; and - (iii) Loamist will retain Customer Materials for sixty (60) days, during which Customer may request export or deletion pursuant to Section 6.6. ### 8.5 Survival The rights and obligations of Loamist and Customer contained in Sections 6, 7, 8, 10, 11, 12, 13 and 14 will survive any expiration or termination of this Agreement. ## 9. Representations and Warranties ### 9.1 Mutual Representations Each Party represents and warrants to the other Party that: (i) it has full power and authority to enter into this Agreement; and (ii) the execution, delivery and performance of this Agreement by it have been duly authorized by all necessary actions and do not violate its organizational documents. ### 9.2 Customer Representations Customer represents and warrants that Loamist's use of the Customer Materials in accordance with this Agreement will not violate any applicable laws or regulations or infringe or violate any intellectual property or other rights of any third party or cause a breach of any agreement or obligations between Customer and any third-party. ## 10. Confidentiality ### 10.1 Customer Materials as Confidential Information Loamist acknowledges that Customer Materials constitute confidential information of Customer. Loamist will not use or disclose any Customer Materials except as necessary to perform its obligations or exercise its rights under this Agreement, or as permitted in Section 6. ### 10.2 Permitted Disclosures Loamist may disclose Customer Materials only: (i) to those of its employees, contractors, agents and advisors who have a bona fide need to know such information to perform under this Agreement and who are bound by written agreements with use and nondisclosure restrictions at least as protective as those set forth in this Agreement; (ii) to third-party service providers as permitted under Section 6.7; or (iii) as such disclosure may be required by the order or requirement of a court, administrative agency or other governmental body, subject to Loamist providing to Customer reasonable written notice to allow Customer to seek a protective order or otherwise contest the disclosure. ### 10.3 Exclusions The obligations in this Section 10 will not apply to information that: (i) is or becomes generally known to the public through no fault or breach of this Agreement by Loamist; (ii) is rightfully known by Loamist at the time of disclosure without an obligation of confidentiality; (iii) is independently developed by Loamist without access to or use of any Customer Materials that can be evidenced in writing; or (iv) is rightfully obtained by Loamist from a third-party without restriction on use or disclosure. ### 10.4 Transfer Upon Acquisition In the event of a merger, acquisition, or sale of all or substantially all of Loamist's assets, Customer Materials may be transferred to the successor entity, provided that such successor agrees to be bound by confidentiality obligations no less protective than those set forth in this Agreement. ### 10.5 Duration The confidentiality obligations set forth in this Section 10 will survive for two (2) years following expiration or termination of this Agreement. ## 11. Disclaimer THE SUBSCRIPTION SERVICES AND OTHER LOAMIST IP ARE PROVIDED ON AN "AS IS" BASIS, AND LOAMIST MAKES NO WARRANTIES OR REPRESENTATIONS TO CUSTOMER, ITS AUTHORIZED USERS OR TO ANY OTHER PARTY REGARDING THE LOAMIST IP, THE SUBSCRIPTION SERVICES OR ANY OTHER SERVICES OR MATERIALS PROVIDED HEREUNDER. ## 12. Limitation of Liability EXCEPT FOR (I) BREACH OF SECTION 10 (CONFIDENTIALITY), (II) BREACH OF CUSTOMER'S PAYMENT OBLIGATIONS AND (III) INFRINGEMENT OR MISAPPROPRIATION OF THE OTHER PARTY'S INTELLECTUAL PROPERTY RIGHTS, NEITHER PARTY WILL BE LIABLE TO THE OTHER PARTY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR ANY LOSS OF INCOME, DATA, PROFITS, REVENUE OR BUSINESS INTERRUPTION, OR THE COST OF COVER OR SUBSTITUTE SERVICES, ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT. IN NO EVENT WILL LOAMIST'S TOTAL LIABILITY TO CUSTOMER OR ITS AUTHORIZED USERS IN CONNECTION WITH THIS AGREEMENT EXCEED THE FEES ACTUALLY PAID BY CUSTOMER TO LOAMIST IN THE TWELVE (12) MONTH PERIOD PRECEDING THE EVENT GIVING RISE TO THE CLAIM. THE LIMITATIONS AND EXCLUSIONS IN THIS SECTION WILL APPLY WHETHER SUCH LIABILITY ARISES FROM ANY CLAIM BASED ON CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, AND WHETHER OR NOT SUCH PARTY WAS ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. ## 13. Indemnification ### 13.1 Indemnification by Loamist Subject to Section 13.2, Loamist will defend Customer against any claim, suit or proceeding brought by a third-party ("Claims") alleging that Customer's Use of the Subscription Services infringes or misappropriates such third party's intellectual property rights, and will indemnify and hold harmless Customer against any damages and costs awarded in a final judgement against Customer or agreed in settlement by Loamist (including reasonable attorneys' fees) resulting from such Claim. ### 13.2 Exclusions Loamist's obligations under Section 13.1 will not apply if the underlying Claim arises from or as a result of: (i) Customer's breach of this Agreement, negligence, willful misconduct or fraud; (ii) any Customer Materials; (iii) Customer's failure to use any enhancements, modifications, or updates to the Subscription Services that have been provided by Loamist; (iv) modifications to the Subscription Services by anyone other than Loamist; or (v) combinations of the Subscription Services with software, data or materials not provided by Loamist. ### 13.3 Indemnification by Customer Customer will defend, indemnify and hold harmless Loamist from and against any damages and liabilities (including court costs and reasonable attorneys' fees) awarded in a final judgment against Loamist, and amounts agreed to in settlement with respect to each of the foregoing, to the extent arising from a Claim against Loamist that: (i) the Customer Materials or its use by Loamist in accordance with this Agreement infringes, misappropriates or violates a third-party's intellectual property rights, or rights of publicity or privacy, or result in the violation of any applicable law or regulation; (ii) is based on Customer's or an Authorized User's use of the Subscription Services or Documentation to the extent such use was not in accordance with this Agreement; (iii) is based on the manufacture, sale, distribution or marketing of any of Customer's products or services; or (iv) is based on a breach of Section 4 by Customer. ### 13.4 Indemnification Procedures Each Party's obligations under this Section 13 are contingent upon: (i) the Party seeking defense and indemnity (the "Indemnified Party") providing the other Party (the "Indemnifying Party") with prompt written notice of such Claim (but in any event notice in sufficient time for the Indemnifying Party to respond without prejudice); (ii) the Indemnifying Party having the exclusive right to defend or settle such Claim; and (iii) the Indemnified Party providing all reasonably necessary cooperation to the Indemnifying Party, at the Indemnifying Party's expense, in the defense and settlement of such Claim. The Indemnified Party may participate in the defense of any Claim at its own expense. ## 14. Miscellaneous ### 14.1 Assignment Neither Party may assign, transfer or sublicense this Agreement, by operation of law or otherwise, without the other Party's prior written consent, except to a successor entity in the event of a merger, consolidation or sale of all or substantially all of the assets of such Party, and any attempt by either Party to do so, without such consent, will be void. Subject to the foregoing, this Agreement is binding upon and will inure to the benefit of each of the Parties and their respective successors and permitted assigns. ### 14.2 Export Control Customer affirms that it is not named on, owned by, or acting on behalf of any U.S. government denied-party list, and it agrees to comply fully with all relevant export control and sanctions laws and regulations of the United States ("Export Laws") to ensure that neither the Subscription Services, software, any Customer Materials, nor any technical data related thereto is: (i) used, exported or re-exported directly or indirectly in violation of Export Laws; or (ii) used for any purposes prohibited by the Export Laws, including, but not limited to, nuclear, chemical, or biological weapons proliferation, missile systems or technology, or restricted unmanned aerial vehicle applications. Customer will complete all undertakings required by Export Laws, including obtaining any necessary export license or other governmental approval. ### 14.3 Force Majeure Neither Party will be responsible for any failure or delay in the performance of its obligations under this Agreement (except for any payment obligations) due to causes beyond its reasonable control. ### 14.4 Severability If any provision of this Agreement is held invalid, illegal or unenforceable, that provision will be enforced to the maximum extent permitted by law, given the fundamental intentions of the Parties, and the remaining provisions of this Agreement will remain in full force and effect. ### 14.5 Entire Agreement This Agreement, including its exhibits and any Order Form(s), is the complete and exclusive agreement between the Parties with respect to its subject matter and supersedes all prior or contemporaneous agreements, communications and understandings, both written and oral, with respect to its subject matter. ### 14.6 Amendments This Agreement may be amended or modified only by a written document executed by duly authorized representatives of the Parties. ### 14.7 No Agency Nothing in this Agreement will be construed to create a partnership, joint venture or agency relationship between the Parties. Neither Party will have the power to bind the other or to incur obligations on the other's behalf without such other Party's prior written consent. ### 14.8 Remedies Except as expressly set forth in this Agreement, the exercise by either Party of any remedy under this Agreement will be without prejudice to its other remedies under this Agreement or otherwise. ### 14.9 Waiver Either Party's failure to enforce any provision of this Agreement will not constitute a waiver of future enforcement of that or any other provision. No waiver of any provision of this Agreement will be effective unless it is in writing and signed by the Party granting the waiver. ### 14.10 Governing Law This Agreement will be governed by and construed in accordance with the laws of the State of California without giving effect to any principles of conflict of laws that would lead to the application of the laws of another jurisdiction. The Parties expressly agree that the United Nations Convention on Contracts for the International Sale of Goods will not apply. ### 14.11 Jurisdiction Any legal action or proceeding arising under this Agreement will be brought exclusively in the federal or state courts located in Alameda County, California and the Parties irrevocably consent to the personal jurisdiction and venue therein. ### 14.12 Notices All notices required to be sent hereunder will be in writing (email being sufficient) and will be deemed to have been given when mailed by certified mail, overnight express, or sent by email, with receipt confirmed. ### 14.13 Counterparts This Agreement may be signed in counterparts, and electronic signatures will have the same weight and effect as originals. ### 14.14 Contact Information For questions about these Terms or to send legal notices: **Loamist, Co.** 1150 Arch St Berkeley, CA 94708 Email: [andy@loamist.com](mailto:andy@loamist.com) ## EXHIBIT A - Default Order Form Upon agreeing to this Terms of Service, the user agrees to the following order form conditions until the service is canceled or until a new order is placed, at which time the new order form will supersede the one agreed upon herein. #### Service Loamist Validator™ #### Subscription Commitment Twelve (12) Month Commitment with Monthly Billing #### Free Trial One (1) month free trial period beginning on the Effective Date. No credit card is required during the free trial period. #### Subscription Term The paid subscription term for Loamist Validator™ begins immediately after the free trial period ends. Customer commits to a minimum subscription period of twelve (12) months ("Subscription Term"). #### Payment Terms - Billing Frequency: Monthly, in advance - Payment Method: Credit card via third-party payment platform - Billing Start: First billing occurs when free trial ends Customer must provide a valid credit card before the free trial ends to continue service. Customer's credit card will be billed monthly at the then-current rate. If Loamist cannot charge Customer's selected payment method for any reason (such as expiration or insufficient funds), Customer remains responsible for all uncollected amounts for the full 12-month Subscription Term. #### 12-Month Commitment Customer commits to the full twelve (12) month Subscription Term. Payment obligations are non-cancelable. The subscriber is responsible for the full subscription fee for the twelve (12) month period, regardless of whether the subscription is actively used or canceled early. #### Cancellation Policy If Customer chooses to cancel the subscription any time after the free trial period: - Customer remains responsible for payment of the remaining monthly fees for the twelve (12) month Subscription Term - There will be no refunds or credits for partial months of service - There will be no refunds for months unused with an open account - Service access will continue until the end of the current billing period #### Automatic Renewal Unless Customer notifies Loamist at least thirty (30) days before the end of the Subscription Term that they want to cancel, the subscription will automatically renew for another twelve (12) month term. The renewal subscription term will be subject to the then-current subscription rates. Note: This Order Form is subject to and incorporates the Loamist Terms of Service and, once accepted, constitutes a binding agreement between Loamist and Customer. Any capitalized terms not defined in this Order Form will have the meaning ascribed to them in the Loamist Terms of Service. Contents - [1. Introduction](#introduction) - [2. Definitions](#definitions) - [3. Right to Use](#right-to-use) - [4. Use Restrictions](#use-restrictions) - [5. Authorized Users](#authorized-users) - [6. Customer Materials and Data](#customer-materials-and-data) - [7. Fees and Payment](#fees-and-payment) - [8. Term and Termination](#term-and-termination) - [9. Representations and Warranties](#representations-and-warranties) - [10. Confidentiality](#confidentiality) - [11. Disclaimer](#disclaimer) - [12. Limitation of Liability](#limitation-of-liability) - [13. Indemnification](#indemnification) - [14. Miscellaneous](#miscellaneous) - [Exhibit A: Default Order Form](#exhibit-a-default-order-form) --- URL: https://www.loamist.com/blog/seventy-percent-less-time-per-letter-of-credit/ # 70% Less Time per Letter of Credit: What a Documentation Team Does With the Hours Back > A Validator client cut effort per letter of credit by around 70%. With routine review handled, examiners moved to exceptions, cargo strategy and advice. Source: https://www.loamist.com/blog/seventy-percent-less-time-per-letter-of-credit/ Published: 2026-10-08 · Operations · By Nick Pachnev, Senior Advisor A client using Loamist Validator reduced effort per letter of credit by around 70%. ## Where the time went before Before Validator, the team's hours on a typical credit broke down the way they do almost everywhere: reading the L/C and confirming the terms with production and logistics, preparing and re-keying documents, checking the set against the credit and against each other, chasing corrections from third parties, and presenting. Most of that is routine review, the same checks on the same document types, corridor after corridor. It is necessary and it is not where an experienced examiner adds value. ## Where it goes now Now, export document teams can quickly react to exceptions, analyse and recommend cargo strategy for difficult or disrupted corridors, and advise commercial teams on new contracts. The specialist who used to spend the afternoon comparing invoice quantities to packing lists spends it telling sales which L/C clauses to push back on before a contract is signed. Once routine review is handled, the examiner can focus on the work that actually needs a person. ## What "around 70%" is made of - Workability review on arrival replaces the back-and-forth with production and logistics with a short list of clauses to amend. - Document generation from the credit removes most preparation time and the re-keying errors that used to trigger a second pass. - The pre-check runs in minutes and routes only its findings to a person, so clean presentations go straight to the bank. - Fewer refusals means fewer courier loops, fewer re-presentations, and fewer conversations with buyers about waivers. ## How the number was measured We did not ask the team how much faster it felt. We compared the hours logged against letters of credit in the months before Validator with the hours logged after the team had settled into the new workflow, on a comparable volume and mix of corridors. The measure covers the whole cycle from credit arrival to bank acceptance, including the rework loops that used to follow a refusal, because a tool that speeds up preparation but leaves refusals unchanged has not saved the team anything real. Refusals fell as well, which is where a good part of the saving comes from: a presentation that is accepted first time carries no courier loop, no re-presentation fee and no second examination. ## What did not change The team is the same size. The examiner with twenty years of corridor knowledge is still there, and still the final authority on anything unusual. What changed is the shape of the day. Routine credits on familiar corridors move through workability, generation and pre-check with a short review of the findings rather than a document-by-document read. The hours that used to go into comparing invoice quantities against packing lists now go into the conversations that need an experienced person: a buyer asking for terms the plant cannot meet, a carrier that keeps misstating the port of loading, a new corridor nobody has shipped through before. ## Key takeaways - Around 70% less effort per L/C, measured on a live client's presentations. - The saving comes from removing routine review, not from removing the examiner. - The recovered time went to exceptions, corridor strategy and advising commercial teams. Want the case study and the practical recommendations on how the client achieved the 70% improvement? [Contact us](https://www.loamist.com/contact.html) and we will send you a copy. --- URL: https://www.loamist.com/blog/client-logic-fenced-and-owned/ # Client Logic, Fenced and Owned: Whose Data Is It, and Where Does It Go? > What Validator learns from a client, corridor rules, counterparties and standards, is assigned to that client as IP. Never trains the general model. Source: https://www.loamist.com/blog/client-logic-fenced-and-owned/ Published: 2026-10-06 · How it works · By Nick Pachnev, Senior Advisor The most common objection we hear is about client data. Whose is it, and where does it go? ## Three layers of knowledge Validator's examination knowledge has three layers, and it matters which is which. - **Industry.** [UCP 600](https://library.iccwbo.org/), [eUCP](https://library.iccwbo.org/), [ISBP 821E](https://library.iccwbo.org/), and the general practice of documentary credit examination. Public, shared, and the same for every client. - **Corridor.** How specific ports, carriers, inspection agencies and issuing banks behave. Learned across the market and shared where it is general knowledge. - **Your product and process.** Your goods descriptions, your counterparties, your document suppliers, the examination standards your team applies, and the patterns in your own presentations. This layer is yours alone. ## Fenced by architecture, owned by contract The logic Validator learns from a client, such as corridor rules, counterparty patterns and examination standards, is legally assigned to that client as their IP. It is never used to train the general model. It never reaches another client. We made that choice deliberately and built it into Loamist's foundational architecture: the isolation is a property of how the system is constructed, not a policy layered on afterwards. The ownership is contractual. Your logic is yours, assigned to you by contract. If the relationship ends, it goes with you. ## Human-readable, exportable, inspectable We also store client logic in a human-readable format that the client can export and inspect at any time. The logic is not locked inside a black box, or inside model weights nobody can read. It is transparent and readily accessible. A documentation manager can open it and see, in plain language, what Validator believes about their corridors and counterparties, and correct it where it is wrong. That transparency is also what makes the ownership meaningful. IP you cannot read is a legal abstraction. IP you can export and audit is an asset. ## What this means in a procurement conversation The questions come in a predictable order, and the answers are short. Is our data used to train your model? No: logic learned from your transactions never reaches the general model or another client. Who owns what the system learns? You do, by contract, as your IP. Can we see it? Yes, in a human-readable format you can export at any time. Can we take it with us? Yes; if the relationship ends, your logic goes with you. Is the isolation a policy or a design? A design: the boundary is a property of the architecture, and Validator is [SOC 2](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2) certified, so the controls around it are independently audited rather than asserted. The reason we can answer that quickly is that we settled the questions before writing the first line of the learning layer. Corridor rules, counterparty patterns and examination standards are the most commercially sensitive thing an exporter's documentation team knows. A vendor that treats them as training data is asking to be paid in the customer's competitive advantage. We would rather be paid in subscription fees. ## Key takeaways - Industry and corridor knowledge is shared; product and process logic is isolated per client. - Client logic is assigned to the client as IP by contract and never trains the general model. - It is stored in a human-readable, exportable format the client can inspect at any time. See how Loamist fences and owns client logic by design: [book a walkthrough](https://www.loamist.com/contact.html). ## Frequently asked questions ### Is our transaction data used to train Loamist's general model? No. Logic learned from a client's transactions is legally assigned to that client as their IP, is never used to train the general model, and never reaches another client. ### Can we see what Validator has learned about us? Yes. Client logic is stored in a human-readable format that the client can export and inspect at any time. --- URL: https://www.loamist.com/blog/explainability-means-credibility-lc-automation/ # Explainability Means Credibility: an L/C Finding You Cannot Trace Is One You Cannot Trust > A flagged discrepancy with no reason makes the examiner redo the work. Validator cites the document, the field, the UCP 600 or ISBP rule, and your practice. Source: https://www.loamist.com/blog/explainability-means-credibility-lc-automation/ Published: 2026-09-24 · How it works · By Nick Pachnev, Senior Advisor An answer you cannot explain is an answer you cannot trust. Black-box logic creates more work than it saves when automating a compliance decision. If a system flags a discrepancy but cannot say why, an examiner has to redo the work to verify it. The automation saved nothing. It added a step. ## What a useful finding contains Loamist Validator explains every decision. Each finding carries four things: - **The rule or practice it applied.** Not "non-compliant", but which article, which paragraph, which practice. - **The exact document.** Bill of lading, third original. Insurance certificate, page two. - **The exact detail.** The field, the value found, and the value expected, side by side. - **The source of the expectation.** Whether the expected value comes from the credit, from another document, or from the exporter's own established practice. ## Two sources of authority Validator cites the external standard: [UCP 600](https://library.iccwbo.org/), [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/). That is the rulebook every bank examiner works from, and a citation to it is something the examiner can look up and agree or disagree with in seconds. It also cites the company's own practices, learned from past transactions. Many examination decisions are not in any rulebook. Whether a particular issuing bank accepts a shipping mark abbreviation, how a specific inspection agency words a certificate, which of two acceptable transport document layouts a given corridor uses: these are learned from what this exporter has presented and what the bank did with it. Validator names that source too. Every decision traces back to both the rule and the exporter's established way of working. When the two disagree, the finding says so, and the examiner makes the call with the evidence in front of them. ## Why this is the whole product, not a feature Explainability is what turns accuracy into throughput. A 99% accurate system that cannot show its reasoning still requires a human to verify each finding, because the human cannot tell which 1% is wrong. A system that shows its reasoning lets the examiner verify a finding in seconds, act on the clean ones without re-checking, and correct the rare miss with a reason attached, which then improves the next examination. Credibility is not a matter of the number. It is a matter of whether the number can be inspected. ## The audit trail is a by-product There is a second beneficiary of a fully traced finding, and it is not the examiner. When a bank refuses a presentation, or a buyer disputes a waiver, the exporter needs to show what was checked, against which rule, and what the documents said at the time. A decision trace that names the document, the field, the rule and the practice is exactly that record, produced as a side effect of doing the examination properly. It also makes internal review possible: a documentation lead can sample findings and confirm the reasoning without re-examining the presentation. ## Key takeaways - A flag without a reason costs examiner time instead of saving it. - A useful finding names the rule, the document, the field and the source of the expectation. - Citing both the external standard and the exporter's own practice is what makes a finding verifiable in seconds. If you want to see a full decision trace on one of your own letters of credit, [book a Validator demo](https://www.loamist.com/contact.html). We will run a live discrepancy check and show the exact rule and document behind every finding. Or [try Validator for free](https://www.loamist.com/lc-check.html), no credit card required. --- URL: https://www.loamist.com/blog/freight-accessorial-charges-where-leakage-hides/ # Accessorials Are Where Freight Leakage Hides: Auditing the Charges You Never Agreed To > 3% to 8% of freight spend is lost to billing errors, and most of it is not the base rate. Fuel, liftgate and peak-season fees are the highest-error lines. Source: https://www.loamist.com/blog/freight-accessorial-charges-where-leakage-hides/ Published: 2026-09-22 · Discrepancy cost · By Nick Pachnev, Senior Advisor Most freight overspend does not come from the rate you negotiated. It comes from the charges you never agreed to in the first place. Industry benchmarks estimate that 3% to 8% of freight spend is lost to billing errors. The base freight rate is rarely where shippers lose money. The accessorials are. ## The highest-error category on the invoice Fuel surcharges. Residential delivery fees. Liftgate charges. Peak-season surcharges. Detention and demurrage. Redelivery. They are discretionary, numerous, and rarely pre-agreed in writing. They also have the most errors of any freight invoice category, and they often account for a large share of total freight spend. They slip through for a simple reason. A base rate is one number, negotiated once, and easy to check. Accessorials are dozens of small numbers, each applied by a carrier's billing system under its own rules, on invoices that nobody reads line by line because there are too many of them. A 6% fuel surcharge applied to a lane contracted at 4% is invisible unless someone is checking every line against the agreement. ## Audit every fee against what you agreed Validator audits invoiced fees against published tariffs and negotiated rate agreements. It flags variances, duplicate charges, and non-contracted fees for review. It gives the team the evidence to hold vendors accountable: the invoice line, the contracted value, and the difference, ready to attach to a dispute. It flags for review; it does not dispute for you. Validator surfaces the variance and your team decides. It is a cost-recovery and vendor-accountability tool, not a replacement for the relationship with your carriers. ## Why this belongs next to L/C examination A freight invoice is a document set checked against an agreement, which is the same job as examining a presentation against a credit. The rate agreement plays the role of the letter of credit, the tariff plays the role of the rulebook, and the invoice lines are the fields to be compared. The skills Validator applies to a bill of lading, reading a value, normalising it and comparing it against the governing text with the source cited, transfer directly. Exporters who already run their L/C documents through Validator get the freight audit on the same platform, against the same carriers, with the same style of evidence. ## The carousel The eight slides that went with this post on LinkedIn are below. You can [download the carousel as a PDF](https://www.loamist.com/blog/assets/loamist-freight-fee-audit-carousel.pdf). Slide 1: most freight overspend isn't the rate you negotiated. 1 / 8 Slide 2: the rate isn't where you lose money; the accessorials are. 2 / 8 Slide 3: 3 to 8 percent of freight spend is lost to billing errors, an industry benchmark. 3 / 8 Slide 4: where it hides, fuel surcharges, residential delivery, liftgate, peak-season surcharges. 4 / 8 Slide 5: why they slip through, the highest-error category, rarely checked line by line. 5 / 8 Slide 6: the fix, audit every fee against tariffs and rate agreements. 6 / 8 Slide 7: flagged for review, not disputed for you; your team decides. 7 / 8 Slide 8: your next step, pull your last three freight invoices and book a demo. 8 / 8 ## Key takeaways - Leakage lives in accessorials, not the negotiated base rate. - They are the highest-error invoice category because they are numerous, discretionary and rarely checked line by line. - Line-level audit against the rate agreement recovers cost and gives your team evidence, while leaving the dispute decision with you. Pull your last three freight invoices and [book a demo](https://www.loamist.com/contact.html). We will let Validator check the accessorial lines against your rate agreement. ## Frequently asked questions ### What are accessorial charges? Fees added to a freight invoice on top of the base rate for extra services or conditions: fuel surcharges, residential delivery, liftgate, detention, peak-season surcharges and similar. They are often discretionary and rarely agreed line by line in advance. ### How much do freight billing errors cost? Industry benchmarks put the loss at 3% to 8% of freight spend. That is a benchmark, not a Loamist guarantee; the figure for a given shipper depends on carrier mix and how tightly accessorials are contracted. --- URL: https://www.loamist.com/blog/what-export-lc-workability-means/ # What Export L/C Workability Means, and Why Compliant Is Not the Same as Workable > A workability check asks whether L/C terms can be met with this cargo, corridor and shipment window before production starts. Compliance checks come too late. Source: https://www.loamist.com/blog/what-export-lc-workability-means/ Published: 2026-09-17 · Workability · By Nick Pachnev, Senior Advisor A workability check is the first step in the export L/C review process. It answers one question: can these terms actually be met, given this cargo, this corridor and this shipment window, before production is committed? A tight latest-shipment date, a conflicting clause, or a document requirement no one can satisfy is far cheaper to catch now than after the goods have shipped. ## The cost of getting it wrong is measurable Roughly 65% to 80% of documentary presentations under letters of credit are rejected on first submission for discrepancies, and each rejection carries fees, delays and payment risk. Many of those discrepancies trace back to terms that were never workable in the first place. The documents did not fail. The credit asked for something the shipment could not deliver. ## Uncurable discrepancies are the real exposure A workability check also reduces the risk of uncurable discrepancies: late shipment, an expired credit, and quantity or goods mismatches. You cannot correct these after the fact. Once a discrepancy is uncurable, the issuing bank is no longer obligated to pay, and the letter of credit becomes a commercial renegotiation rather than a bank-payment instrument. If the L/C was confirmed, that confirmation fee is now wasted, because an uncurable discrepancy turns the transaction into an open-account sale. The applicant holds the leverage. In our analysis, the exporter's exposure can range from a single-digit percentage to a substantial share of the L/C value, depending on cargo control and resale economics. Custom-manufactured goods and a soft market are the worst case. ## Compliant is not the same as workable | | Workability check | Compliance check only | | --- | --- | --- | | Question asked | Can these terms be met? | Are the documents compliant? | | Timing | Before production is committed | After the goods have shipped | | Evaluation approach | Based on cargo and corridors | Pass or fail against the L/C and the rules | | Discrepant presentations | Unworkable terms caught up front | 65% to 80% first-presentation rejections | | Negotiation leverage | Exporter | Importer, especially for custom goods or a soft market | ## Workability is most useful when it is intelligent A generic pass or fail against the rules will tell you the credit is internally consistent. It will not tell you whether your plant can make the latest shipment date, whether your carrier serves the named port on that routing, or whether the inspection agency in the loading port will sign the certificate as worded. Validator learns an exporter's real capabilities from prior shipments. It gives recommendations tuned to the specific cargo types and trade corridors that exporter actually runs: not a generic verdict, but a read on whether this exporter can meet these terms. In one engagement, Validator achieved 99% client-specific workability accuracy by learning from four months of the exporter's historical transactions. The rules were the same as everyone else's. The judgement about what this company could deliver was the part that had to be learned. ## Key takeaways - Workability asks whether the credit can be met; compliance asks whether documents match it. Only the first question can be asked before shipment. - Uncurable discrepancies remove the bank's obligation to pay and waste any confirmation fee. - A workability check earns its keep when it knows your cargo and corridors, not just the rulebook. The best time to fix an unworkable L/C is before you accept it. [Try Validator's free workability check](https://www.loamist.com/lc-check.html), no credit card required, or [contact us](https://www.loamist.com/contact.html) to see the 99% result on your own credits. ## Frequently asked questions ### What is an LC workability check? A review of a letter of credit's terms, done when the credit arrives, to confirm they can be met with the actual cargo, corridor and shipment window before production is committed. It looks for deadlines, documents and clauses that cannot be satisfied as drafted. ### How is workability different from compliance checking? Compliance checking asks whether finished documents comply with the credit, after shipment. Workability asks whether the credit itself can be complied with, before anything is produced or shipped. ### What happens if a discrepancy cannot be cured? The issuing bank is no longer obliged to pay. Payment depends on the applicant waiving the discrepancy, which turns the credit into a commercial negotiation, and any confirmation fee paid is wasted. --- URL: https://www.loamist.com/blog/sibos-2026-miami-book-a-session/ # Sibos 2026 in Miami: Book a Session on Our Live L/C Study > Book a session at Sibos 2026, 28 Sep to 1 Oct: thousands of export L/Cs tested live, plus a before-and-after look at the Strait of Hormuz disruption. Source: https://www.loamist.com/blog/sibos-2026-miami-book-a-session/ Published: 2026-09-16 · Company · By Nick Pachnev, Senior Advisor Loamist is bringing a real, live study of thousands of export L/Cs to [Sibos 2026](https://www.sibos.com/) in Miami. Pete Christensen and Nick Pachnev will be at the Miami Beach Convention Center from 28 September to 1 October. ## The study We ran an AI engine against thousands of real letters of credit transactions spanning all major trade corridors. We checked actual L/Cs for workability against [UCP 600](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/), and verified documentation against each credit's terms. Every result is reproducible: the same engine, the same rules, the same method on every credit, so the findings can be interrogated rather than admired. ## The Hormuz before-and-after The study also includes a before-and-after dataset analysis of the Strait of Hormuz disruption and its impact on L/C workability, presentation and payment cycles. When a corridor is disrupted, credits that were workable last month stop being workable: shipment dates slip past latest shipment, routings change the ports on the transport document, and presentation periods that assumed a direct sailing no longer hold. The data shows how quickly that propagates into refusals and delayed payment, and which clauses broke first. ## Fine-tuned engine versus general LLMs If you want to see a cost and accuracy comparison of a fine-tuned AI engine against general-purpose large language models on the same presentations, and how the Hormuz disruption affected each, book a session. We will show the numbers, the method and the misses on both sides. ## What a session covers Thirty minutes, structured around whatever you bring. A typical session runs in three parts. We open with the headline findings from the study: refusal rates by corridor, the clauses that most often make a credit unworkable, and how long a discrepant presentation actually delays payment in the data. Then we go to the Hormuz before-and-after and show which terms failed first when transit times moved. We close by running Validator live on a credit, yours if you bring one, and walking through the decision trace behind each finding so you can judge the reasoning rather than the verdict. ## What to bring - **A letter of credit**, ideally one that gave your team trouble. A redacted [MT700](https://www.swift.com/standards) is enough for a workability read. - **A document set**, if you want to see a full pre-check rather than a workability check alone. - **A question about a corridor.** If your exporters or clients ship through a route that has been disrupted this year, we can look at how credits on comparable routes behaved in the dataset. If you would rather not share documents, we run the same walkthrough on credits from the study. ## Why a live study rather than a demo Every vendor at Sibos will show a demo, and every demo works. A study on live credits is different in kind: the credits were not chosen to flatter the engine, the outcomes are the banks' real decisions, and the misses are in the data alongside the hits. We think that is the only honest way to talk about accuracy in document examination, and it is the conversation we want to have with trade operations people who know how the work actually goes wrong. ## Book a meeting Book your meeting at [loamist.com/sibos](https://www.loamist.com/sibos). If you would rather just find us, we are on the floor all four days. --- URL: https://www.loamist.com/blog/trust-is-the-product-99-percent-precheck-accuracy/ # Trust Is the Product: Why We Hold Validator to 99% Pre-Check Accuracy on Live Transactions > An L/C pre-check you cannot trust is worse than none: missed discrepancies or phantom flags both send you back to a specialist. Accuracy is the product. Source: https://www.loamist.com/blog/trust-is-the-product-99-percent-precheck-accuracy/ Published: 2026-09-15 · How it works · By Nick Pachnev, Senior Advisor An export L/C pre-check you cannot trust is worse than no pre-check at all. Miss discrepancies and you present with false confidence. Flag phantom ones and your team spends more time investigating problems that are not there. Either way, you are back to a document specialist doing the whole job by hand, now with an extra tool to argue with. ## The two ways an automated check fails An examination tool can be wrong in two directions, and both are expensive. - **It misses a real discrepancy.** The team trusts the green light, presents, and gets a refusal. Worse than no tool, because the tool replaced the human check that would have caught it. - **It flags something that is not a discrepancy.** Each phantom finding costs an examiner's time to investigate and dismiss. After a few dozen of those, the team stops reading the findings, and the tool is switched off in practice if not in name. A tool that is right 90% of the time sounds impressive until you realise that on a 40-document presentation with hundreds of checks, 10% wrong is dozens of findings to argue with per credit. ## The standard we hold ourselves to So we hold Validator to a hard standard: 99% pre-check accuracy, measured on live transactions, not demos. It is pre-trained on [UCP 600](https://library.iccwbo.org/), [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/), and on the exporter's own data. It is tested across thousands of live L/C examinations, and the measurement continues on every client's live presentations, because a number from a benchmark set tells you very little about a number from your corridor. ## What the number buys The payoff is what the number lets your team do: act on the output without re-checking it. That is the whole point. When a documentation team can present on Validator's clean result, and route only its findings to a person, examination effort drops. Our clients cut examination effort by around 60 percent and fully automate low-value presentations, the routine credits on familiar corridors that used to consume most of the day. Every finding also carries a decision trace to the rule or practice behind it, so on the rare occasion the tool is wrong, the examiner can see exactly why and correct it in seconds. That trace is what turns 99% into something a team can operate on rather than a number on a slide. ## Key takeaways - Both misses and phantom findings destroy the value of an automated pre-check. - 99% accuracy, measured on live transactions, is the threshold at which a team can act without re-checking. - Accuracy is not a feature. It is the product. [Book a demo](https://www.loamist.com/contact.html) and we will run a full pre-check on one of your recent presentations, or [try Validator for free](https://www.loamist.com/lc-check.html), no credit card required. ## Frequently asked questions ### How is 99% pre-check accuracy measured? On live client transactions, not demo data: Validator's findings on each presentation are compared with the outcome at the bank and the documentation team's review, across thousands of L/C examinations. ### Why does a pre-check need to be so accurate? Because the value of automation is acting on the output without re-checking it. If a team has to verify every finding, the automation has saved nothing. --- URL: https://www.loamist.com/blog/lc-tools-built-for-banks-not-corporates/ # You Are Not the Bank: Why L/C Verification Tools Miss the Exporter > Bank-side L/C software checks documents that already exist. By then the discrepancies are made. What a corporate-first platform does differently. Source: https://www.loamist.com/blog/lc-tools-built-for-banks-not-corporates/ Published: 2026-09-10 · Workability · By Nick Pachnev, Senior Advisor L/C verification tools were designed for banks to check documents, not for corporates to create them. Corporates are not banks. When bank software examines documents, the discrepancies already exist. ## Two very different jobs A bank's trade operations desk receives a finished presentation and asks one question: does this comply? The documents are fixed. The credit is fixed. The job is comparison, and the software built for it is comparison software. An exporter's documentation team has a different job that starts weeks earlier. Read the L/C. Check with production whether the shipment date holds. Check with logistics whether the routing works. Assemble documents from five sources. Present. And pay for the delay when the presentation bounces. Comparison is the last step of that job, and by the time it happens the expensive mistakes have been made. ## Where the exporter's tools are today Meanwhile, the party with the most at stake, the exporter waiting to be paid, runs on spreadsheets, checklists, and hard-to-find and hard-to-train expertise. The bank has an examination platform. The exporter has a shared drive, a template folder and one person who knows what "as per credit terms" actually means for this buyer. ## Corporate-first, by design Validator is the only L/C platform built corporate-first. It follows the exporter's timeline rather than the bank's: - **On arrival:** contract, sales order and workability review, so the credit is checked against what you actually agreed and can actually deliver. - **During preparation:** document generation from the credit and retrieval of third-party documents with precise instructions. - **Before submission:** a full pre-check of the complete set, so the bank sees a presentation that has already been examined to the bank's own standard. The bank still examines. But it examines documents that were built to comply, checked before they left, and accompanied by a trace of why each one passes. ## What corporate-first looks like day to day The difference is easiest to see in a single credit's life. A bank-side tool meets that credit once, at the end, when the document set arrives for examination. A corporate-first platform meets it four times. On arrival, it reads the [MT700](https://www.swift.com/standards) against the sales order and the exporter's own history and returns the clauses to amend while an amendment is still one message to the buyer. During preparation, it drafts the invoice, packing list and certificates from the credit's data and writes the instructions the carrier and the inspection agency need, so third-party documents come back right the first time. Before submission, it examines the complete set to the bank's own standard and shows the rule behind every finding. After the bank responds, it learns from the outcome, so the next credit on that corridor is checked with one more piece of judgment. None of that is available to a tool that only sees finished documents, because by then the decisions that created the discrepancies have already been made by someone else, weeks earlier, with no software in the room. ## Key takeaways - Bank-side tools examine after documents exist; the exporter's losses happen before that. - The exporter's timeline runs from L/C arrival to presentation, and every stage needs tooling. - A corporate-first platform moves examination to the start of the process instead of the end. Built for corporates. [Book a demo](https://www.loamist.com/contact.html), or [try the free workability check](https://www.loamist.com/lc-check.html) on a credit you have now. --- URL: https://www.loamist.com/blog/clean-at-the-source-generate-lc-documents/ # Clean at the Source: Generate L/C Documents From the Credit Instead of Fixing Them Later > Prepare, check and fix, or generate the documents from the L/C so they start compliant. Most of the industry does the first. The second is cheaper. Source: https://www.loamist.com/blog/clean-at-the-source-generate-lc-documents/ Published: 2026-09-08 · Operations · By Nick Pachnev, Senior Advisor The cheapest L/C discrepancy is the one that never gets typed. There are two ways to create a compliant document set. One: prepare the documents, check them, and fix what is wrong. Two: generate the documents from the L/C itself, so they start as compliant in the first place. Most of the industry does the first. ## Re-keying is the discrepancy factory Every invoice, packing list, transport document and certificate includes data the L/C already specifies. The goods description in field 45A. The applicant's name and address in 50. The ports in 44E and 44F. The credit number itself, which most credits require on every document. Re-keying that data by hand, into templates that were built for a different credit, is what creates discrepancies. The information was correct in the credit. It became wrong in the copying. A typical export document set carries the same twenty or thirty data points across five or six documents. That is well over a hundred manual transcriptions per presentation, each of which a bank examiner will compare against the credit and against each other. ## Generate, do not transcribe Loamist Validator drafts your own documents from the credit's requirements: the commercial invoice, the packing list, the beneficiary's certificates and declarations. The goods description is the credit's goods description. The consignee is the party the credit names. The credit number is populated, not typed. Where the credit has a quirk, such as a specific certification wording or a required reference, the generated document carries it because the credit did. For documents you do not issue yourself, Validator creates detailed instructions for the third party. (The ICC Banking Commission's [Technical Advisory Briefing No. 16](https://library.iccwbo.org/content/tfb/BRIEFINGS/20260727_Briefing_No_16_Third_Party_Documents.pdf) sets out how third-party documents are examined and accepted under UCP 600, which is the standard those instructions are written to.) The carrier gets the exact notify party, port names and marks the bill of lading must show. The inspection agency gets the certificate wording the credit demands, so it is issued right rather than reissued later. Then Validator pre-checks the complete set, your documents and theirs, before presentation. ## Cheaper and faster, not just cleaner Getting the documents right at the source is cheaper and faster than fixing them later. A generated invoice takes seconds and needs no second pass. A hand-prepared invoice takes an hour, then another hour of checking, then a courier if the checking missed something. The compliance benefit is real, but the throughput benefit is what documentation teams notice first. ## Where the credit's data ends up A useful exercise is to take one L/C and count the destinations of each field. The goods description in field 45A appears on the commercial invoice, usually on the packing list, often on the certificate of origin and sometimes on the insurance document. The credit number appears on every document. The applicant's name and address appear on the invoice and the transport document's consignee or notify block. Ports and the latest shipment date govern the transport document. A credit with thirty data points can easily generate over a hundred placements across the set, and under [UCP 600](https://library.iccwbo.org/) article 14(d) every one of them is compared with the credit and with every other placement. Generation from the credit collapses that hundred to one: the value is right in the credit, so it is right everywhere it lands. ## Key takeaways - Most document discrepancies are transcription errors of data the credit already contains. - Generating documents from the credit removes the transcription step, and with it most of the errors. - Third-party documents cannot be generated, but they can be instructed precisely, which is the next best thing. For the fields a compliant invoice must carry, and the ways they usually go wrong, see [how to prepare a compliant commercial invoice under a letter of credit](https://www.loamist.com/commercial-invoice-letter-of-credit-compliance.html). --- URL: https://www.loamist.com/blog/one-character-can-freeze-a-million-dollars/ # One Character Worth $1 Million: Why Cross-Document Consistency Breaks Presentations > A zero typed as O. A vessel name spelled two ways. One conflict between documents means a refusal and 30 to 45 days of delayed payment on shipped cargo. Source: https://www.loamist.com/blog/one-character-can-freeze-a-million-dollars/ Published: 2026-09-04 · Discrepancy cost · By Nick Pachnev, Senior Advisor One wrong character can freeze a million dollars for a month. A zero typed as the letter O. A transposed invoice digit. A vessel name spelled two ways in two documents. A single conflict can be enough to trigger a refusal, and then 30 to 45 days of delayed payment for cargo that has already shipped. ## Why one character is enough [UCP 600](https://library.iccwbo.org/) article 14(d) is short and unforgiving: data in a document must not conflict with data in that document, any other stipulated document, or the credit. It does not have to be identical, but it cannot conflict. The ICC Banking Commission's [Technical Advisory Briefing No. 12](https://library.iccwbo.org/content/tfb/BRIEFINGS/20241113_TABriefing_No_12_Read_in_Context.pdf) explains how "read in context with" is meant to be applied, and it does not rescue an identifier that differs. A vessel named "MV Oceanline" on the bill of lading and "MV Oceanliine" on the insurance certificate is a conflict. A checker cannot know which is right, and the bank is not permitted to guess. [ISBP 821E](https://library.iccwbo.org/) softens this slightly for typing errors that do not affect meaning. "Mashine" for "machine" passes. But a wrong digit in an invoice number, a container number or a quantity changes meaning, and a vessel name is an identifier, not a word. Most of the character-level errors that actually occur fall on the wrong side of that line. ## Where the characters come from The same data is typed into a document set four, five or six times. The vessel name goes on the bill of lading (by the carrier), the insurance certificate (by the insurer or the exporter), the packing list and the beneficiary certificate (by the exporter), and often the commercial invoice. Each is a separate keystroke by a separate person from a separate source. Every one of those is an opportunity for the letter O to become a zero. ## Humans are the wrong tool for this job An experienced checker reading a 40-page presentation for conflicts is doing a task that humans are measurably bad at: sustained, character-level comparison across documents under time pressure. Attention drifts. The eye autocorrects "Oceanliine" to what it expects. Machines, when properly built, trained and monitored, do not. They compare the string, not the impression of the string. Loamist Validator cross-checks every field across the full document set, character by character, before anything goes to the bank. It reads the value on each document, normalises it, compares it with every other occurrence and with the credit, and reports each conflict with the two documents and the two values side by side. ## Key takeaways - A single data conflict between documents is a refusable discrepancy under UCP 600 article 14(d). - Re-keying the same value into several documents is the root cause; each keystroke is a chance to introduce a conflict. - Character-level cross-checking is exactly the kind of task software does better than a tired examiner. The bill of lading is where most identifier conflicts surface. Our [bill of lading compliance guide](https://www.loamist.com/bill-of-lading-letter-of-credit-compliance.html) covers the fields that must agree, and with what. ## Frequently asked questions ### Does every typo cause an LC discrepancy? No. ISBP 821E allows a misspelling or typing error that does not affect the meaning of a word (for example 'mashine' for 'machine'). A variation that changes meaning, or makes the data conflict with another document, is a discrepancy under UCP 600 article 14(d). ### Which documents are checked against each other? All of them. UCP 600 article 14(d) requires that data in a document, read in context with the credit, the document itself and international standard banking practice, does not conflict with data in that document, any other stipulated document, or the credit. --- URL: https://www.loamist.com/blog/loamist-at-sibos-2026-live-lc-study/ # Loamist at Sibos 2026: a Live Study of Thousands of Export Letters of Credit > Loamist is at Sibos 2026 in Miami, 28 Sep to 1 Oct, with thousands of live L/C transactions checked for workability against UCP 600, eUCP and ISBP 821E. Source: https://www.loamist.com/blog/loamist-at-sibos-2026-live-lc-study/ Published: 2026-09-01 · Company · By Nick Pachnev, Senior Advisor Loamist is attending [Sibos 2026](https://www.sibos.com/) in Miami from 28 September to 1 October. Pete Christensen and Nick Pachnev will be on site for all four days. ## What we are bringing We are bringing a live study to Miami: thousands of live L/C transactions, with findings measured under a repeatable methodology. Not a curated demo set. Real credits, real document sets, across all major trade corridors, examined the same way every time so the results can be compared and challenged. ## What Validator is Validator is a documentary credit examination engine. It checks export letters of credit for workability against [UCP 600](https://library.iccwbo.org/), [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/), flags the terms that cannot be satisfied as drafted, and then checks the document set against the credit. Every finding carries a decision trace back to the article or practice it relies on, so a checker can accept or reject the result rather than take it on trust. For a bank audience that last point matters most. An automated examination result is only useful to a trade operations team if it can be verified faster than it can be redone. A trace to UCP 600 article 14 or an ISBP paragraph, with the document and field named, is what makes that possible. ## What we will show - How the engine performed against live credits and global shipping corridors, with the methodology. - A cost and accuracy comparison of a fine-tuned examination engine against general-purpose large language models on the same presentations. - How a major shipping disruption changed workability, presentation and payment cycles in the dataset, before and after. ## How the study was run Every credit in the dataset went through the same three passes. First, the L/C text itself was read for workability: shipment and expiry dates against the corridor's realistic transit and production times, the document list against what the named parties can actually issue, and the clauses against UCP 600 and ISBP 821E for internal contradictions. Second, each document set was examined against the credit, field by field and across documents, with every finding tied to the article or practice it relies on. Third, the results were compared with what happened at the bank, so the accuracy figures are measured against real outcomes rather than against our own opinion of what a checker should have found. Because the method is identical for every credit, the numbers can be sliced by corridor, by issuing bank, by document type and by month, and any single finding can be pulled up and argued about. That is the part we most want to do in person. ## Who should book - **Trade operations and document-checking leads** who want to see how an automated examination result can be verified faster than it can be redone. - **Trade product and innovation teams** weighing a fine-tuned examination engine against a general-purpose model, and who want the cost and accuracy numbers side by side. - **Corporate trade-finance and treasury teams** whose exporters carry the refusal cost, and who want to know which clauses break first when a corridor is disrupted. ## Book a time If you are attending and want to see how the engine performed against live credits, book a session with Pete or Nick at [loamist.com/sibos](https://www.loamist.com/sibos). Sessions are 30 minutes and we are happy to run Validator on a credit you bring. --- URL: https://www.loamist.com/blog/discrepancies-are-born-in-the-lc/ # Most L/C Discrepancies Are Born Before You Produce a Single Document > Unmeetable deadlines, certificates nobody issues, terms that contradict the contract: they are in the L/C. The day it arrives is the cheapest day to fix it. Source: https://www.loamist.com/blog/discrepancies-are-born-in-the-lc/ Published: 2026-08-27 · Workability · By Nick Pachnev, Senior Advisor Most discrepancies are born before you produce a single document. They are in the L/C itself: a deadline you cannot meet, a certificate your inspector cannot issue, terms that contradict the sales contract. By the time you are preparing documents, you are not preventing those discrepancies. You are inheriting them. ## What a defective credit looks like The credit arrives by [MT700](https://www.swift.com/standards) and looks routine. Somewhere in fields 44C to 47A there is a problem that nobody will notice until a document checker does: - A latest shipment date three weeks out for goods with a five-week production lead time. - A phytosanitary or inspection certificate worded in a way no agency in the loading port will sign. - A goods description copied from an old contract, not the one you actually signed. - A port of discharge that the named carrier does not serve on the required routing. - A presentation period of five days for originals that take a week to reach the bank. None of these can be fixed by preparing documents carefully. The documents will be discrepant because the credit asked for something that cannot be delivered. ## The price of the fix rises every week The time to fix an L/C is the day it arrives, while an [amendment](https://library.iccwbo.org/content/tfb/BRIEFINGS/20240805_TA_Briefing_No_10_Amendments.pdf) is still one message to your buyer. An amendment at that point runs roughly USD 50 to 200 in bank fees. The same defect found at presentation draws a discrepancy fee of USD 50 to 150, charged per discrepancy and again on every re-presentation. The fee is the smallest part of it. A discrepant presentation hands your buyer a reason to delay payment or renegotiate the price. Compare the two conversations. "Please amend field 44C to 30 days later" is a routine request made from a position of strength, before you have spent anything. "We shipped, the documents are discrepant, please waive" is a request made after the cargo has left, with the buyer holding every card. ## Reading the L/C on arrival Validator reads the credit the moment you receive it and tells you what is workable and what will create problems, before you commit to production. It checks the terms against [UCP 600](https://library.iccwbo.org/), [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/), and against what it has learned about your cargo, your corridors and your document suppliers from past shipments. The output is a short list of clauses to amend, each with the reason, ready to forward to the buyer. ## Key takeaways - Many discrepancies are structural defects in the credit, not errors in the documents. - An amendment on day one costs about what a single discrepancy fee costs, and it fixes the problem permanently. - Leverage moves from exporter to buyer the moment the goods ship. Review before that point. [Try the free workability check](https://www.loamist.com/lc-check.html) on a credit you have in hand, or read our [10-point pre-shipment L/C review](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) for the manual version. ## Frequently asked questions ### How much does an LC amendment cost? Bank amendment fees typically run USD 50 to 200 per amendment. That is comparable to a single discrepancy fee, but an amendment fixes the problem once, while a discrepancy fee recurs on every re-presentation and comes with delay. ### When should I review a new letter of credit? The day it arrives, before production or booking is committed. That is when an amendment is still a single message to your buyer and the leverage is still yours. --- URL: https://www.loamist.com/blog/lc-document-specialist-retiring-institutional-knowledge/ # The Specialist Who Clears Your Export Documents Is Close to Retirement > One person can read a 20-page L/C and spot the refusal. That judgment took decades and is leaving faster than it is replaced. How to keep it in the business. Source: https://www.loamist.com/blog/lc-document-specialist-retiring-institutional-knowledge/ Published: 2026-08-25 · Operations · By Nick Pachnev, Senior Advisor Every exporter has one. A document specialist who can read a 20-page letter of credit and identify which line will trigger a refusal. That judgment takes decades to build. One or two people in the business hold it, and they are leaving the workforce faster than they are being replaced. ## The numbers have not moved The [ICC Banking Commission](https://iccwbo.org/business-solutions/banking-commission/) estimates that between 65% and 80% of documents are refused on first presentation under documentary credits ([Technical Advisory Briefing No. 3, 27 June 2022](https://library.iccwbo.org/content/tfb/BRIEFINGS/20220627_TA_Briefing_No3_reducing_discrepancy_rates.pdf)). The Commission's [full series of briefings](https://library.iccwbo.org/tfb/tfb-briefings.htm) is free to read and worth a bookmark for any documentation team. That rate has not fallen since [UCP 600](https://library.iccwbo.org/) took effect in 2007. Refusal does not usually stop payment, but it adds delay, discrepancy fees, rework on every affected shipment and occasional renegotiation. Read those two facts together. The rules are stable and public. The failure rate is stable and high. The variable is the human capacity to apply the rules, correctly, under time pressure, to whatever the shipping market is doing this month. ## What the specialist actually knows The retiring examiner is not valuable because they have memorised UCP 600. They are valuable because they know things that are nowhere in the rules: - Which inspection agency in a given port will refuse to sign a certificate worded the way this credit demands. - How a particular issuing bank reads "shipping marks as per invoice" when the packing list disagrees. - Which carriers routinely misstate the port of loading on a transhipment routing, and how to word the instruction so they do not. - What went wrong on this buyer's last three credits, and which clause caused it. That knowledge is learned from transactions, not textbooks. When the person leaves, it leaves with them. The next hire inherits the checklists and none of the judgment. ## Holding examination knowledge in software Validator is our answer to that problem. It holds the examination knowledge in software. It is pre-trained on UCP 600, [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/), so the public part of the job is covered from day one. Then it learns each client's cargoes, corridors and recurring document patterns from their own transaction history, which is the part that used to live in one person's head. It has been tested across thousands of L/C examinations, and each finding is traced back to the rule or the client practice it relied on, so a less experienced checker can verify it rather than take it on trust. None of this removes the need for an experienced examiner. It changes what they spend their day on. Routine review is handled; the specialist's time goes to exceptions, difficult corridors, and teaching the system the judgement calls that still need a person. ## Key takeaways - Refusal rates of 65% to 80% have not improved in nearly two decades of stable rules. - The scarce asset is applied judgment about corridors, counterparties and documents, not knowledge of UCP 600 itself. - That judgment can be captured from transaction history and kept in the business when people move on. If your documentation team is one retirement away from a capacity problem, [book a demo](https://www.loamist.com/contact.html) and we will show how Validator learns a corridor from your past presentations. ## Frequently asked questions ### What does the ICC say about first-presentation refusal rates? The ICC Banking Commission's Technical Advisory Briefing No. 3 (27 June 2022), Reducing discrepancy rates under Documentary Credits, estimates that between 65% and 80% of documents are refused on first presentation under documentary credits. ### Does refusal mean the exporter is not paid? Usually not. Most refusals are cured and paid later. Refusal adds delay, discrepancy fees, rework on every affected shipment, and occasionally renegotiation. --- URL: https://www.loamist.com/blog/two-out-of-three-letters-of-credit-fail-first-presentation/ # Two Out of Three Letters of Credit Fail on First Presentation. It Does Not Have to Be This Way. > The ICC puts first-presentation refusals at 65% to 80%. Why exporters accept it, why they should not, and a workability checklist to stop it. Source: https://www.loamist.com/blog/two-out-of-three-letters-of-credit-fail-first-presentation/ Published: 2026-08-20 · Discrepancy cost · By Nick Pachnev, Senior Advisor Two out of three letters of credit fail on first presentation. If two out of three wire transfers failed, it would be a treasury emergency. In documentary trade, it is just another day. The [ICC](https://iccwbo.org/) puts first-presentation refusals at 65% to 80% ([Technical Advisory Briefing No. 3](https://library.iccwbo.org/content/tfb/BRIEFINGS/20220627_TA_Briefing_No3_reducing_discrepancy_rates.pdf), June 2022), and the figure has barely moved since [UCP 600](https://library.iccwbo.org/) took effect in 2007. ## The strange part is the acceptance Most exporters have made peace with it. Delays are expected and absorbed by working capital. Fees get paid without much argument. Rejection is treated as the normal outcome of a payment instrument whose entire purpose is certainty of payment. No other part of the finance function would tolerate a two-thirds failure rate on a routine process. ## Why it does not have to be this way Three things about a letter of credit are knowable in advance. - **The rules are public.** UCP 600, [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/) are published documents. The standard the bank will apply is not a secret. - **The credit is based on your commercial agreement.** The L/C in your hands should mirror the sales contract. Where it does not, you can see the conflict on day one. - **Your own history shows where things go wrong.** The same corridors, the same document types, the same counterparties produce the same discrepancies. Past presentations are a map of future refusals. Validator checks the full document set against exactly those three inputs: your transaction history, the credit's terms, and UCP 600, eUCP and ISBP 821E. Measured on live transactions, that reaches 99% pre-check accuracy. The first presentation should be the only one. ## The workability checklist The carousel that went with this post on LinkedIn walks through the checks that catch most refusals before production starts. The slides are below, and you can [download the carousel as a PDF](https://www.loamist.com/blog/assets/loamist-workability-checklist-carousel.pdf). Slide 1: Two out of three letters of credit fail on first presentation. 1 / 4 Slide 2: why exporters accept the refusal rate and why they should not. 2 / 4 Slide 3: the workability checklist to run the day an L/C arrives. 3 / 4 Slide 4: the first presentation should be the only one; try the free export workability check. 4 / 4 ## What the failure rate costs a business Put the ICC figure against a modest export book. An exporter presenting forty letters of credit a year at the low end of the range sees roughly twenty-five refused first time. Each refusal draws a discrepancy fee, a courier loop for corrected originals, and a payment delay that commonly runs 30 to 45 days on cargo already shipped. Finance carries that delay as working capital. Operations carries the rework. Sales carries the awkward conversation when a buyer uses the discrepancy to reopen the price. None of those costs appear on a single line, which is a large part of why the rate has been tolerated for so long: it is spread across three departments and never totalled. The same arithmetic explains why the first presentation should be the only one. Cutting the refusal rate from two in three to one in ten does not save a fee. It returns weeks of cash flow and dozens of hours of skilled time across the year, and it removes the buyer's most reliable lever for renegotiation. ## Run it on a real credit Use the checklist on your next L/C, or skip the manual pass and [try our free export workability check](https://www.loamist.com/lc-check.html). Upload the credit and Validator returns the terms that cannot be met as drafted, with the rule behind each one. For the long-form version, our [complete export L/C document checklist](https://www.loamist.com/export-lc-document-checklist-prevent-discrepancies.html) covers every document in the set. --- URL: https://www.loamist.com/blog/true-cost-of-a-rejected-lc-presentation/ # The Discrepancy Fee Is the Smallest Part of a Rejected L/C Presentation > A discrepant presentation costs 0.5% to 2% of shipment value once you add corrections, resubmission and 45 days of delayed payment. Uncurable ones cost more. Source: https://www.loamist.com/blog/true-cost-of-a-rejected-lc-presentation/ Published: 2026-08-18 · Discrepancy cost · By Nick Pachnev, Senior Advisor The discrepancy fee is the minor part of the total cost of a rejected presentation. The real costs are documents shipped back and forth, corrections, resubmissions, and payment delayed for up to 45 days. A single discrepant presentation can easily cost between 0.5% and 2% of the shipment's value. On thin-margin cargo, that can wipe out most of the profit. ## Where the money actually goes - **Fees.** USD 50 to 150 per discrepancy is typical, charged again on each re-presentation. Visible, but small. - **Rework.** Someone has to find the error, get the document reissued (often by a third party in another time zone), and courier originals back to the bank. - **Time.** Each loop adds days. Payment that should have landed at sight can slip 30 to 45 days on cargo that has already left the port. - **Working capital.** That delay is financed by the exporter. At current rates, a month of carry on a seven-figure invoice is a meaningful number on its own. - **Leverage.** A discrepant presentation hands the buyer a legitimate reason to delay payment or reopen the price. ## The greater exposure: discrepancies that cannot be cured Most discrepancies are curable. You correct the document, present again, pay the fee, absorb the delay. The dangerous category is the one where no correction can restore compliance. Once a latest shipment date has passed, a presentation period has expired, or an original document cannot be reissued, the presentation is discrepant for good. At that point payment depends entirely on the applicant's agreement to waive the discrepancies. If that decision is being made when the market has moved against the exporter, the loss can be much more than 2%. On perishable goods, or cargo manufactured to a single buyer's specification, the result can be a complete write-off. The letter of credit has quietly become an open-account sale, with the buyer holding the goods and the exporter holding the paperwork. ## Why the industry tolerates it The [ICC](https://iccwbo.org/) estimates that between 65% and 80% of presentations are rejected on first submission ([Technical Advisory Briefing No. 3](https://library.iccwbo.org/content/tfb/BRIEFINGS/20220627_TA_Briefing_No3_reducing_discrepancy_rates.pdf)). Most exporters treat that as the price of doing L/C business. It is not. It is the price of catching problems too late. A problem spotted while the L/C is being negotiated costs an email to the buyer. The same problem at presentation costs a fee, a fortnight, and a conversation you did not want to have. ## Moving the catch point earlier Loamist Validator is designed around that timing. It drafts L/C terms from purchase orders and commercial contracts before the credit is opened, performs a workability analysis the moment an L/C arrives, generates the documents from the credit so they start compliant, and runs a full pre-check before anything goes to the bank. Each stage moves the moment of discovery to a point where fixing the problem is still cheap. ## Key takeaways - Budget 0.5% to 2% of shipment value for a discrepant presentation, not the fee. - Uncurable discrepancies convert a bank undertaking into a buyer's option to pay. - The cost of a fix rises with every stage; the day the L/C arrives is the cheapest day to find it. For the specific defects behind most refusals, and how to stop each one, see our guide to the [top 10 letter of credit discrepancies](https://www.loamist.com/top-10-letter-of-credit-discrepancies-how-to-prevent.html). ## Frequently asked questions ### How much is a typical LC discrepancy fee? Banks commonly charge USD 50 to 150 per discrepancy, and again on every re-presentation. The fee is small relative to the delay and capital cost it signals. ### What is an uncurable discrepancy? A defect no corrected document can fix: the latest shipment date has passed, the presentation period or credit has expired, or an original document cannot be reissued. Payment then depends on the applicant waiving the discrepancy. --- URL: https://www.loamist.com/blog/validator-launch-ai-native-export-lc-platform/ # Introducing Validator: an AI-Native Platform for Export Letters of Credit > Loamist Validator is live: workability review on L/C arrival, document generation, and a full pre-check before the bank. Over $1B in live L/Cs in 2026. Source: https://www.loamist.com/blog/validator-launch-ai-native-export-lc-platform/ Published: 2026-08-13 · Company · By Nick Pachnev, Senior Advisor We just launched Validator, an AI-native platform for export letters of credit. We have run over $1B in live L/Cs through it so far in 2026, and we are finally ready to release it. ## Built for corporates Almost every L/C examination tool on the market was designed for a bank's trade operations desk, where the job is to check documents that already exist. Exporters live earlier in the timeline. They receive the credit, decide whether to accept it, produce the documents, and carry the payment risk when the presentation bounces. Validator is built for that side of the transaction. ## End to end, in three stages - **Workability review the moment the L/C arrives.** Validator reads the credit and flags the terms that cannot be met as drafted: a latest shipment date that is too tight, a document nobody in the corridor can issue, a clause that contradicts the sales contract. Amendments are cheap at this point; discrepancies later are not. - **Automated document generation and retrieval.** Invoices, packing lists and beneficiary certificates are drafted from the credit's own data, so they start compliant. For third-party documents such as transport documents and inspection certificates, Validator produces the exact instructions the carrier or inspector needs. - **Full pre-check before bank submission.** The complete set is examined against the credit, [UCP 600](https://library.iccwbo.org/), [eUCP](https://library.iccwbo.org/) and [ISBP 821E](https://library.iccwbo.org/), field by field and across documents. Every finding names the document, the field and the rule behind it. Validator is [SOC 2](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2) certified. Client logic learned from a company's own transactions is fenced to that client and never used to train the general model; we will write more about that architecture in a later post. ## The result Errors get caught before they happen, and exporters get paid faster. The [ICC](https://iccwbo.org/)'s long-standing estimate is that 60% to 80% of L/C presentations are refused on first submission. Every one of those refusals carries fees, a courier loop and a payment delay measured in weeks. A presentation that is clean on the first attempt collapses that cycle. ## Why we built it this way We spent 2026 running live letters of credit through the system before releasing it, because an examination tool earns trust on real presentations or not at all. Over a billion dollars of credits later, three design decisions have held up. The first is timing: catching a problem the day the credit arrives is worth more than catching it perfectly the day before presentation, so Validator starts at arrival. The second is provenance: every finding cites the document, the field and the rule or practice behind it, because a finding an examiner cannot verify in seconds is a finding they will redo by hand. The third is isolation: what Validator learns about one exporter's corridors, counterparties and documents stays with that exporter, is assigned to them as their IP, and is never used to train the general model. The rest of the platform follows from those three. Generating documents from the credit is a timing decision. Explaining every decision is a provenance decision. Fencing client logic is an isolation decision. We will take each of them in turn over the coming weeks. ## What Validator does - Workability review on L/C arrival, before production is committed. - Document generation from the credit, plus instructions for third-party documents. - Pre-check of the full presentation against UCP 600, eUCP and ISBP 821E. - SOC 2 certified; client logic isolated per client. More on how each of these works over the coming weeks. If you present letters of credit today, the fastest way to see the difference is to [run a free workability check](https://www.loamist.com/lc-check.html) on a credit you have in hand. --- URL: https://www.loamist.com/blog/what-is-an-export-letter-of-credit/ # What Is an Export Letter of Credit? A Plain-English Explainer > An export letter of credit swaps trust in the buyer for trust in a bank and its documents. How it works, why the terms are strict, and where it goes wrong. Source: https://www.loamist.com/blog/what-is-an-export-letter-of-credit/ Published: 2026-08-11 · Workability · By Nick Pachnev, Senior Advisor An export letter of credit (L/C), in simple terms, is a promise by a bank, called the issuing bank, to pay an exporter on behalf of a buyer. The bank guarantees payment when the exporter provides documents proving that the agreed shipment was fulfilled. That is the whole instrument. Everything else in the trade-finance vocabulary, from [UCP 600](https://library.iccwbo.org/) to discrepancy fees, follows from it. ## How an export L/C works, step by step - **The buyer applies for the credit.** The buyer's bank (the issuing bank) opens a letter of credit in the exporter's favour, usually by [SWIFT MT700](https://www.swift.com/standards), and sends it through a bank in the exporter's country (the advising bank). - **The exporter checks the terms.** Before committing production, the exporter confirms the credit can actually be met: shipment dates, ports, goods description, and the list of required documents. We call this a [workability check](https://www.loamist.com/blog/what-export-lc-workability-means/). - **The exporter ships and prepares documents.** Each export L/C has its own list. Generally, commercial invoices, transport documents, packing lists, insurance and inspection or other certificates are required. - **The exporter presents.** The documents go to the nominated or confirming bank within the presentation period, and before the credit expires. - **The bank examines and pays.** If the documents exactly meet the letter of credit terms, the bank pays the exporter and forwards the documents to the buyer, who needs them to collect the cargo. ## Trust in a bank, and in documents An export L/C substitutes trust in the buyer with trust in a bank and a set of documents. A seller in one country can be paid for goods sold to a buyer in another country, and the buyer can receive the goods, without either party taking the other's word for it. The bank stands in the middle and deals only in paper. This explains why letter of credit terms are so strict. The bank does not examine the cargo. It determines whether the documents meet the L/C requirements, line by line. UCP 600, the [ICC](https://iccwbo.org/) rules that govern most credits, says it directly: banks deal with documents and not with the goods, services or performance to which the documents may relate. ## Why "exactly" is the operative word Because the bank cannot look at the shipment, it has nothing to go on except the consistency of the documents with the credit and with each other. A vessel name spelled two ways, an invoice amount that exceeds the credit by a few dollars, or a certificate dated after the shipment date are not clerical trivia to a document checker. They are the only evidence available, and if the evidence conflicts, the presentation is refused. The [ICC Banking Commission](https://iccwbo.org/business-solutions/banking-commission/) has put first-presentation refusal rates between 65% and 80% for years ([Technical Advisory Briefing No. 3](https://library.iccwbo.org/content/tfb/BRIEFINGS/20220627_TA_Briefing_No3_reducing_discrepancy_rates.pdf), 2022). Most of those refusals are not fraud or failed shipments. They are ordinary documents that do not match an ordinary credit, produced under time pressure by people re-keying the same data three or four times. ## Where exporters get hurt - **Unworkable terms accepted at the start.** A latest shipment date the plant cannot hit, or a certificate no inspector in the corridor issues, guarantees a discrepancy before a single document exists. - **Discrepancies found at the bank.** Each refusal carries a fee, a delay of days to weeks, and a courier loop. Payment can slip 30 to 45 days on cargo that has already sailed. - **Discrepancies that cannot be cured.** Once a shipment date or expiry has passed, no correction restores compliance. Payment then depends on the buyer agreeing to waive, which turns a bank instrument back into a negotiation. ## Key takeaways - An export L/C is a bank's undertaking to pay against complying documents, not against goods. - Strictness is structural: documents are the only evidence the bank has. - Most refusals come from mismatches between documents and the credit, and many of those trace back to terms that were never workable. Over the coming weeks we will take each stage in turn: what workability means, what a rejected presentation actually costs, and how document generation from the credit itself removes most of the re-keying that creates discrepancies in the first place. If you want a head start, the [pre-shipment L/C review guide](https://www.loamist.com/how-to-review-export-letter-of-credit-before-shipment.html) is the practical version of this post. ## Frequently asked questions ### Who pays under an export letter of credit? The issuing bank, on behalf of the buyer, once the exporter presents documents that comply with the credit's terms. A confirming bank may add its own undertaking to pay. ### Does the bank inspect the goods? No. Under UCP 600 banks deal with documents only. If the documents comply, the bank pays, whatever happened to the cargo. ### What documents does an export L/C usually require? Each credit lists its own set. Commercial invoice, transport document, packing list, insurance document and inspection or origin certificates are the usual core.