A structural problem, not a staffing one — and one Arizona courts can actually fix.
It starts before 8 a.m. A court clerk in a municipal courthouse pulls up two screens: the AJACS case management dashboard on one, a spreadsheet on the other. The week hasn’t officially started, but she’s already working through Friday’s payment receipts — cross-referencing transactions, checking that every dollar collected has been allocated to the right state and local funds, and recalculating the 83% Aggregated Surcharge breakout by hand. By the time she’s done, it’s closer to 10 a.m. And that’s a good Monday.
This scene plays out across Arizona’s limited and general jurisdiction courts every week. It isn’t the result of undertrained staff or poor management; it’s the predictable outcome of a payment infrastructure that was never designed to integrate with a case management system. For court administrators navigating the Arizona Code of Judicial Administration, the gap between what the system should do and what clerks actually spend their time doing has become one of the most persistent — and most avoidable — drains on court operations.
The Reconciliation Burden Is a Structural Problem, Not a Staffing One
Under ACJA § 1-501 and the Minimum Accounting Standards (MAS) that govern every court in the state, courts must maintain automated financial management systems that ensure accurate reporting of all transactions and a complete audit trail. Every payment must be receipted by the end of the next business day with a unique sequential transaction number. Month-end reconciliations must balance receipts against disbursements to the dollar. The standard is essentially perfect reconciliation, and anything less creates risk at the next triennial independent review.
The problem isn’t the standard — it’s that meeting it, under the workflow at many Arizona courts, requires an enormous amount of manual labor that adds no value and introduces real error risk. Consider the 83% Aggregated Surcharge, which must be reported differently than the amount actually receipted each day. Clerks manually break out the calculation across as many as 60 different General Ledger accounts, then map and reconcile those against a much smaller number of actual bank accounts — typically around 16. In a non-integrated payment environment there is no automated tool that performs this mapping. It’s spreadsheet work, done by hand, by trained professionals who have more important things to do.
Where the Double-Entry Problem Comes From
The root cause of most reconciliation burdens is a workflow pattern called double entry: recording a payment in one system, then manually recording it again in another. In courts that rely on payment vendors not integrated with AJACS, this is standard operating procedure. A citizen pays a fine online; the transaction records in the payment portal; then staff pull a report and manually key the data into AJACS so the case record reflects the new balance. If there is a discrepancy — a rounding issue, a misapplied surcharge, an NSF that arrived after reconciliation — the process has to be revisited by backtracking through systems that don’t share a record.
Redundant work is error-prone work. The Arizona Judicial Branch has been clear that eliminating duplicative applications and integrating systems are core IT objectives for 2026–2028. The “simplify and unify” mandate isn’t aspirational; it’s the operating philosophy the AOC has pursued for two decades. The challenge for individual courts is translating that statewide priority into a practical local change without taking on significant IT overhead or procurement risk.
What Automated Reconciliation Actually Looks Like
The alternative to the Monday-morning spreadsheet isn’t a more sophisticated spreadsheet. It’s a payment system that speaks directly to AJACS — so that when a citizen pays, the case record updates automatically, the correct funds are allocated to the correct accounts, and the transaction is logged with the sequential receipt number the MAS audit requires. No export, no re-keying, no 60-account GL breakout. Catalis Court Payments is built to do exactly this, with an AJACS integration that automates reconciliation and can reduce manual workload by more than 50%.
When reconciliation is automated at the system level, more changes than time savings. Error rates drop because the opportunity for manual data-entry mistakes is removed. Daily closeout accelerates because staff aren’t hunting for discrepancies between two systems that were never designed to talk. And the monthly reconciliation — balancing the receipts journal against the disbursements journal — becomes a verification step rather than a full manual exercise. For courts preparing for a triennial review, this matters: the most common MAS findings are rooted in documentation gaps and reconciliation discrepancies, and when every transaction is matched to a case automatically and timestamped with a sequential receipt number, the audit trail builds itself.
The Human Cost of the Status Quo
In Arizona courts, the cost of manual reconciliation isn’t just measured in staff hours — it’s measured in attention. Many clerks and administrators hold the Arizona Court Manager (ACM) or Arizona Court Executive (ACE) designation, earned through rigorous coursework in court governance and financial management. These are trained administrators spending hours each week on tasks that are, in the most straightforward sense, beneath their expertise. Every hour spent reconciling payment records by hand is an hour not spent on case support, public assistance, or the access-to-justice functions the AOC has identified as strategic priorities. With most courts operating at reduced headcount, that misallocation thins the margin for everything else.
The Path Forward Starts With the Right Integration
The move to AJACS as the mandated Case Management System for limited jurisdiction courts is part of a decades-long push toward unified, integrated court technology. The next logical step is ensuring every system that touches AJACS — including payments — is fully connected, not bolted on. For Arizona courts there is a cleaner path than most states have: a direct, state-vetted integration between the payment platform and AJACS, built specifically to address the reconciliation burden clerks have lived with for years. The Monday-morning spreadsheet doesn’t have to be a permanent feature of the workweek. The technology to retire it already exists.
The Cost Nobody Puts in the Budget
None of this appears as a line item, which is exactly why it persists. There is no invoice for the hours a Court Operations Specialist spends reconciling by hand, no purchase order for the end-of-month close that runs late, no budgeted figure for the rework a single mismatched transaction creates. The cost is paid in capacity — quietly, every week — and because it never surfaces as a number, it rarely gets challenged. Putting a real figure to it is often the first step toward change: when an administrator tallies the staff hours consumed by manual reconciliation against everything those hours could otherwise support, the case for an integrated workflow stops being theoretical and starts being budgetary.
See how automated reconciliation works within AJACS — book a 20-minute walkthrough with Michael Fodor.