IT chargeback and cost allocation between agency departments

Reference article · 5 min read

Every internal IT organization is paid for somehow: by a general fund appropriation, by a share pushed out through a jurisdiction-wide cost allocation plan, by an internal service fund billing published rates, by direct charges for items such as devices and phone lines, or by a mix. The mix is rarely designed. It accumulates one budget cycle at a time, and most IT directors inherit it.

The funding model is not a bookkeeping detail. It decides whether a department sees the cost of what it asks for, whether grant-funded and enterprise-funded programs pay a share of shared infrastructure, and how much of the year staff spend defending a rate instead of running services. It also decides which arguments you will have, because each model produces a predictable dispute.

Four ways an internal IT organization gets paid

• General fund support. IT receives its own appropriation and serves departments at no visible cost to them. No billing machinery, no rate to defend, no revenue from enterprise funds or grant-funded programs, and no price signal to restrain demand.
• Cost allocation plan. Central costs are spread to departments after the fact on a basis such as headcount, device count, or transaction volume, usually as one line in a wider central service plan covering payroll, purchasing, and facilities. It is the common route for recovering central costs from federal awards and from funds outside the general fund.
• Internal service fund with published rates. IT operates as a proprietary fund that sets rates before the year begins, bills through the year, and recovers its cost over time. Departments budget a known line, and the fund can hold working capital and replacement reserves, which makes multi-year refresh planning possible.
• Direct chargeback. Countable services billed at unit rates: a managed laptop, a mailbox, a phone line, a terabyte of storage, an hour of development. Usually layered on one of the models above.

What each model encourages

General fund support encourages requests. With nothing to pay, no department returns an unused device or retires a legacy application, and IT rations by queue and by relationship. Allocation plans move attention to the driver rather than to consumption: if the basis is headcount, a light user subsidizes a heavy one, and the argument becomes about the count. Internal service funds encourage planning, and push IT to define services precisely enough to price them. Direct chargeback encourages real economizing, and avoidance: a department that can buy a cloud subscription from its own budget will when the internal charge is higher or slower.

Behavior follows the meter: charge for idle devices, legacy hosting, and oversized storage, not for security tooling or help desk contacts.

Building a rate that holds up

• Start from full cost. Salaries and benefits, contracts, software, replacement funding, facilities and power, and a share of IT administration. A rate built on visible operating cost alone creates a deficit finance discovers later.
• Pick a driver departments can see and influence. Device counts, named users, and mailboxes work. Drivers that move for reasons outside a department's control produce unwinnable arguments.
• Settle surplus and deficit in advance. Put a working capital target and a carry-forward rule in policy, and apply them consistently.
• Keep the schedule short and stable. A few well-defined charges are easier to defend than dozens of precise ones, and changing method and rate level in the same year makes each impossible to evaluate.

Federal cost principles and audit exposure

If any department you bill spends federal award funds, your rates reach federally funded programs and fall under federal cost principles, generally the Uniform Guidance at 2 CFR Part 200. The recurring themes: billed services rest on actual allowable cost, rates recover no more than cost over a reasonable period, surpluses and deficits are carried forward and adjusted rather than kept, and unallowable costs are excluded. Jurisdictions commonly prepare a central service cost allocation plan, and some submit it to a federal cognizant agency. Requirements change, so confirm current expectations with your cognizant agency, your auditor, and counsel.

The disputes each model creates

• General fund. The fight is about priority: whose project gets the scarce engineer. Published intake and a governance body with department representation move that out of hallway negotiation.
• Allocation plan. The fight is about the basis. Publish the driver data and let departments correct their counts before the plan closes.
• Internal service fund. The fight is about the rate level and the fund balance. An annual review reconciling last year's rate to actual results answers most of it, and a large surplus draws auditor questions too.
• Direct chargeback. The fight is about the count, not the price. Give each department a monthly inventory it can reconcile, a documented way to add and remove items, and a dispute deadline.
• Shared infrastructure. Network core, identity, and cybersecurity rarely survive as metered services. A flat base charge is easier to sustain than a per-unit price nobody wants to be the one paying.

How to start

1. Cost out what you spend by service for a full year, then decide what is metered and what belongs in a base charge.
2. Model every department's bill under the proposed rates, and build a phase-in where a charge moves sharply.
3. Publish the method and the rate together, and brief finance and department budget staff before the budget hearing.
4. Put the dispute path and the rate change path in writing.
5. When buying the underlying systems, require exportable per-department usage and license assignment reporting in the contract. Counts you cannot pull from a vendor's console are counts you cannot bill or defend.

HQT provides technology advisory and systems engineering support to state and local agencies, including IT service definition, cost modeling, and supporting reporting.

Frequently asked questions