For bank and credit-union third-party risk teams

Third-Party Ongoing-Monitoring Receipt

OCC 2023-17 / FDIC FIL-29-2023 / FRB SR 23-4 expect ongoing monitoring of each third party through the life of the relationship, documented so an examiner can see what was checked and when. This receipt is the dated read: the public record for the exact legal name, re-read monthly by roster with the line-by-line changes, and nothing decided on your behalf.

For banks, savings associations, credit unions, their vendor-management and TPRM teams, and the examiners who read the file. Keys accepted: UEI · EIN · CIK. Matching is exact key or exact printed name; nothing is inferred, scored or labelled.

What is on the receipt

SAM.gov exclusions, OFAC SDN and the trade.gov Consolidated Screening List with file dates and SHA-256
CFPB Consumer Complaint Database — complaints where the company field equals the exact name; companies whose CFPB name contains the words are listed as candidates, not counted
SEC EDGAR registrant and filings by CIK
Federal Audit Clearinghouse, EPA ECHO, HHS OCR breach portal and IRS rows as printed
Monthly roster re-read with the diff since last month, and a re-read the hour an official file changes
Not read, by design: FinCEN beneficial-ownership data (not public), credit-bureau or rating data, anything inferred from a name

Priced per proof event

Roster 150: $3,600 a year, up to 150 names re-read monthly — $2.00 per receipt at a full list; Roster 500: $9,999 a year. Net 30 on invoice or purchase order, W-9 on request.

Partner API: Basic $99/month for 5,000 single receipts (2¢ each beyond), Monitor $499/month for 50,000 with pasted lists and watchlists (1¢ beyond). Terms on /partners.

No seats, no per-user licences. A single free receipt is always available at /screening.

See one

A live sample receipt for this sector, re-run against today's files:

Open the sample receipt

Every receipt conforms to Receipt Format v1 and is issued under the Verification Integrity Standard. Start a pilot at /pilot.

Citing a receipt as audit evidence

Request the receipt with your award, PIID or invoice reference (ref=); the reference is bound into the SHA-256 and printed, never interpreted.
File the JSON and the print page. The citation line on the receipt names the registry id, read time and hash.
An auditor re-runs the same name and keys at /screening or checks the held copy at /r/<id>; the registry confirms the hash without any login.
Where a source is listed as not read, the receipt says so; the auditor's workpaper should treat that source as unchecked, not as clear.