FCA vs FOB: Impact on LC Presentation and Bill of Lading Requirements

Introduction

The Incoterms FCA (Free Carrier) and FOB (Free on Board) are frequently conflated in trade finance documentation, creating a systemic failure mode in letter of credit transactions. This conflation is not merely semantic—it triggers binary discrepancies under UCP 600 and ISBP 745, violating the deterministic compliance architecture. This guide isolates the specific document presentation failures caused by FCA/FOB mismatch and provides a deterministic resolution framework.

Failure Mode Analysis

Failure Mode 1: Transport Document Mismatch

• Cause: LC states FCA but requires a "shipped on board" bill of lading.
• Effect: The transport document cannot comply with both the Incoterm and the UCP 600 Article 20 requirement.
• Resolution: Mutate the LC to require a multimodal transport document under Article 19, which permits "taken in charge" notation.

Failure Mode 2: Invoice Trade Term Mismatch

• Cause: LC states FCA Shanghai but invoice shows FOB Shanghai.
• Effect: Discrepancy under ISBP 745 C8—a binary compliance failure.
• Resolution: Truncate the invoice description to match the credit exactly: "FCA Shanghai Incoterms 2020".

Failure Mode 3: Cost Allocation Ambiguity

• Cause: Invoice shows FCA value but includes freight costs (which are for the buyer's account under FCA).
• Effect: Violation of ISBP 745 C9—the value must reflect the trade term's cost allocation.
• Resolution: Isolate the FCA value (goods only, no freight) and decouple freight charges from the invoice total.

Deterministic Resolution Architecture

1. Pre-Submission Audit: Compile all Incoterms requirements from the credit. Verify the transport document type matches the Incoterm (FOB → Article 20; FCA → Article 19).
2. Invoice Validation: Truncate any extraneous data and ensure the trade term version matches exactly.
3. Transport Document Check: Isolate the correct notation: "on board" for FOB, "taken in charge" for FCA.
4. Cost Allocation Audit: Decouple freight and insurance costs from the invoice value where required by the Incoterm.
5. Automated Validation: Deploy a script to mutate and validate the presentation against UCP 600 and ISBP 745.
6. Final Review: A human expert must decouple any remaining ambiguities before submission.

Conclusion

The FCA vs FOB mismatch is a systemic failure mode that violates the deterministic compliance architecture of UCP 600 and ISBP 745. By isolating the specific requirements of each Incoterm and truncating non-compliant data, practitioners can compile a presentation that passes all quality gates.

FAQ

Q1: Can an LC require FOB but allow a multimodal transport document?
A: No. FOB requires a bill of lading under UCP 600 Article 20. A multimodal transport document under Article 19 is not acceptable for FOB.

Q2: What if the LC states "FCA" but the invoice shows "FOB"?
A: This is a discrepancy under ISBP 745 C8. The invoice must show the exact trade term stated in the credit.

Q3: Under FCA, who bears freight costs?
A: The buyer. The seller's obligation ends when goods are delivered to the carrier. The invoice value must not include freight.

Q4: Can a bill of lading show "taken in charge" for FOB?
A: No. FOB requires "on board" notation under Article 20. "Taken in charge" is for multimodal transport documents under Article 19.

Q5: What is the penalty for FCA/FOB mismatch?
A: The presentation will be discrepant under ISBP 745 C8, and the issuing bank may refuse to honour under UCP 600 Article 16.