Financial transformation changes how a finance function runs, not just what it runs on. The triggers are a slow close, data scattered across systems and a board asking for answers the function cannot produce. The common failure is buying a new system before anyone has standardised the process.
What financial transformation actually means
Three things change together or the exercise is not transformation. The systems: usually an ERP move, a consolidation layer, or connecting source systems that currently talk to each other through a person and a spreadsheet. The process: standardising how a task is done so it is done the same way twice. The team: who does what once the manual work is gone. Change the system alone and you have bought software.
The compliance floor does not move while you do it. Whatever the new architecture looks like, the ATO's record-keeping rules still apply to what you keep and for how long, and directors keep their financial reporting obligations throughout the migration. Both are worth writing into the project plan rather than discovering at the first close on the new system.
What triggers it
Almost always one of three things. The close is too slow to be useful, so the board is making decisions on numbers that are three weeks old. Data is scattered across systems that do not reconcile, so every question becomes a project. Or the business has outgrown the function: new entities, new currencies, a raise or an acquisition, and the existing process cannot absorb it.
Underneath all three is the same shift. Everything is moving towards automation and AI, which means finance roles change rather than the industry disappearing.[1] Transformation is what that shift looks like when a company decides to get ahead of it deliberately instead of absorbing it through attrition.
Why the new system inherits the old chaos
The recurring failure is sequence. A company with a process that differs by entity and by person buys a system, migrates the mess into it, watches the twelve day close relocate rather than shorten, and calls the project a failure. Nothing about the software caused that. The process was never standardised, so there was nothing coherent to automate.
Difficulty also varies by business model more than vendors admit. There is a lot of noise about tech, AI and automation, and it is usually far easier to implement in a digital business than in an inventory-heavy one.[2] Where the returns show up first is in simpler businesses like software and services, which have clean models, and it is much harder in businesses carrying significant inventory, stock and logistics complexity.[3] If you are a scale-up with physical product, budget for a longer runway than the case study you were shown.
| How the project is usually run | What has to happen first | |
|---|---|---|
| Diagnose | Scope the system requirements | Write down how the close is done today, per entity and per person. The variation between those write-ups is the actual project. |
| Standardise | Skipped, because the new system will fix it | Make the process the same everywhere before it is automated anywhere. This is the step that gets cut and the reason projects fail. |
| Implement | Migrate and go live | Run the first two closes with the old process available as a fallback. A migration with no fallback is a bet, not a plan. |
| Reshape the team | Deal with it afterwards | Decide up front what the freed-up hours are for. If the answer is nothing, the business case was never about the hours. |
Who leads it, and what to look for
For senior finance roles that involve system change, the candidates who help are the tech-savvy ones who understand ERP implementation and have carried transformation projects before.[4] That is a narrower group than the CV market suggests, because sitting inside a business during an implementation and owning one are different experiences and read identically on paper.
The bar is lower than founders assume on AI specifically. What employers value is candidates who are adaptable and translatable with technology, with real exposure to automation and process improvement and genuine interest in AI, without expecting expert-level capability.[5] The concrete version of that looks unglamorous: a chat AI with a projects workspace, a data connector or middleware to link the source systems, meaning the accounting platform, the CRM and timesheets, with IT support behind it, and validated review skills for anything that touches contracts.[6]
That capability carries a price. In the Australian market a half-decent finance hire who can add value beyond compliance costs around $150k to $160k, while someone with strong experience across automation, technology, AI, capital raises and acquisitions is closer to $200k and up.[7] The premium is real and it is the cheapest part of a transformation budget.
Where the change is large enough to be its own mandate, the search becomes a finance transformation director hire rather than a line in a Head of Finance brief.
Where this sits for an Australian scale-up
Mostly it does not, yet. I work with smaller Australian businesses, where a formal transformation skill set is often not the relevant thing to hire for.[8] At 30 or 60 people the equivalent work is smaller and more useful: pick one system of record, standardise the close checklist, stop the manual re-keying between tools, and hire a finance leader who is comfortable doing that alongside the day job.
Calling that transformation oversells it, and treating it as a multi-year programme wastes money you do not have. The test is whether, after the work, a new person could run the close by reading the documentation. If not, no system will fix it.
The clearest symptom is usually reporting that arrives too late to act on. Here is who should own the profit and loss statement as the function grows.
Common questions
What is financial transformation?
A deliberate change to how a finance function operates, covering three things at once: the systems it runs on, the process it follows, and the shape of the team. All three have to move together, because a company that changes only the systems has made a purchase. Companies reach for it when the close is too slow to be useful, when data sits in systems that do not reconcile, or when new entities, a raise or an acquisition have outgrown the existing process.
Why do finance transformation projects fail?
Sequence. A company whose process differs by entity and by person buys a system, migrates the variation into it, and watches a twelve day close relocate rather than shorten. Standardising the process has to come before automating it, and it is the step that gets cut because it produces nothing visible. Difficulty also varies by business model: it is far easier in a digital business than in an inventory-heavy one.
Who should lead a finance transformation?
Someone who is tech-savvy, understands ERP implementation and has carried a transformation project before rather than merely sat inside one. Those two experiences look identical on a CV, so the screening has to be about what they owned and what broke. In a larger business this is a dedicated mandate. At scale-up size it belongs to the Head of Finance or CFO alongside the day job.
Does a 50-person Australian company need financial transformation?
Not as a formal programme, no. At that size the equivalent work is picking one system of record, standardising the close checklist, removing manual re-keying between tools, and hiring a finance leader comfortable doing that alongside everything else. The useful test is whether a new starter could run the close from the documentation. If not, no system purchase will fix it.
References
- Where I think the technology bites: everything is moving towards automation and AI, which means finance roles will change rather than the industry disappearing altogether.
- What I see AI actually changing: while there is much noise about tech, AI and automation, it is often easier to implement in digital businesses compared to inventory-heavy businesses.
- How I describe the automation shift: many of the good returns from AI are in simpler businesses like tech or services, which have easy models, and it is much harder to implement in businesses with significant inventory, stock and logistical complexity.
- From the briefs Tom Hunter runs: for senior finance roles involving system change, candidates who are tech-savvy, understand ERP implementation and have experience with transformation projects are particularly helpful.
- What came up in a search I was running: candidates who are adaptable and translatable with tech, particularly in automation, process improvement and an interest in AI, without necessarily expecting expert-level AI capability.
- My read on where automation lands: a chat AI with projects such as Claude, a data connector or middleware such as CData to link source systems like Xero, the CRM and timesheets with IT support, and validated legal-review skills for contract automation.
- What the numbers look like here: a half-decent finance hire who can add value beyond compliance might cost $150k to $160k, but a hire with strong experience in automation, tech, AI, capital raises and acquisitions will be closer to $200k and above.
- From a search I ran: Tom Hunter mostly recruits for smaller businesses, where transformation skill sets might not be as relevant. That focus on first finance leaders and first CFOs at Australian startups is set out in an interview with him on the Honest Wealth Builders podcast.