Most mid-market companies with significant import activity still manage their documentary credits outside the ERP — in a shared spreadsheet or a proprietary bank portal. This siloed approach creates a precise operational risk: letters of credit have a strict expiry date, and if your ERP is not tracking these deadlines, your finance team may let a guarantee expire without realising it. In a world where 60–75% of LC document presentations contain at least one discrepancy on the first submission (ICC Banking Commission data), manual management of documentary credits is a systematically underestimated risk. This guide explains how to integrate LCs into your ERP — natively in SAP S/4HANA, via a banking partnership in Oracle Fusion, or through customisation in Dynamics 365, Odoo or Sage X3.
Letters of Credit and Documentary Credits: Fundamentals for Finance Teams
The 4 Main Trade Finance Instruments: LC, SBLC, Bid Bond, Performance Bond
Finance teams at mid-market companies involved in international trade work with four main instruments.
The documentary letter of credit (LC) is the standard payment instrument: the buyer’s bank irrevocably undertakes to pay the seller, subject to the presentation of compliant documents (bill of lading, commercial invoice, packing list, insurance certificate). It is a trust mechanism, particularly useful when buyer and seller do not yet know each other or operate in regions with elevated political risk.
The SBLC (Standby Letter of Credit) is not a primary payment instrument: it is a last-resort payment guarantee. It is triggered only if the debtor fails to meet contractual obligations. Its accounting treatment in the ERP differs from an ordinary LC: it appears off-balance-sheet as a contingent liability, not as an anticipated cash flow.
The Bid Bond guarantees that a tenderer will honour their offer if they win a contract. The Performance Bond guarantees the correct execution of a contract. Both instruments are common in international construction and capital goods supply.
LC Lifecycle: Opening, Notification, Utilisation, Payment
An LC follows a five-stage lifecycle that must be tracked in your ERP to prevent losses:
- Opening: the buyer (or their issuing bank) opens the LC and sends a SWIFT MT700 message (Issue of a Documentary Credit) to the advising bank.
- Notification: the advising bank informs the seller that the LC is available. This triggers the utilisation deadline.
- Shipment and document collection: the seller ships the goods and collects all documents required by the LC terms.
- Document presentation: the seller presents documents to the nominated bank before the LC expiry date. This is the stage at which 60–75% of presentations reveal a discrepancy.
- Payment: after verifying document compliance (5 banking days under UCP 600), the bank settles the seller.
If your ERP does not track the expiry date (stage 2) and does not send alerts before stage 4, the risk of losing the guarantee is real.
UCP 600: The ICC Regulatory Framework Since 2007
UCP 600 (Uniform Customs and Practice for Documentary Credits, ICC Publication 600) came into force on 1 July 2007. It governs the vast majority of LCs worldwide and sets the rules for document examination, timelines and bank responsibilities. For SBLCs, ISP 98 (International Standby Practices) provides an alternative framework, better suited to the contingent nature of these instruments.
Both sets of international rules must be referenced in your LC conditions and are the parameters your ERP needs to know in order to correctly calculate deadlines.
Why LC Management in ERP is Often Broken
The Disconnect Between the Banking Front-Office (SWIFT MT700) and the ERP
The SWIFT MT700 message is the standard format for issuing an LC. It contains all LC conditions: amount, currency, expiry date, list of required documents, port of loading, incoterm. The problem: few mid-market ERPs can parse this format natively. The practical consequence is that when your bank transmits an LC received from a foreign buyer, that information does not enter your ERP automatically. Someone must manually re-enter the key data — especially the expiry date and the list of documentary conditions.
This manual re-entry introduces two risks: transcription errors (expiry date copied incorrectly, wrong amount) and pure omission during peak activity periods.
Manual Expiry Tracking: The Concrete Operational Risk
An LC without automated tracking in the ERP generates a binary risk: either documents are presented on time and the guarantee serves its purpose, or the expiry date goes unnoticed and the guarantee is lost without recourse. In a mid-market company with ten to fifty LCs open simultaneously, a shared Excel file is structurally inadequate: concurrent edits, the absence of automatic alerts and dependence on individual vigilance make it an unsuitable tool at any meaningful volume.
The stakes go beyond losing the bank guarantee. If the LC finances a critical purchase (raw materials, industrial components), the inability to pay via LC forces a last-minute negotiation of an alternative payment method with the supplier — often at unfavourable terms.
Accounting for LC Bank Charges
Bank charges related to LCs (opening commission, confirmation commission, utilisation commission, discrepancy fees) typically represent 0.3%–1.5% of the LC amount, depending on duration and country risk profile. For a mid-market company with £5m of LCs open at any one time, that is between £15,000 and £75,000 in annual financial charges. These commissions must be recognised as financial expenses, with per-LC tracking to justify provisions and bank reconciliations.
In many mid-market ERPs configured without specific attention to trade finance, these charges land in bulk on a general expense account, with no link to the underlying LC.
The Problem of LCs That Expire Without Presentation
An export LC that expires without presentation — because production ran late or the finance team did not assemble the documentary dossier in time — is a guarantee lost. The seller (your company) loses its right to secured payment. Negotiations restart in open mode, often with a counterparty who understands that your position has weakened.
How to Configure LC Management in Your ERP
SAP S/4HANA: Foreign Trade and LC Management via FSCM
SAP S/4HANA includes a Foreign Trade module (components SD-FT and MM-FT) that manages import and export documentary credits. The module allows you to create a documentary credit, link it to the corresponding purchase or sales orders, track key dates (issue date, validity date, presentation deadline) and generate automatic alerts before expiry.
The Financial Supply Chain Management (FSCM) module complements this by integrating LCs as financial instruments within treasury management and bank reconciliation. The combination enables end-to-end tracking: from purchase order to final settlement, with full traceability of associated documents and SWIFT messages.
For mid-market companies, implementing these modules requires significant initial configuration and, in most cases, the support of an SAP integrator specialised in international finance.
Oracle Fusion Cloud Financials: Trade Finance with J.P. Morgan
Oracle has developed an Automated Trade Finance integration with J.P. Morgan, presented at Oracle CloudWorld 2024 (Oracle OCW24 Trade Finance session). This integration allows import and export LCs to be managed directly from Oracle Fusion Financials, with automated bank data flows via J.P. Morgan API.
For mid-market companies that do not use J.P. Morgan as their primary bank, Oracle Banking Digital Experience Corporate Trade Finance offers LC management, bank guarantees and documentary bills functionality, but requires a custom integration with the company’s own bank.
Microsoft Dynamics 365 Finance: Native Limitations, ISV Integration
Dynamics 365 Finance has no native trade finance module equivalent to SAP’s Foreign Trade. LC management functionality is limited in the standard version: there are no dedicated workflows for expiry tracking or LC document management.
Common approaches in D365 Finance projects for mid-market companies with significant LC activity are: using a specialist ISV module (several publishers offer D365 extensions for trade finance), or integrating with an external TMS (Kyriba, Coupa Treasury) that handles guarantee instrument management.
Odoo and Sage X3: Customisation or Middleware
Odoo (Community and Enterprise) and Sage X3 have no native LC module. Documentary credit management relies on specific developments within the accounting or treasury module, or on integration with a third-party tool via API. For a mid-market company with fewer than twenty LCs per year, a documented process within the ERP treasury module (with custom fields for key dates and manual alerts) may suffice. Beyond that, integrating a TMS becomes more relevant than customising the ERP.
ERP-TMS Integration for Real-Time LC Management
Kyriba: Multi-Bank Guarantee Instrument Synchronisation via SWIFT
Kyriba offers a multi-bank trade finance solution covering import and export LC management, SBLCs and bank guarantees, connected to over 10,000 banks via SWIFT and API (Kyriba Connectivity). The platform centralises guarantee instrument tracking, generates deadline alerts and synchronises data with the ERP.
For a mid-market company whose ERP lacks a native LC module, Kyriba acts as the guarantee instrument management layer, transmitting accounting data (commissions, provisions, settlements) to the ERP via automated feeds.
SWIFT Connectors: Alliance Lite2 and gpi to Automate the LC Cycle
SWIFT Alliance Lite2 is SWIFT’s access solution designed for mid-sized companies. It enables direct receipt of MT700 messages (LC issuance), MT707 (amendment), MT750 (notified discrepancies) and MT799 (free-format messages) into your information system, without going through your bank’s online portal.
Integrating SWIFT into a mid-market ERP represents a significant investment (SWIFT membership fees plus integration costs), but for a company handling more than 50 LCs per year at material amounts, automating the information flow justifies the investment through reduced operational risk.
Accounting for LCs and Guarantees: IFRS Treatment
Import LC: Off-Balance-Sheet Commitment and FX Risk Provision
Under IFRS, an import LC opened by your company constitutes an off-balance-sheet commitment until the underlying performance obligation is fulfilled. It does not generate a balance sheet entry until the related goods or services are received. However, if the LC is denominated in a foreign currency, it creates a foreign exchange exposure that your ERP must track and, where appropriate, hedge.
IFRS 9 (Financial Instruments) requires a more rigorous approach for financial guarantee instruments: SBLCs issued by your company in favour of a third party must be measured at fair value on initial recognition, and a provision must be recognised if the risk of being called upon is material.
Issued SBLC: Off-Balance-Sheet Treatment and Periodic Commissions
An SBLC issued by your bank in favour of a third party (for example, to guarantee a long-term supply contract) appears off your company’s balance sheet as a contingent liability. The periodic commissions your bank charges to maintain the SBLC are financial expenses that must be accrued to the correct accounting period.
Your ERP must allow you to configure a commission schedule and record entries automatically without monthly manual input — otherwise charges are misallocated and period-end closes become unnecessarily complex.
Checklist: 10 Questions to Audit LC Management in Your Current ERP
- Does your ERP have a dedicated field for LC expiry dates? If this date is stored in an external spreadsheet, you have a blind spot.
- Are automatic alerts generated 30, 15 and 5 days before expiry? The 5-day alert must be treated as critical.
- Are LCs linked to the underlying purchase or sales orders in the ERP?
- Are incoming SWIFT MT700 messages automatically fed into the ERP, or do they require manual re-entry?
- Are LC bank charges allocated to a dedicated cost centre per LC?
- Do issued SBLCs appear in your ERP’s off-balance-sheet commitments? Has a provision been recognised where the call risk is material?
- Does your ERP distinguish between import LCs (you are the buyer) and export LCs (you are the seller)? The configuration differs for each case.
- Does final settlement of an LC automatically trigger reconciliation with the purchase order and supplier invoice?
- Are documentary discrepancies notified by the bank (MT750) tracked in the ERP with a response deadline?
- Do your treasury manager and your international procurement/sales manager have access to the same LC tracking screen in the ERP, or do they work on separate systems?
If you answered no to more than four of these questions, your documentary credit management has gaps that justify a configuration or integration project.
For further reading, see our ERP treasury management and cash forecasting guide, our reverse factoring and supply chain finance in ERP guide and our ERP for international trade, customs and multi-country compliance guide.
