When ERP Programs Need Architecture Guidance Beyond Implementation

Your global ERP programme is running.

The implementation is underway. The system integrator is on site. The go-live date is in the calendar.

Then something starts to feel wrong.

Configuration decisions that should have been straightforward are taking longer than expected. Issues that get resolved in one area reappear in another. The programme team is working hard — and the SI is working hard — but the underlying problem does not go away.

This is one of the most common patterns in global ERP programmes that encounter Brazil for the first time.

And it rarely has anything to do with the quality of the implementation team.

What Brazil Does to a Global ERP Programme

Global ERP templates are built to work across multiple markets.

They are well-designed, well-tested, and they work — in every market they were built for.

Brazil creates gaps against them. Not because the template is wrong. Because Brazil's fiscal and regulatory environment is unlike any other market the template was designed for.

A single transaction in Brazil can simultaneously touch supply chain operations, financial accounting, tax compliance, intercompany relationships, and regulatory reporting — each with its own requirements, its own timing, and its own fiscal document obligations.

When global templates are applied without evaluating how they interact with Brazil's specific requirements, these interactions do not always behave as expected.

The gaps they create are not visible immediately.

They surface later — during build, during testing, or after go-live — when they are significantly more expensive to address.

Why Configuration Alone Cannot Resolve It

System integrators are structured to deliver ERP programmes through defined implementation methodologies.

Their work focuses on configuring modules, implementing business processes, deploying integrations, and supporting deployment and testing activities.

This approach works well when the process model is already clearly defined and aligned with the local environment.

The challenge appears when the programme encounters questions that are not primarily about configuration:

• How should the global operating model interact with Brazil's NF-e and SPED requirements?

• How should cross-functional processes be designed across supply chain, finance, and tax simultaneously?

• How should the global template be evaluated against Brazil's fiscal transaction architecture before build begins?

These are not configuration questions.

They are architectural decisions about how the solution should be designed to work in Brazil — and they need to be answered before the configuration work begins, not after it has produced results that do not align.

The Role of Architectural Guidance

When a programme reaches this point, what it needs is not more configuration effort.

It needs someone to step back and evaluate the broader structure of the solution — independently of the implementation workstream.

This means reviewing end-to-end transaction flows across multiple functions, understanding how the global process design interacts with Brazil's fiscal requirements, and identifying where the gaps between them are creating the symptoms the programme is experiencing.

In many cases, resolving the issue does not require significant rework.

It requires reframing how a specific process is structured — so that the ERP system can support it correctly within Brazil's regulatory environment.

What This Looks Like in Practice

The programmes that navigate Brazil most effectively are those that introduce architectural guidance early — before the design is locked in and before the gaps have had time to compound.

At that stage, the decisions are still open. The cost of course correction is low. And the programme team can move forward with confidence that the solution has been designed correctly for the environment it will operate in.

For programmes that are already mid-implementation or post go-live, the same principles apply — with the added urgency that comes from a system that is already live or nearly so.

The question in either case is the same: is the solution designed correctly for Brazil, or is it producing symptoms that configuration is not resolving?

Final Insight

Brazil does not introduce complexity into ERP programmes.

It surfaces gaps between global process design and what Brazilian fiscal requirements actually demand.

When those gaps are identified and addressed at the architectural level — rather than managed through configuration workarounds — the programme can move forward on stable foundations.

The design is either right or it is not. Configuration can only work with what the design allows.

ASDM Solution operates as an independent ERP transformation architecture advisory practice, focused exclusively on Dynamics 365 Finance programmes in Brazil.

If your organisation is facing similar challenges — whether you are planning your Brazil rollout, navigating go-live pressure, or dealing with issues that configuration is not resolving — we'd be glad to have a conversation.