The finance talent shift from processing to analysis was announced roughly every year for two decades before it actually began happening, which is why finance leaders learned to treat it as a slogan. "Business partner, not bookkeeper" appeared in enough conference agendas and consulting decks to become background noise. What changed around the middle of the 2010s was that the processing work started genuinely disappearing, and organisations discovered they had no plan for the people who had been doing it. The mechanism was unremarkable: shared service centres had already moved transactional work out of local finance teams, cloud suites removed a layer of reconciliation, bank feeds killed manual statement matching, and robotic automation took the residue — the copying between systems that no integration project had ever justified. Each step removed a slice of work that had occupied qualified people for years. What replaced it was not a smooth transition into analysis. It was a gap.
The skills problem nobody costed
The assumption embedded in every business case was that finance staff freed from processing would move into analytical roles. The assumption embedded in every actual outcome was different: some did, most did not, and the organisation had not planned for either. The reason is that processing and analysis are not adjacent skills. A strong accounts payable supervisor is excellent at controls, exception handling, supplier relationships and closing on time under pressure. None of those transfer automatically into building a driver-based forecast, questioning a commercial assumption or presenting an uncomfortable finding to a business unit head who outranks them. The capabilities that actually define the new roles are specific: understanding the commercial model well enough to know which numbers matter, data literacy sufficient to work with the source rather than with a report someone else prepared, the ability to structure a question rather than answer one, and — the one that is hardest to hire and rarely taught — the confidence to tell an operating executive something they do not want to hear and make it stick. Organisations that treated this as a training problem generally failed. A three-day analytics course does not produce a business partner. Organisations that treated it as a role design and career path problem did better, because the constraint was never tooling.
The two-tier outcome
What happened in most finance functions was a split rather than a transformation. A minority of staff moved into genuine analytical and partnering roles, usually those who had already shown commercial curiosity and had a relationship with the business. They thrived, and their jobs became noticeably more interesting. A larger group ended up in a hybrid state: doing less processing but not much more analysis, producing reports rather than insight, with roles that had been hollowed out rather than upgraded. Their work looked analytical from the outside — they operated spreadsheets and dashboards — but the intellectual content was still transactional. And a third group left, or was made redundant, which is the part the business cases anticipated and the part organisations handled least well. The practical consequence is that finance functions ended up hiring analytical capability externally while carrying people internally whose roles had lost their purpose. That is an expensive outcome and it was largely predictable. The organisations that avoided it did one thing differently: they identified who could make the transition, and who could not, early and honestly, rather than announcing a transformation and hoping the population sorted itself.
What the new finance function actually needs
The functional shape that emerged is reasonably consistent across organisations that got it right. A small, strong controllership core — technical accounting, statutory reporting, tax, audit relationship. This work did not disappear and it got harder as reporting requirements multiplied. A centralised or outsourced transaction engine, measured on cost per transaction, cycle time and error rate rather than on headcount. A data and systems capability inside finance, not borrowed from IT. Someone who owns the chart of accounts, the master data, the reporting layer and the definitions. This role barely existed in 2015 and is now frequently the most valuable person in the function. And business partners embedded with operating units, whose performance is judged on the quality of decisions influenced rather than on reports delivered. The role that fell away in the middle was the one that had accounted for the bulk of the function: the qualified accountant doing largely repetitive work with occasional judgement.
| Job | Focus |
|---|---|
| Transaction engine | Process routine work and route exceptions. |
| Controllership | Own accounting judgement and the control environment. |
| Data ownership | Maintain consistent definitions and reliable records. |
| Business partnering | Interpret results in their operating context. |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
Practical Guidance for Finance Talent Strategy
- Assess your existing team against the capabilities the new roles actually require, individually and honestly. Commercial understanding, data fluency and the willingness to challenge. Do this before you announce a transformation, not after.
- Design the target operating model and the roles first, then map people to it. Transformations that start with automation and work out the people implications later produce hollowed-out roles and expensive attrition of the wrong people.
- Build a genuine data capability inside finance. One person who owns definitions, master data and the reporting layer does more for analytical quality than a dozen dashboards.
- Change what you measure before you change what people do. If business partners are still assessed on report delivery and close timetables, they will keep doing processing work with better tools.
- Be explicit about who is not making the transition, and manage it properly. Leaving people in roles that no longer have content is worse for them and worse for the function than an honest conversation and a fair exit.
- Give partners commercial exposure, not just training. Rotations into operations, participation in pricing or tender decisions, and sitting in the business unit's meetings do more than any course.
- Recruit for judgement and communication, not only for qualification. The technical accounting bar is necessary for controllership and largely irrelevant for partnering.
- Keep a deliberate path for technical accountants. Not everyone should become a business partner, and losing technical depth while chasing analytics is a real failure mode with audit consequences.
The Regional Dimension
The Gulf version of this shift has a different starting point and a different constraint set. Regional finance functions were, on average, more processing-heavy for longer. Multi-entity structures — mainland companies, free-zone entities, Saudi subsidiaries, branches across several Gulf states — generate duplicated transactional and statutory work that a single-country business does not carry. Add manual interaction with government and bank portals for wage protection payroll submission, gratuity provisioning, social insurance contributions and nationalisation reporting, and a substantial share of finance headcount was occupied by compliance mechanics rather than accounting judgement. The automation wave therefore hit harder here in proportional terms. It also collided with two local realities. First, workforce mobility. Employment-linked residency means turnover is high, and analytical capability built in one organisation tends to leave it. Investment in developing business partners has a shorter payback period in the Gulf than in markets where people stay a decade, which pushes organisations toward hiring ready-made capability — at a premium, and with the same retention problem one level up. Second, nationalisation policy. Emiratisation and Saudisation targets shape hiring, and finance is one of the functions where the targets are met. That creates a genuine opportunity if the roles being filled are the new analytical ones with proper development paths, and a genuine failure mode if nationals are recruited into exactly the transactional roles that automation is about to remove. The organisations handling this well are building national talent into controllership, data ownership and partnering tracks, which is both better policy compliance and better workforce planning. The third factor is the regional shared services model itself. Dubai, Riyadh and Cairo host service centres covering multiple countries, and the analytical layer that should sit above them is frequently still located at headquarters elsewhere. Moving analysis closer to the region — where the commercial context, the regulatory calendar and the customer relationships actually are — is one of the larger unexploited opportunities in Gulf finance functions.
The honest limitation
There is a case that this entire narrative is oversold, and it deserves a hearing. Most organisations do not need a large analytical finance function. They need accurate numbers, produced on time, with controls that work. The volume of genuinely valuable analytical work in a mid-sized business is smaller than the transformation literature implies, and a function that redirects everyone toward "insight" can end up producing a great deal of commentary that nobody acts on while the close slips and the controls weaken. There is also a status problem inside the argument. "Business partner" is presented as a promotion from "accountant," which quietly devalues technical accounting expertise at exactly the moment reporting requirements are becoming more demanding. Functions that lost their technical depth chasing partnering roles found out during an audit. The defensible version of the shift is narrower than the slogan: automate the work that should not require a person, keep controllership strong and properly staffed, and build an analytical capability sized to the decisions your business actually makes — which for many organisations is a handful of people, not a department.
Common Questions
How many people should move into business partnering?
Fewer than most transformation plans assume. Size it against the number of operating units that make genuinely finance-relevant decisions and the cadence of those decisions. A partner with no decisions to influence will generate reports to justify the role.
Can transactional staff be retrained into analytical roles?
Some can, and they tend to be outstanding at it because they understand the underlying data better than an external hire ever will. But it is not a majority, and identifying which individuals can make the move requires an honest assessment rather than a blanket training programme. Pretending everyone can is unkind to the people who cannot.
What is the most useful early investment?
A single owner for finance data and definitions. Analytical work fails more often from inconsistent definitions and unreliable master data than from a lack of skill or tooling, and this role fixes the constraint that every other investment depends on.
How does AI change the picture again?
It moves the boundary upward. The first wave removed data entry and matching; the current wave automates variance commentary, reconciliation explanation, first-draft analysis and much of the report production that hollowed-out roles were still doing. What remains defensible is judgement that requires context the system does not have — knowing which question matters, whether a number is plausible, and how to change a decision. Functions that stopped at "report faster" after the first wave are about to have the same conversation a second time, with less room to manoeuvre.
Finance Talent Strategy — automation removes the work long before the organisation decides what the people doing it are supposed to become, and that gap is where the value leaks out.