Finance Business Systems Analyst

A Finance Business Systems Analyst sits between a company's finance team and its IT team, making sure the software finance uses — general ledger and accounting systems, budgeting and forecasting tools, expenses, purchase-to-pay, reporting dashboards — actually does what accountants need it to do. Day to day that means working out what finance staff are trying to achieve, translating it into something a system can do or a developer can build, testing changes before they go live, and fixing things when reports don't reconcile. The role exists in large corporates, banks, insurers, retailers, universities, NHS trusts, councils, consultancies and software vendors — essentially anywhere the finance function is big enough that its systems need dedicated support.

Starting salary: £26k–£35k
Live graduate jobs: 1 open now
Main way in: Finance or technology graduate schemes at large employers…
They usually ask for: A degree is usually expected but the subject matters less than…

Approximate graduate salary

Typically somewhere around £26,000–35,000 to start, though this varies widely. Graduate schemes at large financial services firms and London-based roles sit at the upper end or above it; public sector, charity and regional roles often sit lower. Consultancy entry salaries vary a great deal by firm.

What you'd actually do

Sitting with finance staff (management accountants, accounts payable clerks, FP&A analysts) to understand a problem — for example, that the monthly cost-centre report takes three days to produce manually — and writing up what the system needs to do differently
Writing requirements documents and process maps: plain-English descriptions of how a process works now and how it should work, often with a flow diagram, that a developer or a system configurator can build from
Configuring parts of the finance system directly — setting up new cost centres, chart-of-accounts codes, approval workflows, user permissions, or building a report in the system's reporting tool
Testing: building test scripts, running transactions through a test environment to check the numbers come out right, and coordinating 'user acceptance testing' (UAT) where finance staff try the change before it goes live

Show 3 more

Investigating things that have gone wrong — a batch of invoices that didn't post, a feed from a sales system that didn't reconcile to the ledger, a report showing a different total from last month — which usually means tracing data through several systems
Pulling and checking data with SQL or Excel to prove whether a discrepancy is a system fault, a data problem or someone entering things incorrectly
Attending project and change meetings, writing user guides, and running short training sessions when a new module or process goes live

How graduates get in

Finance or technology graduate schemes at large employers (banks, insurers, retailers, utilities, FMCG, public sector bodies) that include a rotation in finance systems, finance change or finance transformation — a common route, though the specific rotation is often allocated rather than chosen
Direct entry as a junior/graduate business analyst or finance systems analyst, usually in an internal finance function or a shared service centre — common, and often advertised without the word 'graduate' in the title
Starting in a finance operations role (accounts payable, accounts receivable, management accounts, financial control) and moving sideways into systems work after a year or two, because you already know how the processes and the ledger work — very common and arguably the most reliable route
Joining a consultancy or systems implementation partner as a graduate analyst working on ERP or finance system projects for client organisations ('ERP' = enterprise resource planning, the large integrated business software that includes finance, procurement and HR modules)

Show 2 more

Joining a finance software vendor in an implementation, support or product role and moving to a client-side systems analyst job later — less common as a first step but a solid entry point
Starting in general IT support or data analysis and specialising into finance systems — happens, but you will need to build the accounting knowledge deliberately

What employers ask for

A degree is usually expected but the subject matters less than people assume. Accounting and finance, business, economics, information systems, computer science, maths and management are all common; other subjects are accepted where you can show numeracy and an interest in systems
Grade requirements vary a lot — some graduate schemes still ask for a 2:1 and a set number of UCAS points, while direct-entry vacancies often ask only for a degree or relevant experience, and some drop the degree requirement entirely if you have finance systems experience
Demonstrable Excel ability beyond the basics (lookups, pivot tables, handling large exports) is asked for almost everywhere; SQL is frequently requested and sometimes essential
Some understanding of double-entry bookkeeping and how a general ledger works — you don't usually need a qualification on day one, but you need to know what a journal, an accrual and a reconciliation are, or be ready to learn fast

Show 2 more

Professional qualifications vary by employer: some support an accounting qualification (ACCA, CIMA, ICAEW, or CIPFA in the public sector), others support business analysis certification such as BCS or IIBA, and some support neither. Ask at interview rather than assuming
Relevant experience — a placement year, internship or part-time role in a finance team, a shared service centre or an IT support function — carries real weight, especially for direct-entry roles

Skills that matter

Understanding accounting processes end to end

You can't fix a posting error or design a workflow if you don't know how an invoice becomes a ledger entry and eventually appears in the management accounts.

Requirements gathering and questioning

Finance users typically describe the solution they imagine rather than the problem they have, so the job is largely about asking 'why do you need that?' until the real requirement appears.

SQL and data investigation

Most of your problem-solving involves pulling records from a database or a system export and comparing them to work out where numbers diverged.

Structured testing

A finance system change that goes wrong can misstate reported figures or stop suppliers being paid, so being methodical about test cases and evidence is a core part of the job rather than an afterthought.

Writing clearly for two audiences

The same change has to be explained to a developer in precise technical terms and to a finance manager in terms of what it means for their month-end.

Working through disagreement calmly

Finance and IT often have different priorities and timescales, and a large part of the role is holding the middle ground when a deadline, a budget and a control requirement conflict.

Putting these on a CV? We counted which skills 12,914 live graduate adverts ask for, and what to do with the answer — part of our application advice.

Where it leads

Graduate or junior analyst: supporting a specific system or module, doing testing, data checks, user queries and small configuration changes under supervision.
Business systems analyst / finance systems analyst: owning a system area or process end to end, leading requirements work for smaller changes, and being the person finance goes to for that area. Reaching this point commonly takes a couple of years, but it varies widely with employer size and how much project work is going on.
Senior analyst or lead analyst: running the analysis workstream on larger projects such as an ERP upgrade or a new consolidation tool, and mentoring junior analysts.
From here the path forks and people genuinely go different ways: into finance systems management or finance transformation (leading change programmes for the finance function), into project or programme management, into product ownership, into data and reporting leadership, or back into core finance with a systems specialism — which can be a strong position if you also complete an accounting qualification.
Longer term, experienced people move into roles like Head of Finance Systems, finance transformation lead, ERP consultant (often at a consultancy or vendor, frequently at higher pay), or a broader IT leadership role. Timescales here vary enormously and depend far more on the projects you happen to be on than on years served.

What people get wrong

“It's a coding job in disguise, so you need a computer science degree.”

Most finance systems analysts write little or no application code. You configure off-the-shelf systems, write queries, and specify changes for developers to build. Deep accounting process knowledge is usually more valuable than programming ability — though SQL is a genuine advantage.

“It's a back-office job with little contact with people.”

It is one of the more conversation-heavy roles in a finance function. Much of the week is spent interviewing users, running workshops, chasing decisions, managing expectations about what can be delivered before month-end, and training people. Analysts who dislike that side of it tend not to enjoy the role.

“You'll be building shiny new systems.”

A lot of the work is maintaining, patching and slowly improving systems that are older than you are, and dealing with the awkward interfaces between them. Full replacements happen, but they are occasional events, and even then much of the effort goes into cleaning up historic data and mapping old codes to new ones.

“It's a lesser alternative to becoming an accountant.”

They're different tracks, not a hierarchy, and they overlap. Some employers actively want systems analysts who are part-qualified or qualified accountants, and people move between the two. The systems route also opens doors into consultancy and transformation work that pure accounting roles don't.

Where this varies

The role looks quite different depending on where you do it. In-house at a large corporate you support a defined set of systems for one organisation, work to its month-end and year-end rhythm, and build deep knowledge of one finance function. At a consultancy or software implementation partner you work on client projects, travel or work on client sites more often, see many different setups in a few years, and work to project deadlines rather than accounting cycles. In the public sector (NHS trusts, local authorities, universities) the systems, terminology and reporting rules differ — CIPFA rather than CIMA, different statutory reporting — and change tends to move more slowly with more governance. Job titles are also inconsistent: near-identical work is advertised as Finance Systems Analyst, Business Systems Analyst, Finance Change Analyst, ERP Analyst, Financial Systems Support Analyst or simply Business Analyst (Finance), so search on several titles. Finally, how technical the role is varies a lot — at some employers you will spend most of your time in SQL and system configuration, at others almost all of it in workshops and documents with a technical team doing the build.

See all 1 live Finance Business Systems Analyst jobsFrom employers' own careers sites, updated daily Tailor your CV for this roleFree with an account, 3 a month

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.