Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Financial Systems Replacement topic
No spam. Unsubscribe anytime.
Finance committee backs funding request to replace Needhams aging financial system
Summary
Needhams Finance Committee recommended Article 11 on April 9, supporting a phased replacement of the towns 2014 enterprise financial system after presenters described recurring billing errors, heavy manual reconciliation and compatibility problems with payment processors.
Get email alerts on the Financial Systems Replacement topic
No spam. Unsubscribe anytime.
Needhams Finance Committee recommended adoption of Article 11 on April 9, approving a funding request to replace the towns existing financial system and its disconnected third-party billing tools.
Presenters told the committee the towns current system, implemented in 2014, relies on multiple third-party applications for tax and utility billing that are separate from the general ledger, creating time-consuming data imports, reconciliation and customer-account errors. "We simply have outgrown the system," a Finance Department presenter said during the presentation.
The proposal calls for a phased implementation of a single, integrated enterprise resource planning (ERP) platform. The town plans to replace the tax and utility billing components and the general ledger first, then convert human resources and payroll and other modules. Presenters said the initial conversion and implementation costs are estimated in the project materials at about $1.9 million (one-time conversion and implementation expenses) with recurring licensing and hosting costs estimated at roughly $700,000 per year; the town has identified a $100,000 state Community Compact Cabinet grant and about $500,000 available in current town and school budgets to offset recurring costs, with the balance to be requested at Town Meeting.
Finance staff and the procurement office said the replacement will be procured through a request-for-proposals (RFP) process so the town can evaluate systems on factors beyond price. "The advantage of a request for proposals is we are not required to take the lowest bidder," Dave, the towns chief procurement officer, told the committee. He described planned vendor demonstrations and site visits with current customers as part of the vetting process.
Committee members asked whether the cloud-hosted system would reduce town IT staffing or server maintenance. Presenters said cloud licensing typically raises recurring fees but that existing IT staff would continue to manage the implementation; presenters do not anticipate adding new permanent IT positions for system hosting. They also said recent state grant funding and existing budget lines used to support the current system would be reallocated toward the new systems recurring costs.
The committee voted to recommend adoption of Article 11. Next steps described by staff include issuing an RFP, scoring vendor demonstrations, negotiating terms that include minimum support and service expectations, and starting a phased conversion expected to begin with billing and the general ledger. Presenters said the earliest full resident-facing experience (payments, resident portal) would likely appear during calendar 2026 with broader conversion activity into 2027 depending on procurement and vendor selection.

