A sanctions list update, screened against your customers the minute it lands.
Sanctions lists change during the day, and an overnight run leaves a newly listed customer free to transact until tomorrow. Calseda screens your customers against each list update the moment it arrives. Every hit shows the list entry and the customer name it matched.
A name added at 09:47 waits for tonight's screening run.
A company is added to a sanctions list at 09:47, and one of your customers has the same name. If the customer is the listed company, UK guidance says its funds “are to be frozen immediately”.
| Time | Tonight's run | With Calseda |
|---|---|---|
| 09:47 | The customer keeps transacting. | The customer is a hit at once, with the list entry and the customer record it matched. |
| 09:55 | Nothing yet. Screening runs tonight. | The hit is in your case management tool, sent by webhook, and an analyst reviews the evidence. |
| Next morning | An analyst reaches the match among thousands of others. Someone asks why the customer was not stopped yesterday. | The match was reviewed yesterday morning, the day the name was listed. |
Add a name to the demo's list, and a customer with that name is a hit at once.
The demo screens 20 customers against OFAC's SDN list (US Treasury), again whenever a new edition is published. An exact match by name stands in for your screening engine.
Add one yourself, no sign-in: Screening that keeps up with the lists ↗
The same demo sends each news story about a watched company to an outside service that reads it, once per story: News alerts for your watchlist ↗
Show your regulator how fast each list update took effect.
Calseda measures, for every list update, how long it took from its arrival to the screening results. That is your management information on timeliness.
- Every hit opens to the list entry and the customer record it matched, where each came from and when it arrived, down to the raw data. Export it as a report for your auditor or regulator.
- Matching thresholds stay with your team. A threshold changed by hand carries who changed it, from their sign-in.
See a list change take effect the same morning
Start with one customer book and one list, screened beside tonight's run for a few weeks. Your team writes the matching rule and Calseda runs everything around it, in your own environment, or Calseda calls the screening engine you already use.
Become a design partner: one list screened against one customer book in about six weeks, for a fixed fee. At the end you keep the framework, licensed to run what you built on one server.
Your compliance colleagues can have all this on one page: Financial crime (PDF).