AmericaA usable receipt should connect the award identifier, recipient, payment record, promised deliverable, and evidence of delivery. A spending total alone cannot tell the public whether a program achieved its purpose.
What the evidence establishes
USAspending’s analyst guide distinguishes obligations—commitments that require payment—from outlays, the payments themselves. Award and account data have different scopes. Its data-quality guidance is part of the record, not an optional footnote.
USAspending — Analyst’s Guide to Federal Spending Data ↗
The source defines spending data. It does not establish that this proposed receipt format saves money, that every payment is visible at award level, or that an unusual recipient has committed fraud.
How it could work
Start with one completed contract or grant and retain its official identifier. Link the award rather than copying a number that will become stale. Label the amount as an obligation, outlay, ceiling, or other specific measure. Never add unlike amounts into one supposed spending total.
Add a separate delivery record: the expected result, the accountable office, the due date, the acceptance evidence, and the date you checked. A missing deliverable link becomes “not verified,” not “not delivered.” Preserve subsequent corrections and a right of response.
Tradeoffs & safeguards
A public receipt requires staff time, stable identifiers, and quality checks. Privacy, procurement sensitivity, and protected information can limit what is published. A large file dump is not the same as usable transparency.
Outputs and outcomes differ. A contractor can deliver a functioning portal without improving participation. Conversely, a useful service may have benefits that are difficult to attribute. Show the chosen measure and its limitations rather than inventing a return-on-investment score.
A pilot you could actually evaluate
Proposed pilot: independently document five completed awards from one agency and reporting period. Have a second reader reproduce the amount and delivery status using only the linked sources. Publish disagreements before expanding coverage.
Suggested measures—not reported results
- Receipts reproducible from original records / receipts reviewed
- Time required to locate a deliverable and identify its owner
- Unresolved discrepancies, source gaps, and correction turnaround
Build an evaluation brief
Optional. Keep the unknowns visible. This is saved nowhere automatically and is not submitted to America.co or government.
Questions worth asking
Does a large award prove waste?
No. Size is not an evaluation of necessity, delivery, value, or legality. Read the award scope and compare like measures.
Can this automatically identify fraud?
No. It supports checking and asking better questions. A discrepancy is a review lead, not a legal finding.
Go to the original sources
- USAspending — Analyst’s Guide to Federal Spending Data ↗Official data definitions and limitations; consulted October 4, 2026
AI-assisted synthesis and original evaluation questions, with linked source checks. No independent expert review, legal conclusion, funding commitment, or proven pilot outcome is claimed. People, methods, and corrections.