Accounts payable — dated read before releasing a payment

Template version 2026-10-06 · for: Hospital and health-system AP / treasury; any organization disbursing federal-award funds · owner role: AP Manager (owner); Controller (rule owner); Compliance Officer (oversight) · adopted by  organization  effective  date . Editable .txt · JSON

Template. Written against the public text of the standard cited; the organization adopts, edits and owns it as its protocol. Every threshold, identity, hold or disclosure decision belongs to the organization. We report the findings against the protocol — counts, dates, states — nothing more. Not legal advice, not a compliance determination, not a consumer report.

Standards served

Scope

Payments above $___ (set by the Controller), all payments from federal-award funds, and first payments to any new payee.

Frequency

At the moment of payment-run approval; the read must be dated within  ___  days of release (set here).

Procedure

  1. Write the hold rule here, in words, owned by the Controller: e.g. 'hold for compliance review if any of sam.count, leie.count, ofac.count, state.count, csl.count or uflpa.count rose since the previous read, or if sam or ofac did not answer'. The rule is the organization's; the read is the record of why it fired or did not.
  2. At payment-run approval: for each in-scope payee, obtain a fresh dated read with since=<previous receipt id> so the record carries both the current state and every line that differs from the last read.
  3. Release payments the rule does not stop. For payments the rule stops: route to Compliance with the changed lines; Compliance records the decision (release / hold / escalate) and its basis.
  4. A source that did not answer is printed on the read; the rule above says what AP does with it (hold, or release with the gap recorded). Never treat it as 'no match'.
  5. File each read's id and hash with the payment record so an auditor can reproduce the state at the time of payment.
  6. Quarterly: the Controller reviews the rule and the measures below with the Compliance Officer; a rule change is a notation here.

Findings reported — computed from your own records; the threshold is your protocol's

FindingComputed asData sourceThreshold
In-scope payment coveragepayments in scope with a read dated within ___ days of release ÷ in-scope paymentsAP system; receipt created_at your protocol 
Rule firingspayments stopped by the rule; share released after review; median hours to decisionAP hold log; Compliance decisions your protocol 
Silence at paymentpayments released while a named source did not answer ÷ paymentsreceipt did_not_answer your protocol 
Changed-line review before releasepayments with a changed line where Compliance decision predates release ÷ payments with a changed lineENTITY_STATE_DELTA events; AP timestamps your protocol 
Reproducibilitysampled payments whose receipt hash still verifies and whose proof date precedes the paymentreceipt verify; timestamp proof your protocol 

Records

RecordKept byRetention
Hold rule text and its change notationsControllerindefinite
Read id + hash per in-scope paymentAPper HOSP-08 and finance retention
Compliance decisions on stopped paymentsComplianceper HOSP-08

What this procedure does not decide

Whether to pay. The read states what the files printed and what changed; the hold rule and every release decision are the organization's.

Change log

DateChange
2026-10-06First issue.
 date adopted / edited by  name 

Other templates: 01 · 02 · 03 · 06 · 07 · 08 · 09 · 10 · 01 · Duty Sheets (one page per rule, generated on any receipt) · our own procedures · 2026-10-25