Read profiles · three workflows, one receipt

Which keys to send, which duty it sits beside, which files are read.

A read profile is a shopping list, not a workflow engine: the keys to send, the duty sheet the receipt sits beside, the sources read by exact printed name or key. The decision belongs to the organisation that owes the duty.

Accounts payable — the record at the moment of payment

AP, treasury and procure-to-pay controllers; ERP and payment-platform teams

When: Seconds before a disbursement is released, and on the monthly re-run of the open vendor master.

Keys to send

  • name — the payee name exactly as it appears on the invoice or vendor master — required
  • ein — payee EIN as registered
  • uei — SAM.gov Unique Entity ID, where the payee has one
  • lei / eori / uscc — foreign payees: LEI, EU EORI number, China USCC (read at GLEIF; the Chinese register itself is not read)

Duty sheet it sits beside

What to call

  • POST /api/ap/check — one view per payee under your partner key — per source: answered / did not answer / not read, exact rows, similar names shown (never counted), SHA-256; decision: null
  • POST /api/ap/verify — anyone can replay the hash on a stored view
  • POST /api/batch — the whole vendor master as CSV; one receipt per row; monthly re-run with a line-by-line diff

Reference: /ap/contract.html

The decision is yours. Whether to pay, hold or ask a question is your payment rule, written in your ERP. The view gives your rule dated, cited facts to run on. It never prints approve, hold or clear.

Federal prime contractors and grantees — the covered-transaction record

Prime contractors flowing FAR 52.209-6 and Section 889 down to subcontractors; grantees and pass-through entities under 2 CFR 200.214 / 180.300; the auditors who test them

When: Before any subcontract over the FAR 52.209-6 threshold, before each covered transaction under a federal award, and at the Single Audit.

Keys to send

  • name — the legal business name as registered in SAM — required
  • uei — SAM.gov Unique Entity ID
  • cage — CAGE code
  • ein — EIN, for the FAC single-audit filings

Duty sheet it sits beside

What to call

  • GET /api/public-record/screening?name=…&uei=…&cage=… — the free receipt — same content as the paid one; printed-name rows on every list, SAM parents' names beside the registration
  • POST /api/batch — the subcontractor roster as CSV, one dated receipt per row, coverage table and results CSV for the audit file
  • GET /api/receipts/{id}/vc — the receipt as a W3C Verifiable Credential, Ed25519-signed; it attests to our reading, not to the subcontractor

Reference: /forms

The decision is yours. Responsibility, eligibility and award are the contracting officer's and the prime's determinations. The receipt records what SAM and the lists printed on the date you had to look.

Health systems, plans and credentialing — the exclusion record, monthly

Hospitals and health systems, Medicaid managed-care organisations, MA/Part D sponsors and their FDRs, CVOs and credentialing committees

When: At hire, at credentialing and re-credentialing, and monthly for every employee, medical-staff member and vendor billed to a federal health care program.

Keys to send

  • name — the individual or entity name exactly as enrolled — required
  • npi — NPI, for the CMS rows (Open Payments, Medicare utilization)
  • ein — EIN for entities
  • ccn — CMS Certification Number for facilities
  • state — the state whose Medicaid list to read first

Duty sheet it sits beside

What to call

  • POST /api/batch — the monthly roster as CSV; one receipt per row; the next month's run prints only what changed, line by line
  • POST /api/ap/check — a vendor at the moment of payment
  • GET /exclusion-settlements — what employing one excluded person has cost, as OIG printed it

Reference: /receipts/for/hospitals

The decision is yours. Whether a printed row is your person is your credentialing committee's finding. Exact-name rows do not prove identity; similar names are shown, never counted; a state list that did not answer is printed as did not answer, never as clear.

Never printed, in any profile

  • a score, rating, rank or pass/fail
  • approve, hold, clear or release
  • an identity match or affiliation conclusion
  • 'no record' when a source did not answer
  • a statement that a duty was met or a rule complied with

Other duties — banks' third-party monitoring, counsel diligence, SIG questionnaires, NERC CIP-013 — are on the forms register. JSON: /api/public-record/read-profiles

No tracking cookies; we count visits ourselves, in aggregate. Policy.