When we review a finance function with the CFO and business leaders, the list of possible improvements grows quickly. Reporting is slow, forecasting consumes too much time, data is unreliable, and several systems require attention. The difficult decision is where to use limited capacity without weakening reporting, control, or daily operations.
The people who understand the processes best also close the books, deliver forecasts and support the business. In a larger group, the work depends on local finance teams, a shared service center, corporate functions and external providers. A transformation program has to respect these constraints. A plan that assumes unlimited capacity will slip or transfer risk into day-to-day operations.
We start by asking where the finance function is losing the most time, carrying avoidable cost or leaving management without the information it needs. The target state gives direction. The current situation shows which problems stand in the way and which of them need attention first.
Address weaknesses in financial reporting first
Recurring errors or control weaknesses in financial reporting take priority. We would address these issues even while the broader transformation program is being developed. Reliable reporting gives the CFO the stability and credibility needed to lead the wider change. The response needs to match the cause. A recurring reconciliation error calls for a focused correction. Inconsistent accounting practices across entities require common policies, clearer ownership and changes to consolidation. The aim is to contain the risk and remove its source before scarce capacity is committed elsewhere.
Identify where problems have the greatest impact
The monthly close provides a useful starting point because its problems are visible and measurable. In one company, the close can take ten working days because reconciliations are manual and inputs arrive late. In a larger group, different reporting practices, duplicated controls and dependencies across countries delay group reporting. Management receives the figures late and then spends valuable meeting time establishing what they mean.
Forecasting can create a similar problem. Sales, operations and finance use different assumptions or update their inputs at different times. Parts of the forecast are already outdated when the process ends. Leadership then discusses the figures and assumptions when it needs to decide how the business will respond. Broad statements about data quality provide little help in choosing an initiative. We identify the data that creates the problem, where the error enters the process and which decision is affected. The same customer can be recorded differently across legal entities. Product profitability is calculated with several definitions. A shared service center spends hours correcting source data that should have been right when it entered the process. The consequences make the priority clearer and give the improvement a measurable purpose.
Several problems cross functional boundaries. Order-to-cash involves sales, customer service, operations and finance. Customer information is entered in one system, orders are managed in another and invoices are produced elsewhere. Breaks in that flow become visible through overdue receivables, weak cash conversion and reporting errors, so the CFO usually ends up with the problem. The solution has to reach the point where the error occurs. Depending on the cause, the work could involve clearer accountability, a change in working practice, better source data or a repair to an integration.
System investments expose the cost of confusing causes and symptoms. Delayed reporting can stem from an outdated tool, inconsistent charts of accounts, unclear responsibilities or an excessive number of manual controls. A new tool improves the parts of the process that technology is actually causing. Before approving an initiative, the CFO needs to state the problem, its current cause and the measurable improvement expected.
Prioritize initiatives using three tests
We use three tests when finance leaders need to choose between initiatives:
Two initiatives can promise a similar benefit and place very different demands on the organization. One can be delivered in three months by a focused team. Another requires changes across several processes, data structures and systems. The first deserves priority if it releases capacity or resolves an immediate constraint. Timing for the larger initiative needs to reflect the work required for credible delivery.
The change footprint also affects the decision. A project involving several countries, business units or service providers creates more coordination and a greater cost of disruption. Phased implementation can contain this exposure and provide evidence before the approach is extended. The phases need to follow operational boundaries and real dependencies. A generic pilot in an easy part of the business proves little about the areas where the change is hardest.
ERP decisions require this level of precision. Before an ERP replacement enters the program, leadership needs to define the problems it will solve and the part it plays in the target state. This shapes scope, expected benefits and the sequence of related initiatives. Treating ERP as the transformation goal pushes process choices and data decisions into the implementation, where they become more expensive and harder to resolve.
The same logic applies to automation and analytics. Automated reporting can depend on a common chart of accounts and consistent definitions. Releasing capacity for analysis requires a clear view of which manual activities can end and which processes need redesign. Better forecasting depends on ownership of business drivers and timely input from sales and operations. Technology choices follow these operating decisions.
Where inconsistent definitions and late inputs are extending the monthly close, we would normally clarify ownership, deadlines and reporting rules before investing in automation. Unnecessary controls can be removed as the process stabilizes, followed by automation of high-volume reconciliations. Reporting can be redesigned once the underlying data is dependable. The order changes when the delay comes from a system limitation or a specific control failure. The program needs to reflect the actual cause.
Leadership must also decide what can wait. Every initiative has a sponsor and usually a sound rationale. The combined demand will still exceed the capacity available. Deferring some work and stopping low-value activity protects the initiatives that matter most. This is where prioritization becomes visible in resource allocation and management attention.
Build the program around deliverable outcomes
After leadership has set the priorities, related initiatives can be grouped into a limited number of work areas. A work area might cover the monthly close and reporting, ownership of critical data, or the allocation of finance capacity. System changes belong with the process and business outcome they support. The link to the target state remains visible throughout delivery.
Each work area needs a defined outcome, concrete deliverables, known dependencies and named resources. Milestones mark an operational change: a new close process is in use, an old control has ended, or management receives information earlier. Completing a workshop, design document or system configuration shows progress. The business result starts when the new solution works in daily operations.
The finance calendar belongs in the plan. Year-end close, budgeting and other high-pressure periods restrict the people available for transformation work. External support can cover a temporary capacity or capability gap. Accountability for decisions and knowledge of the solution must remain with the organization that will operate it.
Prioritization is complete when leaders can explain the purpose and sequence of each initiative and name the work they have deferred. The finance organization then has a program it can deliver while meeting its current obligations.




