Written by The January 12, 2026, Marion City Council meeting served as a public post-mortem for a transition that has officially jeopardized the city’s financial integrity. In a move that signaled a total breakdown in communication, City Auditor Miranda Meginness was notably absent from the chambers, leaving Council to face a mounting pile of excuses from her office. The tension reached a peak when representatives from Marion Technical College offered to assist the city in navigating the technical fallout and finding solutions to the ongoing data crisis.
By tracing the failures from the past warning signs to today’s “Fiscal Caution” status, we’ve uncovered a massive gap between administrative rhetoric and professional IT and financial/ payroll standards.
The “Excuse” vs. IT Reality
During the sessions, the Auditor’s Administration provided a startling justification for the ongoing payroll chaos: the claim that the system “doesn’t handle” benefits-related tasks at all. This admission was used to explain the persistent need for manual workarounds. However, when measured against global IT and payroll standards, this excuse points to a catastrophic failure of leadership and procurement, not a limitation of the technology itself. Drawing from the expertise of our Citizen Action Network let’s look closer at this mess.
Video showing the City Auditor being defiant insisting on switching back to the previous payroll system.
1. The Benefits “Dead Zone”
- The Excuse: The administration claimed ADP cannot handle insurance deductions, retirement contributions (OP&F/OPERS), or specialized certification pay.
- The Reality: ADP is an industry leader in HCM (Human Capital Management). Claiming it “doesn’t handle” benefits is the professional equivalent of saying a jet engine “doesn’t handle” fuel.
- The Investigative Truth: If the system is not processing these, it means the city either purchased the wrong “tier” of software or—more likely—failed the Implementation Testing Phase. Standard IT protocol requires a Gap Analysis; if the city bought a system that couldn’t handle its union requirements, it was a failure of due diligence.
- These IT focused failures have consistently been proven true by Marion Watch. To a trained eye, these are predictable outcomes from a failure to test.
2. The Certification Pay Failure
- The Excuse: “Glitches” caused police and fire “add-on” pay to fail, leaving checks short by $500–$600.
- The Reality: Standard ERP (Enterprise Resource Planning) migration requires “Logic Mapping.” ADP supports multi-tiered pay structures. This failure suggests the administration “flipped the switch” without ever programming the system to recognize Marion’s specific union contracts.
3. The Bank Transfer “Miscommunication”
- The Excuse: A “miscommunication” between the city, Fahey Bank, and ADP led to a total failure to fund paychecks on a scheduled Friday in November 2025.
- The Reality: Professional IT management requires a “Cutover Plan” with a “Pre-Flight Check” 48–72 hours before disbursement. This wasn’t a communication error; it was a total breakdown of Standard Operating Procedure (SOP).
- The disruption was directly caused, as advised by the Collins administration, by Deputy Auditor Marden Watts failing to send the necessary money to ADP to release to the banks
Video showing Miranda Meginness and Mayor Collins facing off
Reinstating the IT Oversight Committee
To stop the “bleeding,” City Council has officially reinstated the IT Oversight Committee. This move shifts power away from an Auditor’s Administration that has presided over five years of unreconciled books and into a transparent, audit-driven body.
The Committee’s Immediate Mandate:
- Procurement Audit: They will review the original Statement of Work (SOW) to see if the city was sold a product that didn’t meet its needs or if it was simply implemented incorrectly.
- Eliminate “Shadow Data”: Best practices state that manual “workarounds” create “shadow data” that makes a clean state audit impossible. This is a primary reason the city remains in Fiscal Caution after fifteen years of using misconfigured software.
- Governance: No more “flipping the switch” on major software—such as upcoming utility billing shifts—without a signed-off Risk Assessment.
Closing: Negligence or Intentional Sabotage?
As the meeting drew to a close, a darker sentiment echoed through the council chambers. Several council members noted that the Auditor’s office seems fundamentally unwilling to use the ADP system, despite it being the city’s official platform.
The sentiment from the floor was clear: the constant claims that the system “doesn’t work” feel less like technical limitations and more like intentional protest. Hints were made that the continued reliance on manual workarounds—despite having a world-class automation tool at their fingertips—may constitute a form of deliberate sabotage to prove the system “failed” so the office can return to outdated, less transparent methods of bookkeeping.
With the city in Fiscal Caution, complex software changes due to 15 years of IT failures, and a milti-million, million deficit looming, the IT Oversight Committee is no longer a luxury; it is an emergency measure to ensure that personal or political vendettas do not continue to compromise the paychecks of Marion’s first responders and civil servants.