An internal service fund (ISF) is a government accounting structure in which fleet operates as a self-sustaining internal organization, charging user departments for every service and asset it provides. Rather than absorbing all fleet costs into a centralized budget, each department pays for the vehicles, maintenance, fuel, and administration that supports their operations. This model creates cost visibility and accountability that general fund budgeting cannot replicate, and it is the structure most commonly found in government fleet organizations that manage costs effectively.
Government fleet managers who struggle to get replacement funding, justify staffing levels, or make the case for operational improvements often describe the same problem: leadership does not understand what fleet actually costs.
The frustrating truth is that leadership often does not understand because the data they are seeing does not show it.
Fleet costs that live in a centralized general fund are largely invisible to the departments that generate them. Security's patrol vehicles are maintained, fueled, and eventually replaced by fleet, but security sees none of that cost in their own budget. Public works' heavy equipment racks up significant maintenance expense, but public works has no direct financial exposure to that expense. The result is a system where the people making decisions about how vehicles are used, how hard they are run, and whether they should be replaced have very little financial incentive to care.
Fleet becomes a service that feels free to everyone except the people responsible for running it.
This is not a new observation. According to Government Fleet and fleet consulting firm Mercury Associates, the most cost-effective government fleet organizations are typically structured as internal service funds, because those structures force the connection between cost generation and cost accountability.
As Marc Canton, VP of Fleet Strategy at RTA Fleet, described at GFX 2026: "The overall cost for that vehicle should get charged back to security. Because it's a security cost. They need that truck to get their work done. That's not my job. That's your job."
The behavioral shift that happens when departments are charged for their fleet costs is immediate and significant.
Departments that previously submitted vehicle requests without much scrutiny start asking whether they actually need all the vehicles they are assigned. Supervisors who have never thought about oil change intervals start asking how to extend them. Leadership that ignored replacement proposals suddenly wants to understand why maintenance costs on a particular asset are climbing.
None of this is because fleet managers get better at making the case. It is because the case is now visible in the financial data that department heads review every month.
As Marc Canton put it at GFX 2026: "I didn't pay for it, so I don't got to worry about it. But if they start paying for it, they start really looking at it. Then all of a sudden they care very differently."
Jeffrey Dickman, Equipment Shop Supervisor at the Arizona Department of Corrections' Yuma Complex, described attempting to move his operation toward exactly this model, and finding that even without formal ISF accounting, tracking and presenting chargeback-equivalent data inside Fleet360 was beginning to shift the conversations he was having with administrators.
RTA Fleet's analysis of chargeback system implementation notes that fleet managers who present cost data at the department level, even informally, consistently report stronger engagement from department heads on fleet-related decisions, including maintenance compliance, vehicle care, and replacement timing.
An internal service fund is a specific government accounting structure in which a service department, fleet, IT, facilities, operates on a cost-recovery basis. Revenues come from charges to user departments. Expenses are the actual costs of providing services. At year end, the fund should be at or near breakeven.
The Government Finance Officers Association provides guidance on internal service fund rate development, including the principle that rates should fully recover all direct and indirect costs — meaning parts at true cost including overhead markup, labor at fully burdened rates including benefits and supervision, and administrative costs allocated appropriately.
In a fleet ISF, charges to user departments typically include:
A monthly fixed charge per assigned vehicle covering depreciation, insurance, registration, and fleet administration overhead.
Variable charges per transaction covering fuel, maintenance labor, parts at marked-up cost, and sublet repairs.
Replacement reserves collected per vehicle per month, accumulated to fund future capital purchases without requiring a separate one-time budget request.
This last element, the replacement reserve, is one of the most powerful features of the ISF model for government fleet. Rather than going to leadership every three to five years to request capital funding for vehicle replacements, the fleet accumulates those funds continuously from departmental charges. Replacement becomes a financial process rather than a political one.
The alternative to the ISF model is typically a fleet that runs off a general fund allocation, a fixed budget that may or may not reflect actual operational costs, managed by people who have no direct view into what those costs are generated by or why.
The practical result, over time, is a fleet that is perpetually under-resourced for replacement, perpetually fighting for maintenance budget, and perpetually struggling to make the economic case for investing in newer, safer, more efficient assets.
Jeffrey Dickman's technician at the Yuma Complex described this feeling memorably in the Fleet Success Show conversation: "This could be the Titanic, and we're just trying to put bubble gum on the hole."
The maintenance cost of keeping aging vehicles in service rises non-linearly as those vehicles age. A vehicle held several years past its optimal replacement point is not just consuming more maintenance dollars — it is consuming more technician time, creating more downtime for the departments that depend on it, and in many cases operating with outdated safety technology that increases liability exposure.
The ISF model breaks that cycle by ensuring replacement costs are funded continuously rather than deferred until a crisis.
For fleet managers in organizations that are not ready to formally establish an internal service fund, the most practical first step is to build the reporting infrastructure that makes the ISF model visible without changing the accounting structure.
Fleet management software can capture the same data that an ISF would charge out, parts at marked-up cost, labor at burdened rates, fuel, and administrative overhead, and present that data organized by user department. This creates a "shadow chargeback" report: what each department would have been charged if a formal ISF were in place.
Presenting this data to leadership regularly, this is what security's fleet cost the organization this year, not fleet's budget, security's operational cost, begins to shift the conversation from fleet expense to operational accountability.
As Marc Canton advised Jeffrey Dickman at GFX 2026: "Whether or not they do it in reality on budget, it's going to show. This is how much we spent maintaining this vehicle and that vehicle. It takes somebody like you to present that to them and say, okay, you need to come here and sit down. This is what I'm going to show you."
The goal is not to win a single meeting. It is to build, over time, a track record of credible, transparent, complete cost reporting that makes the case for structural change on its own terms.
For fleet managers ready to move toward ISF-style cost visibility:
Review whether your parts costs include an overhead markup. Calculate the markup that would reflect true parts management cost, typically 10 to 20 percent of parts base cost depending on the operation.
Verify that labor rates in your work order system reflect fully burdened cost, including benefits, supervision, and facility allocation, not just base wages.
Build a report in your fleet management system that presents maintenance and operating costs by user department rather than by fleet as a whole.
Calculate what a monthly fixed charge per assigned vehicle would look like for each department, including a depreciation and replacement reserve component.
Present this data to leadership as "what each department's fleet actually cost the organization this year," even if the accounting structure does not yet reflect it formally.
Document the pattern over time. Show the trend in total cost per department. Show individual vehicles whose annual maintenance cost is approaching or exceeding replacement cost.
The data will eventually make the argument. The fleet manager's job is to make sure the data is complete, accurate, and presented consistently enough that it cannot be ignored.
RTA Fleet's Fleet360 is designed to help public fleet managers capture, track, and present the complete cost picture that makes ISF-style reporting possible. To learn more, connect with a fleet expert today.
This article was inspired by a recent episode of our podcast. Check out the full episode for even more tips and tricks: