Book a Meeting
Contact us
Book a Meeting
Contact us
Book a Meeting
Contact us
Book a Meeting
Contact us
Contact Us
AccSoft

Business Central

Migrating from Legacy ERP to Business Central: Lessons Learned
06
Apr

Migrating from Legacy ERP to Business Central: Lessons Learned 

Migrating from a system is not just about the system; it is about transforming the way your company works. If you are about to embark on the journey to the cloud, here are the hard-earned lessons we learned along the way.  1. “Lift and Shift” is a Trap  The biggest mistake companies make is treating the migration as a copy-and-paste operation. They want to take their messy, convoluted processes from the old system and copy them over to Business Central.  The Lesson: Don’t automate a bad process.  Legacy systems are often messy because the software couldn’t do what the business needed. It required workarounds. Business Central is a much more capable system. Take advantage of the migration to think about your processes. If your old system required five steps to approve a purchase order, see if Business Central can’t do it in two. If you try to make Business Central look and act exactly like your old Legacy system, you will be throwing money away.  2. Data Hygiene is Non-Negotiable  Business thought they had clean data. They didn’t. On extracting data from the old system, we usually discover that there were thousands of obsolete customer data, duplicated vendor data, and inventory items that were not sold in the last ten years.   The Lesson: Don’t boil the ocean.   Don’t migrate everything. You’re moving into a new house. Don’t bring the trash with you.   Archive the old data. Keep the old system accessible. Make it read-only.   Cleanse the master data. Customers. Vendors. Items (GL accounts).   Bring the opening balances. Do bring relevant historical data but not ten years of closed transactional history.  3. Configuration vs. Customization  This is the Golden Rule of Business Central. In the old days, we used to customize the code for everything. We wanted the button to be blue, not grey. We wanted the report to be printed in a specific font.  The Lesson: Stay Standard (Standard = Good).  Every time we customize the code in BC, we make it harder and costlier for future upgrades.  Try and configure the system using standard settings.  Try and look for App Source extensions/add-ons rather than customizing code.  Customize only if it gives you a competitive advantage.  4. The “Excel Trap” is Real  One of the most powerful features of Business Central is its native Excel support. However, be warned that it is also one of the most insidious “features.”  During the go-live of our project, we had users who were afraid of the new UI. Instead of learning how to enter a sales order in BC, they were trying to download everything into Excel, manipulate it there, and paste it back into the system.   The Lesson: Train Early and Train Often  Change management is harder than the technical implementation. People need to be convinced that Business Central is easier than their spreadsheet hell. Invest in “Champion Training” find super users in every department who will be able to pressure their co-workers into using the system correctly.  5. Your Partner Matters More Than the Software  Business Central is a wonderful product, and it’s a platform. It needs a partner to implement it. Chose a partner based on a bid price, and it was a disaster waiting to happen. Chose the lowest bidder, and they treat like a number.   The Lesson: Find a partner that understands your industry, not just the software.  A retail implementation versus a manufacturing implementation is vastly different. Changing partners halfway through the project to one that specialized in the industry costs you more.  6. The Go-Live is Not the Finish Line  Go Live day is, crossing the starting line at a marathon.  The First Month Was a Bumpy Ride  Users forgot passwords. Reports looked a little different. Changes needed to posting groups etc.  The Lesson  Plan for a “Hypercare” period. For the first 4 to 6 weeks after Go Live, be prepared to need extra support. Keep your implementation partner on speed dial. Don’t consider your project complete until you have successfully closed a month-end and run your payroll.  The Bottom Line  Migrating from a legacy ERP system to Business Central is hard. It takes money, time, and a thick skin.  But is it worth it? Yes.  You will have a real-time visibility into business. Can close financials in days instead of weeks. Remote workers can access data from anywhere and you don’t have to think about server maintenance anymore.  If you are considering making the move from a legacy ERP system to Business Central, take the leap, clean your data, and trust the process for your journey to the cloud.
Continue Reading
From APIs to AI: How MCP Changes the Way Systems Integrate with Business Central
09
Mar

From APIs to AI: How MCP Changes the Way Systems Integrate with Business Central 

The “Golden Rule” of systems integration has been simple: if you want to talk to Business Central (BC), you use an API. Whether it was OData, SOAP, or even the newer REST endpoints, developers write code to integrate between external systems and the ERP. And it worked. But it was rigid, expensive, and hard to maintain.  But now, we find ourselves at the precipice of an enormous change. With the advent of Generative AI and LLMs, it is no longer sufficient to simply expose an API. We need systems that can understand context, not just exchange data.  Enter The Model Context Protocol (MCP).  In this article, we’re going to explore how MCP is changing the game in terms of Business Central integration.  The Old Way: The “API Spaghetti” Problem  To understand why MCP is a gamechanger, we first need to understand the problems with the status quo.  The pain point here is that it’s a lot of work. Every time you want to do something new like posting a journal entry or checking the customer’s inventory, you have to do it all over again.   Enter MCP: The “USB Port” for AI  MCP can be thought of as a new “standard,” similar in concept to USB and Bluetooth, but for the data systems and AI.  Rather than requiring glue code for every single interaction between the AI and the data systems, the MCP provides a standardized and open-source protocol that allows the AI assistant to query the data systems securely.  In the context of Business Central, the MCP is a dynamic translation layer that allows the AI model to query your ERP in real-time, without requiring you to create a specific API handler.  How MCP Alters Business Central Integrations  So, what are the implications for the BC developer or consultant?  1. “From Hardcoded Endpoints to Dynamic Discovery”  With traditional APIs, the AI is only able to do what you program into it. But what if you have an MCP server connected into Business Central? The AI can now “discover” what’s available.  For example, if the MCP server exposes the Business Central “Customer” table, the AI can automatically determine how to query the No., Name, or Balance fields without you having to write code like get_customer_balance.  2. Context Aware Interactions  Standard APIs are stateless; they don’t have any knowledge of the conversation history.  MCP is built with the goal of being context aware.  Scenario: “Who owes us the most money?”  Traditional: The API may simply return a list of customers.  MCP: The AI can use the protocol to first query the Detailed Cust. Ledg. Entry table, compute the open balances in real-time, and then ask the user, “Do you want me to send a reminder email to the top 3 overdue accounts?” The integration is not just a simple retrieval; the API is participating in the process.  3. Secure, Governed Access  One of the biggest fears of integrating AI with ERP is security. You do not want a chat session with an AI to accidentally change your General Ledger setup.  MCP servers operate locally or in your infrastructure. This means you can use standard BC security permissions. If the user of the AI question being asked does not have permission to DELETE in the Sales Header table, the MCP server will simply not allow it. They bring their standard BC permission set into the AI conversation.  4. Eliminating “Connector Fatigue”  Today, to integrate a niche app into BC, we must develop a connector. With MCP, however, if a third-party app (such as a niche app for inventory scanning or a niche app for human resources) supports the MCP standard, it will instantly connect to your Business Central AI environment.  The Future is “Agentic”  MCP is not just integration; it’s “Agency.”  Business Central was once just a database, just waiting for the application code to tell it what to do. Now, with the protocol, Business Central is an active participant in the world of business intelligence. An AI agent can always monitor your data and only alert you, when necessary, like when the stock level of an item plummets or when the price of the item in a purchase order is wrong.  Conclusion  APIs aren’t going away anytime soon. Business Central will always need OData and REST for rigid system-to-system heavy lifting to integrate between external systems But for the new generation of intelligent automation: Co-pilots, agents, chatbots… the missing piece is the Model Context Protocol. It turns Business Central from a traditional ERP into a smart platform that any AI can talk to.  For developers and architects: the message is clear: Start thinking about context. The end of the era of static integration is near. The era of intelligent agentic integration is upon us. 
Continue Reading
The Best Automation Workflows to Set Up in Business Central This Quarter
09
Feb

The Best Automation Workflows to Set Up in Business Central This Quarter

As we settle in with the quarter and the initial rush to plan is over, the reality of the daily grind has set in. For finance and operations teams using Microsoft Dynamics 365 Business Central (BC), this is the perfect time to pause and ask a critical question: Are we working for the system, or is the system working for us?  If your team still does any manual data crunching, copies and pastes invoices, or sends approvals around via email, then you’re leaving efficiency on the table.  Automation in Business Central is not about replacing the humans; it’s about freeing your team from repetitive administrative tasks and granting them time for strategy and growth. Here are the top-priority, high-impact automation workflows you should set up this quarter.  1. Finance: Automated Payment Reminders & Collections  Cash flow is the lifeblood of your business. But most accounting teams spend a considerable amount of time every week going over aging reports and composing emails to follow up on late payments.  The Workflow:  Establish in BC the “Reminder Levels” feature to automatically draft and send customers emails for reminders, based on due dates. How it works: You define the terms, such as sending a polite nudge at 7 days past due, a firm notice 14 days past due, and final demand at 30 days past due. BC calculates the interest/fees if applicable and sends the email out under the standard email logging setup.  2. Sales: The “Quote-to-Order” Conversion  Sales reps live in their inboxes or CRMs. When a client approves a quote, the last thing they want to do is log into BC and key up the data again to make an order.  The Workflow:  Use the “Make Order” functionality or integrate it with Power Automate to enable conversion. How it works: Once a quote status has been updated to “Accepted” within Business Central the quote will automatically be converted into a Sales Order. It can then trigger immediately a warehouse pick instruction.   3. Inventory: Smart Reorder Point Triggers  Stock-outs kill the sale; overstock kills cash flow. Finding this “Goldilocks” zone is usually a manual guessing game for purchasing managers.  The Workflow:  Deploy Replenishment Worksheets based on defined Reorder Points. How it works: You put in a “Reorder Point” for each SKU. When the inventory falls below that number, BC flags it automatically. Going a step further, you can create a Job Queue that will automatically create a Purchase Order suggestion by approval, per vendors’ lead times.   The ROI: You move from a reactive purchasing model-buy only when you run out-to a predictive one. This prevents stockout during peak demand and reduces excess inventory capital.  4. Operations: Bank Reconciliation using Feeds  Reconciliation of bank statements is usually the biggest time killer in finance. Matching items on your bank statement to items in your ERP system by hand is time-consuming and prone to errors. Establish the connection for Bank Feeds.   How it works:   Bank transactions are automatically fetched to BC every day. The system enables “Application Rules” for auto allocation of received payments to customer invoices and for outgoing payments to vendor bills.   5. Administration: Automated Approval Workflows  Is a purchase order above $5,000 signed off by the CFO or is a sales discount above 10% signed off by the VP? These signatures need to stop being recorded in Slack threads.  The Workflow:  Set up Approval Workflows in BC. “How it works: You set up a logic chain, like “If Document Type = Purchase Order and Amount > $5,000, Then Notify User = ‘CFO.’” The approver will receive a push notification within BC, which they can accept through the mobile app. The document will be “locked until approval is granted.””  Bonus – The Power Platform Integration  Although BC has native automation power in abundance, it reaches its true potential when integrated with Power Automate. For the current quarter, pick one “power user” workflow.  The Workflow:  Trigger: “CREATE: A new vendor is inserted into table ‘Vendors’.  Action Type: Automatically add the vendor to the “Vendor Onboarding” SharePoint List and place a message inside the Microsoft Teams channel alerting the procurement team to obtain insurance information.  Outlining a Business Plan      Rather than trying to automate all of it at once, you will inevitably overload your team and IT infrastructure. This quarter, pick one of the workflows from the above list where your business feels the most pain.  Map Process: List in detail how it is done currently.  Bottleneck: Identifying Where the Human Component Slows Things Down  Configure: You can make use of BC’s assistant guides or involve your partner to configure the workflow.   The Bottom Line:   Automation in Microsoft Dynamics 365 Business Central (BC) is NOT an “future” project; it is something you NEED to do each quarter. By doing these tasks today, you are not just saving time; you are laying the groundwork for the rest of the year. 
Continue Reading
Multi-Location Inventory: A Day in the Life of the Business Central Replenishment Engine
05
Jan

Multi-Location Inventory: A Day in the Life of the Business Central Replenishment Engine

Managing inventory across several warehouses, stores, and distribution centres is one of the most difficult tasks in today’s business. Inventory misalignment, transfer delays, unnecessary purchases, and lost sales can quickly damage the bottom line and customer satisfaction. Microsoft Dynamics 365 Business Central solves this problem by using its own replenishment and planning engine, which continually assesses demand, availability, and geographical-based inventory to maintain your network in a balanced state. In this article, we will walk through how Business Central accomplishes multiple locations when it comes to inventory on a day-to-day basis. Demand and Inventory are Re-Evaluated As the orders begin to flow in, whether through e-commerce, POS terminals, or B2B sales, Business Central can record this demand and update the inventory automatically by location because of every sale, every shipment, and every return. The replenishment engine evaluates: Rather than being responsive in times of shortage, Business Central is proactive in determining possible risks of stock. Location-Level Planning Begins Business Central looks at inventory planning by location, not only on a global basis. This is very important in a multi-site environment. The system assesses: On this basis, Business Central establishes whether to meet the demand by: This is to ensure that there is no unnecessary buying considering that products already exist in other parts of the network. Planning Parameters Shape Intelligent Decisions Each replenishment proposal is based on the planning configuration of each item, which consists of the following: These enable Business Central to calculate the following: This makes the replenishment process predictable rather than a result of guesses. Actionable Recommendations are Generated When planners open the Planning Worksheet, they will see the following ‘Action’ suggestions: These recommendations already take into consideration what supply already exists, as well as transit inventory. In planning, requirements are reviewed and approved instead of calculated. Execution After approval, the following are created automatically by Business Central: For transferring, the system: For the purchases, it records: Each step is monitored, and it is quantified through inventory availability. Continuous Re-Planning As the shipment is sent, the following is calculated in Business Central: The planning engine is never static. It keeps changing based on what happened during the day. Why This Matters Without a Replenishment Engine, multi-location businesses typically face the following issues: Business Central eliminates these issues by keeping every location aligned to actual demand and available supply. The result is: Conclusion The Business Central replenishment and planning engine is a background process, but it certainly plays a central role in the flow of multi-location operations. Continuous assessment of demand and supply, along with location-level inventory, makes sure the right products are in the right place at the right time without the help of any person. For any organization managing inventory across several sites, this intelligent capability of planning is sure not to be helpful but indispensable.
Continue Reading
From Chaos to Clarity: How Business Central Cleans Up Your Master Data (If You Let It)
08
Dec

From Chaos to Clarity: How Business Central Cleans Up Your Master Data (If You Let It) 

Master data is the backbone of your ERP: your items, customers, vendors, G/L accounts, BOM’s, dimensions. But in many organizations, it quickly turns into a tangled mess: duplicated items, inconsistent naming, missing dimensions, incorrect posting groups, outdated pricing, and unused vendors collecting dust.  The good news?  Business Central is built with powerful master data hygiene tools. But here’s the catch: BC can only clean up your data if you let it. In this blog, we will explore how Business Central transforms master data chaos into clarity, reliability, and automation.  Where the Chaos Begins: The Cost of Bad Master Data  Before we delve into the clean-up, let’s acknowledge the pain. Bad master data creates:  Most ERP issues don’t come from the system; they come from inconsistent or incomplete master data. Business Central solves this with built-in intelligence, validations, templates, and automation.  Templates-Standardization of Master Data to Standardized, Repeatable Setup  One of the most underrated strengths of BC is its Templates. You can create templates for:  Each template can pre-fill:  No more users manually guessing configuration. No more inconsistent setup. BC enforces consistency at the source.  Configuration Packages: Bulk Clean-Ups Without Chaos  Need to clean thousands of items or vendors? Realistically, you cannot change one field at a time. Enter Configuration Packages, BC’s master data Excel engine. You can export, clean, and re-import:  It’s the easiest way to do controlled mass updates while preserving data integrity.  Dimensions: How to Eliminate Reporting Chaos at Source   Dimensions are the secret weapon of Business Central against dirty financial reporting. They provide structure for:  BC lets you:  This ensures your financials, budgets, and Power BI reports are clean and meaningful.  Posting Groups: Preventing Financial Errors Before They Occur  Posting groups are assigned to each item, customer, and vendor that specify the G/L accounts affected when transactions take place.  If these are wrong → your financials break.  If these are right → your financials stay flawless.  BC uses:  This keeps your financial structure consistent, clean, and reliable.  Data Archiving & Deactivation: Cleaning Up Old Clutter  BC supports methods to keep your master data list clean:  Your lists remain accurate without losing historic data.  The Outcome: Clean Data → Clean Operations → Clean Decisions  When Business Central maintains master data integrity, every function benefits from this:  Your whole business becomes smoother, quicker, and more consistent.  Concluding Remarks:   Allow BC to do the cleaning, it was designed for this purpose. Business Central has one mission when it comes to master data: Prevent bad data from entering. Correct what is inside already. Keep going, be consistent. But the system can only do this if you use:  When you let Business Central enforce the structure, chaos turns into clarity. 
Continue Reading
The Role of Approval Workflows in Business Central
03
Nov

The Role of Approval Workflows in Business Central 

In any organization that’s growing, tight control over who is approving what, and when, is of the essence for ensuring accuracy, compliance, and accountability. Microsoft Dynamics 365 Business Central makes it easily possible with native Approval Workflows to automate and standardize approvals for purchases, sales, journals, and so much more. This article discusses what Approval Workflows in Business Central are, why they are important, and how they help in smoothing out business processes. What are Approval workflows in Business Central?  Business Central approval workflows define the process by which documents or transactions are routed through your organization for approval before they can be posted or processed.  They ensure, amongst others, that certain actions are not performed until reviewed or approved by designated users: whether this is approval of a purchase invoice, release of sales orders, or posting of a general journal entry.  Workflows enable you to:  Approval Workflows: Why They Matter  Approvals via email, calls, or spreadsheets are subject to a lot of errors and delays. Workflows within Business Central will eliminate these by embedding the approval right into the ERP system.  Here’s why they’re so critical:  Full Visibility and Traceability  Risk and Compliance Management  Types of Approvals You Can Automate  Business Central supports the following workflows across several business areas:  You can start working with either standard templates or you can create your own, custom workflows using the Workflow Templates feature.  Approval Workflows: How they Work  A simple Approval Workflows in Business Central looks like:  User Submits a Document : The user creates a document, for example, Purchase Order and starts a request for approval.  Workflow Triggers : Business Central checks conditions like document type, amount, or even the role of the user and assigns that to an approver.  Approver Reviews and Approves/Rejects  Approver is notified by BC or via email.  System Action Executes  Once approved, Business Central posts, or releases, the document automatically.  You can also establish rules of delegation so that approvals won’t get stuck when a manager is away from the office.  Getting Your Workflows Set Up: Tips  Start Simple: Start with one or two key workflows-say, purchase-order approvals-and when those are stabilized, expand to other areas.  Use Quantity Tolerances: Establish approval limits per level of responsibility, including up to $5,000 by department heads and above $5,000 by the CFO.  Enable Notifications and Reminders: Keep the process moving-ensure that users receive automated notifications about pending approvals.   Test Before Deployment: Sandbox environments can be used to make sure conditions and chains of approval behave as expected.   Leverage Power Automate: In advanced cases, use the integration with Power Automate in expanding workflows across Microsoft 365, including Teams notifications or multi-step conditional approvals.   Business Impact of Automated Approvals   Businesses that deploy approval workflows in Business Central usually:  By bringing approvals into Business Central, you create a controlled, transparent, and auditable business environment-without the inefficiency of manual processes.  Final Thoughts   Automation of approval workflows in Business Central is much more than just automating signoffs; it creates structure, accountability, and confidence in every business transaction. Be it purchasing, sales, or finance operations, with a well-designed workflow setup, no document moves without the right approval, and all approvals are traceable and efficient. Take the time to set up workflows thoughtfully, and once they are configured, they will save hours of manual effort and protect your organization’s financial integrity. 
Continue Reading