How Microsoft Dynamics 365 Finance works

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

For a company like yours with 8 legal entities spanning the US and Canada, D365 Finance delivers the three dashboard components through a layered set of pre-built, role-based workspaces and reporting tools. For consolidated cash position, the Cash overview Power BI content surfaces in the 'Cash overview – all companies' workspace, allowing analysis of cash by legal entity, currency, and bank account from a single view. For AP and AR aging, the Vendor payments workspace Analytics page shows vendor invoices past due and due in the future across all companies via embedded Power BI, while the Credit and collections management Power BI content (CustCollectionsBICrossCompany) …

Limitations: The embedded Power BI workspace visuals (Cash overview, Credit and collections, Vendor payments) depend on Entity Store aggregate measurement refreshes, which are scheduled rather than instantaneous, so the Power BI analytics pages in workspaces are not push-real-time; the on-demand Financial reporting module is the cl …

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

For a company like yours, running 8 legal entities across the US and Canada with simultaneous reporting needs across entity, department, service line, project, and location, D365 Finance's Financial Dimensions framework is the core mechanism. At transaction entry, each journal line or document is tagged with up to approximately 50 independent dimension attributes (entity, department, project, location, service line, and others), stored separately from the main account string so dimensions do not multiply the chart of accounts. …

Limitations: Each account structure supports up to 10 additional financial dimension segments natively, with conditional dimensions added via Advanced Rules; the buyer's 5-dimension requirement is well inside this limit, but organizations with more complex dimension needs must plan account structure and advanced rule design careful …

Requirement evaluated: Export to Excel and integration with Power BI for advanced visualization

For a $180M company moving from QuickBooks with 8 legal entities, D365 Finance delivers Excel and Power BI connectivity through several complementary, fully native mechanisms. First, most transaction grids and financial reports carry an 'Open in Excel' button that connects the workbook to Finance via an OData plug-in: the workbook stays live and users can publish edits back to Finance directly from Excel, including custom financial dimension values. Static 'Export to Excel' (or PDF) is also available on every finalized Financial Reporting report for audit-ready snapshots. Critically for an 8-entity buyer, the Accounting Source Explorer (version 10.0.45+) …

Limitations: BPA's embedded Power BI dataset refreshes only twice per day (midnight and noon UTC) and is capped at the most recent 8 quarters of data; customers with large data volumes may hit the default Power BI Embedded A3 storage tier, requiring an upgrade. …

Requirement evaluated: Scheduled report delivery (weekly flash report to leadership, monthly board package)

For a company moving off QuickBooks Enterprise and preparing for audited financials, D365 Finance provides three complementary mechanisms to push financial reports to leadership on a defined cadence. First, the Financial Reporting add-in (formerly Management Reporter) includes a native report scheduler inside Report Designer: an administrator sets a recurrence pattern (Daily, Weekly, Monthly, or Yearly), a start time, and an optional end date, and the system automatically generates the report or report group at that cadence, covering multiple companies in a single schedule run. Second, D365's Electronic Reporting (ER) …

Limitations: Financial Reporter's native scheduler generates reports into the Web Viewer portal and does not natively push them to an email distribution list, so the buyer must rely on the Power BI subscription path or ER batch email for true inbox delivery; the Power BI subscription approach requires Power BI Pro or Premium Per Us …

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 with 8 legal entities across the US and Canada, D365 Finance uses a shared chart of accounts model in which a single COA is created once and then assigned to each legal entity on that entity's Ledger page. <cite index="5-7">Any legal entity in an organization can share and use a chart of accounts.</cite> The account string is composed of a Main Account plus Financial Dimensions (Department, Cost Center, Business Unit, Project, etc.) that serve as segments. …

Limitations: <cite index="11-1,11-2">The base account structure supports up to 10 additional financial dimensions (11 segments including Main Account); to add more dimensions beyond this limit, advanced rules can be used, which allow up to 16 total segments, though Microsoft advises thoroughly evaluating setup requirements if you n …

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 across 8 legal entities in the US and Canada, D365 Finance provides a purpose-built 'Shared chart of accounts' architecture that directly solves the multi-entity COA problem. A single chart of accounts is defined once and then assigned to each of your 8 legal entities via the Ledger page — main accounts are maintained in one place rather than duplicated per entity. Financial dimensions (Department, Cost Center, Business Unit, Project, and custom dimensions such as Service Line or Location) …

Limitations: Account structure changes (adding or removing segments) require an activation process that temporarily suspends transaction entry across the affected legal entities, and Microsoft recommends treating activation as a periodic event rather than a routine one — the best-practices guide notes performance degradation when m …

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

For a company like yours moving off QuickBooks Enterprise, D365 Finance handles GL posting through a subledger architecture: transactions in AP, AR, inventory, and other modules first create subledger journal entries, which are then transferred to the General Ledger as a separate step. Microsoft's official documentation on subledger-to-GL transfer documents two configuration options. The first is 'Scheduled batch,' where subledger entries are queued and processed at a scheduled time; this mode directly violates your stated requirement. …

Limitations: D365 Finance does not offer a fully synchronous, in-transaction GL posting option for subledger documents; the best available mode (Asynchronous) requires a functioning batch server and creates a brief but non-zero lag between AP invoice posting and GL update. …

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

For a professional services and distribution company needing headcount and square footage as allocation drivers across 8 legal entities, D365 Finance delivers this through its native Cost Accounting module using a dedicated 'statistical dimension' construct. The controller defines a statistical dimension (e.g., 'Headcount' or 'Square Footage') and assigns it to a Cost Accounting ledger; each individual KPI (e.g., headcount per cost center, square meters per department) becomes a 'statistical dimension member.' Microsoft's terminology documentation explicitly names these exact KPIs: 'Examples of statistical dimensions include the number of employees... …

Limitations: The statistical dimension and allocation base mechanism lives inside the Cost Accounting module, which requires its own ledger setup and configuration separate from the core GL; the buyer's phased implementation plan (GL and consolidation first) …

Requirement evaluated: Configurable approval workflows by entity, department, GL account, and dollar threshold

For a professional services and distribution company running 8 legal entities, D365 Finance's native Workflow framework handles all four routing dimensions the buyer requires. Administrators configure vendor invoice workflows under Accounts Payable > Setup > Accounts Payable Workflows, with a separate workflow instance available per legal entity. <cite index="21-3,21-9">An active vendor invoice workflow is set up per legal entity, and invoices can be automatically submitted to that workflow system once configured.</cite> Within each workflow, <cite index="9-3,9-4,9-5">conditional decisions split the workflow into branches, with the system evaluating the document against specified conditions …

Limitations: Configuring multi-dimensional conditional routing across 8 entities with distinct department and GL-account combinations requires careful workflow design, as each legal entity needs its own workflow instance and expenditure reviewer setup; this is administrative setup complexity rather than a functional ceiling. …

Requirement evaluated: 1099 preparation and electronic filing

For a company like yours processing invoices across 8 legal entities and preparing for audited financials, D365 Finance includes a dedicated Tax 1099 module within Accounts Payable, scoped to US legal entity localizations. During vendor setup, an AP administrator opens the Tax 1099 FastTab on each vendor record, enables 'Report 1099,' enters the Federal Tax ID and Tax ID type, assigns a default 1099 box code, and captures IRS-required fields such as the Name Control, Second TIN flag, and foreign entity indicator. …

Limitations: 1099 processing in D365 Finance runs per legal entity, so your controller will need to execute the Tax 1099 settlement and electronic file generation separately for each US entity (Canadian entities are outside US 1099 scope); there is no single-run consolidated 1099 workflow across all 8 entities in standard D365 Fina …

Requirement evaluated: 1099 preparation and electronic filing

For a company like yours managing 8 legal entities and preparing for audited financials, D365 Finance handles 1099 preparation natively within its Accounts Payable module across each US legal entity. Setup begins on the Tax 1099 FastTab of each vendor record, where users flag 'Report 1099,' enter the Federal Tax ID (TIN), and assign a default 1099 box code; a duplicate-TIN guard prevents data entry errors across vendors. …

Limitations: D365 Finance produces a FIRE-format electronic file for manual upload to the IRS FIRE portal rather than a direct API push to the IRS IRIS system (that direct IRIS API integration is documented for Business Central, not D365 Finance), so your team will handle the final upload step. …

Requirement evaluated: 1099 preparation and electronic filing

For a $180M multi-entity professional services company moving off QuickBooks and toward audited financials, D365 Finance provides a native Tax 1099 module within Accounts Payable. During vendor setup, the controller enables the 'Report 1099' checkbox on the Tax 1099 FastTab for each applicable vendor, enters the vendor's Federal Tax ID (TIN), assigns a default 1099 box code, and records the IRS-required EIN name control field. …

Limitations: The electronic filing mechanism generates an IRSTAX export file that a designated transmitter submits to IRS FIRE; there is no documented in-product 'direct submit to IRS' button, so a manual upload step to the IRS FIRE portal (or a third-party transmitter) is required. …

Requirement evaluated: Customer portal for invoice access and online payment

For a $180M multi-entity professional services and distribution company preparing for audited financials, D365 Finance does not ship a turnkey customer-facing AR portal. The native AR module manages invoice creation, posting, customer account statements (emailed PDFs), and internal collections workflows for your AR staff, but there is no out-of-box externally accessible login environment where your customers can view their invoices and submit payments online. To deliver invoice visibility, the documented approach in the Microsoft ecosystem is to build a portal on Microsoft Power Pages (formerly Power Apps Portals), connected to D365 Finance data via Dataverse. …

Limitations: For this buyer's scenario, the gap is specifically the online payment submission component: even a well-configured Power Pages portal for D365 Finance covers invoice viewing and settlement history, but a customer-facing payment gateway that writes settlements back to the D365 Finance AR ledger requires a separately con …

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

For a professional services and distribution company operating across 8 US and Canadian legal entities, D365 Finance delivers per-entity invoice template configuration through three layered mechanisms. First, because D365 Finance maps each legal entity to a separate 'company,' all Accounts Receivable parameters — including the Print Management setup page — are configured independently per legal entity; an administrator navigates to Accounts Receivable > Setup > Forms > Form setup > Print Management within each company to assign a distinct report format (for example, SalesInvoice.Report_IT or a custom layout) …

Limitations: Modifying ER format configurations — such as adding a logo, adjusting line-item layout, or changing legal footer content — requires use of the ER designer in the Globalization Studio workspace, which is a functional consultant or developer task rather than a self-service controller action; the buyer's controller will n …

Requirement evaluated: Customer portal for invoice access and online payment

For a professional services company preparing for audited financials and needing customers to self-serve invoices and pay online, D365 Finance does not ship a turnkey AR customer portal out of the box. The supported path is to build one using Microsoft Power Pages, Microsoft's own low-code external web portal platform. The official Microsoft reference architecture documents how this works: <cite index="22-1,22-6,22-7,22-8">Power Pages works via Dataverse; when changes happen in Finance and Operations, the integration syncs them to Dataverse, after which Power Pages can read the data, and changes from Power Pages are stored in Dataverse and then synced back to Dynamics 365.</cite> This means …

Limitations: The buyer will not find a configure-and-deploy customer payment portal inside D365 Finance; instead they face a build-or-buy decision: custom Power Pages development (requiring additional Power Pages licensing and developer effort) …

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

For a professional services and distribution company running 8 legal entities and needing audit-ready AR, D365 Finance delivers automated invoicing with configurable templates through its native Accounts Receivable module. Finance supports two invoicing paths: sales-order-based customer invoices and free-text invoices for service-line billing not tied to a sales order. …

Limitations: Free-text invoice templates are designed for service-line or non-inventory billing; for distribution lines tied to sales orders, the template mechanism does not apply and invoicing flows through the order-fulfillment path instead. …

Requirement evaluated: Cross-entity drill-down; from consolidated P&L, click into the entity-level transaction

For a controller managing 8 legal entities across the US and Canada, D365 Finance delivers this capability through its Financial Reporting module (formerly Management Reporter) combined with reporting tree definitions. A consolidated P&L is built using a reporting tree that maps each legal entity as a node; the user opens the consolidated report and can drill down through the financial level, to the account level, and then to individual voucher transactions, all within the same session. …

Limitations: <cite index="5-7,5-8,5-9,5-10">In the Power BI-embedded Financial Analysis workspace (a separate surface from the core Financial Reporting module), drill-back lands on the Accounting Source Explorer rather than voucher transactions, and in some situations the sum of detailed transactions in the ASE may not match the ba …

Requirement evaluated: Real-time consolidated financial statements (not batch/overnight)

For a company with 8 legal entities running on a single D365 Finance instance, consolidated statements are produced through two documented paths. The first is 'Consolidate Online,' where a user selects a template, specifies a date range, and clicks 'Perform consolidation.' Microsoft's own documentation describes this as a background batch job: the interface includes a 'View consolidation timeline' to track batch job progress, and after the job completes a separate 'Rebuild balances' step is required before the Trial balance accurately reflects subsidiary data. …

Limitations: For this buyer's 8-entity US/Canada structure, Consolidate Online is an explicitly manual or scheduled batch process that reintroduces the periodic aggregation problem the buyer wants to eliminate; Financial Reporting's data mart architecture means a transaction posted in a subsidiary ledger is not instantly visible in …

Requirement evaluated: Automated intercompany transaction creation; when Entity A bills Entity B, both sides should post automatically

For a company like yours with 8 legal entities constantly billing each other across the US and Canada, D365 Finance handles this through its native Intercompany Accounting module. An administrator first configures legal entity pairs on the Intercompany Accounting setup page, designating originating and destination companies and mapping the Due-to and Due-from GL accounts for each pair. …

Limitations: Each directional pair must be explicitly configured (e.g., Entity A originating to Entity B is a separate setup from Entity B originating to Entity A), so with 8 legal entities across US and Canada, your implementation team must set up and maintain up to 56 directional pairs; the 'Create reciprocal relationship' button …

Requirement evaluated: Automated intercompany transaction creation; when Entity A bills Entity B, both sides should post automatically

For a company moving off QuickBooks and spreadsheet-based intercompany eliminations across 8 entities, D365 Finance delivers this through two complementary native mechanisms. First, the General Ledger Intercompany Accounting module uses pre-configured originating/destination company pairs: <cite index="1-3,1-10,1-11">administrators use the Intercompany accounting page to create pairs of legal entities that can transact with each other, defining the Debit account (Due from) and Credit account (Due to) …

Limitations: Each entity pair must be explicitly configured as an originating/destination relationship in the Intercompany accounting setup; <cite index="1-8">if a user is active in a destination entity and enters a transaction where that entity is not defined as the originator, the transaction will not post</cite>, so for all 8 en …

Requirement evaluated: Guaranteed 99.5%+ uptime SLA with defined severity levels and response times

For a multi-entity professional services company moving off QuickBooks Enterprise, D365 Finance delivers on this requirement through two interlocking mechanisms. First, Microsoft's official 'Service Level Agreements for Microsoft Online Services' document (published at microsoft.com/licensing/docs and updated as recently as June 2026) explicitly lists 'Dynamics 365 Supply Chain Management; Dynamics 365 Finance; Dynamics 365 Project Operations' as covered services, with a contractually guaranteed 99.9% monthly uptime commitment backed by service credits if Microsoft falls short. …

Limitations: The 99.9% SLA exceeds the buyer's 99.5% ask, but service credits are the sole financial remedy for SLA breaches and are capped at the monthly subscription fee for the affected service. Buyers should note that the support response times (particularly for Severity B and C) …

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

For a company coming from QuickBooks Enterprise and spreadsheets, D365 Finance offers two native mechanisms that support role-segmented training, but neither delivers a ready-made plan scoped to the buyer's four personas out of the box. First, Microsoft Learn hosts a library of D365 Finance learning paths that are tagged by role: paths such as 'Work with accounts payable in Dynamics 365 Finance' are explicitly labeled for 'Business User' and 'Functional Consultant' audiences, covering vendor invoice processing, payment journals, and invoice matching — content directly relevant to an AP clerk. …

Limitations: Microsoft does not publish a named, ready-to-use training plan segmented into the buyer's four specific roles (controller, AP clerk, entity bookkeeper, executive); the role tags on Microsoft Learn map to broad vendor personas (Business User, Functional Consultant, Business Owner) …

Requirement evaluated: Chart of accounts redesign assistance; we need help rationalizing 8 divergent charts into one unified structure

For a company like yours moving from 8 separate QuickBooks entity files, D365 Finance's Shared Chart of Accounts architecture is the core mechanism: a single COA is defined once and then assigned to all 8 legal entities on the Ledger page, so every entity posts to the same natural account numbering scheme. Account Structures layer Financial Dimensions (Business Unit, Department, Cost Center, and custom dimensions) on top of main accounts to capture entity- or project-level detail without proliferating redundant accounts, with up to 11 segments natively and 16 via advanced rules. …

Limitations: FastTrack's advisory role covers design validation, not billable COA rationalization workshops; the hands-on data-mapping work (auditing 8 legacy charts, building account crosswalks, configuring the unified structure) …

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

For a $180M multi-entity professional services company moving off QuickBooks and targeting audited financials within 12 months, D365 Finance provides the underlying infrastructure for role-differentiated training but does not ship a pre-built, out-of-the-box role-based training plan for controller, AP clerk, entity bookkeeper, and executive personas. Microsoft's own implementation guidance (published on learn.microsoft.com) explicitly recommends developing a training plan that distinguishes between user types: it notes that executives should receive training 'tailored to their specific role' and that 'train the trainer' is the prescribed approach for power users who then train system users. …

Limitations: No native, pre-packaged role-based training plan for the four personas the buyer named is included with the D365 Finance license or FastTrack; the buyer must budget for partner-led curriculum design, which adds time and cost to an already compressed 12-month audit readiness timeline.

Requirement evaluated: REST API with documented endpoints for custom integrations

For a company moving off QuickBooks Enterprise and needing to connect Salesforce, ADP, and custom tools, D365 Finance exposes integration through two documented REST-compatible layers. The primary mechanism is OData v4: any data entity marked as 'IsPublic' in the Application Object Tree is automatically available at a structured URL (your-org-root/data/EntityName), supporting full CRUD operations via standard HTTP verbs (POST, PATCH, PUT, DELETE) with JSON payloads. Specific entities for the buyer's process are documented, including the Vendor Invoice Header entity and Vendor Invoice Line entity, which support creating and updating invoice records programmatically. …

Limitations: Not every data entity is exposed via OData by default; entities must be individually marked as IsPublic, and building or enabling entities for custom use cases (such as a bespoke ADP payroll import format) …

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

For a $180M multi-entity company needing to connect D365 Finance with ADP and Salesforce via Workato or Celigo, D365 Finance provides three complementary API surfaces that iPaaS platforms can consume. First, it exposes OData REST endpoints for all data entities marked as IsPublic, supporting full CRUD operations authenticated via OAuth 2.0 (Azure AD client credentials flow), which is the standard authentication model both Workato and Celigo use to connect. …

Limitations: Data events require the Microsoft Power Platform integration to be enabled and do not fire for entities backed by views (only table-backed entities), meaning some financial entities may require OData polling instead of true push triggers. …

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

For a $180M multi-entity professional services and distribution company moving off QuickBooks Enterprise and needing to integrate ADP, Salesforce, and other non-native systems, D365 Finance provides a well-documented, open integration surface that both Workato and Celigo connect to natively. On the D365 Finance side, the platform exposes OData V4 REST endpoints supporting full CRUD operations, a Data Management Framework (DMF) package REST API for bulk/async data flows, and OAuth 2.0 authentication via Microsoft Entra ID; these are the hooks that iPaaS platforms target. …

Limitations: The integration surface is well-established, but each non-native connection (ADP, Salesforce, etc.) still requires iPaaS recipe or flow configuration, Azure app registration, and ongoing connector maintenance; this is implementation effort, not a product gap, but the buyer should budget for it during the 12-month audit …

Requirement evaluated: Bank feed integration with Bank of America and TD Canada Trust for automated reconciliation

For a company with US and Canadian entities running accounts across Bank of America and TD Canada Trust, D365 Finance delivers bank reconciliation through its purpose-built Advanced Bank Reconciliation (ABR) module, housed in Cash and Bank Management. <cite index="1-6">D365 Finance supports three bank statement formats natively: ISO20022, MT940, and BAI2.</cite> Bank of America delivers BAI2 files, which is the most thoroughly documented format in Microsoft's ABR setup: <cite index="1-12,1-13,1-14">the configuration pulls the ABR BAI2 format directly from the ER configuration repository in Dataverse and maps it to the bank account.</cite> Once configured, <cite index="4-11,4-12">a 'Reconcile …

Limitations: The mechanism is file-based import (BAI2 or MT940 delivered to a SharePoint folder or uploaded), not a live open-banking API pull from Bank of America or TD Canada Trust; 'automated' reconciliation still depends on each bank reliably delivering statement files to the configured SharePoint location. …