A bank's transaction network with $47M flowing through shell companies. Suspicious Activity Reports filed retroactively — backdated months after the fact. The bitemporal question that changes everything: at the time we cleared that wire transfer, what SARs had we actually filed?
$47M
Laundered flow
500
Shell accounts
0
SARs at wire time
18 mo
Investigation span
Loading…
The investigation
Loading…
■ AT RECORDED — Compliance Record
What the bank knew at this moment
Suspicious Activity Reports on file
—
Querying…
Shell account volume (recorded)—
Wire transfers cleared—
Compliance status at clearance—
■ AT VALID — Full Picture
What should have existed (current knowledge)
SARs valid at this moment in time
—
Querying…
Total shell volume (all knowledge)—
Backdated SARs (filed later)—
Gap — SARs missed at clearance—
Regulatory gap: — SARs existed in valid time but were not recorded when the wire was cleared.
Transaction flow network
Loading graph…
Querying…
AccountShell Co.TransactionSARBank
Network status
AML Transaction Network
Loading…
—
Accounts active
—
Shell companies
—
Tx volume (shell)
—
SARs filed (recorded)
△ Layering pattern detected
Top shell intermediaries
Loading…
Show the Cypher queries running this demo (real, live, against aml_network)
1. SAR count as recorded at date D (bitemporal — what was on file at the moment)
Loading…
2. SAR count in valid time at date D (full picture — what should have existed)
Loading…
3. Transaction volume through shell companies at date D
Loading…
4. Shortest path — source through shells to destination
Loading…
Your compliance team shouldn't discover this in hindsight.
Every transaction, every SAR, every relationship — replayable at any moment, in both valid time and recorded time. Know exactly what your team knew at clearance. Prove it to regulators.