Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transparency topic
No spam. Unsubscribe anytime.
Kyle council votes 4–3 to post city purchase‑card receipts after debate over staff cost and public transparency
Summary
After a lengthy staff briefing and more than an hour of debate, Kyle City Council voted 4–3 to post purchase‑card transactions and receipts online (with redactions). Staff estimated redaction costs and time; critics said posting raw receipts would invite misinterpretation.
Get email alerts on the Transparency topic
No spam. Unsubscribe anytime.
Kyle City Council voted 4–3 on Tuesday to post purchase‑card transactions and supporting receipts online, a decision council members said was aimed at increasing transparency but that staff warned would require substantial redaction work and ongoing staff time.
The council action followed a detailed presentation by finance staff who described the city’s purchase‑card program: 93 active cards, about $2.7 million in card spend for fiscal 2025, and roughly 5,170 card transactions last year. Staff warned that posting receipts would require redacting card numbers and possibly personal information, and estimated the extra workload at 70–95 hours per month and an annual cost in the $25,000–$55,000 range, depending on how the city managed the process.
Why it mattered: Advocates for posting receipts said residents deserve access to line‑level spending and that open access prevents fraud or unchecked spending. Opponents said publishing raw receipts without context would invite misinterpretation and make public servants’ routine operational purchases subject to misleading scrutiny; several council members urged the city to expand dashboard and transparency tools instead of a blanket receipts dump.
Council action: Councilmember Goza moved to approve the policy to post receipts as presented and the motion passed 4–3 after a roll call. Council also asked staff to clarify redaction timing and communications to manage public inquiries about individual transactions; staff noted posted records would be about two months behind due to closing and redaction.
Staff alternatives discussed: City staff offered three lower‑impact options for council consideration — department‑level summary reporting, transaction‑level statements without receipts, or using the existing monthly financial reports and dashboards to present more context to the public. Several council members and staff said these alternatives could provide meaningful transparency with less staff burden.
What happens next: Staff will proceed to implement the approved posting policy and said the initial publication will be delayed two months to allow for transaction closeout and redaction. The council also directed staff to present clearer audit and risk‑assessment information in March, which may inform future transparency refinements.

