Administrative, financial, operational, and personal — the four costs of a MAS finding, and what ‘audit-ready’ actually looks like.
The letter arrives from the AOC. Your court has completed its triennial independent review, and the auditor has flagged a finding. Not a catastrophic one like fraud or missing funds — just a reconciliation discrepancy in the monthly bank reconciliation. A few transactions weren’t matched to their sequential receipt numbers in the required timeframe, or a General Ledger allocation was off by a rounding error that originated in FARE. These things happen when staff reconcile payments by hand across disconnected systems.
But “the kind of thing that happens all the time” and “inconsequential” are not the same thing in Arizona court administration — not when your court’s financial compliance record is a matter of public accountability, professional standing, and, in some cases, personal legal liability. Understanding exactly what a finding costs, in concrete terms, is the first step toward making sure it doesn’t happen on your watch.
What the Triennial Independent Review Evaluates
Every Arizona court is subject to a triennial independent review conducted under Judicial Branch guidelines, assessing compliance with the Minimum Accounting Standards codified at ACJA § 1-501. The scope is comprehensive. Auditors examine daily receipting — whether every payment was receipted by the end of the next business day with a unique, sequential transaction number. They review monthly bank reconciliations to confirm receipts journals balance against disbursements journals and that discrepancies were documented and investigated. They check whether manual receipt books are reviewed at least quarterly and accounted for in sequence.
They also evaluate the accuracy of fund allocations — whether payments are distributed to the correct state and local funds — and the integrity of the audit trail behind each transaction. In courts that use non-integrated payment vendors, this is where findings cluster. When payments are recorded in an external portal and then manually entered into AJACS, the opportunity for error at each handoff creates a documentation trail auditors can follow straight to the discrepancy. The standard isn’t perfection; it’s what courts can reasonably achieve when their systems work correctly. The trouble is that manual reconciliation requires things to go right at every step, by every staff member, on every transaction — which is not a system, but hope with a spreadsheet.
What a Finding Actually Means
A finding enters the court’s compliance record. Administrative consequences can include formal reprimands, required remediation plans, and increased AOC oversight in later cycles. Funding consequences can be more immediate: certain local funding sources are tied to compliance, and a finding that questions a court’s financial management can affect its standing when applying for Judicial Collection Enhancement Fund (JCEF) allocations or Fill the Gap (FTG) grants — the very mechanisms many courts use to finance technology upgrades. Operational consequences may be the heaviest day to day: a finding requires the court to investigate the root cause, document corrective action, implement new controls, and report back — weeks of distraction for an already understaffed office, often demanding the administrator’s direct involvement.
The Personal Liability Dimension
This is the part most discussions of audit risk skip, and it shouldn’t be. Under the Arizona Judicial Branch Procurement Code, a person who purchases services contrary to the Code is personally liable for recovery of all public monies paid, plus a 20% penalty; intentional schemes to avoid procurement requirements are classified as a Class 4 felony. That language applies to procurement, but it reflects a broader culture: the people who manage public funds are personally accountable for how those funds are handled. Administrators aren’t insulated by their institutional role — in a real legal sense, they are the institution.
That creates a rational risk calculus behind every significant decision. Evaluating a new payment system, the administrator isn’t only weighing features and price; they’re asking whether a vendor that hasn’t been vetted by the state creates procurement liability, and what their accountability would be if a reconciliation error traced back to that system. For many, the historical answer has been to stay with what they know — legacy processes feel safer than unproven technology. That isn’t irrational. But there is a point at which the known risk of a manual process exceeds the unknown risk of an integrated one, and for Arizona court payment reconciliation that point has largely arrived.
This is why an AJACS integration established through the AOC matters beyond its technical benefits: the state has effectively pre-vetted the solution and the integration pathway, removing a layer of personal and institutional risk for the administrators who adopt it. Catalis has been a trusted partner to Arizona courts since 2015 through its e-filing solutions (formerly TurboCourt), and the AJACS payment integration follows that same established relationship.
What “Audit-Ready” Actually Looks Like
Audit readiness isn’t a documentation project, though documentation matters. It’s an operational state in which the systems that handle court finances produce compliance outcomes automatically: every transaction receipted, every surcharge allocated correctly, every bank reconciliation balanced without manual intervention, and every sequential number in order because the system that assigned them never had a gap. The most common findings — sequential receipt gaps, fund misallocation, reconciliation-timing failures, and FARE rounding adjustments — don’t require malfeasance, just normal human fallibility in a workflow that asks people to do work computers should do. When payments write to the case record automatically, with the correct number and allocation and a complete trail, reconciliation still happens — in the system, not on a spreadsheet. The triennial cycle is predictable; the courts that use the time before it to align payment infrastructure with their compliance obligations are the ones that come through without a finding.
The Findings Auditors See Most
It helps to name the specific findings that recur, because each traces back to a manual step. Sequential receipt-number gaps appear when manual receipt books fill in during downtime and the required quarterly review slips. Fund misallocation shows up when a lump-sum payment is split by hand and a surcharge category is missed or inverted. Reconciliation-timing failures happen when a portal report must be re-entered into AJACS before next-business-day close and a busy day gets in the way. And FARE recalculation discrepancies surface when an adjusted balance has to be traced back to the right transaction after the fact. None demands wrongdoing — only ordinary human fallibility in a process that asks people to do work a system should own.
Already thinking about the integration? Contact Michael Fodor to discuss your court’s audit readiness and transition timeline.