Updated recently
Last updated:
Quick Answer: This Dynamics 365 Business Central guide explains what the product actually contains and how a business runs on it: sales and purchase flows, inventory and costing, the posting model that sits underneath every document, bank feeds and reconciliation, the extension ecosystem and the Shopify connector. The mental model to carry away is simple — Business Central is a document-driven system where posting is the moment a document becomes a ledger entry.
Who Should Use This Dynamics 365 Business Central Guide — and Who Should Not
Business Central is Microsoft’s all-in-one ERP for small and mid-sized organisations, typically 10 to 500 employees. It carries accounting, sales, purchasing, inventory, basic manufacturing and a light CRM, on a single database, with a depth of extensions that genuinely surprises people. In India it is the standard answer for a mid-sized manufacturer or distributor replacing Tally, a legacy ERP, or a heroic set of spreadsheets.
Three groups should read this and reconsider. If your business needs detailed production scheduling, multi-level engineering change control or plant-level costing, you want Dynamics 365 Supply Chain Management — Business Central’s manufacturing module is basic and will not stretch. If you are a multi-entity group needing consolidated statutory reporting, you want Dynamics 365 Finance. And if you are a developer who wants to build products rather than configure systems, the AL extension platform is where the interesting work is — Business Central is a great platform to build on, and a mediocre platform to merely configure. Our Dynamics 365 complete guide covers how the three Dynamics ERP options divide up, and the pay bands for this role are in the Dynamics 365 Business Central salary India 2026 guide.
What Business Central Actually Contains
| Area | What it covers | What a consultant really configures |
|---|---|---|
| General ledger | Chart of accounts, journals, periods, dimensional analysis | Account lists and number series, journal templates, global dimensions and dimension sets, posting groups and posting profiles, year-end close |
| Sales | Quotes, orders, invoices, credit, receivables | Customer cards and customer groups, sales quotes and orders, posting policies, payment terms, reminder levels, credit management |
| Purchasing | Requisitions, orders, receipts, invoices, payables | Vendor cards and vendor groups, purchase requisitions and orders, item and vendor ledger setup, invoice and payment posting, three-way matching |
| Inventory | Stock, locations, costing, traceability | Item cards and item categories, units of measure and conversion, locations and bins, costing methods (FIFO, LIFO, average, specific), available-to-promise, lot and serial tracking |
| Manufacturing | Basic production, routings, BOM, work centres | Manufacturing item setup, bills of material and routings, work centres and calendars, production orders and consumption, subcontracting and assembly orders |
| Banking | Bank accounts, feeds, reconciliation | Bank account cards and currency, bank feeds and statement import, bank reconciliation and payment files, cash management and reminders |
| Project and fixed assets | Jobs, resources, timesheets, assets | Work codes and jobs, resource and timesheet setup, fixed asset cards and depreciation books |
| Platform | Extensions, integrations, data exchange | AppSource extension selection and publishing, custom fields, AL development, OData and API integration, Excel and Outlook add-ins, Power Automate and Power BI connections |
The Posting Model: The One Concept That Makes Everything Click
Business Central is a document-driven system, and everything in it revolves around one moment: posting. A sales invoice, a purchase invoice, a receipt, a payment, a journal — each is a document while it is open, and each becomes a set of ledger entries when it is posted. Before posting, it can be edited. After posting, it is largely immutable, and corrections happen through reversal or credit notes.
Every posting produces two families of entries. Ledger entries record the financial and quantity effect: customer ledger entries, vendor ledger entries, general ledger entries, item ledger entries and value entries. Posted documents record what caused them — a posted sales invoice, a posted purchase invoice, a posted receipt. Documents are linked to their entries, which is how the system can show you “this invoice was for order SO-1142”.
Conceptual illustration — the posting model in Business Central
(the object relationships, not a screen path)
Sales Order (open, editable, no accounting effect)
| Post (correct quantity, price, account, dimensions)
v
Posted Sales Invoice
|--> Customer Ledger Entry (the receivable: who owes what)
|--> Item Ledger Entry (the quantity: what left stock)
|--> Value Entry (the cost and value movement)
|
+--> Posted Sales Receipt (if shipped separately)
|--> Item Ledger Entry (the quantity: what arrived)
Why this matters:
- Invoice without receipt => quantity mismatch, "order completed" flags it
- Costing only updates when a value entry is created
- A correction is a reversing entry or credit note, never an edit
Two behaviours follow that every consultant needs to explain to a customer. First, the cost of an item only becomes real when value entries are created, which happens at receipt or shipment and depends on the costing method. If a customer is seeing zero margin on sales, the usual cause is a costing setup problem rather than a pricing problem. Second, invoice and receipt are separate documents, and a customer who invoices before shipping creates a quantity mismatch — the invoice has a customer ledger entry but the matching item ledger entry arrives later, and standard “order completed” reports flag the order as incomplete until they reconcile.
Sales, Purchasing and the Everyday Flows
The sales flow is: request or quote, sales order, delivery, invoice, payment. The purchasing flow is: purchase requisition, purchase order, receipt, invoice, payment. Both are supported by posting policies that determine what a document does when it is posted — whether it requires an inventory receipt or invoice first, whether a payment is a direct deduction, whether partial posting is allowed, and which posting profile picks the accounts. Posting policies are the cleanest configuration object in the product and the one most customers should be told about, because they remove the ambiguity from “what happens when I post this”.
Inventory is where the detail lives. Items carry an item category that determines their behaviour — whether they are stocked, whether they are purchased, manufactured or assembled, how they are costed, and how they appear on the ledger. Units of measure and conversion factors, locations and bins, lot and serial numbers, and reorder policies all hang off that setup. Get the item categories right and most inventory problems never appear; get them wrong and the customer spends years working around a system that is behaving exactly as configured.
Manufacturing, Bank Feeds and the Extension Ecosystem
Manufacturing in Business Central is real but basic: bills of material, routings, work centres with calendars, production orders, consumption and output. It suits assembly and light fabrication. It is not a plant scheduling system, and any implementation that promises one is setting up a dispute. Subcontracting and assembly orders cover the two most common mid-market models.
Bank feeds and reconciliation have improved a lot. Bank account cards carry their own currency and ledger posting setup, statements can be imported directly from the bank in supported regions, and reconciliation matches statement lines to ledger entries with automatic suggestions. Payments can be exported in the formats Indian banks expect. If your customer is still maintaining a parallel Excel cash book, this is often the single highest-value configuration change you can make for them.
Extensions are the strategic story. AppSource is a deep marketplace with thousands of apps — accounting localisation, e-commerce connectors, manufacturing add-ons, field service, quality, payroll and vertical solutions. Alongside first-party extensions, you can add custom fields through the Extension platform without code, and larger requirements get written in AL. The practical advice for an implementer: configure what is genuinely core, extend what is different, and never customise a standard object where an extension will do, because customisation is what makes upgrades expensive. For the e-commerce conversation specifically, the Business Central Shopify connector is the standard route for mid-sized merchants, syncing products, inventory levels, customers and orders.
War Story: The Posted Invoice Nobody Shipped
A mid-sized electronics distributor in Pune went live on Business Central in late 2025, replacing an old ERP with a spreadsheet interface. Six weeks after go-live, their operations manager sent a screenshot of the “Order Completed” report with a red flag on every order, and the sales team had started ignoring it entirely because, in their words, “the system says nothing is ever finished”.
The cause was a posting policy decision made during configuration. Invoices were set to be posted directly from sales orders without a preceding shipment, because the customer’s workflow was to invoice on delivery confirmation and the delivery note was tracked separately on paper. Every posted sales invoice therefore created a customer ledger entry and a value entry, but the matching item ledger entry for the shipped quantity did not exist until the receipt was posted days later. The order status logic compares what was invoiced against what was delivered and, seeing the gap, flagged every order.
The fix was a configuration change rather than a customisation: the sales order posting policy was changed so that a posted receipt is required before a posted invoice, and the delivery note was configured to post the receipt automatically. This moved the invoice to the moment of shipment, which is also what made the tax treatment correct in the eyes of the customer’s accountant, because the invoice date now matched the dispatch date. The reporting mess disappeared within a fortnight.
The lasting lesson is the one worth repeating to every Business Central customer: “completed” is computed from ledger entries, and if your operational reality does not match how the documents are posted, the reports will tell you so loudly and forever. It also demonstrates something about the product that surprises clients — a problem that looks like a reporting bug is nearly always a posting policy decision made in a hurry during configuration.
Training Resources
Work through the modules and the posting logic with SkilBrill Power Platform Functional Consultant Training — Dynamics 365 Business Central functional design, inventory and costing setup, extensions and integration practice, with case-based labs and career support.
FAQ
What is Dynamics 365 Business Central used for?
It is Microsoft’s all-in-one ERP for small and mid-sized organisations, covering sales, purchasing, inventory, accounting, basic manufacturing, bank feeds and e-commerce. It replaces separate accounting packages and spreadsheets with one database and a deep AppSource extension ecosystem.
What does posting mean in Business Central?
Posting is the moment an open document becomes a permanent record. It generates the ledger entries — customer, vendor, general ledger, item ledger and value entries — and links them to the posted document. Before posting, a document is editable; afterwards, corrections require a reversal or a credit note.
How long does a Business Central implementation take?
Typically 6–14 weeks for a mid-sized business, including data migration and one parallel close. The long pole is rarely configuration; it is cleaning up legacy data and agreeing how the business actually wants to post transactions.
Can Business Central integrate with Shopify?
Yes, through the Business Central Shopify connector available on AppSource, which synchronises products, inventory, customers and orders between Shopify and Business Central. It is a common requirement for mid-sized Indian merchants selling online alongside offline.
Is Business Central suitable for a manufacturing company?
For assembly and light fabrication, yes — it handles bills of material, routings, work centres, production orders and subcontracting. For complex scheduling, detailed engineering change control or plant-level costing, choose Dynamics 365 Supply Chain Management instead.
