LUNARI
Consultation · ERP implementation advisory

ERP implementations are expensive. Getting the design wrong is even more expensive.

An ERP implementation touches almost every part of Finance. Your chart of accounts. Your transaction flows. Your controls. Your reporting. Your close. Your data. And ultimately, how your finance team works every day.

Yet many of the decisions that determine whether Finance will actually work are made months before go-live. Our ERP Implementation Advisory helps you get those decisions right.

The reality of ERP implementation

Significant time, capital and capacity — without the operational improvement expected from them.

Implementation risk

Budget overruns

Additional customization, integration rework and expanding scope

Implementation risk

Schedule delays

Data remediation, design changes and testing bottlenecks

Implementation risk

Operational disruption

Processing delays, reporting issues, reconciliation problems and extended close cycles

And even when the ERP goes live successfully, Finance may still be left with spreadsheets, manual reconciliations and workarounds.

Why ERP implementations fail

Rarely caused by the software alone.

A successful go-live does not always mean a successful finance transformation.

  • Bad data and architecture carried into the new system
  • Over-customization of legacy processes instead of redesigning them
  • Weak upstream data controls that push errors downstream into Finance
  • Treating ERP as an IT project instead of a finance operating-model transformation
  • Poor user adoption and change design
Independent finance-side advisory

Someone needs to make sure the system, the technology and the accounting translate into a finance operating model that works.

Your implementation partner knows the ERP.

Your IT team understands the technology environment.

Your finance team understands the business and accounting.

We work alongside your CFO, Controller, finance transformation team and implementation partner to independently challenge and validate the decisions being made throughout the ERP program. We are not there to replace your implementation partner — we are there to help you get more from the implementation.

How we support your ERP implementation

Eight points of independent finance oversight.

01

ERP readiness & finance assessment

Before configuration begins, we assess whether Finance is actually ready for implementation.

We look at your:

  • Current finance processes
  • Chart of accounts
  • Entity and reporting structures
  • Master data
  • Existing systems and integrations
  • Manual processes and spreadsheets
  • Accounting requirements
  • Controls
  • Reporting requirements
  • Close process

This identifies issues that should be addressed before they are designed into the new ERP.

02

Future-state finance design

An ERP implementation should not simply recreate today's finance function on a new platform. We help define how Finance should operate after implementation.

Process design
How should P2P, O2C, R2R, treasury, intercompany and other finance processes work end to end?
Finance architecture
What belongs in the ERP? What belongs in surrounding applications? How should they connect?
Accounting design
How should transactions, entities, dimensions, currencies and accounting requirements be structured?
Controls
Which controls should be embedded into workflows and systems?

The objective is to design the future state first, then configure technology around it.

03

Requirements & design review

Requirements are where many future ERP problems begin. We independently review whether Finance requirements have been translated correctly into the proposed system design.

We challenge questions such as:

  • Does this process work end to end?
  • Does the proposed configuration produce the right accounting?
  • What happens when there is an exception?
  • What happens across entities and currencies?
  • How will Finance reconcile it?
  • What evidence will auditors see?
  • What happens at month-end?

“The system can do it” is not the same as “the design will work.”

04

Data & migration readiness

Moving poor data into a new ERP does not solve the data problem. We review the structures and data that Finance will depend on after go-live.

  • Chart of accounts
  • Customers
  • Suppliers
  • Legal entities
  • Accounting dimensions
  • Opening balances
  • Outstanding transactions
  • Fixed assets
  • Intercompany balances
  • Historical data

The objective is not simply to migrate data. It is to make sure Finance starts the new environment with data it can trust.

05

Controls & governance

Controls should not be added after the ERP has been configured. We help embed control requirements into the design.

  • Approval workflows
  • Segregation of duties
  • User access
  • Accounting approvals
  • Master-data governance
  • Exception management
  • Automated controls
  • Audit trails
  • Period-end controls

This helps prevent the organization from having to rebuild the control environment after go-live.

06

Finance UAT & scenario testing

A transaction successfully posting is not enough. Finance needs to know what happens when things don't go according to plan.

We help develop and review testing around realistic scenarios:

  • Normal transactions
  • Exceptions
  • Reversals
  • Corrections
  • Foreign currency
  • Intercompany
  • Period-end transactions
  • Failed integrations
  • Approval exceptions
  • Reconciliations
  • Reporting
  • Close

The question isn't “did the test script pass?” It is “can Finance actually operate this way?”

07

Go-live readiness

Before go-live, we help Finance independently assess whether the organization is ready to operate on the new environment.

  • Processes
  • Data
  • Accounting
  • Controls
  • Integrations
  • Reporting
  • Users
  • Reconciliations
  • Cutover
  • Close readiness

The result is a clear view of outstanding finance risks and what needs to be resolved before, during or immediately after go-live.

08

Post-go-live & first close

Go-live is not where finance transformation ends. It is where the design meets reality. The first close can expose:

  • Manual workarounds
  • Unexpected accounting
  • Integration issues
  • Reconciliation problems
  • Reporting gaps
  • Control weaknesses
  • User-adoption problems

We help Finance stabilize the environment, prioritize issues and distinguish temporary go-live problems from structural design issues.

Where we fit

You do not need another implementation team. You need someone looking at the implementation through the finance lens.

Your implementation partner

Configures and implements the ERP.

Your IT team

Manages technology, infrastructure, security and integrations.

Your finance team

Owns accounting, reporting, controls and business requirements.

Our role

Independent finance transformation and implementation advisory across the three.

We help translate between the system, the accounting and the way Finance actually needs to operate.

Support across the ERP lifecycle

Engage across the full lifecycle, or at the point where independent finance oversight is needed.

Before implementation
  • ERP readiness
  • Current-state assessment
  • Process redesign
  • Finance architecture
  • Data readiness
  • Vendor / solution evaluation
During implementation
  • Finance design review
  • Requirements validation
  • Accounting design
  • Controls review
  • Data migration review
  • UAT & scenario testing
Go-live & beyond
  • Go-live readiness
  • Cutover review
  • First-close support
  • Issue prioritization
  • Process stabilization
  • Post-implementation optimization
Already midway through?

You don't need to start again.

If the project is already underway, we can perform an independent ERP Finance Health Check.

  • What has already been designed
  • Whether Finance requirements are adequately represented
  • Key accounting and control risks
  • Data and migration readiness
  • Process and integration gaps
  • UAT quality and coverage
  • Reporting readiness
  • Remaining go-live risks

Then we separate what needs attention now, what must be resolved before go-live, and what can be addressed during stabilization.

Particularly valuable when the project dashboard says green, but the finance team isn't convinced.

Already live, but struggling?

Before replacing the ERP, understand why.

If spreadsheets have returned, reconciliations have increased, reporting is difficult or Finance is creating workarounds, the ERP itself may not be the problem. We assess whether the root cause sits in:

  • Configuration
  • Process design
  • Data
  • Integration
  • Controls
  • Reporting
  • User adoption
  • The finance operating model
  • Or genuinely: the ERP

Replacing a system without understanding the root cause risks rebuilding the same problems on another platform.

What success looks like

A successful implementation is not simply one that goes live.

Transactions flow correctly.
Accounting works as intended.
Finance can reconcile the numbers.
Controls are embedded into the process.
Reporting works without unnecessary manipulation.
Users can operate the system effectively.
Month-end works.
Manual work decreases rather than moves somewhere else.

And the organization has a finance architecture capable of supporting what comes next.

Don't wait until go-live to discover the design doesn't work.

ERP decisions made today can shape how Finance operates for years. Whether you are preparing for implementation, already midway through one, approaching go-live or trying to recover an implementation that has not delivered what you expected, we can help you identify the risks before they become more expensive to fix.

Independent finance-side ERP advisory · Think in systems, not silos