📦
D365 Business Central
Cloud ERP for SMBs — financial management, supply chain, manufacturing, and project management in an integrated platform.
General LedgerDimensionsProcure-to-PayOrder-to-CashInventoryManufacturingApproval Workflows75 Questions
Questions 1–10 of 75
D365 Business Central is Microsoft's cloud ERP solution designed for small to medium-sized businesses (SMBs) — providing integrated financial management, supply chain, sales, and project management capabilities.
Core modules: Financial Management (GL, AP, AR, Bank Reconciliation, Fixed Assets), Sales Order Management, Purchase Order Management, Inventory Management, Warehouse Management, Manufacturing, Project Management, Service Management, HR (basic).
Target company profile: 10-500 employees, SMB and lower mid-market, growing out of QuickBooks/Sage/Xero/Navision. Revenue typically $5M-$500M.
Heritage: Business Central evolved from Microsoft Dynamics NAV (Navision). Many Business Central consultants have a NAV background — understanding this is important in upgrade project contexts.
Core modules: Financial Management (GL, AP, AR, Bank Reconciliation, Fixed Assets), Sales Order Management, Purchase Order Management, Inventory Management, Warehouse Management, Manufacturing, Project Management, Service Management, HR (basic).
Target company profile: 10-500 employees, SMB and lower mid-market, growing out of QuickBooks/Sage/Xero/Navision. Revenue typically $5M-$500M.
Heritage: Business Central evolved from Microsoft Dynamics NAV (Navision). Many Business Central consultants have a NAV background — understanding this is important in upgrade project contexts.
💡 Pro Tip: Business Central vs D365 Finance & Operations is a common interview question. BC is for SMBs at $70-$100/user/month. D365 F&O is for enterprise at $180+/user/month with multi-entity, multi-currency, and regulated industry needs.
Dimensions are custom analytical attributes that can be attached to any transaction in Business Central — enabling multi-dimensional financial analysis without multiplying G/L accounts.
Dimension examples: Department (Sales, Operations, Marketing, Finance), Project, Cost Centre, Region, Business Unit, Product Line.
How dimensions work: Define dimension (e.g., "Department") and dimension values (Sales, Finance, Marketing, Operations). Assign default dimensions to G/L accounts, customers, vendors, items. When a transaction posts, dimension values are inherited and recorded with the ledger entry.
Global dimensions: The two "Global Dimensions" (configured in G/L Setup) appear on every document and can be used as filters across all reports. Choose these carefully — typically Department and Region.
Dimension examples: Department (Sales, Operations, Marketing, Finance), Project, Cost Centre, Region, Business Unit, Product Line.
How dimensions work: Define dimension (e.g., "Department") and dimension values (Sales, Finance, Marketing, Operations). Assign default dimensions to G/L accounts, customers, vendors, items. When a transaction posts, dimension values are inherited and recorded with the ledger entry.
Global dimensions: The two "Global Dimensions" (configured in G/L Setup) appear on every document and can be used as filters across all reports. Choose these carefully — typically Department and Region.
💡 Pro Tip: Getting dimensions right at the start is critical. Wrong dimensions cannot be easily added retroactively. Run a dedicated "Dimensions Workshop" early in the project and sign off the dimension structure before any data migration. When clients say "we need separate P&Ls by department," the answer is almost always dimensions — not separate companies.
The Purchase-to-Pay process manages procurement from requisition to vendor payment:
1. Purchase Quote (optional): Request vendor quotes → compare → select vendor.
2. Purchase Order: Formal order to vendor specifying item, quantity, price, delivery date, and G/L account.
3. Goods Receipt (Posted Receipt): Vendor delivers → Post receipt in BC → Inventory increased → Accrual created in AP.
4. Invoice Matching (3-way match): Vendor sends invoice → Match against PO and receipt → Approve for payment.
5. Vendor Payment: Generate payment suggestion (suggest invoices due) → Review → Approve → Post payment → Bank balance updated.
Purchase pricing: Special prices and discounts per vendor-item combination. Line discounts, invoice discounts, payment discounts (2% if paid within 10 days).
1. Purchase Quote (optional): Request vendor quotes → compare → select vendor.
2. Purchase Order: Formal order to vendor specifying item, quantity, price, delivery date, and G/L account.
3. Goods Receipt (Posted Receipt): Vendor delivers → Post receipt in BC → Inventory increased → Accrual created in AP.
4. Invoice Matching (3-way match): Vendor sends invoice → Match against PO and receipt → Approve for payment.
5. Vendor Payment: Generate payment suggestion (suggest invoices due) → Review → Approve → Post payment → Bank balance updated.
Purchase pricing: Special prices and discounts per vendor-item combination. Line discounts, invoice discounts, payment discounts (2% if paid within 10 days).
💡 Pro Tip: The 3-way match is a critical control preventing overpaying vendors. In requirements, always ask: "What invoice tolerance do you accept? If the invoice is 5% more than the PO, do you auto-approve or flag for review?" This defines the matching tolerance configuration.
The Order-to-Cash process manages revenue from customer order to payment receipt:
1. Customer Quote (optional): Pricing presented to customer. Convert to order on acceptance.
2. Sales Order: Customer places order. Line items, prices, discounts, delivery date, ship-to address. Reserve inventory on order.
3. Sales Shipment: Post shipment → Inventory reduced, delivery note created.
4. Sales Invoice: Post invoice → AR debited, Revenue credited. Invoice sent to customer (email or print).
5. Cash Application: Customer payment received → Apply to open invoice → Clear AR balance.
Sales pricing: Customer-specific prices and discounts. Price groups (apply same pricing to a group of customers). Campaign pricing (time-limited promotional prices).
Credit management: Customer credit limit, credit check on order entry, override with approval.
1. Customer Quote (optional): Pricing presented to customer. Convert to order on acceptance.
2. Sales Order: Customer places order. Line items, prices, discounts, delivery date, ship-to address. Reserve inventory on order.
3. Sales Shipment: Post shipment → Inventory reduced, delivery note created.
4. Sales Invoice: Post invoice → AR debited, Revenue credited. Invoice sent to customer (email or print).
5. Cash Application: Customer payment received → Apply to open invoice → Clear AR balance.
Sales pricing: Customer-specific prices and discounts. Price groups (apply same pricing to a group of customers). Campaign pricing (time-limited promotional prices).
Credit management: Customer credit limit, credit check on order entry, override with approval.
💡 Pro Tip: Always ask about customer returns (credit memos) in requirements gathering. Returns are often more complex than sales — partial returns, restocking fees, return-to-different-location, and crediting the original invoice vs. applying credit to future orders.
Inventory Management in Business Central tracks physical goods through the supply chain — from purchase receipt to sale shipment.
Item types: Inventory item (physical good tracked in stock), Service item (non-physical — labour, subscription), Non-inventory item (expense items not tracked in stock).
Costing methods: FIFO, LIFO, Average cost, Standard cost, Specific cost (serial/lot tracked items). Costing method is set per item and affects inventory valuation and COGS.
Item tracking: Lot tracking (track items by lot for recall and expiry management). Serial number tracking (track individual units — electronics, medical devices).
Location management: Multiple warehouses (locations) supported. Inventory tracked per location. Transfer orders move stock between locations.
Item types: Inventory item (physical good tracked in stock), Service item (non-physical — labour, subscription), Non-inventory item (expense items not tracked in stock).
Costing methods: FIFO, LIFO, Average cost, Standard cost, Specific cost (serial/lot tracked items). Costing method is set per item and affects inventory valuation and COGS.
Item tracking: Lot tracking (track items by lot for recall and expiry management). Serial number tracking (track individual units — electronics, medical devices).
Location management: Multiple warehouses (locations) supported. Inventory tracked per location. Transfer orders move stock between locations.
💡 Pro Tip: Costing method selection is one of the most consequential configuration decisions in Business Central — it cannot be easily changed post-go-live. Spend time on this with the client's finance team. "Average cost" is common for distribution; "Standard cost" for manufacturing; "FIFO" for food/pharma.
Financial management is the core of Business Central — every other module feeds financial transactions into the General Ledger.
Chart of Accounts (CoA): Configurable G/L account structure. Dimensions add analytical depth without multiplying accounts.
Journals: General Journal (manual entries), Purchase/Sales Journals (integration postings), Payment/Cash Receipts Journals (bank entries).
Accounts Payable (AP): Purchase invoices, credit memos, vendor payments, payment journals, payment suggestions.
Accounts Receivable (AR): Sales invoices, credit memos, customer payments, cash application, aged receivables report, reminders and finance charges.
Bank Reconciliation: Import bank statements (CSV or direct bank feed). Auto-match transactions. Reconcile balance to book.
Chart of Accounts (CoA): Configurable G/L account structure. Dimensions add analytical depth without multiplying accounts.
Journals: General Journal (manual entries), Purchase/Sales Journals (integration postings), Payment/Cash Receipts Journals (bank entries).
Accounts Payable (AP): Purchase invoices, credit memos, vendor payments, payment journals, payment suggestions.
Accounts Receivable (AR): Sales invoices, credit memos, customer payments, cash application, aged receivables report, reminders and finance charges.
Bank Reconciliation: Import bank statements (CSV or direct bank feed). Auto-match transactions. Reconcile balance to book.
💡 Pro Tip: Bank reconciliation is the first "acid test" of a go-live. If bank reconciliation works correctly in week 1, the financial configuration is almost certainly correct. Make it the first complete test in UAT and the first task in Week 1 post go-live.
Approval Workflows automate the review and approval of documents (purchase orders, sales orders, payment journals) before they can be posted — enforcing segregation of duties.
Standard workflows: Purchase Order Approval, Purchase Invoice Approval, Payment Journal Approval, Sales Order Approval, Customer Credit Limit Approval.
Workflow configuration:
1. Define approver hierarchy (user → manager → department head).
2. Set approval conditions (PO > $10,000 requires manager approval; > $50,000 requires director).
3. Configure notification method (email, workflow notification in Business Central).
4. Set escalation rules (auto-escalate if not approved within 2 business days).
5. Activate workflow.
Delegation: Approvers can delegate to a substitute during absence — critical for holiday periods.
Standard workflows: Purchase Order Approval, Purchase Invoice Approval, Payment Journal Approval, Sales Order Approval, Customer Credit Limit Approval.
Workflow configuration:
1. Define approver hierarchy (user → manager → department head).
2. Set approval conditions (PO > $10,000 requires manager approval; > $50,000 requires director).
3. Configure notification method (email, workflow notification in Business Central).
4. Set escalation rules (auto-escalate if not approved within 2 business days).
5. Activate workflow.
Delegation: Approvers can delegate to a substitute during absence — critical for holiday periods.
💡 Pro Tip: Segregation of duties requirements (who can create vs. approve vs. post) typically drive approval workflow requirements. Always map the approval matrix (Role x Document Type x Threshold → Required Approver) in a dedicated workshop before configuring.
Manufacturing in Business Central (Premium licence) supports discrete production — managing BOMs, routings, production orders, and shop floor execution.
Manufacturing components:
Item BOM (Bill of Materials): Components required to produce a finished good. Multi-level BOM supported. BOM versions for change management.
Routing: Production operations sequence. Work centres, machine centres, setup time, run time per operation.
Production Order: Work order to manufacture a quantity of a finished good. Types: Simulated → Planned → Firm Planned → Released → Finished.
MRP: Planning worksheet generates purchase/production orders based on demand and reorder rules.
Consumption and output journals: Record actual materials consumed and finished goods produced.
Manufacturing components:
Item BOM (Bill of Materials): Components required to produce a finished good. Multi-level BOM supported. BOM versions for change management.
Routing: Production operations sequence. Work centres, machine centres, setup time, run time per operation.
Production Order: Work order to manufacture a quantity of a finished good. Types: Simulated → Planned → Firm Planned → Released → Finished.
MRP: Planning worksheet generates purchase/production orders based on demand and reorder rules.
Consumption and output journals: Record actual materials consumed and finished goods produced.
💡 Pro Tip: Business Central Premium licence is required for manufacturing. Essentials licence excludes it. Always confirm licence type before designing manufacturing requirements — and confirm whether they need process manufacturing (chemicals, food) or discrete (assemblies, finished goods).
Business Central integrates deeply with Microsoft 365 — creating a unified work environment:
Outlook integration: Business Central app for Outlook — view BC customer data (balance, open invoices, recent orders) while reading emails. Create quotes, orders, and contacts directly from Outlook. Send invoices from Business Central via Outlook email.
Excel integration: Export any Business Central list to Excel (live data). Edit data in Excel and publish back to Business Central (for bulk updates).
Teams integration: Share Business Central records (customer, invoice, order) in Teams chats. View record details in Teams without switching apps.
OneDrive/SharePoint: Attach documents from OneDrive to Business Central records. Automatically store BC documents (invoices, statements) in SharePoint.
Power BI: Business Central ships with a Power BI content pack. Embed Power BI reports in Business Central pages.
Outlook integration: Business Central app for Outlook — view BC customer data (balance, open invoices, recent orders) while reading emails. Create quotes, orders, and contacts directly from Outlook. Send invoices from Business Central via Outlook email.
Excel integration: Export any Business Central list to Excel (live data). Edit data in Excel and publish back to Business Central (for bulk updates).
Teams integration: Share Business Central records (customer, invoice, order) in Teams chats. View record details in Teams without switching apps.
OneDrive/SharePoint: Attach documents from OneDrive to Business Central records. Automatically store BC documents (invoices, statements) in SharePoint.
Power BI: Business Central ships with a Power BI content pack. Embed Power BI reports in Business Central pages.
💡 Pro Tip: The Microsoft 365 integration is a major selling point vs. other SMB ERPs (SAP B1, Oracle NetSuite). In demos, always show the Outlook and Teams integration — these resonate immediately with SMB decision-makers who spend their day in email and chat.
Microsoft AppSource is the marketplace for Business Central extensions — pre-built functionality that extends Business Central for specific industries or use cases.
Common Business Central extensions: Continia Document Capture (OCR invoice processing), Jet Reports (advanced financial reporting), Zetadocs (document management), Anveo Mobile App (warehouse mobile scanning), Industry-specific apps (Construction, Automotive Dealership, Rental, Food & Beverage).
Extension architecture: Business Central extensions are built using AL language. Extensions do NOT modify the base application — they extend it. This means Microsoft updates do not break extensions, unlike NAV customisations.
Upgrade benefit: Business Central online (SaaS) updates automatically (2 major updates per year). Because extensions do not touch base code, updates are largely transparent.
Common Business Central extensions: Continia Document Capture (OCR invoice processing), Jet Reports (advanced financial reporting), Zetadocs (document management), Anveo Mobile App (warehouse mobile scanning), Industry-specific apps (Construction, Automotive Dealership, Rental, Food & Beverage).
Extension architecture: Business Central extensions are built using AL language. Extensions do NOT modify the base application — they extend it. This means Microsoft updates do not break extensions, unlike NAV customisations.
Upgrade benefit: Business Central online (SaaS) updates automatically (2 major updates per year). Because extensions do not touch base code, updates are largely transparent.
💡 Pro Tip: When clients ask for functionality not in Business Central out-of-the-box, your first response should be "Let me check AppSource." A certified AppSource extension is faster to implement, better supported, and typically lower total cost than custom development.
Questions 11–20 of 75
| Aspect | Business Central Online (SaaS) | Business Central On-Premise |
|---|---|---|
| Hosting | Microsoft Azure cloud | Client's own servers |
| Updates | Automatic (2/year major) | Manual; client controls timing |
| Licensing | Monthly subscription per user | Perpetual + annual enhancement |
| Customisation | Extensions only (no base code change) | Base code modifications possible |
| Microsoft direction | Primary investment | Supported but not strategic |
💡 Pro Tip: The standard recommendation is online unless there are compelling reasons (data residency regulations, no reliable internet, very heavy customisations that cannot move to extensions). Document the decision rationale in the BRD — this is often challenged by clients who want on-premise for legacy reasons.
Posting Groups are Business Central's mechanism for automatically determining which G/L accounts to debit and credit when posting transactions — the core of the financial configuration.
Types of posting groups:
General Posting Groups: Gen. Bus. Posting Group (on customer/vendor) x Gen. Prod. Posting Group (on item/G/L account) = which Sales Revenue, COGS, and Purchase accounts to use.
Customer Posting Groups: Determine which AR account and sales discount accounts to use per customer type.
Vendor Posting Groups: Determine which AP account and purchase discount accounts to use per vendor type.
Inventory Posting Groups: Determine which inventory account and adjustment accounts to use per item type.
VAT/GST Posting Groups: Determine which VAT accounts and rates to use.
Types of posting groups:
General Posting Groups: Gen. Bus. Posting Group (on customer/vendor) x Gen. Prod. Posting Group (on item/G/L account) = which Sales Revenue, COGS, and Purchase accounts to use.
Customer Posting Groups: Determine which AR account and sales discount accounts to use per customer type.
Vendor Posting Groups: Determine which AP account and purchase discount accounts to use per vendor type.
Inventory Posting Groups: Determine which inventory account and adjustment accounts to use per item type.
VAT/GST Posting Groups: Determine which VAT accounts and rates to use.
⚠ Key Point: Posting group configuration is the most technically complex part of Business Central financial setup. Every posting combination must be defined before any transactions can be posted. Missing a posting group combination causes runtime errors at transaction time — not during setup.
G/L Budgets allow comparison of actual financial performance against planned budgets — a standard financial management requirement.
Budget configuration: Budget name and description, fiscal periods covered (quarterly or annual), budget entries per G/L account and dimension combination (e.g., Marketing Department, Q1 2025, G/L Account 6100 = €50,000).
Budget entry methods: Manual entry per account/period in the budget grid. Export to Excel → fill in → import back. Copy from previous year budget with percentage adjustment. Copy from actuals (start with last year's actuals, adjust for this year).
Budget vs Actual reporting: Account Schedules (Financial Reports) compare actual ledger entries against budget entries. Variance = Actual - Budget. % Variance = Variance / Budget.
Budget configuration: Budget name and description, fiscal periods covered (quarterly or annual), budget entries per G/L account and dimension combination (e.g., Marketing Department, Q1 2025, G/L Account 6100 = €50,000).
Budget entry methods: Manual entry per account/period in the budget grid. Export to Excel → fill in → import back. Copy from previous year budget with percentage adjustment. Copy from actuals (start with last year's actuals, adjust for this year).
Budget vs Actual reporting: Account Schedules (Financial Reports) compare actual ledger entries against budget entries. Variance = Actual - Budget. % Variance = Variance / Budget.
💡 Pro Tip: Budget entry in Business Central's grid is time-consuming. Recommend the Excel-to-Budget import workflow: finance team enters budgets in familiar Excel, imports to Business Central in minutes. This approach significantly reduces budget entry time and improves adoption.
Fixed Assets (FA) in Business Central manages acquisition, depreciation, disposal, and reporting of long-term assets — tangible (machinery, vehicles, buildings) and intangible (patents, software).
FA lifecycle:
1. FA Card created (description, FA class, location, acquisition date).
2. FA Journal: Post acquisition cost → Asset capitalised.
3. Depreciation Books configured: Depreciation method, useful life, salvage value.
4. Monthly depreciation run: Calculate and post depreciation journal.
5. Disposal: Post sale or write-off → Remove from books, post gain/loss to P&L.
Depreciation methods supported: Straight-Line (most common), Declining-Balance (DB1, DB2), Sum of Digits, Units of Production, Manual.
Multiple depreciation books: One for financial reporting (IFRS/GAAP), one for tax purposes. Each can have different methods and lives.
FA lifecycle:
1. FA Card created (description, FA class, location, acquisition date).
2. FA Journal: Post acquisition cost → Asset capitalised.
3. Depreciation Books configured: Depreciation method, useful life, salvage value.
4. Monthly depreciation run: Calculate and post depreciation journal.
5. Disposal: Post sale or write-off → Remove from books, post gain/loss to P&L.
Depreciation methods supported: Straight-Line (most common), Declining-Balance (DB1, DB2), Sum of Digits, Units of Production, Manual.
Multiple depreciation books: One for financial reporting (IFRS/GAAP), one for tax purposes. Each can have different methods and lives.
💡 Pro Tip: Multi-book depreciation (one book for financial reporting, one for tax) is a standard requirement for medium-to-large Business Central clients. Design this in the requirements phase — adding it later requires retroactive depreciation recalculation.
Business Central exposes a comprehensive REST API enabling integration with external systems — from eCommerce to payroll to logistics.
API types: Standard API (v2.0) — pre-built endpoints for common entities (customers, vendors, items, invoices, journal entries). Stable and Microsoft-maintained. OData API (v4) — query any Business Central page exposed as a web service. Custom API pages — AL-developed custom endpoints for entities not covered by standard API.
Common integration use cases: eCommerce integration (Shopify, WooCommerce) — Microsoft provides native Shopify connector. Payroll integration. Logistics/3PL — send shipment confirmations from warehouse to Business Central. Bank integration — auto-import bank statements.
Power Automate connector: Business Central has a native Power Automate connector — 200+ triggers and actions. Most mid-complexity integrations can be built without custom code.
API types: Standard API (v2.0) — pre-built endpoints for common entities (customers, vendors, items, invoices, journal entries). Stable and Microsoft-maintained. OData API (v4) — query any Business Central page exposed as a web service. Custom API pages — AL-developed custom endpoints for entities not covered by standard API.
Common integration use cases: eCommerce integration (Shopify, WooCommerce) — Microsoft provides native Shopify connector. Payroll integration. Logistics/3PL — send shipment confirmations from warehouse to Business Central. Bank integration — auto-import bank statements.
Power Automate connector: Business Central has a native Power Automate connector — 200+ triggers and actions. Most mid-complexity integrations can be built without custom code.
💡 Pro Tip: Document integration requirements as: Source system | Target system | Data entity | Trigger | Transformation | Frequency. This Integration Requirements Document is a standard deliverable that developers and architects use to build integration solutions.
Service Management in Business Central (Premium) manages post-sales service and repair workflows — for businesses that service products they sell or products owned by clients.
Service management components: Service contracts (recurring service agreements — annual maintenance contracts). Service items (specific product units under service, serial number tracked, service history). Service orders (individual service requests — repair, maintenance visit, inspection). Loaner management (track loan items given to customers while their product is being repaired).
Service lifecycle: Service call received → Service order created → Resource (technician) assigned → Work performed → Parts consumed → Service posted → Invoice generated.
When to use Business Central Service vs D365 Field Service: BC Service: product-centric service (repair shop, warranty). D365 Field Service: field dispatch, IoT connected service, scheduling optimisation across many technicians.
Service management components: Service contracts (recurring service agreements — annual maintenance contracts). Service items (specific product units under service, serial number tracked, service history). Service orders (individual service requests — repair, maintenance visit, inspection). Loaner management (track loan items given to customers while their product is being repaired).
Service lifecycle: Service call received → Service order created → Resource (technician) assigned → Work performed → Parts consumed → Service posted → Invoice generated.
When to use Business Central Service vs D365 Field Service: BC Service: product-centric service (repair shop, warranty). D365 Field Service: field dispatch, IoT connected service, scheduling optimisation across many technicians.
💡 Pro Tip: Service Management is one of the most underimplemented Business Central modules. Many clients have it on their licence but use manual processes for service management. Identifying this gap in requirements is a consulting value-add that often leads to additional project scope.
Migrating from Microsoft Dynamics NAV to Business Central Online is one of the most common project types for BC consultants. Key challenges:
Customisation challenge: NAV customisations (C/AL code directly modifying base tables) cannot be moved to Business Central Online as-is. All customisations must be rebuilt as AL extensions — often the most expensive part of the migration.
Data migration: NAV data structures differ slightly from Business Central. Standard migration tools: Cloud Migration App (moves data directly from NAV to BC Online), RapidStart configuration packages. Data must be cleansed before migration.
Process redesign: Some NAV processes used workarounds for missing features. Business Central may have native functionality. Requirements must distinguish "must replicate old process" from "take the opportunity to improve the process."
Customisation challenge: NAV customisations (C/AL code directly modifying base tables) cannot be moved to Business Central Online as-is. All customisations must be rebuilt as AL extensions — often the most expensive part of the migration.
Data migration: NAV data structures differ slightly from Business Central. Standard migration tools: Cloud Migration App (moves data directly from NAV to BC Online), RapidStart configuration packages. Data must be cleansed before migration.
Process redesign: Some NAV processes used workarounds for missing features. Business Central may have native functionality. Requirements must distinguish "must replicate old process" from "take the opportunity to improve the process."
⚠ Key Point: The customisation assessment is the most critical deliverable in a NAV-to-BC migration scoping. Every custom object must be categorised: Rebuild in AL (must have), Replace with AppSource extension (equivalent functionality), or Retire (no longer needed). This assessment determines the project cost and timeline.
Business Central integrates natively with the Microsoft Power Platform — enabling business users to extend and automate Business Central without custom code:
Power Automate: 200+ Business Central connectors. Common flows: Invoice approval, auto-email overdue payment reminders, sync BC data to SharePoint lists, trigger notification to Teams when order value exceeds threshold.
Power Apps: Build custom mobile or browser apps that read/write Business Central data. Examples: Expense capture app for field staff, custom approval app for mobile approvers.
Power BI: Native BC Power BI app with pre-built dashboards — Finance (revenue, expenses, cash position), Sales (order pipeline, top customers), Purchasing (PO volume, vendor spend).
Copilot in Business Central: AI-generated bank reconciliation suggestions, AI-generated product descriptions, natural language query, AI-assisted cash flow forecast.
Power Automate: 200+ Business Central connectors. Common flows: Invoice approval, auto-email overdue payment reminders, sync BC data to SharePoint lists, trigger notification to Teams when order value exceeds threshold.
Power Apps: Build custom mobile or browser apps that read/write Business Central data. Examples: Expense capture app for field staff, custom approval app for mobile approvers.
Power BI: Native BC Power BI app with pre-built dashboards — Finance (revenue, expenses, cash position), Sales (order pipeline, top customers), Purchasing (PO volume, vendor spend).
Copilot in Business Central: AI-generated bank reconciliation suggestions, AI-generated product descriptions, natural language query, AI-assisted cash flow forecast.
💡 Pro Tip: When clients ask for custom apps or automation, check Power Platform first before recommending custom AL development. Power Automate can often solve integration requirements in days rather than weeks — dramatically reducing implementation cost.
Business Central includes a Jobs module (also called Projects) for tracking project-based work — managing costs, revenue, and profitability per project.
BC Jobs components: Job card (project definition — customer, status, billing type, responsible person). Job Task Lines (WBS equivalent — phases and tasks). Job Planning Lines (estimated resources, items, and G/L costs per task). Job Journal (record actual time, items consumed, expenses). Job ledger entries (all actuals posted to the job).
Billing: Invoice for T&M (create invoices from billable job planning lines). Fixed price (invoice milestone amounts regardless of actual work).
When to use BC Jobs vs D365 Project Operations: BC Jobs: SMB professional services, internal project tracking, simpler T&M billing. D365 Project Operations: Enterprise professional services, complex resource management, revenue recognition, multi-entity.
BC Jobs components: Job card (project definition — customer, status, billing type, responsible person). Job Task Lines (WBS equivalent — phases and tasks). Job Planning Lines (estimated resources, items, and G/L costs per task). Job Journal (record actual time, items consumed, expenses). Job ledger entries (all actuals posted to the job).
Billing: Invoice for T&M (create invoices from billable job planning lines). Fixed price (invoice milestone amounts regardless of actual work).
When to use BC Jobs vs D365 Project Operations: BC Jobs: SMB professional services, internal project tracking, simpler T&M billing. D365 Project Operations: Enterprise professional services, complex resource management, revenue recognition, multi-entity.
💡 Pro Tip: Business Central Jobs is often the right choice for SMBs moving off spreadsheets for project tracking. It provides the basics of time tracking, billing, and P&L per project without the complexity and cost of D365 Project Operations.
Understanding common failure causes helps consultants proactively mitigate risks:
1. Data migration underestimated: Poor source data quality (duplicate customers, missing vendor bank details) causes go-live delays. Mitigation: Data quality assessment in week 1; migration validation testing 4 weeks before go-live.
2. Chart of Accounts and dimensions not designed properly: Insufficient G/L accounts or wrong dimension structure means financial reports do not meet requirements. These are expensive to fix post-go-live. Mitigation: Dedicated financial configuration workshop with CFO and accountant.
3. Insufficient user training: Power users trained but not general users. Mitigation: Train all users 2 weeks before go-live; record videos for reference.
4. Missing integrations discovered late: "We also need to connect to our payroll system" discovered in UAT. Mitigation: Integration discovery workshop in week 1.
1. Data migration underestimated: Poor source data quality (duplicate customers, missing vendor bank details) causes go-live delays. Mitigation: Data quality assessment in week 1; migration validation testing 4 weeks before go-live.
2. Chart of Accounts and dimensions not designed properly: Insufficient G/L accounts or wrong dimension structure means financial reports do not meet requirements. These are expensive to fix post-go-live. Mitigation: Dedicated financial configuration workshop with CFO and accountant.
3. Insufficient user training: Power users trained but not general users. Mitigation: Train all users 2 weeks before go-live; record videos for reference.
4. Missing integrations discovered late: "We also need to connect to our payroll system" discovered in UAT. Mitigation: Integration discovery workshop in week 1.
💡 Pro Tip: Standard SMB implementation (50-100 users, 2-3 modules): 8-16 weeks minimum. Be honest with clients about timeline — it is better to push back in week 1 than to fail in week 20. The go-live date is the single most important expectation to set correctly.
Questions 21–30 of 75
The Chart of Accounts (CoA) is the backbone of all financial reporting in Business Central — a structured list of G/L accounts that every financial transaction posts to.
CoA structure in Business Central: Each account has: Account No. (unique identifier — typically numeric, e.g., 1000-9999), Name (descriptive label), Account Type (Posting = can receive transactions, Heading = display only, Total = formula-based subtotal, Begin/End Total = range for summing), Account Category (Assets, Liabilities, Equity, Income, Cost of Goods Sold, Expense), Normal Balance (Debit or Credit), Income/Balance Sheet indicator.
Account numbering conventions: Assets: 1000-1999. Liabilities: 2000-2999. Equity: 3000-3999. Revenue: 4000-4999. Cost of Sales: 5000-5999. Operating Expenses: 6000-7999. Other Income/Expense: 8000-8999.
Totalling accounts: Business Central uses Begin-Total and End-Total account types with a "Totaling" formula field — allowing flexible subtotal structures without requiring a rigid hierarchy. E.g., Account 6990 "Total Operating Expenses" totals all accounts 6000..6989.
CoA structure in Business Central: Each account has: Account No. (unique identifier — typically numeric, e.g., 1000-9999), Name (descriptive label), Account Type (Posting = can receive transactions, Heading = display only, Total = formula-based subtotal, Begin/End Total = range for summing), Account Category (Assets, Liabilities, Equity, Income, Cost of Goods Sold, Expense), Normal Balance (Debit or Credit), Income/Balance Sheet indicator.
Account numbering conventions: Assets: 1000-1999. Liabilities: 2000-2999. Equity: 3000-3999. Revenue: 4000-4999. Cost of Sales: 5000-5999. Operating Expenses: 6000-7999. Other Income/Expense: 8000-8999.
Totalling accounts: Business Central uses Begin-Total and End-Total account types with a "Totaling" formula field — allowing flexible subtotal structures without requiring a rigid hierarchy. E.g., Account 6990 "Total Operating Expenses" totals all accounts 6000..6989.
💡 Pro Tip: The CoA structure is the most consequential early design decision in a Business Central implementation — it determines the structure of the P&L and Balance Sheet forever. Changing the CoA after go-live requires remapping all historical transactions. Always design the CoA with both the accountant (who needs technical correctness) and the management team (who need business-meaningful reporting categories) in the same room.
Posting Groups are Business Central's mechanism for automatically determining which G/L accounts to debit and credit when transactions are posted — the core of the automatic accounting engine.
General Posting Groups (the most important): Gen. Business Posting Group: Assigned to customers, vendors — represents the business type (Domestic, EU, Export, Intercompany). Gen. Product Posting Group: Assigned to items, G/L accounts — represents the product type (Raw Material, Finished Goods, Service, Resale). The intersection of these two groups in the General Posting Setup defines the specific revenue, COGS, purchase, and direct cost accounts.
Specific Posting Groups: Customer Posting Group: Determines the Accounts Receivable G/L account, payment discount accounts. Vendor Posting Group: Determines the Accounts Payable G/L account. Inventory Posting Group: Determines the Inventory asset account and adjustment accounts. VAT/Tax Posting Groups: Determine VAT liability accounts and rates.
How they work together: When posting a sales invoice: Customer Posting Group provides the AR account. Gen. Bus. + Gen. Prod. Posting Groups provide the Revenue account. VAT Bus. + VAT Prod. Posting Groups provide the VAT account. All determined automatically — no manual G/L selection by the user.
General Posting Groups (the most important): Gen. Business Posting Group: Assigned to customers, vendors — represents the business type (Domestic, EU, Export, Intercompany). Gen. Product Posting Group: Assigned to items, G/L accounts — represents the product type (Raw Material, Finished Goods, Service, Resale). The intersection of these two groups in the General Posting Setup defines the specific revenue, COGS, purchase, and direct cost accounts.
Specific Posting Groups: Customer Posting Group: Determines the Accounts Receivable G/L account, payment discount accounts. Vendor Posting Group: Determines the Accounts Payable G/L account. Inventory Posting Group: Determines the Inventory asset account and adjustment accounts. VAT/Tax Posting Groups: Determine VAT liability accounts and rates.
How they work together: When posting a sales invoice: Customer Posting Group provides the AR account. Gen. Bus. + Gen. Prod. Posting Groups provide the Revenue account. VAT Bus. + VAT Prod. Posting Groups provide the VAT account. All determined automatically — no manual G/L selection by the user.
⚠ Key Point: Every combination of Gen. Business + Gen. Product Posting Groups that will ever be used must have a configured General Posting Setup row before any transaction is posted. Missing a combination causes a "posting group not found" error at posting time — discovered painfully by users, not in testing. Always generate a matrix of all combinations and configure them all upfront.
VAT/GST configuration in Business Central determines which tax rate applies to each transaction and which G/L accounts are used for tax accounting — a legally critical configuration that must be correct from day 1.
VAT Posting Setup components: VAT Business Posting Group: Assigned to customers and vendors — represents the customer's VAT status (Domestic, EU, Export, Non-taxable). VAT Product Posting Group: Assigned to items and G/L accounts — represents the product's VAT classification (Standard Rate, Reduced Rate, Zero Rate, Exempt). VAT Posting Setup: Matrix of VAT Bus. + VAT Prod. groups — defines: VAT %, VAT Calculation Type (Normal VAT, Reverse Charge, Full VAT), VAT Account (G/L account for output VAT liability), Purchase VAT Account (G/L account for input VAT recovery).
For India GST specifically: Business Central has a GST India localisation. Configure CGST, SGST, IGST, CESS rates. GST Registration Number required on customer/vendor cards. HSN/SAC codes on items. E-Invoice generation (for turnover above threshold). GSTR reports (GSTR-1, GSTR-3B) generated from Business Central.
VAT Posting Setup components: VAT Business Posting Group: Assigned to customers and vendors — represents the customer's VAT status (Domestic, EU, Export, Non-taxable). VAT Product Posting Group: Assigned to items and G/L accounts — represents the product's VAT classification (Standard Rate, Reduced Rate, Zero Rate, Exempt). VAT Posting Setup: Matrix of VAT Bus. + VAT Prod. groups — defines: VAT %, VAT Calculation Type (Normal VAT, Reverse Charge, Full VAT), VAT Account (G/L account for output VAT liability), Purchase VAT Account (G/L account for input VAT recovery).
For India GST specifically: Business Central has a GST India localisation. Configure CGST, SGST, IGST, CESS rates. GST Registration Number required on customer/vendor cards. HSN/SAC codes on items. E-Invoice generation (for turnover above threshold). GSTR reports (GSTR-1, GSTR-3B) generated from Business Central.
💡 Pro Tip: Always involve the client's tax advisor or CA in VAT/GST configuration. Tax rates, exemptions, and reverse charge rules are legally prescribed and change with budget announcements. Never configure tax solely based on your own interpretation — get written sign-off from the client's tax team on the VAT/GST Posting Setup configuration before go-live.
Bank Reconciliation in Business Central matches bank statement transactions with the company's book entries — confirming that the bank balance and the G/L balance agree at the end of each period.
Bank reconciliation process:
1. Import bank statement: File import (CSV, MT940, BAI2 format) or direct bank feed connection (via Yodlee or bank-specific connector). Statement lines appear in the Bank Reconciliation form.
2. Auto-matching: Business Central automatically matches statement lines to G/L and payment journal entries based on amount, date, and document number. Typical auto-match rate: 60-85% of transactions.
3. Manual matching: Remaining unmatched lines are matched manually. Match a statement line to: an existing G/L entry, an existing customer payment, a new journal entry (for bank charges, interest).
4. Reconcile: When all statement lines are matched and the difference = 0, post the reconciliation. The bank account G/L balance is confirmed to equal the statement balance.
Copilot assistance: Business Central now includes AI-powered bank reconciliation suggestions — Copilot proposes matches for ambiguous transactions, reducing manual matching time by 30-50%.
Bank reconciliation process:
1. Import bank statement: File import (CSV, MT940, BAI2 format) or direct bank feed connection (via Yodlee or bank-specific connector). Statement lines appear in the Bank Reconciliation form.
2. Auto-matching: Business Central automatically matches statement lines to G/L and payment journal entries based on amount, date, and document number. Typical auto-match rate: 60-85% of transactions.
3. Manual matching: Remaining unmatched lines are matched manually. Match a statement line to: an existing G/L entry, an existing customer payment, a new journal entry (for bank charges, interest).
4. Reconcile: When all statement lines are matched and the difference = 0, post the reconciliation. The bank account G/L balance is confirmed to equal the statement balance.
Copilot assistance: Business Central now includes AI-powered bank reconciliation suggestions — Copilot proposes matches for ambiguous transactions, reducing manual matching time by 30-50%.
💡 Pro Tip: Bank reconciliation is the acid test of financial configuration accuracy. If bank reconciliation cannot be completed cleanly in week 1, there is almost certainly a posting group, journal template, or beginning balance configuration issue. Make bank reconciliation the first complete test in UAT — and the first task in week 1 of production. Problems discovered here are faster and cheaper to fix than problems discovered at month-end.
Number Series in Business Central control how documents, records, and transactions are numbered — ensuring sequential, auditable numbering across all business documents.
What uses Number Series: Sales Invoices (SI-00001, SI-00002...), Purchase Orders (PO-2024-001...), Customers (CUST-001...), Vendors (VEND-001...), Items (ITEM-001...), General Journal Batches, Payment References, Bank Account Statements.
Number Series configuration: Administration → Application Setup → Number Series → New. Fields: Code (short identifier, e.g., SI), Description, Starting No., Ending No. (optional cap), Last No. Used (auto-updated), Increment-by No. (default 1), Allow Gaps (allows non-sequential numbering — useful for EDI), Manual Nos. (allow users to enter their own numbers), Default Nos. (auto-assign without user prompt).
Assigning Number Series to documents: Sales & Receivables Setup: Customer Nos., Invoice Nos., Order Nos. Purchases & Payables Setup: Vendor Nos., Order Nos., Invoice Nos. General Ledger Setup: Journal Batch Nos.
What uses Number Series: Sales Invoices (SI-00001, SI-00002...), Purchase Orders (PO-2024-001...), Customers (CUST-001...), Vendors (VEND-001...), Items (ITEM-001...), General Journal Batches, Payment References, Bank Account Statements.
Number Series configuration: Administration → Application Setup → Number Series → New. Fields: Code (short identifier, e.g., SI), Description, Starting No., Ending No. (optional cap), Last No. Used (auto-updated), Increment-by No. (default 1), Allow Gaps (allows non-sequential numbering — useful for EDI), Manual Nos. (allow users to enter their own numbers), Default Nos. (auto-assign without user prompt).
Assigning Number Series to documents: Sales & Receivables Setup: Customer Nos., Invoice Nos., Order Nos. Purchases & Payables Setup: Vendor Nos., Order Nos., Invoice Nos. General Ledger Setup: Journal Batch Nos.
💡 Pro Tip: Design number series formats in requirements to match the client's existing document numbering conventions — especially if they have a long paper-based or legacy system history. Accountants and auditors who are used to seeing "INV-2024-001" will resist a system that uses "SI00001". Also confirm if the client needs year-based numbering that resets annually — this requires a new Number Series each year or a date-embedded format.
Financial Reports (formerly called Account Schedules) in Business Central are the purpose-built financial statement builder — creating P&L, Balance Sheet, Cash Flow, and management reports from G/L data.
Financial Report structure: Row Definition: Defines the rows of the report — which G/L accounts (or account totals or formulas) appear on each row. E.g., Row 10: Revenue G/L accounts 4000..4999. Row 20: Cost of Sales 5000..5999. Row 30: Gross Profit (formula: Row 10 - Row 20). Column Definition: Defines the columns — Net Change This Period, Budget, Variance (Actual - Budget), Prior Year, YTD. Each column can show a specific period, a comparison period, or a formula.
Analysis Views: Enhance Financial Reports by filtering/pivoting by Dimension values. Run the P&L filtered to one Department dimension value — showing one department's P&L without creating separate reports per department.
Standard Financial Reports in Business Central: Income Statement, Balance Sheet, Cash Flow Statement, Trial Balance, Budget Comparison. Each is a pre-built Financial Report that can be customised to match the client's preferred layout.
Financial Report structure: Row Definition: Defines the rows of the report — which G/L accounts (or account totals or formulas) appear on each row. E.g., Row 10: Revenue G/L accounts 4000..4999. Row 20: Cost of Sales 5000..5999. Row 30: Gross Profit (formula: Row 10 - Row 20). Column Definition: Defines the columns — Net Change This Period, Budget, Variance (Actual - Budget), Prior Year, YTD. Each column can show a specific period, a comparison period, or a formula.
Analysis Views: Enhance Financial Reports by filtering/pivoting by Dimension values. Run the P&L filtered to one Department dimension value — showing one department's P&L without creating separate reports per department.
Standard Financial Reports in Business Central: Income Statement, Balance Sheet, Cash Flow Statement, Trial Balance, Budget Comparison. Each is a pre-built Financial Report that can be customised to match the client's preferred layout.
💡 Pro Tip: Build the Financial Reports in requirements by reverse-engineering the client's existing Excel P&L and Balance Sheet. Map each Excel row to a Business Central G/L account range or formula. This exercise is the most important financial configuration activity — done correctly, it means Finance teams can stop maintaining their Excel reports and trust Business Central reporting from day 1 of go-live.
Intercompany (IC) functionality in Business Central automates accounting between two or more Business Central companies within the same group — eliminating manual journal entries for intercompany transactions.
IC setup components: IC Partner Code: A code linking two Business Central companies (or a Business Central company to a non-BC entity). IC Chart of Accounts: A shared account mapping — maps each company's G/L accounts to the intercompany account codes. IC Dimension Mapping: Maps dimension values between companies for consistent reporting.
IC transaction flow: Company A posts a sales invoice to Company B. Business Central automatically creates an IC Outbox transaction for Company A. Company B's IC Inbox receives the transaction. Company B reviews and accepts the IC transaction → A matching purchase invoice is created in Company B automatically. Both entries use the IC account mapping to ensure offsetting entries in each company's books.
IC scenarios supported: Intercompany sales (Company A sells goods to Company B). Intercompany expenses (Company A pays expenses on behalf of Company B and recharges). Intercompany loans (cash transfers between group entities). Intercompany journals (manual recharges, cost allocations).
IC setup components: IC Partner Code: A code linking two Business Central companies (or a Business Central company to a non-BC entity). IC Chart of Accounts: A shared account mapping — maps each company's G/L accounts to the intercompany account codes. IC Dimension Mapping: Maps dimension values between companies for consistent reporting.
IC transaction flow: Company A posts a sales invoice to Company B. Business Central automatically creates an IC Outbox transaction for Company A. Company B's IC Inbox receives the transaction. Company B reviews and accepts the IC transaction → A matching purchase invoice is created in Company B automatically. Both entries use the IC account mapping to ensure offsetting entries in each company's books.
IC scenarios supported: Intercompany sales (Company A sells goods to Company B). Intercompany expenses (Company A pays expenses on behalf of Company B and recharges). Intercompany loans (cash transfers between group entities). Intercompany journals (manual recharges, cost allocations).
💡 Pro Tip: Intercompany in Business Central requires all participating companies to be either in the same Business Central environment (same tenant) or connected via file-based IC exchange. If companies are in different tenants, the file-based exchange is more manual. Confirm the multi-company setup early — the same-tenant vs. cross-tenant architecture determines how automated the IC process can be.
Cash Flow Forecast in Business Central provides a forward-looking projection of cash inflows and outflows — helping management anticipate cash shortfalls and plan financing needs in advance.
Cash flow sources (configurable): Receivables: Open customer invoices and their expected payment dates (based on payment terms). Payables: Open vendor invoices and their payment due dates. Sales Orders: Expected revenue from confirmed but uninvoiced sales orders. Purchase Orders: Expected cash outflow from confirmed purchase orders. Fixed Assets: Planned capital expenditure (purchase orders for assets). GL Budget: Manual cash flow budget entries for items not captured by the above. Bank Transfers: Planned transfers between bank accounts.
Cash Flow Forecast setup: Business Central → Cash Flow Forecast → Setup. Enable each cash flow source. Set Lead Time Calculation for each source (how far in advance to project). Set the Forecast Period (weekly, monthly, quarterly view).
Azure AI integration: Business Central can use Azure Machine Learning to improve cash flow forecast accuracy based on historical payment patterns — predicting which invoices will pay early, late, or on time.
Cash flow sources (configurable): Receivables: Open customer invoices and their expected payment dates (based on payment terms). Payables: Open vendor invoices and their payment due dates. Sales Orders: Expected revenue from confirmed but uninvoiced sales orders. Purchase Orders: Expected cash outflow from confirmed purchase orders. Fixed Assets: Planned capital expenditure (purchase orders for assets). GL Budget: Manual cash flow budget entries for items not captured by the above. Bank Transfers: Planned transfers between bank accounts.
Cash Flow Forecast setup: Business Central → Cash Flow Forecast → Setup. Enable each cash flow source. Set Lead Time Calculation for each source (how far in advance to project). Set the Forecast Period (weekly, monthly, quarterly view).
Azure AI integration: Business Central can use Azure Machine Learning to improve cash flow forecast accuracy based on historical payment patterns — predicting which invoices will pay early, late, or on time.
💡 Pro Tip: Cash flow forecast accuracy depends heavily on payment terms being correctly set on customer and vendor cards, and on sales and purchase orders being raised promptly. A firm that creates invoices only at the end of the month will have a cash flow forecast that is empty for most of the month. If cash flow forecasting is a key requirement, include "timely order/invoice creation" as a process requirement alongside the system configuration.
Aging reports in Business Central show open receivables (customer aging) or open payables (vendor aging) broken down by how long they have been outstanding — the primary tool for credit control and payment management.
Customer Aging (Aged Accounts Receivable): Shows all open customer invoices grouped by aging bucket: Current (not yet due), 1-30 days overdue, 31-60 days overdue, 61-90 days overdue, 90+ days overdue. Key uses: Chase overdue invoices, assess customer credit risk, calculate bad debt provisions.
Vendor Aging (Aged Accounts Payable): Shows all open vendor invoices grouped by aging bucket and upcoming due dates. Key uses: Plan payment runs, avoid late payment penalties, identify overdue payables that may affect supplier relationships.
Report configuration options: Aging Date (calculate aging from: Due Date, Posting Date, or Document Date). Aging Period Length (configurable — 30 days, 60 days, or custom). Filter by currency, salesperson, payment method. Include unapplied payments (show payments not yet matched to invoices).
Ageing by due date vs posting date: Due Date aging shows what is actually overdue. Posting Date aging shows when transactions were created — useful for volume analysis but not credit management.
Customer Aging (Aged Accounts Receivable): Shows all open customer invoices grouped by aging bucket: Current (not yet due), 1-30 days overdue, 31-60 days overdue, 61-90 days overdue, 90+ days overdue. Key uses: Chase overdue invoices, assess customer credit risk, calculate bad debt provisions.
Vendor Aging (Aged Accounts Payable): Shows all open vendor invoices grouped by aging bucket and upcoming due dates. Key uses: Plan payment runs, avoid late payment penalties, identify overdue payables that may affect supplier relationships.
Report configuration options: Aging Date (calculate aging from: Due Date, Posting Date, or Document Date). Aging Period Length (configurable — 30 days, 60 days, or custom). Filter by currency, salesperson, payment method. Include unapplied payments (show payments not yet matched to invoices).
Ageing by due date vs posting date: Due Date aging shows what is actually overdue. Posting Date aging shows when transactions were created — useful for volume analysis but not credit management.
💡 Pro Tip: Aging reports are among the most frequently run reports in any Business Central implementation. Configure them as a Personal Views shortcut on the Finance team's Role Centre (home page). Also set up a weekly automated email with the aging report as an Excel attachment — sent to the credit controller every Monday morning. This automation alone often recovers 5-10% of debtor days for SMB clients.
Payment Terms in Business Central define the credit period and any early payment discounts for customer and vendor transactions — directly controlling when invoices become due and how payment discounts are calculated.
Payment Terms fields: Code (short identifier — e.g., NET30, COD, 2/10NET30), Description (human-readable label), Due Date Calculation (date formula — e.g., 30D = 30 days from invoice, CM+30D = end of current month + 30 days), Discount % (early payment discount percentage), Discount Date Calculation (deadline for discount — e.g., 10D for 2% if paid within 10 days).
Date formula examples: "30D" = 30 days from posting date. "CM" = end of current month. "CM+15D" = 15 days after end of current month. "1M" = one calendar month. "D10" = 10th day of next month.
Assignment: Default Payment Terms can be set on: Customer Card (applied to all their invoices by default), Vendor Card (applied to all their purchase invoices). Can be overridden on individual documents.
Payment Terms fields: Code (short identifier — e.g., NET30, COD, 2/10NET30), Description (human-readable label), Due Date Calculation (date formula — e.g., 30D = 30 days from invoice, CM+30D = end of current month + 30 days), Discount % (early payment discount percentage), Discount Date Calculation (deadline for discount — e.g., 10D for 2% if paid within 10 days).
Date formula examples: "30D" = 30 days from posting date. "CM" = end of current month. "CM+15D" = 15 days after end of current month. "1M" = one calendar month. "D10" = 10th day of next month.
Assignment: Default Payment Terms can be set on: Customer Card (applied to all their invoices by default), Vendor Card (applied to all their purchase invoices). Can be overridden on individual documents.
💡 Pro Tip: Accurate payment terms on customer and vendor cards are essential for cash flow forecasting, aging reports, and the payment suggestion function. During data migration, validate payment terms for every imported customer and vendor. Incorrect payment terms mean the aging report shows invoices as "current" that are actually overdue — leading to missed collections. Payment terms validation is a data quality requirement, not just a configuration requirement.
Questions 31–40 of 75
The General Journal in Business Central is the manual accounting entry mechanism — used for transactions that do not originate from sales, purchase, or other module-specific documents.
Types of General Journals: General Journal: Freeform journal for any G/L posting (accruals, prepayments, corrections, cost allocations, opening balances). Cash Receipts Journal: Record customer payments received (cash and cheque). Payment Journal: Record vendor payments made. Fixed Asset Journal: Post asset acquisitions and disposals manually. Recurring Journal: Journal template that repeats on a schedule with fixed or variable amounts — used for monthly accruals, depreciation postings, and standing charges.
Journal Template and Batch structure: Journal Template: The category (General, Cash Receipts, Payments). Controls which account types are allowed and which number series to use. Journal Batch: A named subset within a template. Multiple users can work in different batches simultaneously without conflict. E.g., "MARCH-ACQ" batch for March month-end accruals.
Balancing and error prevention: Business Central enforces that each journal batch balances to zero before posting (Total Debit = Total Credit). Force Doc. Balance option requires each document number within the batch to balance independently.
Types of General Journals: General Journal: Freeform journal for any G/L posting (accruals, prepayments, corrections, cost allocations, opening balances). Cash Receipts Journal: Record customer payments received (cash and cheque). Payment Journal: Record vendor payments made. Fixed Asset Journal: Post asset acquisitions and disposals manually. Recurring Journal: Journal template that repeats on a schedule with fixed or variable amounts — used for monthly accruals, depreciation postings, and standing charges.
Journal Template and Batch structure: Journal Template: The category (General, Cash Receipts, Payments). Controls which account types are allowed and which number series to use. Journal Batch: A named subset within a template. Multiple users can work in different batches simultaneously without conflict. E.g., "MARCH-ACQ" batch for March month-end accruals.
Balancing and error prevention: Business Central enforces that each journal batch balances to zero before posting (Total Debit = Total Credit). Force Doc. Balance option requires each document number within the batch to balance independently.
💡 Pro Tip: Recurring journals are one of the most valuable features for Finance teams with repeating monthly entries. A recurring journal for monthly rent, insurance, and software subscription accruals saves 20-30 minutes of manual entry every month. Document all recurring entries in a "Recurring Journal Register" in requirements — this is often a list the Finance team does not realise they need until you ask "What do you post manually every month?"
Inventory Costing in Business Central determines the monetary value of inventory on the balance sheet and the cost of goods sold on the P&L — one of the most technically complex areas of Business Central configuration.
Costing methods supported: FIFO (First In, First Out): Oldest items valued first. LIFO (Last In, First Out): Newest items valued first (not allowed in some jurisdictions). Average: Weighted average cost of all units in stock. Standard: Pre-set standard cost — variance posted when actual cost differs. Specific: Individual unit tracking (for high-value serialised items — jewellery, machinery).
Automatic Cost Posting: Inventory G/L Setup → Automatic Cost Posting: On. Every inventory transaction (receipt, shipment, adjustment) immediately posts to the G/L. Off: Inventory transactions post to a staging area — a periodic "Post Inventory Cost to G/L" batch job updates the G/L.
Inventory Valuation report: Shows the inventory value by item at any point in time. Reconciles with the Inventory G/L account balance. Discrepancies indicate missed posting or configuration errors.
Adjust Cost - Item Entries batch job: For Average and FIFO costing, this job recalculates item costs after all receipts for a period are known — correcting any forward-looking cost estimates. Must be run before closing an accounting period.
Costing methods supported: FIFO (First In, First Out): Oldest items valued first. LIFO (Last In, First Out): Newest items valued first (not allowed in some jurisdictions). Average: Weighted average cost of all units in stock. Standard: Pre-set standard cost — variance posted when actual cost differs. Specific: Individual unit tracking (for high-value serialised items — jewellery, machinery).
Automatic Cost Posting: Inventory G/L Setup → Automatic Cost Posting: On. Every inventory transaction (receipt, shipment, adjustment) immediately posts to the G/L. Off: Inventory transactions post to a staging area — a periodic "Post Inventory Cost to G/L" batch job updates the G/L.
Inventory Valuation report: Shows the inventory value by item at any point in time. Reconciles with the Inventory G/L account balance. Discrepancies indicate missed posting or configuration errors.
Adjust Cost - Item Entries batch job: For Average and FIFO costing, this job recalculates item costs after all receipts for a period are known — correcting any forward-looking cost estimates. Must be run before closing an accounting period.
💡 Pro Tip: Costing method selection is irreversible without a complex migration process. Run a dedicated "Costing Method Workshop" with the Finance Director and Warehouse Manager before any items are set up in Business Central. Ask: "How do you currently value inventory? What does your auditor require?" The answer — combined with the product type — determines the correct costing method for each item category.
Business Central offers a spectrum of warehouse management capabilities — from basic inventory locations to directed put-away and pick with barcode scanning.
Warehouse complexity levels (configurable per location): No warehouse management: Inventory tracked at item + location level only. No bins, no specific pick/put-away. Basic Warehouse: Add bins within a location. Require bin assignment on receipts and shipments. Warehouse Activity Documents (Inventory Pick / Inventory Put-Away) — paper-based or basic scanning. Advanced Warehouse (WMS): Full directed put-away and pick. Warehouse Receipts, Warehouse Shipments, Pick Worksheets, Put-Away Worksheets. Integration with handheld scanners via warehouse mobile app.
Bin setup: Bins are named locations within a warehouse (Row 1 Shelf 3, Receiving Dock A, Bulk Storage Zone B). Each bin has a bin type (Receive, Ship, Pick, Put-Away, QC). Items have a preferred bin and a bin content (what is stored where).
Warehouse Mobile App: Business Central's warehouse workers use the Warehouse Mobile App (a browser-based app optimised for warehouse handhelds and tablets). Supports: Inventory Pick, Inventory Put-Away, Internal Movements, Physical Inventory Counting, Bin Content Lookup.
Warehouse complexity levels (configurable per location): No warehouse management: Inventory tracked at item + location level only. No bins, no specific pick/put-away. Basic Warehouse: Add bins within a location. Require bin assignment on receipts and shipments. Warehouse Activity Documents (Inventory Pick / Inventory Put-Away) — paper-based or basic scanning. Advanced Warehouse (WMS): Full directed put-away and pick. Warehouse Receipts, Warehouse Shipments, Pick Worksheets, Put-Away Worksheets. Integration with handheld scanners via warehouse mobile app.
Bin setup: Bins are named locations within a warehouse (Row 1 Shelf 3, Receiving Dock A, Bulk Storage Zone B). Each bin has a bin type (Receive, Ship, Pick, Put-Away, QC). Items have a preferred bin and a bin content (what is stored where).
Warehouse Mobile App: Business Central's warehouse workers use the Warehouse Mobile App (a browser-based app optimised for warehouse handhelds and tablets). Supports: Inventory Pick, Inventory Put-Away, Internal Movements, Physical Inventory Counting, Bin Content Lookup.
💡 Pro Tip: Always visit the physical warehouse before designing the Business Central warehouse configuration. The number of locations, bin structure, put-away logic, and pick strategy must reflect physical reality. A warehouse configuration designed from a desk without a site visit is almost always wrong. Budget at least one full day on-site at the warehouse during discovery — it is the most valuable day of the entire implementation.
The Bill of Materials (BOM) and Routing are the two foundational master data records for manufacturing in Business Central — together they define what to make and how to make it.
Production BOM: A hierarchical list of components required to produce one unit of a finished good. BOM levels: Single-level BOM (all components at one level). Multi-level BOM (components that are themselves manufactured items — sub-assemblies). BOM Version: Multiple versions for engineering changes — only one version is "Certified" (active) at a time. Scrap %: Per-component waste factor added to the required quantity.
Routing: The sequence of manufacturing operations to produce one unit of a finished good. Each routing line: Operation No., Work Centre or Machine Centre, Setup Time (one-time preparation), Run Time (per unit production time), Queue Time (wait time before the operation), Move Time (transfer time after the operation). Routing Version: Multiple routing versions (for different production configurations).
How they connect: The Production Order links the finished item to its BOM and Routing. BOM determines component requirements (materials planning via MRP). Routing determines capacity requirements (production scheduling) and production costs.
Production BOM: A hierarchical list of components required to produce one unit of a finished good. BOM levels: Single-level BOM (all components at one level). Multi-level BOM (components that are themselves manufactured items — sub-assemblies). BOM Version: Multiple versions for engineering changes — only one version is "Certified" (active) at a time. Scrap %: Per-component waste factor added to the required quantity.
Routing: The sequence of manufacturing operations to produce one unit of a finished good. Each routing line: Operation No., Work Centre or Machine Centre, Setup Time (one-time preparation), Run Time (per unit production time), Queue Time (wait time before the operation), Move Time (transfer time after the operation). Routing Version: Multiple routing versions (for different production configurations).
How they connect: The Production Order links the finished item to its BOM and Routing. BOM determines component requirements (materials planning via MRP). Routing determines capacity requirements (production scheduling) and production costs.
💡 Pro Tip: BOM accuracy directly affects inventory management, production costing, and MRP accuracy. A BOM that is 95% correct but missing 5% of components causes production stoppages when those components run out unexpectedly. Always request the client's current BOMs in electronic format (their ERP export or Excel sheets) and perform a line-by-line data validation before importing. BOM data quality is the #1 risk in manufacturing implementations.
Assembly Management in Business Central (available in both Essentials and Premium) handles the assembly of finished goods from components — a lighter-weight alternative to full Production Orders for simpler make-to-order or make-to-stock assembly operations.
Assembly vs Production Orders: Assembly Orders: Simple, no routing/work centres needed. Components consumed and output item produced in one step. Best for: kit assembly, configuration-to-order, packaging. Production Orders: Full manufacturing with operations, work centres, routing, capacity planning. Best for: complex manufacturing with multiple production steps.
Assembly Order types: Assemble-to-Stock: Assemble finished goods into inventory in advance of sales demand. Assemble-to-Order: Assemble specifically for a customer order — the assembly order is linked directly to the sales order line. Components are reserved and consumed at shipment. Allows customer-specific configurations (component substitution per order).
Assembly Bill of Materials: Similar structure to Production BOM but simpler — no routing or work centres. Lists components required per assembly unit. Supports component substitution for assemble-to-order scenarios.
Assembly vs Production Orders: Assembly Orders: Simple, no routing/work centres needed. Components consumed and output item produced in one step. Best for: kit assembly, configuration-to-order, packaging. Production Orders: Full manufacturing with operations, work centres, routing, capacity planning. Best for: complex manufacturing with multiple production steps.
Assembly Order types: Assemble-to-Stock: Assemble finished goods into inventory in advance of sales demand. Assemble-to-Order: Assemble specifically for a customer order — the assembly order is linked directly to the sales order line. Components are reserved and consumed at shipment. Allows customer-specific configurations (component substitution per order).
Assembly Bill of Materials: Similar structure to Production BOM but simpler — no routing or work centres. Lists components required per assembly unit. Supports component substitution for assemble-to-order scenarios.
💡 Pro Tip: Assembly-to-Order with customer-specific configurations is a popular feature for distributors and light manufacturers who configure products to order (e.g., custom PC builds, personalised gift baskets, configured electronics). Demonstrate this feature early in the discovery process — it often surprises clients who assumed they needed full manufacturing (Premium licence) but can actually meet their needs with Assembly (Essentials licence).
The Role Centre in Business Central is the personalised home page shown to each user when they log in — designed for their specific job function. Instead of navigating a complex menu system, users see the most relevant information and tasks immediately.
Standard Role Centres available: Business Manager (executive overview — KPI tiles, financial charts, action items). Accountant (journal postings, bank reconciliation tasks, financial reports). Sales Order Processor (new orders queue, shipment tasks, customer credit alerts). Purchasing Agent (purchase orders, vendor invoices, reorder alerts). Inventory Manager (stock levels, reorder suggestions, warehouse tasks).
Role Centre components: Headline banner (AI-generated insight — "You have 5 invoices due today"). Cue tiles (count of items needing attention — "3 Sales Orders to Ship", "7 Vendor Invoices to Approve"). Charts (embedded charts — sales trend, cash position, aged receivables). Recent documents (quick access to recently viewed records). Navigation (role-specific menu showing only relevant modules and reports).
Role Centre personalisation: Individual users can personalise their Role Centre — adding/removing tiles, rearranging layout, pinning favourite reports. IT admins can lock Role Centre configuration to prevent unapproved changes.
Standard Role Centres available: Business Manager (executive overview — KPI tiles, financial charts, action items). Accountant (journal postings, bank reconciliation tasks, financial reports). Sales Order Processor (new orders queue, shipment tasks, customer credit alerts). Purchasing Agent (purchase orders, vendor invoices, reorder alerts). Inventory Manager (stock levels, reorder suggestions, warehouse tasks).
Role Centre components: Headline banner (AI-generated insight — "You have 5 invoices due today"). Cue tiles (count of items needing attention — "3 Sales Orders to Ship", "7 Vendor Invoices to Approve"). Charts (embedded charts — sales trend, cash position, aged receivables). Recent documents (quick access to recently viewed records). Navigation (role-specific menu showing only relevant modules and reports).
Role Centre personalisation: Individual users can personalise their Role Centre — adding/removing tiles, rearranging layout, pinning favourite reports. IT admins can lock Role Centre configuration to prevent unapproved changes.
💡 Pro Tip: Configuring the right Role Centre per user type is one of the highest-impact go-live tasks — it determines first impressions and drives early adoption. In UAT, assign each test user their correct Role Centre and ask: "When you log in each morning, does this page show you everything you need to know about your day?" Their answer shapes the final Role Centre configuration. Generic Role Centres that show irrelevant information are a common cause of "the system is complicated" feedback post-go-live.
The Customer Ledger and Vendor Ledger in Business Central are the subsidiary ledgers for Accounts Receivable and Accounts Payable — storing the detailed transaction history for every customer and vendor at the document level.
Customer Ledger Entries: Every posted sales invoice, credit memo, payment, and discount creates a Customer Ledger Entry. Key fields: Customer No., Posting Date, Document Type (Invoice, Credit Memo, Payment, Refund), Document No., Amount, Remaining Amount, Due Date, Open (yes = unpaid balance outstanding). Applying entries: When a payment is applied to an invoice, both entries are marked as "Closed" — the Remaining Amount on the invoice goes to zero.
Vendor Ledger Entries: Same structure for vendor transactions — purchase invoices, credit memos, payments. Unapplied entries: Payments posted without application to specific invoices — appear in the Vendor Ledger as open entries with a payment document type. Must be applied manually to clear the aging report.
Aged Accounts Receivable / Payable: These reports are built directly from Customer/Vendor Ledger Entries — showing only "Open" entries (Remaining Amount > 0). Correct aging depends on accurate application of payments to invoices.
Customer Ledger Entries: Every posted sales invoice, credit memo, payment, and discount creates a Customer Ledger Entry. Key fields: Customer No., Posting Date, Document Type (Invoice, Credit Memo, Payment, Refund), Document No., Amount, Remaining Amount, Due Date, Open (yes = unpaid balance outstanding). Applying entries: When a payment is applied to an invoice, both entries are marked as "Closed" — the Remaining Amount on the invoice goes to zero.
Vendor Ledger Entries: Same structure for vendor transactions — purchase invoices, credit memos, payments. Unapplied entries: Payments posted without application to specific invoices — appear in the Vendor Ledger as open entries with a payment document type. Must be applied manually to clear the aging report.
Aged Accounts Receivable / Payable: These reports are built directly from Customer/Vendor Ledger Entries — showing only "Open" entries (Remaining Amount > 0). Correct aging depends on accurate application of payments to invoices.
💡 Pro Tip: Unapplied payments are the most common cause of incorrect aging reports in Business Central. A payment posted without applying it to a specific invoice will appear as an open credit in the Customer Ledger — the invoice will also appear as open and overdue. Train users to always apply payments at posting time, and run a weekly "Unapplied Entries" report to catch any that slipped through.
Item Tracking in Business Central provides traceability for inventory at the lot or serial number level — essential for industries with regulatory traceability requirements (food, pharmaceuticals, medical devices, electronics).
Item Tracking Code configuration: An Item Tracking Code defines the tracking behaviour for an item category. Key settings: Lot No. Required (must assign a lot number on every receipt, shipment, and movement), Serial No. Required (must assign a unique serial number to every individual unit), Lot/SN Expiration Date Required (mandatory expiry date per lot — for perishables), Lot/SN Info. Required (force user to create a tracking info record for audit notes). Assign the Item Tracking Code to each item that requires tracking.
Lot tracking use cases: Food manufacturer: Assign Lot No. = supplier batch number on receipt. If a supplier recalls a batch, immediately trace all units from that lot through production, finished goods, and sales. Pharmaceuticals: Lot No. = manufacturing batch. Expiry date tracked. Automatic block of expired lots from shipment.
Serial number tracking use cases: Electronics distributor: Each product unit has a unique serial number. Customer disputes warranty — system shows exactly when and to whom unit was sold. Service management: Serial-tracked items have their own service history in Business Central.
Item Tracking Code configuration: An Item Tracking Code defines the tracking behaviour for an item category. Key settings: Lot No. Required (must assign a lot number on every receipt, shipment, and movement), Serial No. Required (must assign a unique serial number to every individual unit), Lot/SN Expiration Date Required (mandatory expiry date per lot — for perishables), Lot/SN Info. Required (force user to create a tracking info record for audit notes). Assign the Item Tracking Code to each item that requires tracking.
Lot tracking use cases: Food manufacturer: Assign Lot No. = supplier batch number on receipt. If a supplier recalls a batch, immediately trace all units from that lot through production, finished goods, and sales. Pharmaceuticals: Lot No. = manufacturing batch. Expiry date tracked. Automatic block of expired lots from shipment.
Serial number tracking use cases: Electronics distributor: Each product unit has a unique serial number. Customer disputes warranty — system shows exactly when and to whom unit was sold. Service management: Serial-tracked items have their own service history in Business Central.
💡 Pro Tip: Item tracking significantly increases transaction data volume and can slow posting if not configured correctly. Only enable tracking on items that genuinely require it — not all items in a warehouse. Separate items into tracked (where regulation or warranty requires it) and non-tracked (standard commodity items). Enabling serial number tracking on every item in a high-volume distribution centre will cause performance problems.
Reminders and Finance Charges in Business Central automate the credit control process — sending structured overdue payment notices to customers and charging interest on late accounts.
Reminder Terms configuration: Reminder Terms Code (e.g., STD = Standard). Reminder Levels (typically 3 levels): Level 1 (Grace Period + 7 days): Gentle reminder. "Please find attached invoice overdue for payment." Level 2 (Grace Period + 21 days): Firm reminder with warning. "Your account is overdue. Please pay within 7 days to avoid charges." Level 3 (Grace Period + 35 days): Final notice with finance charge applied. "Your account requires immediate payment. Finance charges have been applied."
Finance Charge Terms: Linked to Reminder Level 3 (or configured separately). Interest Rate %: Monthly or annual rate applied to overdue balance. Minimum Amount: Minimum finance charge regardless of overdue balance. Calculate Only on Open Entries vs All Open Entries.
Reminder creation process: Sales → Create Reminders batch job. Filters: all customers with overdue entries. Creates Reminder records in draft (not yet sent). User reviews, edits if needed, Issues (finalises), then sends via email, print, or both.
Reminder Terms configuration: Reminder Terms Code (e.g., STD = Standard). Reminder Levels (typically 3 levels): Level 1 (Grace Period + 7 days): Gentle reminder. "Please find attached invoice overdue for payment." Level 2 (Grace Period + 21 days): Firm reminder with warning. "Your account is overdue. Please pay within 7 days to avoid charges." Level 3 (Grace Period + 35 days): Final notice with finance charge applied. "Your account requires immediate payment. Finance charges have been applied."
Finance Charge Terms: Linked to Reminder Level 3 (or configured separately). Interest Rate %: Monthly or annual rate applied to overdue balance. Minimum Amount: Minimum finance charge regardless of overdue balance. Calculate Only on Open Entries vs All Open Entries.
Reminder creation process: Sales → Create Reminders batch job. Filters: all customers with overdue entries. Creates Reminder records in draft (not yet sent). User reviews, edits if needed, Issues (finalises), then sends via email, print, or both.
💡 Pro Tip: Reminders are only effective if they are sent consistently. Configure a "Reminders Day" — typically the first Tuesday of each month — when the accounts team runs the Create Reminders batch job and issues all generated reminders. Consistent, predictable reminders train customers to pay on time far better than ad-hoc chasing calls. Build this process into the Finance team's monthly calendar as part of go-live planning.
Consolidation in Business Central combines the financial statements of multiple subsidiary companies into a single consolidated group view — essential for group reporting, management accounts, and statutory consolidated financial statements.
Consolidation setup: Create a "Consolidation Company" in Business Central — a special company that holds only consolidated data (not operational). Each subsidiary's Chart of Accounts is mapped to the Consolidation Company's CoA using a "Consolidation Account" field on each G/L account. If subsidiaries use different CoA structures, the mapping bridges the differences.
Consolidation process: Run the Import Consolidation from Company or Import Consolidation from File batch job for each subsidiary. Business Central imports each subsidiary's G/L balances, translating currencies and mapping accounts. Intercompany eliminations are posted as manual journal entries in the Consolidation Company. Consolidation Financial Reports are run from the Consolidation Company.
Currency translation: Foreign subsidiary balances are translated using: Historical rates (equity accounts — rate at transaction date), Average rates (P&L accounts — monthly average), Closing rates (balance sheet accounts — rate at period end). Currency Translation Adjustment (CTA) is posted as an equity adjustment.
Consolidation setup: Create a "Consolidation Company" in Business Central — a special company that holds only consolidated data (not operational). Each subsidiary's Chart of Accounts is mapped to the Consolidation Company's CoA using a "Consolidation Account" field on each G/L account. If subsidiaries use different CoA structures, the mapping bridges the differences.
Consolidation process: Run the Import Consolidation from Company or Import Consolidation from File batch job for each subsidiary. Business Central imports each subsidiary's G/L balances, translating currencies and mapping accounts. Intercompany eliminations are posted as manual journal entries in the Consolidation Company. Consolidation Financial Reports are run from the Consolidation Company.
Currency translation: Foreign subsidiary balances are translated using: Historical rates (equity accounts — rate at transaction date), Average rates (P&L accounts — monthly average), Closing rates (balance sheet accounts — rate at period end). Currency Translation Adjustment (CTA) is posted as an equity adjustment.
💡 Pro Tip: Business Central consolidation is suitable for groups of 2-10 subsidiaries with straightforward group structures. For complex groups (50+ subsidiaries, multi-currency, minority interests, equity accounting), specialist consolidation tools (CCH Tagetik, OneStream, SAP BPC) are better suited. Set realistic expectations in requirements — Business Central consolidation handles the basics well but is not a full-featured group reporting platform.
Questions 41–50 of 75
Data migration is one of the highest-risk activities in any Business Central implementation — incorrect migration of master data or opening balances causes ongoing operational problems.
Data migration tools available: RapidStart Services (built-in Business Central tool): Configuration Packages (Excel-based). Each entity (Customers, Vendors, Items, etc.) is exported as an Excel template. Data is entered in Excel and imported into Business Central. Validation runs on import — errors are reported per row. Best for: initial go-live migrations of 1,000-10,000 records.
Data migration layers: Layer 1 — Configuration data: Posting groups, Number Series, Payment Terms (must be configured first — master data imports reference these). Layer 2 — Master data: Customers, Vendors, Items, Chart of Accounts (must be imported before transactional data). Layer 3 — Opening balances: Customer/vendor ledger open entries, inventory opening balance, G/L opening balance. Layer 4 — Historical data (optional): Prior period transactions for reporting history — only if reporting requirement demands it.
Data validation checks after migration: Customer count and AR balance matches source system. Vendor count and AP balance matches. Inventory item count and value matches. Trial balance debit = credit. Bank account balance matches last known statement.
Data migration tools available: RapidStart Services (built-in Business Central tool): Configuration Packages (Excel-based). Each entity (Customers, Vendors, Items, etc.) is exported as an Excel template. Data is entered in Excel and imported into Business Central. Validation runs on import — errors are reported per row. Best for: initial go-live migrations of 1,000-10,000 records.
Data migration layers: Layer 1 — Configuration data: Posting groups, Number Series, Payment Terms (must be configured first — master data imports reference these). Layer 2 — Master data: Customers, Vendors, Items, Chart of Accounts (must be imported before transactional data). Layer 3 — Opening balances: Customer/vendor ledger open entries, inventory opening balance, G/L opening balance. Layer 4 — Historical data (optional): Prior period transactions for reporting history — only if reporting requirement demands it.
Data validation checks after migration: Customer count and AR balance matches source system. Vendor count and AP balance matches. Inventory item count and value matches. Trial balance debit = credit. Bank account balance matches last known statement.
💡 Pro Tip: The most dangerous migration step is opening balances. If opening balances are incorrect, every subsequent aging report, trial balance, and financial statement will be wrong — and the errors compound over time. Perform a reconciliation between the source system's final closing trial balance and Business Central's opening trial balance before any live transactions are posted. Do not go live until this reconciliation is 100% clean.
Microsoft provides a native Shopify connector in D365 Business Central (included at no additional cost since 2022) — enabling real-time synchronisation between a Shopify eCommerce store and Business Central ERP without third-party middleware.
What the connector synchronises: Products/Items: Item master data (name, price, description, images, variants) synced from Business Central to Shopify. Inventory: Stock levels pushed from Business Central to Shopify in real time — prevents overselling. Orders: Shopify orders automatically imported into Business Central as Sales Orders. Customers: New Shopify customers created in Business Central on first order. Payments: Payment capture status from Shopify reflected on Business Central Sales Orders. Fulfilment: When a Business Central shipment is posted, the order is marked as fulfilled in Shopify and the customer receives a tracking email.
Configuration options: Multiple Shopify shops: Connect multiple Shopify stores to one Business Central instance (e.g., a B2B store and a B2C store). Order import frequency: Real-time or scheduled (every 15 minutes). Item sync direction: One-way (BC to Shopify) or two-way. Price sync: Which price list in BC maps to which price tier in Shopify.
What the connector synchronises: Products/Items: Item master data (name, price, description, images, variants) synced from Business Central to Shopify. Inventory: Stock levels pushed from Business Central to Shopify in real time — prevents overselling. Orders: Shopify orders automatically imported into Business Central as Sales Orders. Customers: New Shopify customers created in Business Central on first order. Payments: Payment capture status from Shopify reflected on Business Central Sales Orders. Fulfilment: When a Business Central shipment is posted, the order is marked as fulfilled in Shopify and the customer receives a tracking email.
Configuration options: Multiple Shopify shops: Connect multiple Shopify stores to one Business Central instance (e.g., a B2B store and a B2C store). Order import frequency: Real-time or scheduled (every 15 minutes). Item sync direction: One-way (BC to Shopify) or two-way. Price sync: Which price list in BC maps to which price tier in Shopify.
💡 Pro Tip: The Shopify connector is a significant competitive advantage for Business Central — it removes the most common integration pain point for SMB retailers. In demos, always show the end-to-end flow: "Customer orders on Shopify → Sales Order appears in Business Central within 1 minute → Inventory decremented → Shipment posted → Shopify order fulfilled automatically." This 3-minute demo converts more SMB prospects than any feature list.
User Permissions in Business Central control what each user can see and do — implemented through Permission Sets that grant specific read, insert, modify, delete, and execute rights on tables, pages, reports, and codeunits.
Permission Set structure: Permission Set: A named collection of permissions. E.g., "SALES-ALL" permission set grants access to all sales-related pages and tables. Objects types covered: Table (data access), Page (UI access), Report (report execution), Codeunit (business logic execution), XMLport (data import/export).
Access types: Read (R): Can view data. Insert (I): Can create new records. Modify (M): Can edit existing records. Delete (D): Can delete records. Execute (X): Can run the object. Indirect: Access required by another object (e.g., to post a sales invoice, you need indirect access to the G/L Entry table).
Permission Set assignment: Assign Permission Sets to User Groups. Assign User Groups to Users. Multiple Permission Sets can be assigned — permissions combine additively (the union of all assigned sets).
Microsoft standard Permission Sets: Business Central includes pre-built Permission Sets (BC-ALL for full access, D365 BASIC for standard user access, D365 SALES for sales function access). These can be used as-is or copied and modified.
Permission Set structure: Permission Set: A named collection of permissions. E.g., "SALES-ALL" permission set grants access to all sales-related pages and tables. Objects types covered: Table (data access), Page (UI access), Report (report execution), Codeunit (business logic execution), XMLport (data import/export).
Access types: Read (R): Can view data. Insert (I): Can create new records. Modify (M): Can edit existing records. Delete (D): Can delete records. Execute (X): Can run the object. Indirect: Access required by another object (e.g., to post a sales invoice, you need indirect access to the G/L Entry table).
Permission Set assignment: Assign Permission Sets to User Groups. Assign User Groups to Users. Multiple Permission Sets can be assigned — permissions combine additively (the union of all assigned sets).
Microsoft standard Permission Sets: Business Central includes pre-built Permission Sets (BC-ALL for full access, D365 BASIC for standard user access, D365 SALES for sales function access). These can be used as-is or copied and modified.
💡 Pro Tip: Use the "Expand All" function in the Permission Set page to review all permissions in detail — many consultants accept the default permission sets without verifying what they actually grant. Run a security audit 2 weeks after go-live: check that no users have more access than their role requires. The "Effective Permissions" lookup tool in Business Central shows exactly what a specific user can do — use it to validate the security model in UAT.
A Business Central Sandbox is a non-production environment — an isolated copy of Business Central used for development, testing, training, and UAT without affecting the live production environment.
Types of Business Central environments: Production: The live company environment with real data. Sandbox: Non-production — created from scratch or as a copy of production. Test data or production data can be loaded. Developer Sandbox: Specifically for AL code development — linked to Visual Studio Code and GitHub.
Sandbox creation options: Copy from Production: Creates an exact replica of the production environment including all data. Best for UAT — users test with realistic data. Create from Scratch: Fresh empty environment. Best for initial development and configuration. Copy from Backup: Restore from a point-in-time backup of production.
Sandbox safeguards: Outbound email is disabled by default — prevents test emails from reaching real customers. External integrations (to banks, payment providers, etc.) should also be disabled or pointed to test endpoints. Business Central marks Sandbox environments with a banner: "This is a Sandbox environment."
Types of Business Central environments: Production: The live company environment with real data. Sandbox: Non-production — created from scratch or as a copy of production. Test data or production data can be loaded. Developer Sandbox: Specifically for AL code development — linked to Visual Studio Code and GitHub.
Sandbox creation options: Copy from Production: Creates an exact replica of the production environment including all data. Best for UAT — users test with realistic data. Create from Scratch: Fresh empty environment. Best for initial development and configuration. Copy from Backup: Restore from a point-in-time backup of production.
Sandbox safeguards: Outbound email is disabled by default — prevents test emails from reaching real customers. External integrations (to banks, payment providers, etc.) should also be disabled or pointed to test endpoints. Business Central marks Sandbox environments with a banner: "This is a Sandbox environment."
💡 Pro Tip: Always start UAT with a sandbox that is a copy of production (or a clean migration load). Users who test against realistic data find real problems. Users who test against "demo data" find only demo problems. The investment in creating a production-copy sandbox pays back immediately in UAT quality — and dramatically reduces post-go-live support calls.
Item Reorder Planning in Business Central ensures inventory levels are maintained to meet demand — generating suggested purchase or production orders when stock falls below defined thresholds.
Reorder policies per item: Fixed Reorder Qty: When inventory falls below the Reorder Point, order a fixed Reorder Quantity. Simple and predictable — best for A items with stable demand. Maximum Qty: Maintain inventory between a Minimum and Maximum level. When below Minimum, order up to Maximum. Lot-for-Lot: Order exactly what demand requires for a defined period — minimises inventory but requires more frequent orders. Order: Order exactly what a specific demand (sales order, production order) requires — used for expensive or custom items. None: No automatic reorder — manual purchasing only.
Planning parameters per item/location: Reorder Point, Reorder Quantity, Safety Stock Quantity, Maximum Inventory, Minimum Order Quantity, Order Multiple (round up to nearest pallet/case).
Planning Worksheet: MRP/MPS run. Shows all suggested purchase and production orders. Planner reviews, adjusts, and "carries out action messages" — converting suggestions into real purchase orders or production orders.
Reorder policies per item: Fixed Reorder Qty: When inventory falls below the Reorder Point, order a fixed Reorder Quantity. Simple and predictable — best for A items with stable demand. Maximum Qty: Maintain inventory between a Minimum and Maximum level. When below Minimum, order up to Maximum. Lot-for-Lot: Order exactly what demand requires for a defined period — minimises inventory but requires more frequent orders. Order: Order exactly what a specific demand (sales order, production order) requires — used for expensive or custom items. None: No automatic reorder — manual purchasing only.
Planning parameters per item/location: Reorder Point, Reorder Quantity, Safety Stock Quantity, Maximum Inventory, Minimum Order Quantity, Order Multiple (round up to nearest pallet/case).
Planning Worksheet: MRP/MPS run. Shows all suggested purchase and production orders. Planner reviews, adjusts, and "carries out action messages" — converting suggestions into real purchase orders or production orders.
💡 Pro Tip: Planning parameters require operational knowledge that the Finance team usually does not have — they need input from the Operations Manager or Supply Chain team. Run a dedicated "Planning Parameters Workshop" with the people who manage inventory day-to-day. Ask: "For your top 20 items, what is the minimum you'd ever want in stock? What do you typically order? How far in advance do you need to order?" The answers become the planning parameters.
A fundamental control in Business Central is ensuring that the sub-ledger balances reconcile with the General Ledger — confirming that detailed transaction records match the summary G/L balances.
Key reconciliation checks: Accounts Receivable: Sum of open Customer Ledger entries = Balance on the AR G/L account. Accounts Payable: Sum of open Vendor Ledger entries = Balance on the AP G/L account. Inventory: Sum of Item Ledger Entry values = Balance on all Inventory G/L accounts. Fixed Assets: Sum of asset net book values = Balance on Fixed Asset G/L accounts. Bank: Bank Account Ledger balance = Balance on the Bank G/L account.
Business Central tools for reconciliation: Customer/Vendor Reconciliation Report: Directly compares sub-ledger totals to G/L. Inventory Valuation Report: Shows inventory value by item — should equal inventory G/L accounts. G/L to Bank Reconciliation: Bank account balance in BC vs. G/L bank account balance.
Causes of reconciliation differences: Direct G/L postings to the AR/AP account (bypassing the customer/vendor sub-ledger). Incorrect Posting Group setup (transactions posting to wrong accounts). Manual corrections that modified G/L entries without updating sub-ledger.
Key reconciliation checks: Accounts Receivable: Sum of open Customer Ledger entries = Balance on the AR G/L account. Accounts Payable: Sum of open Vendor Ledger entries = Balance on the AP G/L account. Inventory: Sum of Item Ledger Entry values = Balance on all Inventory G/L accounts. Fixed Assets: Sum of asset net book values = Balance on Fixed Asset G/L accounts. Bank: Bank Account Ledger balance = Balance on the Bank G/L account.
Business Central tools for reconciliation: Customer/Vendor Reconciliation Report: Directly compares sub-ledger totals to G/L. Inventory Valuation Report: Shows inventory value by item — should equal inventory G/L accounts. G/L to Bank Reconciliation: Bank account balance in BC vs. G/L bank account balance.
Causes of reconciliation differences: Direct G/L postings to the AR/AP account (bypassing the customer/vendor sub-ledger). Incorrect Posting Group setup (transactions posting to wrong accounts). Manual corrections that modified G/L entries without updating sub-ledger.
💡 Pro Tip: Run all reconciliation checks at the end of each month as part of the standard month-end close process. A difference discovered at year-end that has been accumulating for 11 months is extremely difficult to untangle. Build reconciliation checks into the Month-End Close Checklist as mandatory steps — with sign-off required from the Financial Controller before the period is closed.
Prepayments in Business Central handle advance payments — when a customer pays before goods are delivered (customer prepayment) or when you pay a vendor before receiving goods (vendor prepayment).
Customer Prepayment process: Create Sales Order. Set Prepayment % on the order (e.g., 30% advance required). Post Prepayment Invoice → Customer is invoiced for 30% of order value. Customer pays the prepayment invoice. When goods are shipped and invoiced, the final invoice shows the full order value minus the prepayment received → Customer pays the remaining 70%.
Vendor Prepayment process: Create Purchase Order. Set Prepayment %. Post Prepayment Invoice → Vendor is paid 30% in advance. When goods are received and vendor invoices, the final vendor invoice is reduced by the prepayment already paid.
Prepayment G/L accounts: Prepayments post to dedicated prepayment liability/asset accounts (not the main revenue/COGS accounts) until the final invoice is posted — ensuring correct accrual accounting treatment. Prepayment G/L accounts are configured in the General Posting Setup.
Customer Prepayment process: Create Sales Order. Set Prepayment % on the order (e.g., 30% advance required). Post Prepayment Invoice → Customer is invoiced for 30% of order value. Customer pays the prepayment invoice. When goods are shipped and invoiced, the final invoice shows the full order value minus the prepayment received → Customer pays the remaining 70%.
Vendor Prepayment process: Create Purchase Order. Set Prepayment %. Post Prepayment Invoice → Vendor is paid 30% in advance. When goods are received and vendor invoices, the final vendor invoice is reduced by the prepayment already paid.
Prepayment G/L accounts: Prepayments post to dedicated prepayment liability/asset accounts (not the main revenue/COGS accounts) until the final invoice is posted — ensuring correct accrual accounting treatment. Prepayment G/L accounts are configured in the General Posting Setup.
💡 Pro Tip: Prepayment requirements are common in construction, custom manufacturing, and high-value B2B sales — but often discovered late in implementation because "prepayment" sounds like a simple payment process to the client. Always ask: "Do you ever require advance deposits from customers before delivering? Do you ever pay suppliers in advance?" If yes, prepayment configuration is required — and it affects the Order creation process and G/L account setup in ways that cannot be easily retrofitted.
The Job Queue in Business Central is the scheduling engine that runs background tasks automatically at defined intervals — freeing users from manually running repetitive processes.
Common Job Queue entries: Adjust Cost - Item Entries (daily): Recalculates item costs for FIFO/Average costing — must run before period close. Post Inventory Cost to G/L (daily): Pushes inventory cost postings to the G/L — required if Automatic Cost Posting is off. Send Overdue Payment Reminders (weekly): Automatically creates and emails reminders to customers. Sync with Shopify (every 15 minutes): Imports new Shopify orders and updates inventory. Sales Invoice Posting (end of day): Posts all approved sales invoices in batch. Email queue processing (every 5 minutes): Sends outbound emails from Business Central. Update Exchange Rates (daily): Downloads latest exchange rates from a rate provider.
Job Queue Entry fields: Object Type (Codeunit or Report), Object ID, Schedule (start time, recurrence — daily, weekly, specific days/times), Status (Ready, In Queue, In Process, Error, On Hold). Error notifications: If a Job Queue entry fails, it can send an error notification email to an administrator.
Common Job Queue entries: Adjust Cost - Item Entries (daily): Recalculates item costs for FIFO/Average costing — must run before period close. Post Inventory Cost to G/L (daily): Pushes inventory cost postings to the G/L — required if Automatic Cost Posting is off. Send Overdue Payment Reminders (weekly): Automatically creates and emails reminders to customers. Sync with Shopify (every 15 minutes): Imports new Shopify orders and updates inventory. Sales Invoice Posting (end of day): Posts all approved sales invoices in batch. Email queue processing (every 5 minutes): Sends outbound emails from Business Central. Update Exchange Rates (daily): Downloads latest exchange rates from a rate provider.
Job Queue Entry fields: Object Type (Codeunit or Report), Object ID, Schedule (start time, recurrence — daily, weekly, specific days/times), Status (Ready, In Queue, In Process, Error, On Hold). Error notifications: If a Job Queue entry fails, it can send an error notification email to an administrator.
💡 Pro Tip: Job Queue configuration is often forgotten in go-live checklists. "Adjust Cost - Item Entries" not running daily causes inventory valuation discrepancies that surface at period close — typically when it is too late to fix them cleanly. Add a "Job Queue Audit" to the go-live checklist: verify every critical background job is scheduled, active, and showing as "Ready" or "In Queue" — not in Error status.
Understanding Business Central's licensing structure is essential for scoping and costing implementations accurately:
User licence types: Essentials ($70/user/month): Full access to all Essentials modules — Financials, Sales, Purchasing, Inventory, Warehouse (basic), Projects, Service (basic), HR (basic). Premium ($100/user/month): Includes everything in Essentials PLUS Manufacturing (full), Service Management (full). Team Member ($8/user/month): Very limited — can view and edit a subset of records, enter basic time and expenses, access specific customised pages. Cannot use core ERP modules. External Accountant (free): Read-only access for the client's external auditor or accountant — no posting rights.
Device licence: For shared devices (factory floor terminals, warehouse scanners). One device licence covers unlimited users on that device. Lower cost than named user licences for high-headcount warehouse scenarios.
Capacity addons: Additional database storage (default 80GB for Essentials, 80GB for Premium — can purchase additional storage). Additional environments (default: 3 production + 3 sandbox environments — can purchase additional).
User licence types: Essentials ($70/user/month): Full access to all Essentials modules — Financials, Sales, Purchasing, Inventory, Warehouse (basic), Projects, Service (basic), HR (basic). Premium ($100/user/month): Includes everything in Essentials PLUS Manufacturing (full), Service Management (full). Team Member ($8/user/month): Very limited — can view and edit a subset of records, enter basic time and expenses, access specific customised pages. Cannot use core ERP modules. External Accountant (free): Read-only access for the client's external auditor or accountant — no posting rights.
Device licence: For shared devices (factory floor terminals, warehouse scanners). One device licence covers unlimited users on that device. Lower cost than named user licences for high-headcount warehouse scenarios.
Capacity addons: Additional database storage (default 80GB for Essentials, 80GB for Premium — can purchase additional storage). Additional environments (default: 3 production + 3 sandbox environments — can purchase additional).
💡 Pro Tip: Always clarify whether the client needs Manufacturing before proposing a licence tier. Clients who believe they need "manufacturing" sometimes only need Assembly Management (available in Essentials) — saving $30/user/month. Conversely, clients who say they only need Essentials sometimes have a service management requirement that actually requires Premium. The licensing analysis is a revenue protection exercise — getting it wrong costs the client money or causes licence violations.
Audit Trail capability in Business Central ensures that all financial transactions are traceable, non-editable, and reversible — meeting the requirements of auditors and financial regulators.
Non-editable posted transactions: Once a transaction is posted in Business Central (sales invoice, purchase invoice, payment, journal entry), it cannot be edited or deleted. Any correction requires a reversal (offsetting entry) or a credit memo — creating a complete paper trail.
Reversal of Journal Entries: If a manually posted G/L journal entry was incorrect: Finance → General Ledger Entries → Find the incorrect entry → Reverse Transaction. Business Central creates an equal and opposite journal entry on the same posting date, effectively cancelling the original entry. Both the original and the reversal remain visible in the ledger.
Change Log: Business Central → Change Log Setup: Enable logging for specific tables and fields. When enabled, every insert, modify, or delete on the logged tables is recorded with: User ID, Date and Time, Old Value, New Value, Record ID. Supports: "Who changed this customer's credit limit and when?" "Who modified the vendor's bank account?"
Financial reporting trail: Every G/L entry has a drill-down to its source document (sales invoice, payment, etc.) — providing full traceability from the financial statement to the originating transaction.
Non-editable posted transactions: Once a transaction is posted in Business Central (sales invoice, purchase invoice, payment, journal entry), it cannot be edited or deleted. Any correction requires a reversal (offsetting entry) or a credit memo — creating a complete paper trail.
Reversal of Journal Entries: If a manually posted G/L journal entry was incorrect: Finance → General Ledger Entries → Find the incorrect entry → Reverse Transaction. Business Central creates an equal and opposite journal entry on the same posting date, effectively cancelling the original entry. Both the original and the reversal remain visible in the ledger.
Change Log: Business Central → Change Log Setup: Enable logging for specific tables and fields. When enabled, every insert, modify, or delete on the logged tables is recorded with: User ID, Date and Time, Old Value, New Value, Record ID. Supports: "Who changed this customer's credit limit and when?" "Who modified the vendor's bank account?"
Financial reporting trail: Every G/L entry has a drill-down to its source document (sales invoice, payment, etc.) — providing full traceability from the financial statement to the originating transaction.
💡 Pro Tip: Enable Change Log for the most sensitive master data fields: Customer credit limits, Vendor bank account details, Item costs and prices, G/L account setups. These are the fields where fraud or error has the highest financial impact. Do not enable Change Log on all tables and all fields — the log table grows very quickly and can impact performance. Targeted logging of high-risk fields is the right balance.
Questions 51–60 of 75
Microsoft is embedding Copilot (AI assistant) capabilities progressively into Business Central — reducing manual effort and improving decision quality across key business processes.
Current Copilot capabilities in Business Central:
Bank Reconciliation Assistance: AI analyses unmatched bank statement lines and suggests the most likely matching G/L entries or proposes new posting entries for bank charges and interest. Reduces manual reconciliation time by 30-50%.
Item/Product Description Generation: User enters basic product information (name, category, key attributes). Copilot generates a marketing-quality product description in the configured language — suitable for use in customer-facing catalogues and eCommerce listings. Particularly valuable for companies with large product catalogs that need descriptions in multiple languages.
Sales Lines Suggestion: When creating a sales order, the salesperson types a natural-language description of what the customer wants. Copilot suggests the matching item lines from the product catalog.
Cash Flow Analysis: AI-generated insights on the Cash Flow Forecast — highlighting unusual patterns, upcoming shortfalls, and suggesting the invoices most likely to cause cash flow strain.
Current Copilot capabilities in Business Central:
Bank Reconciliation Assistance: AI analyses unmatched bank statement lines and suggests the most likely matching G/L entries or proposes new posting entries for bank charges and interest. Reduces manual reconciliation time by 30-50%.
Item/Product Description Generation: User enters basic product information (name, category, key attributes). Copilot generates a marketing-quality product description in the configured language — suitable for use in customer-facing catalogues and eCommerce listings. Particularly valuable for companies with large product catalogs that need descriptions in multiple languages.
Sales Lines Suggestion: When creating a sales order, the salesperson types a natural-language description of what the customer wants. Copilot suggests the matching item lines from the product catalog.
Cash Flow Analysis: AI-generated insights on the Cash Flow Forecast — highlighting unusual patterns, upcoming shortfalls, and suggesting the invoices most likely to cause cash flow strain.
💡 Pro Tip: Product description generation via Copilot has immediate ROI for distributors and retailers with large product catalogs. A company with 5,000 items that has been postponing their eCommerce launch because "we don't have product descriptions" can generate first-draft descriptions for all 5,000 items in hours. Position this as a "hidden value" discovery during the implementation demo — it often surprises and delights clients who had not considered it.
The month-end and year-end close process in Business Central requires a structured checklist to ensure all transactions are processed, sub-ledgers reconcile with the G/L, and the period is locked correctly.
Month-End Close Checklist: Post all sales invoices and credit memos for the period. Post all purchase invoices and credit memos for the period. Apply all customer and vendor payments to their invoices. Run bank reconciliation for all bank accounts. Run "Adjust Cost - Item Entries" (for Average/FIFO costing). Post depreciation journals for Fixed Assets. Post accrual and prepayment reversal journals. Run Inventory Valuation Report — reconcile to Inventory G/L accounts. Run Customer/Vendor Reconciliation — reconcile AR/AP sub-ledgers to G/L. Post foreign currency revaluation (Adjust Exchange Rates batch job). Close the accounting period (Administration → Accounting Periods → Set period status).
Year-End Close: All month-end steps plus: Run "Close Income Statement" (moves P&L net income to retained earnings equity account). Open next fiscal year (Create New Fiscal Year).
Month-End Close Checklist: Post all sales invoices and credit memos for the period. Post all purchase invoices and credit memos for the period. Apply all customer and vendor payments to their invoices. Run bank reconciliation for all bank accounts. Run "Adjust Cost - Item Entries" (for Average/FIFO costing). Post depreciation journals for Fixed Assets. Post accrual and prepayment reversal journals. Run Inventory Valuation Report — reconcile to Inventory G/L accounts. Run Customer/Vendor Reconciliation — reconcile AR/AP sub-ledgers to G/L. Post foreign currency revaluation (Adjust Exchange Rates batch job). Close the accounting period (Administration → Accounting Periods → Set period status).
Year-End Close: All month-end steps plus: Run "Close Income Statement" (moves P&L net income to retained earnings equity account). Open next fiscal year (Create New Fiscal Year).
💡 Pro Tip: Build the Month-End Close Checklist as a document in the implementation project and train the Finance team on it during UAT. Run a full simulated month-end close in the Sandbox 2-3 weeks before go-live — using realistic data. This simulation typically reveals 3-5 process or configuration issues that would have been discovered on the real first month-end close, with far less pressure to fix them.
Distribution businesses using Business Central need a comprehensive Supply Chain Management configuration covering procurement, inventory, and fulfilment:
Procurement setup: Purchase Price Lists: Vendor-specific prices for items (different prices per vendor, per quantity tier, per currency). Purchase Order approval workflow: Multi-level approval based on order value thresholds. Vendor Performance Tracking: Lead time accuracy, delivery on-time rate, quality score.
Inventory setup: Multiple Locations: Each warehouse/store is a separate location. Transfer Orders: Move inventory between locations with in-transit tracking. Stockkeeping Units (SKUs): Define item parameters (reorder point, preferred vendor, lead time) per item per location — more granular than item-level planning parameters.
Sales Fulfilment setup: Available-to-Promise (ATP): When creating a sales order, Business Central checks if the ordered quantity is available and confirms the earliest ship date. Drop Shipment: Create a purchase order that ships directly from vendor to customer — no intermediate stock. Cross-Docking: Receive items at the warehouse and immediately allocate them to outbound shipments without putaway (reduces handling for high-velocity items).
Procurement setup: Purchase Price Lists: Vendor-specific prices for items (different prices per vendor, per quantity tier, per currency). Purchase Order approval workflow: Multi-level approval based on order value thresholds. Vendor Performance Tracking: Lead time accuracy, delivery on-time rate, quality score.
Inventory setup: Multiple Locations: Each warehouse/store is a separate location. Transfer Orders: Move inventory between locations with in-transit tracking. Stockkeeping Units (SKUs): Define item parameters (reorder point, preferred vendor, lead time) per item per location — more granular than item-level planning parameters.
Sales Fulfilment setup: Available-to-Promise (ATP): When creating a sales order, Business Central checks if the ordered quantity is available and confirms the earliest ship date. Drop Shipment: Create a purchase order that ships directly from vendor to customer — no intermediate stock. Cross-Docking: Receive items at the warehouse and immediately allocate them to outbound shipments without putaway (reduces handling for high-velocity items).
💡 Pro Tip: Stockkeeping Units (SKUs) are one of the most underused features in Business Central for multi-location distributors. A national distributor with 5 warehouses should have an SKU for every item in every location — with location-specific reorder points, preferred vendors, and safety stock. Without SKUs, all 5 locations use the same item-level parameters, which are almost never correct for every location. Introduce SKUs in requirements workshops by asking: "Do different warehouses have different minimum stock levels for the same item?"
Customer Statistics and Item Statistics in Business Central provide instant performance data on customers and products — accessible directly from their cards without running separate reports.
Customer Statistics panel (accessible from Customer Card): Current balance, Overdue balance, Outstanding orders, Outstanding invoices. Sales YTD, Last year sales, This month sales. Average payment days (DSO). Credit limit utilisation (current balance vs. credit limit). Last invoice date, Last payment date.
Item Statistics panel (accessible from Item Card): Current inventory quantity and value (by location). Sales quantity and value this year vs last year. Purchase quantity and value this year vs last year. Average cost, Last purchase price, Last sales price. Days in inventory (inventory days). Items ledger entries drill-down.
Customer/Item Sales Analysis: Go to any Customer record → Statistics → Open the Item Sales by Month matrix: rows = items, columns = months, cells = sales quantity or value. Instantly see which items each customer buys and when — without running a report.
Customer Statistics panel (accessible from Customer Card): Current balance, Overdue balance, Outstanding orders, Outstanding invoices. Sales YTD, Last year sales, This month sales. Average payment days (DSO). Credit limit utilisation (current balance vs. credit limit). Last invoice date, Last payment date.
Item Statistics panel (accessible from Item Card): Current inventory quantity and value (by location). Sales quantity and value this year vs last year. Purchase quantity and value this year vs last year. Average cost, Last purchase price, Last sales price. Days in inventory (inventory days). Items ledger entries drill-down.
Customer/Item Sales Analysis: Go to any Customer record → Statistics → Open the Item Sales by Month matrix: rows = items, columns = months, cells = sales quantity or value. Instantly see which items each customer buys and when — without running a report.
💡 Pro Tip: Train sales reps and account managers to check the Customer Statistics panel before every customer call. "Your customer last paid on average 45 days — they're getting slower" or "Their sales are down 30% vs last year in Q3" are insights that change the conversation from a routine call to a strategic account review. The statistics panel is always one click away from the customer record — make it a standard part of the sales team's daily routine.
Business Central integrates natively with Microsoft Teams — allowing users to view, share, and collaborate on Business Central records without leaving their Teams workspace.
Business Central app for Teams (installed from Teams App Store): Search for Business Central records directly from Teams chat. Share a Business Central record card (customer, order, invoice) into a Teams channel or chat. The shared card shows key record details (status, amounts, dates) and links to open the full record in Business Central. Colleagues without a Business Central licence can see the card details but cannot edit the record.
Contact sync: Customer and vendor contacts in Business Central can be synced to Microsoft 365 contacts — making them available in Teams, Outlook, and the phone app.
Notifications in Teams: Power Automate flows can send Business Central alerts to Teams channels: "Sales order #SO-0012345 has been approved" posted to the Sales Operations channel. "Customer ACME Corp's credit limit is 90% utilised" sent to the Credit Control channel. "Purchase order #PO-567 is overdue for receipt" sent to the Warehouse team channel.
Business Central app for Teams (installed from Teams App Store): Search for Business Central records directly from Teams chat. Share a Business Central record card (customer, order, invoice) into a Teams channel or chat. The shared card shows key record details (status, amounts, dates) and links to open the full record in Business Central. Colleagues without a Business Central licence can see the card details but cannot edit the record.
Contact sync: Customer and vendor contacts in Business Central can be synced to Microsoft 365 contacts — making them available in Teams, Outlook, and the phone app.
Notifications in Teams: Power Automate flows can send Business Central alerts to Teams channels: "Sales order #SO-0012345 has been approved" posted to the Sales Operations channel. "Customer ACME Corp's credit limit is 90% utilised" sent to the Credit Control channel. "Purchase order #PO-567 is overdue for receipt" sent to the Warehouse team channel.
💡 Pro Tip: The record-sharing feature in Teams is particularly powerful for approval workflows. Instead of "approve this in Business Central by clicking a link in an email," a manager receives a Teams message with the full record card visible inline — amount, vendor, description, approver notes — and can approve or comment directly in Teams. This reduces approval turnaround time from hours to minutes for busy managers who live in Teams.
Blanket Orders in Business Central represent long-term supply agreements — a commitment to purchase or sell a total quantity of items over a period, fulfilled through multiple individual orders drawn against the blanket.
Blanket Purchase Order example: Company agrees with Supplier X: "We will buy 10,000 units of Item A during 2024 at Rs.500 each." A Blanket Purchase Order is created for 10,000 units. Throughout the year, individual Purchase Orders are created ("Make Order") referencing the Blanket — each for the immediate delivery quantity. The Blanket tracks: Total committed quantity (10,000), Quantity ordered to date (running total), Quantity remaining to be ordered.
Blanket Sales Order example: Long-term customer commits to buy 5,000 units per quarter. A Blanket Sales Order locks in the pricing and quantity commitment. Monthly Sales Orders are created from the Blanket for the actual delivery. The customer sees consistent pricing throughout the contract period.
Benefits of Blanket Orders: Pricing is locked for the contract period — protects against supplier price increases. Commitment tracking — both parties know the total obligation. Planning input — MRP can use Blanket Order commitments in demand calculations.
Blanket Purchase Order example: Company agrees with Supplier X: "We will buy 10,000 units of Item A during 2024 at Rs.500 each." A Blanket Purchase Order is created for 10,000 units. Throughout the year, individual Purchase Orders are created ("Make Order") referencing the Blanket — each for the immediate delivery quantity. The Blanket tracks: Total committed quantity (10,000), Quantity ordered to date (running total), Quantity remaining to be ordered.
Blanket Sales Order example: Long-term customer commits to buy 5,000 units per quarter. A Blanket Sales Order locks in the pricing and quantity commitment. Monthly Sales Orders are created from the Blanket for the actual delivery. The customer sees consistent pricing throughout the contract period.
Benefits of Blanket Orders: Pricing is locked for the contract period — protects against supplier price increases. Commitment tracking — both parties know the total obligation. Planning input — MRP can use Blanket Order commitments in demand calculations.
💡 Pro Tip: Blanket Orders are frequently required in manufacturing and distribution but are easily confused with standard orders during requirements gathering. Ask clients: "Do you have any long-term supply agreements where you commit to buy a fixed total quantity or value over a year?" If yes, that is a Blanket Order requirement. Without Blanket Orders, these agreements are managed in spreadsheets alongside Business Central — exactly the kind of process gap that leads to data quality problems.
Document Sending Profiles in Business Central define how posted business documents (sales invoices, statements, reminders) are delivered to customers — by email, print, PDF, or electronic formats — enabling automated document distribution.
Document Sending Profile options: Print: Generate a print-ready PDF. Email (PDF Attachment): Send the document as a PDF attachment via email (using the customer's email address from their card). Email (Body): Embed the document content in the email body. Electronic Document (EDI): Send in a structured electronic format (e.g., PEPPOL, UN/EDIFACT) for customers requiring electronic invoicing. Disk (PDF): Save to a folder on the server. Combined: Multiple methods simultaneously (e.g., Email AND Print AND Electronic Document).
Assignment: A default Document Sending Profile is set in Company Information. Individual customers or vendors can have their own Document Sending Profile — overriding the company default. E.g., Enterprise customers require PEPPOL e-invoicing; SMB customers receive email PDF; government clients require a specific XML format.
Document Sending Profile options: Print: Generate a print-ready PDF. Email (PDF Attachment): Send the document as a PDF attachment via email (using the customer's email address from their card). Email (Body): Embed the document content in the email body. Electronic Document (EDI): Send in a structured electronic format (e.g., PEPPOL, UN/EDIFACT) for customers requiring electronic invoicing. Disk (PDF): Save to a folder on the server. Combined: Multiple methods simultaneously (e.g., Email AND Print AND Electronic Document).
Assignment: A default Document Sending Profile is set in Company Information. Individual customers or vendors can have their own Document Sending Profile — overriding the company default. E.g., Enterprise customers require PEPPOL e-invoicing; SMB customers receive email PDF; government clients require a specific XML format.
💡 Pro Tip: Document Sending Profile configuration is one of the last steps before go-live but causes the most visible user complaints if missed. If profiles are not configured, users must manually select the sending method every time they post a document. Invest 2-3 hours defining the sending profile requirements: "For each customer tier, how should invoices be sent?" Configure the profiles, assign them, and test with 10 real customer email addresses in the UAT sandbox to verify delivery.
Business Central includes specific capabilities to help organisations comply with GDPR (General Data Protection Regulation) requirements for the personal data they hold about customers, vendors, and employees.
Data Subject Request handling: Business Central → Data Subject (under Privacy menu). Search for all records containing a specific person's data across the system. Export all data about the person as a report (Right of Access / SAR response). Mark individual records as "Blocked" (prevents new transactions with the person while historical data is retained). Delete the person's personal data where legally permissible (Right to Erasure) — Business Central validates that no active transactions depend on the record before deletion.
Data Classification: Each table and field in Business Central can be tagged with a Data Classification: Personal, Sensitive, Company Confidential, Unclassified. Run the Data Classification Report to see all "Personal" data fields across the system — supporting GDPR Data Mapping (ROPA documentation).
Data Retention Policies: Business Central → Data Retention Policies: Define how long specific data types are retained before archiving or deletion. E.g., Sales quotes: 2 years. Closed purchase orders: 7 years. Log entries: 90 days.
Data Subject Request handling: Business Central → Data Subject (under Privacy menu). Search for all records containing a specific person's data across the system. Export all data about the person as a report (Right of Access / SAR response). Mark individual records as "Blocked" (prevents new transactions with the person while historical data is retained). Delete the person's personal data where legally permissible (Right to Erasure) — Business Central validates that no active transactions depend on the record before deletion.
Data Classification: Each table and field in Business Central can be tagged with a Data Classification: Personal, Sensitive, Company Confidential, Unclassified. Run the Data Classification Report to see all "Personal" data fields across the system — supporting GDPR Data Mapping (ROPA documentation).
Data Retention Policies: Business Central → Data Retention Policies: Define how long specific data types are retained before archiving or deletion. E.g., Sales quotes: 2 years. Closed purchase orders: 7 years. Log entries: 90 days.
💡 Pro Tip: GDPR compliance in Business Central requires both system configuration AND process documentation. The system provides tools for SAR requests and data deletion, but the client's GDPR processes (who handles SARs, what is the response SLA, which data is retained under which legal basis) must be documented separately. Always recommend that clients appoint a GDPR lead and run a data mapping exercise alongside the Business Central implementation — the system configuration is only one part of GDPR compliance.
Business Central's Resources module provides basic resource management for project-based companies — tracking billable hours, costs, and revenue for people and equipment used on Jobs (projects).
Resource setup: Resource Card: Name, Type (Person or Machine), Base Unit of Measure (Hours), Unit Cost (internal cost per hour), Unit Price (billing rate per hour). Resource Group: Group related resources (e.g., "Senior Consultants" resource group with all senior-level people). Resource skill codes (simple skills tagging).
Resource usage on Jobs: Job Planning Lines (budget): Specify Resource, Hours, Unit Cost, Unit Price for each job task. Resource usage is planned at the line level. Job Journals (actuals): Post actual resource time against jobs. Time can be submitted via timesheet or directly in Job Journals. Billing: Job Planning Lines generate sales invoice lines when marked as billable.
Resource capacity planning: Resource Availability view: Shows each resource's total capacity vs. allocated hours per period. Simple — not as sophisticated as D365 Project Operations' Schedule Board. Best for: small teams (5-20 people) with simple project structures.
Resource setup: Resource Card: Name, Type (Person or Machine), Base Unit of Measure (Hours), Unit Cost (internal cost per hour), Unit Price (billing rate per hour). Resource Group: Group related resources (e.g., "Senior Consultants" resource group with all senior-level people). Resource skill codes (simple skills tagging).
Resource usage on Jobs: Job Planning Lines (budget): Specify Resource, Hours, Unit Cost, Unit Price for each job task. Resource usage is planned at the line level. Job Journals (actuals): Post actual resource time against jobs. Time can be submitted via timesheet or directly in Job Journals. Billing: Job Planning Lines generate sales invoice lines when marked as billable.
Resource capacity planning: Resource Availability view: Shows each resource's total capacity vs. allocated hours per period. Simple — not as sophisticated as D365 Project Operations' Schedule Board. Best for: small teams (5-20 people) with simple project structures.
💡 Pro Tip: Business Central Resources/Jobs is the right tool for SMB professional services firms with simple project needs (time tracking + billing) and fewer than 30 billable staff. For larger, more complex firms (50+ billable staff, complex resource scheduling, revenue recognition requirements), D365 Project Operations is the appropriate solution. During requirements, always ask "How many billable people do you have? How complex is your project billing?" to determine the right platform.
Understanding common post-go-live support issues helps consultants proactively prevent them and prepare support teams for what to expect:
1. Posting errors ("Posting Group not found"): A new customer, vendor, or item combination uses a Posting Group combination that was not set up in the General Posting Setup. Prevention: Comprehensive testing of all posting group combinations in UAT. Post-live: Add the missing combination immediately.
2. Incorrect aging reports (unapplied payments): Payments posted without being applied to specific invoices. Both the payment and the invoice show as open. Prevention: Train users to apply payments at posting time. Configure the payment application workflow. Post-live: Run "Apply Customer Entries" batch job weekly.
3. Inventory valuation discrepancies: Inventory G/L balance does not match the Inventory Valuation Report. Usually caused by: "Adjust Cost" job not running, or manual G/L postings to inventory accounts. Prevention: Configure Job Queue for daily "Adjust Cost" run. Restrict direct G/L posting to inventory accounts.
4. Number Series conflicts: Two users create the same document number simultaneously. Prevention: Use system-assigned number series (no Manual Nos.). Post-live: Renumber the conflicting document.
1. Posting errors ("Posting Group not found"): A new customer, vendor, or item combination uses a Posting Group combination that was not set up in the General Posting Setup. Prevention: Comprehensive testing of all posting group combinations in UAT. Post-live: Add the missing combination immediately.
2. Incorrect aging reports (unapplied payments): Payments posted without being applied to specific invoices. Both the payment and the invoice show as open. Prevention: Train users to apply payments at posting time. Configure the payment application workflow. Post-live: Run "Apply Customer Entries" batch job weekly.
3. Inventory valuation discrepancies: Inventory G/L balance does not match the Inventory Valuation Report. Usually caused by: "Adjust Cost" job not running, or manual G/L postings to inventory accounts. Prevention: Configure Job Queue for daily "Adjust Cost" run. Restrict direct G/L posting to inventory accounts.
4. Number Series conflicts: Two users create the same document number simultaneously. Prevention: Use system-assigned number series (no Manual Nos.). Post-live: Renumber the conflicting document.
💡 Pro Tip: Establish a "Hypercare" support process for the first 4 weeks after go-live: daily 30-minute support call between the consultant and the Finance team lead. Most Business Central go-live issues occur in the first 2 weeks — many are user education issues, not system problems. A daily touchpoint resolves these quickly before they escalate into formal complaints or data quality crises.
Questions 61–70 of 75
Business Central supports multiple languages — allowing users in different countries to use the same Business Central environment in their preferred language without separate environments.
How multi-language works in Business Central: Each user can set their own language preference in their User Settings (profile). The interface labels, field names, error messages, and report headings are displayed in the user's selected language. Data values entered by users (customer names, product descriptions, notes) are stored as entered — not automatically translated.
Available languages: Business Central supports 40+ languages including English, Hindi, Tamil, German, French, Spanish, Arabic, Japanese, Chinese (Simplified), Dutch, Italian, and many more. Language packs are installed as extensions from AppSource.
Document language (for customer-facing documents): Sales invoices and other documents can be printed in the customer's preferred language (set on the Customer Card — Language Code field). Standard report objects respect this setting — an invoice to a German customer prints in German even if the user's interface is in English.
How multi-language works in Business Central: Each user can set their own language preference in their User Settings (profile). The interface labels, field names, error messages, and report headings are displayed in the user's selected language. Data values entered by users (customer names, product descriptions, notes) are stored as entered — not automatically translated.
Available languages: Business Central supports 40+ languages including English, Hindi, Tamil, German, French, Spanish, Arabic, Japanese, Chinese (Simplified), Dutch, Italian, and many more. Language packs are installed as extensions from AppSource.
Document language (for customer-facing documents): Sales invoices and other documents can be printed in the customer's preferred language (set on the Customer Card — Language Code field). Standard report objects respect this setting — an invoice to a German customer prints in German even if the user's interface is in English.
💡 Pro Tip: Customer-facing document language is a frequently missed requirement for Indian clients who serve both domestic and international customers. Ask: "Do any of your customers require invoices or statements in a language other than English?" If yes, configure Language Codes on customer cards and verify that the invoice report prints correctly in each required language. Missing this creates manual workarounds at go-live.
Physical Inventory Counting (stock-take) in Business Central is the process of counting actual inventory on hand and reconciling it with the system records — a required periodic control for inventory accuracy.
Physical Inventory process in Business Central:
1. Calculate Inventory (batch job): Creates a Physical Inventory Journal with a line for every item/location/bin combination showing the system expected quantity.
2. Freeze inventory: Ideally, no stock movements during counting (warehouse closed for count day, or cycle count done zone by zone).
3. Count: Warehouse team counts actual quantities and records them on the Physical Inventory Journal (paper count sheets or handheld devices).
4. Enter counted quantities: Enter actual quantities into the Physical Inventory Journal lines.
5. Post: Business Central calculates the difference (Counted Qty - Expected Qty) and posts an inventory adjustment entry. Positive difference = found stock. Negative difference = shortage.
Cycle counting (ongoing): Instead of counting all items at once (full stock-take), count a subset of items continuously. Business Central's "Phys. Inventory by Bins" approach allows counting one bin at a time. A Items (high value): count monthly. B Items: count quarterly. C Items: count annually.
Physical Inventory process in Business Central:
1. Calculate Inventory (batch job): Creates a Physical Inventory Journal with a line for every item/location/bin combination showing the system expected quantity.
2. Freeze inventory: Ideally, no stock movements during counting (warehouse closed for count day, or cycle count done zone by zone).
3. Count: Warehouse team counts actual quantities and records them on the Physical Inventory Journal (paper count sheets or handheld devices).
4. Enter counted quantities: Enter actual quantities into the Physical Inventory Journal lines.
5. Post: Business Central calculates the difference (Counted Qty - Expected Qty) and posts an inventory adjustment entry. Positive difference = found stock. Negative difference = shortage.
Cycle counting (ongoing): Instead of counting all items at once (full stock-take), count a subset of items continuously. Business Central's "Phys. Inventory by Bins" approach allows counting one bin at a time. A Items (high value): count monthly. B Items: count quarterly. C Items: count annually.
💡 Pro Tip: Always configure Item Tracking (lot/serial numbers) for physical inventory counting before the first count — adding tracking after inventory exists in Business Central requires re-entering all inventory with lot/serial numbers, which is extremely disruptive. If item tracking is in scope, confirm it before the first inventory is entered into the system.
E-Documents in Business Central (released in 2023-2024) is the native framework for sending and receiving electronic invoices in structured digital formats — replacing PDF invoices with machine-readable electronic invoices that comply with local and international standards.
Why E-Documents are increasingly required: Government mandates: Many countries are requiring e-invoicing for B2B transactions (India: e-Invoice for GST, Italy: FatturaPA, Germany: XRechnung, France: Factur-X, Mexico: CFDI). PEPPOL network: Pan-European standard for cross-border e-invoicing in the EU and increasingly globally. EDI trading partners: Large buyers (retailers, government agencies) require structured electronic invoices.
Business Central E-Document capabilities: Send electronic invoices in PEPPOL BIS 3.0, OIOUBL (Denmark), PEPPOL BIS 2.1 (older). Receive electronic purchase invoices from suppliers — auto-create purchase invoices in Business Central from received e-invoices. India GST e-Invoice: Generate JSON payload, send to IRP (Invoice Registration Portal), receive IRN (Invoice Reference Number) and QR code, print on the invoice.
E-Document service connectors: Business Central connects to e-invoice service providers (Pagero, Avalara, Archimede) via connector extensions for managed e-invoice routing.
Why E-Documents are increasingly required: Government mandates: Many countries are requiring e-invoicing for B2B transactions (India: e-Invoice for GST, Italy: FatturaPA, Germany: XRechnung, France: Factur-X, Mexico: CFDI). PEPPOL network: Pan-European standard for cross-border e-invoicing in the EU and increasingly globally. EDI trading partners: Large buyers (retailers, government agencies) require structured electronic invoices.
Business Central E-Document capabilities: Send electronic invoices in PEPPOL BIS 3.0, OIOUBL (Denmark), PEPPOL BIS 2.1 (older). Receive electronic purchase invoices from suppliers — auto-create purchase invoices in Business Central from received e-invoices. India GST e-Invoice: Generate JSON payload, send to IRP (Invoice Registration Portal), receive IRN (Invoice Reference Number) and QR code, print on the invoice.
E-Document service connectors: Business Central connects to e-invoice service providers (Pagero, Avalara, Archimede) via connector extensions for managed e-invoice routing.
💡 Pro Tip: For Indian clients with turnover above the GST e-invoicing threshold (currently Rs.10 crore annual turnover), e-Invoice generation is a legal requirement — not an optional feature. Always verify the client's GST turnover during requirements and confirm whether e-Invoice is mandatory. Missing this at go-live causes the client to issue non-compliant invoices, which attracts GST penalties.
Standard Costing in Business Central values inventory at a pre-determined standard cost — rather than actual purchase cost. This method provides consistent product costing for management reporting and simplifies variance analysis in manufacturing environments.
How Standard Cost works: An item's "Unit Cost" is set to the Standard Cost (set manually or via a cost calculation). When the item is received from a supplier at actual cost, Business Central: Credits the inventory at standard cost. Debits cost of goods at standard cost. Posts any difference (actual cost - standard cost) as a Purchase Price Variance to a designated variance G/L account.
Standard Cost Worksheet: Manufacturing companies run a periodic (typically annual) standard cost revaluation. The Standard Cost Worksheet calculates proposed new standard costs based on: Material cost (current purchase prices), Labour cost (work centre rates × routing time), Overhead cost (overhead absorption rates). The worksheet is reviewed and approved. "Implement Standard Cost Changes" posts an inventory revaluation adjusting all inventory to the new standard — the difference posts to an Inventory Revaluation account.
Variance reporting: Purchase Price Variance (actual vs standard material cost), Manufacturing Overhead Variance, Labour Efficiency Variance.
How Standard Cost works: An item's "Unit Cost" is set to the Standard Cost (set manually or via a cost calculation). When the item is received from a supplier at actual cost, Business Central: Credits the inventory at standard cost. Debits cost of goods at standard cost. Posts any difference (actual cost - standard cost) as a Purchase Price Variance to a designated variance G/L account.
Standard Cost Worksheet: Manufacturing companies run a periodic (typically annual) standard cost revaluation. The Standard Cost Worksheet calculates proposed new standard costs based on: Material cost (current purchase prices), Labour cost (work centre rates × routing time), Overhead cost (overhead absorption rates). The worksheet is reviewed and approved. "Implement Standard Cost Changes" posts an inventory revaluation adjusting all inventory to the new standard — the difference posts to an Inventory Revaluation account.
Variance reporting: Purchase Price Variance (actual vs standard material cost), Manufacturing Overhead Variance, Labour Efficiency Variance.
💡 Pro Tip: Standard cost is most appropriate for manufacturing companies with stable, repeatable production processes. For distributors buying and selling volatile-price commodities (food, raw materials, metals), standard cost creates large variances that are difficult to explain and manage. Confirm the costing method with both the CFO and Operations Director — they often have different opinions on what serves them best.
Business Central includes a deep Power BI integration that brings advanced analytics directly into the ERP interface — giving users rich visual dashboards without leaving Business Central.
Business Central Power BI connector: Power BI Desktop connects to Business Central via the Business Central connector or OData web services. All Business Central tables and queries are exposed as data sources. Real-time or scheduled refresh options.
Pre-built Power BI apps for Business Central: Microsoft provides a set of Business Central Power BI apps available on AppSource (free): Finance App: Revenue trends, expense analysis, cash position, budget vs actuals, aged receivables/payables. Sales App: Sales by customer, by item, by salesperson, monthly trends, order pipeline. Purchasing App: Purchases by vendor, by item, spend analysis, overdue payables.
Embedding Power BI in Business Central: Power BI reports can be embedded directly on Business Central Role Centres and pages. Business Manager Role Centre: Embed the Finance Power BI report so the CFO sees analytics on their home page. Customer Card: Embed a customer-specific Power BI chart showing their sales history.
Self-service analytics: Business users can create their own Power BI reports connecting to their Business Central data — without requiring IT intervention.
Business Central Power BI connector: Power BI Desktop connects to Business Central via the Business Central connector or OData web services. All Business Central tables and queries are exposed as data sources. Real-time or scheduled refresh options.
Pre-built Power BI apps for Business Central: Microsoft provides a set of Business Central Power BI apps available on AppSource (free): Finance App: Revenue trends, expense analysis, cash position, budget vs actuals, aged receivables/payables. Sales App: Sales by customer, by item, by salesperson, monthly trends, order pipeline. Purchasing App: Purchases by vendor, by item, spend analysis, overdue payables.
Embedding Power BI in Business Central: Power BI reports can be embedded directly on Business Central Role Centres and pages. Business Manager Role Centre: Embed the Finance Power BI report so the CFO sees analytics on their home page. Customer Card: Embed a customer-specific Power BI chart showing their sales history.
Self-service analytics: Business users can create their own Power BI reports connecting to their Business Central data — without requiring IT intervention.
💡 Pro Tip: The pre-built Business Central Power BI apps from AppSource are often not deployed during implementation — they require a separate "Deploy Power BI Reports" step that gets overlooked in the go-live rush. Add this explicitly to the go-live checklist. These pre-built apps deliver 80% of the analytics value that clients expect from Business Central reporting — and they are free to deploy.
Business Central includes a basic CRM module (Marketing & Sales in the navigation) — providing contact management, interaction logging, and opportunity tracking for businesses that do not require a dedicated CRM system like D365 Sales.
Contact management features: Contacts: A separate entity from Customers — can represent prospects (not yet customers), multiple contacts at one company, non-customer relationships (journalists, investors, partners). Contact types: Company or Person. A Person contact can be linked to a Company contact. Contact classification: Salesperson assignment, contact category codes (prospect, suspect, active customer).
Interaction logging: Record all interactions with a contact: phone calls, emails, meetings, letters. Link documents (sales quotes sent, emails received) to the contact. View the full interaction history on the contact card.
Segmentation: Create contact segments based on criteria (location, industry, contact classification). Send marketing emails or letters to a segment. Track who received which campaign.
Opportunity management: Basic sales opportunity tracking linked to contacts. Probability, Close Date, Estimated Value. Not as sophisticated as D365 Sales but sufficient for small sales teams.
Contact management features: Contacts: A separate entity from Customers — can represent prospects (not yet customers), multiple contacts at one company, non-customer relationships (journalists, investors, partners). Contact types: Company or Person. A Person contact can be linked to a Company contact. Contact classification: Salesperson assignment, contact category codes (prospect, suspect, active customer).
Interaction logging: Record all interactions with a contact: phone calls, emails, meetings, letters. Link documents (sales quotes sent, emails received) to the contact. View the full interaction history on the contact card.
Segmentation: Create contact segments based on criteria (location, industry, contact classification). Send marketing emails or letters to a segment. Track who received which campaign.
Opportunity management: Basic sales opportunity tracking linked to contacts. Probability, Close Date, Estimated Value. Not as sophisticated as D365 Sales but sufficient for small sales teams.
💡 Pro Tip: Business Central's built-in CRM is suitable for small businesses (1-5 salespeople) with simple sales processes. For larger sales teams, complex opportunity management, or sales pipeline forecasting, D365 Sales is the right solution. During requirements, ask: "How many salespeople do you have? How do you currently track deals?" If the answer involves a dedicated CRM or complex sales processes, recommend D365 Sales integration rather than the built-in BC CRM.
Migrating from QuickBooks or Tally to Business Central is one of the most common SMB implementation scenarios in India and globally. Understanding the migration path sets realistic expectations.
Key differences that require process change: QuickBooks/Tally: Simple, single-entity, cash/invoice accounting. Business Central: Multi-entity capable, full double-entry accounting, much more detailed transaction structure. Posting Groups: No equivalent in QuickBooks/Tally — this is a new concept requiring training. Dimensions: Tally uses cost centres/profit centres which map to Business Central Dimensions — configuration is different. Inventory Costing: QuickBooks uses FIFO or Average. Business Central offers more methods — confirm the correct method in requirements.
Data migration from QuickBooks: Export: Customer list, Vendor list, Chart of Accounts, Item list from QuickBooks as CSV/Excel. Transform: Map QuickBooks account names to Business Central account numbers and posting groups. Import via RapidStart: Use Configuration Packages to import master data. Opening balances: Export trial balance from QuickBooks as at migration date. Post as opening balance journal in Business Central.
Tally to Business Central: Same approach — export from Tally via their data export utility or third-party tools (Intellect, DataMigrationTool). Tally's ledger structure maps to Business Central's CoA.
Key differences that require process change: QuickBooks/Tally: Simple, single-entity, cash/invoice accounting. Business Central: Multi-entity capable, full double-entry accounting, much more detailed transaction structure. Posting Groups: No equivalent in QuickBooks/Tally — this is a new concept requiring training. Dimensions: Tally uses cost centres/profit centres which map to Business Central Dimensions — configuration is different. Inventory Costing: QuickBooks uses FIFO or Average. Business Central offers more methods — confirm the correct method in requirements.
Data migration from QuickBooks: Export: Customer list, Vendor list, Chart of Accounts, Item list from QuickBooks as CSV/Excel. Transform: Map QuickBooks account names to Business Central account numbers and posting groups. Import via RapidStart: Use Configuration Packages to import master data. Opening balances: Export trial balance from QuickBooks as at migration date. Post as opening balance journal in Business Central.
Tally to Business Central: Same approach — export from Tally via their data export utility or third-party tools (Intellect, DataMigrationTool). Tally's ledger structure maps to Business Central's CoA.
💡 Pro Tip: The most common resistance in QuickBooks/Tally to Business Central migrations: "Business Central is too complicated." This perception almost always comes from training on the full interface rather than role-specific features. Show a Finance manager only the Accounts Receivable Role Centre — the interface becomes as simple as any other system. The secret to adoption is role-specific training, not a comprehensive system overview.
The first discovery workshop for a Business Central implementation must cover all dimensions of the client's financial and operational requirements:
Financial management questions: What accounting standards do you follow? (IFRS, Ind AS, local GAAP). What is your financial year end? Do you have multiple companies or legal entities? What currencies do you transact in? How many bank accounts do you have?
Operations questions: Do you buy and sell physical goods? Do you manufacture? Do you have multiple warehouses or locations? How do you currently manage inventory — quantity and valuation? Do you require lot or serial number traceability?
People and process questions: How many users will use Business Central? What are their roles? What does your month-end close process look like today? How long does it take?
Integration questions: What other systems need to connect to Business Central? (Payroll, CRM, eCommerce, logistics, banking). Do you require electronic invoicing (e-Invoice for GST)?
Current system questions: What system are you replacing and why? What do you like about it? What frustrates you?
Financial management questions: What accounting standards do you follow? (IFRS, Ind AS, local GAAP). What is your financial year end? Do you have multiple companies or legal entities? What currencies do you transact in? How many bank accounts do you have?
Operations questions: Do you buy and sell physical goods? Do you manufacture? Do you have multiple warehouses or locations? How do you currently manage inventory — quantity and valuation? Do you require lot or serial number traceability?
People and process questions: How many users will use Business Central? What are their roles? What does your month-end close process look like today? How long does it take?
Integration questions: What other systems need to connect to Business Central? (Payroll, CRM, eCommerce, logistics, banking). Do you require electronic invoicing (e-Invoice for GST)?
Current system questions: What system are you replacing and why? What do you like about it? What frustrates you?
💡 Pro Tip: The single most revealing discovery question for Business Central: "Walk me through your last month-end close — what did you do, in what order, how long did each step take, and where did you get stuck?" This narrative reveals: the full closing process, current system limitations, manual workarounds, and the specific pain points that Business Central must solve. Record this walkthrough and use it to build the Month-End Close Checklist for the new system.
Many organisations in India and globally still run Microsoft Dynamics NAV — the predecessor to Business Central — and are evaluating or planning an upgrade. Understanding this relationship is essential for consultants working with existing Microsoft ERP clients.
The NAV to Business Central evolution: Dynamics NAV (Navision) → Dynamics 365 Business Central: The product was rebranded and moved to the cloud. Business Central is effectively NAV in the cloud — the data model, core functionality, and business logic are largely the same. NAV consultants can transition their skills to Business Central with relatively moderate retraining (mainly on cloud architecture, Power Platform integration, and AL extension development).
NAV versions still in use: NAV 2009 R2 (very old, Windows client only), NAV 2013, NAV 2015, NAV 2016, NAV 2017, NAV 2018 (last pure NAV version before Business Central). All versions are approaching or past end of mainstream support — driving upgrade urgency.
Upgrade approach: Most common: Fresh Business Central implementation with data migration from NAV (cleaner, best practice). Alternative: Technical upgrade (NAV to BC Online via Cloud Migration App — preserves customisations but requires AL extension rewrite). Customisations: NAV C/AL code must be rewritten as Business Central AL extensions — this is the most complex and expensive part of any NAV upgrade.
The NAV to Business Central evolution: Dynamics NAV (Navision) → Dynamics 365 Business Central: The product was rebranded and moved to the cloud. Business Central is effectively NAV in the cloud — the data model, core functionality, and business logic are largely the same. NAV consultants can transition their skills to Business Central with relatively moderate retraining (mainly on cloud architecture, Power Platform integration, and AL extension development).
NAV versions still in use: NAV 2009 R2 (very old, Windows client only), NAV 2013, NAV 2015, NAV 2016, NAV 2017, NAV 2018 (last pure NAV version before Business Central). All versions are approaching or past end of mainstream support — driving upgrade urgency.
Upgrade approach: Most common: Fresh Business Central implementation with data migration from NAV (cleaner, best practice). Alternative: Technical upgrade (NAV to BC Online via Cloud Migration App — preserves customisations but requires AL extension rewrite). Customisations: NAV C/AL code must be rewritten as Business Central AL extensions — this is the most complex and expensive part of any NAV upgrade.
💡 Pro Tip: When meeting a potential NAV upgrade client, ask: "How many custom modifications do you have in NAV? Do you use third-party ISV add-ons?" The answers determine upgrade complexity and cost. A heavily customised NAV with 50+ custom objects and 5 ISV solutions will cost 3-5x more to upgrade than a lightly customised NAV. This assessment drives the project estimate — and separates consultants who understand the technical reality from those who just say "it's a standard upgrade."
A structured period close process in Business Central ensures financial reporting accuracy and audit readiness. Key best practices from real implementations:
Cut-off management: Establish a hard cut-off for each period — e.g., all purchase invoices for March must be posted by April 3rd. Configure period lock: Administration → Accounting Periods → Set the closed period flag on March after the cut-off date. Users who try to post to a closed period receive a warning (or error if hard-locked). Finance Managers only can override the lock with explicit authorisation.
Accruals management: Create a standard Recurring Journal batch for monthly accruals (rent, insurance, subscriptions, audit fees, employee benefits). Post accruals on the last day of the month. Reverse on the 1st of the next month (Reversing Entry flag on the journal line).
Foreign currency revaluation: Run "Adjust Exchange Rates" batch job at month-end. This revalues open foreign currency receivables, payables, and bank balances at the closing exchange rate. The unrealised gain/loss posts to the designated FX account.
Year-end close specific: Run "Close Income Statement" — transfers P&L net income to Retained Earnings. Approve the statutory accounts before running this — it cannot be reversed.
Cut-off management: Establish a hard cut-off for each period — e.g., all purchase invoices for March must be posted by April 3rd. Configure period lock: Administration → Accounting Periods → Set the closed period flag on March after the cut-off date. Users who try to post to a closed period receive a warning (or error if hard-locked). Finance Managers only can override the lock with explicit authorisation.
Accruals management: Create a standard Recurring Journal batch for monthly accruals (rent, insurance, subscriptions, audit fees, employee benefits). Post accruals on the last day of the month. Reverse on the 1st of the next month (Reversing Entry flag on the journal line).
Foreign currency revaluation: Run "Adjust Exchange Rates" batch job at month-end. This revalues open foreign currency receivables, payables, and bank balances at the closing exchange rate. The unrealised gain/loss posts to the designated FX account.
Year-end close specific: Run "Close Income Statement" — transfers P&L net income to Retained Earnings. Approve the statutory accounts before running this — it cannot be reversed.
💡 Pro Tip: Build the Year-End Close into the Business Central implementation timeline explicitly — most go-lives happen mid-year, and the first year-end is 3-12 months after go-live. Schedule a "Year-End Close Training and Simulation" session 2 months before the client's first year-end. Running through the year-end process in a sandbox with real data before doing it live for the first time prevents costly errors in what is the most scrutinised financial close of the year.
Questions 71–75 of 75
Microsoft recommends the Microsoft FastTrack methodology for Business Central implementations — a structured, partner-led approach that defines phases, deliverables, and quality gates to ensure successful deployments.
FastTrack for Business Central key phases: Initiate: Project kick-off, team onboarding, environment setup, initial data assessment. Implement: Configure Business Central to fit the business requirements. Data migration execution. Integration setup. Test: System testing, user acceptance testing, performance testing. Deploy: Go-live preparation, cutover, production deployment. Operate: Hypercare support period, transition to ongoing support.
Sure Step (legacy methodology): Microsoft's previous implementation methodology — still used by some partners. More prescriptive document-based approach. Phases: Diagnostic, Analysis, Design, Development, Deployment, Operation. Less aligned with Agile practices than FastTrack.
Agile vs Waterfall: Business Central implementations for SMBs typically use a hybrid approach: Design is Waterfall (requirements upfront), Build uses iterative sprints (configure module by module), Test uses sprint-based cycles, Go-live is a fixed milestone.
FastTrack for Business Central key phases: Initiate: Project kick-off, team onboarding, environment setup, initial data assessment. Implement: Configure Business Central to fit the business requirements. Data migration execution. Integration setup. Test: System testing, user acceptance testing, performance testing. Deploy: Go-live preparation, cutover, production deployment. Operate: Hypercare support period, transition to ongoing support.
Sure Step (legacy methodology): Microsoft's previous implementation methodology — still used by some partners. More prescriptive document-based approach. Phases: Diagnostic, Analysis, Design, Development, Deployment, Operation. Less aligned with Agile practices than FastTrack.
Agile vs Waterfall: Business Central implementations for SMBs typically use a hybrid approach: Design is Waterfall (requirements upfront), Build uses iterative sprints (configure module by module), Test uses sprint-based cycles, Go-live is a fixed milestone.
💡 Pro Tip: The most valuable methodological practice for Business Central SMB implementations: configuration-based iterative sprints with end-user validation. Configure Finance in Sprint 1 (weeks 1-3), validate with the Finance team in week 3, configure Sales & Purchasing in Sprint 2, validate in week 5. This rhythm prevents the "big bang UAT" failure mode where everything is configured at once, tested at the end, and major issues are discovered with no time to fix them before go-live.
AL Extensions are the modern Business Central customisation framework — replacing the legacy C/AL (Client/Server Application Language) customisation approach from Dynamics NAV with a non-invasive, upgrade-safe extension model.
AL Extension architecture: Extensions do NOT modify Business Central base application code. They extend it by: Adding new fields to existing tables (Table Extension), Extending existing pages with new fields and actions (Page Extension), Creating entirely new tables and pages, Adding new report layouts, Writing event subscribers that execute when standard events fire (e.g., "On After Post Sales Invoice"). The base application runs unchanged — extensions layer on top. Microsoft can update the base application without breaking extensions.
Development environment: Visual Studio Code with the AL Language extension. Git for version control. Test-driven development with AL Test Toolkit. Deploy to Business Central via the Development endpoint or through the Extension Management page.
AppSource publishing: Extensions that meet Microsoft's quality criteria can be published to Microsoft AppSource — making them available to all Business Central customers worldwide.
AL Extension architecture: Extensions do NOT modify Business Central base application code. They extend it by: Adding new fields to existing tables (Table Extension), Extending existing pages with new fields and actions (Page Extension), Creating entirely new tables and pages, Adding new report layouts, Writing event subscribers that execute when standard events fire (e.g., "On After Post Sales Invoice"). The base application runs unchanged — extensions layer on top. Microsoft can update the base application without breaking extensions.
Development environment: Visual Studio Code with the AL Language extension. Git for version control. Test-driven development with AL Test Toolkit. Deploy to Business Central via the Development endpoint or through the Extension Management page.
AppSource publishing: Extensions that meet Microsoft's quality criteria can be published to Microsoft AppSource — making them available to all Business Central customers worldwide.
💡 Pro Tip: When a client request cannot be met by configuration alone, always evaluate AppSource first before recommending custom AL development. A certified AppSource extension is already developed, tested, and maintained by a specialist ISV — typically 10x cheaper and faster to implement than bespoke development. Only commission custom AL development when: the requirement is genuinely unique to the client, or no AppSource solution covers the gap adequately.
Business Central uses a subscription-based pricing model with per-user monthly fees — important for project scoping and Total Cost of Ownership analysis.
Standard pricing tiers (approximate, verify current rates with Microsoft): Essentials: $70/user/month (includes full financial management, supply chain, CRM, projects, basic service). Premium: $100/user/month (adds Manufacturing and Service Management). Team Member: $8/user/month (limited access — reading/limited editing only). External Accountant: Free (read-only for the client's accountant).
Add-ons and capacity: Additional storage (above the included 80GB): Charged per GB/month. Additional environments (above the 3+3 production/sandbox default): Charged per environment/month. Embed licences: ISVs who embed Business Central in their vertical SaaS products use special Embed licensing — typically lower cost but restricted to the ISV's specific industry solution.
Where to find current pricing: Microsoft's official pricing page (dynamics.microsoft.com). Partner Centre (for CSP pricing — which can be lower than list for Microsoft partners). Volume licensing agreements (for organisations with existing Microsoft contracts).
Standard pricing tiers (approximate, verify current rates with Microsoft): Essentials: $70/user/month (includes full financial management, supply chain, CRM, projects, basic service). Premium: $100/user/month (adds Manufacturing and Service Management). Team Member: $8/user/month (limited access — reading/limited editing only). External Accountant: Free (read-only for the client's accountant).
Add-ons and capacity: Additional storage (above the included 80GB): Charged per GB/month. Additional environments (above the 3+3 production/sandbox default): Charged per environment/month. Embed licences: ISVs who embed Business Central in their vertical SaaS products use special Embed licensing — typically lower cost but restricted to the ISV's specific industry solution.
Where to find current pricing: Microsoft's official pricing page (dynamics.microsoft.com). Partner Centre (for CSP pricing — which can be lower than list for Microsoft partners). Volume licensing agreements (for organisations with existing Microsoft contracts).
💡 Pro Tip: Business Central licensing through the Cloud Solution Provider (CSP) channel (most Microsoft partners are CSPs) allows partners to purchase licences at a discount and resell. This can make Business Central significantly cheaper than the listed price for clients who purchase through a Microsoft partner. Always check whether the client has an existing Microsoft EA or CSP arrangement before quoting list price — it may not be the price they will actually pay.
A realistic project team composition and timeline for a standard Business Central implementation (SMB, 20-100 users, Essentials licence, 3-4 modules):
Consultant team (implementation partner): Lead Functional Consultant (1 FTE): Finance, Supply Chain, overall solution design, project management. Finance Specialist / Business Central Accountant (0.5 FTE): G/L setup, posting groups, financial reports, period close. Technical Consultant (0.5 FTE): Extensions, integrations, data migration scripts, report development. Project Manager (0.25 FTE): Governance, risk management, client relationship.
Client team (essential): Executive Sponsor: Decision-making authority, budget owner. Finance Lead (Controller or Finance Manager): Primary owner for financial configuration. Operations Lead: Inventory, purchasing, warehouse configuration. IT Contact: Azure AD, email infrastructure, network access. Super Users (2-4 people): Power users who will train end users and manage the system post go-live.
Typical timeline (standard SMB, Essentials, 50 users): Weeks 1-2: Discovery and solution design. Weeks 3-8: Configuration (Finance, then Supply Chain). Weeks 7-10: Data migration preparation and testing. Weeks 9-12: UAT. Week 12-13: Go-live preparation and cutover. Week 14: Go-live. Weeks 14-18: Hypercare. Total: 14-18 weeks.
Consultant team (implementation partner): Lead Functional Consultant (1 FTE): Finance, Supply Chain, overall solution design, project management. Finance Specialist / Business Central Accountant (0.5 FTE): G/L setup, posting groups, financial reports, period close. Technical Consultant (0.5 FTE): Extensions, integrations, data migration scripts, report development. Project Manager (0.25 FTE): Governance, risk management, client relationship.
Client team (essential): Executive Sponsor: Decision-making authority, budget owner. Finance Lead (Controller or Finance Manager): Primary owner for financial configuration. Operations Lead: Inventory, purchasing, warehouse configuration. IT Contact: Azure AD, email infrastructure, network access. Super Users (2-4 people): Power users who will train end users and manage the system post go-live.
Typical timeline (standard SMB, Essentials, 50 users): Weeks 1-2: Discovery and solution design. Weeks 3-8: Configuration (Finance, then Supply Chain). Weeks 7-10: Data migration preparation and testing. Weeks 9-12: UAT. Week 12-13: Go-live preparation and cutover. Week 14: Go-live. Weeks 14-18: Hypercare. Total: 14-18 weeks.
💡 Pro Tip: The most common cause of Business Central project overruns is an under-resourced client team. If the Finance Manager is 10% available (attending 1 meeting per week), the finance configuration will take 3x longer than planned. In the project kick-off, establish availability expectations clearly: "We need the Finance Lead for 50% time during configuration weeks. This is a critical project success factor." Get written commitment from the sponsor — and flag deviations in the weekly status report.
Preparing for a Business Central functional consultant interview requires demonstrating both platform configuration knowledge and SMB finance/operations domain expertise.
Platform knowledge questions you will likely face: "Walk me through the Purchase-to-Pay process in Business Central from purchase order to vendor payment." "What are Posting Groups and why are they important?" "How does the Dimensions feature work and when would you use it instead of separate G/L accounts?" "What is the difference between Inventory Costing methods FIFO and Average? How would you choose between them?" "How do you migrate data from a legacy system into Business Central?" "What is RapidStart and how does it work?"
Scenario-based questions: "A manufacturing client needs to track production costs by product line — how would you configure this in Business Central?" "A client has 3 warehouses and needs to know inventory levels per location — what do you configure?" "The Finance team cannot reconcile their Accounts Receivable — what are the most likely causes and how would you fix them?"
Business process questions: "What questions would you ask in the first finance discovery workshop?" "How long would a standard Business Central implementation take and what risks would you flag?"
Platform knowledge questions you will likely face: "Walk me through the Purchase-to-Pay process in Business Central from purchase order to vendor payment." "What are Posting Groups and why are they important?" "How does the Dimensions feature work and when would you use it instead of separate G/L accounts?" "What is the difference between Inventory Costing methods FIFO and Average? How would you choose between them?" "How do you migrate data from a legacy system into Business Central?" "What is RapidStart and how does it work?"
Scenario-based questions: "A manufacturing client needs to track production costs by product line — how would you configure this in Business Central?" "A client has 3 warehouses and needs to know inventory levels per location — what do you configure?" "The Finance team cannot reconcile their Accounts Receivable — what are the most likely causes and how would you fix them?"
Business process questions: "What questions would you ask in the first finance discovery workshop?" "How long would a standard Business Central implementation take and what risks would you flag?"
💡 Pro Tip: The most differentiating answer in a Business Central interview is demonstrating knowledge of both the functional configuration AND the accounting principles behind it. Many candidates can describe what Posting Groups do — fewer can explain why they are structured this way (the accounting principle of automatic account determination based on transaction classification). Interviewers test whether you understand the "why" behind the configuration, not just the "how." Prepare to explain the accounting treatment for each major configuration area.
Page 1 of 8