General Ledger Mapping
What is General Ledger Mapping?
General ledger mapping is the process of assigning ledger accounts and cost centers to categories in a cost model, such as TBM cost pools. It turns raw accounting data into usable cost views.
Updated November 2026 · 5 min read
General ledger mapping is the process of translating accounting data into the categories a business needs for analysis. The general ledger records transactions by account and cost center, which suits financial reporting but rarely matches the way technology leaders think about costs. Mapping assigns each combination of account and cost center to a category that is meaningful for management, such as a cost pool, a technology tower or a budget line.
In Technology Business Management, general ledger mapping is the first and most important step in building a cost model. It determines how every dollar of technology spending enters the model. If the mapping is accurate and complete, every later report inherits that accuracy. If it is not, errors carry through to unit costs, bills of IT and chargebacks, and business leaders lose confidence in the numbers.
Definition of General Ledger Mapping
General ledger mapping is a set of rules that assign ledger data to categories in a target model. Each rule identifies a set of transactions, usually by account, cost center or both, and specifies the category they belong to. Some rules also use vendor names, projects or other ledger attributes for greater precision.
The target model varies by purpose. For TBM, the target is typically the cost pools and sub-pools of the TBM Taxonomy. For budgeting, it might be a set of budget categories. For management reporting, it might be services, products or initiatives.
Account-Based and Cost Center-Based Rules
Account-based rules use the chart of accounts to categorize spending by type. A software maintenance account maps to a software maintenance cost pool, and a telecommunications account maps to telecom. These rules work well when the chart of accounts has clear, specific technology accounts.
Cost center-based rules use the cost center to add context. Salaries recorded against the storage team's cost center might map to internal labor in the storage tower, while salaries recorded against the service desk map to end-user services. Combining account and cost center rules gives a far more precise result than either alone.
Rules are usually applied in order of precedence. A specific rule, such as one for a particular vendor within an account, is checked first, and a general rule for the account applies only when no specific rule matches. Keeping a clear order of precedence prevents the same transaction from being mapped twice or to conflicting categories.
Mapping Versus Allocation
Mapping and allocation are related but different. Mapping assigns costs to categories based on what they are, using information already in the ledger. Allocation divides shared costs among multiple categories or consumers using a driver, such as users or storage consumed.
In a TBM model, mapping typically moves ledger data into cost pools, while cost allocation moves cost pools into towers, solutions and consumers. Good mapping reduces the need for allocation, because costs that can be assigned directly do not need to be spread using drivers.
Importance of General Ledger Mapping in IT Financial Management
Mapping is where technology cost models connect to the books. Its quality determines whether the model can be reconciled to the ledger and whether finance leaders trust it.
It also determines how much manual work IT finance teams must do each month. Clear, automated mapping rules turn a recurring manual exercise into a repeatable process.
Accuracy and Reconciliation
Because mapping starts from the general ledger, the total of all mapped categories should equal total technology spending in the ledger. Any difference indicates unmapped or double-mapped transactions, which can then be investigated and corrected.
This reconciliation is essential for credibility. Finance leaders are far more likely to accept a cost model when they can see that its totals match the official financial records, and that every dollar can be traced back to a ledger entry.
Consistency Over Time
Documented mapping rules ensure that the same spending is categorized the same way every month. This consistency makes trends meaningful, because changes in reported costs reflect real changes in spending rather than changes in how it was classified.
Consistency also makes the model easier to maintain. When someone new joins the IT finance team, documented rules explain exactly how the model is built, rather than relying on knowledge held by one person.
How to Build General Ledger Mappings
Building mappings is a detailed but straightforward exercise. It requires close collaboration between IT finance, corporate accounting and the teams that understand what each vendor and contract provides.
Most organizations build an initial set of rules, test them against several months of data and refine them before relying on the results.
Creating the Initial Rules
The first step is listing all accounts and cost centers that contain technology spending, including those outside IT. Each is then assigned to a category, starting with the clearest cases, such as hardware maintenance or software subscription accounts.
Ambiguous accounts, such as general professional services, may need vendor-level rules. A payment to a known IT consulting firm maps to outside services, while a payment to a law firm from the same account is excluded. These rules capture technology spending that the chart of accounts does not separate.
Testing and Maintaining the Rules
Rules should be tested by mapping several months of historical data and reconciling the results to the ledger. Unmapped transactions, mapping errors and unexpected results are reviewed and the rules adjusted.
Once in use, rules need maintenance. New accounts, cost centers and vendors appear regularly, and each needs to be mapped. A monthly check that flags unmapped transactions keeps the model complete, and an annual review keeps the rules aligned with changes in the business.
Examples of General Ledger Mapping in IT Financial Management
The examples below show how mapping rules turn ledger data into useful technology cost views.
Both use illustrative figures but reflect common situations.
In each, the rules made a complicated set of accounts and cost centers easy to read, and the reconciliation step caught problems before they reached reports.
Mapping Professional Services
A company records $12 million a year in a single professional services account used by every department. A vendor-level review shows that $5 million is paid to IT consultancies and managed service providers, with the rest going to legal, audit and marketing agencies.
The IT finance team creates mapping rules for each technology vendor, assigning their payments to the outside services cost pool. Technology consulting spending, previously invisible in the ledger, now appears clearly in every TBM report.
Catching a New Cost Center
During its monthly reconciliation, a TBM office finds that mapped technology spending is $180,000 lower than the ledger total. The difference comes from a new cost center created for a data platform team, which was not yet covered by any mapping rule.
The team adds a rule mapping the new cost center to the appropriate cost pools and adds an automated alert for any cost center with technology spending that has no mapping. Future gaps are caught within days rather than discovered months later.
Conclusion
General ledger mapping assigns accounts, cost centers and other ledger data to the categories of a cost or reporting model. In Technology Business Management, it is the first step in building a cost model and the link between that model and the official books.
Accurate, documented and well-maintained mapping rules make technology cost models reconcilable, consistent and efficient to run. Investing in them early saves time every month and builds the trust that every later report depends on.
Related terms
TBM Taxonomy
The TBM Taxonomy is the TBM Council's standard model for classifying technology costs. It organizes spending into cost pools, resource towers, solutions and consumers so costs can be compared and traced.
Chart of Accounts
A chart of accounts is the structured list of all accounts an organization uses to record financial transactions in its general ledger. It defines how spending, revenue, assets and liabilities are categorized.
Cost Center
A cost center is a department or unit that incurs costs but does not directly generate revenue, such as IT or HR. It is used to assign budgets, track spending and hold managers accountable.
Cost Allocation
Cost allocation is the process of assigning shared costs to the products, services, departments or customers that use them. It shows the full cost of each and supports pricing, budgeting and chargeback.