Batch screening
Batch screening takes a spreadsheet of names and screens them all against LSEG World-Check in one run, without filing a case for each. It is a testing tool for the Vindex team.
What it is for
Trying a list of names at once: to see which return results, to compare how World-Check treats a set of similar names, or to find good test subjects before filing full cases. Each row is screened on its own; nobody is put under ongoing screening, and no Vindex case is made.
Why one call per row
LSEG's web application has a batch upload, but its API screens one name per call. So a batch of 50 rows is 50 calls against the account's allowance. Vindex shows that cost before anything is sent.
Prepare the spreadsheet
Use an Excel workbook (.xlsx) or a CSV file, up to 2,000 rows. The first row must be headings. Only Name is required; Vindex also understands common variations of each heading, such as Full name, DOB or Nationality.
Press Template on the page for a workbook with these headings and a sheet explaining each one.
Upload and check
Use it whenyour spreadsheet is ready.
- 1
Open Batch screening in the left bar.
- 2
Drop the file on the page, or press Choose a file (1).
What you will see
Run the screen
- 1
Set how many rows to screen in this run (3). The page says how many LSEG calls that will use. A new batch starts at 10, or at every row if there are fewer.
- 2
Press Start screening. Results appear row by row as they come in.
- 3
To screen the rest later, press Carry on screening: it continues from where the last run stopped.
Careful
A run stops at the first call that fails, rather than carrying on and spending more. Fix the row it stopped on, or leave it, and carry on.
Read and export the results
Each screened row shows its possible matches, how many are on sanctions lists and how many are PEP-linked. Open a row to see its strongest matches.
Vindex keeps the ten strongest matches for each row. The rest are in the World-Check One account, where each screen is saved as a case.
How the allowance is protected
- Nothing is sent to LSEG when a file is uploaded; only when you start a run, for the number of rows you chose.
- A row with no name, or one that repeats an earlier row, is never sent.
- A set number of calls is held back for case work, so a batch can never use up what real cases need.
- A run that asks for more calls than are available is refused, with the arithmetic shown.
Something missing or unclear? Signed-in users can tell us from Feedback in the app.