"How much does IT actually cost?" Most organizations can answer this at the budget level — total salary, total software licenses, total hardware purchases. What they can't answer is the cost per service, per asset type, or per department. GLPI can, if you connect the right data.
What GLPI tracks financially
GLPI's financial management isn't an ERP — it doesn't handle invoicing or accounting. What it does is link costs to the assets and contracts that generate them:
- Purchase cost — stored per asset at the time of acquisition
- Contract cost — recurring costs tied to support contracts, SaaS subscriptions, or maintenance agreements
- Depreciation — GLPI calculates book value based on purchase date, cost, and depreciation period
- TCO (Total Cost of Ownership) — sum of purchase price, contracts, and associated costs per asset or group of assets
Connecting costs to services
The value of financial tracking in GLPI comes from linking costs to the things your organization cares about — not individual assets, but the services they support.
By department/entity
Every asset in GLPI belongs to an entity and can be assigned to a user or group. Aggregate the cost of assets assigned to the Finance department and you get Finance's IT cost. Do it for every department and you have a cost allocation model — not from spreadsheets, but from actual CMDB data.
By contract
GLPI's contract module tracks vendor agreements with start/end dates, renewal periods, and costs. Link contracts to the assets they cover. When a support contract comes up for renewal, you can see exactly which assets it covers and whether the cost is justified by the asset count and ticket history.
By ticket category
This is less direct but powerful: if you know the average time to resolve a ticket in a given category and the cost per agent hour, you can estimate the support cost per category. Categories with high volume and high resolution time are where money is being spent — and where automation or process improvement has the biggest financial impact.
Budget planning from GLPI data
At budget time, GLPI gives you:
- Hardware refresh forecast — assets reaching end-of-life in the next 12 months, sorted by replacement cost
- Contract renewals — which contracts expire when and at what cost
- License gaps — where you're over-licensed (wasting money) or under-licensed (audit risk)
- Growth projection — if headcount grows 15%, how many new devices, licenses, and support contracts are needed
None of this requires a BI tool — GLPI's built-in reports can produce asset-by-status lists, contract expiration summaries, and cost-by-entity breakdowns. For more sophisticated analysis, export to CSV or connect Metabase.
Common gaps
- Costs not entered — the most common problem. If assets are imported without purchase cost, none of the financial features work. Make cost entry part of the asset onboarding process.
- Contracts not linked — a contract exists in GLPI but isn't linked to the assets it covers. At renewal time, nobody knows what it's actually for.
- Depreciation not configured — GLPI supports linear depreciation, but it needs to be enabled and the depreciation period set per asset type.
Financial visibility in GLPI is opt-in. The data model supports it, but only if someone enters the numbers and maintains the links. Start with purchase cost on new assets and contract linking — that alone gives you more cost visibility than most IT organizations have.