WHICH CAREER PATH IS YOURS? · Future Defined Academy

WHICH CAREER PATH IS YOURS?

Which Career Path Is Yours? Start Here.

Your accounting qualification opens six career paths.

Most accountants do not know all six exist. Fewer know how to position themselves for them. That is what FDA is here to change.

Read the description of each path below. One of them will feel immediately relevant to where you are and where you want to go. That is your starting point.

PATH 1 — FINANCE BUSINESS ANALYST

You analyse data, document how financial processes work today, identify the gaps between current state and future state, write the requirements for how the system should work, and build the artefacts that ERP programmes run on.

You are the bridge between what finance needs and what the technology delivers.

This is the most accessible entry point into ERP careers for qualified accountants. Your AP, AR, GL, and close experience is directly relevant. You do not need to know how to configure Oracle. You need to know what it needs to do — and why.

Accounting knowledge that opens this door: Any experience in AP, AR, GL, reconciliations, month-end close, or financial reporting.

PATH 2 — FUNCTIONAL CONSULTANT

You design solutions, configure ERP systems to match business requirements, run design workshops with finance and operational teams, and support adoption. You understand Oracle, SAP, Dynamics, Unit4, or Workday well enough to configure it — and you understand finance well enough to know what the configuration must achieve.

Functional Consultants sit at the intersection of accounting knowledge and system expertise. They are typically employed by Systems Integrators or work as independent contractors on ERP programmes.

*Accounting knowledge that opens this door: Deep understanding of finance processes end to end — P2P, O2C, R2R, and the modules that support them.*

PATH 3 — FINANCE SYSTEMS SPECIALIST

You own the systems that finance runs on. You support users, optimise processes, manage system upgrades, ensure data quality, build reports, and drive continuous improvement. You sit between the finance team and IT — speaking both languages fluently and ensuring neither side loses the plot.

This is one of the most underrated transitions for qualified accountants. The role exists in almost every organisation that runs an ERP system — and the demand is growing.

Accounting knowledge that opens this door: System-adjacent experience — running reports, managing data, supporting system changes, owning reconciliation tools.

PATH 4 — WORKSTREAM LEAD

You lead Finance, Payroll, or Data workstreams on ERP transformation programmes. You manage teams, challenge suppliers, own delivery at each programme gate, drive go-live readiness, and present to programme boards. You are accountable for what your workstream delivers.

Workstream Leads are not just senior accountants. They are programme delivery professionals who understand both the finance content and the governance that surrounds it. The best ones have a Finance BA background and a strong understanding of the programme lifecycle.

Accounting knowledge that opens this door: Senior finance experience combined with any exposure to system change, audit, or process improvement.

PATH 5 — CONTROLS & GOVERNANCE

You strengthen the controls layer inside financial systems. You design Segregation of Duties frameworks, ensure audit readiness, implement compliance standards, and govern how access and risk are managed across ERP environments.

This path sits at the intersection of accounting, audit, and technology governance. CISA and ISO 27001 are the key professional credentials. The demand for people who understand both ERP systems and financial controls is significant — and growing as regulatory requirements increase.

Accounting knowledge that opens this door: Any experience in audit, internal controls, compliance, risk management, or financial governance.

PATH 6 — TRANSFORMATION LEAD

You lead enterprise-wide finance transformation. You shape strategy, design operating models, manage executive stakeholders, govern programme delivery, and ensure lasting change. You operate at board and director level and are accountable for what the transformation achieves — not just what the system does.

This is the most senior path. It is typically reached after experience as a Finance BA, Workstream Lead, or senior finance professional with significant programme exposure. The Transformation Lead is the person who connects accounting knowledge, technology delivery, and organisational change into a coherent whole.

Accounting knowledge that opens this door: Strategic finance experience — operating model design, business case development, benefits realisation, stakeholder management at executive level.

WHICH PATH IS RIGHT FOR YOU RIGHT NOW?

Post in the Career Paths category and tell us:

— Your current role and qualification

— Which path feels most relevant

— What is stopping you from making the move

Fall4U responds to every post.

Fall4U FCA FCCA — Founder, Future Defined Academy

══════════════════════════════════════════════

SIX CAREER PATH GUIDES

══════════════════════════════════════════════

CAREER PATH GUIDE 1 — FINANCE BUSINESS ANALYST

The Finance Business Analyst Path — What It Is, What You Do, and How Your Accounting Knowledge Gets You There

Category: 🗺️ Career Paths

---

What a Finance BA actually does**

A Finance Business Analyst is the person on an ERP programme who understands what the finance team needs — and can translate that into requirements that the system can be configured to deliver.

They are not accountants who have learned to use Oracle.

They are not IT professionals who have learned some accounting.

They are the bridge between the two.

On a live programme, a Finance BA's day looks like this:

Morning — running a process workshop with the AP team to document how supplier invoices are currently processed, what the pain points are, and what good looks like in the new system.

Afternoon — writing up the requirements from that workshop into a structured requirements catalogue with MUST, SHOULD, and COULD priorities.

End of day — reviewing a defect that has come back from SIT where the Oracle configuration does not match what the business said it needed, and working with the consultant to find a solution.

This is not a glamorous job. It is a precise, methodical, high-value job — and it is one that qualified accountants are uniquely positioned to do well.

The delivery lifecycle from a Finance BA perspective

The Finance BA is active from Gate 0.2 through to Gate 2.2. Here is what that looks like in practice:

Gate 0.2 — Discovery Complete

The Finance BA runs As-Is process workshops, documents current state finance processes, identifies pain points and root causes, and produces the As-Is Process Maps and Pain Points Register. This is the foundation everything else is built on.

Gate 1.1 — Design Approved (HLD)

The Finance BA contributes to the Master Requirements List, validates the High-Level Design against accounting requirements, and signs off the future state process design for the finance workstream.

Gate 1.2 — Detail Locked (LLD)

The Finance BA writes Level 3 process maps, produces User Stories and Acceptance Criteria, and validates the detailed design against business requirements. This is where accounting knowledge is most critical — the LLD specifies exactly how the system will be configured.

Gate 2.1 — Test Complete

The Finance BA produces test cases and test scripts, executes SIT and UAT testing for finance modules, logs defects, and validates migrated data against the legacy system. This is the trial balance mindset applied to programme delivery.

Gate 2.2 — Go-Live Approved

The Finance BA confirms UAT sign-off, validates cutover readiness, reconciles opening balances, and supports go-live and hypercare.

The artefacts a Finance BA produces

These are the deliverables that evidence Finance BA capability in interviews and on CVs:

- As-Is Process Maps (Level 1, 2, and 3)

- Pain Points Register and Root Cause Analysis

- Master Requirements List (MUST / SHOULD / COULD)

- User Stories and Acceptance Criteria

- To-Be Process Maps

- Gap Register

- Data Migration Reconciliation

- SIT Test Cases and Test Results

- UAT Test Scripts and Sign-off Documentation

- Standard Operating Procedures (SOPs)

- Training Materials

---

What accounting experience maps to Finance BA work

You do not need to have worked on a programme to be a Finance BA. You need to have worked in finance — and be able to talk about that experience in programme language.

| Your accounting experience | Finance BA equivalent |

|---|---|

| Processing supplier invoices | AP process knowledge — P2P end to end |

| Bank reconciliation | Cash management and sub-ledger reconciliation |

| Month-end close | Period close process design and testing |

| Management reporting | GL reporting and FP&A module requirements |

| Audit preparation | Controls testing and UAT sign-off |

| Fixed asset accounting | Asset Management module requirements |

| Grant accounting | Oracle Projects and grant coding validation |

---

Real programme example — Northshire Police Oracle Fusion

During Discovery (Gate 0.2), the Finance BA documented the As-Is AP process. The finding: finance was manually recoding approximately 340 transactions per month for the CIPFA SERCOP return — a 3-day process with 12 coding errors per quarter.

The Finance BA did not just document the problem. They identified the root cause — no CIPFA SERCOP mapping at transaction level in the legacy system — and specified the Oracle Subledger Accounting (SLA) rules that would eliminate the manual process entirely.

The result: CIPFA SERCOP production reduced from 3 days to 4 hours. Coding errors: zero.

That is a Finance BA using accounting knowledge to drive system design. Not an IT professional. Not a generic BA. An accountant who understood what the CIPFA codes meant and why they mattered.

How to position for Finance BA roles

Three things every Finance BA CV needs:

1. Finance process experience described in ERP language — AP becomes "Accounts Payable and P2P process knowledge." Bank rec becomes "Cash management and sub-ledger reconciliation." Month-end close becomes "Period close and financial close process experience."

2. Any programme exposure — even small system changes count. A new reporting tool. A finance system upgrade. A process improvement project. Frame it using programme lifecycle language.

3. Evidence of structured thinking — requirements documents, process notes, gap analysis, risk registers. If you have produced any of these in your finance career, they belong on your CV.

Post in the Career Paths category if you have questions about this path.

Fall4U FCA FCCA — Founder, Future Defined Academy

CAREER PATH GUIDE 2 — WORKSTREAM LEAD

The Workstream Lead Path — What It Means to Own Delivery on an ERP Programme

Category: 🗺️ Career Paths

What a Workstream Lead actually does

A Workstream Lead is accountable for the delivery of a defined workstream on an ERP programme — Finance, Payroll, Data, or a combination.

They are not the most technical person in the room. They are the most accountable.

The Workstream Lead owns the delivery plan for their workstream. They manage the Finance BAs and functional consultants who work within it. They challenge the Systems Integrator when deliverables are late, incomplete, or not fit for purpose. They report to the Programme Board on status, risks, and issues. And when go-live comes — they are the person who says whether their workstream is ready.

A football manager analogy: the best managers were rarely the best players. The best Workstream Leads are not always the best Oracle consultants. They are people who understand what the workstream is trying to deliver — and have the governance and leadership skills to make it happen.

The governance layer the Workstream Lead owns

This is what separates a Workstream Lead from a senior Finance BA. The Workstream Lead does not just produce artefacts — they govern the programme.

RAID Register — Risks, Assumptions, Issues, Dependencies. The Workstream Lead maintains and escalates the RAID register for their workstream. They know which risks are critical, which issues need immediate resolution, and which dependencies are at risk of breaking the programme.

Critical Decisions Log — Major decisions that affect the workstream are logged, dated, and signed off. The Workstream Lead ensures nothing is decided informally and nothing significant is undocumented.

Programme Gate Sign-off — At each gate (0.2, 1.1, 1.2, 2.1, 2.2) the Workstream Lead confirms that their workstream has met the gate criteria before the programme proceeds. This is formal accountability — not a rubber stamp.

SI Management — The Workstream Lead manages the relationship with the Systems Integrator for their workstream. They challenge deliverables, raise formal issues, and escalate where the SI is not performing.

Executive Dashboard Reporting — The Workstream Lead produces or contributes to the weekly RAG status report for the programme board. They own the narrative for their workstream — what is green, what is amber, what is red, and what is being done about it.

Real programme example — Northshire Police

During SIT on the Northshire Oracle Fusion programme, the Workstream Lead identified that the compressed hours calculation for shift workers was producing incorrect payroll outputs. The defect (labelled CWM-HOURS-01) was raised as Priority 1 — critical — because it would have resulted in incorrect pay for over 400 officers at go-live.

The Workstream Lead did not accept the SI's initial response that it was a data issue. They escalated using the formal Defect Management process, commissioned an independent review, and held the SI accountable for resolution within 48 hours.

The defect was resolved. The go-live was not delayed. But it required a Workstream Lead who understood both the payroll accounting (what the output should look like) and the governance (how to formally escalate and hold the SI to account).

What accounting experience maps to Workstream Lead work

| Your accounting experience | Workstream Lead equivalent |

|---|---|

| Managing a finance team | Team leadership on a programme |

| Month-end close ownership | Delivery ownership and deadline management |

| Audit management | SI management and formal escalation |

| Board and committee reporting | Programme board reporting |

| Budget management | Programme cost management |

| Risk and controls | RAID register management |

How to position for Workstream Lead roles

Workstream Lead roles typically require:

- Senior finance experience (Finance Manager level or above)

- Some exposure to system change or ERP implementation

- Evidence of stakeholder management at senior level

- Understanding of programme governance and delivery

The FDA Workstream Lead pathway builds the governance knowledge and programme delivery capability that accounting experience alone does not provide.

Post in the Career Paths category if you want to discuss this path.

Fall4U FCA FCCA — Founder, Future Defined Academy

---

## CAREER PATH GUIDE 3 — FUNCTIONAL CONSULTANT

**Title:** The Functional Consultant Path — Where Accounting Knowledge Meets System Expertise

**Category:** 🗺️ Career Paths

---

**What a Functional Consultant actually does**

A Functional Consultant is the person who configures the ERP system to match what the business needs.

They run design workshops to understand finance requirements. They translate those requirements into configuration decisions. They build the system — within the constraints of the platform — to deliver what the business has asked for. And they support testing, resolve defects, and help users understand how the system works.

Functional Consultants typically specialise in one or two ERP systems and one or two functional areas. An Oracle Fusion Finance Functional Consultant understands GL, AP, AR, and related modules deeply — how they are configured, what the options are, and what the trade-offs look like.

---

**The difference between a Finance BA and a Functional Consultant**

The Finance BA writes the requirements. The Functional Consultant fulfils them.

The Finance BA documents what the process should look like. The Functional Consultant configures the system to make that process work.

In practice, the best Finance BAs and Functional Consultants work closely together — because the Finance BA needs to understand what is configurable, and the Functional Consultant needs to understand what the business actually needs.

For an accountant moving into ERP, the Finance BA path is typically the entry point. The Functional Consultant path usually follows after gaining programme experience and platform-specific knowledge.

---

**What accounting experience maps to Functional Consultant work**

| Your accounting experience | Functional Consultant equivalent |

|---|---|

| AP invoice processing | Oracle AP invoice workflow configuration |

| Payment runs | AP payment batch setup and bank integration |

| GL chart of accounts | GL segment structure and CoA design |

| Reconciliations | Cash management and ARCS configuration |

| Fixed asset accounting | Asset Management module configuration |

| Management reporting | OTBI and BI Publisher report design |

---

**The ERP landscape**

Functional Consultants typically specialise in one platform. The main platforms in the UK market:

**Oracle Fusion** — dominant in large public sector and corporate. High demand for Finance Functional Consultants.

**SAP S/4HANA** — dominant in large corporate and multinational. Complex configuration. High earning potential.

**Microsoft Dynamics 365** — common in mid-market. Growing public sector presence.

**Unit4** — specialist in UK public sector, housing associations, and not-for-profit. Smaller market but strong demand.

**Workday** — growing in UK public sector for Finance and HR combined implementations.

---

**How to position for Functional Consultant roles**

Platform knowledge is essential. The Functional Consultant pathway in FDA builds the conceptual understanding of ERP module configuration — the *why* behind configuration decisions — that accounting knowledge provides the foundation for.

Platform-specific navigation and configuration is learned on the job, through Oracle University or SAP Learning, or through hands-on programme experience.

*Post in the Career Paths category to discuss this path.*

*Fall4U FCA FCCA — Founder, Future Defined Academy*

---

## CAREER PATH GUIDE 4 — FINANCE SYSTEMS SPECIALIST

**Title:** The Finance Systems Specialist Path — The Most Underrated ERP Career for Accountants

**Category:** 🗺️ Career Paths

---

**What a Finance Systems Specialist actually does**

A Finance Systems Specialist owns the ERP and finance systems that an organisation runs on — day to day, not just during implementation.

They are the person the finance team goes to when the system is not doing what it should. They are the person IT goes to when a finance process needs to be understood before a system change can be made. They sit between the two — and they speak both languages.

Typical Finance Systems Specialist responsibilities:

- System support and user query resolution

- Period-end close support — ensuring system processes run correctly

- Report development and maintenance

- System upgrade management and testing

- Data quality monitoring and remediation

- Process optimisation — finding better ways to use existing system functionality

- New module or feature implementation

- Training and user documentation

This role exists in almost every organisation that runs an ERP system. It is typically permanent rather than contract. It is often the first ERP role an accountant moves into — and it is a strong stepping stone to Functional Consultant or Workstream Lead roles.

---

**Why this path is underrated**

Most ERP career content focuses on implementation roles — Finance BA, Consultant, Workstream Lead. These are contractor roles that are highly visible and well paid but require programme experience to access.

The Finance Systems Specialist is a permanent role that is almost always open, almost always underfilled by people who have both the accounting and system knowledge, and almost always a better fit for an accountant moving into ERP for the first time than a contract implementation role.

It is the path most accountants overlook. And it is the path that most naturally builds into the others.

---

**Real example — ARCS at DBIS**

On the DBIS Finance Transformation programme, Oracle ARCS (Account Reconciliation Cloud Service) was implemented to replace 12 manual Excel reconciliation templates across 847 GL accounts. After go-live, someone needed to own ARCS — to manage the matching rules, maintain the account profiles, resolve reconciliation exceptions, and ensure the NAO had the audit evidence they needed.

That person is a Finance Systems Specialist. They needed accounting knowledge to understand what each reconciliation was checking. They needed system knowledge to manage the ARCS configuration. And they needed controls awareness to ensure the output was audit-ready.

That combination — accounting, system, controls — is what a Finance Systems Specialist brings.

*Post in the Career Paths category to discuss this path.*

*Fall4U FCA FCCA — Founder, Future Defined Academy*

---

## CAREER PATH GUIDE 5 — CONTROLS & GOVERNANCE

**Title:** The Controls & Governance Path — Where Accounting Meets Audit in ERP Systems

**Category:** 🗺️ Career Paths

---

**What Controls & Governance means in an ERP context**

Every ERP system has a controls layer. It governs who can do what, what approvals are required, what audit trail is maintained, and how the organisation can demonstrate to its auditors that the system is operating as intended.

The Controls & Governance professional is the person who designs, implements, and assures that controls layer.

This is not a new concept for accountants. You already work within financial controls frameworks. You understand Segregation of Duties — the principle that no single person should be able to initiate, approve, and record a financial transaction. You understand audit trails. You understand the difference between a preventive control and a detective control.

What the Controls & Governance path adds is the technical knowledge to apply those concepts inside ERP systems — and the professional credentials (CISA, ISO 27001) that make that expertise formally recognised.

---

**What Controls & Governance professionals do on ERP programmes**

**During Design (Gates 1.1 and 1.2):**

- Design the Segregation of Duties matrix for the ERP system

- Define access control requirements — who can approve what, at what value threshold

- Review the system design for controls compliance

- Produce the User Access Control Matrix

**During Build (Gates 2.1 and 2.2):**

- Review the configured system against the SoD matrix

- Test access controls and approval workflows

- Validate that audit trail requirements are met

- Produce controls testing evidence for external audit

**Post go-live:**

- Monitor access and controls on an ongoing basis

- Support internal and external audit reviews

- Manage user access changes through a formal change control process

- Review controls effectiveness periodically

---

**The credentials**

**CISA — Certified Information Systems Auditor**

Issued by ISACA. The globally recognised credential for IT audit and information systems assurance. Directly relevant to ERP controls work. Builds on accounting and audit knowledge.

**ISO 27001 Lead Auditor**

The international standard for information security management. Increasingly required in public sector ERP environments. Provides a structured framework for assessing and assuring information security controls.

Both credentials are examined. Both require study. Both are achievable for qualified accountants who understand audit and controls frameworks — because the concepts are familiar, only the application to IT systems is new.

---

**Why this path is growing**

Regulatory requirements for ERP controls assurance are increasing. The public sector in particular — following high-profile failures in large ERP implementations — is investing significantly in controls and governance capability on transformation programmes.

The person who understands both the accounting controls framework and the ERP system it operates in is rare. That rarity makes this path valuable.

*Post in the Career Paths category to discuss this path.*

*Fall4U FCA FCCA — Founder, Future Defined Academy*

---

## CAREER PATH GUIDE 6 — TRANSFORMATION LEAD

**Title:** The Transformation Lead Path — Where Accounting Knowledge Becomes Strategic Impact

**Category:** 🗺️ Career Paths

---

**What a Transformation Lead actually does**

A Transformation Lead is accountable for an enterprise-wide change programme — not just the system, but the people, processes, governance, and outcomes that the system is meant to support.

They operate at board and director level. They manage executive stakeholders. They govern programme delivery across multiple workstreams. They ensure that the transformation achieves what it was commissioned to achieve — not just that the system goes live.

The Transformation Lead holds a critical distinction in their thinking: the difference between system delivery and business change. A system can go live on time, on budget, and technically correct — and the transformation can still fail. Because the people did not change how they work. Because the processes were not redesigned. Because the benefits were never realised.

The Transformation Lead is the person responsible for ensuring that does not happen.

---

**What makes an accountant a strong Transformation Lead**

The Transformation Lead needs to understand three things simultaneously:

1. What the organisation does financially — how money moves, how it is controlled, how it is reported

2. How the technology supports that — what the ERP system does and what it does not do

3. How to change an organisation — stakeholder management, change management, benefits realisation

Accountants start with a significant advantage on point 1. The FDA pathway builds point 2. The Transformation Lead programme builds point 3.

---

**The strategic questions a Transformation Lead asks**

These are the questions that distinguish a Transformation Lead from a Workstream Lead or Programme Manager:

- Is the organisation actually going to work differently after this programme — or just use a different system to do the same things?

- What are the measurable benefits this programme was commissioned to deliver — and are we on track to realise them?

- Does the operating model we are designing reflect what the organisation needs to be, not just what it is today?

- Are the executive stakeholders genuinely committed to the change — or are they expecting the programme to deliver without changing how they work?

- What is the plan for after go-live — because that is when the real work of transformation begins?

---

**The journey to Transformation Lead**

This is not typically a first ERP role. The most common journey:

Finance Manager or Financial Controller → Finance BA → Senior Finance BA or Workstream Lead → Transformation Lead

Some people arrive via a different route — senior finance professionals who take on transformation accountability from within an organisation rather than coming in as an external consultant. Both routes are valid.

The FDA Transformation Lead pathway is the most advanced programme in the academy. It builds on everything that comes before it.

*Post in the Career Paths category to discuss this path.*

*Fall4U FCA FCCA — Founder, Future Defined Academy*

---

0 comments

WHICH CAREER PATH IS YOURS?