Most treasury teams can tell you exactly what happens to the money they send. Far fewer can tell you what happens to the money that arrives.
Outbound sanction screening has become a well-working discipline. Every payment is checked against sanction lists before it leaves. But one-directional screening — as the name suggests — only covers half of the exposure. A supplier, a customer, an unfamiliar third party can pay funds into the business, and in most setups those funds arrive unchecked — or get reviewed by hand, well after the fact.
That asymmetry is increasingly hard to defend — and that’s what TIS faces regularly. Banks are asking organizations directly about their inbound payment controls. Auditors consistently flag one-sided screening as a gap. And the common fallback — “we screened them at onboarding” — doesn’t hold as onboarding screening is a point-in-time check on one contracted entity, while sanction lists change daily and payments often arrive from different entities inside a customer’s group.
New: Inbound Sanction Screening
A new release in the Sanction Screening module of TIS’s Payments Hub extends screening to incoming payments.
As statement data is received, incoming transactions and their related counterparties are checked automatically against configured sanction and watch lists — including OFAC, EU, UN, HMT, Dutch sanctions lists and other supported international watchlists. Potential matches surface as alerts in a dedicated Inbound Screening Alert Monitor, where the compliance team investigates each one, dispositions it as a true or false positive, and documents the decision. Every step leaves an audit trail.
If Outbound Sanction Screening ensures you don’t send money to sanctioned parties, Inbound Sanction Screening ensures you don’t receive money from them.
Being precise about what this is — the feature identifies and routes exposure for human review. It does not block or intercept incoming funds — by the time a receipt appears in statement data, the money has already landed. What changes is that you find out in hours rather than never, inside the time window you’re given to act.
The reality today: screening that only runs one way
In a typical setup, outbound payments pass through sanction screening rules as a matter of course. Incoming credits don’t. The practical result:
- Received funds are reviewed inconsistently, or not at all;
- Where review happens, it’s manual and retrospective;
- There’s rarely documentation to prove the review took place.
The last point is the one that tends to surface in an audit. The question is not only whether exposure was caught — it’s whether the organization can demonstrate that it looked. Manual review across high inbound volume doesn’t scale, and it leaves documentation gaps precisely where evidence is expected.
What changes with inbound screening in place
With TIS’s inbound screening running, the impact is twofold:
- A real compliance gap closes — sanction screening extends to incoming funds, not just outgoing payments, so exposure is identified before the money is absorbed into business processes.
- A structured, auditable workflow — potential matches land in a dedicated queue rather than someone’s inbox, with investigation, disposition and documentation recorded in one place.
Sanction coverage becomes symmetric, and it does so without adding another system to the stack.
Why this matters now
Regulatory attention on sanction exposure is not easing, and the burden of proof continues to shift toward the organization. It is no longer sufficient to rely on banks screening their own flows — banks screen against their obligations, not yours, and the responsibility for demonstrating your own controls stays with you.
Inbound exposure is where that responsibility is most often unmet, not because teams don’t recognize the risk, but because there hasn’t been a systematic way to address it inside the systems they already run.
Talk through your setup
In TIS, Inbound Sanction Screening is available as a paid add-on. It requires the TIS Platform with the Bank Statement Management (BSM) module and an active sanction screening configuration — it isn’t switched on by default.
If you already screen outbound payments today and haven’t yet addressed the inbound side, it’s worth a conversation about how your current configuration is set up and where the gaps sit.
Reach out to TIS to set up a demo.
