A Marion Watch “External Observer Forensic IT Investigation”

The Anatomy of a Predicted Collapse (2009–2025)

To the public, Marion’s financial chaos from 2009 to 2021 looked like human error blamed on “complex software.”

To IT professionals, however, these were red flags of deliberate sabotage. Our investigation, which began with rumors of password sharing, suspicion increased drastically with the 2015 Brenda Nwosu theft, concluded that the system’s safety controls were intentionally disabled.

While former Auditor Robert Landon initially claimed he was unaware of these events in 2017, he confirmed that while in office as the Marion City Auditor, he witnessed “permission wars” and demands for shared passwords—claims now corroborated by other officials and other evidence discussed in this article.

These findings prove that previous “spot check” or “general control” audits, such as the ones mentioned having been performed around 2022 were insufficient.

A full forensic IT audit, never performed in Marion’s history, is now non-negotiable according to industry standards.

NOTE: On Mobile Devices Hold Finger on Image & Click Open in Browser or Download to see Full Size Image

---

The “Original Sin”: The Rushed 2009 Install

To an experienced IT administrator, the suspicion started with the implementation timeline itself. 

It’s important to remember that in the information technology sector, this scale of an upgrade is always considered an opportune time for possible malicious actors and backdoor accounts being created. 

The City migrated to the New World system in July 2009.

In any standard IT rollout, such a transition involves months of “parallel testing”—running the old and new systems side-by-side to ensure the safety locks work.

Instead, the 2009 audit reveals that immediately upon “going live,” the City entered a six-month blackout period (December 2009–June 2010) where bank reconciliations simply stopped.

We will discuss this in Exhibit F below.

---

Vindication

Our forensic deductions were later vindicated by facts in official council minutes:

• The Reconciliation Smoking Gun: Council minutes eventually confirmed our long-standing assertion that the Automated Bank Reconciliation module—a standard legally required feature of the software—was never properly installed or activated, forcing staff to rely on manual spreadsheets or other manual involvement for over a decade.

• Veritas mentioned in official council minutes that reconciliation and other issues were present before 2020 but did not investigate as it was outside the scope of their contract.
  
• Misconfigured Settings: Veritas Consultant Greg Blate stated “some of the system settings in New World… are not accurate“.
  
• Data Corruption: Blate demonstrated the severity of this. By changing a single setting—with no financial data change—he created a $137,000 difference in a report total. He also found reports that should have been identical had “differences of upwards of $600,000”.
  
• Incorrect Automation: The system was found to “automate certain transactions, and it books them into cash for non-cash transactions“.
  
• The Collins Confirmation: The current Collins Administration has since confirmed our predictions that other critical safety switches were either off, not present, or grossly misconfigured. This was once again proven true by the findings of the GL override setting being misconfigured in the newly released 2021 audit. 

The software safety controls are legally required.

Software Not Installed / Functioning Properly:

---

New World Issues and Unexplained Errors & Reconciliation Issues Pre 2020 and Other “Inherited Issues”
(VERITAS):

---

---

This following details examples of how we reverse-engineered the “Silent Sabotage” of Marion’s IT infrastructure years before the City finally fully admitted the systems were broken in 2022.

---

Exhibit A: The “Hard Stop” Override

The Legal Requirement: Ohio Revised Code § 5705.41(B) prohibits spending money that hasn’t been appropriated by Council.

The Software Control: Budgetary Hard Stop (Encumbrance Control).

The Public Symptom (Examples of The Evidence):

• 2010 Audit: The first full year of the “New World” system. Auditors noted that the Police Department spent $494,855 more than appropriated.
  
• 2021 Audit: The “unreconciled variance” (the mystery money the City couldn’t account for) and other illegal spending had ballooned.

2021 Audit Examples:

• General Fund-Transfers Out: Spent $1,150,886 over its legal budget.

• Fire Fund: Spent $625,738 over its legal budget.

• Police Fund: Spent $567,688 over its legal budget.

• $543,079 Unaccounted For: The audit found a $543,079 unreconciled and unsupported difference. In plain English, the City had $543,079 in its bank accounts that was not accounted for in its own financial records. The City did not know where this money came from or what it was for.

• Pattern: Year after year, “Expenditures Exceeded Appropriations” appeared as a standard finding. This proves that it is highly likely that the GL Override was misconfigured from the installation of the New World software.

The IT Deduction:

Modern ERP systems have a checkbox setting: “Allow Over-Budget Entry?” or “Activate Hard Stop.”

• If the Hard Stop is Active: The system physically prevents the check from printing. It triggers a “Insufficient Funds” error that cannot be bypassed without a specific administrative password.

• The Deduction: You cannot accidentally drive through a brick wall. The fact that these checks were printed proves that a high-level administrator disabled the Hard Stop. It was activated in 2025 and announced in the newly released Ohio Auditor of State audit for 2021. 

Possible Legal & Compliance Breach:

• ORC § 5705.41(B) Violation: The persistent bypassing of this control resulted in direct, documented violations of state fiscal law.

• ORC § 2921.44 (Dereliction of Duty): By disabling the very mechanism designed to ensure compliance with 5705.41(B), the administration recklessly failed to perform a duty expressly imposed by law—preventing illegal expenditures.

Spending Above Appropriations Questioned at Council

The Conclusion: The system was deliberately configured to allow illegal spending. As detailed in our report “The Override That Broke Marion?”, this “Override Culture” was standard operating procedure established by the Schertzer Administration possibly to allow overspending.

---

Exhibit B: The Checkbook That Wouldn’t Balance

The Legal Requirement: Ohio Administrative Code (OAC) 117-2-02 requires all local public offices to maintain an accounting system and records sufficient to identify transactions and reconcile cash.

The Software Control: Automated Bank Reconciliation Module.

The Public Symptom (The Evidence):

• 2009 Audit: This was the implementation year. The audit noted that the December 2009 reconciliation wasn’t finished until June 2010.

The IT Deduction:

The New World software includes a module that downloads the bank’s digital file and matches it to the City’s ledger instantly. It matches thousands of checks in seconds.

• The Logic: A computer does not get “behind” by six months. Only humans doing manual data entry get behind.

• The Deduction: The six-month delay in 2009 proved the Automated Reconciliation Module was never turned on. The City spent millions on a Ferrari but pushed it by hand for 12 years.
  
• This module was not fully functional until Collins administration came into office.

• There are issues mentioned in Ohio Auditor of State audits regarding software and reconciliation issues prior to 2020.

Possible Legal & Compliance Breach:

• OAC 117-2-02 Violation: The failure to reconcile for months (and eventually years) constitutes a failure to maintain required accounting records.
  
• Breach of Fiduciary Duty: Failing to utilize purchased automated tools to track public funds, resulting in $543,079 in missing/unreconciled money, represents a gross breach of fiduciary responsibility to taxpayers.

The Conclusion: In July 2021, and again in following years’ council minutes the Auditor’s office and Veritas admitted the module “was never properly activated,” confirming the timeline established in “Silent Sabotage II: Decades of Disaster.”

---

Exhibit C: The Invisible Theft (The Brenda Nwosu Case)

The Legal Requirement: Segregation of Duties (Internal Control Principle) and ORC § 2921.41 (Theft in Office).

The Software Control: Approval Workflow Engine.

The Public Symptom (The Evidence):

• 2015 Audit (Finding 2015-001): Utility Supervisor Brenda Nwosu stole $34,276 over 3.5 years (2011–2014). She did this by taking cash payments and then manually “adjusting” the customer’s bill to zero to hide the theft.

The IT Deduction:

In a secure IT environment, hitting “Adjust Balance” triggers a workflow: Request Sent to Manager for Approval.

• The Logic: A thief does not want a manager’s approval. If Nwosu could wipe debts instantly for 3.5 years, she had “Superuser” rights.

• The Deduction: The Approval Workflow was disabled. The “Audit Trail” that should have flagged 71 fraudulent adjustments was either turned off or never reviewed, and possibly concealed from the Finance Committee.

Possible Legal & Compliance Breach:

• Facilitation of Theft: By disabling the Approval Workflow, the IT configuration provided the means for the theft to occur without detection.

• Negligence in Internal Control: The failure to review audit trails for 44 months violates standard government auditing standards (GAS) regarding monitoring.

The Conclusion: Community whistleblowers, including Twila Laing, had warned of this vulnerability but were reportedly ignored and then targeted for retaliation for demanding action. 

The audit confirmed “approvals and monitoring were ineffective,” proving the software controls were wide open.

---

Exhibit D: The $154,000 “Typo” (Vendor Validation)

The Legal Requirement: Proper use of public funds (Proper Public Purpose).

The Software Control: Vendor Validation & Input Masks.

The Public Symptom (The Evidence):

• 2020 Audit (Finding 2020-004): Using the Magic Wrighter ACH system the  City of Marion sent federal tax payments to the State of Ohio for six consecutive months. This resulted in $154,399 in penalties.

The IT Deduction:

Financial systems use “Input Masks” and “Vendor Validation.” If you try to pay the IRS but select the “State of Ohio” Vendor ID, the system should scream “MISMATCH” or “INVALID VENDOR.”

• The Logic: For this error to happen once is a mistake. For it to happen six months in a row means the Validation Rules, and other software safety controls were dormant.
• The system should recognize the length and format of the state and federal account numbers which are generally different from one another and refuse the input. Think of shopping online and the result of entering too few or too many numbers.

• The Deduction: The incoming Landon Administration was flying blind because the previous administration had disabled the safety sensors and—crucially—did not tell them.

Possible Legal & Compliance Breach:

• Waste of Public Funds: The incurring of $154,399 in avoidable penalties due to disabled software validation is a direct waste of public resources.

• Failure to Transfer Knowledge: Concealing the disabled state of validation rules from the incoming administration contributed to the financial loss.
  
  

IT Forensic Summary: Magic-Wrighter Incident

Critical Operational & IT Failures of Images Below

• Audit Logging Failure (Jacob Boldin): The internal investigation was rendered “undetermined” because the IT Administrator, Jacob Boldin, failed to enable the system’s audit trail. He admitted he “didn’t have that setting turned on in the system to track if anyone changed settings,” effectively blinding the organization to who inserted the fraudulent data [Image 1].
  
  • System Defect: Research confirms that Magic-Wrighter systems often do not record “Tracker entries” for employee-initiated setups by default, making Boldin’s configuration oversight catastrophic.   
    
• Destructive UI Design: A severe operational hazard exists in the interface where the “Trash Can” (delete) icon is positioned adjacent to the “Edit” button. This led the user to accidentally delete the “Federal Tax Payment” master account instead of a transaction batch [Image 2].
  
• Master Data Instability: The system permitted a standard user to delete a critical system object (the IRS endpoint). Support staff then guided the manual recreation of this account via phone without proper validation, leading to a configuration error where tax data was transmitted without the required “breakout” metadata (Medicare vs. Withholding) [Image 2].
  
• Segregation of Duties Breakdown: The incident occurred while a new user was processing payroll “solo” with “no guidance,” bypassing standard Maker-Checker operational controls [Image 1].

Suspicious Indicators & Fraud Vectors

• Sabotage Potential: The combination of the “automatic” insertion of Williams and the disabled audit logs (Boldin’s failure) created a “perfect storm” for sabotage, allowing the perpetrator to alter the payroll file with plausible deniability [Image 1].
  
• “Ghost Employee” (Lori Williams): A dormant employee who “didn’t work at all in the last year” was “automatically inserted” into the active payroll batch [Image 1]. This is a primary indicator of a Ghost Employee Scheme, where inactive profiles are reactivated to embezzle funds.   
  
• Concurrent Off-Hours Access: The former payroll specialist, Debbie Wolf, was logged into the system “at off hours (nights and weekends)” simultaneously while the new user was processing the payroll [Image 1]. This indicates unauthorized monitoring or potential database manipulation during the batch window.

Employee Kim Hutchinson Incident Report Detailing the ACH System Issues

The Conclusion: As reported in “Robert Landon Breaks the Silence,” the specific “workarounds” used by the previous administration to navigate this broken system were not passed on. This was the “Knowledge Gap” that turned a configuration error into a financial crisis.

---

Exhibit E: The “God Mode” Anomaly & The Permissions War

​The Incident

In January 2020, Cathy Chaffin vacated the Deputy Auditor position to become Service Director. However, a system screenshot dated March 2021 confirms that for at least 14 months, Chaffin retained “Active” status with “Full” permissions (Add, Change, Delete, Finalize) to the Auditor’s office New World ERP system.

​This was not a system glitch. The software vendor confirmed these permissions must be deliberately granted by a “super administrator,” indicating a purposeful administrative action rather than an error.

​Forensic Analysis of Security Failures

The retention of these permissions for a Service Director violates at least five globally accepted IT security policies, creating a “perfect storm” for potential fraud and surveillance:

• ​Violation of Least Privilege (POLP): A Service Director’s role is to ensure a safe work environment, not manage city finances. Chaffin retained “Financial Management” and “Payroll Security” access, including “Budget Level Maintenance,” which allowed her to create, edit, and finalize budgets at the Auditor level.

• ​Collapse of Segregation of Duties (SoD): SoD requires that the person who initiates a transaction cannot also finalize it. Chaffin possessed the ability to “manipulate financial data and employee pay” and finalize transactions unilaterally. This gave a non-auditor the power to execute and conceal financial activity without independent oversight.

• ​Data Confidentiality Breach: Chaffin retained access to “Human Resources,” “Utility Management,” and “Administrator Security for myReports”. This provided unauthorized visibility into confidential employee records, SSNs, and utility billing data—information totally irrelevant to her new role.

• Destruction of Non-Repudiation (The “Ghost” Account): The existence of this “ghost” account supports reports of a “Permissions War.” By keeping a former Deputy Auditor active with high level access in all modules, the previous administration maintained a “backdoor” to monitor the incoming Auditor (Landon) and potentially override new security controls. Coupled with allegations of password sharing, this destroyed Non-Repudiation—the ability to legally prove who performed a specific action on the network.

Former Deputy Auditor Cathy Chaffin New World Screenshots Showing Inappropriate Permissions 2021 After Leaving the Position in 2020
SOURCE: MARION CITIZEN

NOTICE OF PUBLICATION & PUBLIC INTEREST DISCLAIMER

This documentation is published under the First Amendment as a matter of extreme public concern. These records reveal a critical lack of internal controls and segregation of duties within the City of Marion’s financial administration, posing a direct threat to taxpayer funds.

Though originating from internal systems, these images were obtained lawfully. Under Supreme Court precedent (Bartnicki v. Vopper), the media’s right to publish truthful information regarding public significance supersedes administrative secrecy.

---

Possible ​Statutory & Legal Breaches

Based on the evidence of retained access and the lack of business justification, the following statutes appear to be implicated:

• ​Ohio Revised Code § 2913.04 (Unauthorized Use of Computer Property):

• ​The Breach: Accessing or retaining access to a computer system “beyond the scope of the express or implied consent.” Chaffin’s scope was limited to the Service Department; retaining Auditor-level “God Mode” creates criminal liability.

• ​Ohio Revised Code § 2921.44 (Dereliction of Duty):

• The Breach: The City Administration had a mandatory duty to secure public records. Leaving a “financial vault” open to an unauthorized user for 14 or more months constitutes a reckless failure to perform that duty.

• ​Ohio Revised Code § 1347 (Personal Information Systems Act):

• ​The Breach: State law strictly regulates access to PII. Retaining view-access to employee and licensee Social Security Numbers without a valid job function is a direct violation.

• ​Federal Computer Fraud and Abuse Act (18 U.S.C. § 1030):

• ​The Breach: Retaining administrative capabilities after a job change falls under “exceeding authorized access,” particularly if that access was utilized to monitor, hinder, or alter data under the new administration.
  

The Conclusion:

The retention of Cathy Chaffin’s access represents a “major ethical failure” and a systemic breakdown of the City of Marion’s access control policies. It provided the means, motive, and opportunity for the “Permissions War,” allowing the old administration to maintain control over city finance long after they were legally required to step aside.

---

Exhibit F: The “Original Sin” — The Rushed Implementation of New World 2009

The IT Standard: System Development Life Cycle (SDLC).

In any standard government IT rollout, a transition to a complex ERP system like New World involves a critical phase known as “Parallel Testing.” This typically lasts 3–6 months, during which the old system and the new system are run simultaneously to ensure the new “safety locks” (reconciliations, budget stops) match the old records exactly.

The Public Symptom (The Evidence):

• Go-Live Date: July 2009.

• The Blackout: The 2009 Audit (Finding 2009-002) reveals that immediately upon “going live,” the City entered a six-month blackout period (December 2009–June 2010) where bank reconciliations simply stopped.

• The “Ghost Committee”: The Information Systems Committee, responsible for overseeing this massive transition, failed to enforce this testing phase or intervene when reconciliations halted.

The IT Deduction:

To an experienced IT professional, a “Go-Live” followed immediately by a six-month reconciliation failure is the hallmark of a Rushed Install.

• Suspicion (2015): We suspected that the “hard” modules—specifically Automated Reconciliation and Budget Controls—were bypassed or never installed to meet an artificial deadline or to avoid the friction of proper accounting.

• Confirmation: The subsequent failure to ever turn these modules on (until 2022) confirms they were not just “glitchy”; they were dormant. The administration prioritized “being online” over “being secure.”

Furthermore the stated reason for this emergency measure was that the software was about to become incompatible or expire. 

• The IT Deduction: A system that “goes live” but immediately fails to perform basic balancing has not been properly configured.
  
• It suggests a rushed installation where the “hard” modules—specifically legally required Automated Reconciliation and Budget Controls—were bypassed or never installed to meet a deadline. 

• We later predicted that these modules were left in a “dormant” state to avoid the friction of proper accounting. This created a “Knowledge Gap” that plagued the city for over a decade.

• The declaration of the emergency software purchase is highly suspicious. 

• Hardware (Servers): A server’s “End-of-Life” (EOL) date is publicly announced by the manufacturer 5 to 10 years in advance. A competent IT department would begin planning the replacement at least 1-2 years before that date.

• Software (Licenses): A critical software license is a contract with a fixed end date. The expiration is known years in advance and is a recurring line item in the annual budget. Vendors typically send renewal notices at least 12 months (usually more) before the expiration. 

Possible Legal & Compliance Breach:

• Negligence in IT Governance: The failure to ensure parallel testing and the immediate collapse of reconciliation controls represents a failure of the fiduciary duty of oversight by the Administration and Council.
  

---

Part VI: Summary of Legal & Compliance Breaches for IT Controls

This investigation has identified that the “Silent Sabotage” was not merely a series of bad habits; it was a systematic violation of legal and control frameworks. The following table summarizes the legal exposure created by these disabled controls.

---

Part VII: Conclusion — The Verdict of the “Digital Blackout”

The forensic evidence gathered from over a decade of state audits, combined with the specific timeline of IT failures, leads to a singular, inescapable conclusion: The City of Marion did not just suffer from a software failure; it suffered from a governance failure.

The Architecture of Sabotage

The term “Silent Sabotage” was chosen carefully. Sabotage implies intent—or at the very least, gross negligence so profound it mimics intent. To the forensic IT auditor, the “intent” is visible in the consistency of the deactivation.

• They did not disable random modules. They disabled the Accountability Modules.

• They disabled the module that stops theft (Workflow).

• They disabled the module that prevents debt (Hard Stops).

• They disabled the module that proves truth (Reconciliation).

The “Human Shield” Defense

For years, City officials used the “complexity” of the New World software as a shield. They claimed the system was “too hard” or that “turnover” prevented mastery. Our investigation exposes this as a fallacy.

• Reality: Turning on an automated feature makes the job easier, not harder.

• The Deduction: The features were not avoided because they were complex; they were avoided because they were restrictive. They prevented the “flexibility” the administration desired to move money without oversight.

The Timeline of Vindication

• 2009-2015 (Suspicion): The Brenda Nwosu theft proved that no one was watching the digital doors.

• 2017–2019 (Certainty): The repeated “appropriations exceeded” findings proved the budget locks were cut.

• 2022-2023 (Proof): The admission that the Reconciliation Module was never installed confirmed the “Blackout.”

• 2025 (Validation): The current administration’s confirmation of these and other theories we have long had stands as the final vindication of the Marion Watch IT investigation.

---

The Cost of Silence

The quantifiable cost of this “Silent Sabotage” caused millions in penalties, theft, and uncertified variances. 

However, the true cost is the “Digital Blackout” itself—a twelve-year period where the City of Marion cannot say with 100% certainty where every dollar went, because the digital ledger was deliberately blinded.

The 2021 Qualified Audit Opinion and the Ohio Auditor of State declaring the financial ledger is considered unreliable is not just a bad grade; it is a coroner’s report for the City’s financial integrity. It confirms that by the time the “Silent Sabotage” was admitted, the system was already dead.

---

Silent Sabotage Related Articles & Works Cited – Other Works Cited are in MWI Articles (CLICK HERE):

The Silent Sabotage Truth Again Proven Accurate: https://news.marionwatch.com/2025/11/24/the-silent-sabotage-truth-again-proven-accurate/10/13/marion-news/admin/

“The Inconvenient Receipts” Facebook Teaser:
https://www.facebook.com/share/p/16Ukt11xZ1/

The Override That Broke Marion? How a Hidden Software Loophole Fueled 16 Years of Fiscal Chaos & Contributed to the Silent Sabotage https://news.marionwatch.com/2025/11/21/the-override-that-broke-marion-how-a-hidden-software-loophole-fueled-16-years-of-fiscal-chaos-contributed-to-the-silent-sabotage/05/45/marion-news/admin/

Part II: The 20-Year ‘Ghost Committee’ That Oversaw Marion’s IT Collapse https://news.marionwatch.com/2025/11/17/part-ii-the-20-year-ghost-committee-that-oversaw-marions-it-collapse/17/48/marion-news/admin/

Former Auditor Landon Claims Vindication as Audits Confirm Financial Flaws https://news.marionwatch.com/2025/11/14/former-auditor-landon-claims-vindication-as-audits-confirm-financial-flaws/09/16/marion-news/admin/

Silent Sabotage Culture Again Proven: Newly Released 2021 Audit Reveals Ongoing Severe Mismanagement, Illegal Spending, and Critical IT Failures https://news.marionwatch.com/2025/11/13/silent-sabotage-culture-again-proven-newly-released-2021-audit-reveals-ongoing-severe-mismanagement-illegal-spending-and-critical-it-failures/12/13/marion-news/admin/

The 20-Year ‘Ghost Committee’ That Oversaw Marion’s Silent Sabotage IT Collapse https://news.marionwatch.com/2025/11/12/the-20-year-ghost-committee-that-oversaw-marions-silent-sabotage-it-collapse/18/25/marion-news/admin/

The Silent Sabotage Time Bomb: Marion Watch Predicts Sewer Sanitation & Utility Billing STILL Following the Trail of Broken IT & Financial Controls https://news.marionwatch.com/2025/11/10/the-silent-sabotage-time-bomb-marion-watch-predicts-sewer-sanitation-utility-billing-still-following-the-trail-of-broken-it-financial-controls/17/48/marion-news/admin/

Silent Sabotage III: A Pattern of Problems Marion City Audits Reveal Four Decades of Control Failures 1983-1999 & 2000-2025
https://news.marionwatch.com/2025/11/09/silent-sabotage-iii-a-pattern-of-problems-marion-city-audits-reveal-four-decades-of-control-failures-1983-1999/05/02/marion-news/admin/

Robert Landon Breaks the Silence:
https://news.marionwatch.com/2025/08/16/robert-landon-breaks-the-silence/19/32/marion-news/admin/

Marion Watch Silent Sabotage Research Prompts Mayor’s Request for Forensic IT Audit: https://news.marionwatch.com/2025/11/03/marion-watch-silent-sabotage-research-prompts-mayors-request-for-forensic-it-audit/17/14/marion-news/admin/

The New World System: One Party Control, the Great Recession, and a Fiscal Nightmare for Marion: https://news.marionwatch.com/2025/11/01/the-new-world-system-one-party-control-the-great-recession-and-a-fiscal-nightmare-for-marion/17/20/marion-news/admin/

Marion Watch Predicts: Old, Unsafe Computer Habits Likely Still Harming City Finances: https://news.marionwatch.com/2025/11/07/marion-watch-predicts-old-unsafe-computer-habits-likely-still-harming-city-finances/05/47/marion-news/admin/

Mayor Collins Announces Fiscal Caution Analysis: https://news.marionwatch.com/2025/10/29/mayor-collins-announces-fiscal-caution-analysis/06/28/marion-news/admin/

The Bomb at the Center of Marion’s Financial & IT Silent Sabotage Blast: https://news.marionwatch.com/2025/10/27/the-bomb-at-the-center-of-marions-financial-it-silent-sabotage-blast/17/51/marion-news/admin/

Echos of Silent Sabotage ‘Same Issues, New Account’: Fraud Hits City’s New Checking Account:
https://news.marionwatch.com/2025/10/22/echos-of-silent-sabotage-same-issues-new-account-fraud-hits-citys-new-checking-account/02/51/marion-news/admin/

‘Misfeasance’ Charge Against Auditor, Flock Camera Legality Dominate Council Committees: https://news.marionwatch.com/2025/10/21/misfeasance-charge-against-auditor-flock-camera-legality-dominate-council-committees/05/54/marion-news/admin/

“You Lose Control”: Veteran IT Specialist Ralph Smith Demands Audit, Slams Marion’s Financial Failures:
https://news.marionwatch.com/2025/10/10/you-lose-control-veteran-it-specialist-ralph-smith-demands-audit-slams-marions-financial-failures/05/48/marion-news/admin/

Heated Exchanges in Finance Committee Overshadow Marion Council’s Development Talks: https://news.marionwatch.com/2025/10/08/heated-exchanges-in-finance-committee-overshadow-marion-councils-development-talks/05/42/marion-news/admin/

Twila Laing: Silent Sabotage and the Crisis of Financial and IT Controls:
https://news.marionwatch.com/2025/10/05/twila-laing-silent-sabotage-and-the-crisis-of-financial-and-it-controls/10/18/marion-news/admin/

Marion Charter Candidate Lovell Calls for Radical Financial Overhaul, Citing Decades of Dysfunction: https://news.marionwatch.com/2025/10/04/marion-charter-candidate-lovell-calls-for-radical-financial-overhaul-citing-decades-of-dysfunction/11/03/marion-news/admin/

The Digital Profile: Why Local Financial Failures Fit a Federal Pattern of Silent Sabotage: https://news.marionwatch.com/2025/10/03/the-digital-profile-why-local-financial-failures-fit-a-federal-pattern-of-silent-sabotage/05/30/marion-news/admin/

Prelude to Silent Sabotage III:Marion’s 40-Year Financial Collapse:
https://news.marionwatch.com/2025/09/29/prelude-to-silent-sabotage-iii-marions-40-year-financial-collapse/05/51/marion-news/admin/

Ohio Auditor of State Responds to the Silent Sabotage of Marion City’s Financial and IT systems: https://news.marionwatch.com/2025/09/28/ohio-auditor-of-state-responds-to-the-silent-sabotage-of-marion-citys-financial-and-it-systems/13/41/marion-news/admin/

Marion City Council Grapples with Financial Chaos, Software Woes, IT Audit, and a Push for Accountability in Spirited August 4th Meeting: https://news.marionwatch.com/2025/08/06/marion-city-council-grapples-with-financial-chaos-software-woes-it-audit-and-a-push-for-accountability-in-spirited-august-4th-meeting/05/35/marion-news/admin/

Marion Council Tackles Charter Vote, Financial Scrutiny, and Alleged IT Misconduct: https://news.marionwatch.com/2025/07/22/marion-council-tackles-charter-vote-financial-scrutiny-and-alleged-it-misconduct/05/48/marion-news/admin/

Silent Sabotage II: Marion City Auditor Decades of Disaster and the Roots of the Silent Sabotage:
https://news.marionwatch.com/2025/07/20/silent-sabotage-ii-marion-city-auditor-decades-of-disaster-and-the-roots-of-the-silent-sabotage/19/22/marion-news/admin/

Silent Sabotage: Did Marion Insiders Let Financial Problems Fester?: https://news.marionwatch.com/2025/05/05/silent-sabotage-did-marion-insiders-let-financial-problems-fester/05/29/marion-news/admin/

A Quick Look: Marion’s Auditor Office: A Decades-Long Disaster Zone (Full Investigation Coming Soon):
https://news.marionwatch.com/2025/05/02/a-quick-look-marions-auditor-office-a-decades-long-disaster-zone-full-investigation-coming-soon/04/45/marion-news/admin/

2021 Annual ACH Risk Assessment and Data … – CU*Answers, https://www.cuanswers.com/wp-content/uploads/ACH-Audit-and-Risk-Assessment-FY-2021.pdf

Protecting Your Organization from Employee & Payroll Fraud Schemes – EisnerAmper, https://www.eisneramper.com/insights/blogs/forensic-litigation-valuation-blog/payroll-fraud-flvs-blog-1119/

FRAUD PREVENTION ALERT Payroll Disbursement Frauds December 2021 – AZ Auditor General, https://www.azauditor.gov/sites/default/files/2023-11/21-408_Alert.pdf

A2A Transfers | CU*Answers, https://www.cuanswers.com/wp-content/uploads/A2ATransfers.pdf

Owner’s View – CU*Answers, https://www.cuanswers.com/resources/owners-view/