2026 Changelog

Workforce Planning

We’ve introduced Workforce Planning in Yarken — a powerful new capability that enables you to plan headcount and automatically translate those plans into fully aligned financial budgets and forecasts.

What’s new

Workforce Planning extends your existing Budget and Forecast process by providing a purpose-built experience for managing workforce costs—typically the largest component of IT spend.

With Workforce Planning, you can:

Plan headcount by role

• Define roles with standardized compensation rates

• Plan employee or vendor headcount across months

• Map workforce plans to cost centers, entities, and accounts

• Support both full-time and flexible allocations

  

Align workforce with your organization

• Distribute costs across multiple financial accounts using configurable rules

  

Automatically generate financial budgets

• Convert headcount into account-level budget entries in real time

• Eliminate manual calculations and spreadsheet-based tracking

• Ensure financial accuracy and consistency across all plans

  

Integrated with Budget & Forecast workflows

• Workforce Planning is fully embedded within your existing planning process

• Submit, review, and approve workforce plans using the same workflow

• Ensure headcount and financial impact are validated together

Copy a Model

You can now copy model data directly within the Yarken Designer.

• Copy data from another model and year into the currently selected model (same type)

• If the target model already contains data, it will be overwritten during the copy process

Multi-model publishing for cloud spend and planning data

Cloud spend and Budget/Forecast publishing now support instead of a single destination.

• You can select the model when publishing cloud spend or Budget/Forecast data

  

• For cloud spend, a default Spend model is preselected for faster publishing. The model also supports unpublish behavior, allowing you to remove cloud spend data by unpublishing it from a specific model.

  

Ask Yarken enhancements

Stop response option added in Ask Yarken

Ask Yarken now supports stopping an active response while it is generating or querying data. You can cancel an in-progress response when needed, giving them more control during longer queries or analysis requests.

Organization context setting

Ask Yarken now supports an Organization context setting to provide additional business context for responses.

• Define company-wide goals, processes, or policies (e.g., cost reduction targets)

• Context is applied automatically to improve the relevance and accuracy of responses

• Helps align AI outputs with organizational objectives

• Supports up to 500 characters of contextual input

Search lookup

Ask Yarken now includes Search lookup, a tool that helps identify entities when a user’s question contains an unclear or ambiguous term.

Search lookup can search across dimensions such as vendors, applications, cost centers, accounts, and consumers to find relevant matches in the system.

When multiple matches are found, Ask Yarken can either:

• Ask the user to clarify the intended result

• Make a judgment call automatically

This behavior is configurable from the Search lookup: Ambiguous matches setting.

For example, if ServiceNow exists as both a vendor and an application, Ask Yarken can prompt the user to choose whether they want vendor spend, application spend, or both.

Standardized display format for code and ID

Updated the Designer UI to consistently show Code/ID and Name together as <code>|<name> across Master Data, Assets, Cost Pools, Towers, Solutions, and Consumers. This standardization applies throughout all screens/views, as well as filters (dropdowns/search) and rule creation/selection options.

Asset Mapping – Copy From / Copy To

The Asset Mapping is included with new Copy Asset Mapping From and Copy Asset Mapping To options to reuse configurations across months instead of manually recreating them.

Solution Offering portion validation

Validation has been added for Solution Offering portion values during upload. For each Asset Type + Asset ID, the total portion across solution offerings must equal 1. If the total is below 100%, affected rows are flagged with a row-level error so users can correct the allocation before proceeding.

Asset mapping warnings scoped to current upload

Asset mapping warnings were incorrectly carried over from previous uploads, causing users to see warnings even when uploading valid files.

Validation logic has been updated so asset code checks are performed only against the current upload. Warnings and errors are now correctly scoped, ensuring users see messages only for issues relevant to the file being processed.

New P&L Report (Account-based)

We have introduced a new P&L Report (Account-based) to enhance visibility into account-level financial performance across Actuals, Budget, Forecast, MTD, and YTD.

The report leverages the account hierarchy (Level 1 and Level 2) to present both detailed and aggregated views, and includes key metrics such as Total Operating Expense, Addbacks, and EBITDA, with EBITDA driven by Companion Metrics configuration.

Model export and import

You can now export and import model data to support backup, migration, and replication across environments.

• Export model data for a selected year as a ZIP file containing CSVs for Cost Pools, Towers, Solutions, and Consumers

• Export includes model data, rules, and mappings (upload rules are not included)

• Import ZIP files to create or replicate model data for a selected model and year

• For successful replication, ensure master data and asset data match the source model

• Importing data overwrites existing data for the selected model and year

Journal ID constraint updated

We have removed the unique database constraint on Journal ID to provide more flexibility in handling journal data.

• Multiple records can now reference the same Journal ID, supporting scenarios where a single journal entry spans multiple line items or allocations

• Ensures smoother data ingestion without validation failures due to duplicate journal references

Download asset mappings

You can now download all asset mappings—including both file-uploaded and manually created mappings—from the ellipsis menu.

Export Audit Logs

We have enabled export of the Audit Logs with support for exporting up to 1000 records per file, allowing you to retrieve and analyze larger activity histories.

Background processes corrected

Background process tracking has been corrected to accurately reflect running and completed statuses across operations such as Tower Rules copying and other related processes.

Processes now remain in a running state until fully completed, and the process list displays the correct status and timing, improving visibility and reliability of long-running operations.

Asset rule copy and upload performance improved

We optimized asset rule copying and asset uploading to reduce processing time during bulk uploads.

Model comparison in Analytics

We have included the ability to compare multiple models in Analytics and Custom Dashboards.

• You can now compare the default model with additional custom models within Spend cube.

• When custom models are defined, dynamic measures are automatically created in Analytics, enabling seamless comparison alongside existing default model metrics.

Asset rule - extended filter conditions in “By Spend” split type

When creating asset rules manually, the “By Spend” split type now supports extended filter conditions across all asset types. Previously, filter conditions could only be applied to the selected target asset. This update enables more flexible allocation by allowing additional conditions across all relevant asset types.

Enable or disable AI features globally

Admin users can now enable or disable Ask Yarken and Copilot across the application from AI Settings, providing centralized control over AI functionality when needed.

Custom dashboard - widget and dashboard filter issue

Resolved an issue where combining widget-level filters with dashboard-level filters could cause charts to load inconsistent results in custom dashboards. Filters are now applied correctly across both widget and dashboard levels.

Model management

We’ve introduced model management capabilities that allows you to better organize and configure new models

• Create additional custom models of type Spend, Budget, and Forecast as needed.

• Delete user-created models when no longer required.

• The three default system models—Spend, Budget, and Forecast—are always available and cannot be modified or deleted.

Copy rules and mapping across the models

You can now copy mappings and rules—including Cost Pool, Tower, Asset, Solution Offering, and Consumer rules—between models. This capability is also supported through the Copy To functionality, enabling easier reuse of configurations across models.

Model filter in Cost Explorer

Cost Explorer now includes a Model filter, allowing you to view data by selected model. The filter defaults to the Spend model.

Model configuration and navigation improvements

• Lookup Types moved outside model and year. They are now managed independently of model and year, simplifying configuration and ensuring consistent usage across all models and time periods.

  

• Upload rules are now independent of models; however, you can optionally specify a Model in the filters for more precise rule application.

  

• Naming for Spend has been standardized across Designer, with “Expenses” now used as the common term for model elements, while metrics in Analytics continue to be labeled as Spend, Budget, and Forecast.

  

Consumer Spend cube

The Consumer Spend cube now includes additional fields to support budget and forecast analysis:

• Consumer Budget

• Consumer Forecast

• Budget Variance

• Forecast Variance

Chargeback report visibility and improvement

Resolved issues affecting Chargeback report visibility and added safeguards to protect the chargeback definition.

• The default Chargeback report now appears in Settings → Chargeback even when no custom reports are configured, ensuring the chargeback view is always available.

• Newly created Chargeback reports from Analytics are now visible immediately in Settings → Chargeback after creation.

Additional safeguards:

• The default chargeback definition report cannot be deleted from Saved Reports in Analytics.

• If a user attempts to delete the report configured as the chargeback definition, a popup message prevents the action.

• Mandatory columns (Consumer ID, Solution Offering ID, and Consumer Spend) in the chargeback definition report cannot be removed.

  

Relative date filters corrected in custom dashboards

Relative date and month filters (such as current month and current year) in custom dashboards now recalculate based on the current system date.

This ensures dashboards always display the most recent and accurate data, instead of relying on the date when the dashboard was created or last saved.

Spend flow display corrected in Designer model chart

Fixed an issue in the Yarken Designer Spend Model view where the spend flow from Cost Pools to Towers displayed $0 values in the cost pool flow indicators, even when the downstream spend was correctly allocated to towers.

The visualization has been corrected so that the spend between cost pools and towers now accurately reflects the allocated amounts.

Node limit for Sankey charts in custom dashboards

Resolved an issue where Sankey charts in custom dashboards were truncated when too many nodes were present.

A new Node Limit option has been added to control the number of nodes displayed. Nodes exceeding the configured limit are now grouped under Others, ensuring the chart remains readable and fully rendered.

Financial models in Yarken

Yarken now supports a new Models concept to structure financial planning and analysis data.

Models act as reusable structures that organize Spend, Budget, and Forecast data. Default models are available out of the box, allowing teams to begin working immediately.

What’s included

• Default models: Spend, Budget, and Forecast.

• Models can be applied across:

  • Spend, budget, and forecast

  • Rules and mappings (including Upload Rules and Lookups)

    

• In Pipelines, data mapping templates are now based on the model linked to the template.

• Years are independent of models. Users select a model, and all years remain available within it.

Publishing behavior

• Cloud Spend can be published only into the Spend model.

• Budget and Forecast data are published directly to their respective models, ensuring clear separation between planning and actuals.

Important scope note

Models do not apply to:

• Master data

• Consumption data (cloud and mobile)

• Assets

• License usage (tenant, individual, product)

• Accounts payable

• Companion metrics

Data in these areas remains shared.

Why this matters

The new model structure enables:

• Loading actuals and budgets into defined planning models

• Comparing multiple forecasts, budgets, and actuals

• Supporting different allocation strategies between budgets and actuals

This provides clearer separation of planning scenarios while keeping reporting flexible and consistent.

Entity support in Planning, Business Case and Ask Yarken

Entity-level support in budgets and forecast

Budgets and forecasts now support entity-level management, allowing different planning cadences per entity.

Budget updates

• Entity is stored on each budget line item.

  

• Budget access respects entity-level permissions.

• The Budget overview page includes a global Entity filter.

• CT loads and file uploads respect the user’s entity access.

• When a budget is pushed as Baseline, it replaces the existing budget for that entity.

Forecast updates

• Forecasts follow the same per-entity model as budgets.

  

• When a forecast is pushed for an entity, it replaces the existing forecast for that entity.

This update improves visibility, control, and alignment between planning and entity-based reporting.

Business Cases now support entity at the line level

Business Cases are now entity-aware at the line level, improving alignment with multi-entity reporting.

• You can assign an Entity to each Business Case line item (cloud and non-cloud), for both manual entry and file-uploaded line estimates.

• The global Entity filter is respected in Business Case views.

• Actuals and estimates are now matched by Entity, ensuring more accurate comparisons between Business Cases and actual spend.

Ask Yarken - Entity-level responses

Ask Yarken now fully respects entity-level access controls. When users have permissions across multiple entities, responses and data visibility are constrained to only the entities they are authorized to access, ensuring consistent permissions and accurate reporting behavior.

Modify uploaded spend records

You can now update uploaded spend line items (GL entries only) directly within the application.

• Edit key fields such as spend, SKU, Towers, and other supported attributes.

  

• Changes are applied on top of data processed through upload rules.

• Once a line item is edited, it is de-linked from the original uploaded file. If the original file is later reloaded or deleted, the modified spend records remain unaffected.

  

• Edits respect locked months (including post-chargeback periods).

• Updates trigger downstream rules for the affected spend records.

• Budget/forecast or cloud spend published to CT cannot be edited or deleted.

This enhancement provides greater flexibility to correct or refine spend data without requiring file re-uploads.

Improved cube refresh experience

The cube refresh experience has been enhanced to provide greater visibility and control over partition-level processing.

• Cubes that contain partitions are now clickable, allowing users to drill down and view detailed information for each partition.

  

• Partition-level pending status is now visible. When data changes occur, affected partitions move into a Pending state.

  

• From the partition view, users can refresh individual partitions or refresh all partitions within the cube.

• The Refresh action in the cube view refreshes all partitions (both pending and previously refreshed) to ensure the cube is fully up to date.

• A new Refresh Pending Partitions button allows users to refresh all cubes and their pending partitions in one action, streamlining bulk updates across the application.

Rule Summary column added to rule exports

When exporting Cost Pool, Tower, Asset, and Solution Offering rules to CSV, a new Rule Summary column is now included. This column provides a human-readable representation of the rule JSON for easier review and validation.

Validation added for missing master data in mappings

We’ve introduced validation when loading consumer, solution, or asset mappings to prevent missing master data from being silently ignored.

• If a mapping references a consumer, solution, or asset that does not exist in master data:

• An warning message is shown in notification.

  

• The entry is marked as “Not found”, with a hover message indicating the ID is not available in master data.

  

• Rows with missing identifiers are automatically sorted to the top for easier review.

Once the missing identifier is added to master data and the mapping is refreshed, the “Not found” indicator is removed automatically.

Updates to Towers, Solutions, and Consumers rule views

We’ve updated the rule configuration experience across Towers, Solutions, and Consumers for better clarity and consistency.

Towers

• Unassigned spend is now clearly labeled as Unallocated Cost Pool Spend.

• Tabs have been rearranged for a more consistent experience.

Solutions

• The rule creation experience has been refined with two default manual strategies:

  • Mapping strategy 1: Asset Type, Asset ID (name)

  • Mapping strategy 2: Any Attribute (from asset to solution offering)

• A new Unallocated Asset Spend tab has been added.

• The Rules tab has been renamed to Solution Rules.

Consumers

• A new Unallocated Solution Spend tab has been added for improved visibility into unmapped spend.

Additional columns in Finance Overview tabular view

The Finance Overview tabular view now includes four additional columns: Month, Cost Center, Account, and Vendor. These fields are now queried to display granular data in the table. The same columns are also available in drill-down reports and GL popups.

Fix for grand total for pivot table rows

The row grand total is now enabled for pivot tables in both custom dashboards and analytics.

Calendar date range fixed in Cloud Consumption cube

Fixed an issue in the Cloud Consumption cube where calendar date ranges returned data only for the start date. The underlying function has been updated to include both the start and end date year and month IDs, ensuring data is fetched correctly for the full selected date range.

Multi-Entity support now available in Yarken

Yarken now supports multi-entity structures across the platform, allowing organizations to manage and report spend by region, business unit, or legal entity—all within a single Yarken instance.

This enables clearer ownership, cleaner reporting, and more precise access control across financial and cloud spend.

What’s included

Default entity (automatic)

• Every environment now includes a built-in Default entity.

• All existing data, including users, maps automatically to the Default entity, ensuring uninterrupted reporting.

Entity setup in Settings

• Entities can now be configured in Settings.

• Each entity supports:

  • Entity Code and Entity Name (required)

  • Region, country, owner, and description (optional)

• The Default entity cannot be removed, but it can be renamed and updated.

Entity-based access control

• Entity visibility is now permission-aware:

  • Admins automatically have access to all entities.

  • Non-admin users must be assigned access to one or more entities through Admin → User Management → Entity Access.

    

• If a user is not assigned access to any entity, they will see an error at login until access is granted.

Entity attribution across spend and cloud

• Spend and cloud data now support an Entity field.

• If no entity is provided, records default to the Default entity.

• For cloud consumption uploads:

  • Each upload can carry its own entity.

  • Entity can also be set or overridden using upload rules.

  • The cloud spend summary view now shows the entity.

  • Published cloud spend data include entity attribution for consistent downstream reporting.

    

Reporting and analytics filters

• A new Entity global filter is now available across the application.

  

• The filter supports multi-select, with:

  • All entities selected by default (preserving existing report behavior)

  • Consistent sorting across dropdowns and filters

  • Clear display when multiple entities are selected

• Cost Explorer now includes an Entity filter next to the month filter.

Updated branding and UI

We’ve refreshed the Yarken product experience to align with our new brand identity. This includes an updated logo across the application (including Ask Yarken), refreshed brand colors, updated loading screen visuals, and a new favicon.

Planning exchange rates added for budgets

Yarken now supports separate planning exchange rates for budgets and forecast.

This includes:

• A dedicated planning (budget) exchange rate table, separate from actual exchange rates

• Monthly exchange rates for all selected foreign currencies

• CSV import for planning exchange rates

Ask Yarken enhancements for currency and spend detail

Preferred currency support

• Ask Yarken now displays spend in the user’s preferred reporting currency, converting values from the base currency when needed.

Journal-level spend line item access

• Ask Yarken now supports deeper spend drilldowns using newly exposed journal-level dimensions, including:

  • Journal ID

  • Journal Date

  • Journal Transaction Date

  • Journal Line Description

  • Journal Project ID

  • Journal Invoice Number

This enables more granular visibility into journal-based spend data.

GPT-5.2 support and improved AI model switching

Yarken now supports GPT-5.2 as a globally selectable LLM. When the global model is set to GPT-5.2 or Claude, AI features continue to work consistently across the product, maintaining feature parity and quality regardless of which model is enabled.

Budget and forecast line items now support any currency

You can enter budget and forecast line items in any supported currency. Each budget or forecast has its own planned exchange rates.

• Budget planning rates are copied from the planned exchange rates.

• A currency selector is now available in the budget/forecast line item editor.

• Line items are stored in their original currency, and automatically converted to base currency using the configured budget planning exchange rate.

• Both values are visible:

  • Original currency + amount

  • Converted base currency amount

Refresh budget/forecast exchange rates

You can now update future planning exchange rates to support more accurate multi-year budgeting.

• Budget owners can update exchange rates for unreleased budgets and forecasts.

• In active forecasts, updated rates can be applied by selecting Update Currency Exchange Rate, which recalculates affected amounts.

• Once a budget is submitted, its planning exchange rates are locked to preserve approved figures.

Improved Tower rules sorting across pages

Tower rules sorting has been improved so selected rules can now be moved correctly between pages. Navigation arrows are enabled when needed, allowing rules to be repositioned across pages during sorting.

Unallocated consumer spend visible in Sankey charts

Fixed an issue where unallocated consumer spend was not displayed in Sankey charts across environments. Related bar charts continue to show this spend under Unknown.

Improved login matching and observability for Entra ID / OpenID

Login for customers using Entra ID or OpenID is now more resilient when identity providers return either a username or an email. During sign-in, YäRKEN now matches users by username first, then falls back to email, and automatically updates stored user details when they differ from the identity provider.

Failed login attempts are now captured with improved visibility:

• Logged in YäRKEN Audit Logs with full email details for administrators

• Logged in New Relic using obfuscated identifiers for privacy, including timestamps and clear failure reasons

Conversion-only currency option added

Foreign currencies can now be configured as conversion-only. On the Foreign Currency Selection screen, a toggle controls whether a currency is available for reporting or used only for conversion (for cloud data, budgets, and forecasts).

The toggle is enabled by default, making the currency available for reporting. Turning it off restricts the currency to conversion-only use.

Relative month filters corrected in Analytics

Fixed the behavior of timeline relative month filters to prevent incorrect results across year boundaries.

• Is current month/quarter now applies only the current period and ignores any year filter.

• Is last month/quarter now correctly reflects the previous calendar month/quarter (year is not considered).

• Is current year is no longer applied by default. Instead, only the current month is applied by default across all Analytics cubes.

Fix for budget values in Finance Overview

Fixed an issue where budget values appeared as zero in the Finance Overview transaction details view, even when budget columns were enabled.

The issue was caused by an journal ID filter in the GL popup, which was only applied to spend and not for budget, prevented valid budget data from displaying. The filter has been corrected, and budget values now appear as expected.

New asset allocation method: Split by Spend

A new By Spend split type is now available when creating manual asset rules. This option allocates asset spend proportionally based on existing allocated spend across target assets. Additional filters such as Cost Pool, Sub Cost Pool, Tower, and Sub Tower can be applied to control which spend contributes to the allocation. Changes take effect immediately.

Additional dimensions in Consumer cube

The Accounts, Cost Centers, and Vendors dimensions are now available in the Consumer cube in Analytics, enabling more detailed consumer spend analysis.

Cache Management for YäRKEN Designer

A new Cache Management capability has been introduced specifically for the YäRKEN Designer page to improve performance and responsiveness. The cache is managed internally by admin via /admin/cache. Once the cache is built, the Designer page loads quickly on subsequent access. Any data modification automatically invalidates and refreshes the cache to ensure the latest data is reflected.

Multi-currency support across YäRKEN

YäRKEN now supports end-to-end multi-currency handling, allowing teams to upload, store, analyze, and report spend in both base currency and foreign currencies with full traceability.

What’s new

User-level reporting currency

• Users can select their Reporting Currency directly from their profile.

  

• The list includes the environment base currency and currencies configured under Settings → Foreign Currency.

  

• Changing the currency re-renders all on-screen data instantly.

Exchange rate management

• Exchange rates can be configured from Admin → Settings → Currency Exchange Rate.

  

• Rates are maintained monthly by year, enabling accurate historical conversions.

• Bulk upload is supported to load multiple currency rates at once.

Spend uploads with foreign currency tracking

• Additional columns—Foreign Amount, Exchange Rate, and Foreign Currency—are added to actual spend uploads to track the original source values for spend that has already been converted using an exchange rate.

  

• The system stores both the original source currency and the converted base currency per transaction.

• Multiple currencies are supported within a single file.

• These fields are available in Analytics and as hidden-by-default columns in GL popups.

Cloud spend currency handling

• During cloud file uploads, costs are converted to base currency using the month- and year-specific exchange rate, based on the cloud charge period start date and billing currency.

• If no exchange rate is found during upload, a default rate of 1 is applied.

Analytics and dashboards

• Spend can now be analyzed using base currency or the original foreign currency, along with the applied exchange rate.

• Multi-currency values are supported across Analytics and Custom Dashboards.

Ask YäRKEN is now agentic and reasoning-driven

Ask YäRKEN has been upgraded from a workflow-based assistant to an agentic, reasoning-driven AI built for financial and IT spend analysis.

Instead of relying on fixed workflows and predefined SQL generation, Ask YäRKEN now interprets intent, evaluates context, and determines the best way to answer each question. This delivers more accurate explanations, deeper insights, and greater flexibility when working with complex financial data.

What’s new

Agentic reasoning

• Applies logical reasoning to understand intent and context before responding.

• Adapts its approach based on the question, data relationships, and prior interactions.

Deeper spend and variance analysis

• Explains why spend changes occur, not just what changed.

• Breaks down variances across cost pools, towers, vendors, and time.

• Supports cross-dimensional analysis for more complete financial insight.

Stronger domain expertise

• Improved understanding of FinOps, TBM, and IT financial management concepts.

• More accurate responses to procedural, instructional, and analytical questions.

Data visualization

• Generate column charts, line charts, pie charts, and stacked visualizations

Access-level permissions

• Respects Account- and Cost Center–level permissions. Responses generated by the agent are limited to only the data the user is authorized to access.

Improved workspace

• A new full-screen experience supports longer queries, deeper analysis, and clearer results.

SOP (Playbooks) support for Ask YäRKEN (Beta)

Standard Operating Procedures (SOPs) are now supported for Ask YäRKEN (Beta) to ensure guided and consistent AI responses. Administrators can manage SOPs from Settings > Playbooks, including instructing the model, downloading existing SOPs, and importing updates.

Global search

Global Search functionality now includes the search results for the Cost Center Owners, allowing them to find relevant records directly from the search bar. Results are scoped to the cost centers they own. Selecting a result opens the corresponding Cost Center Owners report.

Charts and mapping aligned with TBM v5.0.1

As part of the TBM v5.0.1 implementation, we updated terminology and mappings to reflect the latest TBM standards.

1. Labor charts

   • Labor charts now follow TBM v5.0.1 terminology.

   • Internal Labor and External Labor are replaced with:

     • Staffing – Internal Labor

     • Staffing – Staff Augmentation

   • The Labor and Labor Trend charts on the home page reflect these updates.

2. Cloud consumption mapping

   • Cloud consumption now uses the following structure:

     • Cost Pool: Cloud Services

     • Sub Cost Pool: Cloud Service Provider

3. Sub tower mapping

• Instead of allocating tower consumption to a generic Cloud sub-tower, the Tower and Sub-Tower assignments will now be determined based on FinOps (version 1.3) Service Category & Sub-Category.

4. Dashboards and charts filter

• All charts affected by the Cloud Sub Tower and Outside Services – Cloud Service Provider filters have been updated to reflect the TBMv5.0.1 changes.

  • Outside Services – Cloud Service Provider (v4.0) → Cloud Services - Cloud Service Provider

5. TBM 4.0 behaviour

   • Existing TBM 4.0 implementations continue to use the Cloud sub-tower with no changes.

Cloud spend publishing aligned with TBM v5.0.1

With the TBM v5.0.1 implementation, cloud spend publishing now aligns with the updated TBM taxonomy, including new Cost Pools, Sub Cost Pools, Towers, and Sub Towers.

Cloud spend publishing is driven by the TBM taxonomy version configured in the application’s default settings.

Publishing behavior by TBM version

• When the taxonomy is set to TBM v5.0.1, cloud spend is published using the v5.0.1 taxonomy structure.

• When the taxonomy is set to both TBM v4.0 and v5.0.1, cloud spend is still published using the v5.0.1 structure, including updated cost pools and towers.

• When the taxonomy is set to TBM v4.0 only, cloud spend continues to publish using the legacy TBM v4.0 taxonomy and allocation logic.

Service category derivation

The logic used to derive Cost Pool and Tower from Service Category can now also be configured using Upload Rules and Lookup files.