How Microsoft Dynamics 365 Business Central works

Requirement evaluated: Statistical accounts for non-financial KPIs (headcount, square footage for allocations)

For a professional services and distribution company like yours that needs to allocate shared costs (facility rent, IT overhead) across 8 entities using drivers like headcount and square footage, Business Central provides a dedicated Statistical Accounts feature within the GL framework. Your controller creates statistical accounts in the Chart of Accounts, then uses the Statistical Accounts Journal to post non-monetary quantities per period (e.g., 47 employees in the Northeast entity, 12,000 sq ft for the Chicago office) without any debit/credit balancing requirement, since statistical accounts are kept separate from the trial balance and do not appear in standard financial statements. …

Limitations: Statistical account values must be manually entered or imported each period via the Statistical Accounts Journal; Business Central does not auto-populate headcount from ADP or square footage from a facilities system without a custom integration or data import routine, so your controller will need a defined process to r …

Requirement evaluated: Period-close controls that prevent posting to closed periods while allowing adjustments with proper authorization

For a controller at a multi-entity professional services company preparing for audit, Business Central delivers period-close controls through a documented, two-layer posting-date enforcement system. At the company level, an administrator sets 'Allow Posting From' and 'Allow Posting To' dates in General Ledger Setup; <cite index="11-1,11-3">these fields define the allowed posting window, and those posting periods apply to the company and to all users.</cite> When a period needs to be locked for general staff while remaining open for authorized roles such as the controller or CFO, <cite index="15-1,15-2">the administrator can define different posting periods for specific users on the User Setu …

Limitations: The 'authorized adjustment' pathway relies on an administrator manually extending a named user's posting date range in User Setup rather than a formal workflow-gated approval chain; there is no native in-product request-and-approve flow for period reopening, which means the authorization process is controlled through a …

Requirement evaluated: Automated recurring journal entries and templates for standard monthly entries

For a controller running 8 legal entities and a 12-day close, Business Central provides two native, complementary mechanisms within the General Ledger module. First, the Recurring General Journal lets the team define journal lines once, setting a Recurring Method (Fixed, Variable, Balance, or their Reversing equivalents, including Balance by Dimension and Reversing Balance by Dimension) and a date formula in the Recurring Frequency field (for example, '1M' for monthly). After each posting, accounts, dimensions, and dimension values remain on the line so nothing needs to be re-entered; the system advances the posting date automatically per the formula. …

Limitations: Because Business Central runs each legal entity as a separate company, recurring journal setups must be configured independently per entity; there is no single central template library that pushes a recurring journal definition to all 8 companies simultaneously, which adds setup effort for the controller. …

Requirement evaluated: Real-time GL posting; we cannot accept batch-only posting

For a controller currently suffering 12+ day closes driven by manual, batch-level reconciliation in QuickBooks Enterprise, Business Central's default posting architecture is a direct improvement. When a user clicks 'Post' on any purchase invoice, sales invoice, or general journal in Business Central, the system simultaneously updates the vendor's account, the general ledger (G/L), the item ledger entries, and the resource ledger entries in a single atomic action — there is no mandatory 'run batch' step standing between the document and the GL. …

Limitations: One configuration to verify at implementation: for distribution inventory transactions, Business Central offers an 'Automatic Cost Posting' toggle that controls whether inventory value entries hit the GL at the moment of posting or are reconciled later via a manual 'Post Inventory Cost to G/L' batch job. …

Requirement evaluated: Real-time executive dashboard showing consolidated cash position, revenue by segment, and AP/AR aging

For a $180M professional services and distribution company with 8 legal entities moving off QuickBooks Enterprise, Business Central delivers executive dashboard visibility through two complementary layers. The first is the native Role Center: a dashboard with real-time activity tiles showing live key figures including cash flow charts, income statement, and balance sheet, accessible directly from the Business Manager or Accountant home page without leaving the application (Microsoft Learn, 'Accountant experiences in Business Central'). …

Limitations: The out-of-the-box Power BI Finance app connects to one Business Central company at a time; multi-entity consolidated dashboards require either using Business Central's native consolidation company as the data source or manually adding queries per entity in Power BI Desktop, and the ODataV4 API does not natively export …

Requirement evaluated: Self-service report builder; our controller must be able to create custom reports without IT or vendor assistance

For a controller at a multi-entity professional services company trying to escape spreadsheet-driven reporting, Business Central provides two native self-service mechanisms that require no IT, no developer, and no vendor assistance. The first is the Financial Reports feature (formerly Account Schedules): the controller builds custom reports by defining row definitions (mapping G/L accounts or account categories to report rows, with formula-based subtotals) and column definitions (specifying period types, budget comparisons, variance columns, and dimension filters). …

Limitations: Column definitions in Financial Reports are capped at 15 columns per report, which may constrain highly granular multi-period layouts. For interactive visual dashboards and KPI tiles beyond what Financial Reports and Analysis Mode provide, Microsoft's documentation points to the Power BI Finance app, which requires a s …

Requirement evaluated: Real-time executive dashboard showing consolidated cash position, revenue by segment, and AP/AR aging

For a company with 8 legal entities replacing a QuickBooks-plus-spreadsheets consolidation workflow, Business Central offers two complementary mechanisms. First, a native Consolidation module lets the controller set up a dedicated "consolidated company," register each of the 8 legal entities as business units, and run the consolidation batch job (via database link for same-environment entities or API for cross-environment) to transfer GL entries into the consolidated company; the Consolidated Trial Balance and G/L Consolidation Eliminations reports then surface a unified, elimination-adjusted financial view. …

Limitations: The out-of-the-box Power BI Finance app does not natively produce a single consolidated dashboard spanning all 8 entities; it requires either custom Power BI development to merge per-entity datasets or use of the consolidation company (which covers GL balances but not live subledger aging detail). …

Requirement evaluated: Dimensional reporting across entity, department, service line, project, and location simultaneously

For your 8-entity professional services and distribution business, Business Central's native Dimensions framework lets your team tag every transaction at posting time with an unlimited set of named dimensions (entity, department, service line, project, location). Two are promoted as 'Global Dimensions,' stored directly on G/L ledger entries for fast filter access across all reports and batch jobs; up to eight more are configured as 'Shortcut Dimensions,' which appear as visible fields on journal lines and document lines at data entry. …

Limitations: The native Analysis by Dimensions matrix displays only two dimensions simultaneously as rows and columns (with additional dimensions applied as filters rather than display axes), so producing a single formatted statement with all five axes visible at once requires either Financial Reports with dimension filters or Powe …

Requirement evaluated: Automated invoicing with configurable templates per entity/service line

For a $180M company running 8 legal entities, Business Central's architecture directly maps each legal entity to a separate 'Company,' and report layouts are managed on a per-company basis. <cite index="5-14,5-15">When there are multiple companies in the application, layouts are set on a per-company basis, so the same report in one company can have a different layout in another company.</cite> Within each company, the controller creates Word (DOCX) or RDLC invoice layouts via the Report Layouts page, embedding entity-specific logos, addresses, payment terms, and styling. …

Limitations: The buyer's requirement spans two dimensions: per-entity (fully covered through Business Central's company-level layout isolation and number series) and per-service-line (not natively supported: no out-of-the-box mechanism auto-selects a layout based on item category or service type without customization or an AppSourc …

Requirement evaluated: Automated payment application from bank lockbox and ACH receipts

For a company receiving ACH payments and bank lockbox deposits, Business Central's primary mechanism is the Payment Reconciliation Journal (PRJ). A user imports a bank statement file or live bank feed into the PRJ, then triggers the 'Apply Automatically' function. <cite index="3-3,3-4">The task is performed on the Payment Reconciliation Journal page by importing a bank statement file or feed; payments are then applied to open customer or vendor ledger entries based on matches between payment text and entry information.</cite> <cite index="31-3,31-4">Payment application rules are configurable on the Payment Application Rules page, where each rule governs which types of data must match before …

Limitations: BAI2 and NACHA bank lockbox file formats are not supported natively out of the box: the buyer's bank will likely need a custom Data Exchange Definition built during implementation or will require the AMC Banking 365 Fundamentals extension (a separately priced Microsoft add-on) to convert formats. …

Requirement evaluated: Automated invoicing with configurable templates per entity/service line

For an 8-entity professional services and distribution company migrating off QuickBooks Enterprise, Business Central handles this requirement through three interlocking native mechanisms. First, invoice templates (RDLC or Word-based Report Layouts) are assigned on a per-company basis: the Report Layout Selection page scopes each layout to a specific company, so each of your 8 legal entities can carry a distinct invoice template with its own branding, logo, address, and field arrangement, with no cross-entity bleed. …

Limitations: Service-line-level template routing within a single entity is not driven by transaction attributes or a routing rule engine: the mechanism is the customer card, so if the same customer receives invoices from two service lines that require visually distinct templates in the same company context, that differentiation req …

Requirement evaluated: Customer portal for invoice access and online payment

For a professional services and distribution company preparing for audited financials, Business Central's native AR module delivers online payment capability through emailed 'pay-now' links rather than a true self-service portal. When the PayPal Payments Standard extension is enabled, <cite index="11-3,11-4">a link to the payment service is available on sales documents that are sent by email to customers, and customers can use the link to go to the payment service and pay the bill directly from the sales document.</cite> <cite index="10-14,10-15">Business Central can register payments automatically if the company has a Business Merchant account for the PayPal Commerce Platform, and when cust …

Limitations: The base Business Central product covers only emailed pay-now links (PayPal); it does not include a native customer-facing portal where customers can log in, view invoice history, and select invoices for payment. …

Requirement evaluated: Support for iPaaS platforms (Workato or Celigo) for non-native integrations

For a $180M multi-entity business needing to connect Business Central with ADP payroll and Salesforce CRM without native connectors, Business Central provides the integration surface through its REST API v2.0 and OData v4 endpoints, enabled by default for Business Central online. Authentication uses Microsoft Entra ID (Azure AD) OAuth 2.0, including a Service-to-Service client credentials flow designed for headless, unattended integrations. …

Limitations: The Workato connector for Business Central is documented at a marketing level in Workato's connector directory, but its object-level coverage (specific supported triggers and actions for BC vs. Dynamics CRM) …

Requirement evaluated: REST API with documented endpoints for custom integrations

For a multi-entity professional services and distribution company moving off QuickBooks Enterprise, Business Central provides a fully documented REST API (v2.0) with published endpoints covering core ERP objects including GL, AP, AR, vendors, customers, and journal lines. The built-in API layer requires no custom code and minimal setup to activate: for the online (SaaS) version, APIs are enabled by default, and any coding language capable of calling REST APIs can be used to build Connect apps for point-to-point integrations with systems like ADP and Salesforce. …

Limitations: One documented constraint is that existing built-in API pages cannot be extended with additional fields directly; if a built-in endpoint does not expose a field the buyer needs, the documented workaround is to copy the AL code and build a new custom API, which requires AL development resources. …

Requirement evaluated: SSO via Azure Active Directory

For your 320-person, 8-entity organization migrating from QuickBooks Enterprise, Business Central online uses Microsoft Entra ID (formerly Azure Active Directory) as its sole authentication mechanism: there is no separate Business Central credential store, and no additional SSO configuration layer to purchase or enable. <cite index="5-9,5-10,5-11,5-12">With Microsoft Entra authentication, user accounts and credentials are stored in a Microsoft Entra tenant; Business Central user accounts are then associated with that tenant, so users access Business Central directly through their Microsoft Entra account, enabling a single sign-on experience across applications and services.</cite> The techni …

Limitations: No material limitations apply to this buyer's scenario: because Business Central online is a Microsoft-hosted product, Entra ID SSO is the default and only supported authentication path, not an add-on. …

Requirement evaluated: SSO via Azure Active Directory

For a multi-entity professional services company already running Azure Active Directory, Business Central SaaS is purpose-built for this requirement: it uses Microsoft Entra ID (the current name for Azure AD) as its native identity platform. Users authenticate to Business Central using their existing Microsoft 365 organizational account credentials, delivering true federated SSO with no separate ERP username or password. The underlying protocol is OpenID Connect (OIDC) built on OAuth 2.0, which became the standard mechanism in Business Central version 22 (2023 release wave 1) after WS-Federation was retired. …

Limitations: For the buyer's 8 US and Canada entities, all users must be homed in the same Microsoft Entra tenant (or in a multitenant app registration if entities span separate Entra tenants), which requires a deliberate tenant architecture decision before go-live. …

Requirement evaluated: 1099 preparation and electronic filing

For a company moving off QuickBooks with 8 legal entities each requiring separate EIN filings, Business Central's US localization includes a fully native 1099 workflow. During the year, each vendor card is flagged with an IRS 1099 Form No. and Form Box No. (e.g., NEC-01, MISC-03) on the Payments FastTab; <cite index="1-12,1-13">on purchase documents you can specify that the document is 1099-liable and assign the 1099 code for the vendor, and before you start using Business Central you must set up 1099 Form Boxes and designate vendors as 1099-liable.</cite> When invoices are posted and payments applied, <cite index="3-39">the Amount field on the 1099 Form Document page updates automatically.< …

Limitations: Business Central's native 1099 module does not document Combined Federal/State Filing (CF/SF) state-level e-filing or active IRS TIN matching against the database; state-level 1099 obligations would need to be handled separately or confirmed with a tax advisor. …

Requirement evaluated: Three-way matching for PO-based invoices with configurable tolerance (we need 2% on price, 5% on quantity)

For a $180M multi-entity company needing audited financials, Business Central does deliver a three-way matching document flow: an AP user creates a purchase invoice by selecting posted receipt lines via the 'Get Receipt Lines' action (or the new 'Get Order Lines' action released in BC28/2026 Wave 1), which structurally links the invoice back to the posted goods receipt and the originating purchase order. The Payables Agent (released in 2025 Wave 2) further automates finding matching orders and receipts for incoming invoices. …

Limitations: The buyer's explicit requirement for a separately configurable 2% price tolerance and 5% quantity tolerance that flags or holds non-conforming invoices before posting cannot be met natively in Business Central: price discrepancies are captured in variance accounts rather than gated by a threshold, and there is no invoi …

Requirement evaluated: Positive pay file generation for our Bank of America commercial accounts

For this buyer's Bank of America commercial accounts, Business Central includes positive pay file generation as a native, preconfigured feature requiring no third-party add-on. After checks are printed through the Payment Journal, a controller opens the Bank Account card, selects the 'Positive Pay Export Format' field (where the Bank of America format is available out of the box), and triggers the 'Positive Pay Export' action. The system draws from Check Ledger Entries, validates the data via the Exp. Validation Pos. Pay codeunit, and generates a file containing vendor information, check number, and payment amount in Bank of America's required format. …

Limitations: File transmission to Bank of America is a manual step: the controller exports the file and uploads it to Bank of America's portal directly; Business Central does not natively schedule or automate the transmission. …

Requirement evaluated: Three-way matching for PO-based invoices with configurable tolerance (we need 2% on price, 5% on quantity)

For a $180M professional services and distribution company needing auditable three-way matching with specific tolerances, Business Central natively performs three-way matching by linking a vendor invoice to a posted purchase receipt (via the 'Get Receipt Lines' action) and to the originating purchase order, covering the PO-receipt-invoice triangle your auditors will expect. As of version 27.3, the Payables Agent also supports three-way matching and PO matching for product-based invoices. However, the buyer's specific requirement for separate, configurable tolerances on price (2%) and quantity (5%) …

Limitations: Business Central does not have a native, configurable price tolerance percentage that blocks posting when the invoiced unit price deviates from the PO price beyond a set threshold; the buyer's required 2% price tolerance cannot be enforced as a hard rule natively. …

Requirement evaluated: Shared services model: centralized AP team processes invoices for all entities with proper entity coding

For your 8-entity US/Canada structure, Business Central uses a 'Company' per legal entity, each with its own isolated ledger and chart of accounts. A centralized AP team can be permissioned to post purchase invoices across all companies within the same environment: permission sets are assigned per user with company-specific scope, meaning AP clerks can hold posting rights for all eight entities from a single Microsoft Entra login. The practical workflow is a company-switcher model: the AP clerk uses Business Central's built-in company switcher (available from any page, no re-login required) …

Limitations: There is no native unified AP inbox that surfaces all incoming vendor invoices across all 8 entities in a single queue with an entity-coding field at entry; AP clerks must manually switch company context for each entity's invoices, which reduces the efficiency gain of a true shared services model. …

Requirement evaluated: Ability to report at entity level, entity group level (US vs. Canada), and full consolidated level

For a company replacing QuickBooks Enterprise across 8 legal entities in the US and Canada, Business Central delivers two of the three required reporting levels natively and well. Each subsidiary operates as a separate BC 'company' with its own isolated ledger, chart of accounts, and GL entries, so entity-level financial reports (balance sheet, income statement, trial balance by legal entity) are available directly within each company's environment. …

Limitations: The intermediate US vs. Canada sub-consolidation level requires either a manually configured second-tier consolidation company or dimension-filtered Financial Reports, not a native persistent group hierarchy with its own automated elimination run; this adds implementation complexity and means the buyer's controller mus …

Requirement evaluated: Ability to report at entity level, entity group level (US vs. Canada), and full consolidated level

This $180M company with 8 legal entities across the US and Canada needs to report at three levels: individual entity, regional group (US vs. Canada), and full consolidated. Business Central covers all three natively. At the entity level, each legal entity runs as its own Business Central company with its own G/L, and financial reports run within that company context. For the group level (US vs. …

Limitations: The native Consolidated Trial Balance (4) report is limited to displaying four business units as columns in a single view; with 8 entities this buyer will need to rely on the standard (non-4) Consolidated Trial Balance or build custom financial reports for side-by-side entity comparisons. …

Requirement evaluated: Multi-currency support: CAD to USD translation with automatic gain/loss calculation per ASC 830

For this buyer's CAD-to-USD requirement across 8 legal entities pursuing audited financials, Business Central delivers two distinct layers of FX handling. At the transaction level, <cite index="1-29,1-30,1-31,1-32,1-33">the Exchange Rates Adjustment batch job uses the exchange rate valid on the posting date to adjust currency balances, calculates differences for individual currency balances, and posts unrealized amounts to dedicated Unrealized Gains and Unrealized Losses G/L accounts, with balancing entries automatically posted to the receivables/payables accounts.</cite> Realized gains and losses are handled at settlement: <cite index="4-18,4-19,4-20">when an invoice is paid and the bank re …

Limitations: Business Central's per-account Average/Closing Rate translation methods and automated unrealized/realized FX gain-loss posting cover the transaction-level mechanics of ASC 830, but the CTA equity section entry is not automated natively, and Microsoft's own documentation explicitly cautions against using the ACY for sub …

Requirement evaluated: Role-based training plan (not generic): controller, AP clerk, entity bookkeeper, executive

For a multi-entity professional services company moving off QuickBooks with distinct controller, AP clerk, bookkeeper, and executive users, Business Central offers one of the most formally segmented training ecosystems in the mid-market ERP space. Microsoft Learn publishes separate, persona-labeled learning catalogues for each audience: a <cite index="31-1">Business Decision Maker learning catalogue</cite> (covering the executive audience), a <cite index="28-1,28-2">Business Users Learning Catalogue organized from core knowledge to specific domains, from most basic to most advanced</cite> (covering AP clerk and entity bookkeeper roles), and a <cite index="30-1,30-2">Functional Consultants le …

Limitations: The Microsoft Learn role-based catalogues are self-paced and publicly available; a structured, engagement-specific training delivery plan segmented by this buyer's exact roles (controller running 8-entity close, AP clerk processing 2,500 invoices/month, entity bookkeeper, C-suite executive) …

Requirement evaluated: Dedicated support contact (not ticket-only) during the first year

For a $180M professional services company moving off QuickBooks, the practical path to a dedicated contact in Business Central runs through the VAR/reseller model, not Microsoft directly. Microsoft's own documentation states that 'each Business Central customer has a partner who assists with technical support when requested by the internal administrator,' and that partner is required to configure their named support contact details in BC's Help and Support page. This means the implementing VAR is, by design, the dedicated human contact for day-to-day support. Beyond the VAR, two Microsoft-direct options exist: (1) …

Limitations: The VAR-as-dedicated-contact model carries no Microsoft-standardized SLA for named contact continuity or response time, and its quality varies entirely by which partner is selected. …

Requirement evaluated: Target go-live within 6 months of contract signing

For a $180M company moving from QuickBooks Enterprise across 8 legal entities with ADP and Salesforce integrations, Business Central provides several deployment accelerators that make a 6-month target possible but not routine. On the tooling side, Microsoft ships two built-in QuickBooks migration extensions (one for Desktop, one for Online), both accessible via the assisted setup wizard, which transfer master data including customers, vendors, items, and GL accounts directly into BC without custom scripting. <cite index="34-2,34-3">Business Central ships with two built-in extensions for QuickBooks migration: the QuickBooks Data Migration Extension (for Desktop) …

Limitations: This buyer's specific combination of 8 legal entities requiring intercompany elimination setup, chart of accounts restructuring from QuickBooks Enterprise's flat structure to BC's posting-group and dimension model, plus live ADP and Salesforce integrations, places the project in the tier where experienced practitioners …

Requirement evaluated: Phased implementation: core GL and consolidation first, then AP/AR, then advanced reporting

For a $180M company migrating off QuickBooks Enterprise with an urgent audit deadline, Business Central's architecture naturally supports the buyer's three-phase sequence. Phase 1 (GL and consolidation) is viable as a standalone starting point because BC's native consolidation feature operates entirely within the core GL layer: the buyer's eight legal entities are configured as Business Units under a dedicated 'consolidated company' container, chart-of-accounts mapping is set up per entity, and the G/L Consolidation Eliminations report handles intercompany elimination postings — all before AP/AR workflows are activated. …

Limitations: BC's Essentials license bundles GL and AP/AR in the same SKU (Manufacturing and Service Management are the Premium-only differentiators), so there is no license-tier gate that automatically restricts AP/AR access during Phase 1; phasing must be enforced through permission-set configuration and partner project disciplin …