Evermore Systems Limited logo More Trade Finance
Evermore Systems Limited
SWIFT-native · Documentary credits · Built by Evermore

The complete lifecycle of the letter of credit — without the friction.

More digitises trade finance end to end across two products: Import LC (ILC) for applicant-side credit issuance and LC Reimbursement (LCR) for interbank settlement. From the applicant's request to the issuing bank's reimbursement, More orchestrates the parties, the messages and the controls — with maker–checker workflows, release tabs, and a full audit trail at every step.

Two products, one platform

Import LC & LC Reimbursement — unified by design

Both products share the same operational plumbing: maker–checker queues, release tabs, SWIFT parsing, and amount tracking. Choose the product that matches your role.

📄

Import LC (ILC)

Applicant-side documentary credit lifecycle: registration, pre-advice, issuance, amendment, acknowledgement, document presentation, discrepancy handling, claim request, and settlement.

MT700 · MT707 · MT730 · MT754 · MT734 View ILC flow →
🏦

LC Reimbursement (LCR)

Interbank reimbursement lifecycle driven by incoming MT740: authorization, amendment, acknowledgment, claim verification, refusal, payment advice, and closure.

MT740 · MT747 · MT742 · MT756 · MT744 View LCR flow →
⚙️

Shared platform services

Maker–checker workflow queues (Input → Update → Approval → Cancellation), release tabs (Posting, Charges, Swift, Advice, Settlement), inbound/outbound SWIFT handling with parsing, validation, matching, and release pipeline preventing double-dispatch.

Workflow · Release tabs · SWIFT
Platform pillars

Everything a documentary credit needs, in one pipeline

From the applicant's request to the issuing bank's reimbursement, More orchestrates the parties, the messages and the controls.

📄

LC issuance & advising

Issue MT700 documentary credits, authenticate them at the advising bank, and add confirmation — systematically recorded in field-level detail.

MT700 · MT730
🔍

Document examination

Nominated banks examine presentations under UCP 600. Complying documents trigger payment; discrepancies follow the refusal path.

MT754 · MT734
⚙️

Advice generation & validation

MT754 advices of payment are generated with correct charges, reimbursement routing and claim amounts — then passed through a multi-gate validation pipeline.

Audit · QA gates
💸

Partial drawings & tolerance

Draw down credits in multiple advices with automatic tolerance checks — one LC we track is settled across two MT754 advices, fully reconciled.

32A · 32B · 39A
🏦

Bank-grade routing

BIC-aware reimbursement routing (field 53A), charge splits across /TELECHAR/ and /COMM/, and ACK/NACK handling with F21 acknowledgements.

SWIFT MT · Nov 2025 standard
🛡️

Compliance & audit trail

Every message carries validation logs, MAC/CHK security blocks and AML/KYC checklists aligned to the documentary examination workflow.

AML · Reg models
Shared plumbing

Same mechanics, different data — across every event

Operations staff experienced with one stage will recognise every other stage. Three mechanisms apply throughout both products.

Maker–checker workflow queues

Every event follows the same queue sequence

When a form is saved it enters the INPUT queue. Submitting advances the record through its configured queue sequence; a decline sends it back one queue with reasons recorded. The final approval queue performs all release actions at once — postings, charges, electronic messages, and stage-specific effects on the master record.

  • Status pattern: P — in progress → AP — approved (or CN — cancelled)
  • A workflow reference (event code + sequence) is minted so every action is traceable in history
Release tabs

Posting · Charges · Swift · Advice · Settlement

Each event is configured with the tabs it needs. Visible tabs must be complete before submit: every posting and charge line needs an account number, and any mandatory SWIFT message must be generated and saved. Completion is shown with colour badges on the tabs.

  • Posting — the accounting legs (double-entry) the event produces
  • Charges — commission lines that may generate their own postings and a customer debit advice
  • Swift — generate/validate the outbound messages for the event
  • Advice / Settlement — event-specific extras (charge debit advice PDF; settlement accounts)
Incoming & outgoing SWIFT handling

Parse → Validate → Match → Generate → Release

Inbound: SWIFT files are read, parsed and stored as raw messages (status Pending → Processed), then routed by type to the matching work screen — MT730, MT750, MT754 for ILC; MT740, MT747, MT742, MT744 for LCR.

Outbound: each event's Swift tab builds the message from captured data, offers a validation preview, and stores it (status Generated → Released on approval). Release pipeline prevents double-dispatch and duplicate emails.

Example: MT754 · Advice of paymentgenerated
{1:F21BKCHCNBJXXX0001000000}{4:
:20:BKCH75427326
:21:CSLC27326EUR0008
:32A:261005EUR100000,
:71D:/TELECHAR/EUR25,00
:34A:261005EUR99975,
:53A:ABBYGB2LXXX
:72Z:/REC/WE ACK COMPLYING PRESENT
ATION FWD AS INSTD WE HAVE
PAID EUR100000, LESS TELECHAR
EUR25,00 CLAIM EUR99975, VIA
ABBYGB2LXXX …
-}{5:{MAC:…}{CHK:…}}
Why teams choose More

Adaptable to your institution's trade finance workflows

🛡️ Local Compliance

Native Form M Integration. Automated CBN reporting.

💰 Hybrid Pricing

Low base license. Pay-as-you-go SaaS scaling.

⚙️ Affordable Customization

Tailor Features on-demand without the incumbent price tag.

🔄 End-to-End Control

Full ILC and LCR lifecycle automation.

📦 Deployment-ready Configurations

Product Config: queues, charges, SWIFT, checklists, postings.

📈 Reporting

Regulatory and other report exports on demand.

See your own portfolio on More

Bring your LC references, currencies and parties. We map your flow onto the platform in minutes.

Request a demo →