Lists updated daily

What an examiner asks for, and which of it we give you

An examination is a request for evidence. Someone asks you to show that a screening happened, when, over what, and what you did about the result. Most of the answer has to come out of your tooling, and the parts that do not have to come out of your own files.

This page is a field-by-field account of what OFACScreen records and what it does not, so that you can decide in advance where the gaps are rather than discovering them during a review. Every line is checkable against the product. Where we do not capture something, it says so in the same voice as the things we do.

What gets written when a search runs

A search from a signed-in account writes a row to the audit trail. That row holds:

  • The timestamp, to the second, of when the search ran.
  • The name searched, exactly as it was typed.
  • Who ran it, the user account it came from. On a team account, a member's searches are written into the owner's audit trail with the member identified.
  • How the search was run: single search, batch upload, API call, or automated monitoring.
  • How many results came back, and whether it matched at all.
  • The IP address the search came from, for searches run from the dashboard and for batch uploads. API calls and monitoring re-screens are recorded without one.
  • How the search was set: the minimum score it ran at, and any country or list narrowing the person searching chose (an API search can also name an entry type). Monitoring re-screens, and rows written before this was recorded, do not carry it.

One row is not always one name

This is the detail most likely to catch you out in front of a reviewer, so it gets its own section.

  • A search from the dashboard writes one row carrying that name, its result count, and whether it matched.
  • A single API call does the same, under the API search type.
  • A daily monitoring re-screen writes one row per monitored name, with that name, its result count and whether it matched, and the lists it was checked against when the account ticked opt-in lists for monitoring.
  • A batch CSV upload writes one row for the whole file. The name on that row is the file, recorded as "Batch:" followed by your original filename, and the row is charged for the number of names in the file. The individual names, their matches and their scores are not in the audit trail; they live on the batch results page and in that run's own CSV export. The batch's API equivalent behaves the same way, recording the call as a batch of a stated number of entities.

So the audit trail proves that a file of 400 names was screened on a given day by a given user. It does not, by itself, prove which 400 names those were. If you need the names in the record, keep the batch results export.

Ready when someone asks for proof

Every check is saved with the date, the name and who ran it. Download it as a spreadsheet any time.

Start free trial

What is not recorded

These are the things people assume are in an audit log and are not in ours. Read this section twice if you are about to put us in front of a regulator.

  • Which lists were live for a given search. A search runs against the 14 core lists, unless the person searching chose others, and a narrowed search records the lists it was limited to. A row that says "core lists" does not name them, and cannot be used to prove which lists were live on a particular day. If your procedure needs the scope evidenced per search, the $9.99 report prints the lists by name for the screening it covers.
  • The matches themselves. The log records how many results came back and whether anything matched. It does not store the matched names, their scores, or the lists they came from. If you need those preserved for a specific screening, buy the report for that screening, or export the batch results, both of which do carry them.
  • The threshold a monitoring re-screen ran at. Monitoring rows do not record their cut-off, which is always 0.4. How OFACScreen Matches Names documents the values, and that page is the substantiation for them.
  • The publication version of each list. The audit log does not record which version of each list was live when a search ran. The report prints each list's name, the date its publisher put on the data where the publisher gives one, and when we fetched our copy. It does not print version numbers, and some lists, the SDN List among them, reach us with no publisher's date at all. If your procedure requires the list version to be pinned per screening, you have to record it yourself.
  • The free public search. Searches run on the free search page are recorded anonymously and are not part of any account's audit trail, on purpose. They spend no allowance and belong to no account. If a screening needs to be in your record, run it from your account or buy the report.

The audit trail export

The audit trail exports as CSV, with an optional date range, and that file is the artifact you hand over. Every plan carries it, including the 14-day trial, so you can see the export before you pay for anything. The columns are:

  • Date, formatted to the second.
  • User, but only on a team account. Where nobody else has been invited, the export has no User column at all, because there is only one person it could be. If your examiner expects to see attribution in the file itself, know this before you send it.
  • Query, the name searched.
  • Type, the search type in readable form.
  • Results, the number of results.
  • Match Found, Yes or No.
  • IP Address.
  • Settings, how the search was set, for example "Min. score 40%; core lists". Empty where the row does not record it.
  • Review Decision, Listed Entry and Review Note, filled only on review rows (see below).

There is no score column in this export, for the reason given above.

Match Review Decisions

Every possible match, from a single search, a batch row or a monitored name, starts as to review. Someone on the account can clear it as a false positive or confirm it, and either way has to write a short reason. Each decision is written to the audit trail as its own row, dated to the second, with who took it, the name screened, the listed entry it is about, the outcome and the reason. A changed decision is a new row; the old one stays.

A decision covers that name against that listed entry, wherever the name is screened on the account. A cleared match does not alert again on the daily monitoring re-check, unless the listed entry itself changes (its name, aliases, program, remarks, locations or identifiers). Then it alerts again and is put back to review, and that reopening is written to the audit trail too.

The batch results export

A completed batch run downloads as its own CSV, and this one does carry match detail, one row per screened name:

  • Name and Entity Type as submitted.
  • Match Found, Yes or No.
  • Top Match, the name of the single highest-scoring match.
  • Score, as a percentage.
  • List, which sanctions list that top match sits on.
  • Match Type, the confidence band.
  • Review Status, to review, cleared or confirmed, for a name that matched.
  • Review Notes, each decision on that name's matches, with who took it, when, and why.
  • Address as submitted, only when you screened an address column.
  • Matched Address, the closest listed address the row's address matched and whose it is, or why the address was not searched.
  • Jurisdiction Flag, an embargoed or high-risk place the row's country or address points to. A flag is not a match and does not change Match Found.
  • Email, Phone and Website as submitted, only when you screened those columns.
  • Matched Identifier, the listed email address, phone number, website or ID number the row matched and whose it is, or why a contact detail was not searched.
  • Other Names, each name screened from another column of the row, such as a director, with its column, only when you screened those columns.
  • Matched Other Name, each of those names that found a listed party, its column, and the closest party it found.

Note the word top. This export carries the best match per submitted name, not every match. A name that hit six entries exports one row showing the strongest of them. The full result set for that run stays visible on the batch results page.

The CSV file you uploaded is deleted 30 days after upload. The results and the audit-trail rows survive that deletion; it is your list of counterparty names that goes, which is usually what you want. Download anything you still need inside that window.

The $9.99 report

The report is the artifact built for handing to somebody else. For one screening it prints:

  • A report ID and the generation timestamp in UTC.
  • The name screened and the screening date.
  • The count of active lists checked, and every one of them listed by name at the foot of the report.
  • The minimum match score used.
  • For each list, the date its publisher put on the data where the publisher gives one, and when we fetched it.
  • The number of matches found.
  • Your company name, if you entered one at checkout.
  • Every match, with its score, confidence band, entry type, the list it appears on, its sanctions program, and any aliases, known locations, identification numbers and remarks the source list publishes. Longer result sets show the highest-confidence matches in full and the remainder in a table that still carries each match's own name, list and score.
  • When nothing matched, the same document is issued as a no-match screening record.
  • A permanent link on this domain showing the same document, so the recipient does not have to trust a PDF you emailed them.

It does not carry list version numbers, and it is not a legal opinion. There is a real sample report you can read in full before buying one.

What stays your job

Treasury's Framework for OFAC Compliance Commitments describes five components of a sanctions compliance programme: management commitment, risk assessment, internal controls, testing and auditing, and training. A screening tool is part of one of them. The rest is yours to run:

  • A written policy. Who gets screened, at what points in the relationship, against what, who reviews a hit, who can clear one, and who is told when something is blocked. An examiner will ask for the document before asking for the logs.
  • A risk assessment. A documented view of your own exposure by customer base, product, geography and transaction type, and the reasoning that led from it to the screening you actually do.
  • Testing and independent audit. Evidence that somebody checked the controls work in practice. Our logs can be an input to that test; they are not the test.
  • Training records. Who was trained, on what, and when. On Professional and above, staff can take sanctions training here, and each pass is kept with its date, score and certificate. Deciding who must be trained is still yours.
  • Your case files. The decision on each potential match, the reasoning, and the supporting comparison of date of birth, location and identifiers. The decision and a short reason can be recorded on each match here, and land in the audit trail. The supporting comparison itself, the documents and the identifiers you checked, belongs in your own file.
  • Blocking and reporting. If a screening produces a genuine hit, the obligations that follow, blocking, rejecting, and the reports OFAC requires, are yours. See How to Handle an OFAC Match.

How to check all of this

Do not take the list above on trust. On a trial account, which needs no card:

  1. Run a search, then open the audit trail and export it. Read the header row and count the columns.
  2. Run a two-row batch file and download the results CSV. Compare it against the results page and see what the export keeps and what it drops.
  3. Read the sample report, or buy one for a name of your own, and check it against the section above field by field.

If you are evaluating us alongside another tool, ask the other vendor for the same field-level list, and be suspicious of an answer that has no "we do not record this" section in it.

Related reading

Check a name now

Free, and no account needed.

14 lists at once 50,000+ names on them Updated daily from the official sources

Try it free for 14 days.

No credit card needed. Cancel any time.