2026-008 Software & Implementation Services for Financial ERP & Tax Collector Systems
| Location: | New Hampshire |
|---|---|
| Posted: | Jul 9, 2026 |
| Due: | Aug 19, 2026 |
| Agency: | Town of Salem |
| Type of Government: | State & Local |
| Category: |
|
| Solicitation No: | 2026-008 |
| Publication URL: | To access bid details, please log in. |
| Bid Number: |
2026-008
|
| Bid Title: |
2026-008 Software & Implementation Services for Financial ERP & Tax Collector Systems
|
| Category: | Bids |
| Status: | Open |
|
Attachment Preview
Requests for Proposals
Software and Implementation Services
for Financial Enterprise Resource
Planning (ERP) & Tax Collector
Software Systems Environment
RFP 2026-008
Town of Salem NH
SALEM PURCHASING
Gia Faccadio, Purchasing Agent
Nicole McGee, Finance Director
Joseph R. Devine, Jr., Town Manager
TOWN OF SALEM NH
RFP 2026-008
SOFTWARE AND IMPLEMENTATION SERVICES FOR FINANCIAL
ENTERPRISE RESOURCE PLANNING (ERP) AND TAX COLLECTOR
SOFTWARE SYSTEMS ENVIRONMENT
The Town of Salem NH, is seeking proposals for Software and Implementation Services for a Financial
Enterprise Resource Planning (ERP) and Tax Collector Software Systems Environment in accordance
with the specifications, terms, and conditions listed in RFP 2026-008 which can be obtained at
https://www.salemnh.gov/bids. A non-mandatory pre-proposal teleconference will be held on Thursday, July 16,
2026. All bids must be received by W e d n e s d a y , August 19, 2026, at 1 0 : 0 0 A M
EST. Late proposals will not be considered. Six (6) h a r d copies and one (1) electronic copy
(USB drive) of the bid package must be submitted in a sealed envelope, plainly marked:
Town of Salem NH
ATTN: Purchasing Division
RFP 2026-008
ERP & Tax Software
Systems Environment
33 Geremonty Drive
Salem, NH 03079
All questions concerning the RFP must be submitted via email only, to the Town’s consulting partner,
BerryDunn (Kate Offerdahl-Joyce – kate.offerdahl-joyce@berrydunn.com).
The Town reserves the right to reject any or all bids or any part thereof, to waive any informality in the
bidding, and to accept the bid considered to be in the best interest of the Town. The Town also reserves
the right to conduct reasonable negotiations with low bidders and sole bidders. Failure to submit all
information may disqualify a bid.
Table 1: Proposal Naming and File Formats
Proposal Section
Technical Proposal
(Inclusive of Attachments A, B and any
Exhibits/Attachments: Signatory
Declaration, Non-Collusion Statement,
Indemnification Agreement, No Bid
Questionnaire, W9:)
Attachment B – Functional and
Technical Requirements
Price Proposal
Attachment C – Cost Worksheets
Recommended File
Naming Convention
Required File Format
“(Proposer Name)”
Technical Proposal
All files combined into one (1)
searchable Adobe PDF
“(Proposer Name) Proposal
Response to Attachment B”
“(Proposer Name) Proposal
Response to Attachment C”
To be submitted in Microsoft
Excel format, in addition to above
PDF format
To be submitted in Microsoft
Excel format, in addition to above
PDF format
Amendment of Proposals: Proposers may amend Proposals prior to the deadline set for receipt of
Proposals. In the event an Addenda is issued and a Proposer has previously submitted a Proposal in
response to this RFP, the Proposer shall notify the Town via email of the need to submit an amendment
and clearly outline the reasons in writing. No amendments will be accepted after the deadline unless
they are in response to a request of the Town.
Confidential Information: Proposers shall clearly mark any information or graphics that are considered
to be confidential as such within Proposal submissions. Any such designation as confidential shall be
specific as to the portions of the proposal deemed confidential by the vendor, and not the entire Proposal
response.
Proposers are instructed to insert the completed Tab forms (Attachment A – Proposal Response Forms)
in the corresponding Tab sections as a part of their response to the Technical Proposal. The Town
expects that Proposers will include additional proposal content beyond simply completing the forms and
worksheets provided through this RFP. The following table contains the organization guidelines for
Proposal responses.
Table 2: Technical Proposal Organization Guidelines
Proposal Tab No.
Tab 1
Tab 2
Tab 3
Tab 4
Tab 5
Tab 6
Tab 7
Tab 8
Tab 9
Technical Proposal Section
Company Introduction and Relevant Experience
Software Solution, Data Conversion, Architecture, Security, and
Hosting
Implementation Methodology, Key Personnel, Training Plan, and
Testing and Quality Assurance Plan
Project Schedule
References
Cost Narrative
Sample Contracts and Warranty
Exceptions to Project Scope and Contract Terms
Please insert the response to Attachment B, Functional and
Technical Requirements, following Attachment A in the electronic
submittals as a consolidated PDF Technical Proposal.
Content for Tabs 1 – 8
1. Tabs 1 – 8
i. Attachment A – Proposal Response Forms is a Word document that provides detailed
instructions and requirements for the Proposer as it relates to the documents to be
submitted as their RFP response and Services required for the Project. Proposers are
instructed to organize Proposals in a tabbed format and to insert the completed Tab forms
(Attachment A – Proposal Response Forms) in the corresponding Tabs as a part of their
response to the Proposal. In addition to the information captured through the questions and
tables in Attachment A, Proposers are requested to provide complementary narrative
information, diagrams, and images to help substantiate and support their proposal response
to each Tab section. Proposers are directed to Attachment A, which includes forms, tables,
and questions, including the cost narrative that are to be completed by the Proposer and
inserted into each applicable tab of the RFP response (Tab 1 – 8).
2. Attachment B: Tab 9
i. Attachment B – Functional and Technical Requirements/Capabilities is an Excel document
that provides detailed requirements and capabilities related to software features and
functions, as well as potential interfaces and data conversion requirements. This tab is to
include Proposer’s response as detailed in Attachment B – Functional and Technical
Requirements/Capabilities, which is an Excel document to be filled out by the Proposer.
Proposers are to provide Attachment B in both Excel format, and also in PDF format
appended to the responses to Attachment A Tabs 1 – 8.
Price Proposal
The completed Cost Worksheets as contained in Attachment C – Cost Worksheets. Proposers shall
not modify the worksheets in any way.
Table 3: RFP SCHEDULE OF EVENTS
Event
RFP Published
Pre-Proposal Vendor Teleconference
Deadline for Questions from Vendors
Deadline for Proposal Submissions
Shortlist Vendors Notified
Vendor Demonstrations
Estimated Date
July 10, 2026
Thursday, July 16, 2026 at 1:00 p.m. ET
July 23, 2026
August 19, 2026 at 10:00 a.m. ET
Week of September 17, 2026
Week of October 19, 2026
SCOPE OF SERVICES
The Town of Salem (Town) is soliciting Proposals from Proposers capable of satisfying the needs
for software and consulting services to implement a new software systems environment to address
the Town’s needs related to Enterprise Resource Planning (ERP). In addition to soliciting written
responses, this document provides information to assist Proposers in preparing their responses and
facilitates the subsequent evaluation and comparison process. In that regard, this RFP:
• Provides information essential to soliciting meaningful recommendations and realistic
commitments from the Proposers
• Specifies the desired format and content of Proposals in response to this RFP
• Outlines the Town’s evaluation and selection procedures
• Establishes a schedule for the preparation and submission of Proposals in response to this
RFP
This RFP and the selected Proposal in response to this RFP will be incorporated into the contract
resulting from this solicitation.
Project Objectives
The overall goal of this project is to take advantage of the newest technology and harness efficiencies
by reviewing business processes and implementing technology to enhance existing business processes
performed by Town departments. The Town is planning to replace its current software systems
environment with a new system or combination of software systems, and to adopt systems
functionality to support core processes. In doing so, the Town seeks to address several challenges in
the current environment, and gain future efficiencies, including, but not limited to:
• Key Objectives and Outcomes:
o Enhance operational effectiveness with an online portal by making more timely, accurate, and
complete information available to citizens, Town personnel, and vendors.
o Transition to end-to-end, system-enabled workflows and document management to replace
manual, paper-based, and offline approval processes, improving efficiency, consistency, and
audit transparency.
o Establish a unified ERP environment that supports single-point data entry and real-time data
exchange across functional areas, reducing duplicate data entry and reliance on batch
processing.
o Provide role-based dashboards, configurable reporting, and real-time access to financial,
operational, and workforce data to enable improved transparency, accountability, and data-
driven decision-making.
• Primary Challenges in the Current Environment
o Business processes rely heavily on manual, paper-based workflows, spreadsheets, and offline
approvals, resulting in inefficiencies, delays, and limited audit visibility.
o Systems are fragmented and lack integration, requiring manual data transfers, repeated data
entry, and increasing the risk of inconsistent or delayed information.
o Critical operations depend on individual staff knowledge rather than standardized, system-
enforced rules, creating operational risk and limiting scalability.
o Departments have limited access to timely and actionable financial and operational
information, delaying decision-making and increasing reliance on centralized support.
o The current Chart of Accounts and financial structure do not support flexible reporting or
project and grant tracking, requiring reliance on spreadsheets and resulting in delayed visibility.
o The legacy ERP system and decentralized governance model limit modernization, scalability,
and long-term system sustainability.
o The current solution experiences performance and reporting delays, with some routine reports
requiring substantial processing time to generate.
Definitions
This is the opportunity summary page. It provides an overview of this opportunity and a preview of the attached documentation.
Daily notification on new contract opportunities
With GovernmentContracts, you can:
- Find more opportunities and win more business
- Receive daily alerts for all new bid opportunities
- Get contract opportunities matched to your business
* Disclaimer: Information regarding bids, requests for proposals (RFPs), or requests for qualifications (RFQs) is provided on this website only for convenience and does not constitute official public notice. Persons wishing to respond to or inquire about bids, RFPs, or RFQs should contact the appropriate government department.