Payments Modernisation: The CFO Business Case
Payment infrastructure modernisation is often easy to justify from a technology perspective.
Legacy platforms are expensive to maintain. Integrations are becoming harder to manage. New payment methods require more development work. Regulatory requirements continue to evolve. And payment teams are increasingly expected to deliver better resilience, faster change and stronger customer experiences from infrastructure that may have been designed years or even decades ago.
The challenge is not always proving that the technology needs to change.
The challenge is getting the CFO, executive team and board to approve the investment.
For finance leaders, "we need a modern payment platform" is not a business case. They need to understand what the current infrastructure is costing, what risk the organisation is carrying, what value modernisation can create and how confidently the organisation can deliver that value.
That means payment technology leaders need to change the conversation.
Instead of presenting modernisation as a technology replacement programme, the business case needs to connect infrastructure decisions to financial outcomes.
What is the cost of maintaining the current environment?
How much revenue is being lost through payment failures or inefficient processing?
What does regulatory change require the organisation to invest in?
What operational costs could be reduced?
And what measurable return can the organisation expect from modernising?
The strongest payment infrastructure modernisation business case answers those questions before the CFO has to ask them.
Why payment infrastructure modernisation struggles to get executive approval
Technology teams often see the weaknesses in legacy payment infrastructure every day.
They know which systems are difficult to maintain. They know where integrations are fragile. They know how long it takes to introduce a new payment capability. They see the manual work required to support outdated processes.
Executives may not see those problems in the same way.
From the board's perspective, the existing infrastructure may appear to be working.
Payments are being processed. Customers are completing transactions. Finance is receiving settlements. Operations are functioning.
That creates a difficult question:
Why spend millions replacing something that technically still works?
This is where many modernisation programmes struggle.
The technology case may be completely valid, but the financial case has not been developed sufficiently.
A CFO needs to understand the difference between the cost of the programme and the cost of doing nothing.
If modernisation is presented simply as a platform upgrade, it competes for investment against every other technology and business initiative.
If it is presented as an opportunity to reduce structural costs, protect revenue, address operational risk, meet regulatory expectations and create a more flexible payment capability, the conversation becomes broader.
The objective is not to make the technology sound more important.
It is to translate the technology problem into business language.
The problem with building a technology-first business case
A technology-first business case usually starts with the infrastructure.
The organisation has an ageing payment platform, multiple point-to-point integrations, fragmented providers and increasing maintenance requirements.
The proposed solution is a new platform, a new architecture or a migration to a modern payments environment.
The business case then focuses on implementation costs, technical benefits and future capabilities.
The problem is that these benefits can be difficult for a CFO to evaluate.
"Modern architecture" is not a financial metric.
"Improved scalability" does not automatically demonstrate ROI.
"Better integration capabilities" does not explain when the investment will pay for itself.
A stronger approach starts with the financial consequences of the existing environment.
For example:
How much does the organisation spend maintaining legacy payment systems?
How many employees are required to support manual payment operations?
How much does each new provider integration cost?
How much revenue is lost through failed transactions?
What does a payment outage cost per hour?
How much is being spent adapting legacy systems to regulatory requirements?
How long does it take to launch a new payment method or enter a new market?
What is the cost of delaying modernisation?
These questions turn infrastructure from an IT discussion into a business discussion.
What legacy payments infrastructure is really costing the business
The visible cost of legacy infrastructure is only part of the problem.
There are licensing costs, maintenance contracts, infrastructure costs and internal technology resources.
But legacy payment systems can also create a series of less visible costs.
Technical debt
Payment platforms that have evolved over many years can accumulate technical debt.
Every additional integration, workaround and custom development can increase the complexity of future changes.
A change that should take weeks may take months because multiple systems need to be modified and tested.
The organisation is effectively paying for historical technology decisions every time it makes a new change.
Operational inefficiency
Fragmented payment infrastructure can also increase manual work.
Payment operations teams may need to reconcile information across multiple systems, investigate failures using different dashboards or manually coordinate provider issues.
Those activities may not appear as a single line item called "legacy infrastructure cost".
They are distributed across technology, operations, finance and support teams.
A proper business case should attempt to quantify them.
Integration costs
Every new payment method, provider or market can create another integration.
The cost is not limited to the initial development.
There can be ongoing maintenance, testing, monitoring, certification and operational support.
Over time, the organisation can spend significant resources maintaining connections that were originally introduced to solve individual business requirements.
Revenue leakage
Payment infrastructure can also affect revenue directly.
A failed transaction can mean a lost sale.
A payment provider outage can interrupt revenue generation.
Poor routing can result in avoidable declines.
Limited payment method availability can prevent customers from completing transactions.
These effects make payment infrastructure relevant to commercial performance, not just technology expenditure.
Risk and compliance costs
Modern payment infrastructure also needs to support changing regulatory and resilience requirements.
For Australian organisations, payments modernisation may need to be considered alongside requirements and industry changes involving areas such as ISO 20022, the BECS transition and APRA CPS 230.
The business case should therefore consider not only the cost of modernising but also the cost of repeatedly adapting legacy infrastructure to meet new requirements.
How to quantify the cost of inaction
One of the most powerful elements of a payment infrastructure modernisation business case is the cost-of-inaction model.
Instead of asking only:
"How much will modernisation cost?"
Ask:
"How much will it cost the organisation if we continue operating as we are?"
The calculation should consider several categories.
1. Current operating cost
Calculate the cost of maintaining the existing payment environment.
This can include:
Platform and licensing costs
Infrastructure costs
Vendor support
Internal technology resources
Application maintenance
Integration maintenance
Testing and certification
2. Cost of payment failures
Estimate revenue affected by failed transactions, outages, avoidable declines and other payment failures.
The objective is not to assume that every failed transaction would have converted.
Instead, use available transaction data to establish realistic recovery assumptions.
3. Cost of manual processes
Quantify the operational effort involved in reconciliation, exception handling, reporting, provider management and other manual activities.
This can help identify where modernisation could reduce recurring operating costs.
4. Cost of regulatory change
Estimate the technology and operational effort required to adapt legacy systems to changing regulatory and payment infrastructure requirements.
If every regulatory change requires a separate technology project, that recurring cost should form part of the investment discussion.
5. Cost of delayed innovation
This is often harder to quantify but still relevant.
If introducing a new payment method takes six months instead of six weeks, the organisation may be delaying potential revenue, customer acquisition or market expansion.
The business case can therefore consider the financial value of faster change.
Building the financial case for payments modernisation
Once the cost of the current environment is understood, the next step is to model what modernisation could change.
A useful business case can divide benefits into several categories.
Cost reduction
Potential savings from lower maintenance costs, fewer bespoke integrations, reduced manual processing and more efficient payment operations.
Revenue protection
Potential recovery of transactions affected by payment failures, outages or avoidable declines.
Revenue growth
The ability to support new payment methods, markets, channels and commercial models more quickly.
Risk reduction
Reduced dependency on ageing systems, concentrated providers and fragile integrations.
Operational efficiency
Less manual intervention and improved visibility across payment operations.
Technology agility
A more flexible platform that allows future payment capabilities to be introduced without rebuilding the underlying infrastructure each time.
This makes the business case more comprehensive than a simple technology ROI calculation.
How to calculate payment technology ROI
The ROI model should be built around measurable financial outcomes rather than broad technology benefits.
A simplified model could look at:
Modernisation ROI = Financial benefits generated − modernisation investment / modernisation investment
But the calculation needs to reflect the timing of the investment.
Modernisation programmes generally require significant expenditure before the full benefits appear.
A CFO will therefore want to understand:
Initial investment
Ongoing operating costs
Annual savings
Revenue recovered
Revenue enabled
Implementation costs
Migration costs
Expected payback period
Net financial benefit over the programme horizon
Scenario modelling can make the case more credible.
For example, organisations can model conservative, expected and higher-value outcomes based on different assumptions for transaction recovery, operating cost reduction and implementation timelines.
The objective is not to manufacture an attractive ROI number.
It is to demonstrate that the organisation understands both the opportunity and the uncertainty.
Factoring regulatory change into the investment case
Payment infrastructure modernisation cannot be considered independently of the wider payments environment.
Australian organisations are operating through a period of significant payment infrastructure and regulatory change.
ISO 20022 is changing the structure and richness of payment data.
The Australian payments ecosystem is also transitioning away from legacy arrangements such as BECS toward newer payment capabilities.
For organisations subject to APRA's operational risk requirements, resilience and third-party dependency also need to be considered as part of broader technology and operational planning.
These developments can create additional reasons to review legacy infrastructure.
But regulatory change should not simply be used as a justification for spending.
The business case should identify the actual investment required, the existing capability gaps and the consequences of maintaining the current environment.
This makes regulatory investment part of a broader modernisation strategy rather than a collection of disconnected compliance projects.
Why payments modernisation should not be a big-bang programme
Large technology programmes carry implementation risk.
This is particularly important for payment infrastructure because payments are connected to revenue, customers, finance operations, reconciliation and multiple external providers.
A failed migration is not simply a technology incident.
It can affect transaction processing and commercial operations.
Research into large technology programmes has also highlighted the financial risks associated with major transformation initiatives, including cost overruns and benefits falling short of expectations.
That makes the structure of the programme itself part of the business case.
A large organisation does not necessarily need to choose between doing nothing and replacing everything at once.
A phased approach can reduce risk by breaking modernisation into manageable stages.
This could involve:
Mapping the existing payment environment.
Establishing baseline costs and performance.
Prioritising the highest-value infrastructure changes.
Introducing modern capabilities alongside existing systems.
Migrating payment flows progressively.
Measuring benefits after each phase.
Using those results to inform the next investment decision.
The result is a business case that is easier to govern because investment can be connected to measurable outcomes at each stage.
Building a phased payments infrastructure investment case
A phased programme can also change the conversation with the CFO.
Instead of asking for approval for a large multi-year transformation based entirely on projected future benefits, the organisation can establish a sequence of investment decisions.
Phase 1: Understand
Map providers, platforms, payment flows, integrations, costs, operational dependencies and performance.
The goal is to establish the baseline.
Phase 2: Prioritise
Identify the areas where modernisation can create the greatest measurable value.
This might include high-cost infrastructure, high-volume payment flows, resilience gaps or processes creating significant operational overhead.
Phase 3: Prove
Select targeted initiatives where benefits can be measured.
This could include payment routing, provider consolidation, modern API integration or automation of selected payment operations.
Phase 4: Scale
Use evidence from the initial phases to expand the modernisation programme.
This creates a stronger investment case because the organisation is no longer relying entirely on theoretical benefits.
It has evidence from its own environment.
How to present payments modernisation to the CFO and board
The presentation should not begin with architecture diagrams.
Start with the business problem.
A CFO needs to understand:
What are we spending today?
What risks are we carrying?
What revenue or efficiency opportunities are we missing?
What will modernisation cost?
When will we see the benefits?
What happens if we delay?
How will we control implementation risk?
A useful executive business case can therefore follow a simple structure:
Current state → Financial impact → Cost of inaction → Proposed change → Investment required → Expected benefits → Implementation risk → Phased roadmap → Measurement framework
This keeps the discussion focused on decisions rather than technology terminology.
It also makes it easier for different stakeholders to understand their role.
The CIO can assess the architecture.
The payments leader can assess transaction performance.
The operations team can assess process improvements.
The finance team can validate the financial assumptions.
And the CFO can assess the investment against competing priorities.
The metrics that matter to executive decision-makers
A payment infrastructure programme should have measurable success criteria.
Depending on the organisation, these could include:
Payment processing cost per transaction
Payment acceptance rate
Failed transaction rate
Revenue recovered from failed payments
Payment outage duration
Number of payment providers
Integration maintenance cost
Time required to add a new payment method
Manual reconciliation effort
Payment operations cost
Cost of regulatory change
Platform maintenance expenditure
Migration progress
Payback period
Return on investment
The important point is to establish the baseline before modernisation begins.
Without a baseline, it becomes difficult to demonstrate whether the programme actually delivered the expected value.
From technology project to strategic business investment
The strongest payment infrastructure modernisation programmes are not simply technology projects.
They are business transformation programmes supported by technology.
Modern infrastructure can give an organisation greater control over payment providers, more visibility into transaction performance, greater resilience and more flexibility to respond to changing customer and regulatory requirements.
It can also change the economics of payment operations.
Instead of continually spending money to maintain an increasingly complex legacy environment, the organisation can begin investing in an infrastructure model designed to support future requirements.
That is a fundamentally different proposition.
The objective is not modernisation for its own sake.
It is creating a payment environment that costs less to operate, creates fewer constraints, protects revenue and allows the business to adapt faster.
For CFOs, that is the difference between approving a technology expense and approving a strategic investment.
What payment leaders should be asking before seeking investment
Before presenting a modernisation programme to the executive team, payment and technology leaders should be able to answer several questions.
What is our current payments infrastructure costing us?
Not just licensing and maintenance, but integrations, operations, support and manual processes.
How much revenue could be affected by payment failures?
Can transaction data demonstrate the scale of the opportunity?
What does our current infrastructure make difficult or expensive?
New providers, new payment methods, new markets, regulatory changes or operational improvements?
What will happen if we do nothing for another three to five years?
Will costs increase? Will technical debt grow? Will regulatory adaptation become more expensive?
What are the financial benefits of modernisation?
Can each major benefit be connected to a measurable financial outcome?
What are the implementation risks?
And how can a phased programme reduce those risks?
How will we measure success?
Which metrics will demonstrate that the investment delivered the expected value?
If these questions cannot be answered, the organisation may not yet have a business case.
It may only have a technology proposal.
Building a payments modernisation strategy that the business can support
A successful payment infrastructure modernisation strategy starts with understanding the existing environment rather than immediately selecting a replacement platform.
The first step is to map the current payment stack.
That means understanding providers, payment flows, integrations, operational processes, costs, performance and dependencies.
From there, organisations can identify where legacy infrastructure is creating measurable financial or operational impact.
The modernisation roadmap should then connect each proposed investment to a specific business outcome.
That might mean reducing infrastructure costs, improving payment resilience, recovering lost transactions, simplifying operations, supporting regulatory change or creating the flexibility to introduce new payment capabilities faster.
This approach makes modernisation easier to evaluate.
It also makes it easier to govern.
Instead of treating the programme as one large technology commitment, leaders can establish clear investment stages, measurable outcomes and decision points throughout the transformation.
Build the business case before you build the new infrastructure
Payment infrastructure modernisation does not need to begin with a platform decision.
It should begin with a business decision.
What is the current environment costing?
Where is value being lost?
What risks are increasing?
What capabilities does the business need?
And what investment approach can deliver those capabilities without creating unnecessary transformation risk?
For payment technology leaders, the strongest case for modernisation is rarely "our technology is old."
It is that the existing infrastructure is creating measurable costs, limiting business flexibility and increasing the effort required to respond to a changing payments environment.
When those impacts are quantified, modernisation becomes easier to discuss in terms the CFO and board already understand.
The goal is not simply to secure approval for a technology programme.
It is to build a credible investment case that connects payments transformation to financial performance, resilience and long-term business capability.
How Conexxia can help build your payments modernisation business case
Payments infrastructure modernisation is a strategic decision before it becomes a technology programme.
Conexxia helps organisations assess their existing payment environments, identify infrastructure and operational challenges, and develop payments modernisation strategies aligned with business objectives.
The starting point is understanding what already exists.
That means mapping payment infrastructure, providers, integrations, payment flows and operational dependencies, then identifying where cost, complexity, resilience or revenue leakage may be creating measurable business impact.
From there, organisations can develop a practical modernisation roadmap that prioritises investment around business value rather than technology change for its own sake.
A phased approach can also help organisations manage implementation risk, validate benefits and build confidence before committing to larger transformation stages.
Whether the priority is legacy payment system replacement, payment platform migration, payment operations, resilience, compliance or creating a more flexible payment architecture, the business case should connect every investment decision to a measurable outcome.
Your payment infrastructure is already affecting the business. The question is whether you have quantified the impact and built the case for changing it.
Conexxia can help you move from a technology challenge to a structured payments modernisation business case, giving your leadership team the financial, operational and strategic context needed to make the investment decision.
Explore Conexxia's Payments Consulting and Payments Infrastructure Modernisation capabilities, or speak with the team about your payments transformation priorities.
Aftab Khan
Head of Payments Consulting
On a mission to help change the world, one experience at a time
I collaborate with progressive businesses to deliver successful business outcomes in 4 key areas: Increasing Revenues, Improving Operational Efficiencies, Regulatory Compliance and Elevating Customer Experience, leading to sustainable business growth.
Comments