Where screening fits in document automation
The risk of automating documents is that speed launders mistakes: a name nobody read gets filed into a legal document nobody can unfile. Screening has to sit inside the automation, not beside it — every packet, every time, before filing.
Screening is heuristic and can misfire on transliterated names, which is why a hit produces a gated decision rather than a silent hard block: the operator sees the flagged party, acknowledges the risk explicitly, and the override is logged.
How the compliance gate works
- Extraction identifies the parties on the packet from the OCR-grounded fields.
- Screening runs before order matching and filing — a packet cannot auto-file without a clear result.
- A hit moves the packet to review with the flagged party named.
- An operator either corrects the extraction, rejects the packet, or overrides with an acknowledgment that is recorded.
Designed for auditability
The point is not that software decides sanctions questions — it cannot. The point is that no packet skips the question, and every human answer leaves a trace.
Frequently asked questions
Does a sanctions hit permanently block a packet?
No. Screening can misfire, so an operator can override — but only with an explicit acknowledgment, and the override is logged.
Is screening skipped when auto-filing is on?
Never. A clear sanctions screen is one of the required gates for auto-filing; without it the packet waits for a human.