CTB Database AML Intelligence Hub database · prepared by AIDA Labs
Connecting to the database…

Executive Data Analytics

The health of the AML Intelligence Hub database, live: what it holds, how old it is, whether every feed is arriving, where suspicious activity concentrates and what needs tuning. Fictional demo data. Every number opens the records behind it.

Records added per day · last 7 days

New alerts, cases, FINTRAC reports, sanctions hits and risk-rating changes each day, up to the latest load. Select a day or a coloured block to see the records.

Show as a table

Records by type

How many rows each kind of record holds. Business records are what investigators work; snapshots and controls are what keep the numbers honest.

Business records

    Rows by group

      Records by age

      How old each type of record is, counted back from the latest load. Old open work and old data both need a decision.

      Show as a table

      Records by status

      Where the work stands: what's open, what's closed and what came out of it.

      FINTRAC reports

      Records by source and data per feed

      Every source feed: how reliably it arrives, how much it brings, and what the quality gate caught.

      Load calendar: are the scans running?

      Each square is one day's load for one feed over the last 60 days. A gap means the load never ran. Hover or tap a square for the date.

      On timeLate Missed / not receivedNo load logged

      Hot spots: where alerts and STRs concentrate

      The rules, products, typologies and sources that produce the most suspicious transaction reports (STRs). Look here first for bad actors and for monitoring that pays off.

      Repeat subjects (masked)

      What needs tuning

      Rules that mostly produce noise or haven't been reviewed in a year, data fields and checks below 99.5%, and KPIs not yet certified.

      Monitoring rules

      False positives = alerts closed with no further action, as a share of decided alerts. Tune: 90% or more, or no change in over a year. Watch: 85% or more, or no change in 9 months.

      Rules not changed in over a year

      Below-the-line testing

      Share of sampled alerts just under the threshold that deserved escalation. Above 5% suggests the threshold is too high.

      Data fields below 99.5% complete (last 90 days)

        Validity checks below 99.5% (last 90 days)

          KPIs not yet certified or without full lineage

          All tables

          Every table in the reporting mart, with its exact row count and the dates it covers.