---
title: "Consolidating Entities onto One Dynamics 365 Template"
canonical_url: "https://cognilium.ai/dynamics-365/multi-entity-consolidation"
slug: "dynamics-365/multi-entity-consolidation"
section: "dynamics-365"
page_type: "pillar"
date_modified: "2026-10-28"
description: "What breaks when entities fold onto one Dynamics 365 template: receipts across the cutover, inherited GRNI, new intercompany flows, and the decisions to take first."
publisher: "Cognilium AI"
author: "Mudassir Marwat"
person_same_as:
  - "https://www.linkedin.com/in/mudassir-marwat/"
  - "https://orcid.org/0009-0008-1927-2598"
  - "https://github.com/mudassirmarwat"
  - "https://medium.com/@mudassir-marwat"
  - "https://www.youtube.com/@mudassir-marwat"
  - "https://dev.to/mudassirmarwat"
  - "https://hashnode.com/@mudassirmarwat"
  - "https://huggingface.co/mudassirmarwat"
  - "https://bsky.app/profile/mudassir-marwat.bsky.social"
  - "https://substack.com/@mudassirmarwat"
  - "https://topmate.io/mudassirmarwat"
  - "https://fueler.io/mudassirmarwat"
  - "https://www.instagram.com/mudassirmarwat/"
  - "https://www.facebook.com/mudassir.marwat"
  - "https://www.reddit.com/user/mudassirmarwat/"
  - "https://www.f6s.com/member/mudassir-marwat"
  - "https://cognilium.ai/founder"
answers:
  - "What breaks when several entities move onto one Dynamics 365 template?"
  - "Is it too early to look at ERP agents while the implementation is still running?"
  - "Why do inherited GRNI opening balances have no document trail?"
  - "When should agent identity and permissions be decided in a D365 rollout?"
  - "Can an agent help during hypercare without adding risk to the cutover?"
entities:
  - name: "Microsoft Dynamics 365"
    id: "https://cognilium.ai/#entity-dynamics365"
    url: "https://www.microsoft.com/en-us/dynamics-365"
    same_as:
      - "https://www.wikidata.org/wiki/Q27556059"
      - "https://en.wikipedia.org/wiki/Microsoft_Dynamics_365"
  - name: "Microsoft Dynamics 365 Business Central"
    id: "https://cognilium.ai/#entity-businessCentral"
    url: "https://www.microsoft.com/en-us/dynamics-365/products/business-central"
    same_as:
      - "https://www.wikidata.org/wiki/Q58883729"
  - name: "Microsoft"
    id: "https://cognilium.ai/#entity-microsoft"
    url: "https://www.microsoft.com"
    same_as:
      - "https://www.wikidata.org/wiki/Q2283"
      - "https://en.wikipedia.org/wiki/Microsoft"
  - name: "Microsoft Power Platform"
    id: "https://cognilium.ai/#entity-powerPlatform"
    url: "https://www.microsoft.com/en-us/power-platform"
    same_as:
      - "https://www.wikidata.org/wiki/Q106253893"
      - "https://en.wikipedia.org/wiki/Microsoft_Power_Platform"
related:
  - "https://cognilium.ai/dynamics-365"
  - "https://cognilium.ai/dynamics-365/agent-readiness-review"
  - "https://cognilium.ai/dynamics-365/aged-grni-investigation-agent"
  - "https://cognilium.ai/dynamics-365/po-receipt-chase-agent"
---

# Consolidating Entities onto One Dynamics 365 Template

A consolidation does not break the ledger, it breaks the trail behind it. Receipts post on one side of the cutover and invoices arrive on the other, opening balances carry over without a document trail anyone in the new entity recognises, and two item masters disagree about units of measure. From Dynamics 365 Finance & Operations version 10.0.47 an agent can hold its own identity with no permissions until an administrator assigns roles, which is why agent identity belongs beside the role design rather than after go-live.


## Five things a consolidation does to the purchasing cycle

### Receipts land on one side of the cutover and the invoice on the other

Stock is received in the system being retired, the invoice arrives after go-live in the system replacing it, and the three-way match has nothing to match against. The line is not wrong in either system. It is only wrong across the pair, which is the one view neither one shows.

### Accrual balances arrive with no document trail anyone recognises

Goods received not invoiced carries over as an opening balance. The receipt behind each line was posted by a team that may no longer exist, against a purchase order in a numbering series nobody in the new entity has seen. The number is auditable; the reason behind it usually is not.

### Two companies become intercompany overnight

Entities that invoiced each other as third parties last quarter are now internal, and the purchasing flow between them has to change on the day the legal structure does. The paperwork that was correct in both systems becomes an elimination problem in one.

### Two item masters merge and the units of measure disagree

The same physical part arrives as an each in one catalogue and a case of twelve in the other. Quantities reconcile on paper and not on the shelf, and the error only shows up as a receipt that nobody will post because nobody believes it.

### Security roles are copied from the template, not from the entity

One template rolled across several entities carries one role design. The segregation of duties that suited the first site rarely suits a site with four people in finance, and the gap is discovered by an auditor rather than by the project.


## Five decisions, before cutover compared with after go-live

| The decision | Taken before cutover | Taken after go-live |
| --- | --- | --- |
| Who the agent is | An identity exists alongside the human roles being designed, with no permissions until someone grants them | A new identity is requested during hypercare, when nobody has time to review what it should be able to see |
| What the agent may change | Read everywhere, change nothing without a named approver, agreed while the approval matrix is still open | Retro-fitted to whatever the agent was already doing |
| Where the opening balances came from | Captured while the people who posted them are still on the project | Reconstructed from the ledger by whoever inherits it |
| Which exceptions a person must see | Written into the test script, so the exception path is exercised before real volume hits it | Discovered at the first month end on live data |
| What the agent costs to run | Estimated against the environment's own capacity, before the rollout fixes the budget | Found in an invoice |


## The three agents, with status

### PO Receipt Chase agent

Finds purchase order lines that arrived but were never received in the ERP, lists them by buyer, and posts the receipt once the site confirms and a person approves. During a cutover: The backlog a cutover creates is exactly this shape: physically in, not posted, and nobody sure which system should carry it. Status: Built, shown on request, test data in a demo environment.

### Aged GRNI agent

Goes through goods received but not yet invoiced at month end and gives the reason for each line: a duplicate receipt, a partial delivery, a supplier who never billed. During a cutover: Opening balances inherited from a retired system are the hardest lines to explain, and they are the ones an auditor asks about first. Status: Built, shown on request, test data in a demo environment.

### Credit Hold agent

Shows why an order is on credit hold, with the evidence, and leaves the release to the credit manager. During a cutover: Credit limits reset when entities merge, and orders stop for reasons the new credit team did not set. Status: Training build on Microsoft demo data, not yet run on a customer system.


## Questions

### We are mid-implementation. Is it too early to look at agents?

It is the cheapest moment to decide two things, and both get harder later: which identity an agent uses, and what it is allowed to change without a person saying yes. From Dynamics 365 Finance & Operations version 10.0.47 an agent can hold its own identity and has no permissions until an administrator assigns roles, so the decision sits naturally beside the role design you are already doing. Building the agent can wait. Designing where it fits should not.

### Does this mean changing our implementation partner's plan?

No. Your partner owns the ERP and keeps running it, and we have never competed for that work. What we build reads through Microsoft's own supported integration points and proposes; a person approves anything that moves money or stock. Nothing is added to your tables.

### We are folding an acquisition onto our template. Where does this start?

With the opening balances, because that is the evidence that decays fastest. The receipts and uninvoiced lines carried over from the system being retired can still be explained while the people who posted them are on the project. Six months later the same lines are a reconstruction exercise.

### Our ERP is not Dynamics 365. Does any of this apply?

The pattern does and our builds do not. The receipt, accrual and intercompany problems above are the same on SAP, Oracle and Infor, and we are glad to compare notes on them. What we build runs inside Dynamics 365 Finance & Operations and Business Central, so a build conversation only makes sense if one of those is where you are heading.

### What runs at a customer today?

Across the company, four AI products are in production with 37 agents between them, and the team has delivered generative AI and optimization work inside a customer's Dynamics 365 Supply Chain environment. Of the three month-end agents named on this page, two are built and shown on test data in a demo environment and one is a training build on Microsoft demo data. None of the three is running at a customer, and we will not tell you otherwise on a call.

### Can you work during hypercare without adding risk to the cutover?

Reading is the part that carries no risk, and it is most of the value during hypercare: the exception list, the reason behind each line, and the evidence a person needs to act. Anything that writes waits for a named approver and is logged. If a cutover is in flight, reading first and writing later is usually the right order anyway.


---

Canonical HTML: https://cognilium.ai/dynamics-365/multi-entity-consolidation