Financial crime: governed facts about a customer

Relata DB 3.0
The domain SQL operators SANCTIONS_SCREEN, CRYPTO_TRACE, WIRE_RECONSTRUCTION and BENEFICIAL_OWNERSHIP_CHAIN were removed from core in 3.0, and so were report composition and signing. This page describes what remains. See the migration notes and the What is new in 3.0. Sanctions list data and screening logic are loaded and run by you or by OpenETL.

The problem

Two systems disagree about where a customer lives. An analyst needs to keep both claims, decide which to trust, correct a wrong one without erasing it, and later show a regulator what the system believed on a given date and why.

The shape

  • Assertions (POST /v1/assertions) record a claim with its source. Analysts confirm or reject with POST /v1/assertions/{id}/decision. A correction supersedes the earlier claim without overwriting it, and POST /v1/assertions/{id}/revoke tombstones a claim. GET /v1/assertions/resolve returns the verdict and explains it as of any valid and recorded time. Resolution rules are a named policy (PUT /v1/assertions/policies/{name}).
  • Ledger-style writes use PUT /v1/objects with If-Match / If-None-Match and atomic bundles through POST /v1/commit, with cursor pagination on GET /v1/objects.
  • Time travel is SQL: SELECT ... FROM Account AS OF SYSTEM TIME '<ts>' and WITH PROVENANCE. Every row carries valid and system time.
  • Legal hold (POST /v1/retention/holds) blocks revocation and erasure of held records.
  • Screening against your own list is a SQL join or a POST /v1/search against a watchlist type you load. Relata no longer ships a sanctions operator or list.
  • Graph tracing of money movement uses links and GET /v1/graph/traverse, plus the SQL graph operators such as DEGREE. The UETR chain and window sums are ordinary SQL over the rows you load.

Honest limits

  • No sanctions feed, no screening operator and no signed report bundle ship in the open build.
  • A bare SELECT COUNT(*) or an unfiltered SUM was observed to include rows that were erased, and a restored node aggregated superseded row versions. Filter on the columns you aggregate until those defects are fixed.
  • Single tenant. Separating several business units in one deployment is Enterprise.

Exercised by

Scenarios V3-09 (bank-ledger transfers with If-Match, atomic bundles, pagination, passed), V3-10 (KYC address from competing sources, review, correction, revocation, legal hold, passed) and the Fincrime F1-F8 journeys on the 3.0 port (SQL name join, search, graph traverse plus DEGREE, UETR chain; the retired operators were removed from the assertions) in the relata-test battery, 2026-11-03, on a debug build. The aggregate defects above come from V3-12.