If you’re running finance operations on legacy financial systems, does it look something like this? It’s only 10 am, and you’ve already flipped between ten different tools, spent 20 minutes loading a report, can’t find the stack of receipts you’ve got to process manually, and you’re worried your Marketing spend is running over budget. Then, it’s time to take the digital transformation leap. Find out how.
Fiddling with paper invoices and receipts? Crunching numbers in Excel? Recoiling in horror because someone flouted the expense policy again? If you can relate, you're probably dealing with these and more of the many headaches of legacy financial systems.
Getting stuck in a rut with your tech stack is easy. Perhaps legacy financial software is all your team has worked with, or fear of the unknown keeps you from exploring other options. Either way, you're not alone: 43% of banking software still operates on (Common Business Oriented Language) COBOL, a computer program developed in 1959 over 60 years ago.
In this article, we'll break down what legacy financial systems are and the tell-tale signs it's time to switch to a more agile and complete alternative. We'll also explore some critical strategies for selection and onboarding. Finally, we'll get you up to speed on the potential hazards you'll encounter to make your digital transformation a hit.
Digital transformation in action: How ATU saved over €2 million
Before diving into the digital transformation strategy, let’s get into some legacy system basics.
What do we mean by legacy financial systems?
In this article, we really mean two different things when we talk about legacy systems:
1) Legacy financial systems as 'archaic' software and hardware.
Systems are often the backbone of finance operations and long-running big businesses, making them intimidating to replace. Think accounting, payments, budgeting, forecasting, and expense management software.
While many come from reputable companies and undergo updates to remain relevant, they're still old-school tech. Why? The underlying infrastructure. It can still reflect past systems and practices. Plus, it may no longer be mainstream.
Some solutions are also custom-built, adding extra complexity and cost when revamping. Companies rack up $1,083,000 of technical debt for every 300,000 lines of code. The kicker is that's just the initial amount.
2) Multiple disconnected systems: a hangover from the first wave of digital transformation.
Many companies in different industries have undergone digital transformations over the past ten years. These changes saw companies adopt various solutions for corporate cards, expenses, subscriptions, and more, which initially seemed really helpful but have now led to a complex and disjointed view.
Payhawk customer Carolina Einarasson, FD Essentia Analytics, describes:
Before Payhawk, we used a couple of point solutions, excel, and a few different credit cards, but we didn't have an all-in-one centralised solution. The first thing I did when I became FD was to remove time-draining activities. For us, spend management was a quick win; we saw Payhawk as the future where we could have expense data entry, credit cards, approvals, spend requests, paying invoices, and employee reimbursements, all in one.
We've got your back if you're looking to move from multiple disconnected solutions and ride the second wave of digital transformation towards a fully connected spend management function.
With Payhawk, you can stop juggling tools and screens as we bring everything you need together in one place. Plus, we're constantly tweaking and improving our features and direct integrations (with ERPs like NetSuite and Xero) to give finance pros better control and a clear view of corporate spending.
Legacy systems were once the pinnacle of technology. But now, more innovative end-to-end solutions have hit the market, easing the load on finance teams. But, decision fatigue can set in when browsing the options, leaving you second-guessing whether to switch.
To help you decide, let’s cover some issues archaic finance systems bring.
Knowing the consequences of avoiding the digital transformation leap is critical.
Here are a few:
Profits nosedive
The upkeep costs of archaic systems rack up quickly. Businesses waste around 20% of their IT budget yearly, and unresolved technical debt is one cause. These costs eat into profits, thinning your bottom line.
Errors galore
Outdated systems and disconnected interfaces combined with manual processes leave room for errors. This issue can steer decision-making in the wrong direction with costly consequences. Imagine a team member putting incorrect numbers into an outdated forecasting system (or waiting ages for a data lag to resolve and show information from one tool to the next) and then overshooting earning projections and budgets by 30%.
The knock-on effect of the above is mass overspending. Reporting a loss soon follows.
All of which you could have avoided by using modern spend management software.
Operational efficiency takes a beating
Some legacy financial systems slow down task completion, making it tough to hit growth targets. Customers also feel the adverse effects of archaic technology through service delays.
Poor adaptability decreases competitiveness
In today's competitive market, agility and speed are essential to remain responsive. Yet, some legacy systems can't adapt, so meeting customer and company needs is tougher. So, market shifts rock the business; worse, it'll lose its competitive edge.
To go from concept to reality in tech modernisation, you’ve got to understand what your finance tech stack looks like now and how you’d like it to be. Here’s the game plan.
First, get to know your finance tech ecosystem to identify what features should stay, go, and join. Gather your team, grab a whiteboard, and answer the following questions:
The harsh reality is that 70% of digital transformation projects flop. The high failure rate isn't due to a lack of enthusiasm but rather improper planning. So, it's essential to have a strategy for replacing legacy systems. Let's break down the steps to build one.
During the objectives-setting phase, we outlined the strengths and weaknesses of your legacy systems. Now, you're going to up the ante by diving into the details of its architecture. Here's how:
Take inventory of your legacy system's characteristics
Zoom in on the biology of legacy financial software. We're talking details like the:
Next, consider the following metrics to evaluate how the system has held up:
Also, highlight any bottlenecks and performance issues. For example:
Next, complete security and compliance assessments to pinpoint vulnerabilities. Concentrate on the following areas:
A crucial question you want to answer is, “How agile are our legacy financial systems?” Note how the legacy system integrates with other systems, considering time, speed, and accuracy. Also, examine how adaptable the tools are.
Understand your legacy system’s maintenance requirements via its technical documents and manuals. Also, review any contracts and licences and note expiry and hardware certification dates.
Next, outline each business process using legacy financial software. Consider how you can simplify these tasks. For example, say your staff isn’t submitting evidence for expenses because the process is too long. They must scan an invoice, email it to themselves, and then upload it to the legacy system. Here, you could use solutions like Payhawk to streamline the process. The global agency FFW did.
FFW had used payment methods and solutions across European entities, creating complex operational challenges. So, they pulled spend management tasks under one roof with Payhawk. Staff now get corporate cards with spend controls that the finance team can manage effortlessly.
Also, cardholders use Payhawk’s AI camera app with OCR technology to extract key receipt details for speedy processing. Then, FFW’s pre-set approval policy facilitates expense approval with a single click on any device.
Payhawk's fuss-free, AI, and automation-powered process saves FFW hours daily. No more wasting energy on manual data entry, triple-checking banking details, or chasing receipts. Read more about FFW’s inspiring journey.
There are seven tried and tested approaches to bring a financial tech stack into the future. Which one works best depends on your budget, existing technical debt, and risk tolerance. Let’s take a closer look.
It entails migrating existing software to another software or hardware with minimal code changes. It aims to improve the system’s infrastructure.
You’ll change the legacy system’s infrastructure by adopting new designs and adapting the system to fit modern standards. Restructuring tackles the system’s performance, agility, and scalability.
You’ll create a new system to copy the legacy system’s functionality. From here, users can access features they know and love while introducing modern technologies and infrastructure. Scaling and maintenance are also quicker.
Involves moving software to a new environment with few code changes, for example, shifting the application to another server while preserving the architecture and code. Rehosting strives to maintain existing business logic and workflows. You can also gain quick results with minimal disruption risk.
Requires ditching the legacy financial software and taking a fresh outlook. You’ll also implement the latest technologies and best practices. Some adoptees integrate the legacy system, while others replace it over time. This approach aspires to align systems with the organisation’s current needs.
Using the Refactoring approach, you’ll restructure the legacy systems code without altering how it behaves on the user side. You won’t debut any new features. Instead, you’ll optimise the code’s internal structure. Refactoring aims to make code easier to maintain, read, and perform.
To encapsulate, you’ll draw from the legacy system and expand its features by breaking up and bundling its data and functions. You’ll also preserve most of the code and use an API to make it accessible as a service. This approach allows the system to be more secure, run more efficiently, and conduct repairs more quickly.
A successful business digitisation project balances each stakeholder's needs. So, get everyone involved with a survey or roundtable. Inquire about the legacy financial software's positives and negatives and get improvement suggestions.
Some key stakeholders include:
You’ve researched, got everyone involved, and whittled down a few options. Great work! Now, break down your testing and implementation into phases. How much depends on your company’s internal procedures and priorities.
For example, imagine you want to onboard a spend management software. If you're a big complex business, you could trial two core functions: spend control and reimbursement of travel expenses. Then, roll out to other tasks once you’ve got proof of concept.
Discordia took a similar approach. They ran a Payhawk trial with about 30 drivers over 2.5 months. Then, using their learnings, they optimised the second trial, involving 700 drivers over one year. Discordia now has a robust technological system, and drivers use the new software seamlessly. (More on Discordia’s phenomenal journey later).
Transforming transport expectations: How Payhawk helps Discordia tackle expense challenges on the road
Recently, groundbreaking solutions have hit the finance world. Here are some of the latest and greatest tools:
Modernisation comes with potential pitfalls, so a risk management strategy is vital. Outline all the possible hazards and how to dodge them to bounce back quickly if disaster strikes. Here are some of the most common:
Switching from legacy financial systems? Take the pre-built solution expressway.
The quickest and easiest way to optimise your finance tech stack is to onboard an all-in-one solution. It should be customisable, with access to technology updates and expert support.
It's the route the transport company Discordia took. Truck driver levels took a hit after tackling complex logistics, international paperwork, and various payment tools. Having to send money to drivers' bank accounts daily also affected the finance team. So, Discordia partnered with Payhawk to drive workforce efficiency, satisfaction, and retention.
Using Payhawk's expense management software and smart capture features, Discordia removed burdensome paperwork from drivers' duties. Discordia's finance team now manages transactions to driver's accounts through one master account on Payhawk. This feature eliminates time-consuming admin and expensive bank transfer charges.
Drivers also get a debit card, which Finance top-up daily, providing more flexibility and convenience. Payhawk even syncs with Discordia's ERP platform for improved insights and decision-making. Check Discordia's trailblazing digitisation journey.
“The only constant in life is change”, as the saying goes. Not too long ago, basic software and manual tools and processes ruled. Thankfully, some new solutions are so good they give legacy financial systems a run for their money.
So, don’t settle for obsolete or multiple disconnected tools. Pull together an action plan, test a few tools, and adjust your tech stack based on the results. Digital transformation is a never-ending journey. So, when you find your match, commit to the long haul and don’t stop improving. Your finance processes will be unrecognisable, and your bottom line, staff, and customers will thank you, too.
Is outdated finance software holding your business back? Take the digital transformation leap with Payhawk: Book a personalised demo today.
Trish Toovey works across the UK and US markets to craft content at Payhawk. Covering anything from ad copy to video scripting, Trish leans on a super varied background in copy and content creation for the finance, fashion, and travel industries.