What is batch AML screening?
Batch AML screening is the processing of a file or queue of customers and counterparties against watchlists asynchronously, instead of blocking a single HTTP request on one name.
When batch is the right tool
Historical book screening, periodic re-checks, and catching up after a list update. It is the wrong tool for a user waiting on signup if you can do a synchronous screen.
How it joins to cases
Every row still needs your customer external id and a returned screening id. Overnight hits must land in REVIEW with the same audit keys as onboarding.
Naiza’s split
Use real-time screening where the user waits. Use batch or event-driven re-screening for the existing book. See the comparison of real-time vs batch AML and ongoing monitoring.
Frequently asked questions
Short answers written so search and answer engines can cite them.
What is a batch sanctions screening API?
It accepts many names and returns structured matches asynchronously so you can backfill or re-screen a portfolio without a request per row on the hot path.
Can batch replace onboarding screening?
No. Someone listed this morning should not wait for tonight’s job before they can pay. Run real-time at the decision, batch for the book.
Is batch the same as ongoing monitoring?
Ongoing monitoring is the control. Batch is one implementation. Event-driven re-screening on list updates is another.