Introducing Sphinx SAR Filing: Drafted While You Investigate

A document written in an afternoon, read a year later

A SAR narrative has an odd life. It gets written once, at the end of a long case, from notes that were taken for the investigation and never meant for anyone else. Then it sits. The person who reads it closely is often an examiner, opening the file cold, maybe a year later, with nobody in the room who remembers the case.

That reader gets whatever survived the rewrite. If the analyst was tired, or the queue was long, or it was the fourth filing that week, it shows. Getting the prose right is a craft, and we've written about how to write a better SAR narrative. The harder problem is that the narrative is written at the worst possible time, after the thinking is finished and the details have started to fade.

So we stopped treating the write-up as a separate job.

What changes

One row doesn't change, on purpose. Sphinx does not decide whether to file. That call stays with the analyst.

Inside a draft

From an open investigation, Sphinx agents assemble the SAR in the shape the regulator already expects. The analyst opens it, reads it, and fixes what needs fixing.

• The sections a SAR already has. Subjects, the suspicious activity, where it occurred, the filing institution, and the narrative, filled from the case while it's still open.
• The evidence beside the story. The customer record, the review period, and the monitoring note stay next to the draft, so the narrative never drifts away from what it describes.
• Warnings before anything leaves. Missing fields and inconsistencies surface before submission, while they're still easy to fix.
• One queue for the month. Drafts, deadlines, and what has already gone out sit in one place.
• Filing without leaving Sphinx. Sphinx integrates directly with FinCEN and dozens of other regulatory bodies, so approved reports go out from the same place they were written. Teams can also export the XML or download the report.

The number we watch

Customers have filed over 5,000 SARs through Sphinx. Over 8,000 hours have moved from the write-up back into investigation.

The first number is volume. The second is the point. Those are hours analysts spend on the next case instead of describing the last one.

There is a quieter effect too. When a filing no longer costs the rest of the afternoon, teams report what they should. The borderline case gets written up the day it's found, instead of waiting for a quieter week.

What it doesn't do

It doesn't decide. Whether a case warrants a SAR is a judgment, and it belongs to the person accountable for it. If you're working through that question, our guide on when to file a SAR walks through it.

It doesn't file on its own. Every report is reviewed and approved by an analyst before it goes anywhere.

And it doesn't leave you reconstructing anything later. Each draft stays tied to the case it came from: the evidence reviewed, the analyst who approved it, the version that was filed. When an examiner on a lookback asks how a SAR from last year was written, the answer is on the screen, not in someone's memory. It's the same standard we hold the rest of the product to, written down as the Interpretable Agentic Framework.

Try it on a SAR you've already filed

The clearest test is a case your team has already closed and filed. Run SAR Filing on it in your Sphinx workspace and put the draft next to the narrative written by hand. The narrative used to be the part teams dreaded an examiner opening. We think it becomes the part they show first.

If you lead BSA, AML, or financial crime operations at a bank, payments company, lender, or fintech, talk to us and we'll walk through it on your own cases.