Mapping FOCUS billing data into the TBM Taxonomy, column by column

In brief

Which FOCUS columns feed which TBM Taxonomy 5.0 cost pools, towers, solutions and consumers, and how to handle amortization, commitments and untagged spend.

Steve Elliott

Steve Elliott · · 5 min read


On this page
  1. Which FOCUS columns feed which TBM layer?
  2. Should SaaS land in Cloud Services or Software & SaaS?
  3. Which cost column should carry the money?
  4. How do ServiceCategory values map to resource towers?
  5. How do the FOCUS 1.3 allocation columns handle shared costs?
  6. What should happen to untagged spend and unused commitments?
  7. What changes with FOCUS 1.4?
  8. Sources

A FOCUS billing file can be mapped into TBM Taxonomy 5.0 in four moves: the provider columns decide the cost pool, ServiceCategory and ServiceSubcategory decide the resource tower, Tags and the FOCUS 1.3 allocation columns decide the solution and consumer, and EffectiveCost carries the money. In our view, most rows then go through cleanly.

The work is in the rows that don't fit: commitment purchases, unused commitments, shared clusters and untagged spend. This guide uses FOCUS 1.3 column definitions and the TBM Council's 5.0.1 taxonomy. FOCUS 1.4, ratified in June 2026 and now the latest release, rewrites a few definitions; the last section covers them. For who owns what, see TBM vs FinOps.

Which FOCUS columns feed which TBM layer?

Column names and definitions are from FOCUS 1.3; all the columns carry over to 1.4. The routing is our view; neither steward publishes an official mapping.

FOCUS column(s)What the spec says it holdsTBM layer it feedsHow we would use it
ServiceProviderName, InvoiceIssuerName, HostProviderNameWho sells the service, who invoices it, and who hosts itCost poolRoute public cloud IaaS and PaaS to Cloud Services; route SaaS vendors to Software & SaaS
ChargeCategory, ChargeClassUsage, Purchase, Tax, Credit or Adjustment; Correction flags a change to a previously invoiced periodCost pool filterDecide which rows enter the model
BilledCostThe invoicing basis, excluding amortization of upfront purchasesGL reconciliationReconcile to invoices and the GL. FOCUS also lists cash-basis allocation; we would allocate from EffectiveCost
EffectiveCostThe cost after discounts, with eligible prepaid purchases amortizedCost pool through to consumersThe value you carry through every layer
CommitmentDiscountId, CommitmentDiscountStatusWhich commitment covered a row, and whether it was Used or UnusedCost pool and Shared/UnassignedKeep used commitment with the workload; isolate unused
ServiceCategory, ServiceSubcategoryThe service's core function, from fixed allowed valuesResource tower and sub-towerRule table, below
SubAccountId, BillingAccountIdThe account groupings the provider bills and controls access bySolution or consumerAttribute directly where an account belongs to one application or business unit
TagsUser-defined and provider-defined key-value pairs, finalized onlySolution and consumerMap solution, owner and cost center keys
AllocatedResourceId, AllocatedTags, AllocatedMethodId, AllocatedMethodDetailsHow the provider split a shared resource, and its method (new in 1.3)Solution and consumerAttribute shared clusters and databases to workloads
ContractApplied, plus the Contract Commitment datasetContract commitments applied to a charge, and contract termsNone directlyCommitment tracking and planning, not a cost feed

Should SaaS land in Cloud Services or Software & SaaS?

Usually Software & SaaS. Since FOCUS 1.2, announced in June 2025, SaaS and PaaS billing can share one schema with cloud billing. TBM 5.0.1 splits them: it defines Cloud Services as cloud services "including IaaS and PaaS," with a Cloud Service Provider sub-pool for external public cloud, and gives SaaS its own sub-pool under Software & SaaS.

FOCUS has no column that says IaaS, PaaS or SaaS. In our view, the cleanest rule is by provider: hyperscalers and data cloud providers to Cloud Services, SaaS vendors to Software & SaaS > SaaS, plus an exception list for hyperscaler services that behave like SaaS. Start with ServiceCategory "Business Applications".

Watch marketplace purchases. FOCUS 1.3 requires BilledCost to be 0 where a third party receives the payment, citing marketplace transactions; 1.4 changes this wording. Read InvoiceIssuerName and ServiceProviderName together so marketplace SaaS is counted once, in the right pool.

Which cost column should carry the money?

We would carry EffectiveCost through the model and use BilledCost to reconcile. BilledCost must match the payable amount on each invoice. EffectiveCost shows amortized cost: eligible prepaid purchases are spread across the usage they cover. For a commitment purchase meant to cover future charges, the spec sets EffectiveCost to 0 on the purchase row and requires the commitment's usage rows to add up, over the term, to what was billed for it.

Take an illustrative one-year compute commitment of $1.2 million, paid upfront in January, that is 80% used.

Row in the January fileBilledCostEffectiveCost
Purchase row for the commitment$1,200,000$0
Usage rows covered by the commitment (Used)$0$80,000
Unused portion of the commitment (Unused)$0$20,000
Total$1,200,000$100,000

The example spreads cost evenly by month.

  • Never sum both columns. Each tells the whole story on its own basis.
  • Expect a timing gap with the GL. The TBM Council notes that cloud invoices don't directly reference GL line items, and recommends reconciling against GL cloud spend. How the ledger books an upfront commitment is an accounting policy question; agree the bridge with the controller before the first close.
  • Corrections arrive late. ChargeClass "Correction" rows adjust a previously invoiced period (in 1.4, a closed one). Restate or book them currently, but consistently.

Cloud Services also has a Capital sub-pool. FOCUS has no capitalization column, so capital treatment comes from the GL and your capitalization policy, not from the billing file. Confirm treatment with your accounting advisers.

How do ServiceCategory values map to resource towers?

ServiceCategory classifies a service by its core function, from fixed allowed values, which makes a rule table for IT towers possible. ServiceSubcategory adds a second level, but it is recommended rather than required, so keep a category-level fallback. This is the table we would start from; sub-tower names are TBM 5.0.1's.

FOCUS ServiceCategory > ServiceSubcategoryTBM tower > sub-tower (our mapping)
Compute > Virtual Machines, Serverless ComputeCompute > Servers, or AI Compute where GPU families or a tag mark AI work
Compute > ContainersCompute for the nodes; Application > Container Orchestration for the control plane
Compute > End User ComputingCompute > Servers for virtual desktops; endpoint management needs a local rule (Workspace is physical devices only)
Storage > Object Storage, Block Storage, File StorageStorage > Online Storage, or AI Storage
Storage > Backup StorageStorage > Offline Storage
Databases > Relational Databases, NoSQL Databases, Data WarehousesData > Database
AI and Machine Learning > Generative AI, Machine LearningApplication > AI Models
Networking > Content Delivery, Network ConnectivityNetwork > WAN (the closest fit for CDN, not an exact one)
Networking > Network Security; SecuritySecurity > Digital Security
IdentityRisk & Compliance > Identity & Access Governance
Developer ToolsApplication > Development
IntegrationApplication > Middleware
Analytics > Data ProcessingData > Data Operations
Management and Governance > ObservabilityDelivery > Operations Center

Other categories, such as Business Applications, Web, Multicloud and Management and Governance (other than Observability), need a local rule. The AI rows need the most judgment: TBM 5.0.1 has AI sub-towers in Compute, Storage and Network as well as AI Models, so a GPU instance and a hosted model API can land in different towers.

How do the FOCUS 1.3 allocation columns handle shared costs?

They let the provider do the first split, for shared resources such as nodes in a Kubernetes cluster or a database. AllocatedResourceId names the workload that receives cost, AllocatedMethodId points to the provider's documented method, and AllocatedMethodDetails carries the ratios. Allocated rows must sum to the origin charge and keep its tags; AllocatedTags adds the workload's tags.

That gives two roll-ups. The spec's examples total EffectiveCost by ResourceId for the shared resource's cost, and by AllocatedResourceId for each recipient's share. In our view, use the first for towers and the second for solutions. Rows that carry an AllocatedMethodId but no AllocatedResourceId are the unallocated remainder; send them to a shared bucket. Some providers spread the remainder across allocated rows instead, so check the method documentation.

What should happen to untagged spend and unused commitments?

Make them visible. The TBM Council's solution guidance calls Shared/Unassigned "transparent buckets for costs/resources not yet mapped to a Solution," says not to hide it, and suggests tracking it as a KPI.

In our view, three things belong there until someone claims them: untagged usage that SubAccountId can't attribute either, unallocated split-cost remainders, and unused commitment. Unused commitment has no workload behind it. It is a purchasing outcome, so report it to whoever owns commitment decisions rather than spreading it as overhead.

The Council's tip: if more than 10% of sub-tower cost sits in Shared/Unassigned, stay with driver-based allocation until usage drivers improve.

What changes with FOCUS 1.4?

FOCUS 1.4 was ratified on June 4, 2026. Four changes touch this crosswalk:

  • BilledCost and EffectiveCost are rewritten around covering and covered charges. BilledCost must be 0 for fully covered charges and for charges from entities not responsible for invoicing; the separate marketplace rule is gone, and marketplace purchases now count as covering charges. EffectiveCost is still 0 on a purchase that covers related charges, and the sums must still match within the covering charge's period, so the worked example holds. Recheck marketplace rules first.
  • Correction now means a previously closed billing period.
  • Provider and Publisher are removed. Move any rules that read them to ServiceProviderName, HostProviderName or InvoiceIssuerName, whichever fits the case.
  • New invoice data. Invoice Detail and Billing Period datasets, plus an Invoice Reconciliation feature that joins Invoice Detail to cost and usage on Invoice ID. In our view that eases the invoice side of the GL bridge. Contract Commitment grows from 13 to 30 columns.

The foundation says FOCUS 1.5 is scoped to show AI model identity and token consumption.

We think the payoff is cloud and SaaS cost arriving in the operating model already attached to the workloads and owners behind it.

Sources

Frequently asked questions

Which FOCUS cost column should a TBM model use?

Use EffectiveCost to carry cost through cost pools, towers, solutions and consumers, because it spreads eligible prepaid commitments across the usage they cover. Use BilledCost to reconcile, since FOCUS requires it to match the payable amount on each invoice. Never add the two together. Agree with your controller how amortized cloud cost bridges to what the general ledger records.

Does SaaS billing data belong in the Cloud Services cost pool?

Usually not. TBM Taxonomy 5.0.1 defines Cloud Services as cloud services including IaaS and PaaS, and gives SaaS its own sub-pool under the Software & SaaS cost pool. FOCUS has carried SaaS data in the same schema since version 1.2, so a single feed can contain both. Route rows by provider and keep an exception list.

How should commitment discount purchases be handled in TBM?

Exclude the purchase row from the allocation view, because FOCUS sets its EffectiveCost to 0 when it covers future charges, and the amortized amount shows up on the covered usage rows. Rows marked Unused in CommitmentDiscountStatus have no workload behind them. In our view they belong in a visible shared bucket, reported to whoever owns commitment purchasing.

What do the FOCUS 1.3 allocation columns do?

They show how a provider split a shared resource, such as a Kubernetes cluster or a database, across the workloads that used it. AllocatedResourceId names the receiving workload, AllocatedMethodId and AllocatedMethodDetails describe the method and ratios, and AllocatedTags carries the workload's tags. Allocated rows must add up to the original charge.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on TBM & IT Financial Management

Cost pools, towers, showback, unit cost.