Skip to content
Start free
All industries

Banking · Customer and transaction context

Every case has a history.
Keep the records connected.

Bring account data, transaction relationships and policy search into one database for the applications your banking teams build.

Discuss your workload Explore the quickstart

Build the case from its sources.

Start with an account, inspect its transfers, and follow the recorded recipient. Your application brings that evidence together for an analyst.

Account → transfers → counterparty → reviewIllustrative records
Case context · account AC-104Open the transfer records ↓
Two recorded transfers
TX-21009:12 · outgoing
From
AC-104
To
CP-08
Source
payments / TX-210
TX-21109:18 · outgoing
From
AC-104
To
CP-08
Source
payments / TX-211
Shared recipient CP-08Harbor Supplies

Two transfers resolve to the same recorded counterparty.

Supporting policy evidenceRecipient review · version 3

Passage: “Check the recipient’s recorded details.”

Policy PL-07 · passage 12
Application + analystReview before deciding.

Compare the transfer sources with the relevant policy. Record the finding and the next action in the case.

Illustrative account, transfers and policy text. The application retrieves the policy and assembles the case; the relationships do not establish a risk finding.

5 use cases / Banking

The right modalities for your workflow.

Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.

Banking: use cases, recommended query modalities and why each combination fits.
Use caseRecommended modalitiesWhy this combination fits
Account servicing

Bring balances, account details and recent activity into a service view.
SQL

SQL joins customer and account records, filters recent transactions and calculates the totals the service team needs.
Connected-account investigations

Explore transfers between accounts and their recorded counterparties.
SQL Graph

SQL narrows activity by amount and time. Graph follows account and counterparty links to reveal the connected records.
Case evidence review

Connect an investigation to its correspondence and supporting documents.
SQL Graph FTS

SQL selects case records, Graph connects accounts and documents, and FTS finds names, phrases and references within the evidence.
Policy knowledge retrieval

Find relevant policy passages for a service or operations question.
SQL FTS Vector

FTS matches policy terms; Vector retrieves passages with similar meaning. SQL supplies document versions and business context for the application.
Branch operations reporting

Track transaction volumes and service workloads by branch and period.
SQL

SQL groups operational records by branch, date and status, with the underlying rows available for drill-down.

Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.

Use the query that fits the question.

Share stable record IDs across your models so the application can resolve each result back to its source.

SQL

What happened on this account?

Filter transactions by account and time. Join customer records and aggregate the result.

Query the records
Graph

Which records are connected?

Declare account and counterparty references, then traverse the relationships with a bounded query.

Follow a relationship
Full-text

Where is this policy mentioned?

Find exact terms or rank matching passages. Keep the document ID with every search result.

Search policy text
Vector

Which passages discuss this issue?

Retrieve similar text using your embeddings, then fetch the source passage for review.

Model the embeddings

Text indexes and vectors use their own write endpoints. Your ingestion pipeline manages their updates and records the source version.

A focused first build

Start with one investigation path.

Use representative sample records before introducing customer data.

Review the design with us
  1. 01

    Define the records.

    Model accounts, transfers, counterparties and source documents with stable IDs.

    Schema reference
  2. 02

    Test one complete case.

    Query the transfers, traverse their references, and check every returned source. Set result and traversal limits.

    Graph quickstart
  3. 03

    Connect the review application.

    Keep credentials server-side. Apply the application's access rules and retain the analyst's decision with its evidence.

    Authentication reference