Before the Payment Gap: ERP Go-Live Execution in the Final 90 Days

The prerequisite phase ends; the execution phase begins

An earlier Signal article on [ERP modernization prerequisites](/signal/state-erp-modernization-prerequisites) covered what needs to be true before a state issues an RFP: named data ownership, process authority, funded change management, independent oversight staffing, and governance that includes technical judgment. Those conditions determine whether a program runs fundamentally differently or accepts substantial risk from the start.

The execution phase tests whether those conditions actually held. Organizations that resolved prerequisites on paper often discover in the final sprint that the data owner did not have the authority they thought, the process authority stopped at a department boundary, or the change management program was quietly defunded during a budget revision two years ago. The cutover window makes these gaps visible and expensive.

The primary operational difference is time compression. Decisions that would have been recoverable with six months of runway become go/no-go calls with hours of runway. The execution phase requires the same governance disciplines as the preparation phase but with tolerances measured in days rather than quarters.

Florida PALM: what the October 2026 timeline looks like

Florida's PALM project — replacing FLAIR, the state's mainframe accounting system that dates to the 1980s (called SAMAS until 1997) — is the most publicly documented major state financial system transition currently in the final sprint, and it is operating under active cutover deadlines as of this publication. The Florida Department of Financial Services' implementation timeline records that the go-live date moved from July 2026 to January 12, 2027. The Florida Auditor General's February 2026 report states the move was made "to provide sufficient time for implementation planning, comprehensive testing, and redesign of internal financial management processes."

Agency Address Memorandum No. 8 (revised October 16, 2026), titled "FLAIR and Florida PALM Cutover Activities," is the operative document for cutover mechanics. The October 2026 issue of the A&A Ledger summarizes where the program stands today:

• Go-live: January 12, 2027. Deployment activities begin in December 2026.
• User Acceptance Testing: ran from February through October 2026, with end-to-end interface testing running concurrently (per the implementation timeline).
• System downtime: all state financial systems go offline at 5:00 p.m. on December 23, 2026, per AAM No. 8. No payments or deposits are processed until catch-up processing begins or until go-live on January 12. Florida has published a supplier and employee Q&A page and a sample vendor notice for agencies to send.
• Payroll: scheduled around the downtime. The biweekly warrant-dated December 24, a supplemental payroll warrant-dated December 29, and the monthly warrant-dated December 31 are all processed before systems go offline. The January 8, 2027 biweekly payroll runs in PALM during catch-up. Agency Addressed Memorandum No. 6 (September 4, 2026) establishes the payroll cutover calendar.
• PCard cutover: the last day to approve existing PCard transactions in Works for FLAIR processing is December 15, 2026; errored transactions must also be resolved by then (AAM No. 8, items 7–8).
• Override deadline: the Bureau of Auditing stops manual budget or cash overrides after 4:00 p.m. on December 15, 2026 (AAM No. 8, item 9). Vouchers not submitted by then are deleted and must be processed in PALM after go-live.
• FLAIR status: FLAIR remains Florida's system of record until PALM is fully implemented, per the Auditor General's February 2026 report.

One reading of the additional Dry Run inserted into the schedule — which the implementation timeline describes as supporting ongoing data cleansing — is that data readiness was not where the program needed it when the July deadline approached. The AG report attributes the slip to schedule delays across several key areas including the start of UAT; data readiness specifically was not named. Either way, a late-cycle Dry Run is a sign that the program is being honest about data quality rather than declaring victory early.

The downtime is the highest planning risk

Most state ERP transitions involve some version of a system downtime: a window around cutover when the old system is locked and the new system is not yet running production transactions. For a vendor or employee waiting on payment, this gap can be invisible — until a check doesn't arrive.

Florida's downtime window runs nearly three weeks — from December 23 at 5:00 p.m. until catch-up or go-live on January 12 — and it spans the holidays when agencies, vendors, and employees expect payment activity to be normal or accelerated. Payroll has been scheduled around it, but ad hoc disbursements, vendor invoices, and grant draws have not. State agencies that have not already taken the following steps need to act now:

Verify the advance-payment deadline has been met. AAM No. 12, which covers processing advanced disbursements in preparation for the cutover, set a deadline of November 2, 2026 at 12:00 p.m. for advance-payment approval requests. That date has passed. Agencies that missed it should confirm with the Bureau of Auditing what options remain for critical disbursements that cannot wait until January 12.

Identify remaining critical disbursements before December 17. Departmental FLAIR and MFMP payment entry ends December 17. Vendor contracts with payment terms that trigger penalties, grant disbursements with federal reporting deadlines, and employee deductions tied to benefit enrollment windows all require resolution before that date, not before "the end of December."

Communicate to vendors and partners. Florida published a sample vendor communication for agencies to send. Vendors have no obligation to know a state is in the middle of a cutover, and communication that reaches them before December reduces escalation volume when payments stop arriving.

Know the contingency payment options. Florida's Deployment Planning page notes that contingency payment plans require weeks of advance notice. The authority to process a critical disbursement during the downtime window should be documented in writing before December, not improvised on December 28.

Interface testing: the last-mile failure mode

In the author's assessment, interfaces are a leading risk in ERP go-lives because they pass functional testing in isolated environments and then fail under production load or when encountering data that test environments did not include. A state financial system connects to many other systems: the payroll and HR platform, procurement systems, the state Medicaid Management Information System, banking files, and Department of Revenue feeds, among others. Florida's Deployment Planning page names banking files and multi-agency files from the Department of Revenue as specific coordination items for the cutover.

Complete the interface inventory before Stage Gate 4. It is common at this stage of a major ERP transition for the program team to know the interfaces it built and tested but not to have a complete list of interfaces built by individual agencies against the old system. Those agency-side connections often did not go through formal testing and frequently fail at go-live. The inventory exercise needs to produce a list with an owner, a test result, and a production readiness status for every interface.

Run production-load tests, not just functional tests. A functional test confirms that an interface works correctly for a representative transaction. A production-load test confirms that it works correctly when the full volume of transactions from the first business day after go-live arrives simultaneously. The failure point for many interfaces is not logic but throughput. If production-load testing has not been completed, this is the last opportunity.

Document rollback criteria for each critical interface. If a payroll disbursement interface fails at 2:00 a.m. on go-live night, the program team needs a pre-agreed decision rule: at what point do they invoke rollback, what does rollback require, and who has the authority to call it? These are not questions to answer under pressure during a cutover weekend.

Data cleansing: the problem that compounds under time pressure

Data cleansing in an ERP transition is not a project task that gets completed and checked off. It is a continuous process of discovering exceptions in legacy data that the new system's validation rules surface. The earlier in the program this discovery starts, the more time exists to investigate, correct, and verify. By the final sprint, each new exception discovered requires an immediate decision: fix it, suppress it with a documented exception, or hold the affected record in the old system.

Florida's insertion of an additional Dry Run specifically to support ongoing data cleansing illustrates how this phase typically goes. Dry runs surface edge cases that earlier cleansing did not catch because they only appear when the full data set interacts with the full system configuration. A Dry Run late in the cycle is not a sign that earlier cleansing was wasted; it is a sign that the program is being honest about data quality.

For agencies approaching a similar window:

• Prioritize open balances, active vendor records, and employee records. These are the data sets that must convert accurately on day one. Errors in historical transaction data can often be corrected after go-live; errors in open balances and active vendor payment records cannot.
• Lock the data cleansing scope. At 90 days, every new cleansing initiative needs to clear a high bar. Adding scope in the final sprint introduces risk that exceeds the benefit of the additional cleansing. Establish a hard cutoff for new data quality items entering the queue.
• Document the accepted exceptions. For records that will convert with known exceptions, document the exception, the decision rationale, and the post-go-live remediation plan. Undocumented exceptions become undiscoverable problems after go-live.

User training: the window that most programs get wrong

Training delivered long before users can practice the new system on real transactions decays. The structural tension in ERP go-live programs is that the training team needs enough time to reach all affected staff, but training delivered too early — before a practice environment is accessible and before users can apply what they learned — is largely lost by go-live. The practical resolution for a January 12 go-live is to schedule role-specific training as close to the go-live date as delivery capacity allows.

Florida's production system is inaccessible to agency end-users between December 23 and January 12; the UAT environment remains available through the transition for practice [Deployment Planning page]. Programs that invest in reference materials and visible day-one support staffing tend to see faster time-to-competence than programs that invest in longer training with no day-one support.

More important than the training itself is what happens between training and go-live. Users need access to a practice environment, a reference document that covers the specific transactions for their role (not the full system), and a named person they can call on day one when they encounter something the training did not cover.

The go/no-go governance gap

A concern in ERP go-lives is that programs proceed without a clear go/no-go decision structure: the date arrives and the system goes live because it was scheduled to, rather than because a named decision-maker reviewed specific acceptance criteria and authorized the go-live. That risk is real. But what the right governance structure looks like depends on the program design.

Florida uses a documented Stage Gate model. Stage Gate 5, a Deployment Readiness vote by the Executive Steering Committee, is scheduled for December 16, 2026. Stage Gate 6, the Project Director's decision on January 4, 2027, is what the Deployment Planning page calls the "critical point of no return": once payroll is processed in PALM, the system must go live. If Stage Gate 6 does not approve go-live, a fallback to FLAIR begins — but that option closes once payroll runs. The ESC votes again on January 11; Florida PALM can go live even if some agencies have not achieved all readiness certification criteria.

That design — payroll as the irreversibility point, with a separate fallback-or-proceed decision on January 4 — is worth examining for any state running a comparable financial system transition. The key features are:

• The go/no-go authority is named and tiered. Stage Gate 4 (agency readiness), Stage Gate 5 (deployment readiness), and Stage Gate 6 (point of no return) each have a designated authority, with the most consequential decision falling to the Project Director, not the program manager.
• Quantitative thresholds replace judgment. Readiness certification can be incomplete at go-live; the question at Stage Gate 6 is whether proceeding is safer than rollback given where things stand.
• Rollback is a real option until a specific date. Florida's contingency restore point, created after final FLAIR processing, is the rollback mechanism. It works until payroll processes in PALM on January 8, 2027. After that, fallback is not possible.

States that want to replicate Florida's model need to define the irreversibility point — whether it is the first payroll run, the first accounting close, or something else — and establish the go/no-go decision before it arrives.

Florida's actual cutover sequence, with key dates

For a January 12, 2027 go-live, Florida's published documents establish this sequence. Florida agencies should follow AAM No. 8, AAM No. 12, and the Deployment Planning page directly; this summary is for orientation, not a substitute.

Already passed (as of publication, October 30, 2026):

• November 2, 2026 at 12:00 p.m.: Deadline for advance-payment approval requests (AAM No. 8, item 5). Agencies that missed this should contact the Bureau of Auditing.

Between now and Stage Gate 4 (November 18, planned):

• November 13, 2026: ChartField value freeze (Deployment Planning page).
• November 18, 2026: Stage Gate 4 — Agency Readiness (planned per AG Report 2026-101).
• November 30, 2026: Final configuration and conversion workbooks due (Deployment Planning page).

December:

• December 4, 2026: Supplier, contract, and grant setup freeze (Deployment Planning page).
• December 15, 2026: Last day to approve existing PCard transactions in Works and resolve errors; Bureau of Auditing manual overrides stop at 4:00 p.m. (AAM No. 8, items 7–9).
• December 16, 2026: Stage Gate 5 — ESC Deployment Readiness vote (Deployment Planning page).
• December 17, 2026: Last day for Departmental FLAIR and MFMP payment entry (AAM No. 8).
• December 23, 2026 at 5:00 p.m.: All systems go offline. No payments or deposits until catch-up or go-live (AAM No. 8).

January:

• January 4, 2027: Stage Gate 6 — Project Director point of no return. Once payroll processes in PALM, go-live must proceed; fallback to FLAIR closes (Deployment Planning page).
• January 11, 2027: ESC go-live vote (Deployment Planning page).
• January 12, 2027: Go-live.

What other states' programs need to take from this

Florida's PALM timeline is the most detailed public record of a large-scale state ERP cutover in the final sprint currently available, and NASCIO's placement of enterprise resource planning at number seven on its 2026 Priority Technologies list for state CIOs reflects that Florida is not alone. States running PeopleSoft, Oracle EBS, or aging custom financial systems toward modern replacements face the same execution challenges.

South Dakota's Project BISON, a statewide ERP transition with a July 2027 go-live, is the next comparable program in public view.

The organizational conditions that determine outcomes — a named decision authority with a real go/no-go process, an interface inventory that includes agency-built connections, data exception protocols that are honest rather than optimistic, and an irreversibility point that is defined before it arrives — are not Florida-specific. They apply to any state financial system replacement approaching the final sprint.

The most important thing a state CIO or CFO can do right now, for any major ERP transition within 120 days of go-live, is convene a review of these specific items: not a program status update, but a direct check on each acceptance criterion. The review surfaces issues when there is still time to act on them.

Sources and further reading

• Florida PALM implementation timeline: myfloridacfo.com/floridapalm/implementation-timeline
• Florida Department of Financial Services, *The A&A Ledger*, Issue 14, October 2026 (go-live date, deployment summary): myfloridacfo.com
• Agency Addressed Memorandum No. 8 (revised October 16, 2026), "FLAIR and Florida PALM Cutover Activities" (PCard, override, and downtime deadlines): myfloridacfo.com
• Agency Addressed Memorandum No. 6 (September 4, 2026), "2026 Payroll Cutover Calendar Information" (payroll schedule around downtime): myfloridacfo.com
• Agency Addressed Memorandum No. 12, "Revised – Processing Advanced Disbursements to Prepare for Florida PALM Cutover" (advance-payment deadlines): myfloridacfo.com
• Florida PALM Deployment Planning page (Stage Gates, ChartField freeze, point of no return): document360.io
• Florida Auditor General Report No. 2026-101, February 2026 (schedule history, FLAIR system-of-record status): flauditor.gov
• NASCIO, *2026 State CIO Top 10 Priorities* (ERP as #7 priority technology): nascio.org
• South Dakota Project BISON go-live timeline, SD.gov knowledge base: sd.gov

Spartan X's program execution and systems modernization practice — legacy migration, data pipeline design, and multi-agency systems integration — maps to the data conversion, exception-tracking, and interface coordination work that determines whether a cutover executes cleanly. State programs in the final sprint face the same decisions regardless of platform; execution risk is organizational, not technical.