Committee asks staff to reconcile energy credits and reporting after software import errors

Olean Budget Committee · February 27, 2026

Summary

Members directed staff to reconcile BQ/EQ energy credits shown as revenue and expense across legacy and OpenGov reports, to supply carried‑over credit amounts, and to clean up inconsistent line‑item imports from Encode into the new budgeting software.

Members raised concerns that energy credits and other account transfers were inconsistently coded during the migration to the new budgeting software, creating inflated or mismatched expense lines.

A presenter noted that BQ/EQ energy credits were entered this year as revenue to offset Light & Power costs, but that legacy budgets and the new OpenGov reports showed inconsistent treatment. "When you look at the revenue line, I believe it was, like, 470,000. So it will offset that number," a staff member said, and the committee asked staff to break out what credits were carried over and what amounts are expected for the coming year.

Staff also acknowledged that some Encode account descriptions did not map cleanly into OpenGov, producing odd duplicates (for example, a traffic‑signals line that showed $200,000 in one view and $20,000 in another because of an extra zero). The committee asked for corrected, annotated pages that show both the legacy and new line descriptions so members can verify totals before votes.

AI generated

The text on this page is AI generated. Summaries, highlights, analysis, and video transcripts are all produced from the original source material.

AI can make mistakes, so if you spot one, and we will fix it for everyone.

Note: the source content is unaltered by us. Any content source we link to, be it a video, an audio recording, or a document, is presented exactly as its publisher released it. That publisher is usually a government body, sometimes an individual official or another organisation.

Source