Mainframe payroll scope, 2026 calendars and access windows
Published: Not stated · Accessed: 2026-10-31A SOURCE-LINKED NATIONAL VIEW
The state payroll
landscape, in context.
Explore all 50 state profiles. System scope, implementation status and hosting evidence are kept separate. Research is dated and should be reconfirmed for an agency decision.
THE NATIONAL LANDSCAPE
50 states. Different systems.
A common need for accountable pay.
Primary-source research separates the payroll core from HR, finance and planned replacements. Use the evidence to plan a migration that fits each agency.
50states researchedAs of 2026-10-31
Source records194State operations, budgets, audits and vendor announcements
Transition evidence23States with at least one implementation or planned system
Qualified findings7State summaries with material verification limits
Validated CivicWage rule packs0System research does not validate statutory payroll
Cloud hosting is already common. Better outcomes need proof.
Our design priorities are employee-level accuracy, transparent rules, portable interfaces, preserved history and independent review. This research does not establish that CivicWage outperforms an incumbent or that every agency uses the listed central system.
Explore state systems
Mississippi: systems and transition evidence
high confidenceEvidence supports a mixed SPAHRS payroll / MAGIC HR and finance landscape, not a verified completed statewide SuccessFactors Payroll replacement.
| System / vendor | Module scope | Status | Hosting | Evidence |
|---|---|---|---|---|
| SPAHRSState-maintained mainframe system; software vendor not established | Central payroll and human resources | live | unknown | 2026-10-31DFA currently publishes 2026 pay calendars and describes central mainframe payroll; the 2025 state vacancy explicitly assigns payroll processing to SPAHRS.Source 1 ↗Source 2 ↗ |
| MAGIC HR / SuccessFactorsSAP | Statewide HR functions / Employee Central ecosystem | live | cloud | 2026-10-31DFA vacancy distinguishes MAGIC HR from SPAHRS payroll. Do not infer that all payroll is in Employee Central Payroll.Source 1 ↗ |
| Employee Central Payroll planned rolloutSAP | Payroll replacement originally planned after Employee Central | uncertain | cloud | 2019-112019 newsletter describes phased ECP rollout. No reviewed official source establishes statewide ECP payroll cutover.Source 1 ↗ |
Procurement and transition context
Earlier MAGIC project totals cannot be treated as payroll-only subscription spend. Verify contract line items and each agency cutover independently.
Documented operational findings
- SPAHRS lists limited operating windows and a request process for after-hours access. Evidence ↗
- Published interface instructions describe budget/cash/code checks and a delay before payroll interface results return; historical guide must be reconfirmed. Evidence ↗
Limits and unresolved questions
The mainframe architecture does not establish the physical hosting arrangement; SPAHRS hosting is therefore unknown. SuccessFactors SaaS classification is product-level; current ECP agency coverage remains unknown.
Mississippi source register
Explicit division between SPAHRS payroll and MAGIC HR
Published: 2025-07-24 · Accessed: 2026-10-31SPAHRS integration resources
Published: Not stated · Accessed: 2026-10-31Historical phased ECP intention; not current go-live proof
Published: 2019-11 · Accessed: 2026-10-31Payroll journal edits and interface-result workflow
Published: Not stated · Accessed: 2026-10-31Research method and coverage
Central state-government HR/payroll; agency exceptions and non-payroll modules identified where evidenced. US territories and DC are outside this 50-state research census.
Primary state operations, procurement, audit and budget sources prioritized; primary vendor implementation announcements supplement them. Live, implementation, legacy and uncertain labels describe the cited evidence, not statutory validation. Hosting is not inferred merely from a product name. Source publication dates and planned go-live dates are kept distinct.
“Live” applies only to the documented module and population. A target date does not prove deployment. “Unknown” hosting is intentional. Confidence describes the bounded summary, not legal compliance or vendor performance. The 50-state census excludes DC and territories; their configuration options in agency setup are separate from this research.
LET’S START WITH YOUR WORKFLOW
A better payroll process
starts with a closer look.
Bring one agency, one workflow and the questions your team needs answered.