Table of Contents
The choice between real-time vs batch sanctions screening shapes how fast you catch a bad party and how much manual work your team carries. Real-time screening checks a name at the moment something happens. Batch screening checks many names at once on a schedule. Both matter. Most compliance programs run both, and they run them for different jobs.
This guide explains what each method does, where each one fits, and how to combine them. You will see the trade-offs in plain terms, a side-by-side table, and steps to set up a program that uses both without gaps. If you are new to the topic, start with the basics of denied party screening first, then come back here.
What real-time sanctions screening means
Real-time screening runs a check the instant a triggering event happens. A new customer signs up. A payment is about to send. A purchase order is created. The system compares the party against sanctions and denied party lists right then. It returns a result in milliseconds. If there is a possible match, the transaction stops and waits for a person to review it.
The point of real-time screening is to block a bad transaction before it completes. You do not want funds to move to a sanctioned party. You do not want to ship goods to a denied entity. Real-time screening puts the check in the path of the action, so nothing gets through unchecked.
Where real-time screening fits best
- Payment processing, such as wire transfers and card authorizations
- Customer onboarding and account opening
- Order entry, before you confirm a sale or book a shipment
- High-risk deals in sensitive countries or sectors
What batch sanctions screening means
Batch screening runs a large group of records against the lists on a schedule. It might run every night. It might run right after a sanctions list is updated. The system takes your whole customer base, or a set of open transactions, and checks all of them in one pass. Results come back as a report of alerts your team then reviews.
The point of batch screening is coverage over time. Lists change often. A customer who was clean last month can appear on a list today. Real-time screening only checks a party when something happens. Batch screening re-checks everyone, so a new designation does not slip past a dormant account.
Where batch screening fits best
- Ongoing monitoring of your existing customers and suppliers
- Re-screening the whole book after a list update
- Portfolio reviews before an audit or a regulator visit
- Historical checks on past transactions
Real-time vs batch sanctions screening: side by side
The two methods answer different questions. Real-time asks, “Is this party safe to deal with right now?” Batch asks, “Is anyone in my whole book now a problem?” The table below shows the main differences.
| Factor | Real-time screening | Batch screening |
|---|---|---|
| Speed | Milliseconds per check | Minutes to hours per run |
| Trigger | An event, like a payment or signup | A schedule or a list update |
| Scope | One record at a time | The whole set at once |
| Main job | Stop a bad deal before it completes | Catch changes across your whole book |
| Alert flow | Handled one at a time as they arise | A batch of alerts to work through |
| Cost driver | Low-latency systems, high uptime | Compute during off-peak windows |
Why you need both, not one
Picking only one method leaves a hole. Run real-time alone and you never re-check a customer after they onboard. If they land on a list next year, you miss it until they transact again. Run batch alone and a sanctioned party can slip through a live payment before the next nightly run catches it. The gap between runs is the risk.
So the two methods cover each other. Real-time guards the moment of action. Batch guards the passage of time. Together they close the gap. This is why regulators expect payment screening in real time and ongoing monitoring on a schedule. One does not replace the other.
Keep both engines identical
The two methods should use the same matching logic and the same list data. If your real-time engine and your batch engine score names differently, you get gaps and confusion. A name that passes real-time might flag in batch, or the reverse. Use one set of lists and one set of rules for both. That keeps your results consistent and your audit story clean.
Which lists to screen against
Both methods are only as good as the lists behind them. A common starting point in the United States is the Consolidated Screening List, which combines the main export and sanctions lists from several agencies into one file. Many programs also screen the OFAC SDN list, the BIS Entity List, and non-US lists such as the EU and UK targets.
- Refresh list data often. Designations change, sometimes daily.
- Screen against every list that applies to your trade lanes.
- Apply the 50 percent rule for entities owned by sanctioned parties.
- Match on name variants, aliases, and spelling differences.
For a deeper look at how each screening run should work end to end, see the guide on how to process denied party screenings.
Handling false positives in each method
Both methods produce false positives. A common name can match a listed party even when the two are different people. How you handle these depends on the method.
In real-time screening, alerts arrive one at a time. A reviewer clears or escalates each one fast, because a transaction is waiting. Speed matters here. A slow review holds up a payment or a shipment. In batch screening, alerts arrive in a group. Your team works the queue in a block. This is easier to plan for, but a large list update can create a spike of alerts to clear.
Tune your matching to cut noise without hiding real hits. Good rules reduce false positives on both sides. For a practical method, read how to resolve a false positive in denied party screening.
Setting up a combined program
You do not have to choose. A sound program uses real-time checks at the moments that matter and batch runs to cover the rest. Here is a simple order to build it.
- Map your trigger points. Note where a live check must block an action, such as onboarding and payments.
- Turn on real-time screening at each of those points.
- Schedule a batch run for your whole book, at least daily, plus a run after each list update.
- Use one list source and one set of matching rules for both engines.
- Set clear steps for who reviews an alert and how fast.
- Keep records of every check, every alert, and every decision.
Records matter for audits and for defending a decision later. Store the list version, the score, the reviewer, and the outcome. See record keeping for denied party screening for what to save. For broader guidance on running a strong program, review denied party screening best practices.
Frequently Asked Questions
Is real-time screening always better than batch?
No. Real-time is better for blocking a live transaction. Batch is better for re-checking your whole base after lists change. Each does a job the other cannot. Use both.
How often should batch runs happen?
At least daily for most programs, plus a run right after any list update. High-risk businesses may run more often. The right pace depends on your risk and how fast lists change. See how often to screen suppliers and customers.
Does batch screening slow down my transactions?
No. Batch runs on a schedule, apart from live transactions, often overnight. It does not sit in the payment or order path. Only real-time screening adds a check at the moment of action, and that check takes milliseconds.
Can small businesses run both methods?
Yes. Many screening tools include both real-time and batch modes. A small firm can screen at onboarding and payment, then schedule a nightly batch run. The setup scales down well. Manual checks work too, but they are slower and harder to audit than an automated tool.
Key Takeaways
Real-time and batch screening are not rivals. Real-time blocks a bad deal at the moment it happens. Batch catches changes across your whole book over time. Run both, feed them the same lists, and use the same matching rules so results stay consistent. Refresh your list data often, tune your matching to cut false positives, and keep records of every check and decision. Do that and you close the gap that a single method leaves open. If you want help designing a screening program that uses both methods well, contact the Globalior team.