Who we work with
Technology partner for finance directors
HQT works with public agency finance directors on the cost, controls, and audit evidence behind systems the agency will run for a decade.
The technology line items in your budget used to behave. A server refresh landed in the capital budget every several years, a perpetual license was bought once and maintained at a predictable rate, and the number you approved in the spring was close to the number you paid. That pattern is coming apart. The same capabilities now arrive as a per-user subscription, a consumption bill that moves with usage, and an implementation cost that is quoted once and invoiced across two or three fiscal years. Your appropriation is still annual, it still lapses, and the fund balance that would absorb a surprise is committed to something else.
The accounting treatment has moved as well. Subscription-based information technology arrangements now come onto the financial statements, which means contract provisions your office never had to read, renewal options, variable payments, and termination rights, drive measurement and disclosure. Auditors ask about user access, change management, and segregation of duties in systems that IT administers and finance answers for. And when a board or council asks what a new platform will cost the agency over the next ten years, you are expected to have a number that holds up under questioning. The people proposing the system are rarely the people who will have to defend it in year six.
What makes this hard
- Vendor pricing is quoted for year one, and the escalation clause, tier change, or renewal uplift that determines years two through ten is either buried in the agreement or absent from it entirely.
- Consumption-based cloud and platform billing varies month to month while the appropriation does not, and the variance has no clear owner until it is already a budget problem.
- Subscription agreements get signed inside departments and never reach finance, so the agency cannot produce a complete list of what it is contractually committed to pay.
- Capital funding sources, including bond proceeds and capital reserves, generally cannot pay for recurring subscription costs, so a shift to software as a service pushes spending into an operating budget that has no room for it.
- Implementation is presented as a one-time cost, and then data conversion, interfaces, and configuration stretch across fiscal years and consume agency staff time that was never in anyone's estimate.
- Information technology general control findings on financial systems land on the finance office to remediate, even when the underlying work belongs to IT and the vendor.
- Grant and one-time federal funding can cover an initial purchase but not the ongoing subscription, and the cost allocation for a shared system has to be defensible to the awarding agency and to auditors for as long as the system runs.
How HQT helps
- Total cost of ownership modeling. We build a cost model across the expected service life of a system, covering subscription fees, consumption charges, implementation, integration, internal staff time, and renewal escalation, in a format your own staff can update at budget time rather than a slide you cannot edit.
- Contract and quote review in finance terms. We read the agreement and the price sheet for the provisions that actually move money: term and renewal options, escalation, user and tier definitions, overage and consumption rates, non-appropriation language, and what data extraction at exit costs.
- Subscription and application inventory. We work from accounts payable data, procurement card activity, and the application inventory to assemble one list of subscription arrangements with the contract and payment facts your accounting staff and auditors need to evaluate them.
- Cloud cost management. We structure and tag cloud accounts by fund, department, and program, set budgets and alerts, and produce showback reporting aligned to your chart of accounts and fiscal calendar so variance is visible during the year instead of after it.
- Control documentation for financial systems. We document and help implement access provisioning and removal, segregation of duties, change management, and backup and recovery evidence in the form auditors ask for, and we automate the evidence collection where it can be automated.
- Integration that supports reconciliation. We build and maintain interfaces between the financial system and departmental systems so revenue, payroll, billing, and purchasing data move without manual re-keying and reconcile on a schedule.
- Independent technical review before award. We review a proposed architecture, migration plan, or vendor estimate on the agency's behalf and report in writing what the assumptions are, which ones are load bearing, and where they are most likely to be wrong.
How work with a finance office usually starts
Finance is rarely in the room when a technology decision begins. The call tends to come at one of four moments. A department has brought forward a system request and the cost estimate does not hold up, because year one is priced and years two through ten are a placeholder. A cloud or platform bill has grown past what was appropriated and nobody can say which department, program, or workload caused the increase. An audit has produced an information technology general control finding on a financial system, and the corrective action plan needs someone who can implement the change rather than describe it. Or the accounting team is trying to identify and measure subscription arrangements for the financial statements and discovers the contracts live in a dozen departments.
The first engagement in each case is short and analytical. It means reading the agreements, price sheets, and invoices, sitting with the IT staff who actually run the system, and producing a cost model with the assumptions written down next to the numbers. The output is something you can put in a budget document, defend to a board or council, and hand to an auditor without a second translation step.
What to ask any technology partner
- Show the cost across the full service life, not the first year. Ask for subscription, consumption, implementation, integration, and support costs laid out by fiscal year, with the escalation assumption stated rather than implied.
- Name what is variable and what drives it. Consumption and per-user pricing should arrive with the unit of measure, the rate, the tier boundaries, and a plain description of what makes the number go up.
- Explain the exit. Ask what data extraction costs, in what format the data leaves, how long access continues after termination, and what happens to the integrations built along the way.
- Put non-appropriation in writing. A multi-year commitment your agency cannot terminate when funds are not appropriated is a problem long before it is a cost.
- Say who does the implementation work. Ask which tasks fall to agency staff, roughly how many hours, and from which departments, because that time is a real cost and is usually missing from the estimate.
- Describe the control evidence. For any hosted system touching financial data, ask what independent service organization control report exists, which controls the agency is expected to operate on its own, and what access and change logs your staff can pull without a support ticket.
A partner worth hiring will answer these in writing before award rather than after. HQT does this kind of work for public agencies: cost modeling over the life of a system, contract and cloud spend analysis, integration between financial and departmental systems, and the control documentation that finance and audit rely on.
Frequently asked questions
Departments buy software without telling us. How do we find every subscription we are already paying for?
Start from accounts payable history and procurement card activity rather than from the contract file, because the payments exist even when the agreements never reached finance. Match recurring vendor payments against the IT application inventory and the list of systems with active user accounts, then chase the gaps. Expect the first pass to surface renewals nobody owns and duplicate tools doing the same job in two departments. Once the list exists, the harder part is keeping it current, which usually means routing new agreements through a single review step before signature.
How should we budget for cloud costs that change every month?
Separate the spending into a committed baseline and a variable layer, then budget them differently. The baseline covers steady workloads and can often be reduced through commitment or reserved capacity pricing, while the variable layer needs tagging by fund and program, monthly alerts, and a named owner who explains movement during the year. Build the appropriation on observed usage with a documented contingency rather than on the vendor's estimate. The goal is that a variance is identified in month two, not at year end.
Does moving from purchased software to subscriptions limit which funding sources we can use?
Often yes, and this is worth confirming early with your own counsel and auditor. Capital funds, capital reserves, and bond proceeds generally have to be matched to assets with a corresponding useful life, which recurring subscription payments usually do not provide, so the cost migrates to the operating budget. Bond covenants, state law, and your capitalization policy all bear on the answer, and they vary by agency. The practical effect is that a technically sound move to software as a service can still create a funding problem nobody planned for.
What does the accounting standard on subscription arrangements require us to gather from a vendor contract?
The measurement depends on facts that live in the agreement, including the noncancellable term, any renewal or termination options and whether exercising them is reasonably certain, the fixed payments, variable payments and how they are determined, incentives, and costs incurred in the implementation stages. Collecting those facts consistently across many contracts is the work, and it is a records problem before it is an accounting problem. HQT can assemble and structure the underlying contract and invoice data, but the recognition, measurement, and disclosure conclusions belong to your accounting staff and your auditor.
Our auditors flagged user access in the financial system. Can a technology partner actually close that finding?
A partner can do the technical work behind the corrective action plan, which is usually where these findings stall. That includes reconciling accounts against current employees, connecting provisioning and deprovisioning to the human resources system so separations take effect promptly, defining roles that enforce segregation of duties, and producing access review and change logs in a form the auditor will accept. The finance office still owns the policy decisions about who should have which authority. What a partner adds is the implementation and the recurring evidence so the same finding does not return next year.