KYC & relationship
Customer file, beneficial owners, declared source of funds, expected activity, prior dispositions and every open alert on the relationship.
18 records
Platform
Heelius does not replace your rules engine, your case manager or your screening vendor. It consumes the alerts they produce, investigates each one against your own records, and writes back a disposition with a narrative and a full evidence trail.
The investigation
Heelius does not summarise an alert. It performs the investigation — retrieving the same records an L2 analyst would pull, in the same sequence, and showing its work at every step.
Customer file, beneficial owners, declared source of funds, expected activity, prior dispositions and every open alert on the relationship.
18 records
The alerted window plus a trailing twelve-month baseline, tested for threshold proximity, velocity, round-value patterning and pass-through.
347 txns
Entity resolution out to three hops. Shared devices, common funding addresses, sequential registrations and circular flow between nominally unrelated parties.
3 hops
Consolidated list screening with discriminator logic — the agent states which identifiers diverge, and never clears on a name mismatch alone.
4 lists
42 languages, deduplicated by event, each candidate tested for homonym risk against date of birth, employer and biography.
1,840 articles
Aggravating and mitigating findings scored against the institution's own thresholds. Unresolvable evidence routes to a human — it is never rounded to clear.
8 findings
Six sections in the conventional order — subject, activity, findings, mitigants, screening, disposition — with a source citation on every asserted fact.
6 sections
Every assertion is traced back to a retrieved record before the case is released. Unsupported prose fails the check and is redrafted.
100% traced
Narrative engine
Narratives are assembled from retrieved records, not written from a summary. Every asserted fact carries the record it came from — so an examiner can walk any sentence back to the ledger it was drawn from.
Retrieved evidence
Unsupported prose fails self-QA and is redrafted before release
Generated narrative · ALT-2026-88104
Activity under review
Alert ALT-2026-88104 was generated by rule TM-STR-004 covering eight transactions totalling 46,300 USD through the retail deposit channel between 20 and 25 August 2026. Five cash deposits ranging from 8,900 to 9,600 USD were placed across three distinct branches, none reaching the 10,000 USD currency-transaction reporting thresholdF-1F-2. The alerted volume represents 1.2× the customer’s declared monthly expectation of 40,000 USDF-3.
Findings
Within 72 hours of the final deposit, 34,000 USD was remitted to a Brazilian construction counterparty against an invoice reference that matches the supplier recorded at onboardingF-4. Sanctions screening returned a single 0.71 fuzzy candidate, discounted on a 14-year date-of-birth divergence and a non-matching jurisdiction under the institution’s two-discriminator ruleF-5.
Integrations
Every record enters through a typed connector with a stable schema, which is what makes retrieval replayable and a case defensible a year later.
Who it is for
Alert volume scales with account growth while headcount does not. Heelius takes the L1 tier whole and gives the compliance team back its senior people for the escalations that actually carry filing risk.
Agent float, till networks, SIM co-registration and cross-border corridors — typologies that legacy tooling was never shaped for, at a per-alert price that works against a local compliance budget.
Corridor-level baselines, aggregated originator handling and beneficiary-side disbursement reconciliation, with narratives in the format each receiving regulator expects.
On-chain attribution joined to the fiat relationship: bridge structuring, unhosted exposure, mixer hop distance and related-party settlement back to the registered UBO.
Where the model has to change
Legacy investigation tooling assumes a correspondent bank's data model and a Western analyst's budget. Both assumptions break in the places where alert volume is growing fastest.
Operators in Nairobi, Lagos, Dhaka and Manila carry the same FATF obligations as a tier-1 bank on a fraction of the compliance budget — and alert volumes that scale with subscriber counts, not revenue. Heelius investigates agent float velocity, SIM-cluster co-registration, device overlap between nominally independent tills and cross-border corridor anomalies.
Chain analytics tells you an address is risky. It does not tell you whether your customer's use of it is suspicious. Heelius joins on-chain attribution to the fiat side of the relationship — bridge structuring below travel-rule thresholds, unhosted-wallet exposure, mixer hop distance, related-party settlement back to a registered UBO.