Small and medium business | Business Central, N...

Performance & Scalability Strategies for Business Central in Multi-Entity Environments

(8) Share

Report

Posted on by alivedean

We are evaluating Dynamics 365 Business Central for an environment that manages high transaction volumes across multiple legal entities.

I would like to understand from the community:

What architectural or configuration strategies help maintain performance at scale?
How do you manage intercompany processing and reporting without slowing down the system?
Are there recommended approaches for integrations, job queue optimization, or data partitioning in SaaS deployments?
Any lessons learned when scaling Business Central for multi-entity operations?

We are looking for best practices and real-world experiences.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Teagen Boll 1,436 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
You will want to review these questions with a partner to get an idea of what to implement. I've implemented a lot of different business central solutions for organizations with multiple entities. Some things to consider related to your questions:

What architectural or configuration strategies help maintain performance at scale?

You will want to have some level of master data synchronization. You can use the master data management tool in Business Central for this. This eliminates the need to duplicate master record creation across entities. You may also want to look at a tool like Multi-entity management from binary stream which helps handle large amounts of entities at scale with a lot of transactions. There is a case study here related to an implementation for this tool: Migrating The Jim Pattison Group’s Multi-Company Solution to the Cloud with Business Central - Catapult

How do you manage intercompany processing and reporting without slowing down the system?

Usually the number of entities you have and the intercompany module doesn't create much slow down. The modules i've seen in BC that do cause slower response times are when you have complex inventory planning scenarios. With intercompany transactions there is typically minimal risk of slow down.

Are there recommended approaches for integrations, job queue optimization, or data partitioning in SaaS deployments?

The master data management tool is recommended.

I would also recommend setting up your Intercompany tables so that transactions are automatically sent and received.

I would also recommend looking at power automate as a tool to help automate workflows for different processes (year end and month end)

Also determine if you need more than one environment for localization purposes. Intercompany transactions can still be sent across environments in BC.

Any lessons learned when scaling Business Central for multi-entity operations?

I highly recommend Multi-entity management as a tool. It makes management of many entities a lot easier in BC.

If you arent going to go with that tool then I recommend rolling out BC to just a few entities at a time. I've had the best experience rolling it out to smaller entities first and then deploying to larger entities later.

Hopefully that helps give you a starting point when looking into Business Central.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,086 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi, hope the following helps as well.

Understanding the infrastructure of Business Central online

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-environment-topology?wt.mc_id=DX-MVP-5004336

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 12,965 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

For high-volume, multi-entity SaaS environments, performance at scale comes down to smart environment design, controlled background processing, and integration discipline. Avoid overloading a single environment (there’s a 300-company limit and operational complexity increases as company count grows), stagger heavy Job Queue tasks and don’t run large batches during peak hours, and distribute background jobs across multiple users/service principals to avoid concurrency bottlenecks. For integrations, design around SaaS throttling limits (6,000 API calls per 5-minute window per user and limited concurrent requests), use event-driven patterns instead of aggressive polling, and separate integration workloads across users if high throughput is needed. For intercompany, treat it as a managed workload (off-peak processing, clean master data mapping). Since SaaS doesn’t allow SQL-level partitioning, scaling is achieved through smart company/environment separation, archiving strategies, and external reporting/data warehouse offloading. Most real-world performance issues come from poorly timed background jobs and chatty integrations — not core posting volume — so telemetry monitoring is critical from day one.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,977 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hey, these are my suggestions -

Use Business Central’s Intercompany feature for transactional automation (sales/purchases, AR/AP) when possible — it’s purpose-built and avoids custom cross-company posting logic.

Batch intercompany posting: Avoid one-record-at-a-time intercompany calls. Use batch/queue patterns that create documents in the source company and then push consolidated batches to the target. This lowers locks and reduces round trips.

Archive old data: Move historic ledger lines and audit trails to some other storage storing feature like Data Lake — keep only recent data in the transactional database. Archival reduces table size and improves day-to-day performance.

Avoid heavy logic in posting triggers. Posting routines are frequent and cause locks — any custom extension that touches posting should be optimized, tested under load, and pushed to background jobs if possible.

Do mark as verified if it helps.

Aman K

Was this reply helpful? Yes No