How we verify Oklahoma data
Every number on our Oklahoma pages comes from Oklahoma OpenBooks (data.ok.gov), the state's own transparency portal. This page is the standing verification report: what we hold, the quality gates every load must pass, and the reconciliation math against the state's own published totals, including the part that doesn't match.
The chain of custody
Each record travels the same six steps, and every step leaves evidence:
- The state records a payment in its accounting system.
- The state publishes it in bulk on Oklahoma OpenBooks (data.ok.gov).
- We fetch the official bulk file; every fetch is logged with a timestamp, and failures are recorded too.
- The state's row is archived exactly as received and fingerprinted. The archive is append-only: records are never edited or deleted, even when the state overwrites its own history.
- Names are normalized with deterministic rules (see methodology); the original name is kept alongside, and quality gates run on every load.
- Pages are published from a versioned release; the version appears at the foot of every page.
Quality gates
A Oklahoma release does not go live unless all four gates pass. Current status:
| Gate | Result |
|---|---|
| Extraction integrity | Published payment facts re-derived from the raw archive match to the penny across 18.8 million payments, fiscal years 2008 through 2026. |
| No orphan payments | Every payment resolves to a vendor and an agency record. Zero orphans. |
| Duplicate rate | 0.0000% duplicates on the natural-key fingerprint. |
| Portal reconciliation | Month-grain totals match the state's portal exactly, to the row and to the penny, for mutually covered periods (details below). |
The reconciliation math, December 2024
Oklahoma is reconciled at month grain rather than by fiscal year, because coverage gaps run in both directions: the state's portal no longer displays some years we hold, and the state's recent monthly files are structurally partial. December 2024 is a month both sides hold in full, so it is where the comparison is exact.
Here is the comparison against the state's own published figures, to the cent:
| Oklahoma Checkbook, Vendor Transactions report, December 2024 by effective date (captured Jul 9, 2026) | $359,553,421.83 |
| SpendLedger December 2024 payment sum | $359,553,421.83 |
| Difference: 0.000%, within the documented 0.5% tolerance | PASS |
No adjustment was needed: 8,768 payment rows on the portal, 8,768 in our archive, identical dollars to the penny. Where Oklahoma's portal and our archive hold the same period, they agree exactly. A fiscal-year-level tripwire is also stored so that any future coverage regression in the state's files fails our gates loudly.
Known limitations
- Fiscal years 2008 through 2022 come from the state's archived annual files and are complete. From fiscal year 2023 onward the state publishes partial monthly files, so recent years understate total state spending until the state's own publication catches up.
- Oklahoma's public portal currently displays only fiscal years 2010 through 2012 and 2021 onward. Our archive preserves eight fiscal years the portal no longer shows, and at least one month (January 2024) where the portal displays a fraction of what the state's data files contain.
- Payees the state masks as protected information stay masked here: about 5.3 million payments totaling $36.1 billion carry no payee name. Their dollars remain in agency totals.
- Batch pseudo-payees (unclaimed property, refund batches, student refunds) are suppressed from vendor listings; they are accounting constructs, not vendors.
- Coverage is payments processed through the state's central accounting system as published on data.ok.gov; some agency spending happens outside that system.
- Vouchers the state later cancelled are excluded (1 to 3% of rows in fiscal years 2008 through 2019).
Check us yourself
Beyond the automated gates, we verify month-level totals and random individual payments against the state's own Vendor Transactions report; the query links above reproduce our filters exactly on the state's site. A single mismatch is treated as a stop-the-line event for the source. You can do the same: pick any payment on this site and look it up on the state's own portal by vendor name and date. If the portal disagrees with us, we want to know.
Machine-readable version of this report: /trust/ok/provenance.json. Report content last reviewed Jul 11, 2026.