Every quarter, the compliance team at a parts supplier faced a familiar job: screen the companies it bought from and the companies it sold to, review relevant ownership information and produce a record for compliance. The customer asked us not to publish its company name, but agreed to share how the process works.
Running a batch was not the hard part. The supplier's previous screening provider could accept a file and return results. The problem appeared at the next quarterly upload: the platform could not preserve a one-to-one connection between each customer record and the case outcome from the previous review.
The same false positives therefore came back as fresh work. An analyst could have already established that a candidate concerned a different person or company, documented the reasoning and closed the case. Yet the next quarterly batch gave the team no reliable way to reconnect that decision to the same internal record. Time was spent retracing work that compliance had already completed.
A quarterly control that keeps its history
The parts supplier wanted to retain the simplicity of a spreadsheet. Its compliance users did not need a large IT integration or an API project for this recurring process. They needed to upload an Excel or CSV file themselves, synchronise the population and know that the records in the file still referred to the same suppliers and customers reviewed in the previous quarter.
The connection is made through the customer's stable internal IDs. Each row carries the ID used in the supplier's own records. When the file is synchronised with Checklynx, that ID keeps the counterparty associated with its screening and case history.
This changes the starting point for the next review. If the same candidate has already been resolved as a false positive and the relevant information has not changed, the earlier decision remains associated with the counterparty instead of returning as an entirely new case. The compliance user can concentrate on results that actually need attention.
Past decisions are not permanent clearance: a changed name, identifier, ownership record or other relevant information can return a result to review. What disappears is only the need to re-investigate the same unchanged match.
Checklynx's CSV Batch Screening supports the upload and synchronisation workflow. For this customer, it meant the quarterly control could be run by a non-technical compliance user without rebuilding the connection to prior work each time.
Screening suppliers, customers and ownership
The population covers both sides of the parts supplier's commercial relationships: suppliers and business customers. The team also needs to understand the companies and owners behind relevant counterparties, rather than treating a company-name screen as the end of the review.
Ownership data is supplied by an external registry and UBO provider through a Checklynx integration partner. Checklynx maps the companies and owners in that data, derives the ownership percentages and screens the resulting parties. The compliance team decides whether the data is sufficient and how the relevant rules apply.
That mapped view can support an assessment under rules such as the OFAC 50 Percent Rule, which can treat an entity as blocked when blocked persons own 50% or more in aggregate, directly or indirectly. Other jurisdictions apply their own ownership and control tests.
The UBO and related-party screening guide explains this separation between registry data, ownership mapping, screening and legal assessment. The wider supplier and third-party screening guide covers how organisations can define the relationships and parties that belong in their own screening scope.
From a spreadsheet to a compliance record
At the end of the quarterly cycle, the supplier produces a report for its compliance team. The report connects the reviewed population with the screening results and the case decisions made during that period. It also makes unresolved work visible, so the handoff is more useful than a spreadsheet containing names and raw matches alone.
Stable IDs are important here too. They connect the report back to the supplier's own records and help show which customer or supplier was checked, which case history belongs to it and what the team concluded. Ownership information can be considered alongside the mapped companies and owners rather than being kept as a separate, disconnected exercise.
Quarterly is this customer's scheduled review rhythm, not a universal rule or a reason to ignore intervening changes. A material change may require attention before the next batch. The guide on when to re-screen suppliers explains how a scheduled cycle can work alongside change-based reviews.
Less repeated work, without a complex rollout
The difference for the customer was practical. The old provider could run a batch, but each quarter risked reopening the same false-positive work. Checklynx kept the familiar Excel or CSV process while connecting each stable customer ID to the earlier case outcome.
That gave the compliance team a more focused quarterly review. Analysts could see prior work where it still applied, investigate changed or unresolved results and produce the evidence needed for the internal compliance record. The customer reported saving substantial review time by avoiding unnecessary repetition; no percentage was provided.
The same customer also left public feedback on Capterra:
“Helped us to replace our current AML screening workflow”
Capterra lists this as a non-incentivized review. It is Silvia R.'s account of the experience, not an audit or measurement study.
Make the next quarterly review build on the last one
For teams managing a recurring population of suppliers and customers, the starting point is simple: preserve a stable identity for each record and keep its review history attached. From there, Excel or CSV can remain an accessible operating tool rather than forcing compliance to start again every quarter.
Talk to Checklynx about supply-chain screening to discuss batch synchronisation, persistent cases and ownership-data workflows. The manufacturing and supply-chain solution shows how these controls fit into a wider operating process, while the API versus batch guide compares delivery options.
Customer results and public-review observations are specific to this implementation. The customer remains responsible for screening scope, ownership-data assessment, legal interpretation and final decisions.