Financial Compliance / AML MonitoringIntel TDX inference
For MLROs, AML officers and financial crime teams

AML Monitoring AI, Sovereign Transaction Analysis.

Triages suspicious transactions, maps them to FATF typologies and 6AMLD red flags, drafts SAR-ready narratives an MLRO reviews and signs. Inference runs in Intel TDX. EU company, EU-hosted customer database.

Sits alongside your existing TMS (Actimize, NetReveal, Quantexa, Hawk AI). Does not replace deterministic rules, accelerates the human triage and narrative drafting stage that consumes most AML team time.

See pricingBack to financial compliance hub

Typical AML workflow

Where the agent fits in the AML lifecycle.

Most AML teams already have a transaction monitoring system. The bottleneck is rarely alert generation, it is alert triage, false-positive disposition and SAR narrative drafting. The agent is built for that bottleneck.

STEP 1Alert exported from your TMS

Export the alert from Actimize, NetReveal, Quantexa, Hawk AI or FICO Tonbeller and upload it with the KYC summary (PDF, DOCX, TXT or CSV). It reaches our API over TLS; we relay it to the TDX enclave without storing it.

STEP 2Intel TDX trust domain processes the case

Inference runs in Intel TDX, with memory encrypted by the CPU. We don't store the alert payload.

STEP 3Typology mapping and red-flag scoring

The model maps activity to FATF typologies and 6AMLD red flags and explains each factor: layering depth, geographic distance, beneficial-ownership opacity.

STEP 4SAR / STR narrative drafted

The model drafts the narrative in the structure your jurisdiction uses (FinCEN SAR, NCA SAR, Tracfin, FIU.ITA, FINMA SR.04), with typology references for the MLRO to check.

STEP 5MLRO reviews and signs

The MLRO edits the draft, accepts or overrides the typology mapping, and files the SAR through their existing channel. Final responsibility stays human.

Sample prompts

What suspicious transaction analysis looks like in practice.

The agent is an AI model following a review checklist; name the FATF typologies and 6AMLD red flags you want applied. Below are simplified example prompts. Real prompts include alert payload, KYC summary, transaction graph context and historical disposition.

Structuring detection

Analyse this customer's last 90 days of cash deposits.
Apply FATF Recommendation 10 typologies and BSA structuring tests.
Return: typology hits, confidence score, suggested SAR narrative draft.

Detects deposits engineered just below the CTR threshold across multiple branches or accounts.

Trade-based money laundering

Review this commercial invoice batch against FATF TBML red flags.
Look for over/under-invoicing, multiple invoicing, phantom shipments,
and high-risk-jurisdiction routing. Output: red-flag list + STR draft.

Flags TBML patterns the rules-based TMS often classifies as legitimate trade.

Mule network triage

Cluster these 14 alerts by counterparty graph, beneficial ownership
and timing. Identify potential mule rings under 6AMLD predicate offences.
Return: cluster ranking + recommended escalation.

Helps the L2 analyst prioritise which alerts probably belong to the same network.

Regulatory context

FATF and 6AMLD, the typologies to ask for.

Prompts can draw on the FATF Recommendations and the typology guidance published in the FATF reports library, covering structuring, trade-based money laundering, professional money laundering, virtual asset service provider exposure, mule networks, sanctions evasion, terrorism financing red flags and tax-related predicates. The model works from its training and what you provide, not from a maintained typology database.

For EU regulated entities the agent can map findings against the 22 predicate offences listed under the Sixth Anti-Money Laundering Directive, including environmental crime, cybercrime and tax-fraud thresholds. Beneficial ownership opacity, PEP layering and high-risk-third-country exposure are flagged with references to the relevant 6AMLD articles, which the MLRO should check.

The agent does not interpret the law. It surfaces typology hits and red flags with references the MLRO uses as a starting point. The legal interpretation, the final classification and the SAR / STR filing decision remain human responsibilities.

Output format

SAR-ready narratives, in your jurisdiction's format.

The agent drafts the narrative section in the standard structure your reporting authority expects: subject identification, activity description, why-suspicious analysis, supporting evidence, recommended action. The MLRO edits and signs.

  • FinCEN SAR, United States
  • Tracfin DS, France
  • NCA SAR, United Kingdom
  • FIU.ITA, Italy
  • FIU Spain (Sepblac), Spain
  • BaFin / FIU Germany, Germany
  • FINMA SR, Switzerland
  • AUSTRAC SMR, Australia

Comparison

VoltageGPU AML agent vs Quantexa, ComplyAdvantage, NICE Actimize.

Quantexa, ComplyAdvantage and NICE Actimize are full transaction monitoring and screening platforms. VoltageGPU is a confidential AI agent layer designed to sit on top of one of those, not to replace it.

DimensionExisting TMS (Quantexa / Actimize / ComplyAdvantage)VoltageGPU AML agent
RoleGenerates and screens alertsTriages alerts and drafts narratives
Confidential computeNo published TEE inferenceInference in Intel TDX
Data residencyVendor-dependentEU company; inference on a third-party network; sub-processors named
Narrative draftingVaries by productAI drafts for MLRO review
Replacement or layerTMS itselfLayer on top of your TMS

Pricing

Same tiers as the financial compliance pillar.

Starter $349/mo (3 seats), Pro $1,199/mo (10 seats, DeepSeek-V3.2-TEE reasoning), Enterprise $3,499/mo (unlimited seats, SCIM 2.0, RBAC admin console, admin audit log).

See full pricing

FAQ

Questions AML officers ask first.

Does the agent file SARs automatically?

No. Drafts only. The MLRO or designated reporting officer reviews, edits and signs every filing through their existing reporting channel.

Does it replace our TMS?

No. It is a layer on top of your existing transaction monitoring system. Deterministic rules and screening stay where they are; the agent helps the team triage and draft narratives.

What happens to the alert payload after analysis?

It passes through our servers to the TDX enclave and is not kept. The chat stays in your browser. If you choose to file it into a Matter at /workspaces (Beta), it is stored encrypted at rest in the EU as a note; the assistant does not read Matter files yet. No training on user data.

Can we run this as a scheduled agent?

Only as a custom scheduled prompt at /scheduled. Scheduled runs have no access to the web, your files or your TMS, so they cannot pull alerts or refresh sanctions lists.

Does it pull from our TMS, case manager and sanctions feeds?

No. Connectors at /connectors cover Gmail, Google Drive, Slack, GitHub and Microsoft 365; there is no TMS, case-manager or sanctions-feed connector. The Starter plan includes 3 connectors, Pro 5, Enterprise unlimited.

Can we audit the typology library used?

There is no separate typology library. The agent is an AI model following a review checklist and works from its training and your prompt, so the MLRO should check every typology reference against the FATF source.

Related

Financial compliance pillar

Back to the AML / audit / FP&A hub for finance teams.

Audit Automation AI

Walkthroughs, sample-test summaries, SOX 404 control narratives.

FP&A AI Agent

Variance analysis, forecast drafts, board memos, inference in Intel TDX.

Sovereign Agentic AI

The hub: vertical agents for legal, finance and regulated professionals.

DORA AI compliance

How VoltageGPU lines up with DORA Article 28-30 third-party risk obligations.

Plans & pricing

Starter, Pro, Enterprise, see what each tier includes.

Security & trust

How requests reach the Intel TDX enclave, and what we store.

Contract Analyst

The flagship legal agent, same architecture pattern.

VoltageGPU for fintech

Sector page: AML, KYC, DORA and SOX-aligned agent workflows.

Confidential agents catalogue

The full agent line-up across legal, finance, healthcare and operations.

Confidential compute platform

The infrastructure layer: Intel TDX confidential compute.