ERP

What to Do When Your Government ERP Vendor Isn’t Delivering

Chris Rodney 18 min read
On this page
  1. First, confirm your ERP vendor is the one not delivering
  2. Build a performance file against the contract and SOW
  3. The escalation ladder for an underperforming ERP vendor
  4. Use the contract levers you already have
  5. How to write a vendor performance letter or cure notice
  6. What a corrective action plan should include
  7. Who to bring in, and when
  8. Exit options: termination for cause, for convenience, or a negotiated exit
  9. Common mistakes that weaken your position
  10. FAQs
  11. Final Words

When your ERP vendor isn’t delivering, treat it as a contract problem first. Document missed obligations against the contract and statement of work, escalate in writing up the vendor’s management chain, use the levers already in the contract (acceptance, payment holds, key personnel, cure notices), and bring in your attorney and procurement lead before anyone mentions termination.

In our experience, agencies tend to start this process months later than they should. Below is a working playbook for finance directors, CIOs, and project sponsors in cities, counties, school districts, and special districts whose integrator is missing dates, rotating staff, letting tickets sit, or delivering work that fails testing.

First, confirm your ERP vendor is the one not delivering

Before you escalate, check that your agency has done what the contract asked of it. If your team missed design decisions, held back subject matter experts, or delivered dirty conversion files, the vendor will say so, and it may be partly right.

Recent public cases show how often responsibility is shared. In Detroit’s WXYZ investigation of Wayne County’s ERP project, the county said its implementer lacked the right experience, while the vendor pointed to county staffing gaps and leadership turnover. In Maryland, state auditors reported that the procurement office chose not to pursue funds for deficient deliverables partly because it “believed the State was partially responsible” for the failure (Maryland Office of Legislative Audits, December 2025).

Run a quick self-check before the first escalation meeting:

  • Were all government decisions in the RAID or decision log made by their due dates?
  • Did your named subject matter experts attend the sessions they were scheduled for?
  • Were conversion extracts, test scripts, and sign-offs delivered on time?
  • Did you change scope or priorities without a change order?

Write down any gaps honestly. Fix them in parallel, so the vendor cannot use them to explain away its own misses.

At a glance
  1. Start by confirming your own side has met its obligations (decisions, staff time, data), because the vendor will raise it.
  2. Build a dated performance file that ties every complaint to a contract clause, SOW deliverable or acceptance criterion.
  3. Escalate in order: vendor project manager, account executive or delivery director, vendor executive sponsor, then a formal written notice.
  4. Stop paying for deliverables that have not passed acceptance, and enforce key personnel and liquidated damages clauses where your contract has them.
  5. Involve your city or county attorney and procurement before sending a cure notice, and brief council before the issue reaches the newspaper.
  6. Termination for cause, termination for convenience and a negotiated exit each carry different costs and risks. Pick deliberately.

Build a performance file against the contract and SOW

An underperforming ERP vendor is easiest to manage when every complaint maps to a specific obligation. “The team isn’t good” goes nowhere. “Deliverable 4.3 (payroll configuration workbook) was due March 14 under SOW section 4, was submitted April 2, and failed 11 of 40 acceptance test scripts” gets a response.

Pull these documents into one folder: the signed contract and all amendments, the SOW and any task orders, the vendor’s RFP response (its promises often become contract obligations by reference), the approved project plan and baseline schedule, the deliverable acceptance log, the change order log, and every invoice with its supporting detail.

Then track the evidence below. Start today, even if you hope never to use it.

Swipe to see all columns →

What to document Where it comes from Owner on your side How often
Missed milestones and deliverable dates Baseline schedule vs. actual Agency project manager Weekly
Deliverables rejected or accepted with exceptions Acceptance log, test results Functional leads Per deliverable
Key personnel changes and vacancies Vendor org chart vs. contract roster Agency project manager As they occur
Ticket and defect aging Issue tracker, vendor support portal Functional leads, IT Weekly
Invoices vs. accepted work Invoices, acceptance forms Finance or AP lead Each invoice
Unanswered requests and escalations Email, meeting minutes Project sponsor Ongoing
Change orders requested by the vendor Change log Contract administrator Each request

Keep the tone factual in every record. Public records laws vary by state, but in our experience you should assume that project emails, minutes, and letters could become public, and write them so they would hold up in front of an auditor or a judge.

The escalation ladder for an underperforming ERP vendor

Escalate one rung at a time, in writing, with a deadline at each step. Skipping rungs makes it harder to prove later that the vendor had notice and a fair chance to fix the problem.

Swipe to see all columns →

Rung Who you go to Typical trigger What you ask for Time box
(KCT rule of thumb)
1 Vendor project manager A missed date, a recurring defect, an unresponsive consultant A dated fix and a named owner One to two weeks
2 Account executive or delivery director Rung 1 commitments missed, or a pattern of misses A written recovery plan and staffing changes Two weeks
3 Vendor executive sponsor (VP level or above) Rung 2 plan missed, or schedule or budget at risk Executive commitment, added resources, revised plan Two to four weeks
4 Formal performance letter or cure notice Material breach of contract or SOW Cure within the contract’s cure period, or a corrective action plan Per your contract
5 Suspension, termination or negotiated exit Cure period lapses without cure Exit on terms your attorney approves Per your contract and counsel

A few practical rules make the ladder work.

  • Match level to level. Your project sponsor or city manager should be the one calling the vendor’s executive at rung 3.
  • Confirm every call in a short email the same day, listing what was agreed and by when.
  • Ask the software publisher to join if your integrator is a partner, not the publisher. In our experience, publishers’ partner management teams pay attention when a partner’s project is failing.
  • Set the next escalation date in the meeting where you agree on the fix.

Washoe County School District in Nevada followed a similar sequence. The district told its board that it “voiced concerns” about its implementer’s performance and staffing during the first four months, then suspended work under the contract and brought the vendor on site, and only terminated after the vendor “failed to correct identified deficiencies”.

Use the contract levers you already have

Most ERP contracts give the government more room to act than agencies use. Apply those terms early and in proportion to the problem, so the vendor’s own finance team starts asking why the project is not getting paid.

Withhold payment tied to acceptance

If your contract ties payment to accepted deliverables, do not pay for work that has not passed acceptance. Approving invoices “to keep the relationship good” removes the vendor’s main reason to fix things.

Maryland’s audit of its eMMA procurement system implementation shows the cost of skipping this step. Auditors found the state had paid $32.5 million of a $38.2 million contract, that a July 2022 internal review identified about $740,000 paid for deliverables later found deficient, and that the office “did not document that it had validated that the contract deliverables functioned as intended”.

Before you hold a payment, have your attorney confirm the contract allows it and how the dispute clause works. Withholding without clear contract support can give the vendor its own breach claim.

Retainage and holdbacks

Some ERP services contracts hold back a share of each payment until final acceptance or the end of a stabilization period. If yours does, track the retained balance and do not release it early as a goodwill gesture. If yours does not, add a holdback when you negotiate any amendment or re-baseline.

Liquidated damages

Liquidated damages clauses set a pre-agreed amount the vendor owes for specific delays. They only work if you assess them. The Maryland auditors noted the contract “provided for liquidated damages if certain delivery dates were not met,” yet the office “frequently adjusted the delivery dates rather than assessing liquidated damages”.

Every time you agree to a new date without reserving your rights, you may be weakening your claim. Ask counsel for standard “reservation of rights” language to include whenever you accept a revised schedule.

Key personnel clauses

A key personnel clause names the vendor staff who must stay on your project and usually requires your approval before they are replaced. In our experience, rotating leads is one of the earliest signs of trouble. Washoe’s board presentation lists “AST changed its project team” at the outset as the first reason for changing implementers.

When the vendor proposes a swap, ask for the replacement’s resume, public-sector references, and a transition overlap period at the vendor’s cost. You can reject a candidate who does not meet the qualifications in the contract.

Service levels and suspension of work

Post-go-live support often carries response and resolution targets, sometimes with service credits. Track them monthly and claim the credits. Some contracts also let the government suspend work, which pauses billing while you force a reset, as Washoe did before terminating.

These levers take steady contract administration, which is hard to sustain when your finance team is also running payroll and closing the month. If you need a team to take over vendor governance on your side, KCT’s ERP Recovery & Stabilization service starts with an assessment within two weeks, then holds the integrator to the contract and re-baselines scope, timeline, and commitments. In Little Elm, Texas, a focused assessment led to KCT getting utility billing back on track and addressing the vendor relationship.

How to write a vendor performance letter or cure notice

A cure notice is a formal written notice that the vendor is in breach, identifies the breach, and starts the cure period set by your contract. A performance letter is a softer, earlier version that puts concerns on the record without formally declaring a breach.

Use a performance letter at rung 3 or 4 when you want the record without escalating the legal posture. Use a cure notice when the problem is material and documented, and only after your attorney has reviewed the contract’s notice, cure, and termination clauses.

The sample below is a template to adapt with your attorney. Notice requirements (addressees, delivery method, cure period length) are set by your contract and local rules, which vary by state and agency.

Sample cure notice (template to adapt with counsel)

  • Header: [Agency letterhead], [Date], sent via [delivery method required by the contract].
  • To: [Vendor contract notice address and named officer].
  • Re: Notice of Deficient Performance and Opportunity to Cure, [Contract name and number].
  • Opening: “The [City/County/District] provides this notice under Section [X] of the Agreement dated [date].”
  • Deficiencies: “[Vendor] has failed to perform the following obligations: (1) Deliverable [ID], due [date] under SOW Section [X], has not been delivered; (2) Deliverable [ID] was rejected on [date] for failing acceptance criteria [list]; (3) [Vendor] replaced key personnel [name/role] on [date] without the approval required by Section [X].”
  • Prior notice: “These failures have been raised with [Vendor] on [dates], most recently with [executive name] on [date].”
  • Cure: “Under Section [X], [Vendor] must cure these deficiencies within [cure period] days of receipt of this notice, or, if the Agreement permits, deliver within [number] business days a written corrective action plan acceptable to the [Agency].”
  • Payment: “Until cure, the [Agency] will not accept or pay invoices for affected deliverables, consistent with Section [X].”
  • Reservation of rights: “The [Agency] reserves all rights and remedies under the Agreement and applicable law, including liquidated damages and termination. Nothing in this notice waives any right, and any acceptance of revised dates is subject to this reservation.”
  • Signature and copies: [Signature of authorized official]; cc: [City/County Attorney], [Procurement Director], [Project Sponsor].

Three cautions apply. Use the exact notice address and method in the contract, or the notice may not count. Have the person with contract authority sign it, usually the official who signed the agreement or a delegate. Keep it factual: assume council and your auditors will read it, and possibly a court.

What a corrective action plan should include

A corrective action plan is the vendor’s written commitment to fix specific deficiencies by specific dates. Accept it only if it is specific enough that a missed item would be obvious.

Require these elements:

  1. A root cause statement for each deficiency in the notice, in plain language.
  2. Named vendor staff responsible for each fix, with their availability on your project.
  3. Dated milestones that tie back to SOW deliverables and acceptance criteria.
  4. Any staffing changes, including replacement of key personnel with resumes for your approval.
  5. A statement of who pays for remediation, which should be the vendor when the deficiency is the vendor’s.
  6. Weekly reporting against the plan, reviewed by your project sponsor.
  7. A clear consequence if milestones in the plan are missed, such as moving to the next rung or termination.

Do not let a corrective action plan become a disguised change order. If the vendor’s plan adds scope, hours or fees to fix its own defects, send it back.

Who to bring in, and when

Escalating a vendor in government pulls in people a private company rarely needs, from the city attorney to the council. Bring each one in at the moment shown below so nobody with approval authority hears about the problem last.

Swipe to see all columns →

Who When to involve them What they do
City, county or district attorney Before any formal notice, payment hold or termination discussion Reviews contract clauses, approves notice wording, advises on claims and counterclaims
Procurement or purchasing director When performance issues become a pattern Confirms contract terms, documents vendor performance, advises on replacement procurement rules
Finance director or CFO From the first missed milestone Holds invoices, tracks encumbrances and budget impact, briefs the manager
City or county manager, superintendent Before rung 3 Owns the executive relationship and the council briefing
Internal audit or audit committee When payments, controls or close are at risk Independent view of whether controls and payments are sound
Council or board Before any amendment, major budget impact, suspension or termination Approves contract actions and funding, sets policy direction

When to bring it to council

Brief council when the problem will change the contract, the budget, the go-live date, or the public’s experience (payroll, utility bills, permits). Council usually has to approve any amendment or replacement contract anyway, so an early briefing in a regular update is better than an emergency agenda item.

Hyattsville, Maryland, is a cautionary example. Streetcar Suburbs News reported that the city treasurer told council in January 2026 that a five-year effort with BC Systems must be “abandoned and begun again” after about $524,000 in payments, and that the audit committee liaison said she did not realize the rollout might need council oversight until 2025 (Streetcar Suburbs News, March 2026).

Keep council briefings short and factual: what the contract requires, what has been delivered, what you have done to enforce it, the options, and the cost and schedule effect of each. Pima County, Arizona’s administrator memos to its board are a useful model for tone, including a March 2024 memo that explained a two-month Workday delay and a $216,000 amendment within contingency (Pima County, March 22, 2024).

Exit options: termination for cause, for convenience, or a negotiated exit

When escalation and a corrective action plan fail, you have three main exits, plus the option to keep the software and replace only the integrator. Each has different legal, financial, and schedule risks, and your attorney should lead the choice.

Swipe to see all columns →

Option When it fits Main risks What to line up first
Termination for cause
(default)
Documented material breach, cure period expired, record is strong Vendor disputes the breach and claims wrongful termination; litigation cost and delay Complete performance file, proper notices, counsel’s sign-off
Termination for convenience Record is mixed, or you want out quickly without proving fault You usually pay for work performed and certain wind-down costs per the contract Budget for the settlement, confirm the clause exists
Negotiated or mutual exit Both sides want out and blame is shared Weaker cost recovery; release language may waive claims Clear handover terms, data return, release wording reviewed by counsel
Replace the integrator, keep the software Platform fits, the delivery partner is the problem Licensing tied to the old integrator; rework; new procurement Check who holds the subscription, confirm reusable work products

Separate the software from the services

Find out who holds your software licenses or subscriptions. When Washoe replaced its implementer, the board was asked to approve new Oracle Cloud subscription agreements described as identical to those previously approved through the prior implementer (WCSD, December 2025). If your subscription runs through the integrator, plan for that step.

Know the real cost and schedule effect

Washoe had paid $1,869,558 of an $11.2 million implementation contract when it terminated, approved a $9,954,960 replacement contract with CherryRoad Technologies that includes a possible credit for work that does not need to be redone, and moved its go-live from April 1, 2026 to July 1, 2027 (WCSD, December 2025). The district called its early decision a “quick hook” that limited financial exposure.

Pursue recovery if you have a claim

Maryland terminated its eMMA integrator for cause in June 2025, but auditors found that as of October 2025 the office had not assessed liquidated damages or tried to recover funds, and recommended a review with counsel to identify amounts to recover (Maryland OLA, December 2025). If you have a claim, make a documented decision about pursuing it while the evidence is fresh.

Protect knowledge and data on the way out

Before any exit, secure configuration workbooks, design documents, conversion programs and mappings, test results, integration specifications and admin access to every environment. Check that the contract requires the vendor to cooperate with transition, and send that request in writing.

For replacement procurement, ask procurement whether a cooperative contract can shorten the timeline. Check with other agencies, your state and your associations for existing cooperative contracts, and confirm your own procurement rules allow their use.

Common mistakes that weaken your position

The mistakes below show up in the public audits cited above and, in our experience, in troubled projects generally. None of them feels serious on the day it happens.

  • Accepting revised dates without reserving rights, which can waive liquidated damages.
  • Paying invoices for deliverables that have not passed acceptance.
  • Allowing key personnel swaps without written approval.
  • Escalating only by phone, leaving no record that the vendor had notice.
  • Letting your own late decisions pile up, which hands the vendor a defense.
  • Briefing counsel only after the problem is public.
  • Signing a mutual release in a negotiated exit without counsel reviewing what claims you give up.

If the project needs triage beyond the vendor relationship, our posts on why government ERP projects fail, keeping a public-sector ERP project on scope, and well-known public-sector ERP failures cover the wider picture.

FAQs

Can a city withhold payment from an ERP vendor?

A city can usually withhold payment for deliverables that have not passed acceptance if the contract ties payment to acceptance. Withholding beyond what the contract allows can create a breach claim against the city, so have your attorney confirm the payment, acceptance, and dispute clauses before holding an invoice.

What is a cure notice in an ERP contract?

A cure notice is a formal written notice that the vendor is in breach, describing the specific failures and starting the cure period stated in the contract. If the vendor does not cure within that period, the government may gain the right to terminate for cause. Notice method, addressees, and timing must follow the contract.

How do you terminate an ERP implementation contract?

An ERP implementation contract is terminated under its termination clause, usually for cause after a failed cure period, or for convenience with payment for work performed. Your attorney and procurement director should lead; the governing body typically approves, and you should secure data, documentation, and system access before the vendor leaves.

What is a key personnel clause?

A key personnel clause names the vendor staff who must work on your project and usually requires your written approval before any of them are removed or replaced. Enforcing it lets you reject unqualified replacements, require resumes and references, and ask for a transition overlap at the vendor’s cost.

When should we tell council the ERP vendor is underperforming?

Council should hear about vendor underperformance before any contract amendment, suspension, termination, or significant change to budget or go-live date. A short, factual briefing during a regular update is better than an emergency item, and it gives council time to ask questions before it has to vote.

How long does it take to replace an ERP implementation partner?

Replacing an ERP implementation partner usually adds months because of procurement, onboarding, and rework. Washoe County School District’s switch moved its planned go-live from April 2026 to July 2027. The delay depends on your procurement options, how much prior work is reusable, and how quickly the new partner can start.

Final Words

Washoe’s board was told the district raised concerns within four months and moved to a “quick hook.”

Maryland’s auditors, by contrast, found repeatedly adjusted delivery dates and payments for deliverables nobody had validated. The difference between those two records was built one invoice and one missed date at a time.

If your integrator is missing dates or delivering work that fails testing, start the performance file this week and schedule the rung 2 conversation. If you would like an independent assessment and a team to manage the vendor on your side, learn how KCT’s ERP Recovery & Stabilization works, or book a conversation with KCT to talk through where your project stands.

Ready when you are

Let's talk before it slips.