Functional governance in Business Central SaaS is not an abstract concept: it is the discipline that ensures the ERP evolves in an orderly, sustainable manner that is aligned with the business.
Without governance, Business Central becomes a collection of patches.
With governance, it becomes a living platform that drives decisions.

Functional governance in Business Central SaaS is not an abstract concept: it is the discipline that ensures the ERP evolves in an orderly, sustainable manner that is aligned with the business.
Without governance, Business Central becomes a collection of patches.
With governance, it becomes a living platform that drives decisions.

1. What functional governance really means in Business Central SaaS

It is the framework that guides how processes are designed, how changes are approved, how responsibilities are assigned and how the ERP evolves over time.
Good governance answers questions such as:

• What is the business impact of this change?
• What is the ERP impact?
• Who approves it?
• How is it documented?
• How is it measured?
• How does it affect future scalability?

Governance is the invisible architecture that keeps Business Central healthy.

2. Real examples (practical cases)

✔ Case 1: Inventory configuration changes

Without governance:

• valuation inconsistencies,
• accounting discrepancies,
• blocked internal audits.

With governance:

• impact assessment,
• sandbox testing,
• documentation,
• committee approval,
• controlled deployment.

✔ Case 2: Proliferation of custom fields

Without governance:

• duplicated data,
• reporting confusion,
• uncontrolled growth of customisations.

With governance:

• validation of need,
• review of standard functionality,
• ownership assignment,
• usage policy.

✔ Case 3: Financial processes

Without governance:

• inconsistent month‑end closing,
• unclear roles,
• hidden dependencies.

With governance:

• RACI matrix,
• closing checklist,
• defined functional roles,
• smoother internal audits.

3. How to measure functional governance (real tools and KPIs)

✔ Key functional indicators

• % of documented processes
• % of changes approved through governance
• Number of incidents caused by misconfiguration
• Number of functional exceptions
• Adoption time for new features
• Ratio of standard vs customised processes

✔ Tools that support governance

• Azure DevOps – change control, approvals, backlog
• SharePoint – functional documentation repository
• Power BI – adoption and usage dashboards
• Copilot Studio – automated functional queries
• Sandbox environments – controlled testing before deployment

4. Adoption: the real thermometer of governance

Governance is not measured in documents.
It is measured in user behaviour:

• Do users follow the designed process?
• Do they avoid shortcuts?
• Do they understand the impact of their decisions?
• Do they participate in functional committees?
• Do they request changes with proper criteria?

A well‑governed ERP has mature users, not just trained users.

5. My experience as a Functional Consultant and MCT

Across projects, I see the same pattern:
The organisations that succeed with Business Central SaaS are not the ones that customise the most, but the ones that govern the best.

Functional governance is:
clarity, responsibility, sustainability and evolution.

It is the bridge between technology and business decision‑making.

To Conclude

Business Central SaaS does not need more customisations.
It needs stronger governance.

Let’s keep building value.

Public sector organisations face increasing pressure to demonstrate transparency, traceability and disciplined administrative processes. In this context, Microsoft Dynamics 365 Business Central SaaS has evolved into more than an ERP: it has become a platform that strengthens governance, ensures data integrity and supports continuous auditability across the entire administrative cycle.

In my experience implementing Business Central for public sector bodies and state‑owned companies, I have seen how the system can address complex administrative scenarios by relying primarily on its native standard functionality, complemented only by functional extensions when legislation or operational casuistry requires it. The objective has never been to override the standard, but to extend it without breaking native flows, preserving the ERP’s architecture and ensuring full traceability.

1. Continuous auditability and full administrative traceability

Public sector entities operate under permanent oversight. Every approval, modification and budgetary movement must be traceable and verifiable.

Business Central provides:

• detailed logging of critical events,
• real‑time user action tracking,
• automatic evidence generation for audits,
• telemetry‑based anomaly detection.

In my experience, standard approval workflows and change logs allow complete audit trails without complex development. Every action is recorded: who approved, what changed, when it occurred and under which permissions. This supports internal auditors, financial controllers and oversight bodies.

2. Case management: standard as the foundation, extensions as the regulatory layer

Case and dossier management is central to public sector operations. Business Central structures cases using:

• related documents,
• native approvals,
• versioning,
• change logs,
• standard workflow orchestration.

In my experience, complex case scenarios have been resolved by relying on the standard and adding functional extensions only when legislation requires additional validations, specific spending controls, restrictions based on service type or multi‑level approval chains.
Extensions are functional, non‑invasive and always respect native flows to maintain auditability and data integrity.

3. Minor and major contracts: operational control without breaking the standard

Contract management is one of the most regulated processes in the public sector. Business Central supports:

• minor contracts,
• major contracts,
• renewals,
• spending limits,
• budget linkage,
• approvals based on thresholds.

In my experience, the standard covers most scenarios—requests, approvals, execution and budget control. When specific regulatory rules apply, functional extensions have been added to ensure compliance, full traceability, data integrity and audit‑ready evidence.
The standard remains the foundation; extensions simply add the regulatory layer.

4. Procurement and tendering: transparency and control through native flows

Public procurement demands complete transparency. Business Central structures tendering processes using:

• standard purchasing flows,
• native approvals,
• role‑based access control,
• decision logging,
• budget integration,
• tender dossier tracking.

In my experience, complex tendering scenarios have been resolved through standard approvals, related documents, change logs and telemetry. Where legislation requires additional steps, functional extensions have been added to support specific tender phases, adjudication controls, operational restrictions and additional evidence for oversight bodies.
The native flow remains intact; the extension adds the administrative requirements.

5. Governance and operational discipline

One of the biggest challenges in the public sector is process heterogeneity: Excel‑based workflows, manual approvals and operations dependent on individuals rather than systems.

Business Central promotes governance by:

• standardising processes,
• automating validations,
• controlling approvals,
• reducing human error,
• enabling fiscalisable operations.

In my experience, adopting the standard has transformed entire departments, replacing manual processes with structured, auditable flows. Functional extensions have been applied only when necessary, ensuring compliance without compromising the ERP’s architecture.

To Conclude

Public sector organisations require systems that guarantee control, transparency and continuous auditability. Business Central has proven capable of meeting these demands with rigour, traceability and operational discipline.

In my experience, the combination of standard functionality, well‑designed functional extensions, native ERP processes and a modern SaaS architecture allows public sector entities to adopt a more mature, auditable and integrity‑driven operational model.

Business Central is not just an ERP:
it is a public governance system.

1. The traditional ERP is obsolete: modern companies need intelligence

For decades, ERPs were designed to record.
Today, organisations require systems that interpret, alert, predict, prove and guide users to operate better.

Business Central evolves into an intelligence system because it integrates capabilities that were previously fragmented:

• Advanced fiscal automation.
• Governance and audit APIs.
• Embedded analytics and traceability.
• Multi‑country localisation.
• User experience designed for adoption.
• Shorter processes and reduced operational friction.

This turns the ERP into a corporate control centre, not merely a financial system.

2. Fiscal intelligence: faster decisions and lower risk

Based on the official update:
Fiscal automation

Business Central now:

• Calculates tax withholdings automatically based on supplier, country and transaction type.
• Applies accelerated depreciation according to fiscal regulations.
• Reduces manual errors and review time.
• Enables simulation of investment and return scenarios.

Real value for the organisation

• CFO: faster decisions and reduced regulatory risk.
• CEO: frictionless expansion.
• Auditor: automated, traceable evidence.
• Business owner: protection of capital and cash flow.
• End user: fewer manual calculations, fewer errors, less operational stress.

3. Internal control intelligence: evidence that previously did not exist

Based on the official links:

• APIs for analysing permissions
• APIs for analysing approval workflows

These APIs expose critical information that was previously hidden:

• Who can approve payments.
• Who can modify master data.
• Which approval workflows are active or inactive.
• Which sensitive configurations have changed.
• Which users hold permissions misaligned with their role.

Real value for the organisation

• CIO: independence from the partner and control of technological risk.
• Internal auditor: segregation‑of‑duties tests based on evidence.
• CEO: real governance, not declarative governance.
• CFO: financial control without blind spots.
• End user: clarity of role, fewer blockages, less “consultant dependency”.

4. Operational intelligence: fewer clicks, more decisions

Business Central incorporates improvements that reduce operational friction:

• Shorter processes.
• Cleaner, more intuitive screens.
• Automation of repetitive tasks.
• Integration with Power BI and Copilot.

Real value for the organisation

• Faster teams.
• Cleaner data.
• More reliable decisions.
• Less dependence on individual knowledge.
• More autonomous end users, with reduced need for support.

5. Multi‑country intelligence: expansion without complexity

The update includes enhancements in:

• Electronic invoicing.
• Regulatory reporting.
• Advanced localisation.
• International compliance.

Real value for the organisation

• CEO: expansion without multiplying complexity.
• CFO: consistent compliance across jurisdictions.
• Auditor: consolidated, traceable evidence.
• End user: standardised processes, fewer variations, fewer errors.

6. Executive intelligence: decisions based on evidence

When an ERP:

• automates fiscal processes,
• exposes permissions,
• reveals traceability,
• integrates analytics,
• reduces operational friction,
• and accelerates adoption…

…it stops being a transactional system and becomes a corporate decision engine.

Real value for the organisation

• Less intuition.
• More evidence.
• Lower risk.
• Higher speed.
• Less partner dependency.
• Stronger governance.
• More competent and productive end users.

7. End‑user adoption: the component that turns intelligence into results

This is the missing piece that delivers real value to companies.

Business Central introduces improvements that directly impact adoption:

✔ Cleaner interfaces

Less visual noise, less confusion, more speed.

✔ Guided processes

Users understand what to do without relying on consultants.

✔ Fewer clicks

Fewer steps = fewer errors = higher productivity.

✔ Copilot integration

Contextual assistance, not generic help.

✔ Process standardisation

Fewer departmental variations, more consistency.

✔ Reduced dependence on individual knowledge

The system guides — not the user’s memory.

Real value for the organisation

• Lower staff turnover.
• Reduced learning curve.
• Less internal support.
• Higher productivity.
• Better data quality.
• Faster operations.
• Greater confidence in the system.

To Conclude

Business Central is no longer an ERP.
It is an enterprise intelligence system that:

• anticipates risks,
• automates compliance,
• exposes control evidence,
• accelerates decisions,
• facilitates adoption,
• and supports international expansion.

Companies that understand this do not only operate better:
they lead better, control better and grow better.

1. The structural problem: an ERP that is used, but not governed

In most organisations, the ERP is the operational core — yet its internal control model is largely opaque:

• Legacy roles inherited from old implementations.
• Excessive permissions granted “to avoid blocking operations”.
• Approval workflows that no one has reviewed in years.
• Audit processes based on screenshots, Excel exports and verbal explanations.

The company operates — but cannot demonstrate that it operates under control.

Microsoft’s new APIs directly address this governance gap by turning what used to be hidden configuration into queryable, analysable and repeatable evidence.

2. APIs for analysing permissions: evidence of who can do what

Based on: Use new APIs for analysing permissions for auditors and IT staff

Utilizar nuevas APIs para analizar permisos para auditores y personal de TI | Microsoft Learn

These APIs allow organisations to extract, in a structured and automated way:

• Which users have access to which objects.
• Which roles are assigned to each user.
• The effective permissions resulting from combined roles.
• Which users hold high‑risk privileges (e.g., modifying vendors, approving payments, changing financial parameters).

Concrete example for a CEO or business owner

A permissions report generated through these APIs can answer questions such as:

• “How many users can modify the chart of accounts?”
• “Who can create vendors and also approve payments?”
• “Which users hold permissions that do not match their actual job role?”

This enables the detection of:

• Internal fraud risks.
• Excessive privilege assignments.
• Poorly designed roles.
• Permissions inherited from former employees or consultants.

Business value

• For a CEO: real control over who can touch critical parts of the business.
• For a CIO: independence from the partner and a clear map of risk.
• For auditors: verifiable, repeatable evidence instead of ad hoc explanations.

3. APIs for analysing approval workflows: traceability of the control process

Based on: Use new APIs for analysing approval workflows for auditors and IT staff

Utilizar nuevas APIs para analizar los flujos de trabajo de aprobación de auditores y personal de TI | Microsoft Learn

These APIs allow organisations to review:

• Which approval workflows exist in the system.
• Which conditions trigger each workflow.
• Which users or groups approve each document type.
• Approval limits and escalation rules.
• Which workflows are active, inactive or misconfigured.

Concrete example for a CFO or auditor

Using these APIs, a CFO or internal auditor can identify:

• Approval workflows that never execute, indicating potential bypass.
• Users with approval limits far above their organisational role.
• Documents that should be approved but are not passing through any workflow.
• Recent changes to approval rules that may weaken financial control.

Business value

• For a CFO: stronger assurance that money does not move without proper oversight.
• For internal audit: full traceability of the approval chain.
• For business owners: protection of cash, assets and reputation.

4. What changes for senior leadership

These APIs are not a minor technical enhancement; they represent a governance shift.

Before

• Dependence on the partner for critical information.
• Manual, slow and inconsistent audit processes.
• Roles and workflows left unreviewed for years.
• Hidden operational and fraud risks.

Now

• Structured, automatable evidence of permissions and approvals.
• Continuous review of the ERP’s control model.
• Integration with Power BI, GRC tools and internal dashboards.
• Governance based on data, not assumptions or trust alone.

For CEOs, CIOs and CFOs, this means the ERP can finally be treated as part of the formal governance architecture, not just as an operational system.

5. What CEOs, CIOs and auditors should do next

For CEOs and business owners

• Request a full effective permissions report using the new APIs.
• Review who can approve payments and modify master data.
• Demand a risk map of the ERP that highlights high‑risk roles and workflows.

For CIOs

• Integrate these APIs into IT and governance dashboards.
• Automate alerts for changes in critical roles or approval rules.
• Establish quarterly ERP governance reviews with Finance and Audit.

For internal audit

• Incorporate these APIs into the annual audit plan.
• Define standard segregation‑of‑duties tests based on permissions data.
• Monitor changes in approval workflows as part of continuous auditing.

6. To Conclude: from ERP usage to ERP governance

The real transformation here is conceptual:

• Business Central stops being merely “the system where transactions are recorded” and becomes a source of structured governance evidence.
• Senior leadership gains the ability to measure and demonstrate control, rather than simply assuming it.
• Auditors and IT teams can move from manual, reactive checks to systematic, proactive and data‑driven oversight.

In practical terms:

• Organisations can quantify their segregation of duties.
• They can trace changes in critical configuration.
• They can prove, not just claim, that their ERP is aligned with their internal control framework.

For CEOs, CIOs, CFOs and business owners, this is the difference between trusting that the ERP is under control and knowing — with evidence — that it is.

Global expansion and financial governance are now competitive advantages

For multinational organisations, growth has always been constrained by two major barriers:

• Regulatory friction when entering new markets
• Operational inconsistency across countries

Microsoft’s latest updates to Business Central directly address both challenges.
These enhancements are not technical refinements — they are strategic enablers for CEOs, CFOs and COOs who need speed, compliance and control across multiple geographies.

PART I — INTERNATIONAL EXPANSION MADE SIMPLER

Microsoft has strengthened localisation and compliance in three key markets:

• France → E‑invoicing compliance
• Australia → Payment Times Reporting
• United Kingdom → Payment Practices Reporting

These capabilities remove barriers that traditionally slowed down international expansion.

1. France — E‑invoicing compliance in one of Europe’s strictest frameworks

France is rolling out one of the most demanding e‑invoicing mandates in the EU.
Business Central now supports:

• mandatory B2G and B2B e‑invoicing formats
• integration with official French e‑invoicing platforms
• compliant electronic document exchange

Why this matters to CEOs and CFOs

Entering France used to require:

• local consulting firms
• custom developments
• parallel compliance projects
• high risk of penalties

Now, the ERP is natively compliant.

Example: A Spanish distributor opening a subsidiary in Lyon can:

• issue compliant e‑invoices from day one
• avoid local development costs
• reduce legal and operational risk

This accelerates market entry and reduces cost of expansion.

2. Australia — Payment Times Reporting for large enterprises

Australia requires large companies to report how quickly they pay suppliers, especially SMEs.
Business Central now supports:

• automated data collection
• compliant reporting formats
• audit‑ready documentation

Why this matters to executives

Non‑compliance can lead to:

• penalties
• reputational damage
• exclusion from public contracts

With native support, organisations avoid building reporting systems from scratch.

Example: A European company acquiring an Australian subsidiary can:

• comply immediately
• avoid manual data extraction
• reduce administrative overhead

This protects reputation and ensures regulatory alignment.

3. United Kingdom — Payment Practices Reporting for public sector suppliers

Companies working with the UK public sector must report:

• average payment times
• percentage of invoices paid on time
• internal payment policies

Business Central now structures and centralises this information.

Why this matters

Without this capability, companies risk:

• losing access to public contracts
• failing pre‑qualification checks
• reputational impact

Example: A Spanish services company entering the UK market can:

• demonstrate compliance from day one
• avoid manual reporting
• accelerate access to NHS and public sector tenders

PART II — FINANCIAL GOVERNANCE FOR MULTINATIONAL OPERATIONS

Alongside localisation, Microsoft has strengthened four financial pillars:

• Automated withholding tax
• Automated invoicing
• Accelerated depreciation
• Harmonised accounting rules

These capabilities reduce risk, eliminate manual work and improve global consistency.

1. Automated withholding tax — lower fiscal risk, higher accuracy

Withholding tax errors are a major source of audit adjustments.
Business Central now:

• applies withholding tax automatically
• handles complex rules across countries
• generates audit‑ready documentation

Example: A company operating in Spain, Mexico and Colombia can:

• eliminate manual calculations
• harmonise criteria
• reduce fiscal risk

This accelerates month‑end closing and improves data reliability.

2. Automated invoicing — operational speed and stronger cash flow

Manual invoicing slows down revenue cycles.
Automation enables:

• invoice generation without human intervention
• predefined business rules
• faster issuance
• improved liquidity

Example: A services company issuing 2,000 invoices per month can:

• reduce operational effort by 60–80%
• eliminate repetitive tasks
• improve cash flow predictability

3. Accelerated depreciation — flexibility and global compliance

Depreciation is a strategic lever for:

• tax optimisation
• asset valuation
• regulatory compliance

Business Central now supports accelerated depreciation natively.

Example: An industrial group with assets in multiple countries can:

• apply consistent criteria
• reduce audit discrepancies
• improve financial transparency

4. Harmonised accounting rules — the foundation of scalability

This is the most strategic enhancement.

Harmonised rules allow:

• consistent processes across all subsidiaries
• faster month‑end closings
• simpler audits
• reliable global reporting

Example: A multinational with 12 subsidiaries can reduce its closing cycle:

• from 10–15 days
• to 5–7 days

This gives CEOs real‑time visibility and CFOs trustworthy data.

To Conclude

Microsoft is eliminating two of the biggest barriers to multinational growth:

✔ Regulatory friction

(France, Australia, United Kingdom)

✔ Financial inconsistency

(withholding tax, invoicing, depreciation, accounting rules)

Business Central is evolving into an ERP that:

• reduces risk
• accelerates expansion
• strengthens governance
• eliminates manual work
• and scales without increasing headcount

For CEOs and CFOs, this is not a technical update.
It is a strategic advantage.

Introduction: it’s not about titles — it’s about judgement

For years, the industry assumed that a consultant’s value was measured by the number of certificates, courses or degrees they collected.
Today, that idea feels outdated.

The modern functional consultant is shaped by critical thinking, strategic awareness, data literacy and the maturity to guide decisions.
Credentials help, of course — but they don’t replace what truly matters: clarity, judgement and the ability to influence.

My own journey includes becoming an MCT, an MB‑800 Associate Consultant, completing an MBA, a Master’s in Strategic and Development Management, training in agile frameworks, and studying Complex Project Leadership at Cambridge.
But let me be absolutely clear: none of this is mandatory for anyone.

These were my steps.
Your steps can be different.
What matters is developing the core capabilities that define the modern consultant.

The real competencies — and how to develop them without spending thousands

1. Critical thinking

The ability to question, prioritise and understand the “why” behind decisions.
You develop it by reading, comparing models, observing patterns and asking better questions.

2. Mastery of the standard

You don’t need expensive courses.
You need curiosity, documentation, and hands‑on practice in sandboxes.

3. Business acumen

An MBA helps, but it’s not the only route.
You can build business understanding by working closely with clients, studying real cases and analysing how organisations operate.

4. Strategic communication

The ability to say “no”, explain risks and guide decisions.
This is learned in conversations, not classrooms.

5. Data‑driven thinking

You don’t need to be a data scientist.
You need to understand what the data is telling you — usage, telemetry, friction points.

6. Change management

Understanding how people adopt systems.
This comes from working with users, not just configuring features.

7. Agile mindset

Agile frameworks teach adaptability, transparency and incremental value.
They help consultants think in outcomes, not deliverables.

Multi‑country and multi‑industry: the most valuable classroom

Working across countries and sectors teaches you things no certification can:

• how different cultures make decisions
• how industries shape processes
• how teams behave under pressure
• how organisations react to change

But even without international experience, you can develop this mindset by exposing yourself to diverse projects and learning to recognise patterns.

How to reach this profile without major investment

Here’s the truth that rarely gets said:

✔ You can become a modern consultant without an MBA
✔ You can become a modern consultant without expensive certifications
✔ You can become a modern consultant without international experience
✔ You can become a modern consultant without a decade in the field

What you need is:

• judgement
• curiosity
• discipline
• exposure to real problems
• and the willingness to think beyond tasks and features

Conclude: the modern consultant is a choice, not a credential

The modern functional consultant is defined by how they think, how they decide and how they guide.
Credentials help — but they don’t create mastery.
Mastery comes from clarity, analysis, leadership and the ability to influence outcomes.

This path is open to anyone who chooses to grow.

For years, ERP projects were built on a risky assumption: “The system must adapt to the customer, no matter the cost.”

This mindset produced:

• heavy customisations
• duplicated processes
• technical debt
• high maintenance costs
• long, unpredictable projects
• systems that could not be updated

Business Central SaaS breaks this pattern.
And it does so with a clear methodology: Fit‑to‑Standard.

Fit‑to‑Standard does not limit the customer.
It frees them from unnecessary complexity.

1. What Fit‑to‑Standard really means

Fit‑to‑Standard is a methodology where:

• the implementation starts from the standard capabilities
• customer data is analysed before making decisions
• gaps are identified based on evidence, not assumptions
• configuration is prioritised over development
• the system remains update‑friendly
• the ERP stays aligned with Microsoft’s SaaS evolution

It is a pragmatic, modern and sustainable approach.

Official Microsoft guidance:

• Business Central Implementation Overview
• Configure Business Central
• Business Central Application Design

2. Why Fit‑to‑Standard is a data‑driven methodology

The goal is not to “force the customer into the standard”.
The goal is to use real customer data to decide what truly needs adaptation.

✔ Historical data

Sales patterns, purchasing cycles, inventory movements, production volumes.

✔ Operational data

Seasonality, exceptions, lead times, bottlenecks.

✔ Usage data

Which processes are used, which are ignored, where friction occurs.

✔ Data quality

Duplicates, inconsistencies, incorrect structures.

With this evidence, the functional consultant can say:

• “This process already exists in standard.”
• “This exception occurs only 2% of the time.”
• “This customisation does not add measurable value.”
• “This requirement can be solved with configuration.”

Fit‑to‑Standard transforms the conversation from subjective to objective.

3. Practical examples of Fit‑to‑Standard in Business Central

Example 1: Inventory management

A customer requests a custom process for special locations.
Data shows only 3% of stock passes through them.
Solution:
→ Standard location rules + configuration.
→ No custom development.

Example 2: Purchasing approvals

The customer wants a 7‑level approval chain.
Data shows 92% of purchases are low‑value.
Solution:
→ Two approval levels + thresholds.
→ No unnecessary complexity.

Example 3: Demand forecasting

The customer wants a custom forecasting model.
Data shows clear seasonal patterns.
Solution:
→ Standard forecasting + manual adjustments.
→ No bespoke model.

Fit‑to‑Standard simplifies with evidence, not by force.

4. Fit‑to‑Standard and the update lifecycle (major & minor updates)

One of the biggest advantages of Fit‑to‑Standard is protecting the update lifecycle of Business Central:

✔ Major updates (twice per year)

Microsoft releases significant functional and platform improvements.
Fit‑to‑Standard ensures the system can adopt them without breaking.

✔ Minor updates (monthly)

Security, performance and reliability enhancements.
Minimal customisation = minimal risk.

✔ Reduced technical debt

Fewer extensions → fewer conflicts → smoother updates.

5. The critical role of customer participation and key users

Fit‑to‑Standard succeeds only when the customer is actively involved.

✔ Key users must:

• validate standard processes
• provide real operational data
• identify exceptions that truly matter
• participate in workshops and testing
• understand the impact of customisations

✔ The customer organisation must:

• commit to process alignment
• accept evidence‑based decisions
• collaborate in data cleansing
• adopt standard terminology and flows

Fit‑to‑Standard is a co‑creation process, not a consultant‑only exercise.

When key users participate, the implementation becomes:

• faster
• more accurate
• more aligned with reality
• more sustainable

6. How Fit‑to‑Standard elevates the functional consultant

The consultant stops being:

• a requirement collector
• a translator between business and development
• a customisation manager

And becomes:

• a data‑driven analyst
• a process architect
• a strategic advisor
• a guardian of sustainability

Fit‑to‑Standard elevates the functional role to a position of decision and leadership.

7. Benefits for the customer

• Faster implementations

Less development, more configuration.

• Lower total cost of ownership

Reduced maintenance and technical debt.

• Update‑friendly system

Major and minor updates without disruption.

• Cleaner, more consistent processes

Fewer exceptions, fewer deviations.

• Decisions based on evidence

Not on assumptions or personal preferences.

To Conclude

Fit‑to‑Standard is not a restriction.
It is a strategic, data‑driven and sustainable way to implement Business Central.

It protects the update lifecycle.
It reduces complexity.
It empowers key users.
It elevates the functional consultant.
And it ensures the ERP remains healthy, modern and aligned with Microsoft’s roadmap.

It is, without doubt, the right methodology for any organisation adopting Business Central SaaS.

Foundry: the governance that turns agents into real enterprise resources

So far, we’ve discussed MCP as the standard that allows agents to work with real business tools.
But every capability needs structure.
Every action needs control.
And every automation needs accountability.

That’s where Foundry comes in.

Foundry is not a tool for creating agents.
It is the environment that defines how those agents live, act, are supervised and integrated into the organisation.
It’s the difference between having experimental agents and having trusted enterprise resources.

1. What Foundry is — in functional terms

Foundry is the framework that allows agents to:

• maintain persistence (remember context and state)
• operate within boundaries (never act beyond their scope)
• use approved tools (only what the business authorises)
• provide auditability (every action is recorded)
• comply with corporate security (respect policies and permissions)
• achieve scalability (grow without losing control)

In short:
Foundry turns automation into a governed enterprise practice.

2. Why governance is the critical point

Automation without governance is an empty promise.
It can be fast, but not reliable.
Efficient, but not secure.
Useful, but not sustainable.

Foundry solves that dilemma.

It defines a framework where every agent has:

• identity
• purpose
• responsibility
• boundaries
• traceability

And that completely changes how functional and technical teams collaborate.

3. Functional examples of governance in action

Example 1: Purchasing agent with controlled access

The agent can review orders and validate prices, but cannot approve or modify records.
Foundry ensures the agent acts within its role — just like a human user with defined permissions.

Example 2: Finance agent with full traceability

Every action —query, validation, alert— is logged.
This enables real audits and compliance without extra effort.

Example 3: Support agent with contextual persistence

The agent remembers previous interactions, but only within authorised boundaries.
It never accesses data outside its scope.
Foundry keeps memory under control.

4. What Foundry brings to enterprise architecture

• Structured security — Agents operate under corporate policies, not improvisation.
• Controlled scalability — You can have dozens of agents without losing traceability or coherence.
• Operational accountability — Each agent has a purpose and a record of actions.
• Natural integration with MCP — Foundry doesn’t replace MCP; it complements it. MCP defines how agents communicate. Foundry defines how they are governed.
• Functional trust — Teams can delegate tasks knowing the agent acts within safe boundaries.

5. What changes for functional and business teams

With Foundry, functional teams stop seeing automation as a technical matter and start seeing it as an extension of the process.

They can:

• design agents with defined roles
• audit their behaviour
• adjust boundaries without technical intervention
• integrate agents into real workflows

And most importantly:
they can trust them.

6. Foundry and the future of enterprise automation

Foundry represents a new stage — automation with accountability.

It’s no longer about creating agents that “do things”.
It’s about creating agents that do the right things, under rules, limits and traceability.

It’s the step that turns artificial intelligence into a mature enterprise practice.

To Conclude

Foundry is the missing piece.
The one that turns automation into governance.
The one that transforms experimental agents into real enterprise resources.
The one that allows functional teams to work with confidence, security and control.

MCP enables action.
Foundry ensures responsibility.
Together, they define the future of automation in Business Central and across the Dynamics ecosystem.

In recent years we have seen agents that answer questions, generate text or explain concepts.
Interesting, yes.
Occasionally useful.
Transformational? Not really.

The real transformation begins when an agent stops being a “conversational assistant” and becomes a worker inside the operational process.

And that is only possible because of MCP.

MCP is not a technical detail.
It is the bridge between an agent’s intention and the organisation’s real tools.
It is the line that separates a chatbot from an operational agent.

Once you understand that, the true potential becomes visible.

1. MCP turns automation into something governed, not improvised

Before MCP, most automation efforts depended on:

• isolated scripts
• fragile connectors
• undocumented automations
• custom integrations
• processes that broke when a field changed

It was an ecosystem full of good intentions and bad habits.

MCP introduces order where creativity used to run unchecked.

It defines:

• what an agent can do
• which tools it can use
• under which permissions
• with what limits
• with what traceability

In short: it brings automation into the domain of enterprise governance.

2. What “using real business tools” actually means

When we say an agent “uses tools”, we are not talking about magic.
We are talking about actions that people perform every day.

Actions that consume time.
Actions that require precision.
Actions that repeat endlessly.

For example:

✔ Checking the status of an order and validating conditions

✔ Reviewing an attached document and spotting inconsistencies

✔ Searching for information in a corporate system

✔ Executing a business rule before approving something

✔ Preparing an operational summary for a manager

✔ Triggering an action that starts a process

This is not “generative AI”.
This is real work.

And MCP is the standard that allows an agent to do it without breaking anything.

3. Functional examples that reveal the real potential

This is where functional readers start to see the impact.

Example 1: A purchasing agent acting as the first filter

• Automatically checks if a supplier has delayed deliveries
• Validates prices against the commercial agreement
• Detects quantity discrepancies
• Suggests actions to the buyer

This agent does not replace the buyer.
It frees them from mechanical tasks so they can focus on strategic decisions.

Example 2: A finance agent preparing partial closing work

• Retrieves open invoices
• Identifies documents pending approval
• Flags potential delays
• Prepares a summary for the finance lead

It does not decide.
It prepares the ground so decisions are faster and better informed.

Example 3: An inventory agent anticipating issues

• Checks stock levels
• Detects potential shortages
• Suggests internal movements
• Recommends urgent purchase orders

It is a silent analyst working 24/7.

4. MCP redefines the role of the functional team

Here is the challenging part.

With MCP, the functional team stops being:

• the one documenting processes
• the one validating data
• the one checking rules
• the one performing repetitive tasks

And becomes:

• the one deciding what tasks to delegate
• the one defining which tools an agent can use
• the one supervising the quality of automated work
• the one deciding where human intervention is essential

It is a shift in role.
A shift in mindset.
A shift in responsibility.

5. MCP is not technology: it is process architecture

MCP is not understood through code.
It is understood through functional architecture.

Because MCP:

• standardises
• structures
• limits
• enables
• protects
• governs

And that allows agents to integrate into real processes without creating chaos.

It is the difference between “automating” and automating well.

6. What comes next

In the third part we will explore Foundry, the capability that turns these agents into governed enterprise resources:

• persistence
• auditability
• security
• boundaries
• approved tools
• scalability
• operational accountability

If MCP is the language, Foundry is the organisation where that language is used with clear rules.

To Conclude

MCP is not a technical feature.
It is the foundation that allows agents to perform real operational work inside the business.

It turns automation into something secure, governed and scalable.
It allows functional teams to delegate tasks without losing control.
It enables specialised agents that work inside the process, not outside it.

And it is, without doubt, one of the most important shifts in how organisations design and execute their work.

For years we have talked about automation, assistants and “intelligent agents”, yet most of those ideas remained as prototypes or isolated experiences. The reason was simple: there was no standard, secure and governed way for an agent to interact with real business tools.

This is where MCP and Foundry come in.

They are not new concepts. MCP has been around since 2024. Foundry has been maturing for some time. But now, with agents becoming more integrated into Business Central and the wider Dynamics ecosystem, these two capabilities are starting to have a real functional impact.

And that impact deserves to be explained from a business perspective, not a technical one.

1. What MCP is (explained for functional teams)

At its core, MCP is a standard that allows an agent to use business tools in a secure, structured and predictable way.

It is not an API. It is not a connector. It is not a plugin.

It is a common language that enables an agent to:

• retrieve information
• perform actions
• validate data
• interact with systems
• all within clear permissions, limits and rules

For functional teams, MCP means something very straightforward: agents stop behaving like “black boxes” and start acting as part of the process.

2. What Foundry is (without technical jargon)

If MCP is the language, Foundry is the platform that turns agents into governed enterprise resources.

Foundry allows an agent to:

• maintain context over time
• operate within defined boundaries
• use approved tools
• be audited
• comply with corporate security
• scale without breaking processes

In other words: Foundry makes an agent trustworthy, manageable and suitable for real business workflows.

3. Why this matters now (even though MCP has existed since 2024)

Because until recently, MCP was available… but without an ecosystem capable of fully leveraging it.

Today the situation is different:

• Business Central now includes agents that can use MCP
• Foundry provides real governance
• Organisations are demanding more mature automation
• Processes require agents that work with real data, not examples

So even if MCP is not new, its functional relevance is.

4. What changes for functional teams

Here is where the real value appears:

✔ Agents can work with real business tools

Not just “answer questions”, but perform actual tasks.

✔ Processes can delegate repetitive work

Data validation, document review, status checks, summaries.

✔ Automation no longer depends entirely on technical teams

MCP standardises interaction. Foundry governs it. Functional teams define the process.

✔ Security and auditability are built‑in

No more “shadow automations”. Everything is traceable.

✔ Specialised agents become possible

Not a generic assistant, but agents for purchasing, sales, finance, inventory…

5. What to expect in the next posts

This is only the beginning. The next posts will explore:

Post 2 — How MCP enables agents to work with real business tools

Functional examples, no code.

Post 3 — How Foundry provides governance, security and persistence

Why this changes how we design processes.

Post 4 — What this means for Business Central and functional roles

Impact on consulting, architecture and operations.

To Conclude

MCP and Foundry are not new technologies. What is new is their functional impact.

For the first time, agents can integrate into real processes with security, governance and approved tools. And that changes how functional teams design, execute and supervise work.

This is the starting point. The interesting part begins now.