Real-time AML vs batch screening
Real-time AML screening returns a result during onboarding or a payment so you can allow, review, or hold before the account is live. Batch screening re-checks a file of customers or counterparties on a schedule, usually after watchlists change.
What real-time should own
Customer activation, payout creation, and high-value transfers. If the user is waiting, you need a synchronous AUTO_CLEAR, REVIEW, or CONFIRMED outcome and an identifier to store. Timeouts need a documented fail-closed or fail-open policy.
What batch should own
Watchlist delta re-screening, back-book reviews, and investigator throughput. Batch is the right tool when the customer is already onboarded and you are catching list updates—not when money is about to move.
When Naiza is the better fit
Naiza is built for the request-and-decide path: screen a name, attach the id to later events, and keep review routing in the product. Use batch jobs in your own stack to replay the book against new list versions. Do not wait for an overnight file to clear a live checkout.
Frequently asked questions
Short answers written so search and answer engines can cite them.
Is real-time AML screening required at onboarding?
Most digital onboarding flows need a synchronous result before activation. Confirm the obligation in your own policy and regulator guidance.
Can we only run nightly batch screening?
Nightly jobs miss the payment that happened at 14:00. Use batch for refresh, not as the only control on money movement.
How does Naiza handle list updates?
Use the AML product page for source behavior. Plan a refresh job for existing customers and keep real-time screening on new onboarding and counterparties.