Business Central Features: A Complete Guide to the Modules

When people ask me what Business Central "does", the honest answer is that the question is slightly wrong. Business Central is not a thing that does one job well. It is a single connected business system that happens to cover finance, sales, purchasing, inventory, warehousing, manufacturing, projects, service and fixed assets from one database, with one set of dimensions and one posting engine underneath all of it. The trick to understanding it is not memorising every screen. It is understanding how the modules relate, because that relationship is where the value lives and where most implementations succeed or fail. This guide gives you the map, module by module, with a route into each deep-dive when you want detail.

The message up front: treat Business Central as one system, not a bundle of apps that happen to share a login. A sales order draws on inventory, drives a purchase, posts to the general ledger, and can flow through to a warehouse pick, all from the same records. If you learn the modules in isolation you will miss the part that makes the platform worth buying, which is how tightly they connect.

1. How to think about Business Central: one connected system, not a bundle of apps

The single most useful mental model for Business Central is that everything eventually becomes a ledger entry. Sell something, buy something, move stock, run a payroll journal, depreciate an asset, and the transaction lands in the general ledger through the same posting engine, tagged with the same dimensions, visible to the same reports. The modules you see in the navigation are really specialised front ends onto one shared financial and inventory core. That is why an inventory adjustment shows up in your margin analysis, and why a posted purchase invoice can update a vendor balance, an item cost, a fixed asset and a project all at once.

This design has two practical consequences worth internalising early. First, master data discipline matters more than in a loosely coupled toolset, because a single item, customer or vendor record is used everywhere and a mess in one place propagates. Second, you rarely need bolt-on integrations for the core flows, because they are already connected inside the product. Where I spend most of my integration work is at the edges, connecting Business Central to a CMMS, a CAFM platform, an e-commerce front end or a payroll engine, not stitching finance to inventory, which Microsoft already did.

If you are still deciding whether the platform fits your organisation at all, start with is Business Central right for your organization, and if you want the wider context of why a cloud ERP looks the way it does, cloud ERP explained sets the scene. The rest of this guide assumes you are past that decision and want to know what is actually in the box.

2. Financial management

Financial management is the heart of Business Central and the module every other module posts into. At its centre is the general ledger, driven by a chart of accounts and a flexible dimension model that lets you slice every transaction by department, project, region or any other analysis axis you define, without exploding the account structure itself. Around the ledger sit the subledgers most businesses live in day to day: accounts receivable and payable, bank account management with reconciliation, and the journals that handle everything from manual corrections to recurring accruals.

The financial module is where Business Central quietly does a lot of heavy lifting that people take for granted. Multi-currency is native, with exchange rate adjustment and realised and unrealised gain and loss handling. Deferrals let you spread income or cost across periods automatically. Bank reconciliation can import statements and match them against posted entries. Fixed period closing, dimensional financial reporting through account schedules, and consolidation across companies all live here. For a growing business this is usually the reason to move to Business Central in the first place, because spreadsheets stop scaling long before the rest of the operation does.

What I stress to finance teams is that the general ledger is not where you should be doing detailed analysis by brute force. The dimension model is the intended tool for that, and used well it replaces dozens of redundant accounts with a handful plus dimensions that reconcile cleanly. Get the chart of accounts and dimensions right at implementation and reporting becomes straightforward for years. Get them wrong and you fight the system forever. The full walkthrough, including account schedules and reporting patterns, is in the financial management deep-dive.

3. Sales order management

Sales order management covers the full quote to cash flow: sales quotes that convert to orders, order confirmation, shipment, invoicing and the receivable that follows. It is the module most of a commercial team touches daily, and Business Central models it as a sequence of documents that flow into one another rather than isolated forms. A quote becomes an order, the order ships and invoices, and each posting updates inventory, the customer ledger and the general ledger in one action.

The depth here is in the surrounding controls. Customers carry payment terms, price and discount agreements, dimensions and posting setups that flow automatically onto their documents, so pricing and coding do not depend on someone remembering. You can partially ship and partially invoice, handle order-to-order reservations, manage drop shipments where the vendor ships straight to the customer, and process returns through credit memos and return orders. Prepayments let you invoice a deposit before delivery. Availability shows whether stock can actually meet the promised date, pulling live from inventory and inbound supply.

The connection that matters most is the one between sales and everything downstream. A sales order is not just a customer document, it is a demand signal that planning, purchasing and the warehouse all respond to. When someone asks why their promised dates keep slipping, the answer is almost always that this connection was configured loosely, so orders were being promised without honest visibility of supply. Configure it tightly and the sales desk stops making promises the operation cannot keep. The detail, including reservations, prepayments and returns, is in the sales order management deep-dive.

4. Purchasing management

Purchasing is the mirror image of sales, running the procure to pay flow: purchase quotes and orders, receipt of goods, vendor invoicing and the payable that follows. The same document-flow design applies, so a purchase order receives into inventory and invoices into the vendor ledger and general ledger through one posting action, updating item cost along the way. Vendors carry their own terms, pricing and posting setups, so purchase documents inherit the right coding automatically.

Where purchasing earns its place operationally is in the controls around commitment and matching. Purchase orders create a commitment the system tracks against receipts and invoices, which is the basis of any credible three-way match between what was ordered, what was received and what was billed. Approval workflows can gate orders above a value or outside a budget before they are ever sent. Item charges let you fold freight, duty and handling into landed cost so your inventory valuation reflects reality rather than just the supplier line price. Blanket orders handle agreed volumes drawn down over time.

The purchasing module also feeds the planning engine, which is the quiet workhorse of the whole supply side. Requisition and planning worksheets look at demand from sales and production, current inventory, and reordering policies, then suggest what to buy and when, turning suggestions into purchase orders in a few clicks. For any business carrying stock this is where control of working capital actually lives. The complete flow, including approvals, item charges and planning, is covered in the purchasing management deep-dive.

5. Inventory management

Inventory management is the shared spine between sales, purchasing, manufacturing and service. Every item carries a costing method (FIFO, LIFO, average, standard or specific), unit of measure conversions, and posting groups that decide how its movements hit the ledger. Business Central tracks quantity and value together, so at any moment you can see both how much stock you hold and what it is worth, valued consistently by the costing method you chose.

The features that make inventory real rather than notional are the ones people underestimate. Item tracking handles lot and serial numbers for traceability and recall. Item variants and multiple units of measure handle the messy reality of how the same product is bought, stored and sold differently. Locations let you hold stock across sites. Item journals handle adjustments, reclassifications and physical count reconciliation. Reordering policies and stockkeeping units drive replenishment per item per location, so planning treats the same item differently in a warehouse than in a shop.

The honest caution: inventory is the module where bad master data hurts most, because errors compound silently. A wrong costing method chosen at go-live, unit of measure conversions that do not reconcile, or items set up without tracking when tracking was needed, are painful to unwind once thousands of transactions have posted on top of them. Spend the time on item setup before go-live. It is the least glamorous part of an implementation and the one that pays back for years.

Because inventory sits under so much else, getting its valuation and tracking right is a prerequisite for trustworthy margins, planning and warehouse operation. The full treatment of costing methods, tracking and valuation is in the inventory management deep-dive.

6. Warehouse management

Warehouse management is where inventory becomes physical. Business Central offers a spectrum of warehouse sophistication rather than one fixed model, and choosing the right point on that spectrum is one of the more important setup decisions. At the simple end, basic receiving and shipping post directly against orders. In the middle, bin-level tracking and inventory put-away and pick documents add structure without heavy process. At the advanced end, directed put-away and pick with zones, bin ranking, warehouse receipts and shipments, and full location-level warehouse activity give you a proper WMS-style operation.

The value of the advanced capabilities is real but so is their cost in discipline. Directed put-away and pick will tell an operator exactly which bin to place goods in and exactly which bin to pick from, optimising travel and enforcing accuracy, but only if the bin setup, zones and ranking reflect the actual physical warehouse. I have seen advanced warehousing switched on because it sounded thorough, then abandoned because nobody maintained the bin data it depends on. Match the warehouse configuration to the operation you actually run, not the one on the org chart.

The connection point here is between the paper-flow of orders and the physical movement of goods. Warehouse receipts and shipments decouple the document from the physical activity, so a single warehouse shipment can consolidate lines from several sales orders, and warehouse staff work from warehouse documents rather than order documents. For any operation past a certain size this separation is what keeps the floor and the office in sync. Zones, bins, put-away and pick strategies are all covered in the warehouse management deep-dive.

7. Manufacturing and assembly

Manufacturing and assembly are how Business Central turns components into finished goods, and the two sit at different levels of complexity for a reason. Assembly management is the lighter option: an assembly bill of materials plus optional resources, assembled to order or to stock, ideal for kitting and light configuration where you do not need routings or capacity. Full manufacturing adds production bills of materials, routings through work and machine centres, production orders, capacity planning and the shop-floor posting of consumption and output.

The manufacturing module connects the planning engine, inventory and costing into a working production system. A production order consumes components from inventory, records output at operations along a routing, and rolls the material and capacity cost into the finished item's value. Supply planning looks at production BOMs to explode demand down to component level, so a forecast or sales order for a finished product automatically drives the purchase of its raw materials. Standard costing with variance analysis lets you compare what production should have cost against what it actually did.

My practical guidance is to be honest about which tier you need. Many businesses that describe themselves as manufacturers are really assemblers, and assembly management gives them what they need with a fraction of the setup and running overhead of full production. Reaching for routings, capacity centres and production orders when assembly orders would do is a common way to make an implementation heavier than the business. The distinction between the two, and when to graduate from one to the other, is in the manufacturing and production deep-dive. Note that full manufacturing is a Premium capability, which brings us to licensing shortly.

8. Project management and jobs

Project management, still called jobs in much of the product and documentation, is Business Central's answer to any business that delivers work as billable engagements rather than shipping stock. A job carries a structure of tasks and planning lines, budgets planned cost and price, captures actuals as time, materials and expenses are posted against it, and supports billing either on a time-and-materials basis or against fixed-price milestones. Work in process and recognition let you account for the value of unbilled or partially delivered work correctly.

The strength of the jobs module is that it reuses the rest of the system rather than living apart from it. Resource time is posted against the job through timesheets or journals. Item consumption on a job draws from the same inventory. Purchases can be tied directly to a job so subcontract and material costs land where they belong. Every posting carries dimensions, so project profitability reports through the same account schedules as everything else. The result is that project cost and revenue reconcile to the general ledger without a separate system to keep in step.

For professional services, construction, installation and any project-based operation, this module is often the reason to choose Business Central over a purely product-focused ERP. The honest limitation is that it is solid project accounting rather than heavy project scheduling, so if you need complex Gantt-based resource levelling you will pair it with a dedicated tool. Where it excels is keeping the money side of projects accurate and connected. Budgets, WIP, and time-and-materials versus fixed-price billing are all covered in the project management and jobs deep-dive.

9. Service management

Service management supports businesses that maintain, repair or service equipment, whether their own installed base or their customers' assets. It tracks service items and the equipment record behind them, manages service contracts with their entitlements and periodic invoicing, handles service orders from fault to resolution, and coordinates the resource allocation that gets a technician to the job. Warranty tracking, fault and resolution coding, and service item history give you a maintenance record against each piece of equipment over its life.

This is the module closest to my own background in CMMS and CAFM, so I will be precise about its scope. Business Central service management is genuinely useful for the commercial side of service: contracts, entitlements, service orders, spare parts consumption from inventory, and billing that ties back cleanly to finance. What it is not is a full enterprise asset management or computerised maintenance management system. It does not aim to replace the deep reliability, condition-monitoring, preventive-maintenance-scheduling and work-management depth of a dedicated CMMS or EAM platform, and it should not be asked to.

The right way to think about it is as the commercial and financial layer of service that lives natively inside the ERP, often paired with a specialist maintenance system for the engineering depth. Where the two meet is exactly the kind of integration I do: keeping the asset, contract, parts and cost data consistent across the ERP and the maintenance platform so neither is guessing. Contracts, service orders, resource allocation and warranty are covered in the service management deep-dive.

10. Fixed assets

Fixed assets management handles the lifecycle of the capital equipment a business owns, from acquisition through depreciation to disposal, all posting into the same general ledger as everything else. Each asset carries one or more depreciation books, so you can run different depreciation for statutory, tax and internal reporting purposes in parallel without maintaining separate spreadsheets. The common depreciation methods are built in, including straight-line, declining balance and combinations, along with the ability to define custom methods where a jurisdiction demands it.

Beyond routine depreciation, the module handles the events that make asset accounting fiddly by hand. Acquisitions can flow straight from a purchase invoice, so buying an asset capitalises it in one step. Write-downs, appreciations, partial disposals, and gain or loss on sale are all posted through structured entries rather than manual journals. Maintenance costs and insurance can be recorded against assets. Asset reclassification and transfer between locations or dimensions keep the register aligned with where equipment actually sits. Physical asset registers and reporting round it out for audit.

For most businesses fixed assets is a quieter module that nonetheless removes a genuine pain, because manual depreciation across multiple books and jurisdictions is exactly the kind of repetitive, error-prone work that belongs in a system. The integration point worth noting is with purchasing, where capitalising an asset directly off a vendor invoice keeps the acquisition value and the payable perfectly in step. Depreciation books, disposals and posting integration are covered in the fixed assets deep-dive.

11. Cross-cutting foundations: dimensions, cost accounting, approval workflows, intercompany

Some of the most powerful parts of Business Central are not modules at all, they are foundations that run through every module. Understanding them changes how you use the whole system, and they are where an experienced implementer adds the most value, because they are easy to set up badly and hard to fix later.

Dimensions are the analysis tags attached to every transaction across finance, sales, purchasing, inventory, jobs and assets. They are how you report by department, project, region, cost centre or any axis you choose without bloating the chart of accounts, and they are the single most important design decision in an implementation. Get them right and reporting is effortless for years. The full framework is in the dimensions deep-dive.

Cost accounting sits alongside the general ledger to move and allocate costs between cost centres and cost objects for internal management reporting, letting you model overhead allocation and internal cost flows that the statutory ledger does not express. It is covered in the cost accounting deep-dive.

Approval workflows let you route documents, purchase orders, sales orders, journals, payments, through defined approval chains based on amount, budget or other conditions, enforcing control before posting rather than catching problems after. The patterns are in the approval workflows deep-dive.

Intercompany handles transactions between companies in the same group, so a sale from one entity to another posts as a matching purchase in the other, keeping intergroup trading consistent and easing consolidation. It is covered in the intercompany transactions deep-dive. Treat these four as the plumbing of the system: invisible when done well, painful when neglected.

12. Essentials versus Premium: what each licence tier unlocks

Business Central sells its core through two licence tiers, Essentials and Premium, and the difference is narrower and more specific than most people expect. Essentials is not a stripped-back trial edition. It includes financial management, sales and purchasing, inventory, project and jobs, fixed assets, the cross-cutting foundations, basic and advanced warehousing, and a great deal more. For the majority of businesses, distribution, professional services, and most trade and commercial operations, Essentials covers everything they need.

Premium adds exactly two functional areas on top of everything in Essentials: full manufacturing (production BOMs, routings, capacity planning, production orders and their costing) and service management (service contracts, service orders, service items and resource dispatch). If your business genuinely makes things through a production process, or services and maintains equipment as a core activity, you need Premium. If it does neither, Premium buys you capabilities you will not use.

The practitioner's rule: you license the whole organisation on one tier, not user by user for the two extra modules, so the tier decision comes down to a single question. Does the business need full manufacturing or service management? If yes, Premium for everyone who needs a full user. If no, Essentials and do not overpay for modules that will sit dark. Assembly management, worth repeating, is in Essentials, so light kitting and configuration do not force the upgrade.

There is also a Team Members licence for light users who only read data and perform limited actions, which sits under both tiers and is a genuine cost saver for occasional users. The mistake I see is buying Premium defensively "in case we need it later", when the tier can be changed later if the business genuinely moves into manufacturing or service. Buy for the operation you run now.

13. How the modules connect: the integration story

This is the section that ties the whole guide together, and it is the part I care about most, because connecting systems is what I do. Everything above is impressive on its own, but the reason Business Central is worth the move is that the modules are not merely adjacent, they are wired into each other through the shared ledger, the shared item and partner master data, the shared dimension model and the shared planning engine.

Trace a single flow and the connection becomes concrete. A sales order for a manufactured product creates demand. The planning engine explodes that demand through the production BOM into component requirements, sees what inventory holds, and suggests purchase orders for the shortfall. The purchase orders receive into inventory at landed cost. The production order consumes those components, records output through its routing, and rolls material and capacity cost into the finished item's value. The finished goods ship through a warehouse pick against the original sales order, post to the customer ledger, and land in the general ledger tagged with the same dimensions that let finance report the margin. One flow, one database, no integration code, every step reconciling to the next.

That internal connectedness is Business Central's core strength, and it is also why the interesting integration work sits at the boundary rather than in the middle. My own deepest experience is connecting Business Central to systems it does not natively cover: a CMMS or EAM platform for real asset maintenance depth, a CAFM system for facilities operations, e-commerce and point-of-sale front ends, payroll engines, and industry-specific applications. The API surface and the event-driven extension model make this genuinely workable, but the discipline is the same as anywhere in integration: agree the master data ownership, keep the item, partner and dimension records consistent across the boundary, and design the flows so neither system is guessing about the state of the other.

The lesson I would leave you with on integration is that the connections inside Business Central are the model to aspire to at the edges. Inside the product, finance never disagrees with inventory because they post from the same transaction. When you extend outward, your job is to reproduce that same single-source-of-truth discipline across the boundary, so the ERP and the specialist system stay as consistent as the modules already are with each other.

Final thoughts

The way to read Business Central is not as a catalogue of features to check off but as one connected system with specialised front ends. Finance is the core everything posts into. Sales and purchasing are mirror images of the same document flow. Inventory is the spine they share, warehousing makes it physical, manufacturing and assembly transform it, jobs bill it as work, service maintains it, and fixed assets account for what the business owns. Underneath all of it run the dimensions, cost accounting, approvals and intercompany foundations that make the whole thing report and control cleanly. Essentials covers most of that, and Premium adds full manufacturing and service for the businesses that need them.

Use this hub as a map. If one module is your reason for looking at Business Central, follow its link and go deep. If you are earlier in the journey, start with whether the platform fits your organisation at all. And when you get to the point of connecting Business Central to the other systems your operation depends on, that boundary is exactly where an experienced integration hand saves you from the mistakes that make a good ERP feel like an island. The modules were built to connect. The work is keeping them connected all the way out to the edge of your business.

Related reading: Financial management, Inventory management, Manufacturing and production, Service management, Dimensions, Is Business Central right for your organization, Cloud ERP explained.