Skip to content ReleaseVezual Beta is in the Plugins Console
Start free

Banking

Investigate suspicious
transactions.

Find transfers, linked accounts and previous case notes in one investigation view. Give analysts the records they need to review an alert.

Explore use cases Talk to our team
Transaction investigation
A selected transfer connects several accounts, with a magnifying glass over the highlighted route.

Trace a transfer through verified account links.

Illustrative use case

01 / Use case guide

10 practical use cases.

Compare the data models behind everyday industry tasks, from finding records to following connections.

SQL Filter and calculate Vector Match similar meaning Graph Follow relationships Full-text Find words and phrases

Suggested model combination

Scroll across to compare all four models
Use case How the data models help SQL Vector Graph Full-text Source
Suspicious transfer network review Investigators need the accounts and prior cases surrounding an unusual transfer. SQL filters transfers, Graph follows recorded account links, and Vector retrieves similarly described case notes for analyst review.
Business ownership evidence review Onboarding teams need to verify the people behind a business account. SQL selects current customer records, Graph traces documented ownership, and Full-text finds names in supporting filings.
Correspondent account activity review Reviewers need to compare a respondent bank's activity with its agreed services. SQL summarizes account activity, Graph links respondent banks and services, and Full-text retrieves relevant agreement clauses.
Trade finance document checks Trade teams need to investigate inconsistent invoices, shipments and payment details. SQL compares recorded values, Graph connects trade parties and shipments, and Full-text locates conflicting document descriptions.
Sanctions alert evidence review Analysts need payment details and source records to resolve a screening alert. SQL selects the flagged message and list version, while Full-text retrieves matching names and references for analyst review.
Check fraud case investigation Investigators need to connect altered checks with deposits and related accounts. SQL compares check amounts and deposit dates, while Graph follows recorded links among checks, deposits and accounts.
Deposit complaint evidence retrieval Service teams need account events and earlier correspondence to resolve a deposit complaint. SQL retrieves account events, Vector finds similarly described complaints, and Full-text locates relevant terms and correspondence.
Funding concentration review Treasury teams need to see reliance on particular funding sources. SQL aggregates funding by maturity and currency, while Graph groups documented relationships between funding counterparties.
Bank service outage tracing Incident teams need to identify which critical services depend on a failed system. Graph traces service and supplier dependencies, while Vector retrieves similar incident reports and recovery notes.
Deposit insurance record preparation Operations teams need to resolve missing depositor and account ownership records. SQL checks required fields and balances, while Graph links deposit accounts with recorded owners and beneficiaries.

Use the query interfaces you need, then connect their results through shared record IDs in your application.

Industry sources 10

These sources describe real industry workflows. The model combinations above are proposed OriginChainDB designs, not customer deployment claims.

  1. BIS Innovation Hub — Project Aurora: collaborative analysis of money laundering (proof of concept)
  2. Federal Financial Institutions Examination Council — Beneficial ownership of legal entity customers
  3. Federal Financial Institutions Examination Council — Correspondent accounts: operational risks and monitoring
  4. FATF and Egmont Group — Trade-Based Money Laundering: Risk Indicators
  5. Swift — Transaction Screening
  6. Financial Crimes Enforcement Network — Alert on mail theft-related check fraud schemes
  7. Office of the Comptroller of the Currency — Consumer complaints and bank dispute resolution
  8. Basel Committee on Banking Supervision — Liquidity monitoring metrics: concentration of funding
  9. Basel Committee on Banking Supervision — Principles for operational resilience
  10. Federal Deposit Insurance Corporation — Part 370 Information Technology Functional Guide, Version 3.0

02 / A closer look

Investigating an unusual transfer

An analyst receives an unusual-transfer alert. The payment record is in one system, linked accounts are in another, and previous investigations sit in written case notes. The analyst needs the supporting evidence in one place.

What makes it difficult

  1. 01

    A single transaction does not show the surrounding network.

  2. 02

    Case notes use different words for similar activity.

  3. 03

    Outdated identity links can send a review in the wrong direction.

Suggested approach

Start from the alert

Filter the transactions by account and time, follow verified account links, then search related case notes. Show the source of each result so the analyst can check it.

03 / Queries

What each data model does

Select a model to see the question it answers.

SQL · Find the facts

The question

Which transfers match this account, date range and amount?

Narrow the investigation.

Explore SQL
Vector · Match the meaning

The question

Which authorized notes describe a comparable transfer pattern?

Find similarly described cases.

Explore Vector
Graph · Follow the connections

The question

Which accounts share a confirmed owner or beneficiary?

Follow verified account relationships.

Explore Graph
Full-text · Find the exact wording

The question

Where is this payment reference mentioned in case notes?

Find exact references.

Explore Full-text

Use shared record IDs to combine results from the different query interfaces in your application.

04 / Implementation

How to build it

  1. STEP 01

    Select closed cases

    Use de-identified alerts from one review queue. Ask investigators to mark the records they needed to resolve each case.

  2. STEP 02

    Link the records

    Assign case, transfer and account IDs. Record where each account relationship came from and when it was valid. Index permitted notes.

  3. STEP 03

    Build the investigation view

    Filter transfers with SQL, follow account links with Graph and search notes by words or meaning. Combine the results in your application with case-level access checks.

  4. STEP 04

    Compare with completed reviews

    Replay closed cases. Check missing evidence, incorrect links and review time before letting analysts use the tool on open cases.

05 / Testing

What to measure

Compare these results with your current process before rollout.

Evidence coverage

Compare retrieved records with the evidence investigators marked necessary.

Irrelevant connections

Track links rejected because identity, timing or source quality was insufficient.

Review effort

Measure time spent gathering context on comparable cases before and during the pilot.

06 / Sources

Examples from the industry

Published projects and reference material relevant to this use case.

Industry example 2025 annual report

Hong Kong Monetary Authority

Banks sharing context through FINEST

HKMA describes expanded bank-to-bank financial-crime information sharing through FINEST, including the enhanced platform introduced in December 2025. This is a documented banking initiative, not an OriginChainDB deployment.

Read the source
Industry context 31 May 2023

BIS Innovation Hub

Project Aurora explores network analysis

Project Aurora tested collaborative analysis, network methods and privacy-enhancing techniques using synthetic payments data. It was a proof of concept, not a production banking implementation.

Read the source

These are industry references, not OriginChainDB customer stories. The implementation above is a proposed example.

Build with OriginChainDB

Discuss your application with us.

Explore use cases Talk to our team