ABSA Group Wins TBM Pioneer EMEA 2026

ABSA Group Wins TBM Pioneer EMEA 2026

When the TBM Council names a TBM Pioneer, it is not recognising a vendor deployment. It is not recognising a project. It is recognising an organisation that has fundamentally changed the way it thinks about technology – one that has moved from treating IT as a cost centre to treating it as a financial discipline with the same rigour, accountability and strategic weight as any other part of the business.

This week, ABSA Group was named the TBM Pioneer EMEA 2026. For the MagicOrange team, who have worked alongside ABSA over the past several years, this award is deeply meaningful. Not because it validates a platform. Because it validates a philosophy.

What TBM Pioneer Actually Means

The TBM Pioneer Award is the TBM Council’s highest individual recognition. It is reserved for organisations driving breakthrough results through either deep penetration of TBM across their operations or advanced use cases that push well beyond traditional cost transparency. Winners are not just running TBM programmes. They are reimagining what TBM can do.

ABSA Group earned this distinction in the EMEA region by doing both: embedding TBM at an extraordinary depth across a 40,000-person, 12-country financial institution, and then extending it into an entirely new domain that no TBM programme of this scale had attempted before.

That extension – branch-level financial visibility at a transaction, job title and work centre level – is what separated the 2026 submission from everything that came before it. But to understand why it matters, you have to understand where ABSA started.

The Problem No Financial Institution Could Answer

ABSA Group is one of the largest financial institutions in EMEA. Its technology estate spans on-premise infrastructure, AWS, Azure and a portfolio of applications and services that serve operations across a dozen African countries. At the scale and complexity of an organisation like ABSA, the questions sound simple. The answers, until recently, were not.

How much does this application actually cost us?

Which of our cloud workloads are wasting money?

Can we justify decommissioning this system?

What are we spending per branch, per transaction, per job title?

These are not technical questions. They are business questions. And for years, the honest answer was: we do not know with any precision. Application owners, CIOs and CFOs were operating with partial visibility. Transfer pricing was not aligned to actual platform and service consumption. Cloud costs were journalled one way, on-premise costs another, and Azure a third way still. The result was fragmented accountability, suboptimal investment decisions and a trust gap between Finance, Technology and the Business that made every planning cycle harder than it needed to be.

ABSA’s leadership recognised that the problem was not one of intent. It was one of infrastructure – the financial infrastructure needed to connect technology spend to business outcomes. That infrastructure did not exist. They decided to build it.

Building the Foundation: What ABSA Actually Constructed

The core TBM programme ABSA built with MagicOrange is, in the language of Technology Economics, a full-stack model. It is not a showback report. It is not a cost allocation exercise. It is a living, integrated financial management system connecting every layer of the technology estate to the business units that consume it.

The integrations alone tell the story of the ambition. Workday, ServiceNow and vCentre were connected to provide utilisation and consumption data at the application level. AWS CUR data was ingested with extended scripting to handle shared and savings plan allocations. Azure integrations were built natively. For systems without native API connectivity, ABSA developed an internal upload platform feeding into a central data lake. Cloud tagging training was introduced across engineering teams to ensure accurate attribution – not as a one-off exercise but as an ongoing practice embedded in how the technology teams operate.

On top of this, ABSA built service-to-application mappings that included compute, storage, network, ITSM tooling, security services and cross-business-unit dependencies. App owners received dashboards showing their full cost footprint. Business units received monthly views they could act on. And at Exco level, two new KPIs entered the formal executive reporting suite: Rack Unit (RU) consumption as a measure of data centre footprint, and vCPU efficiency as a measure of virtualisation and cloud readiness.

Perhaps most powerfully, the model enabled something that changes how organisations make decisions: decommission tracking with financial precision. Applications scheduled for decommission are flagged directly in the model at TCO level. As each decommission progresses, reporting tracks cost and consumption trends across the wind-down period and produces financial metrics on the impact of completion – cost removal, freed capacity and run-rate savings realised. Cloud migration programmes benefit from the same logic: double-bubble costs become visible, gross cost changes post-migration are tracked, and business cases are validated with real data rather than estimates.

This is Technology Economics working the way it should. Every dollar connected to every outcome.

How Do You Build Financial Visibility Across 14 Countries and Into Every Branch?

What made the 2026 Pioneer submission genuinely distinctive was not the depth of the core programme – impressive as it is. It was the decision to extend the model into an entirely new domain: branch operations.

Branch costs at ABSA had previously been reported only at a regional level. That meant business units and cost consumers were making decisions about branch operations, product pricing and transactional efficiency on incomplete data. They could see a regional aggregate. They could not see a branch. That gap was not trivial – it was the difference between accountability and approximation.

ABSA closed that gap.

Working with MagicOrange, they built a dedicated branch cost model, deliberately separated from the technology cost model, focused on operational branch costing. Workshops were run with branch stakeholders to establish consensus on allocation methodologies and agree activity types. Resource and activity data – Sales, Service, Teller and Multiskilled activities, with Standard Time and cost data for each – was loaded directly into MagicOrange, enabling cost allocation at the branch level rather than rolling up to regional totals.

A duty segregation framework was implemented within the platform at multiple points throughout the branch model, creating clear lines of accountability across cost owners and consumers and ensuring the organisation operates with a transparent, auditable cost framework at the branch level.

The result: Cost per Transaction, Cost per Resource Job Title and Cost per Work Centre – at branch level. Not regional. Branch.

This is a step-change in costing precision for a financial institution of ABSA’s scale. Product owners and business units can now access branch-specific financial intelligence and use it to make informed decisions about operational efficiency, staffing models and product pricing. The data that was previously invisible is now the foundation of strategic conversations that were simply not possible before.

What Technology Economics Makes Possible

There is a tendency to describe TBM as a cost management discipline. That framing is not wrong, but it is incomplete – and ABSA’s journey illustrates exactly why.

What ABSA built is not a cost management system. It is a Technology Economics platform. The distinction matters. Cost management asks: what did we spend? Technology Economics asks: what did we spend, what did we get, and what should we do differently? The first question produces reports. The second produces decisions.

That shift – from reporting to decision-making – is visible at every layer of what ABSA has built. App owners are not just accountable for budgets; they are accountable for value. Exco-level KPIs are not just financial metrics; they are transformation trackers. Decommission reports are not just accounting entries; they are the evidence base for strategic investment choices. Branch cost models are not just spreadsheets; they are the financial intelligence layer underneath product and operational decisions.

This is the trajectory TBM is on across financial services globally. Cloud, SaaS and AI are compounding the complexity and the stakes simultaneously. AI workloads in particular represent a new accountability challenge: consumption-based, variable, expensive and hard to attribute. The organisations that will govern AI investment most effectively are not the ones with the best AI tools. They are the ones with the strongest financial foundations underneath those tools. ABSA is building that foundation.

What Comes Next

The 2026 submission gives a clear view of where ABSA’s TBM practice is heading over the next 12 months, and it is ambitious.

On the branch model, the work is to deepen and extend. Branch-level benchmarking to enable comparative performance analysis across branches. Additional activity types and resource categories as the methodology matures. And direct use of Cost per Transaction data to inform product pricing and operational planning – closing the loop between the costing model and the decisions it should be driving.

On the core technology programme, the horizon is predictive. AI-driven cost forecasting and scenario analysis are on the roadmap, alongside the quantification of AI ROI across the technology estate. Automation of chargeback and recovery processes will reduce manual intervention and improve the timeliness of financial data. Self-service reporting will bring more business unit stakeholders into active participation in the model.

And at the broadest level, ABSA is working toward something that few organisations have achieved: a single source of financial truth that spans both the technology estate and branch operations, with sustainability metrics and technology risk indicators integrated into the model alongside cost and consumption data.

A Moment Worth Marking

Awards like this one matter not because they validate what has already been built, but because they set a standard for what is possible. When the TBM Council names ABSA Group as the TBM Pioneer EMEA 2026, they are saying: this is what the discipline looks like at its best. This is what breakthrough results mean. This is the benchmark.

For the ABSA team – the TBM Office, the Finance leaders, the technology stakeholders and the business unit partners who engaged in workshops and built trust in the data over years – this recognition is thoroughly earned. They built something genuinely difficult. They built it well. And they are not finished.

MagicOrange is proud to provide the Technology Economics platform that supports ABSA’s TBM practice. More importantly, this recognition reflects the strength of the partnership and the commitment of the ABSA team to building a mature, data-driven Technology Economics capability. The next chapter promises to be just as significant.

Congratulations, ABSA.

MagicOrange is the Technology Economics platform for enterprise IT finance – ITFM, FinOps and Tech FP&A in a single model. Named a Forrester Wave Leader in IT Financial Management Software, Q2 2026.