The Part That Did Not Make It Into the Budget
Cloud usage is variable by nature. It spikes, it drops, and it shifts based on what agencies are doing at any given moment. Translating that variable usage into accurate, agency-specific chargebacks is a financial operations problem, and most states are still solving it with spreadsheets.
That is the Messy Middle. The infrastructure is modern. The financial back office is not.
The states we talk to fall into a few recognizable categories. Some are still in early stages, focused on getting basic visibility into what agencies are consuming before any formal billing structure is in place. Others have built manual processes that function, barely, held together by the institutional knowledge of one or two specific people. And a few are running serious chargeback volumes and have already hit the ceiling of what any manual process can sustainably handle.
What all of them share is the same underlying gap: a modern operational layer sitting on top of a legacy financial layer that was never designed for dynamic, multi-service, multi-agency consumption data.
Why the Spreadsheet Breaks
Legacy ERP systems and spreadsheets were built for fixed-cost environments. They handle a monthly software license or a flat-rate contract without any issue. They were not built to handle a situation where cloud storage costs doubled mid-month because a new application went live, or where an agency ran a large data migration that sent Azure costs spiking for two weeks.
When the billing process depends on a person manually pulling platform reports, reconciling them against agency cost centers, and submitting a summary to finance, a few things happen consistently. The process takes days every month. Errors accumulate. Agencies receive bills they cannot trace back to actual usage. And when an agency cannot understand its bill, it stops trusting the CCoE model that generated it.
In a private sector context, a billing dispute is a customer service issue. In state government, it is a political one. State CIOs answer to governors, legislators, and agency heads. Every unexplained charge is a liability. Billing transparency in this environment is not a nice-to-have feature. It is the foundation of interagency trust.
The Three Stages Most States Move Through
Based on conversations with state IT leaders at recent conferences including NASTD, CCoE billing tends to follow a recognizable progression.
The first stage is basic visibility. The goal here is simply to understand what agencies are consuming. There is no formal chargeback yet. Central IT is just trying to produce usage reports that both sides can look at together. Even this requires pulling data from multiple platforms and normalizing it into something readable, which is harder than it sounds.
The second stage is manual chargeback. States here have a process, but it lives entirely in human execution. Usage gets pulled, reconciled, and submitted to finance each month. It works until it does not. Staff turnover, volume increases, or a new platform integration can break the whole thing.
The third stage is automated cost recovery. States at this level need the financial back office to match the operational maturity of the CCoE itself. Dynamic rate application, automated journal entries, real-time budget tracking, and self-service portals that agencies can use to verify their own bills.
Most states are somewhere between stage one and stage two. The gap between stage two and stage three is not a technical gap. It is a financial infrastructure gap.
What the Automated Sub-Ledger Looks Like
The transition to automated cost recovery does not require replacing your ERP or rebuilding your operational platforms. It requires a financial sub-ledger: a layer that sits between your cloud environments and your ERP and handles the translation.
That is exactly what SOFTRAX + BluLogix built.
The SOFTRAX + BluLogix platform ingests consumption data from AWS, Azure, ServiceNow, and other platforms. It applies your rate logic, routes charges to the correct cost centers, produces GASB-compliant journal entries, and delivers agency-facing billing statements that are fully traceable down to the individual user and service.
The result is a CCoE that can scale without adding headcount to the billing function, close month-end consistently and on time, give agencies the transparency they need to trust the process, and absorb new service types including AI workloads without rebuilding the billing model from scratch.
For states in early stages, the platform starts with billing transparency and showback before any formal chargeback structure is in place. For states ready to move to full cost recovery, that transition is a configuration change, not a re-implementation.
The Spreadsheet Got You Here. It Will Not Get You There.
The CCoE model is the right model for state IT. But it cannot reach its full potential if the financial operations layer stays manual. The states that automate their billing infrastructure now will be the ones that scale confidently, maintain agency trust, and position themselves to handle the next wave of complexity, including the AI token costs that are already beginning to arrive.
The Messy Middle has a clean way out.
David Mink will be at the NASCIO Midyear Conference in Philadelphia, April 26-29.
If this challenge sounds familiar, let’s connect there to discuss strategies for automating this process and bringing true billing transparency to your agencies.
