A business needs to know if it made money. But a nonprofit needs to know if it spent money the right way. Those are not the same question, and they cannot be answered by the same system. 
Yet thousands of nonprofits (including many well-run, growing ones) are trying to do exactly that. They're managing restricted grants, tracking multiple funding streams, and preparing board-level financial statements inside software designed for a hardware store or a marketing agency. The workarounds accumulate quietly. Spreadsheets multiply. Processes get built by one person who just knows how it works. 
Fund accounting exists to solve this problem. So does purpose-built nonprofit ERP software. This post covers what fund accounting is, where commercial accounting tools fall short, and how nonprofit ERP platforms like Tigunia Spark solve fund accounting for small and mid-sized organizations. 

What's the Core Difference Between Fund Accounting And Commercial Accounting?  

Walk into any business and ask the finance team how things are going. Chances are, the answer involves revenue, margins, and whether the company is on track to hit its numbers. Commercial accounting was built for exactly that conversation. The entire system, from how transactions are categorized to how reports are generated, is designed to measure financial performance against a single bottom line. 
Nonprofits don't have a bottom line. They have obligations. 
Every dollar that comes into a nonprofit organization can carry a different set of rules. Government funds for workforce development cannot subsidize a fundraising dinner. And a donor gift earmarked for a new facility cannot cover payroll during a slow month. These aren't suggestions. They are binding commitments that the organization is legally and ethically required to honor, and honoring them requires knowing, at all times, exactly where every dollar sits and what it is allowed to do. 
Commercial accounting was never designed to track money that way. Fund accounting was. It is the system built specifically around the reality of how nonprofits receive, manage, and report on money. For mission-driven organizations managing multiple programs and funding sources, cloud ERP software built for the nonprofit sector brings all of that structure into a single, connected system. 

Why Nonprofits Have to Track Money Differently Than Businesses 

Commercial accounting tools are designed to track an entity's profit and loss. Nonprofit accounting doesn't work that way.  
Nonprofit money arrives with conditions attached: a grant restricted to a specific program, a donation designated for capital improvements, unrestricted funds that still need to be reported separately from everything else. Tracking all of that accurately, in real time, in a way that satisfies auditors and gives your board confidence, requires a different kind of system entirely. That system is called fund accounting, and nonprofit ERP software is how organizations put that capability into practice. 
Those conditions are not internal preferences. They are legal and ethical obligations. When a donor gives to a specific cause, or a foundation awards a grant for a defined program, that money cannot be redirected without consequence. Nonprofits that commingle restricted and unrestricted funds, even unintentionally, expose themselves to audit findings, damaged funder relationships, and in serious cases, legal liability. 
Board members carry fiduciary responsibility for every dollar that passes through the organization. Meeting that responsibility means having real visibility into fund-level activity throughout the year, not just a year-end summary. When a funder asks about remaining funding balances, or an auditor questions how a restricted fund was spent, the answer needs to come from the system, not a spreadsheet someone built the night before. A profit-and-loss statement was never designed to provide that kind of visibility. But fund accounting is. 

Why Can’t Nonprofits Use Commercial Accounting Software?  

The short answer is that commercial accounting software was designed to solve a different problem. It tracks business transactions cleanly and efficiently, and for a company selling products or billing clients, it does exactly what it needs to do. The trouble starts when a nonprofit tries to bend that structure around a completely different set of financial rules. 
And most do try. The software is familiar, the price is right, and there is usually someone on the team who already knows how to use it. So the organization makes it work, at least for a while. 
What that looks like in practice is a growing collection of patches. A separate tracking category for every active grant. Sub-accounts created to approximate fund boundaries the software doesn't actually recognize. Spreadsheets running alongside the system to capture what the system can't. None of it is wrong, exactly. All of it is fragile. 
The fragility shows up most clearly at reporting time. Pulling together a board report means gathering data from several places, reconciling numbers that should already match, and spending hours producing something the right system would generate in minutes. It is time no one has and work that shouldn't exist. 
It also creates a concentration risk that most organizations don't fully recognize until it's too late. When the process lives in one person's head, the organization isn't running on software. It's running on that person. A resignation, a retirement, or even a leave of absence exposes just how much institutional knowledge was holding the whole thing together. 
Perhaps most concerning is what goes undetected in the meantime. Commercial software has no way to flag when a restricted fund is being drawn down incorrectly. There are no guardrails, no alerts, no enforcement. By the time the problem surfaces, whether in an audit or a funder conversation, the cost of fixing it almost always exceeds what a purpose-built system would have cost from the start. 

How Purpose-Built ERP Software Handles Nonprofit Fund Accounting 

When software is built specifically for nonprofit finance, the mechanics underneath it look completely different from a commercial accounting tool. Rather than forcing fund tracking into a structure designed for profit and loss, purpose-built ERP software organizes everything around the way nonprofit money actually works: by fund, by restriction, and by obligation. 
Here is what that looks like in practice: 

• Fund Isolation. 
  Each transaction is assigned to a specific fund at the point of entry, not sorted retroactively. At any given moment, the organization has a clear, current picture of every fund balance without running a manual calculation or opening a spreadsheet. 

• Restriction Enforcement. 
  The system carries the rules of each fund forward into every transaction. If an expense doesn't qualify under a restricted grant, the software flags it before it posts. That protection is structural, not dependent on someone remembering to check. 

• Inter-Fund Transfers. 
  Money sometimes needs to move between funds, and when it does, purpose-built ERP software handles it properly. Every transfer is recorded with full context: the reason, the amount, the date, and the authorization behind it. 

• Fund-Level Reporting. 
  Nonprofits are expected to produce a statement of financial position, a statement of activities, and a statement of functional expenses. That last report is often the one funders and auditors scrutinize most closely. Purpose-built ERP software generates all three as standard outputs, no reformatting, no manual assembly, no exporting to another tool to make them presentable. 

What To Look For In Nonprofit ERP Software  

The nonprofit software market is crowded, and not all of it deserves the label. Some products are general accounting tools with a nonprofit skin applied at the surface level. Others were built for large institutions with dedicated IT teams and implementation budgets that most small and mid-sized organizations will never have. Finding the right fit means knowing what to look for before you start evaluating options. 
Here is what genuinely purpose-built nonprofit ERP software should do: 

1. Stops ineligible spending before it happens. Restriction enforcement shouldn't rely on a manual review after the fact. The system should recognize fund rules at the transaction level and prevent the wrong expense from posting in the first place. 
2. Keeps fund balances current without manual work. If reconciling fund balances requires a dedicated process at the end of every reporting period, the software is creating work rather than eliminating it. Balances should be accurate and accessible at any point in the month. 
3. Produces the Statement of Functional Expenses as a native report. This is one of the most scrutinized documents a nonprofit produces. It should come directly out of the system, formatted and ready, not pieced together from an export. 
4. Delivers board-ready reporting on demand. A finance team shouldn't need days of preparation to walk into a board meeting with accurate numbers. The right software makes that report a matter of clicks, not a project. 
5. Works for the whole finance team, not just accountants. Nonprofit finance teams are often small and wear many hats. Software that requires deep accounting expertise to operate safely creates the same single-point-of-failure problem the organization was trying to solve. 
6. Grows with the organization. A platform that handles today's fund structure should also handle a more complex one three years from now, without forcing a disruptive migration or a round of expensive custom development. 

Features Differences Between Traditional Business ERP and Nonprofit Fund Accounting ERP Software 

Here is a feature-by-feature comparison for nonprofit organizations evaluating finance software options: 

How to Know When Your Nonprofit Needs Better Accounting Software 

A nonprofit needs better accounting software when its current system requires manual workarounds to produce basic reports, depends on one person's institutional knowledge to function, or cannot show fund balances in real time. These are not minor inefficiencies. They are signs that the software is no longer serving the organization. 
Here are the specific triggers to watch for: 

• Every reporting cycle starts with a spreadsheet. 
  Board reports, funder updates, and audit prep should come directly from the accounting system. If your team is exporting data and rebuilding reports in a separate tool every single time, the system is creating work it should be eliminating. 

• One person holds the whole process together. 
  When the finance process only works because a specific staff member knows how it was set up, the organization is one departure away from a crisis. A long-tenured accountant announcing retirement is one of the most common moments that pushes nonprofits to finally make a change, because it forces a reckoning with how much tribal knowledge was holding things together. 

• Fund balances aren't visible without digging. 
  If answering a simple question about a grant balance requires opening a spreadsheet or running a manual calculation, the system is not doing its job. Real-time fund visibility is a baseline expectation, not a premium feature. 

• Years of investment haven't made it the right fit. 
  Time spent in a system is not a reason to stay. The hidden cost of workarounds compounds every month and never appears on a budget line. Most organizations that make the switch find the return comes faster than they expected. 

How Tigunia Spark Solves the Fund Accounting Problem for Nonprofits 

Tigunia Spark solves the fund accounting problem for nonprofits by replacing manual workarounds with a system built around the way nonprofit money actually works. Fund restrictions are enforced automatically. Fund balances are visible in real time. Board reports and funder statements are generated directly from the platform, without spreadsheet assembly or off-system formatting. 
Spark was built from the ground up for small and mid-sized nonprofits. Not retrofitted from a commercial tool. Not scaled down from an enterprise platform designed for organizations ten times the size. Every part of the system, from how transactions are categorized to how reports are produced, reflects the financial reality of a mission-driven organization managing multiple funds, multiple restrictions, and multiple stakeholders at once. 
Implementation doesn't require an IT department, and training and support is structured around the way small finance teams actually operate, not how large enterprise rollouts typically work. For mission-driven organizations that have spent years making the wrong system work, the transition is more straightforward than most expect. 
If your current system was built for a different kind of industry, it may be time to see what one built for yours can do. 

FAQs for Fund Accounting ERP Software 

 
Is fund accounting more complicated than regular accounting?  
No, fund accounting isn’t more complicated than commercial accounting, but it’s structured differently. Commercial accounting tracks a single bottom line. Fund accounting tracks multiple funds simultaneously, each with its own balance and restrictions. Purpose-built ERP software handles that complexity automatically, which often makes nonprofit finance simpler in practice, not harder. 
Can't a nonprofit just use QuickBooks with some customization? 
QuickBooks can be adapted for nonprofit use, but the adaptations compound over time. Categories multiply, manual reconciliations pile up, and the reports boards and funders actually need still require off-system assembly. Most nonprofits that have tried this approach find that the ongoing cost of maintaining the workaround exceeds the cost of switching to software built for the job. 
What is the difference between a restricted and unrestricted fund? 
A restricted fund contains money that must be spent on a specific, donor- or grantor-defined purpose. An unrestricted fund can be used at the organization's discretion. Nonprofits are legally obligated to honor those restrictions, and fund accounting software enforces them at the transaction level to prevent commingling and ensure compliance. 
What makes Tigunia Spark different from other nonprofit accounting tools? 
Tigunia Spark was designed specifically for small and mid-sized nonprofits, not adapted from a commercial platform or scaled down from an enterprise system. Fund mechanics, restriction enforcement, inter-fund transfers, and board-level reporting are all native to the platform. There are no add-ons required to make it work the way a nonprofit needs it to. 
Is it difficult to switch from commercial accounting software to nonprofit ERP software? 
For most small and mid-sized nonprofits, the transition is more manageable than expected. Tigunia Spark is designed for implementation without a dedicated IT department, and training and support are structured around the way nonprofit finance teams actually work. The more important question is what staying with the wrong system is already costing the organization in time, risk, and staff capacity. 
What is the Statement of Functional Expenses and why does it matter? 
The Statement of Functional Expenses is a financial report that shows how an organization's expenses are allocated across programs, management, and fundraising activities. Many funders require it, and auditors expect it as part of a nonprofit's standard financial statements. Purpose-built fund accounting ERP software produces it as a native output. Commercial accounting tools typically cannot generate it without significant manual work. 
How does fund accounting software help with nonprofit audits? 
Fund accounting software supports audit readiness by maintaining a complete, traceable record of every transaction by fund, including restriction enforcement, inter-fund transfers, and fund-level balances throughout the fiscal year. When an auditor asks how a restricted grant was spent, the answer comes directly from the system rather than a reconstructed spreadsheet. 
Can nonprofit ERP software handle multiple funding sources at the same time? 
Yes. Managing multiple funding sources simultaneously is exactly what nonprofit ERP software is designed to do. Each grant, donation, or revenue stream is tracked within its own fund, with its own balance and its own rules, while the organization maintains a complete view of its overall financial position across all funds at once. 
When should a nonprofit consider upgrading to ERP software? 
A nonprofit should consider upgrading to purpose-built ERP software when board reports require manual assembly, fund balances are not visible in real time, the finance process depends on one person's institutional knowledge, or the organization has outgrown the workarounds holding its current system together. The longer those conditions persist, the higher the compounding cost of staying put. 

The post What’s the Difference Between Fund Accounting and Commercial Accounting? appeared first on ERP Software Blog.

A guide for small business owners who’ve heard the term but never needed to understand it, until now.
Early in my consulting career, I walked into a project ready to talk implementation timelines, data migration, and go-live plans. The executive sponsor pulled me aside before my first session with the team and said something that stopped me in my tracks: “You need to change your approach. These people cannot spell ERP.”
It was humbling and one of the best pieces of advice I’ve ever received. Because he was right. And more importantly, it didn’t matter. These were smart, capable people running a real business. They just didn’t need to care about the acronym. They cared about getting orders out the door, paying their people on time, and knowing whether they were making money.
That moment shaped how I think about technology and the people who use it. So let me try to bridge that gap here.
How Small Businesses End Up Running an “Unintentional ERP”?
ERP stands for Enterprise Resource Planning.
Which, if you’ve never heard it before, tells you almost nothing useful. Here’s a better way to think about it. Most growing businesses run on a collection of systems that don’t talk to each other. Your accounting is in QuickBooks. Your inventory is in a spreadsheet. Your orders come in through your website or over the phone and get tracked in a shared inbox or another spreadsheet. Your team’s schedules live somewhere else entirely. And at the end of the month, someone, probably you or a very tired office manager, manually pulls all of that together to figure out where you stand. That’s not a failure. That’s just how businesses grow. You add tools as you need them, and at some point, you have a patchwork of systems that mostly work, most of the time.
What Does ERP Software Actually Do?
An ERP is what happens when you replace that patchwork with a single connected system. One platform that handles your finances, your inventory, your operations, your sales, and your reporting, all sharing the same data, in real time.
A simple example of how ERP supports a Small Distribution Business
A Simple Example: Let’s say you run a distribution company with 20 employees. A customer calls and places an order. Today, someone takes that order, emails the warehouse, the warehouse checks stock (maybe in a spreadsheet, maybe by walking over and looking), someone invoices the customer in QuickBooks, and at the end of the week someone else tries to reconcile what went out the door with what got billed. With an ERP, that same order triggers everything automatically. Inventory updates the moment the order is placed. The invoice is generated. The warehouse gets a pick list. Your financials reflect the sale. And you can see all of it from one screen, right now. Same outcome. A fraction of the manual work. And far fewer chances for something to fall through the cracks.
How does Microsoft Dynamics 365 Business Central help small and mid-sized businesses?
ERP used to be something only large enterprises could afford or justify. Implementing one meant million-dollar projects, years of disruption, and armies of consultants. That’s no longer true. Modern cloud-based ERP systems like Microsoft Dynamics 365 Business Central are built specifically for small and mid-sized businesses. They’re subscription-based, meaning no massive upfront investment. They’re designed to go live in weeks to months, not years. And they’re built to grow with you, so you’re not re-implementing every time your business changes. The real question isn’t whether you can afford an ERP. It’s whether you can afford to keep doing things the way you’re doing them as your business grows.
How do I know if I need an ERP system?
There are a few signals that tend to show up before businesses start looking at ERP:

• You’re making decisions based on data that’s days or weeks old.
• Month-end close takes longer than it should because reconciliation is manual.
• You’ve hired people whose primary job is moving data between systems.
• You’ve lost an order, missed a shipment, or overbilled a customer because of a spreadsheet error.
• You can’t easily answer the question: “Are we making money with this customer?”

If any of those sound familiar, you’re not behind. You’re just ready for the next step.
How do we move from what we use today to an ERP system?
Going back to that executive sponsor’s advice, the lesson wasn’t that the team needed to learn the jargon. The lesson was that the technology needed to meet them where they were. The best ERP implementations I’ve been part of weren’t the ones with the most sophisticated configurations. They were the ones where the people using the system understood why it was built the way it was and felt like it was designed for how they actually work. Technology is only as valuable as the people using it. And those people don’t need to be able to spell ERP. They just need to feel confident that their tools are working for them and not the other way around.
That’s the job. And it’s worth doing right.
Interested in learning more about what a modern ERP could look like for your business? Let’s connect.

The post What Is ERP for Small Business? (And Why You’re Already Using One Without Knowing It) appeared first on ERP Software Blog.

Data migration is one of the most reliable ways to derail a Business Central go-live. RapidStart is slow on large datasets, cannot write to protected tables like item ledger entries or G/L entries, and has no way to suppress the change log during bulk operations, leaving teams with thousands of audit entries that describe nothing useful.
This webinar covers the Import Export PowerTool, a completely free app from Insight Works for Business Central, and walks through how it handles imports, exports, bulk updates, and direct table writes for common scenarios that RapidStart simply was not designed for.

Date and time: June 17, 2026 | 1:00 pm EDT (North America)
Register: https://dmsiworks.com/events/business-central-data-migration

What You'll Learn:

• Identify why RapidStart fails on bulk updates, ledger imports, and iterative migrations
• Import and export data across any Business Central table, including protected tables
• Control change log behavior during bulk operations to avoid performance and audit noise
• Handle lot numbers, serial numbers, and dimensions in item journal imports automatically
• Perform scoped bulk updates and deletions with field-level validation and confirmation prompts
• Evaluate the tool's fit for opening balance loads, sandbox-to-production copies, and post-go-live cleanup

Register to attend live and see the Import Export PowerTool applied to real migration scenarios in Business Central.
Can't attend live? Register anyway, and we'll send you the recording.
 

The post Faster Data Migration in Business Central with Import Export PowerTool appeared first on ERP Software Blog.

Most ERP upgrade conversations begin with scope and timelines, but a more effective starting point focuses on risk, operational impact, and what will change once you move to Business Central. Organizations running Dynamics NAV are often balancing day-to-day system demands with longer-term concerns about support and scalability. As each NAV version moves closer to end of life, limitations around security updates, compliance, and system performance become more noticeable. Internal teams can end up spending more time maintaining existing infrastructure instead of improving processes, which makes early planning an important advantage.

How to Evaluate Your Current Environment

A successful migration starts with a clear understanding of your current system. Many NAV environments include years of C/AL customizations that were built to solve specific business needs. These do not transfer directly into Business Central, so each one requires evaluation. Some will be rebuilt as extensions, some can be replaced with standard functionality, and others may no longer be necessary. At the same time, data strategy plays a major role. While it may seem practical to bring all historical data forward, most organizations focus on open balances, active transactions, and a defined range of recent history. Data quality is often the bigger priority, since duplicate records, inconsistent naming, and unreconciled balances can create challenges during testing and after go live if they are not addressed early.

What to Expect During Migration

Migration timelines depend largely on system complexity, level of customization, and overall data readiness. A newer NAV system with minimal modifications may take four to six months to transition, while older environments with extensive custom objects and integrations can take closer to six to twelve months. Extension development is typically the most time-intensive part of the process, and completing this work thoroughly before launch helps reduce disruption later. Licensing is another area that benefits from a broader perspective. Moving from a perpetual NAV model to a subscription-based Business Central model shifts how costs are structured, and a full evaluation should include infrastructure, maintenance, and upgrade effort. Many organizations find that this creates more predictable long-term costs while reducing reliance on internal IT resources.

Preparing Your Team for Change

User adoption tends to be more straightforward than expected, especially when planning is intentional. Business Central maintains familiar core functionality while introducing a more modern interface and improved workflows. Role-based training delivered close to go live helps users stay engaged and build confidence quickly. Organizations that identify internal champions often create a stronger support system, allowing teams to resolve questions efficiently and maintain momentum after launch. In addition to usability improvements, Business Central introduces ongoing innovation through regular updates, Microsoft integrations, and AI-driven capabilities, allowing organizations to continue improving without large-scale upgrade projects.

Getting Started

The best place to begin is with a structured assessment of your current NAV environment, including customizations, data quality, integrations, and operational dependencies. This process creates a clear roadmap with realistic timelines, cost expectations, and defined next steps. Western Computer works with organizations across manufacturing, distribution, and professional services to guide this transition. Connect with our team today and we can help you get started with building a migration strategy that aligns with your business goals and reduces uncertainty along the way.

The post Top Questions to Answer Before Moving from Dynamics NAV to Business Central appeared first on ERP Software Blog.

For years, enterprise AI conversations have focused on one goal: helping users find information faster.
Whether through chat interfaces, copilots, or intelligent assistants, the promise has largely been the same. Ask a question, retrieve data, receive recommendations, and make decisions more efficiently.
But a new question is emerging inside enterprise ERP environments:
What happens when AI can do more than provide answers?
What happens when users can execute business transactions through conversation instead of navigating forms, screens, and workflows?
That shift is becoming increasingly relevant for organizations running Dynamics 365 Finance and Supply Chain Management, where operational speed often depends on how quickly teams can move from intent to action.
This is the focus of DynaTech's upcoming Dynamics 365 F&SCM Webinar, a live session exploring how AI agents powered by the Model Context Protocol are changing the way users interact with enterprise ERP systems.
Rather than discussing AI as a future possibility, this webinar examines how organizations can begin enabling real transaction execution through natural language today.

Enterprise AI Is Entering a New Phase

The first wave of enterprise AI helped users access information more efficiently.
The next wave is focused on execution.
Across finance, procurement, operations, and supply chain functions, employees still spend significant time performing repetitive ERP activities. Creating orders, initiating requisitions, updating records, validating transactions, and navigating system interfaces remain part of everyday operations.
While modern AI assistants can simplify information retrieval, they often stop short of performing the work itself.
Users still need to open applications, locate records, enter information, and complete transactions manually.
As organizations continue investing in automation and operational efficiency, this gap between intelligence and execution is becoming more visible.
The upcoming AI agents webinar explores how organizations can begin closing that gap through a different approach to ERP interaction.

Why Dynamics 365 Leaders Are Paying Attention

Organizations using Dynamics 365 Finance and Supply Chain Management manage some of the most critical business processes in the enterprise.
Procurement activities, inventory management, financial operations, purchasing workflows, order processing, and supply chain execution all depend on efficient ERP interactions.
Even small delays across these processes can create broader operational impacts.
For example:

• Procurement requests may wait for manual entry
• Sales teams may experience delays while creating orders
• Remote employees may struggle with ERP accessibility
• Operational teams may spend more time navigating systems than executing work
• High-volume environments may face productivity constraints caused by repetitive interactions

Many organizations have already optimized processes, workflows, and infrastructure.
The next opportunity lies in improving how users engage with the ERP itself.
This is one of the key themes that will be explored during the Dynamics 365 webinar.

What Makes This Webinar Different?

There is no shortage of discussions around AI.
However, many conversations remain focused on concepts, predictions, and future possibilities.
This session takes a different approach.
The webinar is designed as a practical and technical walkthrough of how execution-oriented AI can work within real enterprise environments.
Attendees will gain insight into:

From AI Assistance to AI Execution

Most AI tools are built to provide information, recommendations, or guidance. AI agents take the next step by performing actions on behalf of users. Learn how execution-driven AI differs from traditional assistant-based experiences and why this distinction matters for enterprise ERP environments.

Natural Language as a New ERP Interface

Explore how users can initiate business transactions through conversational prompts instead of navigating multiple screens, forms, and workflows within Dynamics 365 Finance and Supply Chain Management.

Microsoft Teams as an Operational Workspace

See how Microsoft Teams can serve as a unified entry point for ERP interactions, allowing users to execute business processes from the collaboration platform they already use every day.

Inside the Model Context Protocol (MCP)

Gain insight into the architecture behind AI-powered execution. Understand how the Model Context Protocol enables secure communication between AI agents and Dynamics 365 while maintaining enterprise governance and control.

Practical Use Cases and Live Demonstrations

Watch real-world scenarios that demonstrate how AI agents can create Sales Orders and Purchase Requisitions through natural language inputs, helping reduce operational friction and accelerate execution.

Meet the Speaker: JT Gorrell

As VP of Customer Success at DynaTech Systems, JT Gorrell has spent more than two decades helping organizations navigate ERP transformation, enterprise technology adoption, and large-scale operational change. His experience spans program leadership, business process optimization, and successful Dynamics 365 initiatives across complex enterprise environments.
During this session, JT will provide a practical look at how AI agents and the Model Context Protocol (MCP) are changing the way users interact with Dynamics 365 Finance & Supply Chain Management, enabling faster execution, improved accessibility, and a more conversational approach to ERP operations.

Understanding the Model Context Protocol

One of the most discussed topics in modern AI architecture is the Model Context Protocol.
As organizations explore AI-powered execution, a common concern quickly emerges:
How can AI interact with enterprise systems while maintaining security, governance, and control?
The Model Context Protocol provides a framework that helps address this challenge.
Instead of relying solely on user interface interactions, MCP enables structured communication between AI systems and business applications.
Within Dynamics 365 Finance and Supply Chain Management, this creates new possibilities for how transactions can be initiated and executed.
During the MCP webinar, attendees will gain a clearer understanding of:

• How MCP supports enterprise integration scenarios
• Why backend interaction differs from traditional UI-driven workflows
• The role of governance and control in AI execution
• How organizations can evaluate MCP within their ERP strategy

Rather than presenting theory alone, the session connects these concepts to practical Dynamics 365 use cases.

What You'll See During the Live Demonstration

One of the highlights of the session is the live demonstration.
Attendees will see how AI agents interact with Dynamics 365 environments using natural language inputs.
The demonstration is expected to showcase scenarios such as:

• Sales Order creation through conversation
• Purchase Requisition creation using natural language
• Transaction execution without navigating multiple ERP screens
• Interaction through Microsoft Teams
• Backend execution powered by MCP architecture

For organizations evaluating Dynamics 365 AI Agents, seeing these capabilities in action provides valuable context that is difficult to capture through documentation alone.
The live walkthrough helps bridge the gap between technical architecture and practical business application.

Who Should Attend This Dynamics 365 F&SCM Webinar?

This session is particularly valuable for organizations evaluating the future of ERP operations.
Recommended attendees include:

Finance Leaders

Gain insight into how execution-focused AI may impact financial operations, transaction processing, and user productivity.

Supply Chain Professionals

Understand how conversational execution can support faster operational workflows across procurement and supply chain functions.

ERP and Transformation Teams

Explore emerging approaches to ERP modernization and operational efficiency.

Dynamics 365 Architects and IT Leaders

Learn how MCP-based architectures support secure interaction between AI agents and enterprise systems.

Operations Executives

Evaluate how AI-driven execution may influence productivity, accessibility, and process optimization initiatives.

Why DynaTech Is Leading This Conversation

As a Microsoft-focused solutions provider, DynaTech works with organizations across Dynamics 365, Power Platform, Microsoft Fabric, Azure, AI, and enterprise modernization initiatives.
The webinar reflects DynaTech's commitment to helping organizations understand not only where enterprise technology is heading, but how it can be applied in practical business environments.

Deep Dynamics 365 Expertise

Extensive experience across finance, supply chain, CRM, data, and business process transformation initiatives.

Focus on Emerging Microsoft Technologies

Helping organizations evaluate innovations that can improve operational performance and user experience.

Business and Technical Perspective

Combining architectural understanding with practical business outcomes.

Real-World Demonstrations

Moving beyond theory to show how technologies work in operational environments.
For organizations exploring ERP Process Automation, this webinar provides an opportunity to learn directly from professionals working at the intersection of Dynamics 365 and enterprise AI.

Save Your Spot

The conversation around enterprise AI is rapidly evolving.
The next generation of innovation inside Dynamics 365 Finance and Supply Chain Management is not just about accessing information faster. It is about enabling action.
If your organization is evaluating Dynamics 365 AI Agents, ERP Process Automation, or the potential of the Model Context Protocol, this live Dynamics 365 F&SCM Webinar offers a valuable opportunity to explore these concepts through a practical, technical lens.
Join DynaTech and discover how AI-driven execution is reshaping the future of enterprise ERP operations.
Register today and secure your place in the webinar.

The post Dynamics 365 F&SCM Webinar: What Enterprise Teams Need to Know About AI-Driven ERP Execution appeared first on ERP Software Blog.

As more organizations recognize the transformative potential of AI, many are eager to integrate digital agents into their workflows. Tools powered by AI can boost efficiency, uncover new insights, and change how work gets done. However, the integration of AI comes with its own set of challenges.

Here are 5 major challenges organizations face when integrating AI agents: 

Integrating multi-agent systems securely and effectively brings both technical and organizational challenges. For instance, the presence of siloed teams and fragmented communication can be major barriers by hindering collaboration and slowing progress. 
Successful integration often demands a cultural and structural shift: one that encourages cross-functional cooperation and embraces change.
However, such transformation can be met with resistance from employees especially if they are unfamiliar with AI or wary of its implications. Besides, organizations must be prepared to invest in advanced technologies and infrastructure, which can be both costly and time intensive. Without strategic planning and strong leadership, these hurdles can entirely stall or derail AI adoption. 
Integrating AI at scale is a tech initiative, and a human challenge as well. Managing organizational change requires ongoing support, leadership alignment and clear communication  across organizations  to address concerns.  

While AI integration helps reduce the overall workforce needed for specific tasks, human collaboration remains essential to ensure performance, accountability and alignement with business goals. Thus, finding the optimal human-agent ratio is key for successful multi-agent system deployment. Leaders must evaluate the number of AI agents required for specific tasks and the extent of human oversight necessary to maintain these standards.
Striking the right balance requires careful strategic planning and resource allocation. Assigning too many agents to a single human can lead to decision fatigue, increased business risk, and potential employee burnout. Conversely, too much human oversight can limit efficiency and reduce the benefits of automation.  

Implications to Keep in Mind 

Hence, finding the right human-agent ratio is not a one-size-fits-all formula. It demands ongoing assessment, flexibility and a willingness to adapt as systems and teams evolve.

3. Scaling AI

Scaling AI within organizations is as much about people and culture as it is about technology. Organizations that focus on adaptability, education, and collaboration will be best positioned to leverage AI’s greatest benefits.
As business demands grow, there is a widening gap between what human teams alone can deliver. What is needed to stay competitive becomes more pronounced. AI helps bridge this gap, but only when it is integrated strategically.

Importantly, scaling AI is not a one-time effort. It involves iteratively refining systems, workflows, and models to align with changing needs and new opportunities.

One of the most important steps to successfully scale AI across an organization is investing in AI literacy across the workforce. It is not enough to implement intelligent systems. In fact, AI literacy has become the most in-demand skill for 2025, according to LinkedIn. Employees must be empowered to collaborate and work effectively alongside digital agents, adapt to evolving roles, and embrace new ways of thinking. These human-centric strengths are equally important in a way that the future favors those who can blend their AI expertise with skills that machines cannot mimic.
Organizations should take upskilling and reskilling initiatives, such that employees are equipped with both confidence and competence to work alongside AI. This comprehensive approach includes continuous learning, communication and cultural support to make AI adoption both effective and sustainable.
In essence, AI literacy is the foundation to understanding how AI works, where it adds value, and how to leverage it in day-to-day workflows. When employees are empowered, organizations can scale AI more confidently, efficiently and ethically.

As organizations increasingly integrate AI into decision-making, it becomes essential to strike the right balance between automated systems and human oversight. While AI can significantly enhance efficiency, some decisions still require the nuance and responsibility of human judgment. In particular those with ethical, strategic, or high-stakes implications.
To ensure AI complements rather than replaces human roles, organizations must establish clear policies and governance frameworks that define the role of automated systems versus human input. This involves transparent communication, hands-on training, and clear demonstrations of how AI supports and enhances human roles.

AI systems must be deployed with careful consideration of their ethical implications.

In short, balancing automation with essential human oversight is a strategic and cultural challenge. Leaders must assess how automated decisions impact fairness, accountability, and stakeholder well-being. Subsequently, strong guidelines and escalation protocols are crucial to maintaining ethical and moral responsibilities.

Final Thoughts

Embedding AI agents into organizational workflows is a transformative process that demands careful navigation and more than just deploying new technology.
Without a doubt, understanding and proactively addressing technical, strategic and cultural challenges is essential for organizations aiming to stay competitive in an AI-driven future. Those who successfully navigate the challenges integrating AI Agents and master this balance will eventually lead the way in shaping the workplaces of tomorrow with confidence.

The post 5 Challenges Organizations Face When Integrating AI Agents into their Workflows appeared first on ERP Software Blog.

Most FDA warning letters can be traced back to Form 483 observations that were not fully resolved. The same issues appear during inspections, which get addressed at a surface level, and then show up again later.
Over time, repeated findings escalate into warning letters. In many cases, these issues persist even in environments supported by FDA regulatory compliance software because the underlying data and systems are not fully connected.
In this article, we look at why these issues keep repeating, where they actually come from, and why surface-level fixes fail during inspection.
We are also taking this discussion offline with a small group of senior life sciences leaders in a series of private, peer-level Executive Dinners. They will focus on how these issues are showing up in practice and what organizations are doing differently to stay inspection-ready.

Find an Executive Dinner Near You

Most discussions around Form 483s stay focused on procedures and documentation. That’s only a part of the picture. The pattern becomes clearer when you look at how data is created, managed, and connected across systems.
When systems aren’t connected, it becomes harder to manage data and processes consistently. That’s when gaps start to appear, and the same issues tend to repeat.
At STAEDEAN, we help life sciences organizations fix what’s causing these issues in the first place. That usually means moving away from fragmented systems and manual processes to systems that keep data accurate, traceable, and controlled.

What Form 483 Observations Actually Indicate:

Most Form 483 observations focus on familiar issues:

• Incomplete or inconsistent records
• Weak or missing audit trails
• Poor deviation handling
• Gaps in supplier verification
• Limited traceability

These are usually treated as process or training gaps. Teams update standard operating procedures (SOP), retrain staff, and add more checks and approvals. The problem is that these actions rarely address the underlying cause.
In many cases, data is spread across systems that don’t fully connect, and key controls are not enforced consistently. As a result, the same problems return, even after they’ve been “fixed.”

Where Things Break Down in Practice

In most life sciences environments:

• Manufacturing data sits in ERP
• Laboratory data is managed in LIMS
• Quality events are tracked in separate systems
• Supporting documentation is stored in spreadsheets or shared drives

Most organizations already have these systems in place. The issue is not the presence of systems, but how well they are connected and controlled.
During inspections, regulators expect a complete and consistent record across all systems. That means linking production, lab results, deviations, and approvals into a single, coherent view. When systems aren’t connected, teams have to assemble that view manually. This introduces delays and increases the likelihood of inconsistencies or missing information.
At that point, compliance depends on how well teams can reconstruct the data.
For example, during an inspection, a team may be asked to show the full history of a batch—covering raw materials, production steps, lab results, and any deviations.
In a disconnected environment, that information sits across ERP, LIMS, and quality systems. Teams then have to pull reports from each system, cross-check them, and manually align timelines and records.
It’s common to find that timestamps don’t match, a deviation isn’t fully linked to the batch, or a supporting record is missing or stored outside the system. At that point, the discussion shifts from demonstrating control to explaining gaps.

Why Issues Escalate into Warning Letters

When Form 483 observations are handled as isolated fixes, the underlying conditions remain unchanged.
Overtime:

• The same gaps reappear
• Inconsistencies accumulate
• Confidence in the data weakens

Most systems appear compliant during normal operations. The gaps become visible when data is tested during inspection.
By the time a warning letter is issued, the impact is already operational:

• Production timelines are affected
• Batch release slows down
• Remediation efforts expand
• Approvals are delayed
• Future inspections become more rigorous

For companies with active pipelines or time-sensitive products, these delays directly affect revenue, supply commitments, and planning.

Common Risk Areas Behind Warning Letters

Most findings fall into a few recurring areas:

• Data integrity and recordkeeping 

Incomplete records and weak audit trails, often linked to manual processes or fragmented systems.

• Process monitoring and traceability 

Limited visibility across materials, suppliers, and production makes it difficult to demonstrate control.

• Documentation and regulatory alignment

Gaps between submitted documentation and actual operational data.

• Commercial or conduct-related issues

Less frequent, but still relevant in certain cases.
Across the first three areas, the same underlying issue appears repeatedly: data is not consistently connected across systems.

Why Disconnected Systems Increase Risk

When systems operate in silos:

• Data is entered or transferred manually
• Records may not match across systems
• Updates can be delayed or missed
• Traceability becomes harder to prove

This shifts the compliance burden from the system to the people using it. As a result, teams spend more time collecting and reconciling data than reviewing it. Under inspection pressure, that difference becomes critical because regulators are not assessing effort. They are assessing whether the data is complete, consistent, and reliable.

What Inspection-Ready Operations Look Like

Organizations that perform well during inspections reduce reliance on manual processes and embed control into their systems.
Typically, they have:

• Connected data across manufacturing, quality, and laboratory systems
• Automated audit trails
• Controlled and traceable approvals
• End-to-end traceability for materials and batches
• Linked deviations and quality events
• The ability to produce records quickly without manual reconstruction

In these environments, compliance is part of daily operations rather than something assembled during audits.

A Practical Way to Assess Your Risk

Consider how your team would respond to a typical inspection request.
If asked to provide a complete history for a batch, including deviations and approvals:

• How long would it take to gather the information?
• How many systems would be involved?
• How much manual effort would be required? 

If the answer involves coordination across multiple systems or reliance on spreadsheets and emails, your setup exposes you. In that case, it’s worth assessing how well your current approach supports inspection readiness.  

Schedule a Conversation 

Where FDA Compliance Software Fits

To address these issues, many organizations invest in FDA compliance software alongside broader system improvements.
The objective is not to add more tools, but to improve how data and processes are managed across the organization.
Effective FDA regulatory compliance software helps:

• Connect data across systems
• Enforce workflows and approvals
• Support compliance with FDA regulations
• Meet requirements such as 21 CFR Part 11
• Enable consistent, compliant processes

When implemented correctly, compliance becomes part of the system rather than something managed separately.

How STAEDEAN Supports This Approach

STAEDEAN Life Sciences extends Microsoft Dynamics 365 with capabilities designed specifically for regulated life sciences environments. Unlike generic ERP or standalone compliance tools, it brings data, workflows, and controls together within a single operational framework, supporting traceability, auditability, and validation requirements as part of everyday processes.
With the right setup, organizations can:

• Strengthen data integrity through system-enforced controls
• Track materials and batches across the lifecycle
• Enforce role-based approvals and workflow discipline
• Reduce validation effort with structured approaches
• Improve batch-release readiness through better visibility

This allows compliance to be managed through the system, rather than through manual oversight.

Why This Matters

Regulatory expectations around data integrity and traceability continue to increase.
Having the data available is not enough. It needs to be consistent, traceable, and accessible when required. Organizations that cannot meet these expectations face both compliance risk and operational disruption.
If your current setup depends on manually connecting data across systems, the exposure is already there, whether it has been identified or not.
The playbook, Why Life Sciences Companies Keep Getting Warning Letters: A Playbook for Building Inspection-Ready Operations, explains: 

• Where the warning letter risk originates
• How Form 483 observations escalate
• What changes reduce recurring issues
• What inspection-ready operations require

The post Why Life Sciences Companies Get FDA Warning Letters appeared first on ERP Software Blog.

There are a lot of Microsoft partner events. A lot. If your first instinct when you hear about a new one is "do we really need another conference?" you're not alone. I sat down with Liz Hallen, Co-Owner of PartnerIn and host of the Vibe 2.0 Microsoft partner conference, and asked her the questions a skeptic would actually want answered. This is what Liz had to say. 

Why would a Dynamics partner bother going to such a small event? 

Turns out, fewer people in the room often means more people actually talking to each other. 
What PartnerIn found at Vibe 1.0 is that people actually talk to each other when there aren't 3,000 of them in a convention center. They share real problems, real numbers, real war stories, and none of that happens when you're scanning a lanyard to decide if someone is worth your time.  
At a smaller Microsoft partner event, you end up meeting more people (not fewer) because you're not spending half the conference navigating a crowd. 

Isn’t Provo, Utah too far from an airport? 

Provo is not your typical conference destination; Liz admits they have heard that a lot. But the fact is that Salt Lake City is a major airline hub that most people can reach with one connection, and from there it's a 40-minute Uber ride down a four-lane interstate straight to the Marriott in Provo. Liz points out that's roughly the same ride as getting from O'Hare or DIA to downtown, so the "it's too remote" argument doesn't really hold up once you look at a map. 

There are no end users at this event, so how will I get LEADS? 

That's a fair concern if you're defining "leads" the way it's always been defined, but given how the Microsoft partner ecosystem has shifted, that definition might be overdue for a rethink. 
Vibe 2.0 is exclusively for Microsoft partners: VARs, ISVs, MSPs, and partners working across Business Applications, Azure, Modern Work, Security, and Data. No end users, that's true. But think about how many partners are now selling through partner channels.  
Meet the right Azure partner at Vibe 2.0, and their customer who's been asking about Business Central suddenly has a name to call.  
Referral leads are the best leads you'll ever get, and this is a room full of people positioned to send them your way. 

I already see the same Dynamics partners at events all year – isn’t this just going to be the same crowd in a different city? 

If your world is primarily Business Applications, you actually won't recognize most of the room, because PartnerIn has spent the past year deliberately building relationships outside the business applications space, pulling in Azure partners, security partners, and others who have never set foot at a Dynamics event.  
Liz was direct about it: "We've been very intentional about building those bridges." The whole point is to get you in a room with Microsoft partners you'd never otherwise meet, because they've been operating in a completely different corner of the ecosystem. 

Every Microsoft partner conference has the same sessions. Why would Vibe 2.0 sessions be different? 

Because PartnerIn is allergic to that format. As Liz put it: "We want people to talk with each other and not necessarily always be talked at." The sessions that landed hardest at Vibe 1.0 were open workshops, roundtables, and panel discussions where the whole room contributed, and people walked away having solved actual business problems, not because a speaker told them what to do, but because another partner in the room had already figured it out and was willing to share. 
The technical sessions go deep too: 300 and 400 level content, 90-minute workshops where people work through real problems together rather than watch a demo.  
PartnerIn even publishes submitted session titles publicly in the Vibe 2.0 Call for Speakers section. Everyone can see the topics, so there's no excuse for duplicate (or boring) content.   
Note: The Call for Speakers ends June 15th.  
As Liz said: "We're not interested in regurgitating content. We're looking for fresh new ideas that people can participate in." Shocking concept, we know. 

I am so tired of sitting in an 8am keynote watching a Microsoft product demo, isn’t there a better way? 

Liz and Molly heard that feedback after Vibe 1.0 and they are completely with you on it. They're working with their Microsoft speaker specifically to avoid the standard product presentation, and they've rethought what a keynote even looks like.  
Last year's was delivered at an evening reception with lounge couches, round tables, and an open bar, which is a significant improvement over a dark auditorium before most people have finished their first coffee. 
One keynote for Vibe 2.0 is Beth Leonard, COO of R3, talking about going from homelessness to the C-suite. It's about resilience and risk, and it's the kind of thing people are still talking about at the next conference. 

I don’t want to be sold to in the expo hall, can I avoid it? 

Good news - Vibe 2.0 skips the traditional expo hall setup entirely because, as Liz put it: "You don't remember the conversation you had at the exhibit. But you remember the person you laid next to while you were doing yoga stretches on Tuesday morning." 
That philosophy shapes how sponsorships work at Vibe. Instead of tiered booth packages with a fixed list of benefits, every sponsorship is built around what the sponsor actually wants to accomplish.  
Mekorma is sponsoring a wellness morning with yoga and a healthy breakfast.  
Blue Dragonfly is serving a signature cocktail at the opening keynote.  
USTPay is providing a charging station. 
These are experiences people will remember and connect to those brands. If a partner or ISV genuinely wants a traditional exhibit table, Vibe can make that work, but for an all-partner audience a shared experience tends to go a lot further than a branded tablecloth. 

My team is already stretched thin. Why would I send someone to yet another conference? 

Because there's a difference between sending someone to collect product updates they could have read in a release note, and investing in them as a business professional. Vibe 2.0 is designed to be the second kind of conference. 
Liz made the point directly: “the Microsoft partners that are succeeding at the best rate right now are the ones investing in their people.” Everyone is chasing certifications, co-sell opportunities, and frontier partner status, and those things matter. But the partners pulling ahead are also making sure their people know how to build better businesses, handle customers well, motivate their teams, and learn from others who have already solved the problems they're wrestling with. That's what Vibe 2.0 is built around. 
Sending someone to a peer-to-peer professional development conference isn't a distraction from the work. It is what makes the work better. 
Some attendees told Liz that Vibe 1.0 felt more like a reward, like an inner circle trip that you earn based on a job well done. Don’t you want your employees to feel rewarded? 

Okay fine. But there are so many Microsoft partner events now. Make the case. What actually makes Vibe 2.0 worth the time and money? 

Most Microsoft partner conferences are built around product content: features, roadmaps, certifications. Those events have their place. What Vibe 2.0 is going after is something different: peer-to-peer professional development where partners learn from partners, build real relationships, and go home with things they can actually use to run their businesses better.  
Liz doesn't know of another event in the Microsoft space doing exactly that right now. 
If you need a frame of reference, think about why everyone who makes it to DynamicsMinds in Europe comes back completely evangelical about it. It's not really about the sessions; it's about the experience. The boat ride, the beach, the fact that they were somewhere unexpected doing something memorable with a small group of people invested enough to travel there. Most of all, it is about the connections and the conversations. 
Molly pulled the evening keynote concept directly from DynamicsMinds, and that experience-first philosophy is what PartnerIn is going for at Vibe 2.0. (And for many of us, Provo is easier to get to than Slovenia, right?) 
There is one more unique thing: the Monday before the main event features She's a Vibe, an intentional, half-day experience focused on the topics impacting women in tech today (men also welcome!). A full morning of breakout sessions, connection, and inspiration.  

Don’t Be a Skeptic – Don’t Miss Out On Vibe 2.0  

The Vibe 2.0 conference runs September 21-23, 2026 in Provo, UT. Three full days of learning and connections, two evening receptions and plenty more yet to be announced. (Vibe 1.0 featured a baby alligator, so expectations for surprises are already set appropriately high.) 
Vibe 2.0 | Microsoft Partner Peer-to-Peer Professional Development Conference | September 21-23, 2026 | Provo, UT. Registration and more information at partnerin.io/vibe. 
By Anya Ciecierski, ERP/CRM Software Blog 
Proud to be a VIBE 2.0 Media Partner 

The post 9 Questions a Skeptical Microsoft Dynamics Partner Would Ask About Vibe 2.0  appeared first on ERP Software Blog.

There is one event in the EMEA calendar that the Dynamics 365 Business Central community considers unmissable. In 2026 it will take place in Paris, on the 27-29 October. 
Directions EMEA brings together the people who build, sell, and extend Business Central across Europe, the Middle East, and Africa. Amongst those attending are resellers, ISVs, distributors, developers, consultants, MVPs, and Microsoft representatives. This three day event will provide the most focused, commercially relevant conversations that you will have all year. 
If you work in this ecosystem, this is where you need to be. Secure your place at www.directionsforpartners.com/emea2026.  

What’s on the Agenda?

The event runs across three full days, with an optional welcome reception on the evening of 26 October if you would like to get a head start on networking with others. 
Each morning opens with a keynote, and there are three in total across the conference. On the evening of 28 October there is a community party which is definitely worth staying for. The full session schedule is still being finalized, stay tuned for further updates.  

Who Is It For? 

Business Central is central to what your business does, and this event is built for you. That includes: 

• Resellers and VAR partners looking to sharpen their competitive edge 

• ISVs who build extensions and vertical solutions on the platform 

• Developers and consultants who need to stay current with technical changes 

• Business leaders and practice managers making strategic investment decisions 

What You Will Take Away 

Three things consistently make this event worth the trip. 

You get the roadmap from the source. 

Business Central moves quickly. Release waves, licensing shifts, and new platform capabilities can all have a real impact on how you operate. The keynotes and sessions here are one of the few places you can hear that information directly, rather than filtering it through partner communications weeks later. 

Networking is just as valuable as the sessions.

Talking to peers who are navigating the same market, the same challenges, and the same opportunities gives you a perspective you simply cannot get from a webinar or a newsletter. Those conversations happen here. 

It is an efficient investment for your business.

Three days of focused and relevant content, whether technical or commercial, is hard to replicate through any other single event. For the people in your team who need to stay up to date, this is time well spent. 

What Does It Cost? 

• Super Early Bird: €1,149 
• Under-30 ticket: €750 
• Group discount: 10% for five or more attendees, 20% for ten or more

Ready to Book? 

Full details of the programme, venue, and registration can be found at www.directionsforpartners.com/emea2026 
The Super Early Bird rate is available now, so lock in your place and make October 2026 in Paris one of the most productive trips of the year. 
By Madi Abhishek, ERP/CRM Software Blog

The post Directions EMEA Paris 2026: A Must-Attend Event for Dynamics 365 Business Central Partners appeared first on ERP Software Blog.

Listen to the Podcast

Getting a warehouse management system live in Business Central has never been the hard part. Getting 30 Android scanners configured, enrolled, and locked down before a go-live deadline—that's always where projects slow down. For warehouses running Warehouse Insight or WMS Express, Insight Works has addressed that problem directly by adding SureMDM, a mobile device management (MDM) solution powered by 42Gears.
The result is a deployment experience that is meaningfully different from anything that has come before. A new scanner comes out of the box, a worker scans a single barcode, and the device is fully configured: Warehouse Insight or WMS Express is installed, Business Central settings are applied, and the device is locked to the app. No IT staff on-site. No manual setup. Done.

Why device deployment has always been a friction point

Traditional warehouse scanner deployment in Business Central follows a familiar, painful pattern. IT staff receive a shipment of devices. They configure each one individually: installing the WMS app, entering server credentials, applying network settings, testing connectivity, and locking down the interface so workers cannot stray into unrelated apps or settings. For a ten-device deployment, this is inconvenient. For a fifty-device rollout across three locations, it becomes a project in itself.
Multi-location operations face an additional layer of complexity: devices need site-specific configurations, policies may differ between warehouses, and physical access to remote sites can turn a straightforward update into a scheduled trip. Version drift across locations—where one site runs a newer build of the WMS app than another—is common and creates support headaches.
These are not edge cases. They are the standard experience for most Business Central WMS implementations. SureMDM was built to eliminate them.

One barcode. Fully deployed.

When a customer adds MDM to their Warehouse Insight or WMS Express deployment, Insight Works provides a single enrollment barcode. That barcode encodes everything: which apps to install, which Business Central environment to connect to, and which policies to enforce. A worker scans it on a new device, and within minutes, the scanner is operational and locked to the WMS application.
For multi-location operations, this changes the logistics of fleet expansion entirely. New devices can be shipped directly to any warehouse location and handed off to a local worker on day one, without requiring an IT technician to be present. Site-specific policies and configurations can be baked into the enrollment process, so a scanner destined for a remote facility receives the exact right setup without extra steps.

Ongoing fleet management from a single console

Fast initial deployment matters, but the ongoing management of a scanner fleet is where MDM delivers sustained value. Key capabilities include:

• Kiosk lockdown: Devices run only Warehouse Insight, WMS Express, and other approved apps. Workers cannot access browsers, unrelated apps, or device settings.
• Remote lock and wipe: Lost or decommissioned devices can be remotely locked, located, or wiped from the console, keeping Business Central data protected.
• Over-the-air updates: Warehouse Insight updates and Android OS patches can be pushed to the entire fleet simultaneously. No manual installs, no version drift across locations.
• Multi-location management: Different policies, app configurations, and user assignments can be applied per site from a single console, without juggling multiple systems.
• Real-time monitoring: Device status, battery levels, app versions, and last-known locations are visible at a glance, so IT teams can identify and resolve issues before they affect warehouse operations.

Compatible hardware and enrollment requirements

SureMDM supports Android-based barcode scanners and mobile computers from Honeywell, Zebra, Datalogic, and other major manufacturers—the same devices used with Warehouse Insight and WMS Express today.
Full management capabilities require devices to be enrolled from a clean state: either new out of the box, or an existing device that has been factory reset. This is an Android platform requirement, not a limitation of SureMDM. For businesses purchasing new hardware or refreshing an aging fleet, the enrollment process is seamless and automatic. Customers unsure about their current device compatibility can contact Insight Works directly for guidance.

Who benefits most

MDM delivers the most visible impact for operations in several situations:

• Businesses going live with Warehouse Insight or WMS Express for the first time and deploying a fleet of new devices
• Multi-site operations where centralized IT needs to manage scanners across locations without traveling to each one
• Growing distribution and 3PL operations that regularly add devices as order volumes or headcount increase
• Any organization where keeping scanner software current across the fleet has historically been a manual, time-consuming process

Availability

SureMDM is available now as an add-on for Warehouse Insight and WMS Express. If you are purchasing new hardware for a Business Central WMS deployment, pairing it with SureMDM is the fastest and most reliable path to a fully operational scanner fleet.
For more information, visit https://dmsiworks.com/features/simplified-device-deployment-for-business-central-wms or contact your Insight Works reseller.

The post Faster WMS Deployment in Business Central: How MDM Changes the Game appeared first on ERP Software Blog.

There is an overlooked disconnect in business technology right now. The conversation is dominated by artificial intelligence and what it might do next, while a surprising number of companies are still running core financial processes on paper. This post looks at that gap, why accounts payable is where it shows up most clearly, what it costs to stay stuck, and how businesses still running on systems like Microsoft Dynamics GP can move forward without tearing everything down. 

The Paper Trail Nobody Talks About

For those of us inside the bubble of the business management software space, Agentic AI is the topic du jour. And while it’s true that many leaders and early adopters in corporate finance and accounting are deeply invested in the AI revolution, there is often a different story on the ground level.
You can still walk into the finance department of an average mid-sized company and find someone hunched over a stack of paper invoices, manually keying numbers into a screen, one line at a time.
It isn’t that businesses with outdated or legacy technology have missed the boat on AI-powered finances or that they have no interest. They might wish for better systems, but there is a gap between what they want and what is possible to add to their current tech stack. Think of electric vehicles… Maybe someone wants a shiny new EV with all the cool tech, but if they live in a region where there just isn’t the infrastructure to keep it charged, connected and running, it just isn’t practical. So they drive a classic muscle car in the meantime.
For many accounts payable departments, the gap lies between ERP solutions that don’t support the latest agentic tools and vendors who still send paper invoices and want to be paid by paper check.
You might be interested in: Paperless Accounts Payable System - Need-to-Knows to go Paperless AP

The Cost of Being Outdated

If you spend your days at the bleeding edge of the accounting software industry, it’s easy to forget that many people still spend their days in a world of manual processes. Paper invoices arrive in the mail or as PDFs that get printed out anyway. Someone sorts them. Someone routes them around the office for approval, often by literally walking them to a desk or sticking them in a folder. Then, after all that, someone cuts a paper check, stuffs it in an envelope, and mails it.
It could almost be seen as quaint if it wasn’t costing the company so much.
Every paper invoice that gets handled by hand introduces a chance for error. A transposed number. A missed due date. Studies on AP processing have long pointed to manual workflows being slower and more expensive per invoice than automated ones, sometimes by a factor of five or more. The labor adds up. The late fees add up. The strained vendor relationships add up.
Paper checks are their own special problem. They are slow. They get lost. And they remain one of the most common targets for fraud in business finance. Check fraud has actually been climbing in recent years, not falling, even as so much attention goes to flashier digital threats.

So why are companies stuck here?

Part of it is inertia. The old system works, sort of, and ripping it out feels risky. The person who has processed invoices the same way for fifteen years knows where every body is buried, and replacing that knowledge with a new tool feels like a gamble.
Part of it is the belief that modernization means a massive, disruptive, expensive overhaul. And part of it is simply that the loud conversation about cutting-edge AI makes the boring, unglamorous work of fixing accounts payable seem like a problem from a previous era, not something worth a leadership meeting.
The good news is that fixing this does not require the futuristic tech in the headlines. The wins in accounts payable are not exotic. They are practical. Capturing invoice data digitally so it never gets rekeyed by hand. Routing approvals electronically so nothing sits in a physical inbox. Paying vendors through electronic methods. Secure, automated check fulfillment. None of this is science fiction. Most of it has been available and proven for years.
This unglamorous foundation is exactly what makes the fancy stuff possible later. Clean, digital, structured financial data is the raw material that any genuinely useful AI tool needs to function. A company that automates its AP is not just saving money and reducing fraud risk today. It is quietly preparing the ground for everything it might want to do tomorrow.

The Microsoft Dynamics GP Situation

Microsoft Dynamics GP has been a workhorse ERP for thousands of mid-sized businesses for decades, and plenty of finance teams still rely on it every day. But GP was not built for the agentic, AI-driven world that dominates the headlines now, and Microsoft has signaled that its long-term roadmap points elsewhere.
This has left a lot of companies feeling stranded, running a stable system that simply was not designed to plug into modern AP tools, and switching to Business Central or another platform doesn’t rank high on the executive buying committee’s priorities, especially when they are heavily investing in front-office and point-of-sale tech. 
Fidesic can help... Rather than forcing a painful, rip-and-replace migration, Fidesic layers AI-based accounts payable directly onto Dynamics GP, bringing intelligent invoice capture, electronic approval routing, and secure automated payments to the ERP companies already know and trust. It is a simple path forward, one that lets a GP shop modernize accounts payable and start building that clean, digital foundation without abandoning the platform their entire finance operation runs on.
What’s more, Fidesic is here for GP users today, and poised to move with you if and when you do migrate to a new ERP.

Takeaway

The lesson here is not to ignore the future. It is to be honest about the present. Before chasing the next shiny thing, it is worth asking a simpler question. Is anyone in the building still chasing signatures on paper invoices?
If the answer is yes, that is where the real opportunity sits. Not in some distant frontier, but in the stack of paper on the desk down the hall.

Conclusion

The disconnect between the AI conversation and some companies’ paper-bound reality is not a reason for despair. It is a roadmap. The companies that win will not be the ones chasing every flashy new AI tool, but the ones honest enough to fix the unglamorous problems first. For accounts payable, that means trading paper invoices and mailed checks for clean digital workflows, and for GP users, it means a practical path forward that does not require abandoning the platform they rely on. The future starts with the stack of paper on the desk down the hall.

The post The Paper/Manual to AI Disconnect appeared first on ERP Software Blog.

Why Is This So Complicated?

If you’ve ever felt frustrated working in a structured ERP system, you’re not alone. That frustration is common, in fact, there’s actually a good reason it feels this way.
Take a moment and try to remember what it was like learning how to drive. Most of us started in a parking lot. You could stop whenever you wanted, turn around easily, and mistakes didn’t carry many consequences. It felt flexible because it was.
Now think about driving on the highway for the first time. Suddenly there were lanes, barriers, rules, and very little room for improvisation. It was uncomfortable, but you understood those controls existed so you could go farther, faster, and safer at scale. And I bet that teacher of yours made a huge difference.
Many teams start their businesses in tools that behave like that parking lot. Whether it’s spreadsheets or lightweight accounting software, you can do almost anything you want. You can edit history, force balances, and bypass subledgers. These are “parking lot moves”, and they don’t work on the highway. That flexibility feels productive until volume and number of stakeholders increases and confidence in the data starts to erode.
Systems like Business Central are built for the highway. Auditability, permission sets, process controls, and segregation of duties can feel overly complex until you understand they’re the infrastructure that keeps high-volume systems reliable. When corrections are layered instead of overwritten and transactions flow through defined processes, the result is data you can trust.
Workarounds may feel faster in the moment, but over time they undermine confidence. When users can bypass controls, no one is quite sure which numbers are real anymore, including auditors, leadership, and (you’d be surprised) even the people doing the work.
At Ternpoint, our role isn’t just to implement software. We help teams adjust to the processes and flows that inherently exist in a structured system like Business Central. We bring end users into the conversation early, explain the why behind the controls, and design solutions that promote adoption instead of resistance. That's how we get you from driving in the parking lot to the highway.
Yes, the highway feels restrictive at first. But once you understand how it works, and have the right guide in the passenger seat, the benefits far outweigh the initial discomfort.

The post Why Business Central Feels Hard (and Why That is actually a Good Thing) appeared first on ERP Software Blog.

Maintenance delays and unexpected equipment failures increase operational costs and reduce productivity. This insight is relevant for maintenance managers and operations teams seeking to improve asset reliability through better planning within Business Central.

Equipment maintenance challenges disrupt operations and elevate costs when tasks rely on manual processes or disconnected systems. Improving maintenance workflows within Business Central helps organizations prevent downtime, extend asset life, and coordinate parts and task tracking efficiently. Viewers gain clarity on integrating preventive maintenance, mobile technician access, and data-driven planning to reduce risk and improve operational continuity.

• Managing maintenance workflows inside Business Central
• Automating preventive maintenance scheduling
• Tracking assets, parts, and maintenance tasks
• Mobile technician access to work orders and documents
• Using data to enhance maintenance planning and reduce risk

About Insight Works

We've been around for just over 10 years now. We work primarily through resellers, so if you have questions about this solution or any of the others I'll briefly talk about today, go through your partner. If they don't have the answers for you, you can contact us on the website and we'll help you out.
We work mostly in manufacturing and distribution. We also have retail — a counter-sale solution — which means that any time you're physically having to touch inventory, we're likely going to have a solution that helps you with that process, whether that's warehouse management, shipping, counter sales, production, or any of those other things.

Our Application Ecosystem

We have well over 60 applications and add-ons available within Business Central, and a number of those are free — both as add-ons and as apps you can get from AppSource at no cost. I'll mention a few of these quickly because they do play with Maintenance Manager. Maintenance Manager is part of a larger solution stack, and some of these fit in there.
The Enhanced Planning Worksheet is one worth highlighting. If you're using the planning worksheet or requisition worksheet in Business Central today, use this instead — it's free and it's better, especially on the warehouse side, where it offers better planning logic for warehouse procurement and related activities. We also have a Sales Forecasting app, and that's also a free app.
Some of the more commonly used apps include Graphical Scheduler, which is basically drag-and-drop scheduling. You can use that with maintenance, and Maintenance Manager uses it to display a maintenance calendar in an Outlook-style view. You can also use Graphical Scheduler for production information, maintenance, custom data — whatever you want to put on there.
Doc Extender provides drag-and-drop document management. If you want to attach maintenance guides and things like that to your assets, you can drag and drop using Doc Extender. You can use the built-in Business Central attachment capability, but Doc Extender is a bit nicer because it's easier to use and it will also store all that information in SharePoint in a clean, accessible way.
Order Ship Express and WMS Express cover shipping and warehouse management. Even if you don't have large warehouse management requirements, something like WMS Express can be handy for spare parts on the maintenance side. If I'm picking parts to a maintenance order, I can use WMS Express to do that picking or run an inventory count of my parts inventory on a handheld scanner-style device.
Safety Logbook may also be useful on the maintenance side. It can track HSE events and log certifications and other related information.

Where Maintenance Manager Fits

Maintenance Manager is really positioned around production asset maintenance. The focus is on work centers, machine centers, and the assets you use within production — that's what it was built for. You can use it to track anything you like, including office equipment, but it's really tailored to work with those production assets.
Within the broader manufacturing workflow, we plan everything in for production using the enhanced planning pack, send it out to be scheduled using automated production scheduling and the Graphical Scheduler, and then execute using Shop Floor Insight to capture labor time, component usage, and related data. That integrates with Quality Inspector for quality information capture. Microsoft has also released their own Quality Management module, which is actually a subset of Quality Inspector — they licensed Quality Inspector and turned a subset of it into Quality Management. You can use either one to manage things like equipment inspections or lockout procedures.
Once manufacturing is complete, output is fulfilled through WMS Express or Warehouse Insight for scanning, shipping, and everything else. But the key piece missing from that picture is maintenance activities. If I'm scheduling production and my equipment goes down because it broke, or preventative maintenance is scheduled right when a rush order is running through, that creates conflicts on the shop floor. The ability to include maintenance activities within the production scheduling and execution environment is exactly where Maintenance Manager comes in.

About Maintenance Manager

Maintenance Manager is a lightweight tool. We're not an enterprise asset management solution — we're a basic CMMS that helps you schedule maintenance activities alongside your production activities. That's really the goal. But you can also track laptops, phones, vehicles, or any other assets within Maintenance Manager if you want to.
From a preventative maintenance perspective, it allows you to create schedules for PM tasks and automatically schedule them into the future so you get an idea of what spare parts you're going to need. With production assets like work centers and machine centers, it blocks off capacity when a PM has been scheduled. You can also create maintenance requests for break-fix situations — either in Business Central, in Teams, or through a Power Automate interface.
Because Maintenance Manager is built within the production module in Business Central, it works with any existing Business Central extension or capability. We've leveraged the production module for maintenance orders, which means if you already have tools for capturing time or managing parts in Business Central, they'll just work with Maintenance Manager. It's not a separate system — it slides right in, leverages what you already have, and works directly within BC. It does require a Premium license because it uses the production module.
One of the key advantages is how quickly you can get up and running. A lot of CMMS and EAM solutions are expensive to set up — not just because of software cost, but because of implementation time. If you're on a paper-based maintenance solution, nobody wants to manually migrate all those work instructions into BC. Maintenance Manager makes it easy because we're leveraging everything that's already in BC. All you really need to do is attach your work instructions by dragging and dropping them in, and you can be up and running in very little time.

System Walkthrough

Let's go into Business Central and walk through the structure of it — how it's set up and how you would use it.

Master Data: Equipment Assets and Equipment Items

On the master data side, we have three different concepts. The first is maintenance equipment assets. These are essentially your fixed assets — you come in here and identify all the fixed assets you're using within the maintenance module. Accounting might have a hundred fixed assets in the system, but you're only maintaining three of them, so that's all you see in your list. They might also have laptops and other items that I'm not responsible for. I don't care about those.
Conversely, you might have 50 things you maintain that aren't fixed assets. You don't want accounting to have to create a fixed asset record just so you can calibrate a torque wrench.
That's where maintenance equipment items come in. These are the records that define what you actually maintain. An equipment item can be tied to a machine center and also linked to a specific fixed asset if both exist in BC. Or it can have no association with a work center or fixed asset at all — for example, a Toyota forklift that just needs to be tracked as something you maintain. You don't need a fixed asset or work center assigned to it.
The assignment quantity field shows how many maintenance tasks are assigned to a specific piece of equipment — whether that's an outstanding break-fix or a scheduled PM task.
There are also two ways to set up equipment items from an inventory perspective. You can track a piece of equipment without any inventory association, or you can associate it with inventory. When you do that, you can use all of Business Central's warehouse management capabilities to manage that equipment item — transfer it to a subcontract vendor, move it to a different warehouse or facility, use transfer orders, scan guns, anything you can do with standard BC inventory. You can use that same functionality for your maintenance equipment without any additional add-ins or customization.

Master Data: Maintenance Parts

Maintenance parts are simply items in BC — they work like any other item. That means you can set up all your replenishment rules: spare parts inventory, consumables like oil, min and max quantities, costing, all of it. It's standard Business Central, so your purchasing team already knows how to manage it. As you plan maintenance into the future, the planning system in BC will automatically generate purchase orders for those parts through the planning worksheet, requisition worksheet, or the Enhanced Planning Worksheet.
From a categorization standpoint, the item usage type will be set as a maintenance part, which lets you segregate spare parts from your standard inventory for purchasing, receiving, and reporting purposes — while still following all the same rules you have set up for your other items in BC.
You can also define custom attributes for equipment items and view them hierarchically using the analysis view in BC — for example, by area of the facility, by subcontract vendor responsible for the equipment, or by how many tasks are currently assigned to each piece of equipment.

Defining Maintenance Tasks

Once you've set up your equipment and parts, you define the tasks — the activities you need to perform on that equipment. There are a few different maintenance types. Corrective maintenance covers break-fix situations. You can create a work request on the fly from within BC, from a handheld device, or through a Power Automate interface. If you want to expose it in Teams so people without a BC license can submit requests, or if you just want a simple webpage, that's all possible through Power Automate.
The other major type is preventative maintenance. Let's look at a weekly laser cutter maintenance task as an example. The interval type here is duration, meaning it recurs on a time-based schedule. You can also use runtime, output count, or distance as interval types. For equipment tied to a work center or machine center, runtime and output count are automatically updated as production activities are posted — so you always know in real time where you are relative to the next scheduled maintenance. For example, if you want to do maintenance every 10,000 pieces produced on a die or mold, the system tracks that piece count automatically through the standard manufacturing module.
You can also set an effective range on a task. If a machine requires one type of maintenance for the first 100 hours and a different type after that, you can set up two separate tasks with non-overlapping effective ranges.
A task can be assigned to multiple pieces of equipment simultaneously. If you have 10 lathes that all require the same weekly maintenance, you create one task and assign it to all 10. Each task also has a production BOM and a routing associated with it. The BOM lists the spare parts you need, and the routing defines the labor required. For production assets, there's a maintenance placeholder in the routing setup that gets replaced with the actual work center or machine center when the maintenance order is created — so the system blocks off capacity on the right machine automatically.
Parts on the BOM can be set to back flush, so the maintenance technician doesn't have to manually record consumption — they just mark the task complete and the material is consumed automatically. If additional parts are needed during the work, they can be added manually to the maintenance order on the fly.

Creating and Managing Maintenance Orders

Once tasks are set up and assigned, you generate work orders. The assignment quantity field gives you a quick view of what's due — anything showing a non-zero value has maintenance due. You can then come in and select Plan Maintenance Where Due, and the system will create a recommendation to generate work orders for everything outstanding.
You can also use Auto Schedule Tasks to plan ahead. Set a date range, and the system will generate a full schedule for all duration-based tasks within that window. You'll see weekly vehicle inspections, laser cutter maintenance, compressor maintenance — everything laid out by equipment. This schedule drives spare parts planning: if you agree with the schedule, the purchasing system in BC will automatically flag the parts you'll need and prompt purchase orders to be created through the standard planning process.
Maintenance orders are effectively production orders in BC. They're classified separately so maintenance personnel only see maintenance orders in their views, while standard production order lists won't show maintenance orders unless explicitly requested. As a maintenance administrator, you see all released maintenance orders in your list.
There's also a maintenance calendar — an Outlook-style calendar view where you can see upcoming maintenance, create new maintenance orders, and drag and drop activities to different time slots.
When you open a maintenance order, you have the standard components and routing, plus a maintenance-specific section where you can record details like the current mileage or interval reading, and flag the order as finished. When you change the status to finished in the standard BC way, it applies to the maintenance equipment record as well — updating the interval history and everything else.
You can also attach quality inspection steps to a maintenance order using either Quality Inspector or Microsoft's Quality Management. If you need to perform a lockout inspection before working on electrical equipment, or a startup checklist after the work is done, you can manage that directly from the maintenance order.

Scheduling Maintenance Alongside Production

On the planning and scheduling side, if you're using our MX APS tool, it will take your maintenance activities and schedule them in alongside production automatically. What often happens without this is the maintenance team says a machine needs to come down Tuesday at 8 AM, and the production team has an order starting at the same time. MX APS resolves that conflict by finding the least disruptive window for the maintenance activity. You can even define a window — say, this maintenance needs to occur within a three-day range around a target date — and MX APS will find the best available slot.
In the Graphical Scheduler, you can see all your production orders alongside maintenance orders — differentiated visually, for example by color. You can zoom in, drag and drop orders to different time slots, and click into any maintenance order to see the full details right from the schedule view.

Execution and Time Capture

For execution, you can use the standard BC interface or use Shop Floor Insight or Warehouse Insight. There's both a kiosk interface and a personal device interface, so you can send a maintenance technician out with a tablet or phone. They see their unassigned and assigned maintenance tasks, tap or scan a barcode to pull up the work instructions, view attached manuals and equipment photos, and clock on to start capturing who did the work and when. Everything is tracked in real time in Business Central.
If you don't use Shop Floor Insight, you can do all of the same things directly in the maintenance work order in Business Central via the mobile app. And if you already have your own solution for capturing time in production, that same solution will work for maintenance as well — because maintenance orders are just production orders in BC.
Once work is complete, you change the status to finished, all costs are posted, and if the equipment is tied to a fixed asset, those maintenance costs are tracked against it. The full history of all maintenance activities — everything consumed, every time work was done, all costs — is stored in BC using standard capabilities. Any dashboards or Power BI reporting you already have set up will work with Maintenance Manager data automatically.

Licensing and Pricing

Maintenance Manager is available from AppSource for cloud environments. For on-premises, you get it through your partner. It requires a Premium Business Central license because it leverages the production module.
There are two licensing options. The first is the Maintenance Manager User Plan, purchased directly through Microsoft on AppSource. This is a per-named-user plan at $50 per month. That user gets access to Maintenance Manager across all companies. Importantly, only the administrators of the system need this license — the people creating equipment items, maintenance parts, and tasks. Technicians recording time and materials against work orders only need their standard Business Central license. So if you have 10 techs and one supervisor, you likely only need one Maintenance Manager license.
The second option is the Pre-Purchased Maintenance Manager User Plan. This appears on AppSource at zero dollars, so Microsoft will not charge anything to your credit card — though you still need to provide one. You still get a 30-day trial, and after that trial we can extend it if needed. The purchase goes through your partner rather than through Microsoft.
If you purchase the per-user plan through AppSource, you get one month free. There's a checkbox to disable recurring billing — if you uncheck it, you won't be charged after that month, though your trial will stop working at that point.
If you have questions, visit the website at dmsiworks.com — there's a chat box there. You can also go to AppSource, click Buy Now, and start a free trial. Just turn off recurring billing and you won't be charged anything. Try it out, see if it works for you, and go from there.

FAQs

Q: How do you submit a maintenance request — is there a submission link or form?

A: There are a couple of ways. You can do it directly in Business Central. It can also be exposed in Teams using Power Automate — that's typically the approach when you want to allow submissions without requiring a Business Central license. If you're using Shop Floor Insight or Warehouse Insight, you can submit through those as well. If you want a simple webpage for submissions, that's also doable through a Power Automate interface. There are also some third-party partners who have automated equipment monitoring that can automatically kick off work requests when something goes wrong with a piece of equipment, and we have integration with some of those partners.

Q: Can maintenance tasks be grouped together into a single order?

A: Not automatically through the planning process — by default, each task generates its own work order. If two tasks happen to fall due at the same time on the same piece of equipment, you'd get two separate work orders. You can manually combine them by either adding the additional steps directly onto an existing work order, or creating a new work order from scratch and adding whatever tasks and instructions you need. But when you're doing automated planning, it's one task per work order. One task can generate multiple work orders for different pieces of equipment or different intervals.

Q: What's the difference between maintenance equipment assets and maintenance equipment items?

A: Assets are the fixed assets — that's what accounting manages. The maintenance team typically has read-only access to fixed asset cards and isn't creating or editing them. Equipment items are the maintenance team's records. An equipment item defines what you're actually maintaining, and optionally whether that equipment is tracked as an inventory item so you can move it around using BC's inventory management capabilities. You don't have to associate an equipment item with a fixed asset. Typical examples without fixed assets would be things like torque wrenches or calibration equipment — a $50 torque wrench isn't going to have a fixed asset record, but you still might want to schedule maintenance on it.

Q: Do you need fixed assets set up to maintain equipment?

A: No. You can create an equipment item with no fixed asset and no work center or machine center associated with it. In that case, scheduling maintenance on it will have no impact on your production schedule — it just exists as a standalone record you're tracking maintenance against. You can still assign weekly, monthly, and break-fix tasks to it without any connection to the rest of the production environment.

Q: Can you do recurring non-inventory consumables?

A: You can handle consumables through the bill of materials on a task — set them up to back flush so they're consumed automatically every time maintenance is completed. If you want to order a fixed quantity of something on a recurring schedule without tying it to a specific work order, that would require a bit of creativity, since Business Central doesn't have a native mechanism for reducing inventory without a work order driving it. It's possible, but you'd need to work through the approach.

Q: Does it work with locations that have warehouse pick and warehouse receive set up?

A: Absolutely. Maintenance parts categorized as such will follow all the same rules you have set up for your other inventory in BC — picks, receives, all of it. The item usage type flags them as maintenance parts for segregation purposes, but they behave like normal inventory in every other way.

Q: Does the licensing apply across all companies?

A: It depends on which plan you're on. The per-user plan at $50 per month gives that named user access across all companies. The pre-purchased plan at $200 per month is unlimited users but per company, so if you have multiple companies, you'd need a separate plan for each.

Q: Can you integrate with PLCs to automatically report back cycle times and counts?

A: It can be done, but it's typically not a direct PLC-to-BC connection. The most common approach is to use OPC as the standard for device communication, feed that into an SQL database, and then have Business Central read from that database. If you already have an MES on the floor, it likely already has that capability in place, and then it becomes an integration between BC and the MES. We have some partners who have that kind of capability already built out.

Q: To clarify — is a maintenance task the same as a maintenance order?

A: Not quite. A maintenance task generates maintenance orders. The task describes the work to be done and what's needed to do it. You assign that task to one or more pieces of equipment, and it's the combination of the task, the equipment it's assigned to, and the timing interval that generates work orders. For example, if you have a task for an oil change every 2,000 hours, and you assign it to five forklifts, that one task will generate five work orders when maintenance comes due — one for each forklift. The task is the template; the work orders are the execution records.

The post Manage Equipment Maintenance in Business Central: Plan Smarter, Prevent Downtime appeared first on ERP Software Blog.

The post 10 Types of Warehouse Management Systems appeared first on ERP Software Blog.

Small and mid-sized businesses face a familiar tension: their teams move fast, but the back-office processes meant to support that speed do not. Sales reps close deals on the road. Project managers juggle multiple sites. Consultants rack up receipts across client engagements. Yet when it comes to getting those expenses into the books, most organizations are still relying on a process built for a different decade.
Traditional expense reporting was designed around the desktop — collect paper receipts, photograph them later, upload files into a portal, key in amounts and categories by hand, and wait on approvals that can drag across days or weeks. Legacy ERP systems were not built to meet employees where they actually work. The gap between when an expense happens and when it gets recorded has always been a problem. For growing businesses, that gap is now a liability.
That changes with the Expense Agent in Dynamics 365 Business Central, part of Microsoft's 2026 Wave 1 release. This AI-powered agent brings expense capture directly to the mobile device employees already carry — eliminating manual data entry, reducing reporting delays, and feeding clean, governed data into the general ledger from the moment of spend.
In this post, we will walk through the core challenges of mobile expense management, how the Business Central Expense Agent addresses each one, a real-world example of the impact, and how KTL Solutions helps organizations implement it the right way.

What Makes Expense Management So Painful for Field Teams?

Before looking at the solution, it helps to understand exactly where the friction lives. Most organizations share three compounding problems.

1. Receipt Loss and Manual Entry Errors

Receipts get lost. They fade in wallets, pile up in glove compartments, and disappear before an expense report is ever opened. Employees on the road rarely have time to log expenses the moment they occur, so details get fuzzy and finance staff spend hours chasing documentation. Manual data entry compounds the problem — every keyed-in amount is a chance for a typo, a miscategorized expense, or a duplicated submission.

2. Delayed Reporting Distorts Financial Visibility

When expense reports trickle in at month-end rather than flowing in continuously, finance leaders are working from incomplete data. Cash flow forecasting becomes guesswork. Budget owners cannot see actual spend until it is too late to course-correct. For businesses running on tight margins — consulting firms, field service companies, construction outfits — that lag is not just an inconvenience. It is a strategic blind spot.

3. Disconnected Tools Create Compliance Risk

When expense data lives in spreadsheets, email chains, or siloed apps that never connect to the general ledger, compliance becomes a recurring headache. Auditors cannot trace expenses back to projects or cost centers. Policy violations go undetected. Business Central users who rely on workarounds outside the platform are quietly building a reconciliation problem every single month.

How Does the Dynamics 365 Business Central Expense Agent Work on Mobile?

The Expense Agent in Dynamics 365 Business Central, combined with the Business Central mobile app, offers a direct answer to each of these problems. Here is how it works in practice.

1. Capture Expenses at the Moment of Spend

The Expense Agent plugs directly into the native share functionality already built into every iOS and Android device. An employee pays for a client lunch, opens their camera app, snaps the receipt, and shares that photo with the Expense Agent — the same way they would send an image to a colleague. The agent reads the relevant data and creates an expense entry automatically, without the employee touching a keyboard.
This is not a third-party app bolted onto the side of an ERP system. It is a native, integrated experience inside the same Business Central environment where the rest of the business runs.

• Photograph a receipt and share it — the agent extracts vendor, amount, date, and currency automatically
• Select an existing PDF invoice from email or cloud storage and share it directly into the expense workflow
• Review and complete expense details on-screen before submission, no desktop required

The closer expense capture sits to the moment of spend, the more accurate the data — and that accuracy compounds into cleaner financials and faster month-end closes.

2. A Full Expense Workflow That Lives on the Phone

Many mobile expense tools offer a stripped-down experience that pushes employees back to a desktop to finish what they started. The Business Central Expense Agent is different. The mobile interface is fully aligned with the web application, meaning employees can manage individual line items, build complete expense reports, and submit them for approval entirely from their phone.
The bottleneck in most expense processes is not the approval. It is the submission. When employees can complete the entire workflow from the field, reports come in continuously rather than in batches at month-end.

• Review and modify AI-extracted expense details before finalizing
• Group individual expenses into full expense reports on mobile
• Submit complete reports for manager approval without switching devices

The downstream effect is a finance team that sees current data — not last month's data.

3. Native Integration Closes the Compliance Gap

Because the Expense Agent is native to Dynamics 365 Business Central, every mobile submission flows directly into the same general ledger, project accounting, and approval workflows that govern all other financial transactions. There is no import step, no manual reconciliation, and no separate system to maintain. Expense policies configured in Business Central apply equally to mobile submissions.

• Expenses post to the correct cost center, project, or dimension automatically
• Approval routing follows the same hierarchy used across all Business Central workflows
• Audit trails run from receipt photo to posted journal entry, with no gaps

Organizations that need to demonstrate policy compliance — for external auditors, project billing clients, or internal governance — get a defensible, documented record rather than a patchwork of emails and attachments.

Real-World Example: How a Regional Consulting Firm Cut Its Expense Cycle from 18 Days to 3

Consider a mid-sized IT consulting firm with 80 employees, roughly 50 of whom travel regularly for client engagements. Before the Expense Agent, every consultant maintained a folder of receipt photos on their phone, filled out a spreadsheet at week's end, and emailed it to their manager for approval. Finance spent the first week of every month reconciling submissions, chasing missing documentation, and manually posting entries into Business Central. The average time from expense incurred to posted entry was 18 days.
After deploying the Business Central Expense Agent with the mobile app, consultants photograph receipts at the point of purchase and share them directly from their phone. The agent reads the data, creates the entry, and the consultant confirms the details in under 60 seconds. Managers receive approval requests the same day. Finance sees live expense data rather than batched submissions.
The results were meaningful and measurable. The expense-to-posted cycle dropped from 18 days to under 3. The finance team reclaimed roughly 15 hours per month previously spent on manual entry and reconciliation. Project billing became more accurate because expenses were recorded against the correct engagement in real time. The CFO gained a spend dashboard that reflected actual costs continuously — not retroactively.
That kind of shift does not require a large IT project. It requires the right platform and a partner who knows how to configure it properly from day one.

How KTL Solutions Implements Business Central Expense Management

At KTL Solutions, we help growing businesses adopt Dynamics 365 Business Central and its intelligent features through a practical, phased approach that delivers measurable value at each stage rather than asking organizations to change everything at once.

Phase 1: ERP Stabilization

Before layering in new capabilities, we make sure the Business Central foundation is solid. That means reviewing chart of accounts structure, confirming that dimensions and cost centers are configured correctly, and verifying that user roles and approval hierarchies match how the business actually operates. Expense management built on a shaky foundation produces bad data faster — not better data.

Phase 2: Expense Policy Configuration and Data Governance

We work with finance leadership to document expense policies — per-diem limits, allowable categories, project billing rules — and configure those policies directly inside Business Central. When the Expense Agent creates entries from mobile submissions, those entries inherit the governance structure from day one. No exceptions, no workarounds, no policy drift.

Phase 3: Mobile Deployment and User Enablement

We manage the rollout of the Business Central mobile app and the Expense Agent across employee devices, with role-specific training built around actual job functions. A traveling sales rep needs a different onboarding than a finance analyst. We build the enablement program to match, so adoption happens quickly and sticks across the organization.

Phase 4: AI Enablement and Continuous Improvement

Once the Expense Agent is running, we help organizations use the data it generates to sharpen decisions. Spend analytics, budget variance reporting, and project profitability dashboards all become more reliable when expense data flows in continuously and accurately. We also help clients evaluate adjacent AI capabilities in Business Central that build on a well-run expense process.

Conclusion

Growing businesses cannot afford to run expense processes the way they did a decade ago. The gap between when money leaves the organization and when it appears in the books is a gap in visibility, compliance, and control — and it grows wider as teams scale and spend more time in the field.
The Expense Agent in Dynamics 365 Business Central closes that gap by meeting employees where they already are: on their phones, in the moment. It is not a bolt-on tool or a separate system to maintain. It is a native capability inside the same platform that runs the rest of the business, which means every captured receipt becomes a clean, governed, traceable financial record from the second it is submitted.
KTL Solutions has the experience to help your organization implement this correctly — with the right configuration, a structured rollout, and the training your team needs to use it consistently. The technology is ready. The question is whether your expense process is ready to keep up with your business. Because growth requires systems that can adapt — not break.
Contact us: https://www.ktlsolutions.com
Ready to migrate to Dynamics 365 Business Central? Get a migration quote.

The post How Growing Businesses Can Eliminate Expense Report Delays with Dynamics 365 Business Central appeared first on ERP Software Blog.

Microsoft Dynamics 365 Business Central Partners have started adopting AI, but struggle to monetize it.
That was one of the themes coming out of Directions North America 2026, according to Amy Homan, president of Directions North America and president of All Your Ducks, Inc.
Homan told PartnerTalks the Business Central channel has evolved from how to follow Microsoft’s AI roadmap to comparing use cases.
“I saw this shift between last year’s show and this year’s show,” Homan said. “The sidebar conversations last year were, ‘Well, Microsoft’s telling us about AI, and we’re kind of looking at AI, and do I have to do it yet?’”
Now, the conversation has evolved.
“This year, the partner sidebar conversation was really about, ‘What are you doing? How is that working?’”
Partners have built their businesses around implementation, customization, support, managed services and industry expertise. AI may help them deliver work faster, create new services or package more repeatable IP. Still, it also raises a commercial problem: customers may not value AI work by the hour if the result is faster delivery, better automation or improved business outcomes.
“I think that’s the biggest challenge we’re facing today is how do we start doing projects for customers that generate revenue for us and how do we change our pricing models to be outcome or value-based?”

Owners are now part of the AI discussion

The AI discussion is no longer limited to developers and consultants, Homan said. Sales, marketing and ownership teams are also using AI inside their own firms.
“I would say not just are the developers and the consultants out there doing it, but I see the sales and marketing team certainly adopting AI and even the owners,” she said.
That makes the owner track more important. Technical enablement can show Partners how to build AI-driven solutions. Owners still need to decide how those services are packaged, sold and supported.
Directions NA drew just over 1,400 attendees this year, Homan said. It also included a stronger focus on Microsoft Dynamics GP Partners, who are facing a defined timeline for product support and security updates. That transition creates another layer of urgency as customers consider Business Central, cloud migration and AI readiness together.
Homan said Directions also brought in students from the University of Central Florida, giving Partner owners a chance to meet potential new entrants to the ecosystem.
But the central issue from the conference was Business Central AI pricing. Partners are successfully adopting AI. The next year will test whether they can turn that adoption into revenue models customers understand.
Directions North America 2027 is scheduled for April 18 to 20 at the Hyatt Regency New Orleans.

The post Business Central AI pricing is the next Partner challenge appeared first on ERP Software Blog.

Most contract management articles tell you what products exist. This one tells you what decision to make.
Organizations lose an average of 9% of annual revenue to poor contract management. For a $500M business, that is $45 million — not from a single failure, but from missed renewals, unenforceable pricing, and obligations nobody is tracking. If you run Dynamics 365, you already have the infrastructure most CLM vendors are trying to sell you integration with. The question is which gaps are actually costing you money, and what is the right-sized fix.

Start Here, Not With a Vendor Demo

Before evaluating any tool, answer four questions with your legal, finance, and procurement leads:

• Which contracts are expiring in the next 90 days without a structured renewal process?
• Where are you paying or charging prices that no longer match your executed agreements?
• Which contractual obligations — SLAs, milestones, insurance certificates — are tracked manually or not at all?
• What would change in your monthly close if every active contract were searchable and connected to D365?

When you can answer those with specific dollar figures, the technology decision becomes straightforward. If you cannot, no CLM tool will solve your problem. You are missing process governance, not software.

Contact us for Managed Service

CLM Is Not E-Signature

A complete contract lifecycle runs nine stages: intake, authoring, redlining, approval, execution, repository, obligation management, performance monitoring, and renewal. Most organizations handle approval and execution reasonably well. Stages one through three and six through nine are where the revenue leakage lives. Any evaluation that does not address all nine stages is solving the easy part of the problem.

Your Five Options — Decided Quickly

Native D365 only works if your contracts are transactional and your primary need is procurement compliance, not legal governance. The moment your legal team negotiates customer or vendor terms, this is insufficient.
SharePoint + Microsoft Syntex is a legitimate mid-market path in 2026. Syntex extraction models, Power Automate workflows, and Copilot in Word now close gaps that previously required dedicated CLM software. The honest limitations are no counterparty portal and no purpose-built redlining. Best for organizations where the bottleneck is process and repository, not external negotiation.
Enterprise ISV — Icertis, DocuSign CLM, or Conga — is the answer for $500M+ organizations with high contract volumes, complex negotiation cycles, and multi-jurisdictional obligations. Budget 12 to 18 months for implementation and expect year-one costs to exceed $500,000. Require demonstrated D365 Finance connector depth, not just API documentation.
Mid-market CLM on Power Platform — Dataverse-native ISVs or a well-architected Power Platform build — covers 80% of CLM requirements for $50M to $500M organizations at a fraction of enterprise ISV cost. The 20% gap is counterparty collaboration and enterprise redlining.
Vertical CLM tools (Ironclad, Evisort, Coupa Contract) are worth evaluating only when industry-specific requirements outweigh the value of deep D365 integration.

The AI Question

Copilot and Syntex have raised the floor of what is achievable without a dedicated CLM platform. They have not raised the ceiling. The decision rule is simple: if your legal team spends more than 20% of their time reviewing contracts for risk rather than negotiating terms, a purpose-built AI layer will pay for itself. If the bottleneck is workflow and process, Microsoft-native AI is likely the higher-ROI path.

The Decision in One Rule

Match the CLM investment to the revenue and risk exposure of the contracts you are managing — not to the sophistication of the technology available.
A $75M professional services firm with 150 active contracts does not need Icertis. A $600M manufacturer with cross-border vendor obligations should not be running on SharePoint lists. Get the revenue-at-risk number first. The right option becomes obvious.

Contact us for Managed Service

The post The CLM Decision Playbook for Dynamics 365 Leaders appeared first on ERP Software Blog.

Most process manufacturers don't experience a sudden ERP failure. They experience something slower, and in many ways harder to fix: the system still technically works, but the team has quietly built a parallel infrastructure of spreadsheets, shared folders, and manual workflows to compensate for what it can't handle.
By the time that parallel infrastructure is visible, it's usually load-bearing. Removing it requires more effort than implementing a better system from scratch. And that's before you account for the compliance exposure it's been quietly creating.

What Process Manufacturing Actually Asks of an ERP

Process manufacturing — any production environment built around formulas, recipes, or batch-level inputs — introduces a category of operational complexity that discrete manufacturing doesn't share. Inputs fluctuate in potency or yield. Formulations change over time. Co-products and by-products affect costing in ways that don't follow standard inventory logic. Shelf life creates distribution constraints. Regulatory requirements demand lot-level traceability that survives an audit or a recall scenario.
An ERP built for process manufacturing needs to handle all of this natively — batch-level costing, controlled formula revision management, integrated quality workflows, compliance documentation generated as part of production rather than reconstructed afterward. When it doesn't, teams compensate. And those compensations accumulate.
The data reflects this: 48% of suppliers in batch-based manufacturing environments still rely on manual spreadsheets for key operational tracking, and 39% of those teams report data entry errors as a recurring problem. The ERP is in place. The data just isn't in it.
 

Why the Break Point Comes Faster Than Expected

The challenge with process manufacturing ERP misalignment is that it's not visible at launch. A system that handles today's SKU volume, today's formulation complexity, today's compliance requirements may look like a reasonable fit on go-live day. The problem surfaces as the business grows.
New product lines add SKU complexity. Regulatory requirements tighten — particularly in food and beverage, nutraceuticals, specialty chemicals, and personal care. Multi-site operations introduce multi-location traceability requirements. Each of these stresses the architecture in ways that compound rather than add up linearly.
The financial consequence of getting this wrong is significant. The average product recall event now carries $10 million in direct expenses — and that assumes the affected lots can be isolated quickly. When lot genealogy lives in spreadsheets rather than a governed ERP system, recall scope expands because the data isn't available at the speed the situation demands.
 

The Warning Signs Worth Taking Seriously

The operational signals of ERP misalignment in process manufacturing are consistent across industries and company sizes. They don't always appear together, but when two or three are present simultaneously, the architecture question is usually overdue.

• Lot genealogy reconstruction requires manual effort at audit time — the ERP can't surface a clean, complete trace from raw material to shipment without spreadsheet assistance
• Formula revisions are managed outside the system — version control lives in shared files rather than governed ERP workflows
• Quality documentation is tracked in parallel tools — because the ERP workflow is too cumbersome or too slow to trust in production
• Inventory discrepancies driven by yield variance can't be reconciled inside the system
• Compliance preparation feels reactive rather than systematic — because the records aren't in one place

Individually, each of these can look like a process or training problem. Together, they indicate that the ERP architecture isn't absorbing the complexity the business has accumulated.
 

What ERP Fit for Process Manufacturing Actually Looks Like

The right ERP architecture for a process manufacturing environment doesn't just cover the checklist of features. It reflects how batch production actually operates — variable inputs, yield-driven costing, co-products, controlled revision management, quality gates embedded in the production workflow rather than appended to it.
Evaluating fit against that standard requires asking different questions than most ERP selection processes use. Not just "does the system have lot tracking?" but "what does the system do when lot genealogy becomes complex under volume pressure?" Not just "can it handle formula management?" but "how does it enforce revision control when formula changes happen under regulatory scrutiny?"
Western Computer, in partnership with Yaveon, works with batch-based manufacturers to implement and configure Dynamics 365 Business Central specifically for these operational realities. The combination brings Microsoft's platform depth together with Yaveon's process manufacturing-specific frameworks — built over decades of work in batch-based industries.
 

What the Right Next Step Looks Like

On June 18, Western Computer and Yaveon are hosting a live session — Built for Batch: What Long-Term ERP Stability Looks Like for Process Manufacturers — specifically for operations and IT leaders who are either evaluating new ERP options or questioning whether their current system can absorb where their complexity is heading.
The session walks through the ERP fit evaluation framework, a live demonstration of how D365 Business Central + Yaveon handles the scenarios that typically stress process manufacturing ERP systems, and the three architectural questions worth asking before any platform commitment. Register today to see what Business Central can do for process manufacturing.
 

The post Why Process Manufacturers Outgrow Their ERP Faster Than Expected appeared first on ERP Software Blog.

 
A brand-new event built specifically for the Microsoft Dynamics 365 Finance and Supply Chain Management partner community. Directions for Enterprise 2026 will bring together Microsoft leaders, ISVs, system integrators, consultants, developers, and decision-makers for three days of strategic insight and real-world collaboration.

When and Where?

Mark your calendar now. Directions for Enterprise 2026 takes place September 23-25, 2026 at the Tivoli Hotel and Congress Center in Copenhagen, Denmark.

Why Should You Be There?

The enterprise ERP space is moving fast. This event is designed to help partners keep up. Sessions will cover: 

• AI-driven business processes across finance, HR, supply chain, and operations 

• The shift from implementation partner to AI advisory partner 

• Real-world Copilot and agent-based ERP use cases 

• Enterprise architecture and scalability best practices 

Whether your role is strategic, technical, or commercial, the agenda is being built to deliver value across the board.

Who Will You See There?

The sponsor lineup for Directions for Enterprise 2026 is already taking shape, and it is an impressive one. Some of the most recognized names in the Dynamics 365 ecosystem will be on the floor, making it an ideal opportunity to connect with the solutions and teams that matter most to your business.  

Platinum Sponsors: 

• Microsoft 

Gold Sponsors:

• Dynalogic

• Tasklet Factory - ERP Software Blog Member
  Tasklet delivers a comprehensive and intuitive Mobile WMS solution for Microsoft Dynamics Finance & Supply Chain Management. With powerful features like Easy App Configuration and our newest addition, Easy Flow Configuration, tailoring the app to your customers’ warehouse processes has never been easier. Warehouse employees can personalize the interface to match their preferences, streamlining daily processes, increasing productivity, and significantly reducing errors. Meet us at Directions for Enterprise to discover how Tasklet Mobile WMS can empower and optimize your F&SC operations. Learn more: User-friendly Mobile WMS for Microsoft Dynamics 365 FO/AX. 

• Yavrio

Silver Sponsors:

• Binary Stream - ERP Software Blog Member
  Binary Stream works with more than 200 Microsoft partners worldwide to extend the capabilities of Microsoft Dynamics 365 Business Central and Dynamics 365 Finance for customers in the ecosystem. For over 25 years, Binary Stream has provided trusted, fully embedded solutions to help more than 3,000 customers across the world maximize their ERP investments. Our solutions enable and streamline complex subscription billing, multi-entity management, property and lease management, and other advanced financial and operational requirements. 

• Cegeka

• Companial

• Dox42

• Ecosio

• Eone Solutions - ERP Software Blog Member
  The eOne Solutions mission is simple: we're here to make connecting apps to apps and people to apps a simpler, developer-free experience for businesses. We know every business is unique and juggles 100+ applications, leading to data silos, costly mistakes and potential headaches. That's where we step in with an iPaaS suite that is user-friendly, no-code, and is the only iPaaS that delivers both virtual and physical data integration. eOne is scalable, 100% configurable, AI-ready, and covers critical ERP, CX, and CRM integration use cases to make your people smarter. Trusted by thousands of customers across the globe, our team of ERP & CRM integration experts are on a mission to help businesses conquer custom integration, migration and reporting challenges with speed and precision. We want you to scale and grow, while we handle the rest. Learn more at www.eonesolutions.com. 

• Kyriba

• Lasernet

• QBuild Software

• SEER 365

• Truvio - ERP Software Blog Member
  Truvio helps organizations close what we call the ERP Value Gap, the space between what ERP systems can do and what your business needs them to do, by unifying finance, operations, and commerce in a Microsoft-native suite built on Dynamics 365. That gap is where manual workarounds, disconnected add-ons, compliance risks, and delayed decisions often live. By closing that gap, Truvio elevates the ERP promise from potential to performance, simplifying complexity, strengthening controls, and accelerating time to value through embedded domain expertise and AI-driven automation. 

Bronze Sponsors:

• Experlogix - CRM Software Blog Member
  Experlogix delivers proven industrial-grade software solutions - CPQ, Document Automation, and Digital Commerce - that have been trusted by organisations around the globe for 25 years. We enable smart, scalable quoting, compliant document generation, and 24x7 B2B webshops fully integrated with Microsoft Dynamics CRM and ERP systems to enable revenue growth and productivity savings. These products are supported by a global team of experienced professionals with a passion for understanding customer requirements and delivering solutions that help businesses grow faster, with less friction. The Experlogix team of trusted advisors bring expertise without ego - combining technical excellence with a practical and grounded approach. 

• Portal Systems

What Does It Cost?

• Early Bird Ticket: €1299 
• Normal Ticket: €1499 (Available from July 1st) 
• Group discount: 10% for five or more attendees, 20% for ten or more  

Ready to Book?

If your organization works within the Dynamics 365 Finance and Supply Chain Management ecosystem, this is one event you do not want to miss. Register now at directionsforpartners.com/enterprise2026 and secure your spot today. 

The post Why Directions for Enterprise 2026 Should Be on Every D365 F&SCM Partner's Radar appeared first on ERP Software Blog.

Dynamics 365 Finance & Operations Performance Optimization Does Not Always Require Rebuilding What You Have

When a Microsoft Dynamics 365 Finance & Operations environment starts to feel slow, unstable, or difficult to support, it is understandable that teams begin to wonder what part of the original implementation is the problem. By that point, users may be frustrated, finance may be waiting on posting processes, and IT may be moving from ticket to ticket without a shared explanation for what is actually happening. The pressure to make a decisive move can make rebuilding the customizations, or even the implementation itself, seem like the cleanest answer. 
In practice, that is not always where the evidence points. Many D365 F&O performance issues come from accumulated operational and technical friction: inefficient batch execution, poorly timed integrations, unmanaged customizations, old AX-era patterns, weak environment governance, missing indexes, or limited diagnostic visibility. None of those problems should be ignored, but they do not automatically mean the implementation needs to be rebuilt. 
A more disciplined approach is warranted. Before an organization commits to rebuilding customizations, replacing features, or redoing the implementation, it should first determine whether the current environment can be stabilized through diagnostics, tuning, customization cleanup, and better governance. For many ERP managers and Dynamics 365 administrators, that path is faster, less disruptive, and more defensible than tearing down what already works. 

1. Begin With Diagnostics Before You Change the System 

The most expensive performance fixes are often the ones made before anyone has confirmed the cause. A team sees delays in posting or reporting, then responds by adding capacity, restarting services, adjusting indexes, disabling an integration, or rewriting code. Each of those actions can be reasonable in the right context, but without evidence they become experiments carried out inside a live business system. 
A diagnostic-first approach slows the impulse to treat symptoms and instead asks which layer is actually creating the bottleneck. Batch execution patterns, SQL telemetry, query behavior, integration timing, user sessions, and workload peaks all need to be viewed together. That combined picture is what separates a performance tuning effort from a troubleshooting loop. 
For Ryse Technologies, this is also where tools such as Performance Scout fit into the broader conversation. A diagnostic tool should not simply confirm that the system is slow. It should help teams see where the delay begins, which process is involved, and whether the fix belongs in code, data, integration design, batch scheduling, or governance. Performance Scout is incredibly effective for capturing diagnostics about intermittent or persistent performance issues in production without having to recreate the issue in a test environment. 

2. Reorganize Batch Jobs Around Real Business Usage 

Batch execution is one of the easiest areas to overlook because it usually runs in the background. Users experience the slowdown on the front end, but the source may be a transaction-heavy job competing with the same resources they need to complete daily work. This is especially common when invoice processing, inventory updates, reporting refreshes, integrations, and synchronization tasks are all scheduled around convenience rather than workload impact. 
The issue is not that batch processing is bad. The issue is that many environments keep adding jobs without revisiting how those jobs interact with the business day. By the time finance, operations, and reporting teams are all active, background tasks may already be consuming capacity that should be reserved for interactive users. 
Improving performance may require reorganizing batch groups, resequencing dependencies, introducing throttling, or moving certain jobs into off-peak windows. These changes are not glamorous, but they are often the difference between a system that feels constantly strained and one that supports the rhythm of the business. 

3. Reduce Customizations That No Longer Serve the Business 

Customizations usually begin with a reasonable business request. A process needs to be supported, a screen needs to be adapted, a legacy workflow needs to be carried forward, or a partner needs a workaround to keep the project moving. The problem is that those decisions rarely get revisited once the organization is live. Over time, they become part of the performance burden. 
This is especially true for environments that have moved from AX to D365 F&O, passed through multiple implementation partners, or relied on emergency fixes during go-live. Deprecated patterns, duplicated workspaces, inefficient extensions, over-customized forms, and unsupported logic can all slow the system while also making future troubleshooting harder. 
Reducing customizations and technical debt does not mean stripping away everything that makes the environment fit the business. It means asking which customizations still create value, which ones duplicate native D365 functionality, and which ones are making the environment harder to maintain than it needs to be. 

4. Tune Indexes and Long-Running Queries With Precision 

Database behavior is often where vague complaints about slowness become measurable. A user may describe frozen screens, delayed postings, slow lookups, or reporting lag, but behind those experiences there may be missing indexes, inefficient joins, oversized tables, locking patterns, or long-running transactions. These issues can quietly affect multiple parts of the business before anyone connects them to a common root cause. 
Indexing and query optimization should be handled carefully because not every index improves performance in every context. Adding indexes reactively can create maintenance overhead, dramatically increase database size, or mask deeper design issues. The better approach is to identify where high-impact queries are slowing execution, then tune based on observed behavior rather than assumption. 
In a performance tuning services engagement, this is where technical depth matters. The objective is not to make a long list of possible improvements. The objective is to identify the changes most likely to improve actual execution times, reduce contention, and support the workloads the organization depends on every day. 

5. Treat Monitoring and Diagnostics as Different Disciplines 

Monitoring is valuable because it tells teams when something is wrong. It can surface CPU spikes, failed jobs, memory pressure, uptime issues, or abnormal activity. For operational support, that visibility matters. It gives teams a signal that the environment needs attention. 
Diagnostics answer a different question. They help teams understand why the issue is happening, where it began, and what should change. Without that deeper layer, monitoring can create a pattern where IT is constantly alerted but not necessarily equipped to resolve the underlying cause. 
This distinction is important for mid-market and enterprise organizations that do not have unlimited internal capacity. A small team can spend enormous time reacting to alerts, especially when the same issues keep returning. Performance diagnostics tools like Performance Scout can help reduce that burden by turning recurring symptoms into a clearer remediation plan. 

6. Reschedule and Redesign Integrations That Compete With Users 

Integrations are often treated as plumbing until they become a performance problem. D365 F&O may be connected to CRM, warehouse systems, payroll platforms, eCommerce, reporting tools, or industry-specific applications. Each connection may make sense on its own, but together they can create heavy data movement at the wrong time. 
When integrations run during peak usage windows, the user experience can deteriorate even if the integration itself appears to be functioning. Finance teams may see slower posting, operations may experience lag, and IT may struggle to explain why the environment feels unpredictable. The issue is not always a failed integration. Sometimes the issue is a successful integration consuming resources at the worst possible moment. 
Optimization may involve changing execution windows, reducing duplicate processing, redesigning data flows, or moving reporting workloads away from transactional activity. These changes can be less disruptive than rebuilding the integrations from scratch, but they require teams to look at D365 as part of a wider operating system rather than a standalone application. 

7. Make Non-Production Environments Reliable Enough for Real Testing 

Performance work becomes much harder when non-production environments cannot be trusted. If a sandbox is stale, incomplete, manually refreshed, or materially different from production, it can create false confidence. A fix that appears to work in testing may fail under real workload conditions, while a problem that only appears in production becomes harder to reproduce safely. 
This is why environment governance belongs in a conversation about D365 performance. Reliable replication gives teams a safer way to reproduce issues, validate fixes, test workloads, and reduce production risk. It also helps partners and internal teams move faster because they are not debating whether the test environment reflects reality. The process required to prepare an environment after it has been copied from production can be difficult and expensive, which is why Ryse Technologies created the Clone Commander utility. Clone Commander automates all of the steps needed to prepare an environment after it has been copied including reducing the database footprint, reconfiguring the application (enabling users, configuring integrations, etc), and obfuscating sensitive data. 
For organizations trying to speed up D365 F&O without tearing the implementation down, this is often an overlooked lever. Better non-production discipline does not just improve testing. It improves the quality of decision-making before changes reach the live environment. 

8. Modernize ALM and Deployment Practices Before They Create Regression Risk 

Manual deployments tend to survive longer than they should because teams build habits around them. A developer knows the steps, a project team trusts the routine, and urgent fixes keep moving. The risk is that the process depends too heavily on individual memory, inconsistent branching, limited validation, and informal controls. 
In a complex D365 F&O environment, that kind of deployment model can create instability even when the change itself is small. A fix can introduce regression risk, a release can be hard to trace, or a rollback can become more difficult than expected. Over time, deployment anxiety slows improvement because teams become reluctant to change anything unless the issue is severe. 
Modern ALM practices, including Azure DevOps pipelines, structured branching, validation environments, and clear promotion controls, help stabilize the path from development to production. They do not solve every performance problem, but they reduce the chance that tomorrow's fix becomes next month's slowdown. 

9. Rebuild User Confidence Through Stabilization, Not Just Speed 

A slow ERP system does more than waste time. It changes how people talk about the system. Once users lose confidence, every delay, error, or unclear process can be interpreted as proof that D365 cannot be trusted. Support volume rises, leaders hear competing explanations, and IT is asked to defend a platform that may not yet have been properly diagnosed. 
That is why implementation stabilization is broader than technical tuning. It requires visible progress, clear issue ownership, better communication, and a shared understanding of what is being fixed. Users do not need every technical detail, but they do need to see that the organization has moved from reaction to control. 
Performance optimization should therefore be measured not only by faster postings or fewer failed jobs, but also by whether teams regain confidence in the platform. When people trust the system again, adoption improves, support noise decreases, and leadership can make decisions with less friction. 

10. Bring in External Specialists When the Internal Team Needs a Clearer View 

Internal teams often know the environment better than anyone, but that does not always make performance issues easier to diagnose. They are also managing daily support, stakeholder pressure, backlog priorities, and business continuity. When problems have accumulated across code, integrations, batch jobs, data, environments, and partner decisions, it can be difficult to step back far enough to see the pattern. 
External specialists can help by bringing a structured diagnostic process and a less entangled view of the environment. The goal is not to replace internal knowledge. The goal is to organize it, test it against telemetry, and turn it into an actionable plan. 
This is also where mid-market partner and consultant selection becomes important. A good D365 performance partner should be able to explain what they are investigating, how they will separate symptoms from causes, and where they believe the organization can improve without unnecessary disruption. 

Speeding Up D365 F&O Without a Full Rebuild Starts With Visibility 

Rebuilding parts of the implementation may be necessary in some environments, especially when the original build has structural flaws that cannot be safely corrected in place. But it should not be the default conclusion every time performance declines. For many organizations, the better first step is to understand whether the current platform can be stabilized through diagnostics, tuning, technical debt reduction, stronger ALM, and better environment governance. 
The practical question is not whether D365 F&O can be made faster in the abstract. The practical question is where the friction is coming from, what it is costing the business, and which changes will create the most meaningful improvement with the least disruption. 
Ryse Technologies helps organizations answer those questions by diagnosing difficult and unusual D365 problems, stabilizing troubled environments, and supporting long-term Dynamics 365 Finance & Operations performance optimization. If your team is trying to speed up D365 F&O without rebuilding what already works, the right starting point is not a teardown. It is evidence. 

Frequently Asked Questions 

What causes Dynamics 365 Finance & Operations to slow down over time? 

D365 F&O often slows down because several issues accumulate at once. Common causes include inefficient batch scheduling, poorly timed integrations, unnecessary customizations, missing indexes, technical debt from prior implementations or AX upgrades, and limited diagnostic visibility. 

Can D365 F&O performance issues be fixed without rebuilding the implementation? 

Yes, in many cases. If the core implementation is still viable, organizations can often improve performance through diagnostics, tuning, customization cleanup, ALM modernization, and better environment governance before considering a rebuild. 

What is the difference between monitoring and diagnostics in D365? 

Monitoring shows that something is wrong, such as a failed job, a spike in usage, or a slowdown. Diagnostics help explain why it is happening and what needs to change to prevent the issue from recurring. 

When should a company bring in external D365 performance specialists? 

External support is useful when performance problems keep returning, internal teams cannot isolate the root cause, or the environment has accumulated complexity across code, integrations, data, batch jobs, and deployments. A specialist should help create clarity, not simply add another opinion. 

Ready to Improve D365 F&O Performance Without Starting Over? 

Ryse Technologies helps organizations diagnose and stabilize difficult Dynamics 365 Finance & Operations environments through performance diagnostics, implementation stabilization, environment optimization, ALM modernization, and troubleshooting acceleration. 
Contact the Ryse team to discuss your D365 environment and identify where performance friction may actually be occurring. 

The post 10 Ways to Speed Up Dynamics 365 F&O Without Rebuilds appeared first on ERP Software Blog.

Weidenhammer helps food and beverage manufacturers modernize ERP and regain control of inventory, production, and compliance. Learn more at hammer.net. 

What ERP Capabilities Do Food and Beverage Manufacturers Actually Need?

If a customer called your plant right now and asked which lots of a finished-good went to which distribution centers in the last 72 hours, could you answer before lunch? For most food and beverage manufacturers, that one question exposes every weakness hiding inside the current system stack. Modern F&B ERP, built on Microsoft Dynamics 365 Business Central and extended with YAVEON ProBatch, closes that gap. It gives leaders real cost visibility, defensible traceability, and the ability to grow without disrupting what works. This solution is purpose-built for process manufacturing, where formulas, variable yields, and regulatory complexity make generic discrete-assembly ERPs an expensive mismatch. 
This is the short version of what F&B leaders should expect from an ERP in 2026, and where Business Central fits. 

The Real Problem Isn't Just Compliance. It's Working Without a Live Picture of the Plant. 

Most ERP conversations in food and beverage start with FSMA, SQF, and recall readiness. Those matter. But the deeper issue is speed. Regulations, customer requirements, and supply conditions shift faster than legacy systems can keep up with, and the response time that used to be acceptable now results in deductions, lost shelf space and, in the worst cases, recalls or fines. Leaders are making pricing, production, and supplier decisions against data that is days or weeks old, spread across spreadsheets, a legacy MRP, a QC system, and a warehouse tool that nobody fully trusts. Institutional knowledge, the kind that lives in the head of the scheduler who has been there 22 years, covers the gaps until it doesn't. 
That is how silent margin leakage happens. A yield variance, an ingredient sub, a changeover that ran long, none of it ties back to a product-level P&L until month-end surprises the CFO. 

Cost Control That Survives Ingredient Volatility 

Business Central with YAVEON ProBatch captures actual production cost at the batch level, not standard cost dressed up in a report. That means yield variances, ingredient substitutions, labor fluctuations, and landed cost all flow into margin by SKU, customer, channel, and region. Add Power BI on top and scenario modeling stops being a finance project and becomes a Monday-morning question: what happens to margin if this supplier moves 9%, or if we switch co-packers for the club channel? 

Traceability and FSMA Rule 204 Without a Separate System 

Bi-directional lot traceability, from raw material receipt through processing, packaging, and shipment, is expected in the industry today. Where Business Central earns its place is operational: Key Data Elements captured at Critical Tracking Events as a byproduct of normal transactions, HACCP control points tied to production orders, COA capture, allergen segregation enforced through picklists and release holds, and audit-ready documents stored alongside the lot record. When the 24-hour sortable trace file is requested, the data is already assembled, without scrambling to create it. This is the difference between a system that was retrofitted for compliance, or worse, one that relies on manual processes, and a system where traceability is woven into every transaction from the start. 
 

End-to-end item tracing in Microsoft Dynamics 365 Business Central for a bakery product. This Item Tracing screen provides full forward and backward traceability — linking finished production orders, raw material consumption (flour, sugar, butter, sprinkles, egg), lot numbers, and package numbers across the entire supply chain. Bi-directional lot traceability like this enables food and beverage manufacturers to support rapid mock recalls, identify affected ingredients in minutes, and maintain FSMA, HACCP, and SQF compliance with auditable digital records.
Watch the full series about how Business Central can support your manufacturing processes.

Recipes, Yields, and Multi-Output Reality 

Formulations are living assets. An F&B ERP must handle version-controlled recipes, batch scaling, co-products and by-products with cost allocation, yield and scrap tracking, and multi-level BOMs for intermediates and packaging. Business Central supports this structurally, making cost and quality drift visible in real time. 

Production BOM version comparison in Microsoft Dynamics 365 Business Central showing side-by-side differences between bill of materials versions for a manufactured product. This screen enables food and beverage manufacturers to track recipe and formula changes over time — comparing component quantities across BOM versions to maintain full version control, ensure consistent product quality, and support regulatory audit trails required for FSMA, HACCP, and SQF compliance.

Production, Supply Chain, and Shelf-Life 

Scheduling in F&B goes beyond efficiency. It includes allergen sequencing, changeover minimization, catch-weight accuracy for variable items, rework disposition, and FEFO inventory tied to dynamic expiration. By adding Copilot for AI-driven demand sensing, Power Automate for exception alerts, and vendor scorecards within the procurement workflow, plants can move from reacting to constraints to anticipating them. 

Lot-level inventory tracking with expiration dates in Microsoft Dynamics 365 Business Central. This Item Availability by Lot No. screen shows real-time inventory, gross requirements, scheduled receipts, and available inventory for each production lot — enabling FEFO (First-Expired, First-Out) picking and shelf-life management critical for food and beverage manufacturers.

 Customer, Channel, and Growth 

Private label, club, foodservice, and DTC each bring their own SKU variants, EDI maps, and retail program rules. Business Central handles customer-specific items and supports EDI integration, so customer profitability is visible before the deduction shows up. For multi-site operations, Business Central’s data model scales across plants without forking the chart of accounts every time. For multi-entity or post-acquisition scenarios, add-ons like Multi-Entity Management (MEM) enable centralized control and reporting. 

Sustainability as Auditable Data, Not Just a Talking Point 

Regulators, retailers, and trading partners are asking for numbers, not narratives. Carbon, waste, packaging, and yield data must come from transactional systems. Business Central captures the transactional details across procurement, production, and logistics. Dataverse and Power BI turn that detail into auditable sustainability reporting without a manual spreadsheet cycle. 

Where This Leaves F&B Leaders 

The real ROI of a modern F&B ERP is not only the audit you pass. It is the decisions you make three weeks earlier because the data is already right. Where is your current system forcing you to guess? 
Weidenhammer works with food and beverage manufacturers to move from legacy systems to Dynamics 365 Business Central, with deep domain expertise in production, compliance, and shelf-life management. Start a conversation at hammer.net.

The post Food and Beverage ERP: Controlling Cost, Compliance, and Growth with Microsoft Dynamics 365 Business Central appeared first on ERP Software Blog.

Introduction

Artificial Intelligence is no longer a futuristic concept in manufacturing. Today, manufacturers are using AI to improve demand forecasting, optimize inventory levels, predict equipment failures, streamline production planning, and strengthen supply chain resilience.
However, despite significant investments in AI initiatives, many manufacturers struggle to achieve meaningful results.
The problem often isn't the AI technology itself.
The real challenge lies in the foundation supporting it.
Many manufacturing organizations continue to rely on legacy ERP systems that were designed for a different era—long before cloud computing, real-time analytics, intelligent automation, and AI-driven decision-making became business priorities.
As a result, manufacturers frequently discover that their existing ERP infrastructure limits the value AI can deliver.
In this article, we'll explore why legacy ERP systems prevent AI success and what manufacturers are doing to prepare for an AI-driven future.

The Growing Role of AI in Manufacturing

Manufacturers are under constant pressure to improve efficiency, reduce costs, and respond quickly to changing customer demands.
AI is helping organizations address these challenges through:

• Predictive maintenance
• Demand forecasting
• Production scheduling optimization
• Inventory management
• Quality control improvements
• Supply chain risk analysis
• Financial forecasting and planning

These capabilities can provide a significant competitive advantage.
But none of them can function effectively without access to accurate, connected, and real-time business data.
This is where many legacy ERP systems fall short.

The Hidden Problem: AI Is Only as Good as Your Data

Artificial Intelligence depends on data.
To generate reliable recommendations and predictions, AI requires:

• Clean data
• Consistent data
• Real-time data
• Cross-functional data visibility

Unfortunately, many legacy ERP environments create the exact opposite conditions.
Manufacturers often operate with disconnected systems, manual processes, outdated databases, and siloed information spread across departments.
When AI is fed incomplete or inaccurate information, the results become unreliable.
Simply put:
Poor ERP data leads to poor AI outcomes.

Click here to schedule your free demo.

6 Reasons Legacy ERP Systems Prevent AI Success

1. Data Silos Limit AI Visibility

In many manufacturing companies, critical information is stored across multiple systems.
Production data may exist in one application, financial information in another, inventory records elsewhere, and supplier information in separate spreadsheets.
Because AI relies on connected datasets, fragmented information creates significant limitations.

Business Impact

• Inaccurate predictions
• Incomplete insights
• Limited operational visibility

Why It Matters

AI cannot optimize what it cannot see.
Without unified business data, manufacturers struggle to gain meaningful intelligence from AI tools.

2. Legacy ERP Systems Lack Real-Time Data Processing

Modern manufacturing environments generate massive amounts of data every day.
Inventory movements, supplier updates, production schedules, machine performance metrics, and financial transactions constantly change.
Legacy ERP systems often process information in batches rather than in real time.
This delay creates a significant challenge for AI-driven decision-making.

Business Impact

• Slow response to disruptions
• Delayed planning adjustments
• Reduced forecasting accuracy

Why It Matters

AI performs best when decisions are based on current information rather than yesterday's reports.

3. Manual Processes Reduce Data Accuracy

Many manufacturers continue to rely on spreadsheets and manual data entry to manage critical operations.
While these processes may seem manageable, they introduce errors that directly affect AI performance.

Common Examples

• Manual inventory updates
• Spreadsheet-based forecasting
• Offline production tracking
• Manual financial reconciliations

Business Impact

• Data inconsistencies
• Forecasting errors
• Reduced trust in AI recommendations

Why It Matters

AI requires reliable inputs to generate reliable outputs.

4. Legacy Infrastructure Cannot Support Advanced Analytics

AI initiatives require substantial processing power and scalable infrastructure.
Many legacy ERP systems were never designed to support:

• Predictive analytics
• Machine learning models
• Large-scale data processing
• Advanced business intelligence

As data volumes increase, system performance often declines.

Business Impact

• Limited analytical capabilities
• Higher maintenance costs
• Slower innovation

Why It Matters

Manufacturers need technology that can evolve alongside business growth and future AI requirements.

5. Supply Chain Disruptions Require Faster Decision-Making

Supply chain volatility has become a major concern for manufacturers worldwide.
Raw material shortages, transportation delays, geopolitical risks, and shifting customer demand require organizations to make rapid decisions.
AI can help identify risks before they become major problems.
However, legacy ERP systems often lack the visibility necessary to support proactive planning.

Business Impact

• Inventory shortages
• Production delays
• Increased operational costs

Why It Matters

Manufacturers need predictive insights, not reactive reporting.

6. Legacy ERP Systems Make AI Adoption More Expensive

Many organizations assume adding AI tools on top of their existing ERP environment is the most cost-effective approach.
In reality, integrating AI into outdated systems often creates additional complexity.
Manufacturers may need to:

• Build custom integrations
• Clean and migrate data
• Upgrade infrastructure
• Maintain multiple disconnected platforms

Business Impact

• Higher implementation costs
• Longer project timelines
• Lower return on investment

Why It Matters

A modern ERP platform reduces complexity and accelerates AI adoption.

What AI-Ready Manufacturers Are Doing Differently?

Manufacturers that successfully leverage AI typically focus on building a strong digital foundation before implementing advanced technologies.
Their priorities often include:

Centralizing Business Data

Creating a single source of truth across finance, operations, procurement, inventory, and production.

Automating Manual Processes

Reducing human intervention and improving data consistency.

Enabling Real-Time Visibility

Providing leadership teams with immediate access to operational and financial information.

Moving to Cloud-Based ERP Platforms

Supporting scalability, innovation, and future AI initiatives.
Rather than treating AI as a standalone project, these organizations view it as part of a broader digital transformation strategy.

How Microsoft Dynamics 365 Finance & Operations Supports AI-Driven Manufacturing

Microsoft Dynamics 365 Finance & Operations helps manufacturers establish the foundation required for successful AI adoption.
The platform combines operational visibility, financial management, supply chain intelligence, and advanced analytics within a unified cloud environment.
Key capabilities include:

• Real-time production and inventory visibility
• Intelligent demand forecasting
• Automated financial processes
• Supply chain optimization
• Advanced analytics and reporting
• Scalable cloud infrastructure
• Integration with Microsoft's AI ecosystem

By connecting business-critical data across departments, D365 F&O enables manufacturers to make faster, smarter, and more informed decisions.

The Future of Manufacturing Depends on an AI-Ready ERP Foundation?

AI has the potential to transform manufacturing operations, but technology alone is not enough.
Manufacturers cannot expect AI to deliver accurate forecasts, predictive insights, or operational efficiencies when the underlying ERP system lacks the visibility, scalability, and data quality required to support those outcomes.
The organizations achieving the greatest success with AI are not simply investing in new tools.
They are modernizing the systems that power their business.
For manufacturers still relying on legacy ERP platforms, the path to AI success begins with creating a connected, intelligent, and future-ready operational foundation.

Ready to Prepare Your Manufacturing Business for AI?

At Dynamics Square, we help manufacturers modernize operations with Microsoft Dynamics 365 Finance & Operations, enabling greater visibility, automation, and AI readiness across the enterprise.
Speak with our ERP experts to assess your current environment and discover how a modern ERP platform can support your long-term growth strategy.

The post Why Manufacturers Can't Achieve AI Success With Legacy ERP Systems? appeared first on ERP Software Blog.

Why B2B distributors on Microsoft Dynamics keep absorbing failures their integration dashboards never flag 
B2B distributors running Microsoft Dynamics often invest heavily in ERP-commerce integration and still find their operations teams clearing order exceptions that should never have reached the warehouse. The monitoring tools report healthy syncs. The fields are populated. The orders are flowing. The failure is not in the connection between systems,  it is in what the connection chooses to carry. 
One Order, Two Guarantees the ERP Never Made 
A procurement lead at a regional electrical contractor opens his distributor’s eCommerce portal to source materials for a commercial retrofit job. The distributor’s back office runs on Dynamics 365 Business Central. The product listing shows 110 units available. His account profile displays Net 30 as an active payment option. He selects 85 units, chooses Net 30, and submits. The order confirmation arrives in his inbox within seconds. He forwards it to his site supervisor and books the delivery window into the crew schedule. 
From his position, the transaction is complete. A supplier he has worked with for years just confirmed availability and payment terms through their own digital channel. He has no reason to question either. 
The distributor’s warehouse and finance teams are already looking at two versions of the truth. The warehouse cannot fill the order as confirmed. Finance cannot release it on the terms the storefront offered. Both failures originated at the same point in the integration design, and neither appeared in the system logs as an error. 
What Business Central Tracks and What the Storefront Received 
Inventory in Dynamics 365 Business Central is not a single value. It is a set of related operational states that the system maintains to reflect how quantity is actually allocated across the business. Total on-hand quantity exists alongside reservations held against open sales orders and work orders, safety stock levels configured to protect against demand variability, and inbound quantity tied to purchase orders and warehouse transfers not yet received. Each state has a different meaning for fulfillment. The number the system considers available to promise is a calculation, not a stored field. 
When the distributor integration was built, it mapped inventory to the storefront by passing the on-hand total, likely summed across warehouse locations. The eCommerce platform received a number. It stored that number as a product attribute and used it to render availability on the listing page. The platform had no mechanism to interpret what the number included or what the ERP considered committed against it. 
Of the 110 units the storefront displayed as available, 35 were reserved against existing open orders, 20 were held at the safety stock threshold, and approximately 55 were actually available to promise. The warehouse team discovered the shortfall when they pulled the pick list. The failure was not that the inventory figure was stale, though latency compounds this problem significantly. The failure was that the meaning of the figure never traveled with it. Sellable quantity requires the integration to derive what the ERP would recognize as available, not copy what the ERP happens to store. 
What Business Central Calculates and What the Storefront Displayed 
The same order carried a second authorization failure at checkout. 
In Dynamics 365 Business Central, payment terms are not simply a label attached to a customer record. They are enforced through a credit evaluation that runs at order entry and, in many configurations, again before the order is released to the warehouse. That evaluation takes the customer’s credit limit, subtracts the outstanding balance and the total value of open orders already committed to the account, and returns what the account can absorb on the requested terms. Layered on top of that calculation are account-level conditions: aging holds that activate when invoices pass a defined number of days past due, hard and soft blocks tied to credit risk policy, and in some cases prepaid-only restrictions applied by contract or customer segment. 
The storefront had access to none of those conditions when the procurement lead logged in. The last integration run had passed a credit limit value and a flag indicating that the account carried Net 30 terms. The platform stored both as customer record attributes. At checkout, it rendered Net 30 as a selectable option. 
On the day the order was placed, outstanding invoices and existing open order commitments had already consumed most of the account’s available credit. Two invoices had aged past due, which in the distributor’s Business Central configuration triggered a more restrictive account state. When the order reached the ERP, Business Central ran its credit evaluation and flagged the order for hold. Finance reviewed it, confirmed the account was not eligible for Net 30 on this transaction, and stopped it. 
The buyer had already received confirmation. Hours later, he received a phone call. The explanation involving credit balances and aging thresholds did not change what the storefront had already put into writing. 
The Integration Pattern Underneath Both Failures 
The structure of both failures is identical. The integration passed ERP values to the storefront without passing the conditions that govern those values. At i95Dev, this is the most consistent pattern we observe across ERP-commerce implementations on Dynamics 365 Business Central and Dynamics 365 Finance. The storefront stores what it receives and renders it as a buying signal or an available option. The ERP, when it receives the order, applies the logic that was never shared with the channel. 
The integration logs report no errors because there are no connectivity failures. Fields are syncing on schedule. Orders are reaching the queue. On a monitoring dashboard, the implementation looks healthy. The gap does not appear in those tools because it is not a technical failure. It is an interpretation failure. The storefront is operating on copied values. The ERP is operating on derived logic. When those two things diverge, the gap lands on the distributor’s operations and finance teams as manual resolution work carried in a daily exceptions queue that exists because the channel has no mechanism for asking ERP what it actually allows. 
The buyer sees something simpler: a promise that was not kept. 
What a Properly Scoped Integration Actually Requires 
Closing this gap is not primarily a matter of syncing more data or reducing the interval between sync runs. A storefront that operates on copied values will continue generating commitments the ERP has not authorized regardless of how frequently those values are refreshed. The correction requires the integration to execute ERP logic at the storefront boundary rather than downstream in an ERP queue. 
For inventory, the integration must produce a sellable quantity rather than pass a stored quantity. That figure is calculated from on-hand minus reservations minus safety stock, derived either directly from Business Central or from an integration layer that applies the same logic the ERP uses. The calculation should be scoped to the warehouses that serve the relevant fulfillment region rather than aggregated across all locations. It should also carry lead time information so the storefront can distinguish between what is available for immediate shipment and what is on order with a projected receipt date. Inbound purchase orders and warehouse transfers represent a separate availability state and should be surfaced to the buyer as such, not folded silently into the displayed stock count. 
For payment terms and credit, the integration must shift from copying credit data at intervals to querying credit status at the moment of checkout. When a buyer begins the checkout process, the storefront queries Business Central to retrieve the current outstanding balance, the total value of open order commitments, and the account’s current state, including any aging conditions or blocks that may have been applied since the last sync. The storefront then computes available credit using the same formula the ERP applies and presents only the payment options the account qualifies for at that moment. If the proposed order would push the account over its available credit, or if the account is in a restricted state, that determination should occur before confirmation is issued. Pre-validating orders against credit rules before the storefront generates a confirmation is the only mechanism that reliably prevents the channel from promising what the ERP will immediately block. 
This distinction plays out consistently for Dynamics 365 ERP customers. The implementations that hold at scale, where operations teams are not spending their days resolving order exceptions and finance is not fielding calls from buyers disputing holds, are built with an understanding of how Business Central makes decisions at order entry, and they execute that logic at the storefront layer rather than leaving it to be caught downstream. 
For a detailed look at how mid-market distributors on Dynamics 365 typically scope this kind of integration work, i95Dev’s mid-market guide to ERP-eCommerce integration covers the architecture decisions that determine whether financial controls travel with the data or run after it. 
What the Buyer Decides After the Second Broken Promise 
B2B buyers in distribution and industrial supply are not natural early adopters of digital purchasing channels. They shift their ordering behavior to a supplier’s eCommerce portal because someone on the account team made the channel reliable enough to be worth the change in their own workflow. A procurement lead who books crew schedules and delivery windows against what a confirmation email says is extending operational trust to a digital channel. That trust is extended once. It is not extended again after the channel has generated commitments the supplier could not honor. 
When the integration is built to carry that logic, the confirmation email means what it says. The buyer books the delivery window and the warehouse can honor it. The procurement manager stops calling to verify before placing anything time-sensitive. That is the job the channel was built to do. 
When inventory figures prove unreliable, the storefront becomes a reference catalog. The buyer uses it to find part numbers and pricing indications, then calls the branch to verify stock before placing anything time-sensitive. That behavior change does not appear in the integration logs. It appears in call volume, in digital order attachment rates that plateau or decline, and eventually in the accounts where digital adoption stalled without a clear technical explanation. 
The commercial cost of this pattern is not dramatic. It does not show up as a single lost transaction. It accumulates in the accounts where buyers quietly moved job-critical orders to a competitor whose channel matched what their ERP knew, in the sales calls spent explaining why the portal said yes when the warehouse said no, and in the procurement managers who stopped trusting the channel before anyone on the distributor’s side noticed

The post The Order Your ERP Would Have Blocked Before the Storefront Said Yes appeared first on ERP Software Blog.

Insight Works has released Product Configurator v4.1 for Business Central, introducing context-aware rule logic, inherited sub-configuration values, and configurable production order status. The update also resolves sub-configuration cost inconsistencies and improves lookup speed for teams managing complex configure-to-order workflows.

Insight Works has released Product Configurator v4.1 for Microsoft Dynamics 365 Business Central, delivering improvements to rule-building logic, sub-configuration cost handling, and interface performance. The update targets manufacturers and distributors that rely on configure-to-order workflows, where gaps in rule precision or inconsistent cost calculations lead to downstream errors in production planning and order management.
Two of the most significant changes in v4.1 address how configurations share data and how rules respond to context. Sub-configurations can now copy or inherit values from a parent configuration, eliminating the manual re-entry that previously slowed complex product builds and introduced transcription errors. Alongside this, rules can now reference variables directly from the record that triggers them — for example, identifying a specific choice code when a rule runs from an option choice. This context-aware logic allows the rule builder to behave more precisely across product hierarchies, reducing the need for workaround configurations or hardcoded values. For teams managing products with dozens of configurable options and nested sub-assemblies, these changes meaningfully reduce both setup effort and the risk of invalid outputs reaching production.
Version 4.1 also corrects cost inconsistencies that affected sub-configurations and choice-level pricing. Sub-configurations now correctly apply the calculated standard cost setting when created or updated from a parent, ensuring cost figures remain coherent across the full product hierarchy. Unit price, unit cost, net weight, and gross weight for child choices now update correctly when the update-on-when-used setting is active. On the scheduling side, users can specify the exact production order status, such as firm planned or released, when generating orders from sales orders in Business Central, giving planning teams direct control over where a new order enters the production queue. The release also improves interface speed: option choice lookups and choice variables for rule editing load significantly faster, and obsolete page fields have been removed to reduce visual noise and improve overall application performance.
"The rule-building changes in this release address something our users run into frequently: rules that need to behave differently depending on where they're triggered from," says Brian Neufeld, Director of Marketing at Insight Works. "That kind of context-awareness was difficult to achieve before v4.1. The sub-configuration cost corrections are equally important. If the numbers don't roll up correctly through a product hierarchy, you're solving an accounting problem instead of shipping product." For more information about Product Configurator, visit CPQforDynamics.com. Businesses looking to implement or upgrade can connect with any of Insight Works' 750+ global Microsoft Partners.

About Insight Works

Insight Works is a leading Independent Software Vendor (ISV) dedicated to creating apps exclusively for Microsoft Dynamics 365 Business Central. The company specializes in the manufacturing and distribution industries, providing innovative solutions that streamline operations and enhance productivity for businesses worldwide. With a vast reseller network comprising over 750 global Microsoft Partners, Insight Works ensures its apps are accessible and supported wherever businesses operate. Headquartered in Canada, Insight Works also maintains a regional office in the Netherlands, strengthening its global reach and commitment to localized support. Learn more at dmsiworks.com.

The post Insight Works Releases Product Configurator v4.1 for Microsoft Dynamics 365 Business Central appeared first on ERP Software Blog.

For many organizations still running Microsoft Dynamics GP, the challenge isn't simply maintaining an aging ERP system. It's the growing amount of time spent reconciling data, validating reports, and working around limitations that make it harder to support a modern business.
As companies grow, leadership teams need faster access to accurate information, stronger financial controls, and confidence that their ERP system can support future expansion.
One consumer products company recently faced those challenges firsthand. Following a private equity acquisition, the organization recognized the need to strengthen financial reporting, improve visibility across operations, and create a scalable foundation for future growth.
Their journey from Dynamics GP to Microsoft Dynamics 365 Business Central provides valuable lessons for finance leaders evaluating modernization initiatives.

Why the Company Decided to Move Beyond Dynamics GP

The company had successfully grown its business over many years and distributes products through major retailers across North America and internationally.
Following private equity investment, leadership identified several areas where modernization could create value:

• Stronger financial controls
• Improved reporting capabilities
• Better visibility across the organization
• Greater confidence in financial data
• A platform capable of supporting future growth

Like many GP users, reporting often relied on third-party tools and extensive spreadsheet manipulation. Data extraction, validation, and reconciliation consumed valuable time each month.
For finance leaders, these challenges can create risk. When reports require manual intervention, teams spend more time validating data and less time analyzing it.

Financial Controls Became a Growing Concern

One of the most significant challenges involved financial controls and data integrity.
During migration planning, the finance team uncovered numerous historical reconciliation issues that required cleanup before moving to the new system. Many of these issues stemmed from processes that allowed transactions to be posted without the safeguards and validations finance teams often expect.
As organizations grow, these small inconsistencies can compound over time.
Finance leaders need confidence that:

• Transactions are posting correctly
• Required information is captured
• Reports reflect accurate data
• Subledgers reconcile properly with the general ledger

Business Central's built-in validation capabilities helped address many of these concerns by introducing stronger controls around transaction processing and reporting.

A Structured GP to Business Central Migration Approach

ERP projects are rarely successful because of software alone.
Success often depends on planning, governance, user adoption, and implementation expertise.
Organizations evaluating a move from Dynamics GP often benefit from a structured migration framework that addresses data quality, process design, training, and long-term business objectives.
The company partnered with Crestwood Associates to guide the migration from Dynamics GP to Business Central.
The implementation focused on several key areas:
Data Integrity
Before migration, the team performed extensive data cleanup and validation activities to ensure clean opening balances and accurate reporting in the new system.
Role-Based Training
Department-specific training sessions helped users understand their responsibilities and gain confidence before go-live.
This approach reduced uncertainty and improved user adoption.
Project Governance
Daily working sessions, milestone tracking, and clearly defined ownership helped keep the project moving forward without overwhelming internal teams.
EDI Continuity
Because the company conducts significant business through major retail partners, maintaining EDI functionality was critical.
Extensive testing helped ensure business continuity and protected retailer relationships throughout the transition.

The Results: Faster Processes and Better Visibility

The move to Business Central delivered measurable improvements across multiple areas of the finance organization.

Month-End Close Improved by 37.5%

Perhaps the most notable result was the reduction in month-end close time.
8 Days → 5 Days
This represents a 37.5% improvement and returns valuable time to the finance team each month.

Reconciliations Became More Efficient

Financial reconciliations improved as reporting accuracy and visibility increased.

• Approximately 1 day saved per month

Accounts Payable Processing Accelerated

The finance team also reported meaningful gains in accounts payable efficiency.

• Approximately 2 days saved per month

Executive Reporting Became Significantly Faster

Prior to Business Central, leadership inquiries often required substantial effort to gather and validate information.
The process could take days.
Today, many of those same questions can be answered within hours using information available directly within the system.
This allows finance teams to spend less time collecting data and more time providing strategic insight.

Better Visibility Supports Better Decisions

One area that delivered significant value was margin reporting.
With improved reporting capabilities, the organization gained greater visibility into:

• Item-level profitability
• Retailer-level profitability
• Cost trends
• Pricing opportunities

This visibility helps leadership make more informed decisions about pricing, profitability, and operational performance.
Rather than debating whether the data is accurate, teams can focus on taking action.

Advice for Organizations Still Running Dynamics GP

Many Dynamics GP users are currently evaluating their long-term ERP strategy.
While every organization has unique requirements, several themes emerged from this project:
Modernization Is About More Than Technology
The most successful projects begin by identifying business challenges rather than focusing solely on software features.
Financial Controls Matter
Strong controls help reduce risk, improve reporting confidence, and create consistency across the organization.
User Adoption Is Critical
Training and process alignment play a major role in long-term success.
The Right Partner Makes a Difference
ERP implementations require hundreds of decisions.
Organizations benefit from experienced guidance that helps avoid costly mistakes and supports long-term success.
Not every organization is ready to migrate immediately. Many companies first evaluate whether they are receiving the support, guidance, and strategic planning they need from their current Dynamics GP partner.

Conclusion

For this organization, migrating from Dynamics GP to Microsoft Dynamics 365 Business Central delivered measurable improvements in efficiency, reporting, visibility, and financial control.
The results included:

• Month-end close reduced by 37.5%
• Faster reconciliations
• Faster accounts payable processing
• Improved executive reporting
• Stronger financial controls
• Better profitability visibility

For finance leaders evaluating the future of Dynamics GP, this case study demonstrates how modernization can create both immediate operational improvements and long-term strategic value.

Download the Full Case Study

See how Wet & Forget successfully migrated from Dynamics GP to Business Central and achieved measurable financial improvements across finance operations, reporting, and financial controls.
Download the Full Business Central Case Study →

The post Business Central Case Study: How One Company Reduced Month-End Close by 37.5% appeared first on ERP Software Blog.

Electronic Data Interchange, or EDI, helps businesses exchange documents such as orders, invoices, shipping notices, and other trading partner communications electronically. For companies using Microsoft Dynamics 365 Business Central, the right EDI add-on can reduce manual entry, improve transaction visibility, and help keep supply chain workflows moving inside the ERP system.
Business Central offers strong operational capabilities, but many companies still need specialized EDI functionality to meet retailer, supplier, warehouse, carrier, or compliance requirements. That is where Business Central EDI solutions can help. They extend the ERP system with automation, mapping, trading partner connectivity, managed services, and real-time visibility that may not be available out of the box.

How can attendees compare Business Central EDI solutions in one event?

Attendees can compare the featured EDI tools by watching short product demos from each provider and listening for differences in integration approach, managed services, mapping control, supported standards, transmission methods, dashboards, and support models.
Each solution featured in the Showcase is designed for Microsoft Dynamics 365 Business Central, but they do not all take the same approach. Some emphasize embedded ERP-native processing. Others highlight managed service expertise, large trading partner networks, scalable integrations, or support for specific supply chain workflows.
The Showcase format gives Business Central users a practical way to evaluate multiple options without scheduling separate discovery calls with each provider.
As a bonus, you’ll receive a free PDF comparison chart, an essential tool to evaluate each solution in the light of your organization’s unique needs. It’s yours to keep!
EDI for Dynamics 365 Business Central Comparison Showcase — Thursday, June 18th, 2026. Choose 9:00am, 12:00pm, or 3:00pm ET. Register now

Meet the Presenters and Their Best-of-Breed Business Central EDI Tools

The following previews offer a look at what each presenter plans to highlight during the Showcase. Use these summaries as a guide for what to watch for during the demos.

How does ProcessOne EDI automate supply chain processes in Business Central?

ProcessOne EDI is designed to help automate real-world supply chain processes, including orders, advance ship notices, invoicing, warehouse communication, and trading partner communication. Because the solution is fully embedded inside Business Central, users can manage EDI activity within a familiar ERP experience rather than relying on disconnected external systems for daily transaction work.
The ProcessOne demo will focus on embedded EDI automation for trading partners, warehouses, and supply chains. The company emphasizes real-time visibility, streamlined order-to-cash operations, and the ability to keep teams working directly inside Business Central.
ProcessOne also supports ANSI X12, EDifact, Tradacoms, CSV, XLS, and HTTP APIs, along with AS2, SFTP, FTP, and VAN transmission methods. Customers can use both test and production environments, and the solution offers transaction history, searchable document retention, archiving, managed service options, and self-service options.

How does Rand Group’s EDI 365 provide managed EDI services for Business Central?

EDI 365, a cloud-based EDI automation solution built for Microsoft Dynamics 365 Business Central, is designed to help manufacturers, distributors, and retailers automate EDI workflows without relying on disconnected systems. The solution supports real-time transaction visibility and helps businesses manage EDI activity directly within Business Central.
Rand Group combines its EDI technology with managed services, mapping expertise, onboarding support, and ongoing operational assistance. The company’s demo will highlight how EDI 365 can help reduce manual processes, improve visibility into transactions, and support scalable integrations across retailers, suppliers, warehouses, and carriers.
EDI 365 supports major EDI standards such as ANSI X12, EDIFACT, and XML. It also supports AS2, VAN, FTP, and SFTP transmission methods. Rand Group provides phone and email support for onboarding, mapping assistance, troubleshooting, transaction monitoring, and ongoing EDI operations.

How does TrueCommerce EDI connect Business Central users with trading partners?

TrueCommerce emphasizes the scale of its network, including more than 200,000 pre-connected trading partners and more than 500 live Business Central customers. Its solution is designed to automate the flow of orders, shipments, and invoices between trading partners and Business Central, helping reduce manual re-entry and improve operational visibility.
The demo will also highlight its managed service approach. TrueCommerce handles trading partner specification changes, provides support, and includes map updates as part of its model. For businesses that want EDI expertise along with the software, this approach can help reduce the internal burden of managing changing trading partner requirements.
TrueCommerce supports a broad range of EDI standards and formats, including X12, EDIFACT, Tradacoms, XML, cXML, JSON, flat file, PDF, and more. It also supports common transmission methods such as VAN, AS2, API, SFTP, and HTTPS. The solution includes pre-built EDI dashboards and reporting inside Business Central, along with support for Business Central workflows such as order-to-cash, procure-to-pay, and fulfillment.

What should you look for when comparing EDI tools for Business Central?

When comparing EDI tools for Business Central, look for how each solution handles day-to-day usability, trading partner requirements, data visibility, mapping, support, and long-term scalability.
A few key questions to keep in mind during the Showcase include:

• Is EDI managed directly within Business Central?
• Does the solution reduce duplicate data entry?
• Which EDI standards and transmission methods are supported?
• Are dashboards and exception alerts available?
• Does the provider offer managed services, self-service options, or both?
• How are mapping changes handled?
• Can the solution support warehouses, 3PLs, carriers, retailers, and other trading partners?
• What support options are available after implementation?

The best choice will depend on your Business Central environment, your trading partner network, your internal resources, and the level of support your team wants from the EDI provider.

Find the Right EDI Tool for Business Central

EDI plays an important role in automating trading partner communication, reducing manual work, and improving visibility across orders, shipments, invoices, warehouse activity, and other supply chain transactions within Business Central.
This year’s EDI for Dynamics 365 Business Central Comparison Showcase gives you the opportunity to review three different solutions in one focused event. You’ll see how ProcessOne Solutions, Rand Group, and TrueCommerce approach EDI for Business Central, and you’ll come away with a free PDF comparison chart, along with a clearer understanding of which solution may fit your organization’s needs.
Don’t miss this opportunity to compare Business Central EDI tools side by side and learn how each provider can help simplify trading partner communication!
Register now for the EDI for Dynamics 365 Business Central Comparison Showcase on Thursday, June 18th, 2026. Choose 9:00am, 12:00pm, or 3:00pm ET.
By ERP Software Blog Writer | www.erpsoftwareblog.com
 

The post Compare 3 EDI Tools for Dynamics 365 Business Central in the MSDW Comparison Showcase appeared first on ERP Software Blog.

OmniVue’s Recorder App for D365 CRM addresses challenges employees face when working away from the office. Teams in industries like field services, healthcare, insurance, legal, and construction often need to document conversations, inspections, or updates while moving between locations and working in environments with unreliable connectivity.
OmniVue’s Recorder App for Dynamics 365 CRM combines mobile audio recording, offline functionality, and direct CRM integration through Microsoft Power Apps. The result is a streamlined way to capture, manage, and sync recordings without adding complexity to field operations.

Key Highlights

• Record and manage audio files directly inside Dynamics 365 CRM
• Continue working offline with automatic synchronization when connectivity returns
• Attach recordings to CRM contacts, cases, inspections, and related records
• Use built-in workflow automation with Power Automate
• Improve field productivity with GPS navigation, multi-record viewing, and mobile-first functionality

What Is OmniVue’s Recorder App for D365 CRM?

OmniVue’s Recorder App is a mobile-first audio recording solution built with Microsoft Power Apps and designed to work directly with Dynamics 365 CRM. It allows field teams to securely capture audio recordings, associate them with CRM records, and manage data whether they are online or offline.
The app is designed for organizations that rely on accurate field documentation and need a practical way to connect audio recordings to customer interactions, inspections, agreements, or service activities. Because the solution is built on the Microsoft Power Platform, it fits naturally into existing Microsoft business environments without requiring disconnected third-party tools.
Instead of relying on handwritten notes or delayed data entry, users can capture information immediately at the point of interaction. That helps improve accuracy, reduce duplicate work, and create a more complete record inside CRM.

How Offline Functionality Supports Mobile Teams

One of the most valuable features of the Recorder App is its offline capability. Many field employees work in locations where internet access is limited or inconsistent, and traditional mobile applications often fail in those situations.
The Recorder App allows users to:

• Access CRM records while disconnected
• Capture and store audio recordings offline
• Update CRM data in the field
• Complete tasks without interruption
• Automatically sync changes when connectivity returns

This approach helps eliminate gaps in documentation and prevents information from being lost during service calls, inspections, or site visits. Teams can continue working naturally instead of waiting for a stable network connection before updating records.
For organizations with mobile workforces, offline functionality is often the difference between reliable field documentation and incomplete customer data.

Key Features That Improve Field Productivity

The Recorder App includes several features designed specifically for real-world field operations. Each feature supports faster documentation, better visibility, and more accurate CRM records.

Daily Recordings Dashboard

Users can view all recordings created throughout the day in a centralized dashboard. This makes it easier to replay recordings for quality review, training, or verification purposes.
Managers and team members can also use recordings to support peer coaching and ongoing employee development.

Emergency Recording Screen

Workflow interruptions can happen unexpectedly during field operations. The Emergency Recording Screen acts as a backup option that helps guarantee recording capture even when normal workflows are interrupted.
This additional layer of reliability is especially important in industries where documentation accuracy and compliance matter.

Recording Pairing Across Multiple CRM Records

The app allows a single recording to be associated with multiple related CRM records. Instead of creating duplicate recordings or manually updating several records separately, users can connect one recording to all relevant information.
That improves consistency while reducing unnecessary administrative work.

Multi-Record Viewing

While recording, users can view related CRM records such as agreements, account details, or customer information. This provides full context during interactions and helps employees make better on-site decisions.
Having access to connected information in real time reduces the need to switch between systems or revisit records later.

Direct CRM Editing

Users can update CRM records directly within the app, whether they are online or offline. This keeps customer information current and allows teams to document details immediately after conversations or inspections occur.
Capturing information in the moment typically results in more accurate data and fewer follow-up corrections.

Built-In Integration with Dynamics 365 CRM and Power Automate

The Recorder App was built to work directly within the Microsoft ecosystem. Audio recordings can be attached to contacts, cases, inspections, and other CRM records inside Dynamics 365 CRM, creating a complete and centralized customer history.
The app also supports workflow automation through Power Automate. Organizations can automatically route recordings and related files to platforms such as:

• SharePoint
• OneDrive
• Azure
• Other connected Microsoft services

This automation helps reduce manual handling while improving document organization and accessibility across teams.
In addition, integrated GPS navigation allows users to launch Apple Maps or Google Maps directly from CRM coordinates, making it easier to navigate to customer sites quickly and accurately.

How Different Industries Use the Recorder App

The flexibility of the Recorder App makes it useful across a wide range of industries that depend on mobile documentation and field data capture.

Field Services

Field technicians can record notes during service visits or repairs and sync them later when connectivity is available. This reduces paperwork and helps preserve important service details.

Healthcare

Healthcare organizations can securely document patient consultations and connect recordings directly to related records for improved documentation management.

Legal

Legal professionals can capture client conversations, case updates, and important discussions while maintaining quick access to CRM information.

Insurance

Insurance teams can create voice notes during onsite claims assessments, helping improve accuracy and time-stamped documentation.

Construction

Construction teams can log project updates, safety observations, and field reports tied to specific job sites and related records.
Across each of these industries, the combination of offline access, CRM integration, and workflow automation helps simplify field operations while improving record accuracy.

How OmniVue Uses Microsoft Power Platform to Build Business Applications

OmniVue helps organizations develop custom business applications using Microsoft Power Platform technologies. Solutions like the Recorder App are designed to integrate smoothly with existing Microsoft environments so organizations can improve workflows without introducing unnecessary complexity.
By combining low-code development with CRM integration, organizations can create tools that match the way their teams actually work in the field. This allows businesses to improve productivity, strengthen compliance efforts, and streamline data collection across devices and departments.
For companies already using Microsoft technologies, building custom Power Apps often provides a faster and more flexible way to solve operational challenges than relying on disconnected standalone applications.

FAQ About OmniVue’s Recorder App for Dynamics 365 CRM

Q: What does the Recorder App do in D365 CRM?

A: The Recorder App allows users to capture audio recordings, attach them to CRM records, and manage documentation directly inside Dynamics 365 CRM.

Q: Can the Recorder App work offline?

A: Yes. Users can access records, capture recordings, and update data offline. Changes automatically sync when connectivity returns.

Q: What industries can use the Recorder App?

A: The app supports industries including field services, healthcare, legal, insurance, and construction.

Q: How does the app integrate with Microsoft Power Platform?

A: The Recorder App is built with Microsoft Power Apps and supports automation through Power Automate.

Q: How does OmniVue support organizations using the Recorder App for D365 CRM?

A: OmniVue helps organizations design, customize, and deploy Power Platform applications that integrate with their Microsoft ecosystem and support real-world operational needs.

Final Thoughts

Organizations that rely on mobile teams need practical tools that support accurate documentation without slowing employees down. OmniVue’s Recorder App for D365 CRM combines audio capture, offline access, CRM integration, and workflow automation into a single solution built for real field conditions.
For businesses already using Microsoft technologies, integrating audio recording directly into Dynamics 365 CRM can improve visibility, reduce manual effort, and create more reliable customer records across the organization.
If your team is evaluating ways to improve field documentation or modernize mobile workflows, exploring custom solutions built with Microsoft Power Platform is a practical next step. OmniVue can help organizations identify opportunities, design the right approach, and build applications that align with day-to-day operations.
Contact our experts at OmniVue to learn more about the OmniVue Recorder App for D365 CRM.
By OmniVue, omnivue.net

The post Recorder App for D365 CRM Improves Mobile Audio Capture appeared first on ERP Software Blog.

Enterprise resource planning platforms have advanced by leaps and bounds in recent years, driven by developments in artificial intelligence and related technologies. Modern ERP solutions now support a broader range of business functions, from intelligent automation and predictive analysis to conversational interactions with enterprise data. Yet many organizations continue to rely on highly customized installations of legacy platforms such as Microsoft Dynamics GP, AX, and NAV.
These platforms have often served their organizations exceptionally well. However, changing business expectations, evolving technology landscapes, and new opportunities presented by AI-powered capabilities are encouraging leaders to re-examine their long-term ERP strategies. This article explores why organizations remain committed to legacy Dynamics systems, the long-term implications of delaying modernization, and how Microsoft Dynamics 365 can provide a practical foundation for future growth, innovation, and operational excellence.

Why Organizations Stay on Legacy Dynamics Systems

Many organizations hesitate to move away from Dynamics GP, AX, or NAV because of the substantial investments already made in custom configurations. These modifications often reflect years of operational knowledge and business-specific requirements. Finance teams may rely on tailored approval structures, manufacturing departments may depend on specialized inventory logic, and procurement divisions may operate around custom reporting frameworks that no longer exist in standard software packages. Rebuilding these functions within a modern ERP environment can appear financially daunting.
The decision to remain on a legacy platform is often influenced by several practical considerations:

• Years of custom workflows built around unique operational requirements
• Legacy integrations connecting ERP systems with finance, warehouse, procurement, or production applications
• Concerns regarding business disruption during migration activities
• Employee familiarity with existing interfaces and reporting processes
• Significant historical investment in custom development
• Uncertainty surrounding data migration, testing, and business continuity.

Deferring this migration creates an invisible fiscal drain on operational budgets; calculating the true cost of stagnation when migrating GP to Business Central saves money by highlighting how legacy licensing renewals outpace the cost of modern SaaS efficiencies.

The Growing Cost of Waiting

Delay tends to compound costs rather than avoid them. Legacy ERP systems grow more expensive to maintain as infrastructure ages, the pool of available specialists shrinks, and compatibility with modern applications deteriorates. Cybersecurity risks arise due to the discontinuation of official support. Organizations compensate through manual workarounds, duplicated data entry, and disconnected third-party tools. These costs rarely appear on a single budget line, which makes them deceptively easy to overlook.
Beyond direct costs, reduced adaptability becomes a measurable competitive problem. Competitors on modern cloud platforms can adjust pricing, supply chain operations, and forecasting far more quickly. A manufacturer requiring several days to consolidate production data is at a structural disadvantage against one producing near real-time insight. The question is no longer about maintaining older software. It is about preserving the organization’s capacity to remain commercially relevant.

What Modern Dynamics 365 Actually Offers

Not all transitions from legacy Dynamics platforms follow the same path, and understanding the distinction matters before any modernization project begins. The two principal routes are Dynamics AX to Dynamics 365 Finance and Operations, and Dynamics GP or NAV to Business Central. Each involves a different scope of change, different technical considerations, and a different commercial profile.

Dynamics AX to Finance and Operations (F&O)

AX and F&O share a common lineage, which tends to make this transition the more technically involved of the two. The underlying data model is familiar enough to encourage optimism, but sufficiently different to reward careful planning. Key considerations include:

• AX customizations written in X++ require assessment before migration; many can be retired in favor of standard F&O features or low-code extensions
• Executing a code-cleanse during this re-platforming phase prevents legacy technical debt from migrating to the cloud; partnering with a certified specialist for a structured AX to F&O migration allows engineering teams to map historical ledger structures to modern cloud standards cleanly.
• F&O is built for complex, multi-entity, multi-currency operations; organizations with simpler requirements may find it larger than they need
• The cloud-first architecture introduces continuous update cycles, replacing the periodic major upgrade model that AX users are accustomed to

Navigating these evergreen updates requires an accurate look at your ongoing architectural overhead; consulting our comprehensive Microsoft Dynamics 365 Finance and Operations (F&O) licensing and pricing guide helps project stakeholders map user-tier access levels against implementation roadmaps.

Dynamics GP or NAV to Business Central (BC)

Business Central is the natural landing point for organizations moving off GP or NAV. NAV users, in particular, will find the interface and data structures recognizable, though the gap between what existed and what is now standard is wider than it first appears. Relevant points for decision-makers:

• BC is a strong fit for small to mid-market organizations; those with complex manufacturing or multi-jurisdiction requirements may outgrow it sooner than anticipated
• GP customizations, often built using Dexterity or SQL modifications, do not carry across directly; a functional mapping exercise is necessary before any data migration begins
• Replacing these ancient database modifications with cloud-native configurations streamlines data flow; choosing an authorized path for a GP to Business Central migration ensures all standard financial histories move over without losing data integrity.
• BC’s AppSource ecosystem offers a broad range of third-party extensions, which can address functional gaps without the cost of custom development

Transitioning from monolithic code bases to modular architectures prevents future system locking; enforcing established Dynamics 365 customization best practices ensures that your new environment relies on low-code extensions rather than intrusive core modifications.
Both platforms share the broader Dynamics 365 ecosystem, which means access to Microsoft Copilot, Power BI, and AI Agents regardless of which route an organization takes. Employees can generate reports, analyse trends, and retrieve information through natural-language prompts. AI Agents monitor processes, identify exceptions, and support routine activities without constant oversight, freeing staff to focus on work that genuinely requires their judgment.

Reducing Migration Complexity

Migration is a legitimate concern for any organization carrying years of custom development. Structured frameworks such as QuickSwitch treat modernization as a phased transition rather than a disruptive all-or-nothing exercise. This methodology extracts data without requiring ground-up manual restructuring; deploying our automated QuickSwitch GP to BC framework accelerates extraction validation pipelines and maps charts of accounts into the cloud environment within minimized timelines. They identify which customizations remain genuinely valuable, which processes native Dynamics 365 already covers, and which legacy practices no longer serve a meaningful purpose. Organizations frequently discover that current platform features accommodate workflows that previously required costly custom development, substantially reducing migration complexity and future maintenance.

Selecting the Right Implementation Partner

ERP modernization frequently runs into difficulty when organizations attempt to replicate every historical customization without reconsidering whether those customizations remain justified. An experienced partner approaches the process with greater discipline, distinguishing genuine operational requirements from legacy habits preserved out of familiarity. Thoughtful implementation also addresses data governance, user adoption, and phased deployment, ensuring modernization improves operations rather than transferring old complications into a newer interface with brighter icons and a more expensive license.

How LevelShift Supports ERP Modernization

LevelShift supports organizations navigating this transition through Dynamics 365 solutions aligned with operational practicality and measurable business requirements. Services span Dynamics 365 Finance & Operations, Business Central, Customer Engagement, Copilot capabilities, and Microsoft Fabric integration. The approach prioritizes modernization strategies that preserve business continuity while reducing operational friction, with structured advisory support from initial assessment through to deployment.

Preparing for the Next Decade

Legacy ERP systems have supported countless businesses through years of growth and change, and they deserve recognition for the value they have delivered. The commercial environment surrounding them has, however, advanced considerably. Modern platforms function increasingly as decision-support environments connected to analytics, automation, and AI-assisted processes. Organizations that modernize thoughtfully are better positioned to respond to market changes and reduce long-term operational drag. The objective is neither to discard the past recklessly nor to preserve it out of habit. It is to build systems suited to the next decade rather than the previous one.

The post The Hidden Cost of ERP Customizations in Legacy Dynamics Systems appeared first on ERP Software Blog.

Every order delayed by manual entry slows down fulfilment, increases operational cost, and directly impacts customer satisfaction. For growing eCommerce businesses using Shopify alongside Microsoft Dynamics 365 Business Central, the wait is doubled for each sale, as is the occurrence of errors, mismatches in inventory and reconciliation hassles. 
Connecting these two platforms takes the manual intervention out of it, the flow of the orders between online store and ERP becomes simpler. This article walks through the automation process and the impact on both inventory and shipping speed as well as readiness factors for integration. 
What Is Shopify Business Central Integration 
Shopify ERP integration connects your Shopify store directly to Microsoft Dynamics 365 Business Central, which eliminates manual data entry and bridges the gap between your online sales channel and back-office operations.  
Instead of manually transferring order details from Shopify into Business Central, the integration automatically creates a sales order the moment checkout is completed. The moment a customer completes checkout, their order appears in Business Central as a sales order—complete with customer info, line items, shipping details, and payment status. 
Why Manual Order Processing Creates Problems 
To understand what integration fixes, it's helpful to see what breaks without it: 
Teams manually extract orders from Shopify, reformat the data, and enter it into Business Central. This process causes delays, mistakes and limits how orders you can handle each day. 
Here's what that looks like in practice: 

• Data entry errors: Typos in SKUs, quantities, or shipping addresses lead to wrong shipments and frustrated customers. 

• Inventory mismatches: The stock levels in Shopify don't match what's in the warehouse causing overselling or stockouts. 

• Delayed order processing: Orders wait until someone has time to enter them which delays shipping. 

• Reconciliation issues: Finance teams spend hours matching Shopify transactions to Business invoices at the end of the month. 

 
How Automated Order Syncing Works Between Shopify and Dynamics 365 Business Central 
The foundation of any Shopify Business Central integration is order sync. Here's exactly what goes on when a customer places an order: 
Order Capture and Transfer 
The moment a customer wraps up their checkout on Shopify, our integration picks up that order data and sends it over to Business Central. This usually happens quickly—think seconds or just a few minutes, though it can vary a bit depending on how you've set things up.  
When that order record arrives in Business Central, it's packed with all the crucial details your warehouse and finance teams will need. You'll get the customer's name and contact information, their billing and shipping addresses, along with a full breakdown of line items including SKUs and quantities. It also takes care of any discounts that were applied, tax calculations, and the current payment status. 
Customer Record Creation 
If your customer is new the integration can automatically create a new customer in Business Central based on their order. If they are a returning customer, the integration will match their order to their existing account record. This prevents the creation of multiple identical customer entries across your business. 
Sales Order Creation 
Once the data arrives in Business Central, it generates a sales order that's ready for fulfilment. Warehouse teams can access the order immediately without waiting for manual import or batch processing.  
This automation gets rid of the delay between when a customer places an order and when the order gets into your system, which affects how quickly you can pick, pack and ship the order. 
Real-Time Inventory Sync Across Shopify and Business Central 
Inventory accuracy is a problem for online stores that sell on multiple platforms. The Shopify Business Central integration helps solve this by syncing inventory in real time between both platforms. 
How Bidirectional Sync Prevents Overselling 
When a product sells on Shopify, the inventory count in Business Central is updated in real time. At the same time, when stock levels change in Business Central—for example, when new shipments arrive, returns are processed, or inventory is adjusted—those updates are reflected in Shopify 
This two-way flow means your Shopify storefront always reflects actual available inventory. Customers don't see "in stock" for items you've already sold out, and you don't have to manually reserve safety stock to compensate for sync delays. 
Multi-location Inventory Visibility 
If your business operates out of more than one warehouse, the integration can sync inventory by location. Shopify's multi-location functionality will work with your Business Central location tracking to accurately manage stock levels by individual warehouse. 
This visibility helps you route orders to the nearest warehouse, reduce shipping costs, and avoid situations where one location is overstocked while another runs dry. 

 
Faster Fulfilment Through Automated Shipping Updates 
Ecommerce is about speed. Customers expect fast shipping, and they expect to know where their order is at every step. Integration accelerates both. 
Shipping Details Flow Automatically 
When your warehouse team fulfills an order in Business Central and enters tracking information, the integration pushes that data back to Shopify. The customer receives their shipping notification without anyone manually copying tracking numbers between systems. 
This automation also updates the order status in Shopify, so your customer service team sees correct Fulfilment information when customers call or chat with questions. 
Reducing Fulfilment Cycle Time 
Integration reduces your order-to-ship cycle time by removing manual handoffs from Order receipt to Fulfilment. An order that took 24-48 hours to be entered and processed can now ship the same day. 
For businesses competing on delivery speed, this compression becomes a meaningful competitive advantage. 
Streamlined Financial Reconciliation and Reporting 
Finance teams often bear the hidden cost of disconnected systems. Reconciling Shopify sales with Business Central invoices, payments, and taxes can consume hours each week—especially during month-end close. 
Automatic Invoice and Payment Mapping 
With integration Business Central invoices directly link to Shopify orders. Payment details like transaction IDs and payment methods automatically go into your accounting records. 
This direct mapping removes the task of matching bank deposits to individual orders. Your finance team can close the books quicker. 
Tax Calculation Consistency 
Tax handling is another area where integration reduces friction. When tax rates calculated at checkout in Shopify flow into Business Central, you avoid discrepancies between what you charged the customer and what you recorded in your ERP. 
For businesses selling across multiple states or countries, this consistency simplifies compliance and audit preparation considerably. 
Handling Returns and Refunds Efficiently 
Returns are a fact of eCommerce life. How you handle them operationally determines whether they're a minor inconvenience or a major drain on resources. 
Return Data Synchronization 
When a customer wants to return something in Shopify, the system can automatically create a return order or credit note in Business Central. This keeps your records correct and makes sure your inventory is updated properly. 
Returned items can be routed back to available stock or flagged for inspection, depending on your business rules. The key is that this happens systematically, not through ad-hoc manual processes that someone might forget. 
Refund Tracking 
Refund transactions sync between platforms, so your finance team has a complete picture of money out as well as money in. This visibility is essential for accurate cash flow reporting and customer account management. 
Native Connector vs Third-Party Integration Platforms 
Microsoft offers a native Shopify connector for Business Central, which handles basic synchronization scenarios. However, many businesses find they outgrow what the native connector provides. 
When the Native Connector Works 
The built-in connector is a reasonable starting point for businesses with straightforward requirements: a single Shopify store, a standard product catalog, and basic order flow. It's included with Business Central, so there's no additional licensing cost to get started. 
When You Need More 
Businesses with complex requirements often run into limitations with the native connector quickly. Some common scenarios that need a better integration platform are: 

• Multiple Shopify stores syncing to a single Business Central instance 

• B2B pricing and customer-specific catalogs that reflect ERP pricing rules 

• Custom fields and attributes that don't map cleanly between platforms 

• High order volumes requiring sophisticated error handling and retry logic 

• Multi-currency and multi-company configurations 

 
Third-party integration platforms, like i95Dev Connect offer the flexibility to handle these scenarios and still give you the automation benefits of integration. 
Implementation Considerations for a Successful Integration 
Integration projects succeed or fail based on preparation. A few key considerations can make the difference between a smooth rollout and a frustrating one. 
1) Data Mapping and Field Alignment 
Shopify and Business Central do not use the way of organizing data. You have to make sure that things like SKUs, customer information, tax codes and payment methods matchup between the two systems. If you take the time to figure this out at the beginning, you will avoid a lot of problems on. 
2) Error Handling and Monitoring 
No integration runs perfectly 100% of the time. Sometimes the network will have problems, or the data will not be valid or something unusual will happen. Your integration needs to be able to log problems send alerts and try again so that issues can be caught and fixed quickly before your customers even notice. 
3) Testing with Real Scenarios 
Test your integration with actual order data, not just sample records. Include edge cases: orders with discounts, orders with multiple shipping addresses, orders with backordered items. The goal is to find problems before your customers do. 
4) Change Management 
Your team needs to understand the way of doing things. The people, in the warehouse the customer service people and the finance team all use order data in ways. If you train them and give them documentation, they will be able to adapt to the new integrated process without getting confused. 
Choosing the Right Integration Partner 
Selecting an integration solution is both a technology and partnership decision. You need a provider who understands Shopify and Microsoft Dynamics 365 Business Central deeply and can support you throughout implementation and beyond. 
Look for partners with proven experience in Shopify and Microsoft Dynamics 365 Business Central, pre-built connectors that reduce implementation time compared to custom development, a flexible architecture that accommodates your unique business requirements. 
At i95Dev, we’ve helped hundreds of businesses integrate Shopify with Microsoft Dynamics 365 Business Central and other ERP systems. Our i95Dev Connect platform is purpose-built for Shopify–Business Central integration scenarios, offering the reliability of a productized solution with the flexibility to handle complex requirements. 

The post How Shopify and Business Central Integration Streamlines Order Management appeared first on ERP Software Blog.

Organizations that operate across multiple entities face significant challenges when it comes to managing complex financial structures, reconciling intercompany transactions, and ensuring data consistency across various business units. These challenges become even more pronounced as companies grow and expand, requiring them to manage operations across different regions, subsidiaries, and legal entities. 
Traditional ERP systems often struggle to handle the complexity of these environments, leading to errors, inefficiencies, and delays in financial reporting. However, with the integration of Agentic AI into multi-entity ERP environments, organizations can automate and streamline these processes, ensuring consistency and control across complex structures. 
In this blog, we’ll explore how Agentic AI simplifies multi-entity operations by automating intercompany reconciliations, standardizing processes, and ensuring data consistency. We’ll also look at how Dynamics 365, combined with Agentic AI, provides the intelligence and automation needed to manage multi-entity ERP environments effectively. 
 
The Challenges of Multi-Entity ERP Environments 

1. Complex Financial Structures

Organizations with multiple entities often have to deal with intricate financial structures, including: 

• Multiple currencies 

• Diverse accounting practices 

• Complex tax regulations 

These structures make it difficult to maintain accurate and consistent financial reporting across the organization. As entities grow, so does the complexity of financial consolidations and tax reporting. 

1. Intercompany Transactions

Another significant challenge in multi-entity ERP environments is managing intercompany transactions. These transactions occur between different entities within the same organization, such as: 

• Sales of goods between subsidiaries 

• Transfer pricing for tax purposes 

• Intercompany loans and settlements 

Tracking and reconciling these transactions manually can be time-consuming and error-prone, especially when entities operate in different regions or currencies. 

1. Data Inconsistencies

As data is generated across different entities, ensuring data consistency becomes a significant challenge. Inconsistent data between entities can lead to: 

• Incorrect financial reporting 

• Delayed decision-making 

• Compliance issues 

Without real-time data synchronization, organizations struggle to maintain a single source of truth across multiple entities. 
 
How Agentic AI Simplifies Multi-Entity ERP Operations 
Agentic AI addresses these challenges by automating and optimizing key processes, ensuring consistency and control across different entities. Here’s how Agentic AI simplifies multi-entity ERP environments: 

1. Automating Intercompany Reconciliations

One of the most time-consuming tasks in a multi-entity environment is intercompany reconciliation. Traditionally, reconciliation involves manually matching transactions between entities, which is prone to errors and delays. 
Agentic AI automates this process by: 

• Automatically identifying intercompany transactions across entities 

• Matching records to ensure that transactions are recorded correctly 

• Reconciling discrepancies by flagging mismatches and suggesting corrective actions 

With AI-powered reconciliation, businesses can significantly reduce the time spent on manual processes and ensure that intercompany transactions are always aligned, accurate, and compliant. 

1. Standardizing Processes Across Entities

In multi-entity environments, each entity may have different processes, accounting rules, or data structures. This lack of standardization can lead to inefficiencies, errors, and compliance issues. 
Agentic AI helps standardize business processes across all entities by: 

• Automating workflows: AI can ensure that processes such as order processing, invoicing, and inventory management are standardized across entities, reducing the need for manual intervention and ensuring consistency. 

• Enforcing consistency in data: AI ensures that data formats, reporting structures, and tax treatments are standardized across the organization, making it easier to consolidate financial data and ensure compliance. 

By standardizing processes, Agentic AI enables smoother operations and greater consistency across all entities, ensuring that everyone is following the same rules and procedures. 

1. Ensuring Data Consistency

Data consistency is one of the most critical aspects of managing multi-entity ERP environments. Inconsistent data can lead to inaccurate reporting, compliance issues, and operational inefficiencies. 
Agentic AI ensures data consistency by: 

• Monitoring cross-entity data in real-time to ensure it is accurate and up-to-date 

• Flagging discrepancies in data between entities, such as mismatched product codes, pricing inconsistencies, or incorrect financial figures 

• Executing automatic corrections based on predefined rules, ensuring that data is consistent across the entire organization 

By leveraging AI for data consistency, businesses can maintain accurate and reliable data that can be used to make better-informed decisions. 
 
How Agentic AI in Dynamics 365 Works 
Dynamics 365, when combined with Agentic AI, provides a powerful platform for managing multi-entity operations. Here’s how the integration works: 

1. AI Agents Monitor Cross-Entity Transactions

AI agents within Dynamics 365 continuously monitor transactions between different entities, ensuring that all intercompany activities are tracked and reconciled in real-time. By analyzing transaction data as it’s generated, AI can quickly identify mismatches and discrepancies, automating the reconciliation process and minimizing errors. 

1. Detecting Discrepancies

When discrepancies are detected—whether it’s in financial data, inventory records, or customer orders—Agentic AI immediately flags them for review. The AI can: 

• Highlight inconsistencies in currency conversions 

• Identify missing transactions or duplicate records 

• Provide actionable insights on how to resolve the discrepancies 

By detecting issues early, AI ensures that problems are addressed proactively, reducing the risk of costly errors. 

1. Executing Corrections Automatically

Once discrepancies are identified, Agentic AI can take corrective actions automatically based on predefined rules. This can include: 

• Adjusting records to match intercompany transactions 

• Re-calculating financials to align with standardized processes 

• Generating audit logs for compliance purposes 

This level of automation ensures that the business is always operating with accurate and consistent data, without the need for manual intervention. 
 
At DAX Software Solutions: Building Multi-Entity ERP Architectures with Agentic AI 
At DAX Software Solutions, we specialize in helping organizations design and implement multi-entity ERP architectures that leverage the power of Agentic AI. Our approach ensures that businesses can: 

• Automate intercompany reconciliations to reduce manual work and improve accuracy 

• Standardize processes across entities to streamline operations and improve efficiency 

• Ensure data consistency across all systems, enabling better decision-making and compliance 

By combining Dynamics 365, Agentic AI, and integration platforms like Aonflow, we help businesses build scalable, AI-powered ERP systems that improve control, reduce complexity, and drive growth. 
 Conclusion 
Managing operations across multiple entities can be complex, especially when dealing with intercompany transactions, data inconsistencies, and complex financial structures. However, with Agentic AI, businesses can simplify these challenges by automating processes, standardizing operations, and ensuring real-time data consistency across all entities. 
At DAX Software Solutions, we help organizations leverage Agentic AI in Dynamics 365 to streamline multi-entity ERP environments, ensuring that AI delivers real business value. By integrating AI into your ERP system, you can transform complex organizational structures into efficient, proactive, and intelligent operations. 
Because scale should not introduce complexity—it should be managed intelligently. 
Contact us: https://daxsws.com/contact-us 

The post The Role of AI in Multi-Entity ERP Environments  appeared first on ERP Software Blog.

TL;DR: Integrating supplier portals with Dynamics 365 eliminates manual data entry, reduces errors, and speeds up processes like purchase orders, invoices, and supplier onboarding. This allows teams to automate purchase order tracking and manage by exception. By automating workflows and syncing data in real-time or near-real-time, procurement teams can save costs and improve efficiency.
<!, more, >
If your procurement team relies on SSRS reports for supplier portal visibility, you're already behind. Custom reports tie up IT resources, go stale between refreshes, and miss real-time data. Dynamics 365 has the raw data—PO confirmations, invoice arrivals, receipt records—but without the right integration, you're stuck exporting to Excel and waiting for IT to build your next report.
D365 captures the transactional data your procurement team needs: line items, quantities, delivery dates, invoice flags. But presenting that data in real time without custom SSRS or Power BI dependencies requires integrating your supplier portal directly with your ERP. Modern integration platforms read D365 data via native APIs, auto-sync supplier submissions, and compute KPIs automatically—no code changes to your ERP configuration required. This transforms your integration from basic functionality to strategic visibility: suppliers self-onboard, POs auto-transmit, invoices land with receipts already matched.

Planning Your Integration Strategy

Defining Business and Technical Goals

Before diving into coding, it's essential to set clear and specific integration goals. Broad objectives like "improve efficiency" won't help when you're faced with tough decisions during implementation.
On the business side, focus on measurable outcomes. For example, aim to reduce invoice rejection rates by targeting a first-time submission success rate of over 95%. Manual processes, like portal management, often drop success rates below 50% because of formatting errors. Other key goals might include shortening the PO-to-payment cycle and giving finance teams real-time visibility into invoice approvals.
On the technical side, clarity is just as critical. Start by identifying the source of truth for each type of data. For instance, your onboarding portal might own the W-9 PDF, while your ERP system manages the Vendor ID. Oracle's integration methodology offers a smart approach:

"Avoid moving data in both directions unless necessary. Always create data first on the identified source of truth and connect it with other systems."

You'll also need to define how frequently data should sync. For example, punch-out catalog pricing often requires real-time updates, while PO transmissions can usually handle near-real-time syncing. Vendor master updates, on the other hand, are often processed in nightly batches.
Once your goals are in place, document your current systems and data flows. This will help you pinpoint potential integration challenges.

Mapping Existing Systems and Data Flows

With your goals defined, the next step is mapping out all your systems and current data flows. This includes your ERP, supplier portal, and any middleware you use.
Pay close attention to field-level mappings. For instance, ensure that a supplier's "Tax ID" in the portal matches the corresponding ERP field, with proper formatting and validation. Payment terms codes often vary between systems and may require custom lookup tables. Similarly, Unit of Measure (UOM) codes can differ - your portal might use "BOX" while your ERP uses "BX." Incorrect mappings like these can cause downstream issues, such as 3-way match failures.
Syncing master data is crucial before starting transactional workflows. One common problem is invoices or POs arriving before the vendor record exists in the ERP, which can lead to payment blocks and reconciliation headaches. Additionally, plan for potential failure points, like punch-out session timeouts or invoices arriving before a goods receipt is posted.
Once you've mapped your data flows, you can prioritize which workflows to integrate first.

Prioritizing Use Cases and Integration Scope

Take an incremental approach to integration by prioritizing use cases based on their impact and complexity.
If you manage 50 or more suppliers across procurement portals, full automation is likely worth considering. For most teams, starting with PO transmission - automating order delivery to suppliers via cXML - is a practical first step. After that, adding an invoice flip (where suppliers convert POs directly into invoices) can significantly reduce 3-way match failures and speed up payment cycles.
Here's a comparison of different integration scopes:

Keep in mind that cXML is designed for transactional documents only. Vendor master data requires separate REST or SOAP APIs. Being aware of this distinction upfront can help you avoid scope creep and unexpected issues during the project.

sbb-itb-b077dd9

Building the Integration Framework

Standardizing Data Models and Mappings

To ensure smooth integration between your supplier portal and ERP system, it's crucial to standardize key entities like suppliers, purchase orders, and invoices.
One important step is separating the supplier profile (used for sourcing and risk management) from the pay-enabled vendor profile (used for payments and tax purposes). This distinction allows procurement teams to focus on supplier management tasks without interfering with the payment-critical data maintained by finance teams. A staged approach to data collection works best: start with essential registration details like legal name and Tax ID/EIN, then move to qualification data such as certifications and compliance documents. Finally, request banking or remit-to information only when the supplier is ready for payment.
Document field-level mapping differences thoroughly. For instance, SAP limits supplier names to 35 characters, while Oracle allows up to 360. Clearly outline all transformation rules, such as converting state codes (e.g., "CA" to "California"). Similarly, ensure unit of measure conversions follow predefined standards.

"A report by Gartner estimated that companies that have automated onboarding solutions may reduce data entry errors by 50%." - Zenwork

For US-based integrations, your data model should support formats like the 9-digit EIN and DUNS numbers required for Ariba Network registration. When parsing currency values from cXML Money elements, always treat them as decimals rather than floats to avoid rounding errors in financial calculations.
Once your data models are standardized, the next step is determining the best interfaces for seamless data exchange.

Defining Interfaces and Integration Methods

The right interface depends on your data volume, speed requirements, and system capabilities.
For transactional documents like purchase orders, invoices, and punch-out catalog requests, cXML is the go-to protocol. REST APIs, on the other hand, are better suited for supplier master data and sourcing events due to their speed and lightweight nature compared to SOAP protocols. For bulk data imports, SFTP/CSV batch processing offers simplicity and reliability.

When deciding between polling and webhooks, consider performance needs. Polling involves checking for updates at regular intervals, which can waste API quota and cause delays. Webhooks, by contrast, trigger data flows immediately when an event occurs (e.g., "Supplier Created"), making them faster and more efficient. For platforms like Coupa, which may limit API requests to 50 per minute, event-driven webhooks are particularly useful.
Before transmitting outbound cXML documents, validate them against the official Document Type Definition (DTD). Skipping this step could result in "406 Not Acceptable" errors during production.

Ensuring Security and Compliance

Securing your integrations is non-negotiable, especially when dealing with sensitive financial data.
Use OAuth 2.0 with scoped tokens for API calls, and store credentials securely in a secrets manager instead of version control. For cXML SharedSecrets, which many SRM platforms don't support rotating automatically, set up a quarterly manual rotation schedule.
Adopt additional best practices like enforcing UTF-8 encoding for all XML payloads to avoid character corruption. Never transmit sensitive information such as bank account numbers through standard cXML. Instead, use a separate, encrypted channel for this data. If your integration involves Oracle Identity Cloud, handle HTTP 429 (Too Many Requests) errors with exponential backoff logic to maintain stability.
For teams operating under Sarbanes-Oxley (SOX) requirements, implement strict access controls and maintain a detailed audit trail of every synchronization event. Tools like Leverage AI can help by offering real-time insights into supplier data flows and automating purchase order management within your ERP system. This ensures data accuracy without the need for manual intervention.

Implementing and Testing the Integration

Preparing Systems and Environments

Before diving into the coding phase, it's crucial to set up separate sandbox and production environments. These should each have their own credentials and endpoints to avoid any mix-ups. Using the wrong environment - like accidentally running a test transaction on a live ERP system - can lead to serious issues, such as corrupting vendor data or unintentionally generating real purchase orders.
Start by registering on your selected SRM platform (e.g., Ariba Network, Coupa, or Jaggaer) and exchanging authentication credentials. Platforms typically use cXML SharedSecrets or OAuth 2.0 client credentials, and you'll need to configure these separately for each environment. On the network side, make sure to open the required ports and add integration endpoints to your allow lists. Assign integration user roles based on the Principle of Least Privilege, ensuring users only have the permissions necessary to perform essential CRUD operations on relevant business objects.
Additionally, confirm which system will act as the source of truth for each data entity, as this ensures consistency across platforms.

Developing Core Integration Workflows

Once the environments are ready, focus on building out key workflows. Prioritize the following processes: purchase order transmission, order confirmation, advance ship notice (ASN), and invoice processing. These workflows form the backbone of the procure-to-pay cycle and have the highest integration value.
Accuracy is critical when handling data for these workflows. For example, when processing cXML Money elements, always parse currency values as decimals instead of floats to avoid rounding errors in financial calculations. Also, ensure decimal precision is consistent across systems. While cXML supports up to 4 decimal places, some ERPs, like SAP, only allow 3. A mismatch here could silently cause errors in line-item totals. Additionally, keep cXML document sizes under 5 MB to comply with Ariba Network limits. If a purchase order exceeds this size, break it into multiple documents.
To prevent duplicate transactions during retries, assign unique payloadID values as idempotency keys for each outbound document.
Once these core workflows are developed, proceed to methodical testing.

Conducting Structured Testing

After building the workflows, rigorous testing ensures everything functions as intended. Testing should follow a structured progression: connectivity → unit → end-to-end → load. Start with simple tasks like sending a cXML ProfileRequest or using a curl command to verify credentials and connectivity. Then, test individual workflows using tools like Postman for REST APIs or SOAP UI for SOAP endpoints.
Once basic connectivity and unit tests pass, move on to end-to-end testing. This involves executing the entire document lifecycle, including punch-out catalog browsing, purchase order transmission, order confirmation, ASN, and invoice flip. Pay close attention to the 3-way match process, ensuring the portal-generated invoice aligns with the ERP's purchase order and goods receipt within the acceptable tolerances. Don't skip testing failure scenarios, like how the system reacts when the ERP is unavailable during maintenance. For example, the Ariba Network queues documents and retries delivery for up to 72 hours if a supplier's endpoint is down, but your ERP logic must handle these delayed deliveries without issues.

"Verify that the integration handles expected failures, errors, and invalid data as expected." - Oracle

Before launching in production, conduct a smoke test with a single transaction. This step helps catch any last-minute connectivity or credential issues before handling the full transaction load.

"Do a smoke test for a single transaction before sending the entire load to production." - Oracle

Once the smoke test is successful, you can move closer to deployment.

Deploying and Improving the Integration

Running a Pilot with Selected Suppliers

After your smoke test confirms the integration works, resist the urge to roll it out to all suppliers at once. A staggered approach minimizes risk. Start small: test with a handful of non-production vendors, then move to a limited group of new suppliers before expanding further.
When choosing pilot participants, focus on high-volume and critical suppliers. These are the partnerships where integration issues can cause the most disruption, but also where early successes can provide the greatest impact. For each supplier in the pilot, test the entire workflow - purchase orders, invoice submissions, and payment verifications.
The onboarding process should follow these four steps: invitation, registration, user setup, and transaction testing. Don't overwhelm suppliers by asking for too much information upfront. Begin with the basics needed for registration, and collect banking and tax details only when the supplier is ready to receive payments.
Once the pilot is successful, move forward with full deployment, supported by a structured change management plan.

Full Deployment and Change Management

Rolling out the integration to all suppliers involves more than just technical readiness. Supplier adoption is often the biggest hurdle - nearly 60% of procurement teams say managing supplier data during onboarding is their top challenge.
Using the lessons learned from your pilot, prepare for a phased rollout. Group suppliers into manageable waves and provide clear communication. Include invoicing instructions and portal guidance directly on purchase orders and portal messages - don't expect suppliers to search for documentation on their own. Internally, train your procurement and accounts payable teams ahead of the launch. A tiered support model can help, with Tier 1 addressing basic navigation questions and Tier 2 handling exceptions and more complex issues.
Establish clear ownership of data fields across systems. The supplier portal should manage vendor-entered data like W-9 forms and banking details, while the ERP system retains control of the permanent Vendor ID. Ensure the ERP pushes this Vendor ID back to the portal for reconciliation. To maintain data integrity, prevent direct edits to vendor information within the ERP.

"If suppliers cannot onboard and transact digitally without repeated helpdesk support, adoption will stall." - Umbrex Source to Pay Playbook

Tracking Performance and Making Improvements

After full deployment, ongoing monitoring is key to keeping the integration efficient and effective. Run daily reports to identify integration failures, and perform reconciliations between the portal and ERP to catch synchronization issues early.
Track essential metrics to measure success:

For failed messages, implement a dead letter queue (DLQ) to ensure no transaction is lost. Route these to human review after multiple retries.
Tools like Leverage AI can simplify this process by automating supplier follow-ups and providing real-time insights. By layering AI-driven automation on top of your ERP integration, you can track supplier performance without manual effort. As your system evolves, this level of automation transforms your integration from basic functionality to a more strategic advantage.

Making Supplier Portal & Supplier Self Service Work in an SAP Landscape

Conclusion

Connecting your supplier portal with your Dynamics 365 system can lead to faster processes, more accurate data, and better supplier relationships. The supplier portal market is on a strong growth trajectory, expected to rise from $11.4 billion in 2026 to $25 billion by 2032, with a 14% compound annual growth rate (CAGR).
The integration process can be broken down into clear steps: defining objectives, mapping data flows, choosing the right integration method, thorough testing, and phased deployment. This structured approach ensures success. For example, companies using automated onboarding tools have seen a 50% drop in data entry errors, while integrated B2B commerce flows have been linked to a 20% revenue boost from both new and existing customers.

"Integration is the technical foundation that turns a standalone vendor onboarding process into a strategic, automated business workflow." - Mohammed Kafil, Founder and CEO, Zapro.ai

This integration serves as the backbone of a more efficient procurement process.
Real-time data visibility adds even more value. By uniting your Dynamics 365, supplier portal, and procurement workflows, you can minimize discrepancies and speed up decision-making. Automation tools like Leverage AI take this further by automating supplier follow-ups, monitoring performance, and identifying delays before they escalate into larger issues.
The result? A procurement operation with fewer errors, smoother processes, and improved confidence across the procure-to-pay cycle. This integrated strategy can turn procurement into a powerful strategic advantage.

FAQs

What should be the source of truth for supplier data?

A centralized, integrated system is essential for maintaining accurate and up-to-date supplier data. Most organizations rely on an ERP system or a procurement platform to act as the main repository for this information. This setup ensures data consistency and reliability across the board. By centralizing supplier data, companies can eliminate silos, minimize manual errors, and create a single, dependable reference point for all supplier-related processes.

Should I use cXML or APIs for my integration?

When deciding between cXML and APIs, it all comes down to your specific requirements and the systems you're working with.
cXML works best for handling transactional documents - think purchase orders or invoices. It's particularly useful for businesses using platforms like Ariba or Coupa. On the other hand, APIs, such as REST APIs, shine when you need more flexibility. They're ideal for tasks like supplier onboarding or other broader data exchanges.
In many cases, integrations mix both approaches. Middleware often steps in to translate between protocols and keep data flowing smoothly between systems.

How do I prevent duplicate POs or invoices during retries?

To prevent duplicate purchase orders (POs) or invoices during retries, leverage idempotency keys for each transaction. These keys should be stored alongside timestamps, allowing you to verify them before processing any new requests. For webhooks, promptly acknowledge receipt and validate signatures to ensure authenticity. On top of that, establish system controls, such as duplicate checks based on key fields like vendor, invoice number, date, and amount. This ensures that retries won't result in duplicate entries.

The post Integrate Supplier Portals with Dynamics 365 Without Custom SSRS appeared first on ERP Software Blog.

Physical inventory counts in Business Central often stall because the native tools weren't built for operations with multiple count teams, complex bin setups, or items tracked by lot and serial number. Coordinating paper sheets, chasing down uncounted items, and manually reconciling discrepancies can stretch a count across days that should take hours.
Date & Time: June 10, 2026 | 1:00 pm EDT (North America)
Register: https://dmsiworks.com/events/inventory-counting-business-central
This webinar walks through how Advanced Inventory Count extends Business Central to handle the full count process, from configuring flexible count sheets and enabling simultaneous multi-user entry to running reconciliation reports and posting adjustments with confidence.
What You'll Learn

• Automate data collection by integrating barcode scanning with count sheets
• Configure count sheets grouped by location, bin, shelf, or item criteria
• Enable multiple users to enter count data simultaneously across sheets
• Identify uncounted items before and after a count to avoid posting gaps
• Reconcile lot and serial number discrepancies automatically
• Use the Count Difference Analysis report to locate and resolve count errors
• Validate journal entries before posting to catch blocking issues early

Register to join us live for a walkthrough you can apply directly to your next count cycle. Can't attend live? Register anyway, and we'll send you the recording.

The post Counting Inventory in Business Central: Faster Counts, Fewer Errors appeared first on ERP Software Blog.

If you run Microsoft Dynamics 365 Business Central, you probably have more reporting options than you really wanted in the first place. Standard BC reports, account schedules, Excel exports, Jet or Solver, Power BI dashboards. On paper, it looks like plenty. In practice, most teams only notice the gaps when things get stressful: close week, board packs, acquisitions, or the first serious conversation about Copilot and AI. 
Here’s the real test: can your reporting stack handle multi-entity consolidations, dimensional analysis, and high-stakes, time-sensitive work—without devolving into a mess of exports and last-minute fixes? That’s when most teams realize their setup isn’t as scalable or AI-ready as they thought. 
In this post, you’ll get: 

• A breakdown of the main reporting paths BC customers use today 
• Where each approach works—and where it breaks down 
• A simple way to pressure-test your next reporting move (without getting lost in feature grids or demo hype) 

Ready to find out which tools are actually built for the AI era? Let’s dive in. 

The five paths Business Central customers use today 

Most Business Central teams are not starting from a blank slate. They already have some mix of native reports, spreadsheets, third‑party tools, and Power BI. But does that patchwork still fit now that reporting complexity, cloud expectations, and AI ambitions are all climbing at the same time? 

Native Business Central reports and account schedules 

Native reporting is where almost everyone starts. It’s already there, finance knows it, and for straightforward financials—basic P&Ls, balance sheets, trial balances—it gets you through the day. 
But as soon as you add real-world complexity—multiple entities, years of history, extra dimensions for projects or departments—native reporting starts to feel rigid. The moment an exec asks, “Show me this by region and product line across all companies,” your team quietly heads back to Excel. If you’re seeing this pattern, it’s a clear sign the built-in layer isn’t enough. 

Excel exports and hand-built spreadsheets 

No honest Business Central reporting conversation can skip Excel. Controllers, finance managers, and ops leaders still live there because it’s fast, familiar, and you can model almost anything if you’re willing to wrestle with formulas for long enough. When someone needs an answer today, exporting and reshaping in Excel often feels like the shortest path. 
And it works—until it doesn’t. Ever seen a workbook with 47 tabs, each with its own version of “final” in the file name? When your business depends on these artifacts, manual refreshes, and formulas only one person understands, reporting gets fragile. Things slow down, trust erodes, and version-control fights break out—usually right when you need answers most. 

Jet, Solver, and other legacy reporting tools 

Jet, Solver, and similar tools still have a real footprint in Business Central shops—especially if you’ve got a long Dynamics history or a deep Excel culture. They can deliver solid financial and operational reporting, and plenty of teams have built critical processes around them. 
But as cloud strategies mature, these tools start to show their age. Performance lags with big data volumes or lots of entities, upgrades turn into projects, and you end up relying on a handful of internal experts to keep things running. Instead of being the platform you build on, they become something you manage around while you try to modernize the rest of your stack. 

Power BI for Business Central 

Power BI shines at what it was built for: interactive dashboards, trend analysis, and executive-level visibility. Most Business Central customers already use it, and it fits right into the Microsoft ecosystem. If you want shared performance views, drill-downs, and KPIs on big screens, Power BI is a strong fit. 
But here’s where frustration creeps in: pixel-perfect financial statements, highly formatted reports, and Excel-centric workflows aren’t Power BI’s strong suit. If every team spins up its own dataset and logic, you get impressive demos but a governance headache—margin, backlog, or “customer” end up defined three different ways in three different places. 

Cloud‑native, BC‑only reporting platforms 

That brings us to the newer camp: cloud‑native reporting platforms built only for Business Central. These usually show up when you’re stuck between Excel exports, aging point solutions, and BI projects that always seem to be ‘almost there’ but never quite land. 
The key difference? Fit. Generic BI platforms are powerful, but they demand more modelling, more technical skill, and more internal ownership than most mid-market teams can spare. A BC-specific reporting solution, built for your data and workflows, cuts out that overhead. Finance and ops get a direct path to governed, self-service reporting—no mini data engineering team required. 

What “AI‑ready” actually means in Business Central 

AI-ready reporting in Business Central isn’t about prompts or flashy Copilot demos. It starts with one question: is your data and reporting logic structured enough to be trusted, reused, and explained—without drama? 
In plain terms, AI-ready means your data is governed, your key metrics—revenue, margin, on-time delivery, backlog—are defined the same way everywhere, and performance is strong enough that users aren’t working around delays. Underneath it all, you need a clean reporting model that AI can query without inheriting a decade of shortcuts and exceptions. 
Here’s where most businesses stumble: they assume adding AI on top of messy reporting will magically fix things. It won’t. AI amplifies whatever you feed it. If your margin logic changes from report to report, or every department defines “backlog” differently, AI just makes bad reporting faster (but more convincing—it’s up to you if that’s a net positive or not). 
That’s why true AI-readiness is about architecture over features. If your reporting foundation is weak, the AI on top will be weak too—no matter how slick the demo looked. 

How to compare Business Central reporting tools 

When you’re comparing native BC reporting to third-party tools, skip the endless feature matrix. Focus on a few practical criteria—and see how each option holds up under pressure. 

Performance and scalability 

Ask yourself: can this tool handle big data volumes, multiple entities, years of history, and lots of users at once? That’s where native reporting, spreadsheet-heavy processes, and older tools usually start to drag. Cloud-native platforms—especially those running governed queries in Azure—tend to hold up better as you grow. 

Excel experience 

Most BC customers aren’t trying to ditch Excel—they just want to make it safer. The real question isn’t “Does it work with Excel?” but “Does it give you a governed Excel experience without turning every workbook into its own reporting system?” The right tools let you keep Excel as a front end, while shifting logic and data into a controlled back end. 

Governance and consistency 

If finance, ops, and leadership all pull different numbers for the same KPI, you don’t have a dashboard problem—you have a reporting-layer problem. Strong BC reporting tools let you define logic once, reuse it everywhere, and cut down on metric drift. 

Implementation speed and risk 

Nobody wants a reporting project that feels like a second ERP rollout. Look for tools with prebuilt BC structure, BC-specific content, and a fast path to usable reports—without needing scarce internal developers for every tweak. 

AI‑readiness 

And if you want Copilot or AI-driven analysis soon, ask: does this tool move you closer or farther away? Tools that rely on exports, one-off models, or undocumented logic just create more cleanup later. Tools that build a governed, reusable reporting layer give AI something solid to stand on. 

Where a BC‑only, cloud‑native platform fits 

This is where a platform like Cosmos fits. It’s not here to replace every tool you already have—it’s designed to fill the gap most BC customers eventually hit. You need something more robust than exports and disconnected reports, but more business-friendly than a full custom BI project. 
Cosmos is built only for Dynamics 365 Business Central and is designed as a born‑in‑the‑cloud reporting and analytics platform. That matters because it doesn’t ask users to start from raw BC tables or design a model from scratch. It comes with a prebuilt Business Central data model and more than 30 prebuilt reports, which shortens time to value and lowers implementation risk. 
Just as important, it keeps Excel in the mix. You can design and run reports in Excel, but those reports hit a governed, Azure-based BC data model—not raw exports or fragile workbook logic. That combo—a familiar Excel front end with a governed cloud back end—is exactly why BC-only, cloud-native tools are getting so much attention. 
If you’re stuck between standard BC reports and a bigger BI ambition, this kind of platform is often the missing step. Once your reporting layer is consistent, fast, and governed, Power BI gets easier to manage—and AI scenarios start to look credible, not risky. 

How to pressure‑test reporting tools in a demo 

A strong demo shouldn’t just be a tour of pretty visuals—it should feel like a real working session. When you’re comparing BC reporting tools, bring tests that mirror the pressure your team actually feels. 
Try things like: 

• Run a multi‑company P&L with several years of history and watch how long it takes. 
• Ask a non‑technical user to make a live change to a report in Excel during the demo. 
• Change a KPI definition—gross margin, on‑time delivery—and see how quickly and broadly the change carries through. 
• Ask how the governed reporting model (if it exists) supports Power BI and future AI use cases. 
• Simulate close week: run several reports at once and see what happens to performance. 

These questions reveal more than missing features. They show whether the tool is actually built for how you work in BC—not just for how the vendor likes to demo it. 

Choosing the right next step 

The goal isn’t to rip out every reporting tool you’ve collected over the years. It’s to figure out which ones still fit, which ones are causing friction, and what kind of foundation you need if you want AI to actually be useful—not just impressive. 
For some teams, the right move is to keep Power BI for dashboards but shore up the reporting layer underneath. For others, it’s about reducing Excel sprawl or cutting dependence on legacy tools that don’t fit a cloud-first strategy. In most mid-market shops, the smartest next step won't be a bigger BI project or a rushed AI rollout—it’s building a better reporting layer first, then adding AI on top of something you already trust.

The post Business Central Reporting Tools: Which Ones Are Actually Ready for AI? appeared first on ERP Software Blog.

The struggle when organizations underestimate how much preparation on the client side matters before a project ever kicks off. Having the right partner, methodology, and technology is important, without a doubt, but none of that offsets a lack of clarity around how your business runs today. The most successful implementations are led by organizations that come to the table prepared: operationally, technically, and organizationally.
So, what does “being prepared” mean?
1. Start With an Honest Internal Process Review prior to moving to ERP
Before you evaluate new systems or sit in a discovery workshop, you should be able to clearly explain:

• How work moves from quote to cash
• How production is scheduled, released, and tracked
• Where handoffs occur between departments
• Which steps are manual, duplicated, or heavily Excel-driven

This isn’t about documenting your “ideal” future state, it’s about acknowledging reality.
A clear-eyed internal process review gives your implementation team context. It allows them to distinguish between processes that are core to your business and ones that exist simply because “that’s how the old system worked.”
Organizations that skip this step often spend time and money recreating inefficiencies in a new system.
Those that do it well create space for meaningful improvement.
2. Understand Your Data Before You Move It
Data migration is rarely the hardest part of a project technically. But it’s often the most underestimated organizationally.
Successful clients understand:

• Where their data lives today (and how many sources exist)
• Which data is actively used vs. historically referenced
• Where inaccuracies, duplicates, or workarounds already exist
• Who owns data by functional area

Cleaning data during implementation is expensive and stressful. Cleaning it before implementation accelerates testing, reduces rework, and dramatically improves user confidence at go-live.
Good data doesn’t guarantee success. Bad data almost guarantees frustration.
3. Map All Systems That Keep the Plant Running
Very few manufacturing or distribution teams operate on a single system. In addition to ERP, production environments often rely on:

• Scheduling tools
• Quality systems
• Warehouse or shipping platforms
• EDI, payroll, or ecommerce integrations
• Homegrown databases or spreadsheets no one wants to admit exist

A successful implementation requires understanding how information flows between these systems today, not just technically but operationally. If your ERP project assumes the ERP will instantly replace everything else, surprises will follow. If it accounts for reality, integration planning becomes intentional instead of reactive.
4. Assign ERP Project Ownership, Not Just Participation
One of the strongest predictors of success is whether the client has:

• Clear executive sponsorship
• Empowered process owners
• Dedicated core team members with decision-making authority

Trying to implement a major system “part-time” almost always leads to delays. When accountability is shared by everyone, it’s ultimately owned by no one.
Prepared clients understand that participation isn’t enough, ownership is required.
5. Align Expectations Before the ERP Implementation Project Begins
ERP implementations are change initiatives, not just technology projects.
Clients that are prepared:

• Understand tradeoffs between speed, cost, and customization
• Accept that some processes will change
• Agree internally on what success looks like

When expectations are aligned early, discovery becomes collaborative instead of defensive, and decisions happen faster with fewer escalations.
Why This Preparation Changes Everything for a successful ERP Implementation
When clients come prepared:

• Discovery is faster and more meaningful
• Configuration decisions are grounded in reality
• Testing reflects real-world scenarios
• Users trust the system earlier
• Go-live risk is dramatically reduced

In short, preparation doesn’t just help the implementation team, it protects your investment.
Final Thoughts on preparing for your ERP Implementation
ERP implementations aren’t won in configuration sessions. They’re won in the weeks and months before the project starts, when organizations take the time to understand themselves.
If you’re considering an ERP project, the most valuable question you can ask isn’t “What system should we buy?”
It’s “How ready are we to implement it well?”
Looking for an honest opinion with regards to your ERP Implementation readiness? Please reach out to us directly.

The post The Most Overlooked Factor in a Successful ERP Implementation: Client Readiness appeared first on ERP Software Blog.

Manufacturing companies face the highest sales tax audit rate of any industry — 18%, according to Avalara research. For ERP teams and finance leaders responsible for compliance, that number is a useful starting point. The harder question is: which part of the compliance process is most likely to break, and why?
The answer varies by operation, but the pattern is consistent. Tax in manufacturing is not one problem. It is several simultaneous obligations that intersect at the ERP layer — and when the ERP is not set up to handle them, the gap usually goes undetected until an audit makes it visible.
 

Use Tax: A Common Blind Spot

Use tax is the compliance obligation most manufacturing operations underestimate. When raw materials are purchased tax-exempt because they are intended for resale or incorporated into finished goods, use tax typically applies if those materials are consumed internally — for facility maintenance, equipment repair, or other non-production purposes. The rules vary significantly by state.
Machinery exemptions add another layer. Some states require equipment to be used directly in production more than 50 percent of the time to qualify for an exemption. Others draw distinctions between new equipment and replacement parts. The same asset can be taxable in one state and exempt in another based on classification and actual use. ERPs that are not configured to distinguish these scenarios are calculating incorrectly by default.
 

Exemption Certificate Management at Scale

Manufacturers selling to resellers and exempt buyers are responsible for maintaining valid exemption certificates on file. An expired, missing, or misapplied certificate creates direct financial liability — the state treats those transactions as taxable and assesses back taxes and penalties across the full audit period.
An Avalara survey found that 53% of finance and tax professionals still manage exemption certificates manually or through a combination of manual and automated processes. At low transaction volumes, that approach is manageable. At scale — particularly for manufacturers serving multiple exempt customer types across multiple jurisdictions — it becomes a documentation risk that compounds over time.
 

Property Tax Across Multiple Facilities

Every facility adds property tax obligations. Real property tax applies in all 50 states. Personal property tax — covering machinery, equipment, and business assets not permanently affixed to land — applies in 43 states, with varying classification rules and depreciation schedules. Research from Avalara indicates 82% of companies say their exposure to tax compliance risk is higher today than five years ago, and for multi-facility manufacturers, property tax is often where that risk is most concentrated.
Overpaying due to inaccurate valuations is a real and often unnoticed cost. When assessments go unchallenged because no one has time to review the underlying calculations, the variance accumulates annually.
 

Where the ERP Fits In

Business Central provides the operational foundation manufacturers need. Purchasing, production orders, inventory, and financial management all flow through a single system. What it was not designed to do autonomously is track use tax rules across 40+ states, validate exemption certificates at scale, manage property tax filings across facilities, or handle VAT and e-invoicing for cross-border shipments.
Avalara's integration with Business Central closes those gaps natively — real-time sales and use tax calculation, automated multi-jurisdiction returns, exemption certificate management with AI-assisted validation, property tax compliance, and global requirements including VAT and HS code classification. The integration is available through Microsoft Marketplace and applicable toward Azure commitment.
 

The Takeaway for ERP Teams

Tax compliance in manufacturing is not a single configuration decision. It is an ongoing operational requirement that has to be built into the ERP layer — not managed around it. The manufacturers getting ahead of audit risk are the ones who treat tax automation as part of the ERP architecture, not an afterthought.
For the full breakdown of where compliance breaks in manufacturing operations and how the ERP layer can close those gaps, see the original piece at westerncomputer.com.

The post Manufacturing Tax Compliance Is More Layered Than Most ERP Teams Expect appeared first on ERP Software Blog.

The Microsoft ecosystem is having an important conversation right now, and it’s one Binary Stream has been part of for a long time.
With the launch of the OptimAL Performance Initiative, Microsoft, Ciellos, and a community of MVPs are tackling something that’s been undermining Business Central deployments for years: performance problems that stem not from the platform, but from the code running on it. The real culprits behind slow systems and frustrated users:

• Outdated coding patterns.
• Inefficient customizations.
• PTEs that weren’t built with scale in mind.

OptimAL addresses this head-on. It’s a structured program that moves partners from reactive troubleshooting to proactive performance optimization, with real diagnostic tools, hands-on work with Ciellos experts, and a clear measure → optimize → re-measure approach. Partners come out with:

• Better code.
• Better practices.
• The modern development skills that agentic solutions actually demand.

The foundation of the agentic future.

Here’s something we’ve learned building AI agents for Business Central and Dynamics 365: agentic automation is only as reliable as the foundation it runs on.
If your ERP environment has performance bottlenecks, inconsistent data, or processes that depend on manual intervention to stay on track. agents won’t fix that. In fact, they’ll inherit it.
That’s why the OptimAL philosophy resonates with us. Before you can automate intelligently, you need a system that behaves predictably. Performance-first development isn’t a box to check before going live. It’s what makes everything that comes next actually work.

What the agentic future looks like: Binary Stream’s AI agents.

We recently showcased two of our AI agents at Microsoft’s Dynamics 365 ERP Agents Coffee Break, and both are built on exactly this principle.
The Renewal Assistant Agent automates the full contract renewal lifecycle inside Business Central:

• Detects expiring contracts and sends personalized notifications automatically.
• Interprets customer responses — renew or cancel — and executes the outcome directly in the system.
• Maintains a structured, auditable record of all renewal actions.

No inbox monitoring. No manual follow-up. No dropped renewals.
The AI Quote Agent eliminates one of the most time-consuming bottlenecks in D365 F&O sales workflows:

• Pulls live ERP data to validate pricing and availability before a quote is ever drafted.
• Generates consistent, structured quote communications ready for customer delivery.
• Prepares approved quotes for invoicing with minimal manual handoffs.

Where we’re headed.

The partners who will win in the agentic era are the ones who build on solid ground; optimized code, modern practices, and a delivery approach that scales.
OptimAL is helping the partner community get there. Binary Stream is building on top of it.
If you want to learn more about the OptimAL Performance Initiative, visit aka.ms/OptimAL. And if you’re curious about what agentic ERP could look like for your business, we’d love to talk.

The post Redefining performance: Binary Stream joins the OptimAL Initiative with Microsoft. appeared first on ERP Software Blog.

While labor distribution often takes center stage in DCAA compliance, tracking Government Furnished Property (GFP) and Contractor Acquired Property (CAP) is equally vital for operational success and audit readiness. For contractors managing complex manufacturing, logistics, or research awards, losing track of physical assets isn't just a financial loss—it's a significant regulatory failure.
XTIVIA GovCon365, built on the Microsoft Dynamics 365 Business Central platform, provides the integrated visibility needed to manage property throughout the entire contract lifecycle, from procurement to closeout.

The Challenge of Property Segregation

Government property must be clearly identified and tracked separately from company-owned assets. Relying on manual logs or separate spreadsheets creates "data silos" that are difficult to reconcile during a property audit. GovCon365 solves this by embedding property tracking into your core project accounting workflow.

1. Procurement with Project Precision

The tracking of property begins at the moment of acquisition. In GovCon365, every Purchase Order can be linked directly to a Job No and a specific Job Task (WBS) code. This means that when an item is received, it is immediately associated with the contract it supports, creating an automated link between your physical inventory and your contract ledger.

2. Managing Contractor Acquired Property (CAP)

For items purchased specifically for a contract, GovCon365 ensures that these costs are accumulated correctly for billing and reporting. By using specialized Job Categories for materials and items, you can isolate these costs from your labor and indirect pools, meeting the transparency requirements of the FAR.

3. Integrated Fixed Asset Tracking

High-value property acquired under a contract often needs to be tracked as a long-term asset. GovCon365 leverages Business Central’s native Fixed Assets module, allowing you to record equipment, vehicles, or specialized machinery. You can maintain detailed records of location, maintenance, and eventual disposition—all while keeping the asset linked to the relevant government contract.

Driving Audit Readiness

When an auditor asks for a list of property associated with a specific task order, GovCon365 users don't have to go digging through paper files. Because the property data is integrated into the Job Card and Job Task Ledger Entries, you can generate reports that show:

• What was purchased?
• When it was received?
• Which project is currently being charged for its use?

Conclusion: A Unified View of Contract Performance

Managing government contracts involves more than just counting hours; it involves the stewardship of government-funded assets. By tracking property and materials within Business Central and XTIVIA GovCon365, you provide your project managers with a 360-degree view of their projects and your compliance team with the data they need to pass any property audit with ease.

The post Beyond Labor: Managing Property and Materials in Business Central with XTIVIA GovCon365 appeared first on ERP Software Blog.

Business Central reporting may be moving into cloud tools, dashboards and AI-assisted workflows, but many finance teams still start with Excel.
That creates an opening for Microsoft Partners working with Dynamics 365 Business Central customers. Exsion365, a Netherlands-based company with roots in the Navision market, is one example of how that opening is being packaged for the channel.
Its flagship product, Exsion Reporting, connects Excel to Business Central so finance users can build and refresh reports using ERP data. The company says the product can pull data from Business Central tables, refresh reports in Excel and follow the user’s Business Central permissions.
For Elielma Silva, Director of Strategic Partnerships at Exsion365, the appeal starts with the way controllers already work.
“As a previous controller myself, I know that I opened Excel every day even to think,” Silva said during an interview with PartnerTalks.

Business Central reporting as discovery work

Silva said Partners are central to Exsion365’s growth because they understand the customer’s Business Central implementation and the reporting requirements around it. That can become especially important during a new deployment, when customers are still learning what they need from ERP data.
As reports are built, customers may realize they need additional fields, customizations or different ways to view operational information. For implementation teams, those reporting conversations can expose requirements that might not surface in a standard discovery session.
“They start reporting on a new implementation of Business Central where the customers are still also learning a little bit about it,” Silva said. “And then they are like, “Oh, maybe we can add these fields or maybe we can do this customization.””
That makes Business Central reporting a discovery tool. It can show how a customer reads the business, which data points matter and where the system may need to be configured or extended.

Excel still shapes finance workflows

Silva pointed to construction and manufacturing as common use cases.
Construction companies often need to report by project, location or entity. Manufacturing companies can face high transaction volumes that make reporting more complex.
Those examples fit a broader pattern in the Business Central ecosystem. As PartnerTalks has reported on Business Central cloud reporting, finance teams and executives often need reporting capabilities that go beyond the ERP’s standard outputs.
That does not mean every customer wants the same reporting layer. Some will move toward Power BI or cloud-native analytics. Others will continue to rely on Excel because it remains familiar, flexible and widely understood by finance staff.
For Partners, the question is how to turn that reality into structured services work.
Business Central reporting can support requirements discovery, report design, user training and post-go-live support. In project-heavy or transaction-heavy accounts, it can also give Partners a clearer view of where customers struggle after the ERP is in place.
Exsion365 is also working on interface improvements and testing AI functionality inside Exsion Reporting, though Silva said that work remains in early stages.
For now, Business Central may hold the data, but Excel remains the working surface for many controllers. For Microsoft Partners, the opportunity is to make reporting part of the implementation conversation from the start.

The post Business Central reporting keeps Excel in play | Elielma Silva, Exsion365 appeared first on ERP Software Blog.

Growing eCommerce businesses can reduce operational complexity with Microsoft Dynamics 365 Business Central ERP by connecting inventory, order management, fulfillment, purchasing, and finance within a single platform. Instead of managing critical processes across disconnected systems, businesses gain real-time visibility into operations, helping teams make faster decisions, improve inventory accuracy, and support growth more efficiently. 
As online businesses expand into new sales channels, fulfillment models, and markets, operational complexity often grows faster than revenue. What begins as a manageable technology stack can quickly become a collection of systems that require constant coordination. This is why many growing organizations are evaluating how a connected ERP platform can help simplify operations and create a stronger foundation for long-term eCommerce growth. 
This is where Microsoft Dynamics 365 Business Central ERP helps. By connecting finance, inventory, purchasing, fulfillment, and reporting within a unified platform, Business Central gives growing eCommerce businesses the visibility and control they need to scale without creating additional operational friction. 

Growth Often Exposes the Limits of Disconnected Systems

Most eCommerce businesses do not begin with an ERP strategy. 
They start with an online storefront, a payment platform, and a fulfillment process that works for current demand. As the business grows, additional tools are introduced to solve specific challenges. 
A marketplace integration is added. Inventory management moves into a separate application. Shipping and fulfillment are handled through another platform. Reporting is pulled from multiple sources. 
None of these decisions are wrong individually. In fact, they often help businesses move faster. 
The challenge appears when teams need a complete picture of the business. 
A customer service representative may need information from multiple systems to answer a simple order inquiry. Finance teams spend valuable time reconciling transactions across channels. Inventory visibility becomes less reliable as stock moves between warehouses, marketplaces, and fulfillment partners. 
The business grows, but the operational effort required to manage that growth increases as well. 

Why eCommerce Complexity is Increasing

Today's commerce environment is significantly more complex than it was just a few years ago. 
Customers expect consistent experiences whether they buy through a website, marketplace, mobile channel, or social platform. At the same time, businesses are expanding into new regions, working with multiple fulfillment providers, and offering more delivery options than ever before. 
According to research, businesses continue to increase investments in omnichannel commerce, AI-driven customer experiences, and cross-border selling as growth priorities. As sales channels expand, the operational complexity behind them grows as well. 
The challenge is no longer simply generating demand. It is coordinating everything that happens after an order is placed. 

Visibility Becomes More Valuable Than Additional Tools

Many organizations respond to growth by adding more technology. However, more tools do not always create better visibility. 
In fact, disconnected applications often create new blind spots because critical information is spread across multiple platforms. 
Leaders frequently find themselves asking questions such as: 

• What inventory is actually available right now?  
• Which orders are delayed?  
• How are individual sales channels performing?  
• What is the financial impact of fulfillment decisions?  

Answering these questions often requires pulling information from different systems and manually validating the results. 
A connected ERP platform changes this dynamic by creating a shared operational view across the organization. 

Why Business Central ERP is Becoming Important for eCommerce Operations

For many growing businesses, the value of Microsoft Dynamics 365 Business Central ERP is not that it replaces every existing application. 
Its value comes from creating a central operational foundation that connects key business processes. 
Rather than managing finance, purchasing, inventory, and order management separately, organizations can operate from a common source of information. 
This improves visibility across: 

• Inventory availability  
• Order management  
• Purchasing activities  
• Financial performance  
• Fulfillment operations  

When information flows more consistently across departments, decision-making becomes faster and more accurate. 

Inventory Visibility Has Become a Competitive Advantage

One area where complexity frequently becomes visible is inventory management. 
Inventory information influences purchasing decisions, fulfillment performance, customer satisfaction, and financial planning. When inventory data is fragmented across systems, organizations often experience stock imbalances, fulfillment delays, or inaccurate availability information. 
Business Central helps bring inventory activity into a more connected environment, making it easier for organizations to understand what inventory they have, where it is located, and how demand is affecting future requirements. 
For growing eCommerce businesses, this level of visibility becomes increasingly important as operations expand. 

Connected Operations Create Scalable Growth

One of the biggest misconceptions about growth is that operational complexity must increase at the same pace. The most scalable organizations focus on reducing friction as they grow. They create processes that are connected, visible, and easier to manage. Teams spend less time searching for information and more time acting on it. 
This is where ERP for eCommerce becomes especially valuable. Instead of adding another layer of technology, it provides a framework that helps existing business functions work together more effectively. 
The result is a business that can support additional channels, customers, and transactions without creating the same level of operational strain. 

Building a Stronger Foundation for eCommerce Growth

As eCommerce businesses grow, success becomes less about managing individual transactions and more about coordinating the entire operation behind them. 
Finance, inventory, purchasing, fulfillment, and customer experience all become interconnected. When these functions operate in isolation, complexity increases. When they operate from a connected platform, organizations gain greater visibility, efficiency, and control. 
Microsoft Dynamics 365 Business Central ERP helps businesses create that connected foundation, supporting growth while reducing the operational challenges that often come with it. 

Exploring Microsoft Dynamics 365 Business Central ERP

Organizations looking to improve inventory visibility, order management, and operational efficiency often start by evaluating how well their current systems support growth. 
Microsoft Dynamics 365 Business Central ERP provides a unified platform that helps connect financial, operational, and commerce processes, enabling businesses to scale with greater confidence and clarity. 
Get in touch to learn how businesses are using Business Central ERP to simplify eCommerce operations and support long-term growth. 

The post How Microsoft Dynamics 365 Business Central ERP Helps Growing eCommerce Businesses Reduce Complexity appeared first on ERP Software Blog.

Quick answer: When you move from on-premise Dynamics NAV to Business Central online (SaaS), every user identity has to be rebuilt on Microsoft Entra ID (the service formerly called Azure AD). NAV's Windows and database logins don't carry forward - Business Central SaaS authenticates only through Entra ID. Getting the identity layer right means provisioning Entra accounts, assigning the correct Business Central licenses, mapping NAV permissions to Entra security groups, re-platforming integrations onto OAuth 2.0, and enforcing MFA before go-live. The checklist below is the exact sequence we run.
If you've scoped a NAV-to-cloud project, you've probably spent most of your planning on data: chart of accounts, open transactions, historical posting. That's the part everyone budgets for. The part teams routinely underestimate - and the one that causes the most go-live-morning surprises - is identity.
On-premise NAV mostly trusted your network. A user was a DOMAIN\username Windows account, or a NAV-specific credential, sitting behind your firewall. Business Central SaaS makes no such assumption. There is no domain controller, no NAV Server service account, and no SQL login. Authentication is handled entirely by Microsoft Entra ID using modern, token-based protocols. So the migration isn't just "copy the users over" - it's a full identity re-platforming.
This guide walks through that re-platforming step by step. If you want the broader picture of moving the application and data, pair it with our overview of Business Central migration services and our field notes on migrating messy legacy data into Business Central. Here, we stay focused on the Azure AD / Entra ID side.

A note on the name: In 2023, Microsoft renamed Azure Active Directory to Microsoft Entra ID. The product, your tenant, and your accounts are the same - only the branding changed. We use "Microsoft Entra ID (formerly Azure AD)" throughout because both names still appear in admin centers, documentation, and PowerShell cmdlets you'll touch during the project.

Why identity is the hardest part of a NAV → Business Central SaaS migration

Three things change at once when you go from NAV on-premise to Business Central online, and all three run through Entra ID:

• Authentication model. NAV typically used Windows authentication or NAV-specific credentials. Business Central SaaS uses cloud identity exclusively - every sign-in flows through Entra ID, and access works from any device without a VPN.
• The protocol. Older NAV/Entra setups used WS-Federation. Business Central moved to OpenID Connect (built on OAuth 2.0), and WS-Federation support was removed in the 2023 release wave 1 (version 22). Any integration still using basic auth on NAV web services has to be rebuilt.
• Permission management. Business Central replaced user groups with security groups that live in Entra ID and sync into the app. Your old NAV permission structure needs to be re-expressed as Entra security groups plus Business Central permission sets.

Miss any one of these and the symptom is the same: users can't sign in on day one, or an interface that ran quietly for a decade suddenly fails authentication. The checklist exists to surface those failures during testing instead of during go-live.

Before you start: prerequisites

You need these in place before the identity work begins:

• A Microsoft 365 / Entra ID tenant for the organization (most companies already have one through Office/Teams).
• A Business Central online environment provisioned in the Business Central admin center.
• Business Central licenses purchased and available to assign (Essentials, Premium, and Team Members, as appropriate).
• The person running the cloud migration holds SUPER permissions in Business Central and an admin role in the Microsoft 365 admin center. If a partner runs it for you, that's done through a GDAP (granular delegated admin) relationship.
• A supported NAV upgrade path: you migrate to Business Central online from NAV 2015 or later by way of Business Central on-premises version 14 (Spring 2019), with customizations converted to AL extensions. Data sitting in code-customized tables can't be carried forward as-is.

If you're not certain your environment qualifies, an ERP readiness assessment will confirm the upgrade route before you commit budget. And if your NAV version is old enough that re-implementation beats upgrading, our breakdown of Business Central re-implementation vs. migration is worth reading first.

Timing matters. NAV 2016 left extended support on 14 April 2026, NAV 2017 ends 11 January 2027, and NAV 2018 - the final version - ends 11 January 2028. Once those dates pass, there are no more security updates. The same deadline pressure that we wrote about for GP customers waiting until 2029 applies to NAV, just on a different clock.

The Azure AD / Microsoft Entra ID migration checklist

We run this in six phases. Each one gates the next - don't start phase 3 until phase 2 is signed off.

Phase 1 - Identity discovery and clean-up

This is the audit. You can't migrate identities you haven't inventoried.

• Export every NAV user, including disabled and dormant accounts. Flag anyone who hasn't logged in for 90+ days for retirement, not migration.
• Separate humans from non-humans. Service accounts, scheduled-job runners, and integration logins need a completely different treatment in the cloud (see Phase 5) than named employees.
• Find every shared login. NAV environments are full of "AccountsPC" style shared credentials. These cannot move to Entra ID as-is - each real person needs their own account for licensing and audit.
• Document the current NAV permission sets per user, so you have a source of truth to map against later.
• List every integration that authenticates into NAV (EDI, e-commerce, Power BI, Excel add-ins, third-party apps) and how each one signs in today.

Phase 2 - Microsoft Entra ID tenant readiness

• Confirm every employee who needs Business Central has an active Entra ID account. New hires, contractors, and warehouse staff who only had a NAV login but no Microsoft 365 account need one created now.
• Standardize User Principal Names (UPNs). The UPN (usually the work email) becomes the sign-in identity and the value Business Central matches against. Inconsistent or personal email UPNs cause headaches, fix them before provisioning.
• Decide your Conditional Access posture. Moving to Entra ID is the moment to enforce MFA and device/location policies. Plan it deliberately so it protects people without locking out the service accounts you'll set up in Phase 5.
• Set up a break-glass / emergency admin account that's excluded from Conditional Access, so a misconfigured policy can never lock you out of your own tenant.
• Handle external users. If vendors or external accountants touched NAV, they're now Entra External ID (B2B) guests. Note that Microsoft ended new sales of the legacy Azure AD B2B/B2C model in May 2025 in favor of Entra External ID - plan external access on the current platform.

If your team isn't comfortable hardening the tenant, this is the natural point to bring in Microsoft Azure consulting support.

Phase 3 - Licensing and user provisioning

• Map each user to the right Business Central license: Essentials, Premium, or Team Members. Premium is required for users who touch manufacturing or service management.
• Assign licenses in the Microsoft 365 admin center, not inside Business Central. Entitlements flow from the assigned license into the app - a user with no license (or the wrong one) lands in read-only or can't sign in.
• Account for Microsoft 365–only users. People who only need light access via Teams can be granted limited Business Central access with an M365 license, but that requires enabling it on the environment and assigning a security group.
• Run "Update users from Microsoft 365" in Business Central to pull the licensed users in, then verify the list matches your Phase 1 inventory.
• Right-size the license count. Migrations are a great time to stop paying for the dormant accounts you flagged earlier. If you're unsure how Business Central licensing has shifted, our D365 licensing changes for 2025–2026 post breaks it down.

Phase 4 - Security groups and permission mapping

• Rebuild NAV permission structures as Entra ID security groups. Security groups replaced user groups starting in version 22 (user groups were usable through version 25 / 2024 release wave 2). Create the groups in the Entra admin center with the group type set to Security, Microsoft 365 groups won't work here.
• Map old NAV permission sets to Business Central permission sets, then attach those sets to the matching security group. Assign permissions to the group, not to individuals, so future joiners inherit access automatically.
• Sync the security groups into Business Central and confirm each user shows the expected group membership and effective permissions on their user card.
• Watch for conflicting permission sets when a user belongs to more than one group - resolve overlaps before go-live, not after.
• Confirm at least one named SUPER user exists in the target company (beyond the break-glass account).

Getting this layer modeled correctly is foundational to a clean Business Central implementation - under-scoped security design is one of the quiet reasons out-of-the-box Business Central deployments stall.

Phase 5 - Authentication cut-over and integrations

This phase breaks more go-lives than any other, because integrations rarely get tested until late.

• Re-platform every integration onto OAuth 2.0 / OpenID Connect. Basic-auth web service calls that worked against NAV will not work against Business Central SaaS.
• Create Entra ID app registrations for service-to-service (S2S) authentication. Background integrations and Automation API consumers authenticate as an app - not as a person - using client credentials, not a shared password.
• Re-issue credentials for first-party connectors - Power BI, the Excel and Outlook add-ins, and Power Automate flows all require Entra authentication in Business Central. Reconnect and retest each one.
• Verify MFA and Conditional Access don't block automation. Service principals should be governed by their own policy, separate from the human-user MFA rules.
• Run a full sign-in test with real users on real devices - including remote and mobile - before cut-over weekend. This is the dress rehearsal that catches the UPN mismatches Phase 2 missed.

Phase 6 - Post-go-live identity hardening

• Decommission on-premise identity dependencies: retire the NAV Server service accounts, SQL logins, and any VPN rules that only existed to reach NAV.
• Disable the migrated dormant accounts you chose to keep temporarily for reference.
• Turn on sign-in and audit logging in Entra ID and review the first weeks of access.
• Document the security group → permission set mapping so your admins can onboard and offboard staff without re-discovering it.
• Schedule a 30-day access review. Real usage always reveals over- and under-provisioned users; tune it once people are working in the system.

Ongoing, this is the kind of thing a Business Central support arrangement keeps healthy long after the project closes.

Common pitfalls we see (and how to avoid them)

• Treating NAV logins as 1:1 mappable. They almost never are. Shared accounts and orphaned service logins always need redesign, not migration.
• Assigning licenses inside Business Central first. Licensing starts in the Microsoft 365 admin center; the app only reflects what Entra grants.
• Forgetting integrations until cut-over week. The one EDI feed nobody documented is the one that fails on Monday. Inventory it in Phase 1.
• Skipping the break-glass account. A single over-aggressive Conditional Access rule can lock every admin out of the tenant. The emergency account is cheap insurance.
• Carrying over permission sprawl. A migration is a rare chance to clean up access. Re-model around security groups instead of replicating a decade of one-off NAV permission tweaks.

How long does the identity work take?

For a single-company NAV environment with clean accounts and a handful of integrations, the identity workstream is usually a few weeks running in parallel with data migration. Multi-company tenants, heavy customization, or a tangle of legacy integrations push it longer. The variable that moves the timeline most isn't headcount - it's how much clean-up Phase 1 uncovers. The cleaner your starting inventory, the faster everything downstream goes.
Once you're on Business Central SaaS, the identity foundation you've built is also what unlocks the cloud-only capabilities NAV could never offer - continuous updates, the Power Platform, and Copilot inside Business Central.

Frequently asked questions

Does Business Central SaaS still support Windows authentication like NAV did? No. Business Central online authenticates exclusively through Microsoft Entra ID (formerly Azure AD). Windows authentication, SQL logins, and NAV-specific credentials don't exist in the SaaS model, every user signs in with their Entra ID account.
Do my NAV users automatically become Business Central users? No. NAV users don't migrate as identities. Each person needs an active Entra ID account, an assigned Business Central license, and membership in the right security group. The cloud migration tool moves your data, not your logins.
What happened to Azure AD - is it gone? It was renamed, not removed. Azure Active Directory became Microsoft Entra ID in 2023. Your tenant, accounts, and policies are unchanged; you'll just see both names across admin centers and documentation.
How are NAV permissions handled in Business Central online? Through Entra ID security groups synced into Business Central, combined with Business Central permission sets. Security groups replaced the older user-group model. You map each NAV permission profile to a security group and assign permissions to the group rather than to individuals.
Will my NAV integrations keep working after migration? Only if they're rebuilt for modern authentication. Business Central SaaS uses OpenID Connect (OAuth 2.0); basic-auth web service calls are removed. Background integrations need Entra ID app registrations using service-to-service authentication.
Can I enforce MFA on Business Central after migrating? Yes - and you should. Because identity moves to Entra ID, you can apply MFA and Conditional Access policies to Business Central like any other cloud app. Just carve out separate handling for service accounts so automation isn't blocked.
Which NAV versions can migrate directly to Business Central online? You migrate from NAV 2015 or later via Business Central on-premises version 14 (Spring 2019), with customizations converted to AL extensions. Older versions may need an intermediate upgrade or a re-implementation instead.

About the author

This guide was written by the Microsoft Dynamics consulting team at Trango Tech Enterprise, a Microsoft Dynamics 365 Business Central partner specializing in NAV-to-cloud migrations, identity re-platforming, and post-go-live support. The checklist above reflects the sequence our consultants run on production migrations. Planning a move off on-premise NAV? Talk to our migration team.

The post On-Premise NAV to Business Central SaaS - Azure AD Migration Checklist appeared first on ERP Software Blog.

Most ERP systems were designed around structured navigation.
Users open forms, search records, move through workflows, validate fields, and complete transactions step by step. Even in modern cloud ERP environments, execution still depends heavily on manual interaction.
That model is becoming increasingly difficult to sustain.
Finance and supply chain teams today operate in environments where decisions must happen faster, field teams need mobile accessibility, and operational delays directly impact customer experience, procurement cycles, and revenue flow.
Organizations running Dynamics 365 Finance and Supply Chain Management are now asking a different question.
What if ERP execution could happen through conversation instead of navigation?
This shift is exactly what DynaTech’s upcoming Dynamics 365 F&SCM Webinar explores.
The session focuses on how AI agents powered by the Model Context Protocol are changing the way users interact with Dynamics 365 Finance & Supply Chain Management. Instead of using ERP interfaces to manually complete transactions, users can execute actions directly from Microsoft Teams using natural language.
The result is not simply a better user experience.
It is a fundamentally different approach to ERP process automation.

Why ERP Work Still Feels Slower Than It Should

A huge number of organizations have already modernized their ERP infrastructure, yet operational friction still exists at the user interaction layer.
A procurement manager may need multiple screens just to create a requisition. A sales representative working remotely still depends on navigating complex ERP menus. Finance teams spend valuable time validating repetitive transaction flows instead of focusing on operational priorities.
Even standard AI assistants only solve part of the problem.
They summarize information, retrieve records, or provide recommendations, but execution still requires users to manually complete the process inside Dynamics 365.
This creates a major limitation for enterprises managing high-volume operational environments.
The gap between information access and transaction execution remains largely manual.
That is why AI-driven execution is becoming one of the most important conversations in modern ERP strategy.

What Makes This Dynamics 365 Webinar Different

Many enterprise webinars focus on concepts.
This AI agents webinar is designed as a technical walkthrough of how execution-based AI works inside real Dynamics 365 Finance and Supply Chain Management environments.
The session demonstrates how the Model Context Protocol enables secure interaction directly with the Dynamics 365 backend without depending on UI-driven workflows.
Instead of asking users to adapt to ERP complexity, the system adapts to the user.
Participants will see how conversational execution inside Microsoft Teams can simplify operations such as:

• Creating Sales Orders
• Generating Purchase Requisitions
• Triggering ERP transactions through natural language
• Reducing dependency on manual navigation
• Improving accessibility for mobile and remote users

This Dynamics 365 webinar is especially relevant for:

• Finance Directors
• Supply Chain Leaders
• ERP Transformation Teams
• Operations Executives
• Dynamics 365 Solution Architects
• IT and Digital Transformation Leaders

For organizations evaluating AI-enabled ERP process automation, this session provides practical architectural insight instead of high-level marketing narratives.

Understanding the Model Context Protocol in Enterprise ERP Environments

One of the biggest reasons enterprises remain cautious about AI execution is security.
Most organizations cannot expose sensitive ERP environments to uncontrolled AI interaction.
The Model Context Protocol solves this challenge by creating a secure execution framework between AI agents and enterprise systems.
In this MCP webinar, attendees will learn how the protocol enables controlled, backend-level interaction with Dynamics 365 Finance and Supply Chain Management while maintaining enterprise governance.
The architecture supports:

• Secure execution within Azure environments
• Controlled transaction orchestration
• Natural language interaction through Microsoft Teams
• Isolation of sensitive ERP metadata
• Enterprise-grade encryption and access control
• Backend execution without UI dependency

This approach changes the conversation around enterprise AI.
Instead of limiting AI to chat-based assistance, organizations can begin enabling secure operational execution.
For enterprises planning long-term ERP modernization strategies, this represents a significant shift in how users interact with business systems.

Meet the Speaker - JT Gorrell

With more than 25 years of experience leading enterprise technology initiatives, JT Gorrell brings deep expertise in ERP transformation, program delivery, and organizational change management. Throughout his career, he has worked closely with executive leadership teams to help organizations successfully implement and optimize business-critical systems while driving measurable operational improvements.
As VP of Customer Success at DynaTech Systems, JT partners with organizations to maximize the value of their Dynamics 365 investments.
In this webinar, JT will share practical insights into how AI agents and the Model Context Protocol (MCP) are reshaping ERP execution within Dynamics 365 Finance & Supply Chain Management, helping organizations move beyond traditional workflows toward more intelligent, conversational business operations.

What Attendees Will Experience During the Live Session

The webinar is structured as a technical and operational walkthrough designed to show how AI-driven execution works in practice.
Key discussion areas include:

The Friction Problem in ERP Operations

The session begins by examining why manual workflows continue to slow down high-volume finance and supply chain operations.
Attendees will see how repetitive navigation, data entry, and structured workflows create operational inefficiencies even in cloud ERP environments.

From AI Assistance to AI Execution

The webinar explains the difference between standard AI copilots and execution-capable AI agents.
Participants will understand why retrieval-based AI experiences are no longer sufficient for enterprises seeking faster operational responsiveness.

Technical Deep Dive Into the Model Context Protocol

DynaTech experts will break down how the Model Context Protocol interacts directly with the Dynamics 365 backend.
The session explores how secure execution layers can support transaction orchestration without depending on traditional UI navigation.

Live Demonstration Inside Microsoft Teams

One of the core highlights of the webinar is a live demonstration showing how users can create transactions using conversational inputs.
The demonstration includes:

• Sales Order creation
• Purchase Requisition execution
• Real-time ERP transaction processing
• Natural language interaction through Teams

The focus is on showing how execution speed changes when ERP interaction becomes conversational.

Security, Governance, and Enterprise Control

The session also addresses enterprise concerns around governance, compliance, and security.
Attendees will see how the MCP architecture keeps ERP data within controlled Azure environments while enabling AI-powered operational execution.

Why This Matters for Dynamics 365 Enterprises Right Now

AI adoption inside ERP systems is accelerating quickly.
However, many organizations are still evaluating AI primarily through the lens of assistance rather than execution.
The next phase of enterprise transformation will not simply involve retrieving information faster.
It will involve reducing operational friction across everyday ERP activities.
For organizations using Dynamics 365 AI Agents, this creates opportunities to:

• Accelerate transaction execution
• Improve operational responsiveness
• Reduce manual ERP interaction time
• Expand ERP accessibility for remote teams
• Simplify mobile ERP experiences
• Improve user adoption across operational departments

This is particularly important for enterprises managing distributed teams, warehouse operations, procurement workflows, field sales execution, and high-volume finance processes.
As ERP systems become more intelligent, the ability to execute transactions through natural language will become increasingly valuable.

How DynaTech Is Helping Enterprises Explore AI-Driven ERP Operations

DynaTech helps organizations evaluate and implement next-generation ERP execution models across Dynamics 365 Finance and Supply Chain Management environments.

Dynamics 365 and AI Execution Expertise

DynaTech works across Dynamics 365, Azure, Power Platform, and AI-driven enterprise architectures to help organizations modernize operational workflows.

Focus on Practical ERP Automation

The approach goes beyond AI experimentation and focuses on real operational use cases such as transaction execution, workflow acceleration, and conversational ERP interaction.

Enterprise-Ready Architecture Perspective

The session highlights the architectural, governance, and security considerations involved in enabling AI-powered ERP execution within enterprise environments.

Technical and Business Alignment

The webinar is designed for both technical and operational leaders looking to understand how AI agents and ERP process automation can improve execution speed and user accessibility.

Guidance for Long-Term ERP Modernization

For organizations exploring the future of Dynamics 365 AI Agents and intelligent ERP operations, DynaTech provides strategic and implementation-focused guidance backed by Microsoft ecosystem expertise.

Reserve Your Spot for the Live Dynamics 365 F&SCM Webinar

The future of ERP interaction is moving beyond menus, forms, and repetitive navigation.
AI-driven execution powered by the Model Context Protocol is creating new possibilities for how enterprises interact with Dynamics 365 Finance and Supply Chain Management.
If your organization is evaluating AI agents, ERP process automation, or conversational execution inside Dynamics 365 environments, this webinar provides a practical view into where enterprise ERP operations are heading.
Join DynaTech’s live Dynamics 365 webinar to explore how natural language execution inside Microsoft Teams can simplify operations, accelerate transaction workflows, and modernize ERP interaction.
Reserve your spot now and experience how AI-powered execution is redefining Dynamics 365 operations.
 

The post Dynamics 365 Webinar: How the Model Context Protocol Enables AI-Driven ERP Execution appeared first on ERP Software Blog.

The apparel industry moves fast. New collections launch every season, customer demand shifts quickly, and brands must manage thousands of product variations across multiple sales channels. Yet many growing apparel companies still rely on disconnected spreadsheets, legacy software, and manual processes that make scaling difficult.
As brands expand, operational challenges become harder to manage. Inventory inaccuracies, fulfillment delays, overselling, and limited visibility into financial performance can directly impact profitability. This is why many apparel companies are turning to industry-specific ERP solutions built on Microsoft Dynamics 365 Business Central.

Why Standard ERP Systems Struggle with Apparel Operations

Unlike most industries, apparel businesses must manage complex combinations of styles, colors, sizes, fits, seasonal collections, and multi-channel sales. Generic ERP systems often provide strong financial and operational capabilities but lack the specialized functionality required to handle apparel-specific workflows effectively.
Common challenges include:

• Managing large style-color-size matrices
• Planning seasonal collections and product launches
• Coordinating wholesale, retail, eCommerce, and marketplace orders
• Maintaining accurate inventory across multiple channels
• Tracking profitability at the SKU, collection, and channel level
• Forecasting demand for seasonal products

Without apparel-specific capabilities, businesses often create manual workarounds that increase complexity, slow decision-making, and introduce costly errors.

How Business Central Supports Growing Apparel Brands

Microsoft Dynamics 365 Business Central provides a modern cloud ERP foundation that connects finance, inventory, purchasing, warehousing, sales, and reporting within a single platform. It helps apparel companies eliminate data silos and gain real-time visibility across the business.
Key benefits include:

• Centralized financial management
• Real-time inventory visibility
• Multi-location warehouse management
• Purchasing and supply chain control
• Integrated reporting and analytics
• Scalability for growing brands and distributors

The Need for Apparel-Specific ERP Functionality

While Business Central provides a strong ERP foundation, apparel brands often require additional functionality designed specifically for their industry. Solutions such as Volt 365® Apparel extend Business Central with capabilities tailored to fashion, footwear, wholesale, and apparel operations.
These industry-focused enhancements include:

• Style, color, and size matrix management
• Seasonal collection planning
• Soft inventory allocation
• Multi-channel order management
• SKU-level forecasting
• Product lifecycle management
• Landed cost and margin tracking
• Wholesale and EDI processing

Because these capabilities operate natively within Business Central, businesses can avoid complex middleware, duplicate data entry, and disconnected systems.

Benefits for Apparel Brands

By combining Business Central with apparel-specific functionality, brands can:

• Improve inventory accuracy
• Reduce fulfillment errors
• Streamline product management
• Gain better visibility into margins and profitability
• Manage seasonal collections more effectively
• Support growth across wholesale, retail, and direct-to-consumer channels
• Create a scalable foundation for AI, analytics, and future digital transformation initiatives

Final Thoughts

For growing apparel brands, operational complexity increases with every new collection, sales channel, and product variation. A modern ERP platform is no longer optional, it's essential for maintaining efficiency and profitability.
Microsoft Dynamics 365 Business Central provides the cloud-based foundation needed to unify operations, while apparel-specific ERP extensions add the specialized functionality required to manage the unique challenges of the fashion industry. Together, they help apparel brands gain control, improve visibility, and scale with confidence.
Discover how leading apparel brands are modernizing operations with Microsoft Dynamics 365 Business Central. Read the full blog here: https://volt-technologies.com/post/business-central-for-growing-apparel-brands/

The post Microsoft Dynamics 365 Business Central for Growing Apparel Brands appeared first on ERP Software Blog.

Insight Works has released Graphical Scheduler v2.2 for Business Central, adding Double Zoom In and Double Zoom Out actions for faster timeline navigation. The update also introduces smarter style defaults and a new Blue-Gray color option for production event coding.

Insight Works has released Graphical Scheduler v2.2 for Microsoft Dynamics 365 Business Central, introducing faster zoom navigation, improved default style behavior, and an expanded color palette for production event coding. For production planners and operations managers who work daily in the scheduling interface, the update addresses recurring friction in how users navigate timelines and configure visual styles.
Availability: Graphical Scheduler is a completely free app from Insight Works for Business Central.
Navigation adjustments that previously required multiple clicks now take fewer. Graphical Scheduler v2.2 introduces Double Zoom In and Double Zoom Out actions, allowing users to move between levels of timeline detail in a single step. For teams managing dense production schedules across multiple work centers, reducing the number of interactions required to reach the right view level translates directly to less time spent adjusting the interface and more time acting on what it shows.
The update also closes a gap in style configuration. Previously, when no border color was defined for a scheduler style, the event border would render inconsistently, requiring manual correction to achieve a clean appearance. In v2.2, the scheduler automatically applies the background color as the default border when none is specified, producing a uniform event appearance without additional configuration.
Blue-Gray has also been added to the available style color palette, giving teams one more option for color-coding production events, statuses, or departmental groupings within Business Central.
"These are the kinds of changes that don't make headlines but matter every day," said Brian Neufeld, Director of Marketing at Insight Works. "When schedulers are navigating timelines dozens of times a day, fewer clicks add up. The style improvements mean teams spend less time fixing visual inconsistencies and more time using the scheduler as it's intended."
For more information about Graphical Scheduler, visit SchedulerForDynamics.com. Businesses looking to implement or upgrade can connect with any of Insight Works' 750+ global Microsoft Partners.
About Insight Works
Insight Works is a leading Independent Software Vendor (ISV) dedicated to creating apps exclusively for Microsoft Dynamics 365 Business Central. The company specializes in the manufacturing and distribution industries, providing innovative solutions that streamline operations and enhance productivity for businesses worldwide. With a vast reseller network comprising over 750 global Microsoft Partners, Insight Works ensures its apps are accessible and supported wherever businesses operate.
Headquartered in Canada, Insight Works also maintains a regional office in the Netherlands, strengthening its global reach and commitment to localized support. Learn more at dmsiworks.com.

The post Insight Works Releases Graphical Scheduler v2.2 for Microsoft Dynamics 365 Business Central appeared first on ERP Software Blog.

ATLANTA, GA  — 6/1/2026 — Velosio, a Microsoft Inner Circle partner with over 30 years of Microsoft ecosystem expertise, announced today the acquisition of Domain 6, a respected Microsoft consultancy known for enterprise delivery excellence and deep industry specialization. Domain 6 will operate as Domain 6, a Velosio company, reinforcing Velosio's commitment to delivering Microsoft-aligned solutions at enterprise scale — without disruption to existing client, field, or partner relationships.
The acquisition expands Velosio's enterprise capabilities across the full Microsoft stack — including Dynamics 365, Power Platform, Azure, and Copilot — and strengthens its ability to support Microsoft's largest and most complex customers. Domain 6 brings a proven track record of enterprise delivery, trusted relationships with Microsoft field teams, and industry-specific expertise in real estate, & Service based industries (including Media, Advertising, Construction and core professional services) — verticals where Microsoft-aligned, complex implementations demand specialized depth.
"This acquisition is a deliberate investment in our ability to serve enterprise customers across the Microsoft ecosystem," said Robbie Morrison, CEO of Velosio. "Domain 6 has built exactly the kind of credibility we respect — trusted by Microsoft field teams, deeply embedded in their client organizations, and consistently delivering outcomes that matter. Together, we are better positioned to support Microsoft's most strategic customers and deepen our role as a premier enterprise partner."
For Microsoft field teams, partner managers, and co-sell partners, the transition is designed to be frictionless. Existing co-sell motions, Microsoft relationships, and partner commitments continue uninterrupted. Domain 6 leadership remains in place, and the endorsed brand model — Domain 6, a Velosio company — ensures market continuity while the two organizations thoughtfully align go-to-market strategy over the coming months.
"Domain 6's strength has always been our people and our Microsoft ecosystem relationships," said Salim Faroukh, CEO of Domain 6. "Joining Velosio gives us the scale and investment to do even more for our clients and Microsoft partners — while staying grounded in the enterprise focus and delivery excellence we're known for."
The combined organization strengthens Velosio's upmarket presence, expands its industry vertical capabilities, and further solidifies its position as one of Microsoft's most trusted transformation partners across the full stack.
About Velosio
Velosio is a leading Microsoft partner delivering business transformation through Microsoft Dynamics 365, Power Platform, Azure, Modern Work, and the broader Microsoft Cloud. With deep industry expertise and a customer-centric approach, Velosio helps organizations operate more efficiently, scale with confidence, and achieve long-term success through the Microsoft stack. Velosio is a portfolio company of Court Square Capital Partners. Learn more at: www.velosio.com
 
About Domain 6
Domain 6 is a Microsoft-focused consultancy specializing in enterprise solutions and industry-specific transformation. Known for deep Microsoft expertise, enterprise delivery credibility, and trusted relationships across the Microsoft field and partner ecosystem, Domain 6 partners with organizations to deliver scalable, high-impact Microsoft solutions across complex engagements. Learn more at: www.domain6inc.com
About Court Square Capital Partners
Court Square is a middle market private equity firm with over 40 years’ experience in the industry. Since 1979, Court Square has completed over 245 platform investments and is focused on helping Founders, Families, and Manager-owners to develop their companies into market leaders. Court Square invests in companies that have compelling growth potential in the industrial, business services, healthcare, and tech and telecom sectors. As of December 31, 2025, Court Square has $10.1 billion of assets under management and is based in New York, N.Y. For more information on Court Square, please visit www.courtsquare.com.

The post Velosio Acquires Domain 6 to Strengthen Enterprise Delivery and Deepen Microsoft Ecosystem Alignment appeared first on ERP Software Blog.

The Business Central MCP Server is a Microsoft-built integration layer that connects AI tools like Microsoft Copilot Studio, GitHub Copilot, Claude, and ChatGPT directly to your Dynamics 365 Business Central environment using natural language. Released as part of the 2026 Release Wave 1, the Business Central MCP Server gives mid-sized organizations a practical, governed way to unlock ERP data and automate routine tasks without custom API development or middleware.
Mid-sized organizations running Microsoft Dynamics 365 Business Central face a common challenge. Although they have the data, accessing it fast enough to act on it remains difficult. Customers, inventory levels, sales orders, and vendor balances are all inside Business Central. However, getting to that information requires navigating the right pages, knowing the right filters, and running the right reports. For many employees, the workaround is to ask someone else or export data to a spreadsheet.
For IT administrators and Dynamics 365 partners, the problem is different but equally frustrating. Routine environment management tasks like refreshing sandboxes, diagnosing upgrade issues, and validating configurations have always required scripting skills or deep familiarity with the admin center. As a result, skilled people spend time on repetitive tasks instead of higher-value work.
In this post, we explain what the Business Central MCP Server does, why it matters for operational efficiency, and how mid-sized organizations can get started with a phased implementation approach.

What Is the Business Central MCP Server?

Specifically, the Business Central MCP Server is built on the Model Context Protocol (MCP), an open standard for connecting AI tools to external systems in a consistent and secure way. Because MCP is an open standard, any MCP-compliant AI client can connect to a Business Central environment using the same endpoint and tool definitions. Consequently, there is no need to rebuild the integration for each new tool.
With the Business Central MCP Server, AI clients can read and write ERP data through natural language. For example, they can query customer records, check inventory, manage sales orders, and run environment administration tasks, all without opening the Business Central client directly. Furthermore, operations run under the user's existing identity and permissions, so governance and compliance requirements are addressed from day one.

The Three Challenges the Business Central MCP Server Solves

The organizations we work with are not struggling because they lack data. Instead, they are struggling because it is too hard to act on it. Three friction points come up repeatedly.

1. ERP Data Is Locked Behind Specialized Interfaces

Business Central holds a tremendous amount of operational intelligence. However, accessing it requires navigating menus and knowing the right reports. Employees who are not power users often wait for someone else to pull the information they need. Alternatively, they build manual workarounds in Excel. Traditional ERP systems were built for structured data entry and reporting, not for the fast conversational access that modern teams expect. As AI tools become part of everyday workflows, the gap between what employees want and what their ERP delivers keeps growing.

2. Administrative Work Requires Too Much Technical Overhead

Additionally, routine Business Central environment management has always required a certain level of scripting skill or deep admin center familiarity. When only a few people can perform these tasks, any absence creates a bottleneck. Moreover, every hour a skilled administrator spends refreshing a sandbox or investigating an upgrade issue is an hour not spent on implementation work or helping users. This overhead does not scale as an organization's Business Central footprint grows.

3. Connecting AI Agents to Live ERP Data Requires Custom Integration Work

Meanwhile, many organizations want to deploy AI agents across sales, finance, and operations. The problem is that connecting those agents to live Business Central data has historically required bespoke integrations, including custom APIs, middleware, and ongoing maintenance. Furthermore, each new AI use case has meant a new integration project. That slows adoption and increases cost.
Fortunately, the Business Central MCP Server addresses all three of these problems through a single, standardized connection layer.

What the Business Central MCP Server Enables

1. Conversational Access to Real-Time ERP Data

In practice, the Business Central data MCP server exposes a set of tools that allow AI clients to interact with ERP data through natural language. As a result, employees can ask an AI agent questions about customers, inventory, orders, and financials without navigating menus or learning Business Central's interface. The agent handles the query and returns the answer directly.
Common use cases include:

• Asking an agent to list all customers with overdue balances and trigger a follow-up workflow
• Pulling real-time inventory levels through natural language to support purchasing decisions
• Creating and updating sales orders conversationally without opening the Business Central client

The result is faster ERP data access for every employee across the organization, including those who rarely open Business Central directly. Additionally, organizations see a meaningful reduction in time spent searching for information.

2. Streamlined Administration Through Natural Language

The Business Central admin center MCP server applies the same approach to environment management. Instead of writing scripts, administrators and partners can interact with environment management APIs through tools like Visual Studio Code. They ask questions and issue instructions in plain language.
A partner managing multiple Business Central environments can diagnose upgrade issues, manage sandbox refreshes, and validate configurations without switching contexts or writing PowerShell. In addition, the 2026 Wave 1 release adds configuration validation with one-click fixes, import and export between environments, and telemetry and audit events, making the MCP server a comprehensive administration layer.
For example, common admin tasks include:

• Requesting a sandbox environment refresh through a conversational prompt, with the agent handling the API call
• Diagnosing upgrade failures by querying environment status in natural language
• Validating MCP server configuration and applying recommended fixes with a single confirmation

For organizations with lean IT teams, this kind of efficiency is not a convenience. Indeed, it is a real competitive advantage.

3. A Standardized Foundation for AI Agent Integration

The most significant long-term benefit of the Business Central MCP Server is what it enables for AI agent development. Because MCP is an open standard, any MCP-compliant AI client can connect to Business Central using the same endpoint and tool definitions. Moreover, operations run under user identity and permissions, so governance and compliance requirements are addressed from the start.
Here is what that foundation makes possible:

• Connect a Copilot Studio agent to Business Central to automate purchase order creation based on inventory thresholds
• Use Claude or ChatGPT as MCP clients to surface Business Central insights inside existing team workflows
• Build custom agents that post documents, change statuses, and run business logic through a governed, auditable interface

This standardized foundation accelerates AI adoption across the organization. Furthermore, it means future agent capabilities can be added without rebuilding the integration layer each time.

Real-World Example: Business Central MCP Server in Action

Consider a mid-sized wholesale distributor with 120 employees. Their sales team spends significant time on tasks that should take no effort at all. These include checking whether an item is in stock before quoting a customer, finding out if an order has shipped, or confirming whether a credit hold applies before processing a request. Each of these questions requires logging into Business Central and navigating to the right screen. Multiply that by dozens of queries per day across the sales team, and the total time lost is substantial.
After implementing the Business Central MCP Server and connecting it to a Copilot Studio agent, the team handles these queries through a familiar chat interface. The agent pulls live data from Business Central and responds in seconds. Consequently, the sales team closes faster, customer calls resolve on the first contact, and Business Central navigation drops because employees get answers without navigating the system directly.
Similarly, the finance team benefits as well. An AI agent monitors accounts receivable activity overnight, identifies balances that are past due or approaching credit limits, flags disputes that are pending, and drafts a list of recommended holds for review. What used to take an AR clerk 45 minutes to compile manually is ready before the workday begins.
None of this required custom API development, middleware, or months of integration work. The MCP server provided the connection point, and the AI client handled the interaction. The data stayed inside Business Central, governed by the same user permissions already in place. For a distributor that competes on speed and service, that responsiveness is a genuine differentiator.

How to Implement the Business Central MCP Server: A Phased Approach

At KTL Solutions, we help mid-sized organizations adopt the Business Central MCP Server in a practical, phased approach. This approach delivers early wins while building toward long-term scalability.

Phase 1: ERP Stabilization and API Readiness

Before connecting AI clients, we make sure the Business Central environment is properly structured. Specifically, we assess data quality, custom object documentation, and API surface readiness. We also review which Business Central data endpoints are needed to support the planned use cases and confirm the environment is stable enough to serve as a reliable data source for connected agents.

Phase 2: MCP Server Configuration

We configure the data and admin center MCP servers based on the organization's priorities. First, we identify which data entities will be exposed through the MCP server and configure the appropriate read and write permissions for each. Next, we set up named configurations that are passed as a header at connection time, so different teams or agents can access tailored subsets of ERP data. Finally, audit and telemetry settings are activated to provide full visibility into agent activity from day one.

Phase 3: AI Client Integration and Agent Deployment

With the MCP server configured, we connect the chosen AI clients (whether Copilot Studio, GitHub Copilot, or a custom agent built on another platform) and design initial workflows around the highest-priority use cases. For instance, this might be conversational data access for a sales team, automated purchase order management, or administrative task automation for IT. This is the phase where organizations start seeing measurable efficiency gains.

Phase 4: Expanded AI Enablement and Continuous Optimization

Once initial agents are running reliably, we expand coverage to additional departments and use cases. We refine agent configurations based on real usage patterns, add new data entities as needs evolve, and ensure the MCP server configuration keeps pace with Business Central updates. Ultimately, this phase is about building on early success and extending the value of the MCP server investment across the organization.

Frequently Asked Questions About the Business Central MCP Server

What is the Business Central MCP Server?

The Business Central MCP Server is a Microsoft-built integration layer that uses the Model Context Protocol (MCP) open standard to connect AI tools like Copilot Studio, GitHub Copilot, Claude, and ChatGPT directly to Dynamics 365 Business Central. It allows AI agents to read and write ERP data through natural language, without custom API development.

When was the Business Central MCP Server released?

Microsoft released the Business Central MCP Server as part of the 2026 Release Wave 1 in April 2026.

Which AI tools are compatible with the Business Central MCP Server?

Any MCP-compliant AI client can connect to the Business Central MCP Server. Compatible tools include Microsoft Copilot Studio, GitHub Copilot, Claude, ChatGPT, and custom agents built on MCP-compliant platforms.

Is the Business Central MCP Server secure?

Yes. All operations through the Business Central MCP Server run under the user's existing identity and permissions. Data access follows the same Business Central security model already in place, so organizations do not need to create separate access controls for AI agents.

Does the Business Central MCP Server require custom development?

No. The Business Central MCP Server provides a standardized connection layer that eliminates the need for custom API development or middleware. AI clients connect through the same MCP endpoint, and new use cases can be added without rebuilding integrations from scratch.

Why Mid-Sized Organizations Should Act Now

Most mid-sized organizations already have a capable, cloud-native ERP platform. The Business Central MCP Server is the layer that connects that platform to the AI tools their teams are already using and the agents they are ready to deploy. It removes the friction between a question and an answer, reduces the scripting overhead that has long burdened administrators, and gives organizations a standardized foundation for expanding AI across the business without rebuilding integrations from scratch each time.
At KTL Solutions, we have helped hundreds of mid-sized organizations get more value from their Dynamics 365 investment. The Business Central MCP Server is one of the most practical capability releases in recent memory. The organizations that move on it now will build a real advantage. Because the best ERP is not the one with the most features. It is the one your people can actually use.
Ready to implement the Business Central MCP Server? Contact KTL Solutions to learn how we can help your organization unlock ERP efficiency with AI.
Ready to migrate to Dynamics 365 Business Central? Get a migration quote.

The post How Mid-Sized Organizations Can Unlock ERP Efficiency with the Business Central MCP Server appeared first on ERP Software Blog.

Property management billing requires more than charging each tenant for individual utility usage. Many property expenses are shared across apartments, units, buildings, or contracts, which means the billing system needs a fair and consistent way to allocate those costs. SkyBill supports configurable cost allocation rules that help property managers distribute shared expenses, residual meter differences, and additional charges according to property rules or tenant contract terms.

Key Highlights

• Property management billing includes shared costs that are not tied to individual tenant meters.
• SkyBill allows cost allocation rules to be configured by property, building, or individual contract.
• Shared costs can be allocated by square meters, registered occupants, measured consumption, equal distribution, or custom formulas.
• Different resources, such as heating, wastewater, electricity, and water losses, can follow different allocation rules.
• SkyBill helps property managers handle bulk meter losses and residual differences in a structured, auditable way.

Why Is Cost Allocation So Important in Dynamics 365 Property Management Billing?

Cost allocation is important in property management billing because many operating costs are shared among tenants rather than measured directly for each unit. Unlike standard retail utility billing, where charges are usually tied to a specific customer’s consumption, property billing often includes expenses that support the whole building or property.
Tenants want to understand why they are being charged and how the amount was calculated. When allocation rules are clear and consistent, property managers can support financial transparency, reduce disputes, and build greater trust with tenants.

What Shared Costs Are Common in Property Management Billing?

Shared costs are expenses that benefit multiple tenants, units, or common areas and cannot always be assigned to one specific meter or tenant. In residential and commercial properties, these costs may represent a meaningful portion of total operating expenses.
Common examples include:

• Heating in common areas
• Staircase and hallway lighting
• Elevator electricity
• Shared water systems
• Land lease costs
• Facility maintenance
• Building insurance
• Administrative expenses

Property billing may also need to account for additional differences or losses, such as:

• Losses from bulk meters
• Technical losses between master meters and sub-meters
• Residual consumption that must be redistributed

Because these costs affect both the property owner’s financial reporting and the tenant’s bill, the allocation method needs to be accurate, repeatable, and easy to explain.

How Does SkyBill Allocate Shared Costs Among Tenants?

SkyBill allocates shared costs using configurable rules that can reflect tenant contracts, property policies, and the structure of the building. Instead of forcing property managers into a single allocation method, the system supports multiple approaches depending on how each cost should be distributed.
Typical allocation methods include:

• Proportional allocation based on apartment size, such as square meters
• Allocation based on the number of registered occupants
• Allocation based on measured consumption, such as water, electricity, or heating usage
• Equal distribution among units
• Custom allocation formulas defined by the property manager

This flexibility is especially important because property billing is rarely one-size-fits-all. A residential building, commercial property, or mixed-use property may each require different billing logic depending on how costs are incurred and how tenant agreements are structured.

Where Can Allocation Rules Be Applied in SkyBill?

SkyBill allows allocation rules to be applied at different levels, so the billing logic can match the real structure of the property. This helps property managers avoid manual workarounds when one building, unit group, or contract needs to be treated differently from another.
Allocation rules can be applied at the:

• Property level
• Building level
• Individual contract level

For example, a property manager may need one allocation method for a whole property, another for a specific building, and another for a tenant contract with unique terms. SkyBill’s structure supports that type of variation while keeping the process rule-based and consistent.

Can Different Resources Use Different Allocation Models?

Yes. In SkyBill, different cost categories or resources can follow different allocation methods within the same property. Not every shared cost should necessarily be distributed in the same way.
For example:

This resource-specific allocation model gives property managers more control over how charges are calculated. It is particularly useful in mixed-use buildings or properties with varied unit types, where a single allocation rule may not fairly represent how costs are actually shared.

How Does SkyBill Handle Bulk Meter Losses and Residual Differences?

SkyBill supports structured allocation of bulk meter losses and residual differences between master meters and individual sub-meters. These differences can occur when the master meter reading does not match the total of all individual sub-meter readings.
In property billing, that gap is often referred to as a bulk meter loss. Instead of requiring property managers to calculate and distribute the difference manually, SkyBill can allocate residual values using predefined rules.
Supported approaches include:

• Proportional distribution
• Contract-based rules
• Consumption-based redistribution
• Custom formulas defined by the property manager

This helps ensure that discrepancies are handled systematically. It also reduces the risk of inconsistent manual calculations, especially when residual differences must be included in tenant billing on a recurring basis.

How Does Flexible Allocation Help Property Managers and Tenants?

Flexible allocation and billing accuracy improve:

• Tenant satisfaction
• Dispute frequency
• Financial transparency
• Trust between landlords and tenants

In some jurisdictions, cost allocation can also be connected to regulatory compliance, making consistency even more important.
When a property management billing tool cannot handle flexible allocation rules, property managers may have to rely on spreadsheets or manual calculations. That creates more room for errors, makes billing harder to audit, and can make tenant questions more difficult to answer.
SkyBill addresses this by supporting structured, rule-based allocation logic. For property managers using Dynamics 365 or evaluating property management billing tools, that means shared expenses, residual meter differences, and contract-specific rules can be handled with greater consistency.

How Does SkyBill Improve Dynamics 365 Property Management?

SkyBill extends Microsoft Dynamics 365 Business Central by adding the property and rental billing structures that standard Business Central does not include natively. This includes support for meters, supply points, tariff management, smart meter integrations, shared cost allocation, tenant billing details, tenant portals, and automated debt collection workflows.
Key property billing capabilities supported by SkyBill include:

• Meter and supply point management
• Tariff management
• Smart meter integrations
• Tenant billing details
• Shared cost allocation rules
• Tenant portals
• Automated debt collection workflows
• Billing from first meter read to final settlement

This purpose-built approach is shaped by more than 20 years of experience in ERP and billing, including work with clients managing portfolios from a few hundred units to hundreds of thousands of units. Across those environments, the challenge is often the same: billing data spread across spreadsheets and disconnected systems, with teams spending too much time reconciling information instead of managing properties.
With SkyBill, property and rental billing stays connected to the Business Central platform. For property managers already using or evaluating Dynamics 365 Business Central, that means a more structured and scalable way to manage complex billing without adding a separate system around the ERP.

FAQ About SkyBill and Dynamics 365 Property Management

Q: How does SkyBill allocate shared property management billing costs among tenants?

A: SkyBill allocates shared costs using configurable rules based on property rules or tenant contract terms. Costs can be distributed by square meters, number of occupants, measured consumption, equal shares, or custom formulas.

Q: Can SkyBill use different allocation rules for different types of costs?

A: Yes. SkyBill can apply different allocation methods to different resources or cost categories, such as heating, wastewater, common electricity, or water losses.

Q: How does SkyBill handle bulk meter losses?

A: SkyBill can allocate differences between a master meter reading and the total of individual sub-meter readings using proportional distribution, contract-based rules, consumption-based redistribution, or custom formulas.

Q: Why is cost allocation important in Dynamics 365 property management?

A: Cost allocation affects tenant satisfaction, dispute frequency, financial transparency, regulatory compliance in some jurisdictions, and trust between landlords and tenants.

Q: Does SkyBill support allocation rules at different property levels?

A: Yes. SkyBill supports allocation rules at the property level, building level, and individual contract level, allowing billing logic to reflect the actual structure of the property.

SkyBill Gives Property Managers Structure for Complex Billing

SkyBill is designed to support the real-world complexity of property management billing, where costs are not always tied neatly to individual meters or simple tenant charges. By allowing property managers to configure allocation rules by resource, property, building, or contract, SkyBill helps create a more consistent and transparent billing process.
For organizations evaluating property management billing tools for Dynamics 365, the key question is  whether the system can explain, repeat, and audit those calculations when shared costs, residual differences, and tenant-specific rules are involved.
This is just one aspect of property management billing. Learn what else companies should ask before choosing a property management billing tool for Microsoft Dynamics 365.
To take the next step, contact us at SkyBill today to streamline your billing processes.
 
By SkyBill | www.skybill.eu

The post How to Allocate Shared Costs Among Tenants with Dynamics 365 Property Management appeared first on ERP Software Blog.

The Approval Problem Nobody Talks About

You already know your finance systems are holding the business back. Month-end close takes too long. Reporting is a patchwork of Excel files and manual reconciliations. Your team is spending more time chasing numbers than analysing them. Compliance is becoming a full-time job in itself.
The solution — Microsoft Dynamics 365 Finance — is clear. But getting board approval is a different challenge entirely.
Boards do not approve technology. They approve outcomes. They approve risk reduction. They approve return on investment. They approve strategic alignment. And when a finance transformation proposal lands on a board agenda without those elements front and centre, it gets deferred — or quietly shelved.
This guide is for finance leaders, CFOs, and transformation directors who know what they need but must now build the case that gets a "yes" in the boardroom.

Why D365 Finance Business Cases Fail

Before getting into what works, it is worth understanding why so many technology business cases fail at board level — even when the underlying need is obvious.
They lead with features, not outcomes. A board does not care that D365 Finance has multi-currency consolidation capabilities. They care that your current process for consolidating four subsidiary ledgers takes three weeks and produces numbers the auditors question every year.
They underestimate the cost of doing nothing. The status quo always looks "free" until you quantify it. The real cost of your legacy finance system — in staff time, error correction, audit fees, delayed decisions, and compliance risk — is almost always higher than the cost of replacing it.
They lack credibility. Numbers without evidence are just assertions. Boards that have been burned by over-promised technology projects scrutinise ROI claims carefully. A business case with vague "efficiency savings" and no methodology will be sent back for more work.
They ignore risk. Boards are risk committees as much as they are investment committees. A business case that does not address implementation risk, change management, and mitigation strategies signals inexperience and raises red flags.
They do not connect to strategy. If the board's current strategic priorities are growth through acquisition, international expansion, or ESG reporting — and your business case does not explicitly connect D365 Finance to those priorities — it will feel peripheral rather than essential.
Avoid all five of these mistakes, and your approval odds improve dramatically.

Step 1: Define the Problem in Board Language

Your opening argument must articulate the problem in terms a non-finance board member can feel the weight of. Translate operational pain into business consequence.
Instead of: "Our month-end close process takes 18 days and involves manual journal entries."
Say: "We are providing the board with financial performance data that is already three weeks old when it arrives. In a business making real-time trading decisions, that lag carries material risk."
Instead of: "Our current ERP does not support multi-entity consolidation."
Say: "Each acquisition we make adds six to eight weeks to our year-end consolidation process. At our current growth trajectory, this becomes operationally unsustainable within two years."
The questions to answer at this stage:

• What decisions are being made on incomplete or delayed financial data?
• What regulatory or audit risks exist in the current state?
• What business opportunities are we unable to pursue because our finance infrastructure cannot support them?
• How does the current state limit growth — through acquisition, international expansion, new product lines?

When these answers are concrete and specific to your business, the board will recognise the problem before you have even introduced the solution.

Step 2: Quantify the Cost of the Status Quo

This is the most underused section of any technology business case — and the most persuasive.
The goal is to put a credible number on what your current finance system is costing the business every year. This reframes the conversation: the board is not deciding whether to spend money on D365 Finance. They are deciding how much longer to tolerate the existing cost.
Labour cost of manual processes
Calculate the hours your finance team spends on activities that D365 Finance automates: manual journal entries, intercompany reconciliations, management reporting consolidation, bank reconciliation, VAT return preparation, and audit evidence gathering.
A mid-sized UK finance team of eight people, spending 30% of their time on automatable manual tasks, represents approximately £80,000–£120,000 in annual labour cost that delivers no analytical value.
Cost of errors and rework
Manual finance processes produce errors. Those errors have a cost: rework time, delayed reporting, audit queries, and in some cases regulatory penalties. Even conservative estimates — one material error per quarter at four hours of senior finance time to resolve — add up quickly when quantified.
Audit and compliance cost
External auditors charge for time spent navigating complex, manually maintained financial records. Finance teams at UK businesses commonly report spending two to four weeks per year preparing audit evidence packs. At current audit fee rates, reducing that by 50% through better system-generated documentation has measurable value.
Delayed decision-making
This is harder to quantify but critical to include. What is the cost of a pricing decision made on last month's margin data? What is the risk value of a cash flow forecast that is manually compiled weekly rather than generated in real time? Boards understand opportunity cost — make it explicit.
Scalability ceiling
If your current systems cannot support the next acquisition, the next country launch, or the next regulatory requirement without significant manual workaround — what is that constraint worth? Frame it in terms of the strategic initiatives currently limited or blocked by finance infrastructure.

Step 3: Build the ROI Model for D365 Finance

Now present the investment and the return. A credible ROI model for Dynamics 365 Finance typically addresses five value categories:

1. Process Efficiency and Labour Reallocation

D365 Finance automates accounts payable, accounts receivable, general ledger management, bank reconciliation, fixed asset management, and financial consolidation. UK organisations implementing D365 Finance typically report:

• Month-end close reduction from 15–20 days to 5–7 days
• 60–70% reduction in manual journal entry volume
• AP processing time reduced by 50–65% through automated invoice matching
• Management reporting pack preparation time cut from two days to under two hours

Translate these into FTE hours saved and assign a cost rate. This is your efficiency return.

2. Improved Financial Visibility and Decision Speed

Real-time financial dashboards, built-in Power BI integration, and role-based reporting in D365 Finance give leadership access to performance data that previously required days of manual compilation.
Faster, more accurate financial data improves decisions on pricing, investment, cost management, and capital allocation. While this is difficult to quantify with precision, include a conservative estimate — even a 1% improvement in margin decision-making accuracy across a £50 million revenue business represents £500,000 of value.

3. Compliance and Risk Reduction

D365 Finance is built with UK and international compliance requirements embedded: Making Tax Digital (MTD) for VAT, IFRS and UK GAAP accounting standards, multi-currency consolidation under FRS 102, and audit trail integrity.
Quantify this as:

• Reduction in external audit time (hours × audit daily rate)
• Reduced risk of HMRC penalties through MTD-compliant automated VAT submissions
• Reduced risk of financial restatements, with associated cost and reputational implication

4. Scalability Value

If the business has acquisition, international expansion, or significant growth plans — D365 Finance's multi-entity, multi-currency, multi-language architecture removes the finance infrastructure constraint on those plans.
Frame this as: "Our current system would require X months of manual configuration and Y days of additional finance staff time to onboard each new entity. D365 Finance reduces this to Z weeks with no additional headcount."

5. IT Cost Consolidation

Many UK businesses running legacy finance systems carry significant ongoing IT costs: annual maintenance contracts, bespoke integrations, server infrastructure, and the cost of supporting a system that fewer IT professionals know how to maintain.
D365 Finance, as a cloud-native SaaS platform, consolidates many of these costs into a predictable per-user subscription. Calculate the delta between current total cost of ownership and D365 Finance's projected TCO over a three-year period.

Step 4: Present Total Cost of Ownership — Honestly

Boards that have been through technology implementations before will scrutinise the cost side of your model carefully. Present costs honestly and comprehensively. Understating costs destroys credibility the moment the board's experienced members probe the numbers.
A D365 Finance TCO model for a UK mid-market business should include:
Licensing costs D365 Finance is licensed on a per-user, per-month basis. Full user licences (for finance team members requiring full transactional access) are typically priced at £135–£180 per user per month under current UK Microsoft licensing. Activity licences (for managers requiring read and approval access) are available at lower rates.
Implementation and professional services Implementation cost is driven by scope, complexity, and the number of legal entities, integrations, and custom workflows required. For a UK mid-market business (50–500 employees, 2–5 legal entities), implementation costs typically range from £80,000 to £250,000 depending on scope.
Change management and training Often underestimated. Budget for structured change management, end-user training, and a hypercare period post-go-live. A realistic allowance is 15–20% of implementation cost.
Ongoing support and optimisation Post-implementation support from your Microsoft partner, plus periodic optimisation as the business grows and Microsoft releases new functionality through its regular update cycle.
Present a three-year total cost of ownership figure alongside a three-year cumulative benefit figure. The point at which cumulative benefits exceed cumulative costs — the payback period — is the number boards focus on. For well-scoped D365 Finance implementations, UK businesses typically achieve payback within 18–30 months.

Step 5: Address Implementation Risk Head-On

Every board member who has lived through a failed ERP implementation will be thinking about risk. Address it directly rather than waiting to be asked.
Risk: Implementation overrun on time and cost
Mitigation: A phased implementation approach, a clearly scoped Phase 1 with fixed-price delivery milestones, and a Microsoft-accredited partner with a proven delivery methodology. Reference specific comparable implementations your partner has delivered.
Risk: Business disruption during go-live
Mitigation: Parallel running strategy, data migration validation protocol, and a defined hypercare period with dedicated support resource. Most D365 Finance implementations use a phased cutover approach that significantly reduces go-live risk.
Risk: User adoption failure
Mitigation: Executive sponsorship (the board's own visible commitment), structured change management, role-based training, and a super-user network within the finance team. Adoption risk is greatest when change management is treated as an afterthought rather than a workstream.
Risk: Integration complexity
Mitigation: Early integration mapping as part of the discovery phase, with clear decisions made on which integrations are in scope for Phase 1. D365 Finance's native connectors for common UK business systems significantly reduce custom integration risk.

Step 6: Connect to Board-Level Strategic Priorities

Your final section should connect D365 Finance explicitly to the strategic agenda the board is already focused on. This transforms the proposal from "a finance team request" to "a strategic enabler."
Common board-level strategic priorities and how D365 Finance connects:
Growth through acquisition: Multi-entity, multi-currency architecture means each acquisition can be onboarded to the finance platform in weeks, not months. Consolidated reporting across the group is available from day one.
International expansion: D365 Finance supports over 40 country-specific localisation packages, including VAT and tax compliance, local chart of accounts, and regulatory reporting — removing finance infrastructure as a barrier to new market entry.
ESG and sustainability reporting: Integrated financial and operational data in D365 Finance supports the emerging UK requirement for sustainability-linked financial reporting, including Scope 3 emissions cost tracking and TCFD-aligned disclosures.
Investor readiness / IPO preparation: Audit-grade financial records, IFRS-compliant consolidation, and board-level dashboards position the finance function for the scrutiny of institutional investors or public market readiness.
Digital transformation agenda: D365 Finance sits within the Microsoft ecosystem alongside Dynamics 365 Supply Chain, Business Central, Sales, and the full Power Platform. Approving D365 Finance is not just a finance decision — it is a foundational step in a broader digital transformation programme.

Structuring the Board Paper

Once your analysis is complete, structure the board paper as follows:

1. Executive summary (one page maximum) — problem, solution, investment, return, recommendation
2. Current state assessment — quantified cost of the status quo
3. Solution overview — what D365 Finance delivers, in outcome terms
4. Financial model — three-year TCO, cumulative benefits, payback period, NPV if relevant
5. Implementation approach — phasing, timeline, partner selection rationale
6. Risk register — top five risks with likelihood, impact, and mitigation
7. Strategic alignment — explicit connection to board priorities
8. Recommendation and decision required — clear ask, clear next step

Keep the main paper to eight to ten pages. Supporting detail — vendor comparison, full financial model, implementation methodology — goes in appendices for board members who want to interrogate the detail.

A Note on Partner Selection

Boards will ask: "Why this partner?" Be prepared to answer.
Your Microsoft Dynamics 365 implementation partner is arguably the single biggest determinant of whether your D365 Finance project delivers on its business case. The right partner brings:

• Deep D365 Finance technical expertise and a track record of UK implementations
• Sector knowledge relevant to your business
• A delivery methodology that protects against scope creep and timeline slippage
• Post-go-live support and continuous improvement capability
• A commercial model that aligns partner incentives with your outcomes

Include a brief rationale for partner selection in your board paper — and make sure it goes beyond "we got three quotes." Boards want to know that the partnership is founded on capability and cultural fit, not just price.

Conclusion: The Board Wants to Say Yes

Here is the most important thing to understand about board approval processes: boards are not looking for reasons to say no. They are looking for reasons to say yes with confidence.
A business case for Microsoft Dynamics 365 Finance that quantifies the cost of the status quo, presents a credible ROI model, honestly addresses risk, and connects to strategic priorities gives the board everything it needs to approve with confidence.
The finance function that invests the time to build that case — rather than submitting a technology proposal and hoping for the best — is the finance function that gets the investment it needs, on the timeline it needs it.

Ready to Build Your D365 Finance Business Case?

Dynamics Square UK has helped finance leaders and CFOs across the UK build compelling, board-ready business cases for Microsoft Dynamics 365 Finance — and then delivered the implementations that fulfilled those cases.
Our UK-based team of D365 Finance specialists brings deep sector knowledge, a proven delivery methodology, and a commercial model built around your outcomes — not just your go-live date.
We offer a free Business Case Workshop — a structured two-hour session with one of our senior D365 Finance consultants to help you build the financial model, identify the right ROI levers for your business, and pressure-test your assumptions before they reach the boardroom.

• Call us: +44 203 769 7689
• Email us: info@dynamicssquare.co.uk
• Visit: www.dynamicssquare.co.uk

No obligation. No sales pitch. Just experienced D365 Finance specialists helping you make the case that gets approved.

The post How to Build a Business Case for D365 Finance That Boards Approve appeared first on ERP Software Blog.

Introduction 

Until now, ERP has been the safest bet for accurate, efficient, and scalable business operations. It has served as the single source of truth. Converted chaos into order. Delivered expected results.  
But not anymore. Not in 2026. 
No, the ERP hasn’t failed. It still delivers but lacks intelligence.  
Today’s ERPs are falling short of handling the speed, scale, and complexity of business operations. Businesses witness volumes of unstructured data, a lack of real-time analytics, reliance on human intervention for insights, and integration challenges between multiple modern systems.  
The result? 
Lack of clarity, insights, and predictions.  
This is where data platforms come into the picture. ERP and data platform integration is the perfect ERP modernization strategy that enables analysis, predictions, and decision-making.   
Our thought leadership article explores why ERPs alone are not enough and why data platforms have become a necessity in ERP architecture. We also examine the best ERP and data platform integration approach.

ERP: Goals and achievements 

ERP started as a system to automate business processes. It connected different business functions, gathered data from all, and created a single source of truth.  
All these features facilitated the following: 

• Standardized processes across departments, business units, and geographies without ad hoc variations 
• A unified picture of operations available and accessible to all departments, based on which decisions are made 
• A single source of truth resulting from consistent, accurate data that led to automated reconciliation and trackable audits 
• Better management and control over reporting, financial compliance, and audit trails across geographies and regulatory environments 

With these capabilities, ERP became the operational backbone. Rightly so, because leaders depend on it for operational efficiency and employee productivity. 
So, where’s the problem?  
The problem is not ERP at all. The problem is that ERP alone is not enough for managing enterprise workflows.

Where ERP Falls Short in 2026 

What is missing in ERP design that the ERP modernization strategy can target in 2026? 
Intelligence. Insights. Analytics.  
ERPs were built for structure and control. They recorded what happened. But this is not the perfect design for a data-driven enterprise.  
In the data-driven environment, businesses need to know why it happened and predict what will happen next. This requires insights, predictive analytics, and context, which are critical for modern enterprise decision-making.  
In 2026, ERP falls short in the following areas:

Generating insights instantaneously 

ERPs generate transactional insights, but the speed is slow. Moreover, they don’t capture external signals that can change the data context.  

Supporting multi-system infrastructure 

The current ERP system is one of the many tools in your business ecosystem, be it SaaS, IoT, or other applications. Data from all these systems intersect, for which you need substantial infrastructure that the existing ERP alone cannot support. 

In-depth data analysis 

Most of the organizational data is unstructured. Analyzing it requires AI capabilities and advanced analytics. The existing ERP systems lack this capability, resulting in inefficiencies. 

Real-time intelligence 

Reporting modules in existing ERP systems facilitate compliance, but customization and in-depth analytics are missing. You need transformational, real-time intelligence from exploratory analytics and machine learning processes.  

Incorporation of external data 

Your existing ERP system fails to capture or consider external data points, such as pricing variations, geopolitical events, and weather changes. These impact internal operations, resulting in amendments to business decisions.  
So, ERP ensures process control but lacks insights, intelligence, and clarity.

What Needs to Be Added to the ERP Modernization Strategy 

Data platforms bring the intelligence that the ERP system lacks.  
With ERP and data platform integration, your ERP transforms from a system of record to a system of intelligence.  
Now, you will not merely create and store data (what ERP usually does) but also connect, process, and understand data (what a data platform does). Hence, the shift from “ERP only” to “ERP + data platform strategy” is essential. 
Microsoft Fabric is a unified analytics platform that brings together data integration, engineering, science, warehousing, real-time intelligence, and business intelligence in one environment. It can enable intuitive insights, visual representations, and more informed decisions through capabilities such as the following: 

• Data integration: Connect and orchestrate data from multiple sources in a unified environment
• Data science: End-to-end workflows with data and insights
• Real-Time Intelligence: Ingest, analyze, visualize, and act on streaming data in near real time
• Copilot in Microsoft Fabric: Assists with tasks such as generating queries, summaries, code, and reports to reduce manual effort and speed up analysis
• Fabric IQ and Data Agents: Help users interact with business data more intelligently by grounding responses in a unified business context and governed data sources
• OneLake: Provides a single, unified, logical data lake for the organization
• Data engineering: Facilitates exploration of large volumes of data
• Data Warehouse: Provides scalable SQL-based analytics and storage for structured enterprise data
• Business Intelligence: Enables interactive dashboards, reports, and visual insights
• Databases: Supports operational SQL and NoSQL database scenarios within Fabric 

These capabilities in Microsoft Fabric can help teams bring data together, analyze it more effectively, and support more informed decision-making. Microsoft Fabric helps organizations unlock more value from their data in one unified environment.

ERP and data platform integration

Now that you understand that ERP + data platforms = business intelligence, let us understand the process loop:

This process converts workflow data into insights that facilitate decision-making, growth, and scalability.  
The ERP system is the center of your business. It is connected to all systems and records all processes. It generates transactional data and exports it to the data platform using APIs, connectors, and data pipelines. 
From here, data is stored in the data platform’s central storage layer, Microsoft Fabric’s OneLake, in structured and unstructured formats. This data is combined with data from other systems, processes, and externally ingested sources, then cleaned and structured. After this, the data is optimized for further analysis and scrutiny. 
Power BI in Microsoft Fabric enables data analytics and visualization. You can create dashboards, reports, and performance views based on unified data. Microsoft Fabric also supports real-time intelligence, automated workflows, and AI-assisted analysis to help teams make faster, more informed decisions. These decisions can then influence the business processes managed in ERP. 
Copilot in Microsoft Fabric and emerging agent experiences can support the following with less technical effort: 

• Automated monitoring
• Asking data questions 
• Generating insights
• Creating dashboards
• Identifying inefficiencies
• Supporting faster responses across workflows 

The ERP and data platform integration converts ‘what happened’ from your ERP into ‘why it happened and what will happen in the future’ using the data platform, which you then use for decision-making.

Data ownership post-implementation 

While the integration of ERP and data platforms is critical, do not forget to define: 

• Who owns the data, IT or the business units where the data is generated?
• Who validates reports and dashboards?
• Who is responsible for data quality, access, and permissions, and the necessary compliance requirements
• What’s the governance plan? 

A hybrid ownership model is the typical setup, with IT handling the infrastructure, security, and governance, while business units handle the reporting, analytics, and decision-making.  
Microsoft Fabric’s OneLake helps define the workspace roles and their access to have clarity on who can do what.

Business Benefits of ERP + Data Platform Strategy 

This modern ERP architecture with a cloud data platform helps with the following: 

Real-time clarity 

AI-driven ERP data integration provides an in-depth understanding of what is happening in your business, what it leads to, and why it is necessary for business growth in real time. Copilot-enabled insights further support contextual understanding, driving proactive decisions instead of reactive ones. 

Better planning 

You can predict the future based on real-time and historical data. The data platform enables the prediction of changing demands, trending economic variables, and business disruptions affecting operations. With this data, you can plan production, resource allocation, delivery timelines, and capital distribution.   

Strong financial strategies 

ERP and data platform integration allows 360-degree visibility of present operations, performance forecasts, and business plans. Thus, you can evaluate timelines, costs, and resource usage in real-time and revise financial strategies accordingly.  

Continuous optimization 

You can identify loopholes in the process in terms of cost, timing, and process inefficiencies. This gives you enough time to fix them before the situation worsens. In particular, AI-assisted analysis in Microsoft Fabric can support more proactive operational optimization, helping reduce working costs, resource wastage, and rework. 

Faster and consistent decisions 

You can determine the best courses of action to achieve the desired outcomes. Moreover, shared data across teams keeps them aligned and working towards common goals. This results in quality decisions, faster execution, and maximum operational efficiency.

Challenges of ERP and Data Platform Integration 

Since this ERP modernization strategy is finding many takers in 2026, you must be aware of the challenges beforehand to prepare and plan: 

Governance 

Creating the enterprise ERP data architecture is not straightforward. Control over data sharing, system usage, and process definition is essential. More so when multiple systems are integrated, and data is centralized. You need to answer questions on the following:

• Accessibility and permissions
• Private data security
• Data sharing and handling
• Necessary compliance with regulations and standards
• Decision rights and responsibilities 

Defining these rules and principles and adhering to them is a challenge.  

Competence 

An individual with expertise in data engineering, data science and analytics, and business intelligence can derive maximum benefits from enterprise data platforms. Experience also matters, and finding such talent remains a challenge. 

Inconsistent data 

Another data-related challenge for enterprise ERP data architecture is data consistency. The formats, structures, and categories of data from different systems, processes, and external sources vary. This inconsistency requires proper master data management, including cleaning, standardization, and governance. 

Change management 

Technology adoption and deployment are still manageable. But managing change internally is a significant challenge. It involves training employees on the new enterprise data platforms, motivating employees to accept the change, and navigating the evolving organizational dynamics. It is a business transformation requiring complete acceptance and continuous learning to derive benefits.  

Legacy system constraints 

You may already operate on a legacy ERP system customized to business needs. Integrating the data platform with the ERP system requires work on the logic, coding, and connectors, which is challenging. Proper assessment of the existing ecosystem’s compatibility with the new data platform is essential. 

Adopting the Best ERP and Data Platform Integration Approach 

ERP and data platform integration is complex. The risks of this ERP modernization strategy are also high. It is not just a solution deployment but an architectural design, which, if done wrong, can harm your efficiencies. So, you must navigate this phase carefully to maximize business value. 
Making your ERP more insightful and a stronger contributor to business decisions is a strategic move, for which an enterprise ERP data architecture is necessary. But its success depends on your choice of the right implementation partner. 
Intech Systems is a Microsoft Solutions Partner and AI transformation partner with deep expertise across ERP, analytics, and Microsoft technologies. We help businesses move from fragmented systems and delayed reporting to connected operations, trusted data, and faster decision-making. 
Intech Systems brings hands-on experience in integrating ERP with data platforms and shaping enterprise data foundations for long-term scale. Our Microsoft Fabric expertise spans 500+ clients and 1000+ successful implementations across geographies and industries, helping businesses improve visibility, strengthen governance, and turn operational data into actionable insight. 
From assessment to implementation, Intech helps define the right data strategy, connect ERP with surrounding systems, build dashboards and reporting layers, establish governance and security models, and enable teams to adopt the new way of working with confidence. Our 2-week Microsoft Fabric implementation services are designed to help businesses translate data challenges into measurable business outcomes faster. 
We help modernize ERP with data platforms through a practical, phased approach that connects strategy, architecture, implementation, and business adoption: 

• Business assessment focused on wrong decisions, visibility gaps, and real-time intelligence needs
• Designing the enterprise ERP data architecture, involving data extraction from ERP and integration with other systems
• Defining the core data principles, including data pipelines, data standards, governance policies, security and access controls, and data quality checks
• Cross-functional insight generation and reporting through dashboards, visualizations, and self-service analytics
• Feeding insights and analytics back into workflows and decisions to derive value for the now data-driven business 
• Running the pilot phase and scaling

Conclusion

An ERP modernization strategy is not just about technology, people, or process. It is an architecture-driven consideration that has gained importance in 2026. Until now, it was ERP and other business systems such as CRM, inventory management, and more. 
But now, businesses have realized the challenges of using ERP without a data platform. There is no visibility into the full picture, organizations miss growth opportunities, data usability is minimal, and responses are reactive and delayed. Data platforms complete the picture with insights, context, unified views, predictive analytics, and AI depth. So, ERP and data platform integration has become a major business transformation priority. 
Want to turn your ERP into a more intelligent platform? 
Explore the all-in-one analytics platform Microsoft Fabric with AI-backed intelligence. Read more here: https://intech-systems.com/ai-solutions/ai-with-data-analytics-solutions/microsoft-fabric/.  
Get started with our Microsoft Fabric 2-week implementation offer to turn data into decisions. Sign up here: https://intech-systems.com/services/data-engineering-analytics-services/.  
FAQs 

1. Why is ERP alone no longer enough for enterprises?
   ERP records transactions well, but it does not provide the full depth of intelligence modern businesses need. A data platform adds context, analytics, and predictive insights for faster and smarter decisions.
2. What does a data platform add to an ERP system?
   A data platform connects structured and unstructured data, supports real-time analysis, and helps teams move from reporting what happened to understanding why it happened and what may happen next.
3. How can Microsoft Fabric support ERP modernization?
   Microsoft Fabric brings together data integration, storage, analytics, and AI in one environment. This helps businesses unify data, generate insights faster, and improve decision-making across teams.
4. Why should businesses work with Intech Systems for ERP and data platform integration?
   Intech brings hands-on Microsoft Fabric expertise, implementation experience across industries, and a practical approach to turning business problems into measurable outcomes. That makes the journey faster, more structured, and lower risk.
5. What makes Intech Systems the right Microsoft Fabric partner?
   Intech combines data strategy, architecture, governance, and implementation support in one engagement. This helps businesses move from scattered data to trusted insights with clarity and confidence.

The post Why ERP Alone Is No Longer Enough for Enterprises: The Need for ERP and Data Platform Integration appeared first on ERP Software Blog.

In today's fast-paced business environment, customer expectations are evolving faster than ever before. Customers demand personalized, timely, and relevant interactions across all touchpoints. Traditional Customer Relationship Management (CRM) systems are no longer enough to meet these growing expectations. 
Historically, CRM systems have primarily been used to: 

• Store customer data 

• Track customer interactions 

• Manage sales pipelines 

While these functions are crucial, they are only the starting point for managing customer relationships. To truly stand out in the market, businesses need to move beyond traditional CRM capabilities and leverage the power of Agentic CRM. 
Agentic CRM goes beyond simply managing customer data—it transforms how businesses engage with customers by predicting behavior, automating engagement strategies, and personalizing experiences in real-time. Agentic CRM in Dynamics 365 Customer Engagement uses AI agents to analyze data, recommend actions, and trigger workflows automatically, enabling organizations to not just react to customer needs, but proactively engage and delight them. 
In this blog, we’ll explore how Agentic CRM helps businesses transform their customer experience and drive measurable results like improved satisfaction, higher retention rates, and increased revenue. 
 
Traditional CRM vs. Agentic CRM: The Evolution of Customer Experience 
Traditional CRM: Storing Data and Tracking Interactions 
Traditional CRM systems are designed primarily for: 

• Storing customer information: This includes contact details, purchase history, interaction logs, and more. 

• Tracking customer interactions: CRM systems help sales teams keep records of customer conversations, emails, meetings, and touchpoints, ensuring that customer information is organized and easily accessible. 

While these functions are essential for businesses to maintain relationships, they are limited in scope. Traditional CRM systems are often reactive—they store and organize data but don't provide actionable insights or enable proactive engagement. 
The Rise of Agentic CRM: Proactive and Intelligent Engagement 
Agentic CRM represents a shift in how businesses engage with their customers. Instead of simply tracking interactions, Agentic CRM anticipates customer needs, personalizes experiences, and automates actions. This makes it possible to deliver exceptional service that not only meets but exceeds customer expectations. 
Key Features of Agentic CRM: 

• Predicts customer behavior: By analyzing past interactions and using machine learning, Agentic CRM can predict what customers are likely to need next—whether it's a product recommendation, an upsell opportunity, or personalized service. 

• Automates engagement strategies: Agentic CRM automates routine engagement tasks such as sending follow-up emails, scheduling meetings, and triggering personalized offers, ensuring that customers receive timely communication without the need for manual intervention. 

• Personalizes experiences: AI agents analyze customer data to tailor each interaction to the specific needs, preferences, and behavior of the customer, creating a truly personalized experience. 

With Agentic CRM, businesses can engage with customers in a more intelligent, data-driven way that aligns with their needs and expectations, ensuring that no opportunity is missed. 
 
How Agentic CRM Works in Dynamics 365 Customer Engagement 
Dynamics 365 Customer Engagement, powered by Agentic AI, offers organizations the tools they need to build a truly intelligent and proactive CRM system. Here’s how Agentic CRM works: 

1. AI Agents Analyze Customer Data

AI agents in Dynamics 365 Customer Engagement continuously analyze customer data, including historical interactions, purchasing patterns, and demographic information. This analysis allows AI to identify trends, preferences, and opportunities that can be used to drive more relevant and timely engagement. 

1. AI Recommends Actions

Based on the data analysis, Agentic AI provides actionable insights to sales, marketing, and customer service teams. For example: 

• Sales teams may receive recommendations for the best times to follow up with customers or cross-sell related products. 

• Marketing teams can target customers with personalized offers based on their browsing or purchasing history. 

This ensures that businesses are always engaging with customers in the most relevant and effective way. 

1. Automated Workflow Triggers

With Agentic CRM, workflows can be triggered automatically based on real-time customer data. For example: 

• When a customer abandons a shopping cart, an automatic email can be sent offering a discount or reminding them of the items left behind. 

• After a support ticket is resolved, the system can automatically send a satisfaction survey or offer a follow-up recommendation based on the customer’s previous issues. 

This automation allows businesses to deliver consistent, timely, and personalized communication without manual intervention, improving customer satisfaction and engagement. 
 
The Results: Improved Customer Satisfaction, Higher Retention, and Increased Revenue 
The benefits of implementing Agentic CRM go beyond just automation. By leveraging AI-driven insights, personalized experiences, and proactive engagement, businesses can see tangible improvements in key performance metrics: 

1. Improved Customer Satisfaction

By anticipating customer needs, automating responses, and providing personalized offers, Agentic CRM helps businesses improve customer satisfaction. Customers appreciate relevant, timely interactions that align with their preferences and behaviors, leading to increased loyalty and brand advocacy. 

1. Higher Retention Rates

With the ability to engage customers proactively, Agentic CRM helps businesses retain customers over the long term. Personalized offers, timely follow-ups, and automated loyalty programs encourage repeat business, reducing churn and fostering long-term relationships. 

1. Increased Revenue

By automating upsell and cross-sell opportunities, Agentic CRM helps businesses increase average order value and boost revenue. Additionally, AI-driven recommendations ensure that customers receive the right offers at the right time, leading to higher conversion rates and improved sales performance. 
 
At DAX Software Solutions: Transforming Customer Experience with Agentic CRM 
At DAX Software Solutions, we specialize in helping organizations implement Agentic CRM within Dynamics 365 Customer Engagement to create intelligent, proactive CRM systems that drive better customer experiences. Our approach includes: 

1. Assessing your CRM needs to identify opportunities for AI integration. 

1. Implementing Agentic CRM to automate workflows, predict behavior, and personalize experiences. 

1. Integrating CRM systems with other business functions to ensure seamless data flow and optimized decision-making. 

By working with DAX, businesses can unlock the full potential of Agentic CRM to deliver exceptional customer experiences, increase retention, and drive revenue growth. 
 Conclusion 
The traditional approach to CRM—focused on tracking data and managing interactions—is no longer sufficient to meet the evolving demands of today’s customers. Agentic CRM in Dynamics 365 goes beyond simply managing customer data; it enables businesses to predict behavior, automate engagement, and personalize experiences in real-time. 
At DAX Software Solutions, we help organizations build intelligent CRM systems that are not just reactive, but proactive and data-driven. By leveraging Agentic CRM, businesses can improve customer satisfaction, increase retention, and drive revenue growth. 
Because customer experience is no longer a function—it is a strategy. 
Contact us: https://daxsws.com/contact-us 

The post Customer Experience Transformation with Agentic CRM  appeared first on ERP Software Blog.

Listen to the Podcast

Business Central Quotes and Production BOMs: Why They Don't Match

There is a version of this story in nearly every Business Central manufacturing business that builds products to customer specification. A salesperson takes a requirement, works through the options with the customer, and produces a quote. The quote goes out. The order comes in. And somewhere between the sales order and the shop floor, the details change.
Sometimes it's a small thing, a finish that was swapped, a component quantity that doesn't match what was sold. Sometimes it's more significant: a production BOM that reflects a standard configuration rather than the one the customer actually ordered. The result is the same either way. Manufacturing builds something. Sales sold something else. Someone has to reconcile the difference, and that someone is usually doing it manually, after the fact, under pressure.
This is the configure-to-order problem. It's common, it's costly, and it tends to get worse as product complexity increases.

Why the Gap Exists

The root cause is almost always a broken or missing handoff between the sales process and the production planning process. In businesses where products are straightforward, a fixed catalog, limited variants, predictable configurations, this handoff is easy. The sales order references a standard item. The BOM for that item already exists. Production picks it up and gets to work.
Configure-to-order is different. The customer is selecting from options. The finished product doesn't exist yet as a standard item. Its BOM and routing need to be assembled from the selections made during the sales process. And in most businesses without a formal configuration tool, that assembly happens manually, either by a salesperson who also knows enough about production to build the BOM themselves, or by an engineer who takes the sales quote and rebuilds it from scratch.
Both approaches work at small scale. Neither scale reliably. As product complexity grows, more options, more combinations, more rules about what can and can't be ordered together, the manual process becomes a bottleneck and an error source simultaneously.
The specific failure modes tend to cluster around a few recurring patterns:

• The BOM reflects the base item, not the configured item. A production BOM was created from a template and never updated to reflect the specific options on this order. Manufacturing builds the standard product. The customer receives something different from what they ordered.
• The quote and the BOM were built independently. Sales produced a quote. Engineering built a BOM. Both are internally consistent. They don't match each other because they were created by different people from the same customer conversation, interpreted differently.
• A rule that should have prevented a bad combination didn't. The salesperson selected options that aren't physically compatible. Nothing in the system flagged it. The error reaches production.
• Costs on the quote don't match costs in the system. The quote was built with one set of component costs. The BOM was generated with another. Finance reconciles the difference at month end.

These are not technology failures in the sense that the software broke. They are process failures enabled by the absence of a system that connects the sales configuration directly to the production output.

The Real Cost of Manual Configuration

The visible cost of this problem is re-work. A BOM that must be corrected before production can start. A production order that must be revised mid-run. A customer who receives the wrong product and has to be managed through a correction.
The invisible cost is harder to measure but probably larger. It lives in the time engineers spend rebuilding BOMs from sales quotes that should have generated them automatically. It lives in the caution that builds up around complex orders, the informal rule that certain products need to be reviewed by someone in engineering before they go to production, because experience has taught the team not to trust the handoff. It lives in the quotes that take longer than they should because the salesperson is waiting on confirmation that the configuration they've proposed is actually buildable.
None of this shows up as a line item. All of it shows up in capacity, throughput, and margin.
There is also a quoting cost that often goes unexamined. A salesperson who has to rely on an engineer to validate every complex quote is a salesperson whose response time is limited by engineering availability. In competitive markets, quote speed matters. The business that can respond to a complex configuration request in hours rather than days has a structural advantage over the one that can't.

What a Properly Connected System Does Differently

The configure-to-order problem is solvable. The solution requires connecting three things that are currently disconnected in most businesses that experience it: the option selection process, the BOM generation process, and the rules that govern what combinations are valid.
When these are connected, the sales process and the production process stop being two separate workflows that have to be manually reconciled. They become a single workflow. The salesperson selects options. The system validates the combination against defined rules in real time. The BOM and routing are generated automatically from those selections. The production order is created with the correct configuration already embedded. There is no handoff to manage because the handoff is built into the process.
This changes several things at once.
Quote accuracy improves because the same logic that generates the BOM governs what the salesperson can select. If a combination isn't valid, it's excluded at the quoting stage, not discovered in production. The salesperson doesn't need to know the production implications of every option choice, the rules handle that.
Quote speed improves because the salesperson is no longer waiting on an engineer to validate the configuration or build the BOM. The system does it. Response time is limited by the conversation with the customer, not by the capacity of the engineering department.
Cost accuracy improves because the BOM is generated from the same selections that generated the quote. Component costs flow from the configuration. There is no separate cost build to maintain in parallel.
And perhaps most importantly, the information that manufacturing receives is the information that sales produced, not an approximation of it, not a reconstruction of it, but the actual configured BOM derived from the actual customer selections.

What to Look for in a Configuration Tool

Not every configuration tool is the same, and the differences matter more than vendors typically acknowledge. A few capabilities are worth evaluating carefully before committing to an approach.
Rule enforcement at the point of selection, not after.
The value of rules is that they prevent bad configurations from being created, not that they flag them after the fact. A tool that validates after submission still requires someone to correct the quote and resubmit. A tool that enforces rules during selection prevents the problem from being created at all.
Automatic BOM and routing generation from the selected options.
This is the core capability. The BOM should be a direct output of the configuration, not something that has to be built separately. This includes handling both production BOMs and assembly BOMs, depending on the manufacturing model, and correctly generating routings for production-type items.
Cost calculation from the configuration.
The configured item's cost should be calculated from the options selected, including component costs, resource costs, and any applicable waste or scrap factors. This cost should be consistent between the quote and the BOM, derived from the same source, not maintained separately.
Support for complex product hierarchies.
Products with sub-assemblies that are themselves configurable require a tool that can manage nested configurations. The cost and attribute logic needs to remain coherent through the hierarchy, parent configuration settings should propagate correctly to sub-configurations, not require manual replication.
Integration with planning.
A configured item that feeds correctly into MPS and MRP is a configured item that can be planned. The tool should connect naturally to Business Central's planning functions, so that new configured products are visible to the planning engine from the moment the order is created.

Where Product Configurator Fits

Product Configurator from Insight Works is built specifically for Microsoft Dynamics 365 Business Central and addresses the configure-to-order problem within the platform businesses are already running on. It handles both production and assembly BOM types, enforces configuration rules at the point of selection, generates BOMs and routings automatically from the options chosen, and integrates with standard Business Central MPS and MRP.
It is designed to be approachable for businesses of varying size and product complexity, not a full CPQ platform requiring a lengthy implementation, but a focused tool that solves the specific problem of connecting sales configuration to production output within Business Central.
For businesses managing configure-to-order products and experiencing the gap between what sales quotes and what production receives, it is the closest available answer to the problem described in this article.
More information is available at CPQforDynamics.com. Businesses looking to implement can connect with any of Insight Works' 750+ global Microsoft Partners.

The post Business Central Quotes and Production BOMs: Why They Don’t Match appeared first on ERP Software Blog.

"With Tigunia, I can take a vacation for the first time in three years and know operations will keep running smoothly." 
John White, IT Manager, Merrick Hardwoods 

The Problem 

The Solution  

Recognizing the need for change, Merrick Hardwoods chose Tigunia to lead a comprehensive modernization effort, and started with the most pressing risk. Tigunia migrated Merrick from its vulnerable on-premise environment to a secure, cloud-based Microsoft Dynamics 365 Business Central platform, eliminating the infrastructure weaknesses that had allowed ransomware to take hold. From there, the team worked closely alongside Merrick Hardwoods to untangle persistent EDI challenges, improving both the accuracy and speed of data exchanges and clearing up the bad data issues that had been quietly slowing down the pellet mill division. 

The Result 

Since partnering with Tigunia, Merrick Hardwoods has experienced a fundamental shift in how confidently and efficiently the business operates. The move to Business Central's cloud environment closed the security gaps that had plagued the organization for years, and Merrick has not experienced a single ransomware incident since. Beyond security, the impact has been felt across the entire operation: 

• Improvements to the prepayment invoice process and key workflows prevented up to $100,000 in potential lost revenue. 
• Automation of internal processes reduced manual errors and improved day-to-day efficiency across all six companies. 
• Resolving EDI issues eliminated the time lost chasing bad data, particularly in the pellet mill division, their largest profit center.

Perhaps the most telling measure of success is this: for the first time in three years, Merrick's sole IT manager was able to take a vacation, fully confident that operations would continue without interruption. That kind of peace of mind is only possible when the right partner is in your corner. 

"Tigunia doesn’t just fix problems; they anticipate them and keep our business running without interruptions." 
John White, IT Manager, Merrick Hardwoods

The post Merrick Hardwoods Gains Over $100K in Efficiencies with Tigunia’s Business Central Cloud Migration and IT Partnership appeared first on ERP Software Blog.

For many organizations using Business Central, automated emails play a major role in daily operations. Payment confirmations, invoice notifications, customer portal alerts, collections reminders, and workflow communications are constantly being generated throughout the day. And depending on which ISVs you have, you may have additional emails being generated out of the system.
But as email volume grows, many finance teams are seeing more important emails being delayed because they’re in line behind less important emails.
A payment receipt likely needs to be delivered immediately. A collections reminder may be important, but it usually does not require the same level of urgency. When all emails are processed through a single queue with identical priority, delays can occur, especially during periods of heavy processing.

The Problem with One Large Email Queue

Many Business Central environments rely on Job Queue Entries to process automated tasks and communications. When a single queue is responsible for all outbound emails, organizations may experience:

• Delayed customer notifications
• Slower delivery of payment confirmations
• Backlogs during high-volume processing periods
• Reduced visibility into which emails are being processed first
• Competition between operational and customer-facing communications

This becomes even more noticeable as businesses scale automation efforts across AR, invoicing, customer portals, and workflow notifications.

Prioritizing Emails in Business Central

Not all communications have the same impact. High priority emails are the ones that customers anticipate receiving immediately after they take an action –

• Payment confirmation emails
• Order confirmation or shipment alerts
• Customer portal username or password reset emails

These messages are time-sensitive and should be delivered without delay to ensure a smooth customer experience.
Standard priority emails, on the other hand, are not typically expected in real time and can be processed within a normal queue. These include:

• Collections reminders or follow ups
• Scheduled notifications

Separating  high priority and standard priority emails into different processing queues can improve both customer experience and your overall system performance and responsiveness.

Out of the Box Capabilities in Business Central

Out of the box, Dynamics 365 Business Central does not include a dedicated email queue management system with multiple priority queues. However, it does include several native queue and scheduling mechanisms that handle automated email-related processes. This is done through job queue entries that are used to

• Send workflow notifications
• Process scheduled reports
• Run background tasks
• Trigger automated email-related processes

The Email Outbox in Business Central provides visibility into emails that are pending delivery.  While this is not a configurable priority queue, it does allow users to monitor pending messages and their sending status.
 

iPayments Add-On App for Business Central

With the iPayments App for Business Central, you gain the functionality to prioritize emails in your AR process. This provides greater flexibility and control, enabling faster customer communication and better system performance.
iPayments helps Business Central users enhance their accounts receivable processes directly within the system. iPayments supports streamline payment processing, automate collections workflows, a real-time customer portal, and improved cash flow acceleration.
Pricing for iPayments starts at $350/month
 

Learn more about how iSolutions can help fill the gaps in your Business Central environment by streamlining your entire accounts receivable process – reach out today.

The post Why Email Queue Management Matters in Microsoft Dynamics 365 Business Central appeared first on ERP Software Blog.

For many equipment rental companies, long-used rental management systems have quietly shifted into a state of slow updates, limited enhancements, and unclear product roadmaps. 

When a platform stops evolving, it eventually slides into “maintenance mode,” a pattern where no new improvements or updates are made to the system. And that’s when the real business risks begin. 
Read on to learn how rental software that’s nearing end of life can impact your equipment rental business, and how moving to STAEDEAN'S Equipment Rental Solution embedded in Microsoft Dynamics 365 ERP system can protect your business operations and enable growth. 

Maintenance Mode Creates Hidden Inefficiencies 

Over time, equipment rental businesses relying on outdated or semi-sunset systems start feeling the strain: 

• Outdated tools slow down daily operations 
• Manual data transfers introduce delays and errors 
• Teams struggle to plan due to limited equipment visibility leading to underutilization 
• Fixed pricing, instead of dynamic pricing, makes revenue management harder  
• No development roadmap makes future planning uncertain

These challenges drain productivity and create barriers that limit growth, efficiency, and profitability. That’s why many equipment rental organizations are now reassessing their technology foundations and exploring what a modern cloud rental management solution can deliver, especially as more companies with legacy systems move toward upgrading to D365.

A Clearer, More Stable Path: A Modern Dynamics 365 Rental Management Solution

As legacy systems wind down development, rental leaders are choosing stability, scalability, and innovation. A cloud-based, rental-specific rental management solution that is continuously enhanced—such as STAEDEAN Rental Management, embedded in Microsoft Dynamics 365 Finance and Supply Chain Management (F&SCM)—provides the reliable foundation needed for future growth.

STAEDEAN Rental Management extends Microsoft Dynamics 365 F&SCM with rental-ready processes that enable your teams to manage daily operations, finance, and supply chain on a single, connected platform. The two systems work together as a single solution, giving you a central location for all rental and business data.
It’s a single, connected solution designed to help equipment rental companies modernize without disruption. The combination of Microsoft’s enterprise ERP with proven rental-ready capabilities gives your business:

• Unified rental, finance, and logistics
• Fast, reliable cloud performance
• Modern, intuitive planning, billing, and mobility solutions
• A scalable system for multi-country operations
• A proven, stable, and future-ready solution backed by 20+ years of rental expertise

Curious how this works in practice? Explore the solution through a short, self-guided experience.

Explore STAEDEAN Rental Management

STAEDEAN Rental Management stands out because it delivers rental-specific capabilities directly within Dynamics 365, giving teams everything they need in one connected platform. And the impact becomes even clearer when you see how it replaces the long-standing limitations of legacy systems.

How STAEDEAN Rental Management Helps You Move Beyond End-of-Life Systems

Legacy systems or systems that are approaching end of life leave too many gaps for rental businesses to fill on their own. STAEDEAN Rental Management closes those gaps with a modern, Dynamics 365–based platform built to support every stage of the rental lifecycle. Here’s how it solves the issues outdated systems often create.

1. A Clear, Low-Risk Migration Path

Many rental companies hesitate to move systems because migrations feel risky. With STAEDEAN Rental Management, embedded in Dynamics 365 F&SCM, you get:

• Rental-specific processes
• Standard finance, supply chain, and rental integration
• A platform with continuous Microsoft innovation
• A partner with two decades of rental expertise and providing stable and strategic upgrade

2. Real-Time Data That Eliminates Manual Checks

STAEDEAN Rental Management enables real-time synchronization across rental, finance, and supply chain functions, eliminating the need for middleware and manual checks. Decisions become faster and more reliable with accurate, real-time data.

3. Cloud Performance that Keeps Teams Productive

Older systems with slow response times can frustrate users and force them to workarounds. Running in the Microsoft Azure cloud, STAEDEAN Rental Management delivers the reliability, performance, and scalability needed for multi-branch and multi-country operations, ensuring teams stay productive wherever they work.

4. Modern Planning Capabilities for Higher Fleet Utilization

Without modern planning tools, teams often rely on spreadsheets to track equipment availability and maintenance schedules. STAEDEAN Rental Management provides a visual global planner with drag-and-drop scheduling, showing what’s available, in service, or in transport at a glance. This leads to better asset utilization and fewer operational bottlenecks.

5. Mobile Check-In/Check-Out That Eliminates Paper and Errors

Paper-based check-in and check-out workflows slow operations and introduce errors. There’s no automation or integration with contracts and invoicing.  STAEDEAN Rental Management’s mobile app digitizes every step—from photo capture to digital signatures and AI-driven damage comparison—and syncs directly with contracts and billing. As a result, users experience faster transactions and greater accuracy across all branches.

6. Flexible, Revenue-Friendly Billing

Outdated systems limit billing options. STAEDEAN Rental Management supports  flexible billing models, including subscription-based, period-based, and consumption-based rates, that automatically recalculates charges when contracts change to ensure accurate, predictable revenue.

7. Real Mobile Productivity, Even Offline

Mobile access is no longer optional. Field teams need to capture and update data in real time, even when offline. STAEDEAN Rental Management offers offline-ready mobile apps for service, logistics, and inspections, which automatically sync with Dynamics 365.

8. Unified Reporting for Multi-Country Operations

For dealers operating in multiple countries, fragmented data leads to incomplete visibility. STAEDEAN Rental Management supports multi-company and multi-country setups with consolidated reporting. Users gain unified Microsoft Power BI insights for fleet, revenue, and utilization, enabling a single global view of performance.

Move Forward with Confidence

Rental management systems in maintenance mode make it harder to modernize, stay efficient, and prepare for the future. STAEDEAN Rental Management gives equipment rental companies a modern, cloud-based platform that strengthens operations today while supporting tomorrow’s growth.
With standardized rental processes, automation that removes manual work, and unified reporting across regions, teams can finally operate on a connected foundation that’s built for scale.
Backed by more than 20 years of rental industry expertise, STAEDEAN Rental Management provides a fit-to-standard solution designed to grow with you.
To help you evaluate the solution, we’ve created a blueprint that outlines STAEDEAN Rental Management’s capabilities and estimated pricing.

The post Still Running Your Rental Business on Software That Can’t Scale? appeared first on ERP Software Blog.

Most warehouse problems look like execution problems. A pick goes to the wrong bin, a shipment goes out late, a cycle count comes back with discrepancies no one can explain. But trace those issues back far enough, and they almost always land in the same place: the team was working from information that was incomplete, delayed, or disconnected from the system of record.
Microsoft Dynamics 365 Business Central and Power BI, used together, address this at the source.

What Each Platform Brings

Business Central handles the operational layer: bin-level inventory control, directed put-away and pick strategies, barcode scanning through mobile devices, and real-time transaction posting. When stock moves, the system records it immediately, flowing into inventory valuation, order fulfillment status, and procurement signals at the same time. Advanced warehousing unlocks zone and bin management, FEFO picking for lot-tracked items, cross-docking, and automated replenishment. There are no synchronization jobs between a WMS and ERP, no reconciliation step before month-end, and no lag between what the floor sees and what management reports.
Power BI fills the visibility gap that Business Central's native reporting leaves open. Microsoft's purpose-built Power BI Inventory app for Business Central connects directly to the ERP's data model, surfacing warehouse data in dashboards that different roles can act on. Supervisors track picking speed and shipment status. Procurement managers monitor stock-on-hand against demand signals. COOs review inventory turnover without waiting for an end-of-week report. Because dashboards update as transactions post, the data reflects what is happening on the current shift, not a summary from yesterday.
Beyond standard reporting, teams can build custom views tailored to their workflows. A warehouse capacity dashboardmight track bin utilization by zone and flag items sitting in storage past a defined threshold. A fulfillment dashboard might show order accuracy by picker, on-time shipment rate by carrier, and open orders aged beyond the target lead time.

Where Efficiency Gains Show Up

Inventory accuracy improves when picks are validated by barcode scanning against the expected item and bin before confirming the transaction. Mistakes get caught before they become shipment errors, and cycle count discrepancies shrink because inventory movements post in real time.
Order fulfillment speeds up when staff follow directed pick paths rather than searching for items. Power BI dashboards let supervisors spot bottlenecks before backlogs develop. Distributors who connect Business Central inventory data to Power BI can also visualize stock levels across locations, identify slow-moving items, and base purchasing decisions on actual demand patterns rather than estimates, bringing carrying costs down directly.

What to Get Right Before You Start

The integration is technically straightforward, but dashboards are only as good as the data behind them. Companies migrating from older systems often find that inconsistent bin structures, item categorizations, or cycle count processes surface quickly in Power BI. A well-configured Business Central warehouse setup with clean data, defined bins, and trained staff using barcode scanning is the foundation everything else builds on.
For most distributors, picking efficiency, on-time shipment rate, inventory accuracy, and stock turnover are the right starting metrics. Additional layers can follow as the team gets comfortable acting on what they see. Most Power Platform implementations can be extended to include custom warehouse dashboards without significant development work.
For the full breakdown, including implementation considerations and where distribution companies see the most impact, read the complete article on ACE Micro's website. Ready to improve your warehouse efficiency? ACE Micro works with distribution companies to configure, implement, and support the full Microsoft stack. Connect with the ACE Micro team today to start with a structured assessment of your operation.
 

The post Improving Warehouse Efficiency with BC and Power BI appeared first on ERP Software Blog.

How Growing Businesses Can Build a Customer Portal with Power Pages and Business Central for Less Than You Think

Building a Customer Portal for Business Central has become essential for growing companies. Mid-sized businesses sit at a unique crossroads. Customers, vendors, and partners now expect self-service access to order status, invoices, and account information. They want it anytime, on any device. Meanwhile, internal teams stretch thin answering the same repetitive questions every day. The gap between stakeholder expectations and current systems keeps growing wider. However, traditional approaches to closing this gap cost too much and take too long. Custom-built portals demand significant development resources. They also bring long timelines and ongoing maintenance costs. In addition, third-party portal products add yet another disconnected system to manage. These integrations often break when your ERP system updates. As a result, many companies delay the project indefinitely. Others invest heavily in solutions that don't scale. Fortunately, there is a better path forward. Microsoft Power Pages, connected to Dynamics 365 Business Central, offers a low-code way to build professional portals. Furthermore, these portals surface real-time ERP data without a six-figure price tag. It's a Microsoft-native solution that extends the investment you already made in Business Central. In addition, it puts secure, role-based access to your data directly in the hands of your customers and partners. In this blog, we'll explore the challenges businesses face without a connected portal. We'll also cover how Power Pages and Business Central solve them. Finally, we'll show what a realistic implementation looks like.

Why a Customer Portal for Business Central Matters

Without a portal, operational drag grows over time. For instance, customer service teams field repetitive calls about order status and invoice copies. Meanwhile, sales reps spend hours pulling reports that customers should access on their own. Vendors send emails back and forth to track payment status. Often, those delays strain key relationships. Inside your organization, staff log into Business Central, look up information, and then relay it through email or phone. As a result, this process eats productive hours. Furthermore, it introduces delays, errors, and frustration on both sides. For example, when a customer asks for an invoice copy at 4:55 PM on a Friday, your team scrambles. Meanwhile, the customer waits until Monday for an answer. That kind of friction adds up over time. Eventually, it erodes loyalty. Beyond inefficiency, the lack of a portal creates a competitive disadvantage. Today's customers compare every interaction to consumer experiences like Amazon and Netflix. As a result, they expect instant access to their information. When competitors offer modern portals and you don't, you lose business.

How Power Pages Powers a Customer Portal for Business Central

Microsoft Power Pages is a low-code platform built for external-facing websites and portals. Because it sits within the Microsoft Power Platform, it connects natively to Business Central through Dataverse. This direct connection means data flows in both directions in real time. For instance, a customer can view an order, check its fulfillment status, and submit a service request. They do it all from one intuitive interface. As a result, your team handles fewer routine inquiries. Furthermore, your staff focuses on higher-value work.

1. Self-Service That Frees Your Team

A self-service portal shifts routine inquiries away from your staff. Here's what changes:

• Customers view open orders, shipment tracking, and delivery confirmations without contacting your team
• Vendors check payment status and submitted invoices on their own schedule
• Internal staff redirect their attention from inquiry management to higher-value tasks

As a result, inbound inquiries drop measurably. In addition, your team gains productivity without adding headcount.

2. Real-Time Transparency That Builds Stronger Relationships

Power Pages portals surface live data from Business Central. Therefore, the information your customers and partners see stays accurate and current. It's not a snapshot from last night's batch sync. This real-time visibility transforms the relationship. For example, customers trust what they see. Similarly, vendors plan around accurate payment timelines.

3. Microsoft-Native Means Lower Cost and Faster Time to Value

Power Pages uses the Microsoft tools your team already knows. Here's why that matters:

• You skip the integration headaches that come with third-party portals
• Implementation timelines shrink from many months to a few weeks
• Security, authentication, and compliance controls come built in

For businesses that already invested in Business Central, a Power Pages portal ranks among the highest-ROI extensions available today.

A Hypothetical Scenario: What This Looks Like in Everyday Work

Let's walk through a realistic example to make this concrete. Imagine Apex Distribution, a mid-sized wholesale distributor with 120 employees. They run Dynamics 365 Business Central for their ERP.
Apex has 300+ active customer accounts. Their customer service team spends roughly 15 hours per week answering order status and invoice questions by phone and email.
After they implement a Power Pages portal connected to Business Central, here's what a typical day looks like.

7:30 AM : A Buyer Starts the Day Self-Served

At 7:30 AM, a buyer at one of Apex's retail customers logs into the portal before the business day even starts. She pulls up her three open purchase orders. One has shipped and is arriving today. Another is being picked at the warehouse. The third is on backorder with an estimated ship date.
She forwards the shipping confirmation to her receiving team. Then she gets on with her day without calling anyone.

9:15 AM : A Vendor Checks Payment Status

At 9:15 AM, the AP manager at a vendor Apex works with logs into the portal to check on a payment. He can see his submitted invoice. He also sees the date it was approved in Business Central and the scheduled payment date.
As a result, the question is answered in 30 seconds. No single call goes to Apex's accounting department.

11:00 AM : A New Customer Submits a Credit Application

At 11:00 AM, a new customer submits a credit application through the portal. The form feeds directly into Business Central. It creates a new record and triggers a Power Automate workflow.
That workflow routes the application to the right team member for review. No manual data entry is required.

Just Before Noon : A Purchasing Manager Plans Next Week's Order

Just before noon, a purchasing manager at one of Apex's larger accounts logs in to plan next week's order. Rather than calling the sales desk to ask whether a product is in stock, she pulls up the inventory page directly in the portal.
Stock levels from Business Central display in real time. As a result, she can see exactly what's available, what's running low, and what's on a replenishment order. She builds her order around what she knows is ready to ship. In addition, she avoids the back-and-forth that used to eat up half her morning.

1:30 PM : A Controller Reconciles an Account

At 1:30 PM, the controller at another customer account logs in with a specific question. Their accounting team thinks they have an outstanding balance from two months ago. However, they aren't sure if a recent payment was applied.
Through the portal, she can see the full account statement pulled live from Business Central. That includes each invoice, its due date, and its current status. The payment they submitted last week shows as received and applied. As a result, she closes the tab and moves on without sending a single email to Apex's AR team.

3:00 PM : A Complex Call Gets the Attention It Deserves

At 3:00 PM, a longer-tenured customer calls Apex's customer service line. This time the question is different. He's trying to reconcile a disputed charge from last quarter.
Because the portal already handles the routine questions, the rep who picks up has time to pull up the account, walk through the details, and resolve the issue properly. Previously, that conversation got rushed because the phone queue was full of stock and balance inquiries.

End of the Week : The Compounding Effect

By the end of the week, Apex's customer service team has fielded a fraction of the calls they used to handle. The questions that do come in are genuinely complex. They are the kind that actually need a human.
Furthermore, because the team isn't buried in routine lookups, response times on those real issues improve too. This isn't a future vision. It's what Power Pages connected to Business Central makes possible today. Distributors, manufacturers, and service businesses are implementing it right now.

Phased Approach to Building Your Customer Portal for Business Central

A successful portal launch doesn't require a big-bang rollout. Instead, a phased approach reduces risk and delivers value quickly.

Phase 1: Discovery and Quick Wins

Start with the highest-volume, lowest-complexity use cases. For instance, order status lookups and invoice downloads usually top the list. Typically, this phase takes two to four weeks. As a result, it delivers immediate impact.

Phase 2: Expanded Self-Service

Next, add features like order placement, support ticket submission, and document uploads. Build on the foundation from Phase 1. Furthermore, each new feature follows the same pattern, so your team learns the platform as it grows.

Phase 3: Vendor and Partner Portals

Then extend the same approach to vendors and partners. Because Power Pages supports multiple audiences, you scale without rebuilding. In addition, each new audience adds value without disrupting existing users.

Phase 4: Continuous Improvement

Finally, use feedback and usage analytics to refine the portal. Add new capabilities based on what your users actually need. Small, additive changes keep the portal aligned with your business as it grows.

Conclusion

Growing businesses can no longer afford the gap between stakeholder needs and system capabilities. Customers expect self-service visibility. Vendors expect payment transparency. Furthermore, internal teams deserve to spend time on work that matters. Traditional ERP systems alone can't bridge that gap. In addition, custom portal development sits out of reach for most mid-sized organizations. However, Power Pages connected to Business Central changes the equation entirely. It's a Microsoft-native, low-code solution that leverages your existing investment. Furthermore, it delivers a professional portal experience in weeks rather than months. As a result, you scale at a fraction of the cost of a custom build. With KTL Solutions guiding your implementation, you get a partner who knows both the technology and the business processes behind it. Therefore, the portal your customers expect doesn't have to cost a fortune. It just has to be built on the right foundation. Ready to launch a Customer Portal for Business Central? Contact KTL Solutions today. Get a tailored portal built on Microsoft Dynamics 365 Business Central. Also explore other add-on products for Microsoft Dynamics ERP that pair well with a Customer Portal for Business Central.

The post Customer Portal for Business Central appeared first on ERP Software Blog.

As businesses face increasing pressure to move faster, operate leaner, and make smarter decisions. Artificial Intelligence (AI) is rapidly becoming a strategic necessity rather than an emerging technology experiment. Yet despite growing enterprise investments in AI, many organizations still struggle to convert AI initiatives into measurable business outcomes.
The issue is not a lack of AI tools or ambition. The real challenge lies in operationalizing AI across workflows, systems, and decision-making processes in a way that delivers scalable business value.
This is where modern ERP platforms like Microsoft Dynamics 365 are playing a critical role.
Microsoft Dynamics 365 ERP has evolved far beyond being a transactional system for finance, operations, or supply chain management. With embedded AI capabilities, predictive analytics, intelligent automation, and Copilot-driven experiences, Dynamics 365 is becoming an intelligent business platform that helps organizations improve agility, increase productivity, and drive operational efficiency at scale.
By integrating AI into everyday business functions, organizations can automate repetitive work, uncover actionable insights faster, improve forecasting accuracy, and create more connected customer and employee experiences.

Why AI Matters in Modern ERP Systems

Traditional ERP systems were designed primarily to centralize data and standardize processes. While that foundation remains important, modern enterprises now require systems that can also analyze, predict, recommend, and automate in real time.
AI enhances ERP by transforming static operational data into intelligent insights that guide faster and more accurate decisions.
Within Microsoft Dynamics 365, AI capabilities help organizations:

• Improve forecasting and planning accuracy
• Reduce manual effort through automation
• Identify operational risks earlier
• Optimize customer interactions
• Enhance supply chain resilience
• Accelerate financial reporting and analysis

More importantly, AI allows organizations to shift from reactive operations to proactive decision-making.
Instead of relying solely on historical reporting, businesses can use AI to predict trends, detect anomalies, and respond to changing conditions before they impact performance.

Eight Ways AI is Enhancing Microsoft Dynamics 365 ERP

1. Smarter Decision-Making with Predictive Insights

One of the biggest advantages of AI within Dynamics 365 is the ability to turn historical and real-time data into predictive intelligence.
AI-powered analytics help organizations forecast demand, identify business risks, anticipate operational disruptions, and improve strategic planning. Leaders gain deeper visibility into patterns and trends, allowing them to make faster, data-driven decisions with greater confidence.
Rather than reacting to issues after they occur, businesses can proactively address challenges before they escalate.

2. Creating More Resilient Supply Chains

Supply chain disruption continues to be a major concern for organizations across industries. AI within Dynamics 365 Supply Chain Management helps businesses improve visibility, optimize inventory, and strengthen operational resilience.
Using predictive analytics and real-time monitoring, organizations can better anticipate fluctuations in demand, identify supplier risks, and improve logistics planning.
Microsoft Copilot capabilities further enhance supply chain operations by helping teams analyze data faster and make informed decisions in real time.

3. Delivering More Personalized Customer Experiences

Customer expectations continue to evolve, with businesses expected to provide faster, more personalized support across channels.
AI-powered capabilities within Dynamics 365 Customer Service help organizations scale customer engagement while maintaining service quality. Intelligent chatbots, automated case management, and Copilot-assisted responses enable support teams to resolve issues more efficiently and consistently.
AI also helps customer service teams access relevant case history and contextual insights quickly, improving response accuracy and reducing resolution times.

4. Improving Financial Visibility and Accuracy

Finance teams are increasingly leveraging AI to streamline reporting, automate reconciliations, and improve financial planning.
Within Dynamics 365 Finance, AI helps organizations reduce manual effort associated with repetitive financial tasks while improving reporting accuracy and operational agility.
AI-driven anomaly detection can also identify irregularities in financial data earlier, helping businesses strengthen compliance and reduce risk exposure.
As a result, finance leaders can spend less time compiling reports and more time focusing on strategic analysis and growth initiatives.

5. Enabling Real-Time Operational Intelligence

Modern businesses need access to real-time insights to remain competitive in rapidly changing markets.
AI-enhanced business intelligence within Dynamics 365 enables organizations to monitor operations continuously, identify performance gaps faster, and make informed decisions across departments.
From sales and procurement to finance and operations, AI helps teams access contextual insights when they need them most.
This level of operational visibility supports faster execution and better cross-functional collaboration.

6. Automating Repetitive Business Processes

Many business functions still rely heavily on manual, repetitive tasks that consume time and reduce productivity.
AI-driven automation within Dynamics 365 helps organizations streamline workflows across finance, HR, procurement, and operations. Tasks such as invoice processing, approvals, reporting, and data entry can be automated, allowing employees to focus on more strategic work.
Automation not only improves efficiency but also helps reduce errors and improve process consistency.

7. Embedding AI into Everyday Workflows

Organizations are seeing greater value from AI when it is integrated directly into daily workflows instead of being treated as a separate technology layer.
Dynamics 365 enables businesses to embed AI capabilities into operational processes, allowing employees to interact with intelligent recommendations, automated insights, and guided actions within the applications they already use.
This approach improves adoption, accelerates decision-making, and creates more responsive business operations.

8. Strengthening Forecasting and Planning

Forecasting accuracy remains critical for maintaining operational agility and controlling costs.
AI-powered forecasting within Dynamics 365 analyzes historical patterns, market trends, and real-time variables to improve demand planning and inventory management.
More accurate forecasting helps organizations reduce excess inventory, avoid shortages, and optimize resource allocation across the business.
The result is a more agile and responsive operational model.

Real-World AI in Action

A precision machinery manufacturer faced growing challenges managing a high volume of customer service cases. Service teams spent significant time searching through emails, gathering case history, and drafting responses manually, leading to delays and inconsistent communication.
By implementing a Generative AI-powered Copilot solution integrated with Dynamics 365, the company transformed its customer service operations.
The AI solution enabled teams to:

• Consolidate customer and case information in one place
• Generate concise case summaries quickly
• Draft context-aware emails automatically
• Improve response speed and communication consistency

As a result, customer service teams could resolve cases more efficiently while delivering more accurate and personalized support experiences.

The Future of AI in Microsoft Dynamics 365 ERP

The future of AI within ERP systems is centered on creating intelligent, adaptive, and increasingly autonomous operations.
As organizations continue moving from isolated AI experiments to enterprise-wide AI operating models, Microsoft Dynamics 365 will play an even larger role in enabling connected, data-driven business ecosystems.
Several emerging innovations are expected to shape the next phase of ERP transformation:

Natural Language Processing (NLP)

Conversational AI interfaces will make ERP systems easier to interact with, enabling employees to access information and complete tasks using natural language commands.

Self-Learning AI Models

Machine learning models will continue improving over time by learning from new business data, helping organizations strengthen forecasting, personalization, and operational decision-making.

Advanced Analytics and Deep Learning

AI systems will become more capable of identifying complex patterns across large datasets, generating deeper operational insights and more precise recommendations.

IoT-Driven Intelligence

The integration of IoT data with AI-powered ERP systems will improve asset monitoring, predictive maintenance, and real-time supply chain visibility.

Expanded Intelligent Automation

Businesses will increasingly automate complex workflows across departments, improving scalability while reducing operational inefficiencies.

Moving from AI Adoption to AI Operationalization

AI is becoming a core driver of operational transformation. Organizations that achieve the greatest success with AI are those embedding intelligence directly into their business processes rather than limiting AI to isolated use cases or experimentation.
Microsoft Dynamics 365 ERP provides the foundation for this transformation by combining enterprise data, intelligent automation, predictive insights, and AI-driven experiences within a connected operational platform.
As AI capabilities continue to evolve, businesses that operationalize AI across finance, supply chain, customer service, and operations will be better positioned to improve agility, increase productivity, and drive long-term competitive advantage.
 

The post AI-Powered Microsoft Dynamics 365 ERP: 8 Ways Businesses Are Improving Operations appeared first on ERP Software Blog.

TL;DR

For CIOs, “AI-first” in Business Central is not about flashy agents, it’s about governance, security, and process integrity at scale. The right partner protects least privilege, enforces auditability, defines clear data ownership, monitors integrations and automations continuously, and builds human checkpoints into AI-assisted workflows. If governance, monitoring, and incident response are vague or treated as phase two, the AI risk outweighs the upside.
AI in ERP can be transformational  or it can amplify problems at scale. The CIO's risk is rarely the AI model itself. It's permissions, inconsistent definitions of truth, and unmonitored workflows. That's why the best AI-first ERP partners are also process governance partners: they design controls, ownership, monitoring, and accountability from day one.
This guide helps CIOs evaluate an AI-first Business Central partner with a governance-first approach, while still recognizing the value of Fabric and agentic patterns when deployed responsibly.
In this article

• What “AI-first” should mean for IT
• What to prioritize: governance + monitoring + ownership
• Verification questions (security, data, recovery)
• CIO red flags
• FAQs

What “AI-first” should mean for IT

For IT leaders, AI-first should mean:

• Least privilege and auditability remain intact
• Data ownership is explicit (so outputs are grounded)
• Monitoring and recovery exist for integrations and automations
• AI/agents have clear boundaries and human checkpoints for sensitive actions

The baseline for this is Microsoft's own security model. Least privilege - the principle of giving each user, agent, or process only the permissions it needs and nothing more is the foundational control that prevents AI from amplifying access risks at scale. If a partner can't explain how they enforce this in plain language, their AI capability may be risky in production.

What to prioritize (CIO lens)

A process-integrity approach prioritizes stability over novelty. You’re looking for a partner who can keep the system correct and secure after go-live—because that’s when real entropy begins.
Prioritize:

• Security + access model: roles, least privilege, segregation of duties
• Data governance: owned definitions, lineage expectations, conflict handling
• Monitoring + operating model: who watches what, how often, and what happens when it breaks
• Integration reliability: continuity for operational lifelines

Data governance is where most AI deployments quietly fail. Before any AI can be trusted, data ownership and governance must be established owned KPI definitions, resolved conflicts between records, and clear lineage so AI outputs are grounded in truth rather than noise.
Minimum viable governance (buyer-friendly)
At a minimum, the partner should be able to describe:

• What gets logged and how actions are audited
• How AI-assisted actions are bounded and reviewed
• How data quality issues are detected early
• How incidents are triaged and resolved 

Verification questions

Identity and auditability
Ask:

• “Show your role-based access model and how you enforce segregation of duties.”
• “How do you audit sensitive actions and AI-assisted actions over time?”

Data ownership and grounding
Ask:

• “Who owns KPI definitions across finance and ops?”
• “How do you handle conflicting records and data drift?”
• “What’s your approach to lineage and stewardship?”

Monitoring and incident response
Ask:

• “What do you monitor daily for integrations and critical workflows?”
• “What’s your incident response plan for automation failures?”
• “Who owns tuning and governance after go-live?”

CIO red flags

• Governance is postponed or hand-waved
• No least-privilege story (permissions are “we’ll configure it”)
• No monitoring plan for integrations/automations
• Data ownership is vague (“we’ll figure it out later”)
• "Autonomous agentic patterns in Business Central" pitched without auditability and boundaries

FAQs

Do we need Microsoft Fabric for Business Central AI scenarios?
Not always, but you need governed data grounding and ownership. Fabric is often used to unify data and support scale when implemented responsibly.
What’s the biggest AI risk in ERP?
Scaling weak permissions and inconsistent data definitions, plus unmonitored workflows that silently degrade.
How can IT verify a partner is AI-capable without accepting risk?
Demand governance, monitoring, incident response, and workflow boundaries—not just demos.
Further reading:

• How to Choose the Best ERP Partner in the USA (AI-First Business Central Edition): Scorecard + Methodology
• Red Flags When an ERP Partner Claims They’re “AI-First”

The post AI-First ERP Partner for CIOs: How to Evaluate Business Central + Fabric + Agents with Governance and Process Integrity appeared first on ERP Software Blog.

Modernizing ERP Before the Clock Runs Out.

Our GP Support North team at Endeavor4 loves Dynamics GP and is the Safe Haven for Dynamics GP (Great Plains) users BOTH before and after the Microsoft-set End of Life for GP in 2029.  A member of our team was recently interviewed by CIO Review Magazine on the topic of Dynamics GP and Dynamics GP to Business Central.

The following is a quick Executive Summary of the article named - Modernizing ERP Before the Clock Runs Out

The CIOReview feature on Endeavor4 positions the company as a leading ERP consulting partner helping organizations navigate the transition from legacy systems, particularly Microsoft Dynamics GP, to modern cloud-based platforms like Dynamics 365 Business Central. The article highlights an industry-wide shift driven less by immediate technical failure and more by defined vendor timelines, with Dynamics GP support scheduled to end by 2029, prompting organizations to proactively modernize. Source [cioreview.com]
Endeavor4 plays a central role in this transition through deep experience supporting over 650 GP clients and executing structured migrations to Business Central. Its approach emphasizes reducing risk through standardized tools, benchmarks, and repeatable delivery practices, while focusing on long-term client outcomes rather than simple system replacement. Source [cioreview.com]
A key theme is the growing importance of security and AI in ERP decision-making. The article notes that AI-driven cyber threats are increasing in sophistication, exposing limitations of legacy platforms. In response, cloud-based Microsoft environments offer continuous security investment and enterprise-scale protection. At the same time, embedded AI capabilities in Business Central enhance operational efficiency through automation, anomaly detection, and improved data capture, strengthening financial controls and reducing manual effort. [cioreview.com]
The modernization journey is also framed as an opportunity to redesign business processes. Many organizations rely on layered Excel workarounds and fragmented data environments; migrating to a modern ERP allows them to clean and standardize data, streamline workflows, and improve reporting accuracy. [cioreview.com]
Overall, the article positions Endeavor4 as a strategic partner focused on helping clients build a resilient, future-ready operational foundation. Rather than treating ERP migration as a technical project, the firm emphasizes transformation across data, processes, and governance to enable continuous evolution and long-term business value.  https://www.endeavor4solutions.com/businesscentral/d365-upgrade/

Regards,
GP Support North

 

About our team

GP Support North is a large in-house team of GP consultants dedicated to supporting clients using Microsoft Dynamics GP (Great Plains) ERP.  We made a 10-year pledge to support GP and are your safe-haven for long-term GP support and consulting services.  We will not force you to change platforms, but if and when you are ready, we can help migrate you to the cloud.
We love Dynamics GP (Great Plains) and have more than 650 active GP clients across North America, predominantly in the USA and Canada. Over the years, our team has been named multiple times to the Microsoft President’s Club – The top 5% of Microsoft Partners Worldwide.
https://www.gpsupportnorth.com/ 
https://www.gpsupportnorth.com/gp-to-business-central/

The post We love Dynamics GP, but are also uniquely qualified for BETTER GP to BC migrations appeared first on ERP Software Blog.

SureMDM integration makes deploying Android warehouse scanners dramatically easier for Business Central users

Insight Works, a leading provider of warehouse and manufacturing apps for Microsoft Dynamics 365 Business Central, today announced the availability of SureMDM device management as an add-on for Warehouse Insight and WMS Express. Powered by 42Gears, SureMDM gives IT teams centralized control over their Android scanner fleet — and reduces device deployment to a single step.
For warehouses running Warehouse Insight or WMS Express, getting Android scanners deployed has traditionally required IT staff to configure each device individually. SureMDM eliminates that process. Once enrolled, a new scanner can be fully configured by scanning a single barcode — Warehouse Insight or WMS Express is installed, settings are applied, and the device is automatically locked to the app. For businesses managing multiple locations or scaling their device fleet, this fundamentally changes how warehouse technology gets deployed.
"Deployment complexity has been one of the biggest friction points for warehouses adopting barcoding," said Brian Neufeld, Director of Marketing at Insight Works. "With SureMDM, we've reduced that to a single scan. A new device comes out of the box, someone scans a barcode, and it's ready to run Warehouse Insight. That's the kind of simplicity our customers have been asking for."

Beyond Deployment: Ongoing Fleet Management

Once devices are enrolled, SureMDM provides IT teams with ongoing visibility and control across the entire scanner fleet from a single web-based console — without requiring physical access to any device. Key capabilities include:

• Kiosk lockdown: Devices are locked to run only Warehouse Insight or WMS Express, preventing workers from accessing unrelated apps, browsers, or settings.
• Remote lock and wipe: Lost or decommissioned devices can be remotely locked, located, or wiped, keeping Business Central data protected.
• App and OS updates: Warehouse Insight updates and Android OS patches can be pushed to the entire fleet simultaneously, eliminating version drift across locations.
• Multi-location management: Different policies, configurations, and user assignments can be applied per site from a single console.
• Real-time monitoring: Device status, battery levels, app versions, and last-known locations are visible at a glance, enabling IT teams to identify and resolve issues before they affect warehouse operations.

Device Requirements

SureMDM's full management capabilities require devices to be enrolled from a clean state — either new out of the box or factory reset. This is an Android platform requirement. Businesses purchasing new hardware or refreshing an aging fleet will find enrollment seamless and automatic.
SureMDM supports Android-based barcode scanners and mobile computers from Honeywell, Zebra, Datalogic, and other leading manufacturers — the same devices used with Warehouse Insight and WMS Express every day.

Availability

SureMDM is available now as an add-on for Warehouse Insight and WMS Express. For more information, visit https://dmsiworks.com/features/simplified-device-deployment-for-business-central-wms.

About Insight Works

Insight Works is a leading Independent Software Vendor (ISV) dedicated to creating apps exclusively for Microsoft Dynamics 365 Business Central. The company specializes in the manufacturing and distribution industries, providing innovative solutions that streamline operations and enhance productivity for businesses worldwide. With a vast reseller network comprising over 750 global Microsoft Partners, Insight Works ensures its apps are accessible and supported wherever businesses operate. Headquartered in Canada, Insight Works also maintains a regional office in the Netherlands, strengthening its global reach and commitment to localized support. Learn more at dmsiworks.com.

The post Insight Works Adds Mobile Device Management to Warehouse Insight and WMS Express appeared first on ERP Software Blog.

  
Microsoft Dynamics 365 helps businesses relocate inventory to a new site by supporting transfer orders, warehouse setup, item updates, inventory tracking, reconciliation, and reporting. Because a site relocation can affect customer orders, delivery timelines, production schedules, and daily warehouse operations, the process needs to be planned carefully and reflected accurately in the system.

Key Highlights

• A site relocation in Dynamics 365 can affect customer orders, production schedules, delivery timelines, and supply chain activity.
• Reviewing inventory quantity, type, value, and storage requirements helps prepare the new site before the move.
• Transfer orders, item master updates, transaction records, and reconciliation help keep the relocation controlled and accurate.
• Barcode scanning, RFID tags, and integrated inventory tracking can improve visibility while items are moving.
• Communication, reporting updates, testing, and monitoring help confirm that the relocation was completed successfully.

What Is Inventory Site Relocation in Dynamics 365?

Inventory site relocation in Dynamics 365 is the process of moving stock from one site or warehouse to another while keeping system records aligned with the physical movement of goods. In Microsoft Dynamics 365 Finance and Supply Chain Management, this process may involve setting up the destination warehouse, creating transfer orders, tracking inventory movement, updating transaction records, and reconciling on-hand quantities.

Why Does Inventory Relocation Require Careful Planning in Dynamics 365?

Inventory relocation requires careful planning because it affects both physical stock movement and the system records that teams rely on to make decisions. If warehouse, purchasing, production, and customer service teams are not aligned, the relocation can lead to delays, inaccurate inventory visibility, or operational confusion.
A strong plan should account for customer order commitments, delivery timelines, production schedules, and lead times. These details help determine when inventory can move, how it should be transferred, and when it needs to be available at the destination site.
Planning also helps prepare employees for changes in daily work. If the new site requires different workflows or reporting steps, teams should understand those changes before the relocation begins.

How Should You Analyze Inventory Before Moving It to a New Site?

Before moving inventory to a new site, businesses should review the quantity, type, and value of the items being relocated. This analysis helps determine whether the new location has the right storage space, layout, and operational setup to support the inventory being moved.
The review should also identify obsolete or excess inventory. Items that are no longer needed may be disposed of or transferred to a different location, which streamlines inventory management, reduces carrying costs, and ensures the new location starts with a more accurate stock position.

How Can Dynamics 365 Support a Smooth Inventory Transfer?

Dynamics 365 supports a smooth inventory transfer by giving teams a structured process to create, release, ship, receive, and validate inventory movement. A complete transfer plan should define the required steps, timelines, responsibilities, and system updates needed to complete the move.
The transfer schedule should reflect current order fulfillment commitments, production schedules, and lead times. When those factors are included in the plan, the business is less likely to interrupt customer orders or create unnecessary downtime.
Logistics also need to be considered before the move begins. Transportation, packaging, and labeling requirements should be planned carefully because properly packaged and labeled inventory is easier to track, receive, and manage at the new site.

How Does Inventory Tracking Reduce Disruption During Site Relocation?

Inventory tracking reduces disruption by helping teams maintain accurate counts and visibility while stock is moving. During a site relocation, the business needs to know where items are, whether they have been shipped, and when they have been received at the destination warehouse.
Barcode scanning technology or RFID tags can support real-time tracking of inventory movement. Barcode scanning uses printed codes that are scanned as items move through warehouse processes, while RFID, or radio frequency identification, uses tags to identify and track items.
When your inventory tracking system is integrated with Dynamics 365, teams can monitor stock levels, generate accurate reports, and make more informed inventory management decisions. This visibility helps reduce stockouts, support order fulfillment, and lower the risk of confusion during the relocation.

How Can Your Team Optimize the Site Relocation Process in Dynamics 365?

Teams can optimize a site relocation in Dynamics 365 by implementing best practices and leaning on technology to provide structure and a streamlined workrkflow.
Training is an important part of the transition. Employees should understand the new site’s processes and workflows before they are expected to work with relocated inventory.
Automation tools and workflows within Dynamics 365 can also help streamline tasks such as data entry, inventory updates, and reporting. These tools can save time and reduce the risk of human error when the relocation involves many transactions or records.
After the move, teams should review what worked and what needs improvement. Feedback from employees can help refine the process and make future site relocations more efficient.

What Are the Practical Steps to Set Up a New Site and Warehouse in D365 F&SCM?

Setting up a new site and warehouse in Dynamics 365 Finance and Supply Chain Management includes creating the destination location, configuring warehouse rules, updating item records, transferring inventory, and reconciling stock. Each step helps ensure that the system reflects the physical relocation accurately.

1. Navigate to Warehouse Management

In the D365 F&O system, go to the Warehouse management workspace. This is where the setup for the new site and warehouse begins.

2. Create the New Site and Warehouse

Create a new site and warehouse for the destination location if they do not already exist. This gives the system a defined location where transferred stock can be received and managed.

3. Configure Location Directives

Configure location directives to define how the system should direct item movement within the warehouse. Location directives are rules that guide where items should be picked, put away, or moved.

4. Update Item Master Data

Update item master data with the new site and warehouse information. Item master data is the core item record in Dynamics 365, and it needs to reflect the correct site and warehouse details so inventory activity is recorded properly.

5. Create the Transfer Order

Navigate to “Inventory Management” and create a transfer order to move items from the old site or warehouse to the new one. The transfer order should specify the source warehouse, destination warehouse, and items being transferred.

6. Generate Transfer Order Lines

Generate transfer order lines based on the items and quantities that need to be moved. These lines define the specific inventory included in the transfer.

7. Confirm and Release the Transfer Order

Confirm the transfer order to validate that the items are available for transfer. Then release the transfer order to initiate the physical movement of items.

8. Pick and Pack Items

In the warehouse, use mobile devices or the system interface to pick and pack the items according to the transfer order. This step prepares inventory for transfer from the old location.

9. Ship Items

If required, register the shipment of items to update inventory and shipping information. This helps keep the system aligned with the physical shipment.

10. Receive Items at the New Warehouse

Once the items arrive at the new warehouse, use the system to receive them into inventory. Confirming the receipt updates inventory levels and finalizes the transfer.

11. Update Transaction Records

Verify that all transaction records, such as inventory transactions and ledger entries, are updated to reflect the movement accurately. This helps ensure that the inventory history in Dynamics 365 matches what happened physically.

12. Adjust Stocked Quantities if Needed

If necessary, adjust stocked quantities for items at the old warehouse to account for the transfer. This helps prevent inventory discrepancies after the move.

13. Perform Inventory Reconciliation

Reconcile inventory to confirm that on-hand quantities in the system match the physical quantities in the warehouse. Inventory reconciliation means comparing system records with actual stock counts and resolving any differences.

14. Update Reports and Records

Update any reports, documents, or records that reference the location or status of the items. This may include item configurations, purchase planning setups, and existing purchase and sales orders.

15. Communicate the Inventory Location Changes

Inform relevant stakeholders about the change in inventory location. Employees, customers, and suppliers may need to know where inventory is now located or how the relocation affects related processes.

16. Monitor and Test the New Warehouse

Monitor the new warehouse’s performance and conduct testing to confirm that the inventory transfer did not affect system integrity. This final step helps ensure that the new location is operating correctly in both the warehouse and Dynamics 365.

FAQ: Dynamics 365 Inventory Site Relocation

Q: What is the main goal of relocating inventory in Dynamics 365?

A: The main goal is to move inventory to a new site or warehouse while keeping physical stock movement, system records, reporting, and warehouse operations aligned.

Q: Why should inventory be analyzed before a site relocation?

A: Inventory should be analyzed to understand the quantity, type, and value of items being moved and to confirm that the new site has the right storage space and layout.

Q: How do transfer orders help with inventory relocation in Dynamics 365?

A: Transfer orders define the source warehouse, destination warehouse, items, and quantities being moved, giving teams a structured process for relocating stock.

Q: What role does inventory tracking play during the move?

A: Inventory tracking helps teams maintain accurate counts, locate items, prevent stockouts, and support order fulfillment while inventory is in transition.

Q: How does Pharos Solutions help with Dynamics 365 inventory relocation?

A: Pharos Solutions provides practical guidance on Dynamics 365 inventory processes, including site relocation, transfer orders, tracking, warehouse setup, reconciliation, and process optimization.

Work With Pharos Solutions on Dynamics 365 Inventory Site Relocation

Pharos Solutions specializes in Microsoft Dynamics 365 implementations and operational support, with deep expertise in inventory management, warehouse configuration, and supply chain optimization within the D365 Finance & Operations environment. Their consultants have guided organizations through complex inventory transitions — including multi-site relocations — with a focus on minimizing disruption and maintaining system integrity throughout the process.

Wrap Up

A successful inventory relocation depends on more than moving items from one building to another. It requires accurate planning, careful system setup, clear communication, and a reliable process for confirming that system records match physical stock.
If your organization is preparing for a site relocation in Microsoft Dynamics 365, Pharos Solutions can help you review the process, prepare your D365 F&O setup, and move forward with greater confidence. Contact us today!
 
By Pharos Solutions | www.pharossolutions.com

The post How Can Dynamics 365 F&SCM Help You Relocate Inventory to a New Site? appeared first on ERP Software Blog.

Every troubled Dynamics 365 Finance and Operations implementation reaches a moment where the team is asked to choose between two postures: keep patching to hold the line, or pause to understand why the line keeps breaking. The first is the more visible response, and often the one stakeholders expect. The second is usually the one that determines whether the program recovers.
Patch-forward is the default response to a destabilizing rollout because it mirrors the urgency of the moment. A ticket lands, a fix ships, a dashboard turns green, and the program keeps moving. The problem is not that the fixes are wrong in isolation. It is that, applied without diagnostic clarity or environment isolation, they accumulate. What looks like momentum is often debt being written against the future stability of the system.
This piece argues that patch-forward is not a remediation strategy at all. It is a risk-deferral pattern, and in a D365 rescue context the deferral compounds faster than the fixes resolve.

The Shape of Patch-Forward

Patch-forward rarely announces itself. It emerges instead from a sequence of individually defensible decisions, each one made under enough pressure that the alternative looks worse. An emergency SQL update is pushed straight to production because the close window will not wait. A piece of custom logic is bolted on to bypass a failing process, with a note to revisit it later. Infrastructure is scaled up when performance degrades, on the theory that capacity will at least buy time. A configuration change is merged without a full regression cycle because regression would push the milestone, and the rollout continues despite unresolved instability because pausing it would mean explaining why. Each of these reads as decisive on a status report, and in isolation each is.
Viewed in aggregate, though, the pattern reads differently. The system is being asked to absorb change faster than the team can reason about it, and the cost of that asymmetry stays invisible until fixes begin to interact with each other in ways nobody planned for, at which point the cost arrives all at once rather than at the pace of the decisions that produced it.

Why the Debt Compounds Faster Than the Fixes

Technical debt in a D365 rescue does not behave linearly, and that is what makes the trajectory hard to feel from inside. Every emergency change adds structural weight to the system. Execution paths grow more tangled as workarounds layer on top of one another, query performance becomes harder to predict once those workarounds start interacting under load, and the catalog of customizations expands faster than anyone is documenting it. Governance boundaries soften in parallel, less by decision than by attrition, as the team learns which controls can be bypassed without an immediate cost. By the time the next fix is being scoped, it is being introduced into a system that is materially less understood than it was a week ago, which raises the odds that the fix itself will require a follow-up, and that the follow-up will require one of its own.
This is the mechanism that traps programs. The team is not failing to work hard. They are working against a curve where complexity is compounding faster than remediation can keep up, and the only way out is to flatten the curve, not run faster on it.

The Financial Signature CIOs and CFOs Should Recognize

From a finance perspective, patch-forward has a recognizable signature long before it shows up as a failed milestone, and most of the indicators are visible in the standard reporting pack if you know what to look for. Consulting spend climbs without a corresponding improvement in system stability, and stabilization timelines tend to slip in two-week increments small enough to avoid triggering a formal replan but cumulative enough to move the go-live date by a quarter. Regression cycles multiply as fixes interact with earlier fixes. Audit readiness becomes harder to assert with confidence, in part because the documentation trail is thinner than the change log. And the texture of stakeholder updates shifts: more activity metrics, fewer outcome metrics, more verbs about what the team is doing and fewer about what the system is now able to do reliably.
The instinctive read is that the program needs more capacity. The accurate read is usually that the program needs less change, applied with more discipline. Structured containment, in nearly every rescue we have seen, costs less in absolute dollars than another two quarters of patching, and it produces an asset the organization can actually operate.

The Questions Patch-Forward Cannot Answer

The deeper limitation is epistemic. Patch-forward optimizes for the symptom in front of the team, which means it never has to answer the questions that actually determine whether the system can stabilize, and over time the team stops asking them. Which workload patterns are triggering instability under realistic concurrency, and which are merely correlated with it? Which customizations are amplifying degradation rather than causing it? Which integrations turn a local failure into a cascading one, and which batch sequences collide only under the specific conditions production happens to hit at month-end? None of these are answerable from a hotfix. They require instrumentation, environment isolation, and the willingness to hold a hypothesis open long enough to test it without that test threatening the live system.
Until those questions are answered, every fix is a guess dressed up as a decision. Sometimes the guess is right. Often enough, it is not, and the cost of being wrong is paid by the next fix, and the one after that.

Structured Rescue as the Alternative

The alternative to patch-forward is not slower work. It is differently sequenced work. A structured D365 rescue starts by re-establishing a few disciplines that the patch-forward posture tends to erode. The team needs to be able to observe how the system actually behaves under realistic workload, which means instrumenting it before drawing conclusions about it. Experiments need somewhere to run that is not production, which means isolating environments well enough that a hypothesis can fail safely. Issues need to be triaged by systemic impact rather than by how long they have been sitting in the ticket queue, and remediations need to clear a controlled validation before they go anywhere near a live system. Deployment, finally, needs to route back through governance rather than around it. None of these are exotic in principle. The rescue work is in re-establishing them after a period in which they were treated as overhead.
None of this is novel as a list. What makes it work is the order. Containment first, then diagnosis, then change. Programs that try to compress these steps, or run them in parallel under deadline pressure, tend to recreate the conditions that produced the original instability.

Signals You Are Already in Patch-Forward Mode

The pattern is easier to recognize from outside than from inside, but a handful of signals tend to surface together once a program has drifted into it. The most telling is cultural rather than technical: emergency fixes have become frequent enough that the team has stopped remarking on them, and production changes routinely ship without a controlled test because the controlled test would slow the next fix. Underneath that, the system itself starts behaving in recognizable ways. Infrastructure gets scaled more than once without a corresponding gain in stability, each remediation seems to expose a new issue rather than close out an old one, and governance controls quietly erode as deadlines stop leaving room for them. None of these is damning on its own. Several of them at once usually is.
When several of these are true at once, the question is no longer whether to slow down. It is how to slow down without losing the program. That is a different conversation than the one most steering committees are having, and it is the one worth having.

Post-Go-Live Rescue Assessment

In our Post-Go-Live Rescue Assessment, Ryse has helped organizations halt patch-forward escalation, isolate production risk, and reset governance before resuming the rollout. The case study is worth reviewing if any of the signals above feel familiar. If they feel urgent, contact Ryse to structure a controlled rescue before the next round of patches is written against a system that is harder to recover than it was last quarter.

Frequently Asked Questions

Is patch-forward ever the right call?

Yes, narrowly. Genuine emergencies, particularly those threatening data integrity or financial close, sometimes require a fix before a diagnosis. The discipline is treating that fix as a flagged exception that will be revisited, not as the new operating model.

Why does adding infrastructure rarely help?

Capacity addresses contention, not causation. If the underlying issue is an inefficient workload pattern or an unstable customization, scaling delays the symptom rather than removing it, and usually raises the cost of the eventual fix.

Does patch-forward create compliance exposure?

It can. Emergency changes made without governance oversight tend to be poorly documented, and poor documentation is where audit findings and data-integrity questions originate.

Replacing Patch-Forward With Structured Rescue

If your Dynamics 365 Finance and Operations environment is being held together by repeated emergency fixes, the trajectory will not self-correct. The fixes will continue to land, the debt will continue to compound, and the conversation with stakeholders will get harder rather than easier.

The post The Risk of Patch-Forward Strategies in Troubled D365 Implementations appeared first on ERP Software Blog.

In April and October of each year, Microsoft rolls out a scheduled set of updates—implementing new features, functionality improvements, and navigation changes across their applications—as one large “release wave.”
Microsoft announces their planned release waves several months ahead of deployment so that organizations have time to review upcoming changes, test their environments, and prepare their teams before updates are automatically applied.
Here’s an overview of the latest release wave plans for Business Central.
We’ve created several helpful resources designed to simplify your update testing and release wave preparation process for Microsoft Business Central.
 

Why is Update Testing Important?

Testing your existing Business Central environment before a release wave update is essential for minimizing disruptions and maintaining smooth day-to-day operations. While release notes can explain what an update is designed to do, they can’t predict exactly how those changes will interact with your unique Business Central environment. The only way to fully understand the impact is to test updates firsthand before they go live.
Here are a few additional reasons why update testing is so important:

Protect Your Customizations and Extensions

One of the most important reasons to perform update testing is to ensure your customizations, integrations, and extensions continue functioning properly after the release. Business Central environments can be tailored to meet a business's unique needs, so even standard updates can affect custom workflows or third-party tools in unexpected ways.

Prevent Business Disruptions

Critical business operations depend on your Business Central system working reliably. Testing updates in a sandbox environment first allows your team to evaluate how essential processes—like posting journal entries, generating reports, processing orders, and printing documents—will function before changes are applied to the live environment.
By identifying issues early, organizations can avoid interruptions that may slow down productivity or impact customers.

Validate Real-World Workflows

Update testing is most effective when teams walk through the actual processes they use every day. This helps confirm that your core workflows, permissions, automations, and connected systems will still behave as expected after the update.
The more thoroughly you test your environment, the more confidence you’ll have when it’s time to move the update into production.

Give Your Team Time to Resolve Issues

When you start testing early, you give your organization more time to troubleshoot and correct any problems they discover during the process. If an issue is found only shortly before Microsoft schedules an automatic update, there may be limited time available for investigation, fixes, and retesting.
Release wave updates may be automatically applied within 60 days of general availability, so early preparation is a good idea.

Reduce Stress During Release Waves

Preparing for semi-annual release updates can feel overwhelming, especially for organizations with complex environments or numerous extensions. Having a structured testing process in place helps simplify the experience and makes updates feel more manageable.
To support that process, we’ve created three free testing resources designed to help organizations prepare for upcoming release waves with confidence.
 

Resource #1: The PDF Checklist

Our interactive PDF checklist is a simple, easy-to-scan resource that outlines our recommended approach to update testing.

Who It’s Meant For:

This PDF checklist is especially useful for small businesses, individual team members managing testing on their own, or organizations looking for a foundation upon which to build a more customized testing process.

What’s Inside:

Inside the PDF, testing tasks are organized by Business Central functionality in a clear checklist format, so you can easily track progress and make sure every important workflow is reviewed. You’ll also find a notes section where you can document additional test cases, special considerations, or items that may require follow-up attention.
Get the PDF Checklist →

Resource #2: The Excel Workbook

Our Excel workbook is a more customizable version of our update testing checklist, designed for organizations that want more fine-tuned solutions while still maintaining a straightforward testing process.
With this workbook, you can easily add, remove, or hide testing actions to better align with your company’s workflows, extensions, and Business Central environment. The workbook is also sortable, filterable, and color-coded, making it easy to organize tasks and monitor progress throughout the testing process.

Who It’s Meant For:

The Excel workbook is designed for small businesses, individual team members managing testing independently, or teams that want an easy-to-adjust resource without worrying about breaking complex formulas or automations. For teams conducting collaborative testing (which we strongly recommend), you can also duplicate testing tabs so multiple team members can work within the same resource simultaneously.

What’s Inside:

Inside the workbook, you’ll find an Introduction tab that provides an overview of the resource, along with general instructions for conducting release wave testing.
The primary testing area is housed within the BC Update Test tab, where all testing activities are tracked. The tab includes a header section for documenting the Business Central version or update number being tested, the team member responsible for testing, and the testing date. From there, the workbook organizes test items into structured columns that identify the Business Central area being reviewed, the specific testing action, the status of the test, and any notes or follow-up items related to the results.
Get the Excel Testing Workbook →

 

Resource #3: The Formula-Driven Excel Workbook

The formula-driven Excel workbook is our most advanced update testing resource, designed for larger organizations or teams managing complex Business Central environments.
This workbook builds upon the structure of our standard Excel workbook but includes built-in formulas and advanced reporting features that help teams monitor testing progress more efficiently. Because multiple users may contribute to testing simultaneously, we recommend storing the workbook in a shared cloud location so all participants can view updates and progress in real time.

Who It’s Meant For:

The formula-driven Excel workbook is especially useful for companies with multiple team members participating in testing, organizations that need deeper tracking and reporting capabilities, or teams comfortable working with Excel formulas.
Due to the workbook’s formula-driven structure, it’s best suited for teams that either plan to use the workbook largely as designed or have internal staff who are experienced with Excel. While the workbook can be customized, changes should be made carefully to avoid disrupting built-in functionality.

What’s Inside:

Inside the workbook, you’ll first find an Instructions tab that explains how to use the resource and configure the testing experience. This section also includes settings that allow users to select which Business Central areas their organization actively uses. Any unnecessary sections can be hidden.
The Key Definitions tab serves as a reference guide for the structure and dependencies of each column in the workbook. Since the workbook contains interconnected formulas and automated reporting elements, this tab helps users understand how each section functions together. Teams planning to customize the workbook should review this tab carefully before making adjustments.
The primary testing activities take place within the BC Update Test tab. Here, users can assign testing responsibilities to individual team members, track test results, document notes, and monitor the status of each testing action. Like the standard workbook, this tab is sortable, filterable, and color-coded for ultimate visibility and organization. Teams can also customize testing actions, add additional tasks, or hide irrelevant items to better align with their specific Business Central environment.
The Summary tab provides advanced tracking and reporting capabilities that give teams a high-level view of testing progress. Using various reporting tools, this section allows teams to quickly evaluate testing completion, identify outstanding tasks, and review overall testing results. This section includes pivot tables, so users should remember to refresh the tables periodically to ensure the displayed data remains up to date.
Get the Formula-Driven Excel Testing Workbook→

 

6 Frequently Asked Questions About Business Central Update Testing

Don’t get caught in the undertow of the latest release wave. Knowing what to expect can help your team prepare more effectively and approach updates with confidence. Review these frequently asked questions for more information on the update testing process.

1. Why is it important to test customizations and extensions?

Testing your customizations, add-ins, and extensions is one of the most crucial parts of the update process. Updates can affect how these solutions function, so it’s critical to verify that everything continues working as expected after the update.
Review your Extension Manager to be sure you include all installed extensions in your testing process.

2. How thorough should update testing be?

It depends. The more thorough your testing is, the smoother your update experience will typically be. Comprehensive testing helps identify issues early, reduce operational disruptions, and minimize unexpected problems after the update is applied.

3. Should more than one person review the testing results?

Yes, we recommend having at least two people review and test workflows whenever possible. A second set of eyes can help catch issues that might otherwise be overlooked. As a certified Microsoft Partner, Syvantis has experience helping businesses of all sizes implement effective testing strategies for Business Central release waves.

4. What should I do if I encounter an issue during testing?

If you discover issues triggered by the update, contact your testing Partner as soon as possible. Early communication gives your support team more time to investigate and resolve problems before the update is applied to your live environment.
If Syvantis is your Partner and you’d like assistance with testing, we’re happy to schedule a support session to guide you through the process.

5. Should I document testing errors?

Absolutely. We strongly recommend taking screenshots or snippets of every error you encounter during testing. Using tools like the Windows Snipping Tool can help you quickly capture and organize images for easier troubleshooting and resolution later.

6. Finally, are Syvantis' testing resources customized to my Business Central environment?

No, these resources are designed for a general audience of Business Central users. Because every environment is different, some steps or recommendations may not apply to your organization, while customizations, extensions, or workflows unique to your system may not be included.
We recommend skipping anything irrelevant and adding additional tests specific to your configuration.
 

Test with Confidence. Update with Excitement.

Release waves should be something to look forward to. New features, functionalities, and performance improvements are opportunities to increase efficiency and get even more value from your Business Central environment. But when testing feels overwhelming, or hasn’t gone smoothly in the past, it can be difficult to feel confident about upcoming updates.
With the right testing process in place, your team can approach release waves with greater confidence and less stress. Proactive testing helps implement updates smoothly, so you can focus on leveraging new capabilities rather than troubleshooting unexpected issues.

The post 3 Resources to Prepare for the Next Business Central Release Wave appeared first on ERP Software Blog.

CFOs and finance leaders are at a unique crossroads. They are under pressure to protect cash flow and shorten DSO, yet their accounts receivable teams remain bogged down in manual chasing, spreadsheet tracking, and one-size-fits-all dunning. While finance is expected to be more strategic than ever, the day-to-day reality of collections too often pulls senior talent into low-value, repetitive work.
Traditional ERP systems are often not designed to handle the nuance of modern collections management. They can store invoices and aging buckets, but they struggle to prioritize accounts intelligently, personalize outreach, or predict which customers are about to slip into delinquency. The result is wasted effort on customers who would have paid anyway—and missed signals on the ones who won't.
This is where AI-powered collections, delivered through Microsoft Dynamics 365 Business Central and Copilot, becomes a game-changer. By layering predictive analytics, automated workflows, and intelligent agents on top of the ERP, finance leaders can transform collections from a reactive cost center into a proactive driver of working capital.
In this blog, we'll explore why CFOs need to bring AI into their collections process now, and how doing so inside Business Central can deliver faster cash conversion, stronger customer relationships, and measurable bottom-line impact.

The Challenges CFOs Face in Collections

Finance leaders running collections inside legacy or under-utilized ERP environments routinely encounter the same pain points:

1. Rising DSO and Unpredictable Cash Flow

Days Sales Outstanding is creeping up across nearly every industry, and CFOs are feeling the strain. When collections rely on static aging reports and reactive outreach, payments slip and cash flow becomes harder to forecast. Traditional ERP systems can show you what was overdue yesterday, but they can't tell you which invoices are likely to be paid late next week—leaving finance teams perpetually a step behind.

2. Manual, Time-Consuming Processes

AR teams spend the bulk of their week on repetitive tasks: pulling aging reports, drafting reminder emails, logging customer responses, and updating call notes in spreadsheets outside the ERP. This manual workload doesn't scale—doubling the customer base means doubling the headcount, or watching collection performance deteriorate. Traditional ERP environments lack the embedded automation needed to keep collectors focused on the conversations that actually move money.

3. One-Size-Fits-All Customer Outreach

Not every late-paying customer should be treated the same way. A long-standing strategic account that pays in 45 days needs a different touch than a new customer drifting toward 90 days. Yet most ERP-driven collections rely on rigid dunning sequences that send the same templated reminders to everyone. This damages relationships with good customers and lets high-risk accounts hide in the noise—two outcomes no CFO can afford.

The Role of AI-Powered Collections in Overcoming These Challenges

AI, embedded in Business Central and amplified by Copilot, offers a practical answer for finance leaders. Here's how:

1. Predictive Prioritization of Accounts

AI turns the aging report from a static document into a dynamic worklist. By analyzing payment history, customer behavior, communication patterns, and external signals, Business Central can score every open invoice by likelihood of late payment and surface the accounts that need attention before they become problems.
Rather than working alphabetically or by aging bucket, collectors start their day with a ranked list of the highest-impact actions—maximizing the recovery on every hour they spend on the phone or in email.
For example, AI in Business Central can:

• Predict payment dates for each open invoice based on the customer's historical behavior
• Flag at-risk accounts showing early warning signs such as slowing payments or declining order volume
• Recommend next-best actions for each customer—call, email, payment plan, or escalation

This predictive prioritization directly improves DSO, sharpens cash flow forecasting, and gives CFOs the visibility they've been asking for.

2. Automated, Personalized Outreach

In today's fast-paced business environment, speed and tone both matter. Copilot inside Business Central can draft collections emails tailored to each customer's situation—pulling in invoice details, payment history, and prior conversations—so AR specialists spend their time reviewing and sending rather than writing from scratch.
Automated workflows handle the routine cadence (first reminder, second notice, escalation) while preserving the human judgment needed for sensitive accounts. The result: every customer gets a timely, appropriate touch, without burning out the team.
For example:

• Copilot can draft a polite reminder for a top-tier customer and a firmer notice for a chronically late payer—using the same source data
• Workflow rules can automatically generate payment plans for invoices over a defined threshold and route them for approval
• AI agents can log every interaction back to the customer record in Business Central, eliminating shadow spreadsheets

With personalized automation, finance teams collect faster without sacrificing the customer relationships that drive long-term revenue.

3. Real-Time Cash Flow Visibility

CFOs can't make confident decisions on capital, investment, or hiring without a reliable view of incoming cash. AI-powered collections in Business Central close the gap between activity and insight—every customer interaction, payment commitment, and risk signal feeds directly into the cash flow forecast.
By leveraging AI, finance leaders can:

• Forecast collections by week and month with confidence intervals, not guesswork
• Identify customers whose payment behavior is changing—before it shows up in the aging report
• Quantify the impact of collection actions in real time, so the team knows what's working

This real-time visibility turns collections from a backward-looking function into a forward-looking lever for working capital and strategic decision-making.

The Phased Approach to Implementing AI-Powered Collections

At KTL Solutions, we help CFOs and finance leaders adopt AI-powered collections in a practical, phased approach. This ensures finance teams experience quick wins while building toward long-term scalability.

1. ERP Stabilization

We begin by stabilizing Business Central—cleaning up customer master data, aligning payment terms, and streamlining existing AR workflows. This baseline ensures the data feeding any future AI model is accurate and the team is working from a single source of truth.

2. Data Governance

We establish data governance practices specific to collections: consistent customer segmentation, clean aging categories, standardized interaction logging, and clear ownership of every account. High-quality data is the foundation of every reliable AI recommendation.

3. System Integration

We then integrate Business Central with the surrounding finance and customer ecosystem—banking platforms, CRM, customer portals, and communication tools—so AI has full visibility into every signal that affects payment behavior.

4. AI Enablement

Finally, we introduce Copilot and AI-driven collections capabilities in Business Central—enabling predictive scoring, automated outreach, and real-time forecasting. This phased rollout lets finance teams adopt new capabilities without disrupting the day-to-day work of getting paid.

Conclusion

For CFOs and finance leaders, healthier cash flow requires more than working harder at collections—it requires the ability to predict, prioritize, and personalize every customer interaction at scale. Traditional ERP environments can't deliver that level of intelligence, but AI-powered collections inside Business Central can.
At KTL Solutions, we help finance teams modernize collections through a structured, phased approach—turning AR from a reactive function into a strategic driver of working capital. By combining Business Central, Copilot, and proven integration practices, we enable CFOs to shorten DSO, sharpen forecasting, and deliver measurable value to the business.
Because cash flow waits for no one—and neither should your collections process.
Contact us: https://www.ktlsolutions.com

The post Why CFOs Need AI-Powered Collections in Business Central Now appeared first on ERP Software Blog.

Managing complex product configurations and accurately generating BOMs and routings can be manual and error-prone. This topic is most relevant for manufacturing and assemble-to-order business roles seeking clarity on streamlining configuration workflows.
Complex product configurations increase the risk of inconsistencies in quotes, production plans, and customer expectations. Understanding how to automate BOM and routing creation, apply advanced rule logic, and use dynamic pricing improves accuracy and reduces manual effort in managing configurable products within Business Central.

• Automated BOM and routing creation
• Advanced rule builder for product configurations
• Real-time dynamic pricing for quotes
• Streamlining management of configurable products

Watch the full recording
The recording is structured into chapters that walk through how the Product Configurator app improves Business Central's capabilities.
0:00 — Welcome & agenda (Product Configurator overview)
1:12 — Insight Works overview & free apps
5:00 — Why use a Product Configurator (CPQ concepts)
8:01 — Demo: configuring a computer (sales order workflow)
12:15 — Assembly orders, BOMs, routings, and item creation
16:00 — Editing configurations & additional choices
18:04 — Quoting items vs real items (table example)
22:59 — Production orders & passing instructions to the shop floor
26:59 — Smart item numbers & item conversion
27:59 — Demo: bicycle configuration with images
31:00 — Printing quotes & confirmations
31:47 — Bulk configurator (multiple configurations at once)
35:58 — Configurator setup: item categories & numbering
39:58 — Options, choices, pricing, and hidden logic
47:00 — Rule Builder: conditional logic & automation
55:00 — Pricing, implementation, and wrap-up

About InsightWorks

Just a little bit about InsightWorks: we've been around for just over 10 years now as InsightWorks, and we've got a lot of applications for Business Central—both on-prem and in the cloud.
We work primarily through our reseller partners. So if you have questions on pricing or implementation or things like that, and your existing Business Central partner is one of our resellers, they should be able to help you out. Otherwise, I'll give you some contact information at the end of the presentation, and you can contact us directly.
On the side here, you can see we've got quite a few apps. Each of these blocks is one of our apps, and Product Configurator is one of those. It's going to help you build your configurable items, your bills of materials, and your routings that feed into the production and assembly modules in Business Central.
We work primarily in manufacturing and distribution. We do quite a bit there, with a very large number of customers using our software on a daily basis to run their operations.
We've got over 34,000 installs from AppSource now. We do work with cloud and on-prem, as I mentioned. And with that, of our applications, we do have a number of free applications that are available. These are predominantly for Business Central Cloud. You can go into AppSource and install them—there's no licensing or registration required.

Free Apps Highlighted

The Graphical Scheduler: if you're doing anything with production orders or assembly orders—which will likely be the case if you're building configurable products, or really anything that you want to show graphically on a time base—the Graphical Scheduler is likely for you.
The default is production orders, but you can plot anything you like on the scheduler. For example, if you're using warehouse picks for your components, it has a pick assignment screen where you can go in and do pick scheduling and assign picks to individual people using the Graphical Scheduler, or whatever information you want to show on that. So it's very configurable, a nice little tool—again, completely free.
Doc Extender is drag-and-drop document management. Business Central has some support for drag-and-drop now, but Doc Extender is easier to use. The big advantage is that it supports uploading to SharePoint with a nice folder structure that it creates.
So if you're dropping documents onto a sales order, you don't need a Business Central license to go into SharePoint and view those documents. Then you can also add SharePoint automation, like alerts and revision histories and things like that. With that, you have a pretty comprehensive document management solution just by plugging in Doc Extender and using it with SharePoint.
For example, if you're working on a sales quote for a prospective customer and they provide you a PDF with their specifications for the product that they want you to configure, you can drag and drop that file into the sales quote and have it saved and stored for easy access.
In the middle here, we have our Import-Export Power Tool. This allows you to easily import and export data in Business Central. If you've ever used configuration packages or RapidStart, you'll understand how long it can take sometimes to process those imports and exports.
The Import-Export Power Tool does all of that and more in a fraction of the time. That's a very useful tool along with the configurator. If you're coming from an existing CPQ, or using spreadsheets, you can map your data to the Product Configurator tables and use the Import-Export Power Tool to quickly migrate or upload that data into Business Central.

Why Use Product Configurator

Let's talk about why you might want to use the Product Configurator—and CPQs in general. You can use them whenever you're selling or creating configurable products.
In the demo today, we'll be configuring computers, a table, and a bicycle, but our Product Configurator is currently used in a wide range of industries—from heavy equipment, furniture, and building materials to electronics and medical devices. The applications really are endless.
If you have standard product lines and you can configure those products, that is when you would want to use the configurator. If you've ever created items with bills of materials and routings manually in Business Central or NAV, you know how long that can take. Our Product Configurator saves you time and does the heavy lifting for you.
It's going to help you simplify that data entry process for your sales team, improve efficiency and accuracy, and whatever you need really to create those configurable items. It's all built directly into Business Central or NAV.

Key Benefits and Features

A big benefit is that it's built into Business Central or NAV. It's not external, and that means you can use the configurator on a sales quote or a sales order—we'll look at that today.
Or if you're in engineering, you can use it independently as well. Suppose you're part of the engineering or product design team—you can use it to create items ahead of time. But it's primarily meant for the sales team to quickly create configurable products with pricing details and reference data, such as the production BOM and routing, or the assembly BOM, so that the item can be used immediately by your business.
It's very easy to set up and use. There are many other configurator products out there, and regardless of the product, it takes time to set up the rules and the options before you can start using it. We try to make those tasks as simple as possible so you can be up and running in a very short time.
Product Configurator has many features we'll be looking at today. One is the Bulk Editor—where, say, you're selling several items from the same product line on a sales order, you can configure the items in a spreadsheet-style view to make data entry more efficient. We'll see that a bit later on.
Another feature is the ability to create complex rules and formulas using our Rule Builder application. That lets you build up your own custom logic in a simple, user-friendly interface.
And it's an inexpensive solution relative to other products currently available on the market. A lot of CPQ tools out there can add significant cost and time to get set up and running. Our Product Configurator can likely do everything you need for configuring products in Business Central, with a much lower cost and setup investment compared to other solutions.

Demo Setup in Business Central

That's enough of the slides for now. Let's take a look at the software in action. I'm going to switch over to Business Central here.
I will mention that our Product Configurator is also available for NAV. In NAV, you won't have the advanced Rule Builder and some of the new features that we see here today. But for Business Central, it's available for both on-prem and cloud, and today we're going to be using it in the cloud.
To set the stage, let's imagine we're part of the sales team. We get a request from a customer to buy a computer. We could start with a sales quote or a sales order depending on our business process, and today we'll use a sales order.
I'm going to create a new sales order, choose our customer, and then to configure a product I'll select this empty sales line and then select Line, Configurator, and BOM Designer.

Configuring a Personal Computer in BOM Designer

The BOM Designer is the worksheet that we're going to use to configure the product. If it's a new sales line like this, it opens like a blank canvas. To start, we select the item category for the product we want to configure.
If I open the dropdown, this includes the products or product lines that we sell and configure. If we're selling personal computers, we might have several product lines—desktop, laptop, or even more specific offerings. But in our setup here, we've kept it very simple and we just have a single category for personal computers.
So I'm going to choose the PC category, and the BOM Designer refreshes with all the options I can configure when selling this PC—processor, memory, hard drive, and so on.
I can go through these options and select choices based on the customer's request. This is using some older Microsoft sample data, so it's a little dated, but it's fine for demonstration purposes.
I'll select a processor, choose some RAM, and you'll notice the quantity defaults automatically, but I can change it—maybe the customer wants two sticks of RAM. As I make these choices, the total line price updates to reflect the choice and quantity, and it's also building up a rolled-up cost for the product.
I'll choose a hard drive, and down at the bottom we have summary information: total MSRP, expected total cost, and if weight calculations are included, expected weight.
You may notice the total sale price is more than the sum of the visible line prices. That's because it includes hidden options—components we always include when configuring a computer, like assembly labor, shop supplies, or other standard components that aren't directly chosen by the salesperson.
So that's a simple example: we select options, it calculates the price, and once we're happy with the configuration, we click OK.

Item Creation, Description, and Comments

When we click OK, it takes us back to the sales order and creates an item for us. In this case, the item is set up as an assembly order item, so it created the item, created the assembly BOM, and added the item to the sales line.
The description is generated based on the choices we made—processor, RAM, and hard drive—and it also added comments based on those choices. These comments can be formatted using rules you set up, so you can see the information the way you want to see it.
You can even take it further and have those same comments added to the production BOM or the routing, or in this case the assembly BOM. For example, you might want to pass special instructions to the shop floor—like cut-to-length measurements captured in the configuration.
These comments are optional, but they can be very useful. And if I scroll to the right, you can also see it included the unit price and unit cost it calculated as well—so it did a lot of the heavy lifting we'd normally need to do manually.

Assembly Order and Item Card Review

I'm going to take this a little further and create an assemble-to-order assembly order so we can look at the component lines. When we open the lines, we can see the components match the choices from the configurator—processor, RAM, hard drive—and we also see assembly labor that we didn't choose directly, but it was included automatically.
Next, let's look at the item card that was created. Here's the item number and description that was generated automatically. Scrolling down, we can see unit cost and unit price, and if we open the assembly BOM, we see the bill of materials that the Product Configurator created for us.
One other thing: when it created this item, we had it set up to insert item attributes as well. Based on the components and quantities selected, it created item attributes, which can be useful for reporting or searching for items with specific attributes.

Editing an Existing Configuration and Additional Choices

Back on the sales order, imagine the customer wants to change something—say they want to add a monitor. We can open the BOM Designer again from the existing sales line, and it loads the same configuration so we can make changes.
For the monitor, we have two standard choices, but if they want a larger monitor and we only stock certain sizes, we can use the Additional Choices functionality to select non-standard items from our item catalog lists.
This allows salespeople to select from a much larger list of products that are accessible to them, so they can build the product exactly how the customer requires.
Also, when we configured this item, we had it set up to create an actual item. Another option is to only create the bill of materials and routing, which can be useful for a one-off item you're unlikely to sell again in that exact configuration.

Configuring a Table with Groups, Mandatory Options, and Rules

Now let's imagine the customer asks for a table to put the computer on. We'll go to a blank sales line and open the BOM Designer. When it opens, we select the item category for the table.
This one has a bit more going on than the computer. You can see styling and grouping, and we can flag options as mandatory. If the user hasn't selected a choice, the name appears in red; when it's satisfied, it turns green.
We also put options in groups to make it easier to follow—like a tabletop group, legs group, and a components and labor group. The flow is the same: choose options, calculate price and cost.
I'll choose a thickness, set a length and width, select walnut material, set the height, and choose a leg type. When I chose the leg type, you'll notice the leg type size option suddenly appeared. That logic was built using our Rule Builder—so it conditionally shows or hides options depending on what the user selects.
There's also a rule that conditionally shows which size choices are available based on leg type. If the leg type is round, you see the round size choices; if it's beveled, you see beveled choices.
For this category, you'll notice the total line price is zero. That's because the design is set up to calculate total price and costs using hidden options intended to give us a net price and net cost based on the choices made.
Once we're happy, we click OK and return to the sales order. It updates the sales line, brings in a generated description and formatted comments. The comments for the table are formatted in a more customer-friendly way, and you can format them however you want.