Skip to content
Lotus Comply

Lotus Comply / Transaction Monitor

Selectable service

Turn transaction patterns into informed compliance action.

Bring authorised transaction data, versioned rules and analyst review into one traceable workflow. Transaction Monitor helps your team understand alerts, assess customer context and refer concerns to Case Manager when selected.

Who uses it

Transaction-surveillance analysts, rule owners, investigators and integration teams.

Lotus Comply / Transaction Monitor

Sample workspace

Evaluation DEMO-014 · Sample

Example alert
Transaction patternDEMO-R02
Sample startRule evaluation window

Threshold exceeded in this sample · human review required

Sample workspace data

Inside Transaction Monitor

The work behind the outcome.

From the first input to the final handoff, understand what is captured, what gets checked and what still needs a person’s judgement.

Complete process

One flow. Explicit next steps.

  1. 01

    Onboard the source

    Agree source authority, institution-specific data mappings and approval for operational use.

  2. 02

    Validate & link

    Validate transaction fields and connect the correct customer record.

  3. 03

    Evaluate active rules

    Apply the approved rule version and its configured thresholds.

  4. 04

    Triage the alert

    Review transaction context, history and pattern evidence.

  5. 05

    Investigate & decide

    Record the analyst’s decision and refer to Case Manager where selected.

No alert in evaluation

The evaluated rule did not trigger on the supplied data; this result is separate from customer clearance.

Alert for investigation

A rule threshold triggers analyst review; customer context and a recorded decision guide the next step.

Invalid / unavailable source

Hold or reject unusable data, resolve the source issue and validate it before evaluation resumes.

Example workflow. Selected services, mandatory requirements, source availability and institutional authority determine the permitted next step.
01

Transaction Monitor / sources

Connect your authorised transaction data.

Transaction Monitor connects to your institution’s authorised transaction data sources through an agreed integration process. We configure the relevant data mappings, validate the connection and test the monitoring rules before operational use.

  • Source authority and access
  • Institution-specific mappings
  • Testing and operational acceptance
02

Transaction Monitor / validation

Validate transactions before drawing conclusions.

Validate transaction identifiers and relevant fields, then link each record to the correct customer. Unmatched or malformed records are held for resolution so analysts can work with reliable transaction context.

  • Transaction identifiers and relevant fields
  • Correct customer-record linkage
  • Invalid-record resolution
03

Transaction Monitor / replay

A repeated delivery is not a new transaction.

Duplicate and replay safeguards prevent repeated source records from multiplying evaluations or alerts. Retrying a delivery must preserve its identity and processing history.

  • Source record identity
  • Duplicate-processing protection
  • Replay and retry traceability
04

Transaction Monitor / rules

Make every rule clear and traceable.

Define monitoring scenarios and thresholds using deterministic, versioned rules. Each evaluation has an explicit rule basis, helping analysts understand the trigger and rule owners review configuration changes.

  • Versioned typology rules
  • Explicit scenario thresholds
  • Explainable evaluation inputs
05

Transaction Monitor / activation

Backtest before activation.

Evaluate draft rules against authorised sample or historical data to review thresholds and expected results. Rule owners assess the findings before approving a specific version for operational use.

  • Draft rule configuration
  • Backtest and review
  • Controlled activation of a specific version
06

Transaction Monitor / alerts

Understand what triggered the alert.

Connect each alert to its rule version, customer record and relevant transaction pattern. The sample repeated-transfer alert shows how analysts can examine the threshold and supporting context before deciding what needs attention.

  • Evaluation and rule-version history
  • Contextual transaction pattern
  • Threshold and supporting context
07

Transaction Monitor / investigation

Move from alert to accountable review.

Analysts review transaction context and history, document their assessment and record a disposition. Where Case Manager is selected, concerns can move into an investigation with the relevant customer context attached. Alerts support review; analysts determine the appropriate next step.

  • Analyst triage and history
  • Optional case handoff
  • Reasoned investigation outcome
08

Transaction Monitor / limits

Keep transaction and customer review connected.

Transaction Monitor focuses on transaction patterns and the alerts they generate. Monitor is the separate service for ongoing customer reviews, evidence expiry and material changes. Select the services your team needs while keeping their responsibilities clear.

  • Transaction-pattern evaluation
  • Analyst-led alert decisions
  • Monitor for ongoing customer review

Information in context

See what the team works with.

A sample transaction monitor workspace shows the relevant fields and outstanding work.

Lotus Comply / Transaction Monitor

Sample workspace

Evaluation DEMO-014 · Sample

Example alert
Transaction patternDEMO-R02
Sample startRule evaluation window

Threshold exceeded in this sample · human review required

Source
Sample transaction file
Customer linkage
Alex M. · linked record
Rule version
DEMO-R02 · evaluated version
Pattern
Repeated transfers
Evaluation
Threshold exceeded in sample
Case referral
Awaiting analyst review
Sample workspace data

In practice / Payments surveillance

From repeated transfers to a reasoned review.

In this example, a sample dataset links repeated transfers to Alex M. Evaluation against rule version DEMO-R02 identifies a pattern above the configured threshold. An analyst examines the transactions and customer context, records a disposition and considers referral to Case Manager where selected.

What becomes clearer

Connect data, configuration and investigation so an alert can be explained from its originating rule.

Questions & answers

Before you choose Transaction Monitor.

Is a transaction source required?

Yes. Your institution authorises the transaction data source, agrees customer linkage and field mappings, and approves the connection after validation and rule testing.

How is a core-banking connection set up?

The connection is configured for your institution’s system, data contract and authorised access. Integration, testing and operational approval are agreed as part of commissioning.

Can rules be customised?

Yes. Rule owners can configure institution-specific scenarios and thresholds, review backtest results and approve a defined version for activation.

Does it automatically block payments?

No. Transaction Monitor supports alert evaluation and analyst review, rather than automatic payment intervention.

What does the sample workspace show?

The sample workspace shows how a versioned rule identifies a repeated-transfer pattern and brings its supporting context into analyst review.

What happens if the feed is unavailable?

The source status remains visible so the integration team can resolve the issue. Unusable data is held or rejected and validated before evaluation resumes.

What needs to be agreed before operational use?

Implementation requirements: operational monitoring depends on bank-authorised, institution-specific data-source integration, validation, rule testing and approval. External connections are currently inactive pending approved commissioning; each source requires institution-specific configuration and validation. Payment blocking and AI-based detection are not part of the standard offering. Service scope, commercial terms, institutional configuration and data authority are agreed before activation.

Connected where selected

Related modules and capabilities are optional; access depends on selected services, configuration and permissions.

Build the right transaction monitor workflow for your institution.

Discuss your requirements