Trade finance compliance · built on IONLive demo

ION Trade Finance Suite

It reads every document behind a letter of credit and explains every warning in plain words. People decide.

About ION Trade Finance Suite

The idea

Criminals sometimes hide dirty money inside ordinary trade: an invoice priced far too high, a shipment that never sails, or a clause that lets goods be re-sold to a related company. The suite reads every document behind a letter of credit, checks the price, the companies, the goods and the ship, and explains each warning with its source, so the bank's own people make every decision with the evidence in front of them.

Product tour

How ION Trade Finance Suite works

  1. Bring in a letter of credit

    The trade team uploads the credit and its documents: the SWIFT message (MT700), the invoice, the bill of lading and any scans. Every file is stored read-only, and nothing is written back to the bank's systems.

    Bring in a letter of credit
  2. Confirm what it wasn't sure about

    The system reads every field and scores how sure it is. Anything below 85% waits in the checker queue for a person to confirm, and nothing is screened from a field nobody has confirmed.

    Confirm what it wasn't sure about
  3. Read the findings

    Each finding is red, amber or green and says in one sentence what was found and where: the invoice line, the clause in the credit, or the sanctions list version. In this example the tea is priced 46% above the market range, and a clause lets the goods be re-invoiced to an affiliate. A chat answers questions about the case from its own documents.

    Read the findings
  4. See the price against the market

    Every credit is placed against the normal price range for its goods and trade route, built from at least two independent sources. A credit far outside the range, like this tea shipment, stands out at once.

    See the price against the market
  5. Decide, or pass it to the MLRO

    The analyst accepts the credit, holds it for more documents, or escalates it with a written reason. Escalations go to the bank's Money Laundering Reporting Officer, who makes the call. The software never files, freezes or blocks.

    Decide, or pass it to the MLRO
  6. Show the auditors

    The examiner pack shows what was screened, which checks and list versions ran, what could not run, and every decision with its reason, so an auditor or regulator can follow each case from start to finish.

    Show the auditors
The film · 0:43

See ION Trade Finance Suite in motion

Sample data · synthetic demo
The problem

What ION Trade Finance Suite catches

Case 01

Over-invoicing

An importer pays USD 100 a unit for goods worth USD 10. The extra USD 90 a unit is dirty money reaching the exporter, dressed up as an ordinary payment.

Red flag: The unit price sits far above the market range for those goods on that trade route.

Case 02

A shipment that never sails

The letter of credit is paid and the bill of lading looks perfect. Every name on it screens clean.

Red flag: The vessel and voyage on the bill of lading don't hold up when the ship's history is checked.

Case 03

The clause nobody reads

Every field in the credit matches the documents, so a box-by-box check passes it.

Red flag: Free text in field 47A says the goods may be re-invoiced to an affiliated party.

Stage by stage

How work moves through ION Trade Finance Suite

  1. Application

    Before the credit opens, it screens the parties, the goods description and the countries for shell companies, mis-described goods and sanctions hits.

  2. Issued

    When the SWIFT message (MT700) arrives, it checks the unit price against the market, reads the free-text clauses, and watches for a beneficiary changed later by an amendment (MT707).

  3. Shipped

    Once the ship and voyage are known, it checks the vessel's risk and history, and looks for phantom shipments and goods routed through free trade zones to hide where they came from.

  4. Presented

    With the full document set in, it checks that the credit, invoice and bill of lading agree, and looks for goods shipped short or over, or invoiced twice.

  5. Settled

    As the money moves, it follows the payment legs for money sent round in a circle, payments to third parties, and export earnings that never come home.

Ground rules

Promises it always keeps

  • "Not run" is never green

    A check that could not run is shown as "not run", never as a clear result, so nothing looks safe just because it was skipped.

  • Sources are never blended

    Each sanctions list edition and each data source is stored and cited on its own, so you always know which one said what.

  • Every finding cites its source

    A document line, a list version or a data row: every warning points to the evidence behind it.

  • Software recommends, people decide

    No software decision is final. The bank's Money Laundering Reporting Officer (MLRO) makes the call.

Under the hood

What's inside ION Trade Finance Suite

Planner

Picks the checks that fit the credit's stage and the documents in hand. Required checks always run, or are logged as not run.

Screening

Checks names and ships' IMO numbers against every sanctions list edition separately, with fixed rules an examiner can repeat.

Cross-reference

Connects parties, addresses and vessels with past cases, to show links that sit between the records.

Goods and price

Flags dual-use goods and licence needs, and measures how far the unit price sits from the market range.

Research

Looks up vessel history, owners and officials in outside registers, sending only public identifiers and logging every call.

Reference data

Every reference value, like a price range or a ship's owner, comes from at least two independent sources, and any disagreement is kept as evidence.

By design

What it deliberately won't do

  • It won't: Block payments or hold transactions

    It never sits in the payment path, so an outage never reaches the bank's customers.

  • It won't: File reports by itself

    It puts together a draft report in the goAML format; a person reviews and submits it.

  • It won't: Replace your case management

    It links alerts into cases with an evidence pack, and works alongside the tools you already use.

  • It won't: Keep the bank's data elsewhere

    It runs on the bank's own systems, not as a shared cloud service hosted by BISTEC.

  • It won't: Let AI produce the evidence

    A model's output is only a candidate. Evidence always traces back to a versioned check that can be re-run.

Questions

Does it block payments or file reports by itself?

No. It never files, freezes or blocks anything. Every finding is a lead until a named officer decides what to do with it.

Does our data leave the bank?

It runs on the bank's own systems and only reads bank data, without changing it. Only the research look-ups go outside, sending public identifiers such as a ship's IMO number (its official ID), and every such call is logged.

What happens if a check couldn't run?

It is shown as "could not run", never as a green pass, so nothing looks safe just because it was skipped.

What documents does it read?

SWIFT messages (MT700 and MT707), commercial invoices, bills of lading and scanned PDFs.

Can I see why something was flagged?

Yes. Every finding points to its source: the document line, the sanctions list version, or the price data behind it.

Book a demo

See any of the nine running on your own use case.

A 30-minute walkthrough with the team that built it.

Email us
hello@bistecglobal.com

Offices in Sydney and Colombo.

bistecglobal.com
© 2026 BISTEC Global · Intelligent design. Engineered for adaptability.Demos on this page use sample data.