SAP GTS 2025: c/o name and employee screening in SPL checks

Names are messy. They arrive through c/o lines, bank details, employee records and operational shortcuts that made sense to somebody once.

Separate c/o and employee screening expands coverage, but it also raises the bar for data quality, legal basis, audit evidence and user explanation.

Here is the project version: SAP GTS 2025 adds more screening depth in two practical areas: c/o name handling and employee screening. The c/o name can be screened separately in SPL Screening with SAP HANA Search, and employee data can be screened for supported S/4HANA employee business partners. That sounds simple, which is how SAP topics lure us into underestimating them.

The SAP evidence trail is less romantic: Care-of-name screening matters because address data can contain relevant names outside the main partner name. In some industries and regions, c/o names are operationally meaningful and can change the compliance risk picture. In a clean demo this takes minutes; in production it asks for ownership, variants and a little courage.

Treating them as separate searchable terms improves coverage when the data is maintained correctly.

This is where the support ticket usually starts: Employee screening extends the compliance model beyond customers and suppliers. For organizations that require employee-related screening, the key design question is not only technical transfer. The screen is only the stage. The process is the plot.

It is data ownership, consent/legal basis, screening frequency, role design and audit evidence.

The control angle is the part worth underlining: The implementation risk is false confidence. Screening more fields does not automatically mean better compliance if the source data is inconsistent. A consultant should be able to explain this without opening a thirty-slide apology deck.

Teams should review partner address quality, employee partner role maintenance and comparison-procedure settings before relying on the expanded coverage.

For training, the useful lesson is this: Training should show how a match can originate from the main name, c/o name or employee data, and how the audit trail reflects the source of the match. Users need to understand where the matched term came from before they can make a defensible decision. That is the difference between technical navigation and knowledge people can reuse.

The field looked harmless. Compliance fields often do, right up until they meet a screening list.