How Microsoft Dynamics 365 Business Central works

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For a company like yours operating 8 legal entities across the US and Canada, Business Central addresses this requirement through two complementary mechanisms. First, each legal entity is configured as its own company within a shared Business Central environment, and administrators can standardize the core chart of accounts structure across all entities by replicating the same account numbering scheme; consolidation then maps each subsidiary's GL accounts to a parent consolidation company's COA for group reporting. …

Limitations: Business Central does not system-enforce a single shared COA across all entities: consistency is maintained by convention and administrator discipline, not a locked shared-COA architecture, so entities can diverge over time if governance is weak. …

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

For your 8-entity close, where the controller currently spends 12+ days in QuickBooks Enterprise and spreadsheets, Business Central blocks posting to closed periods with allowed posting date ranges. An administrator sets Allow Posting From and Allow Posting To on General Ledger Setup, and these ranges apply to the company and all users, while exceptions can be defined for specific users on User Setup, which overrule the company range. Posting is also checked at the General Journal Template level, and the order of evaluation is User Setup, then General Ledger Setup, then the General Journal Template. …

Limitations: Closing an accounting period or fiscal year does not by itself stop posting. You can still post general ledger entries to a closed fiscal year, so the actual lock is the posting date range, which has to be set in each of your 8 companies. …

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For a company with 8 legal entities moving off QuickBooks, Business Central assigns each legal entity its own independent G/L account list (company file). The segment layer is delivered not through a multi-part account string but through Dimensions: each company can configure up to 2 Global Dimensions (available as filter fields across reports, batch jobs, and ledger entries) and up to 6 Shortcut Dimensions, for 8 total per company. To achieve cross-entity rollup, BC requires two mapping steps: (1) an Intercompany Chart of Accounts that all partner entities map their local G/L accounts to, enabling intercompany transaction routing; and (2) …

Limitations: BC does not natively enforce a single shared master COA across all 8 entities: each company maintains its own G/L account list, and alignment depends on deliberate, ongoing configuration discipline to keep account lists in sync and consolidation mappings current. …

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: Self-service report builder; our controller must be able to create custom reports without IT or vendor assistance

For a controller at a $180M professional services and distribution company preparing for audited financials, Business Central's native Financial Reporting feature (formerly Account Schedules) provides genuine self-service report creation for financial statement-type output. The controller opens the Financial Reports page, chooses New, then builds custom row definitions (specifying G/L account ranges, formulas, and totaling types) and column definitions (period comparisons, budget-vs.-actual, percentage-of-budget) without IT involvement. …

Limitations: The self-service ceiling is real: Business Central's Financial Reporting feature covers GL-based financial statements (income statement, balance sheet, trial balance, budget-vs.-actual) …

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: ADP payroll integration: automated journal entry posting after each pay run with departmental cost allocation

For a professional services and distribution company running ADP Workforce Now for payroll, Business Central supports automated journal entry posting after each pay run through ADP's own published integration connector. After each payroll cycle completes, ADP's General Ledger Interface passes payroll journal entries directly into Business Central's General Journal, where pre-configured G/L account mappings are remembered from prior pay runs so accounts are prefilled automatically on import. …

Limitations: The journal entry creation step is triggered by ADP's GL Interface file following payroll cycle completion, not a fully event-driven push that bypasses human review: a user must initiate the import and then post the pre-populated journal lines, meaning there is still a brief manual confirmation step per pay cycle. …

Requirement evaluated: SSO via Azure Active Directory

For a company in your position moving off QuickBooks and targeting audited financials, Business Central online is built natively on the Microsoft identity platform and uses Microsoft Entra ID (Azure Active Directory) as its sole authentication method. Per Microsoft's official security documentation, this is "automatically set up and managed" for cloud tenants, meaning your existing Azure AD tenant becomes the identity authority for Business Central without any third-party federation layer. Users sign in with their existing corporate credentials, and the experience is a full SSO: signing out of Business Central does not terminate the Entra ID session, and vice versa. …

Limitations: On-premises Business Central deployments require a separate, manual configuration to enable Entra ID authentication via OpenID Connect, which adds implementation effort; however, the cloud (SaaS) …

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: 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. 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. 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. 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. …

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, 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. …

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: 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; 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. When invoices are posted and payments applied, 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: Real-time consolidated financial statements (not batch/overnight)

For a company with 8 legal entities spanning the US and Canada, Business Central natively supports multi-entity financial consolidation through a dedicated consolidated company architecture. Each subsidiary is configured as a 'business unit' within a parent consolidated company, and Business Central can pull GL entries across entities even if they run in separate Business Central environments, use different charts of accounts, or transact in different currencies (USD and CAD in this buyer's case). …

Limitations: The buyer explicitly requires real-time consolidation with no batch or overnight dependency, but Business Central's consolidation is architecturally a triggered batch job ('Run Consolidation') that must be executed before consolidated statements reflect current subsidiary activity. …

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: Target go-live within 6 months of contract signing

For your 8-entity, QuickBooks Enterprise-based group, Business Central is a cloud SaaS product that Microsoft positions for small and midsize businesses (fact sheet: AI-powered ERP for growing businesses), so there is no hardware or server build. Implementation is delivered by Microsoft partners, not by Microsoft. Partner sources describe typical timelines of about 4-6 months for mid-size companies, and larger multi-entity projects can run 6-12+ months, often phased (MS Dynamics World guide). Microsoft documents built-in QuickBooks Desktop and Online migration extensions that move customers, vendors, inventory items and GL accounts, and these shorten the data-load phase. …

Limitations: Microsoft makes no committed go-live duration, so the 6-month date depends on the partner's plan and your own data readiness. Partner benchmarks put 3+ entity projects at around 20 weeks and complex ones at 25-35 weeks, so adding 8-entity intercompany design, ADP posting and Salesforce integration could push you past 6 …

Requirement evaluated: Data migration of 3 years of transactional history from QuickBooks plus open balances

For a buyer migrating from QuickBooks Enterprise across 8 entities, Business Central provides a native QuickBooks Data Migration Extension (available for both QuickBooks Online and QuickBooks Desktop via Microsoft's Data Exporter tool) that runs through an assisted setup guide inside BC. The extension migrates customers, vendors, items, chart of accounts, beginning balance transactions in the general ledger, on-hand inventory quantities, and open documents such as invoices, credit memos, and payments from QuickBooks to Business Central. For master data and opening balances, this covers the cutover fundamentals. Beyond the native extension, BC's RapidStart Services (Configuration Packages) …

Limitations: The standard QuickBooks-to-BC migration approach focuses on master data, opening balances, and open items; full historical transaction history is not typically brought in automatically. …

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 Business Decision Maker learning catalogue (covering the executive audience), a Business Users Learning Catalogue organized from core knowledge to specific domains, from most basic to most advanced (covering AP clerk and entity bookkeeper roles), and a Functional Consultants learning catalogue organized from core knowledge to specific domains, from most bas …

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. …