City accounts payable
Claims, payment registers and supporting vendor invoices.
Supporting records pending02 / Public money ledger
Follow the stages.
A request, a contract and a payment can describe the same money. Keep each stage visible; never add them together.
- 01
Requested
An application or request. No approval implied.
- 02
Authorized
A source-supported approval, with its scope and cap.
- 03
Contracted
An executed agreement and its terms.
- 04
Invoiced
A bill or claim. Payment remains a separate question.
- 05
Paid
A supported disbursement, including adjustments.
- 06
Delivered
Documented performance or receipt of the work.
A fixed historical window
September 13, 2016
to September 13, 2026
Acquisition is ordered newest first. Later records and revisions belong to a separate ongoing lane. The date range is the scope, not a claim of completed collection.
Separate books. Separate questions.
MRA assistance
Authorizations, agreements and documented reimbursements.
Supporting records pendingCity TIF & renewal districts
Increment, collections, commitments, balances and debt.
Supporting records pendingCounty funds & districts
County claims, district programs and related transfers.
Supporting records pendingBusiness improvement districts
Assessments and separately documented expenditures.
Supporting records pendingEconomic partnership contracts
Contract terms, invoices and documented delivery.
Supporting records pendingCoverage is still being established
No published financial records to show.
This is a gap in this observatory’s coverage. It does not establish that no activity occurred.
Examine the source directory ↗Before a number becomes a finding
Repeated invoice appearances are not duplicate payments. Credits, split payments, retainage, voids and reissues require reconciliation. Transfers and later expenditure must not be counted twice.
Insufficient coverage means not evaluable. Review queues and unreleased findings are not exposed here.
Read the financial method ↗