D365 Finance vs Business Central vs QBO for ERP & Core Accounting

For a $180M professional services and distribution company operating across US and Canadian legal entities, D365 Finance handles CAD-to-USD translation natively at the legal entity level using its dual-currency and foreign currency revaluation framework. Each Canadian legal entity records transactions in CAD as the functional (accounting) currency; the system then translates those amounts to USD for consolidation using configurable exchange rate types (current, historical, average) per account range, consistent with ASC 830 requirements for balance sheet vs. income statement rates. Per Microsoft's documentation, <cite index='3-27'>"currency translation" allows users to "set up the account ranges and rates to translate from the accounting currency of the source company to the accounting currency of the consolidation company." For unrealized gain/loss, the Foreign Currency Revaluation process in General Ledger, AR, and AP automatically generates system-created entries: <cite index='12-8,12-9,12-10,12-11'>"when you run the revaluation process, the balance in each main account posted in a foreign currency is revalued. The unrealized gain or loss transactions that are created during the revaluation process are system-generated. Two transactions might be created, one for the accounting currency and a second for the reporting currency, if relevant. Each accounting entry will post to the unrealized gain or loss and the main account being revalued." Realized gains and losses are captured at settlement: <cite index='12-20,12-21'>users specify "the realized gain, realized loss, unrealized gain, and unrealized loss accounts for currency revaluation"; realized accounts are used when settling AR and AP transactions, while unrealized accounts are used for revaluing open transactions and general ledger main accounts. The revaluation process can be run in real time or scheduled via batch, and <cite index='11-1,11-2'>"uses a new exchange rate to revalue the open amounts, or not settled amounts, on a specified date" with "the differences between the original posted amounts and the revalued amounts" creating "an unrealized gain or loss for each open transaction."

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, 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. Realized gains and losses are handled at settlement: when an invoice is paid and the bank returns the actual currency rate for the payment, the realized gain or loss is calculated and the unrealized gain or loss is then reversed. For consolidated reporting, if a business unit uses a different currency than the consolidated company, exchange rate methods must be specified for each account before consolidation, with the Consol. Translation Method field on each account card determining the exchange rate applied; the Currency Exchange Rate Table field on the business unit card controls whether consolidation uses rates from the business unit or the consolidated company. The available methods include Average Rate and Closing Rate, which correspond to the income statement and balance sheet treatments under ASC 830's current rate method. However, a critical limitation surfaces at the consolidation layer: Business Central's own documentation warns that the Additional Reporting Currency (ACY) feature should not be used as a basis for financial statement translation unless its limitations are understood, specifically that it cannot translate foreign subsidiary financial statements as part of a company consolidation. Furthermore, after consolidating companies, intercompany elimination transactions must be found and eliminated manually, as processing consolidation eliminations is a manual process requiring general journal lines to eliminate them. There is no documented native automation for Cumulative Translation Adjustment (CTA) posting to the equity section, which is the distinguishing ASC 830 requirement auditors will scrutinize.

This buyer operates 8 legal entities across the US and Canada and needs CAD-to-USD translation that is fully ASC 830-compliant in time for audited financials. QBO's Multicurrency feature does post realized FX gain/loss automatically at the transaction level: when a CAD-denominated invoice is settled at a different exchange rate than the booking rate, QBO calculates the difference and records it to a system-generated 'Exchange Gain or Loss' account. For period-end unrealized revaluation, QBO offers a 'Revalue Currency' workflow (Settings > Currencies > Revalue Currency) that applies a closing or custom rate to open CAD balances on A/R, A/P, and bank accounts, and generates a journal entry reflecting the adjustment. However, the mechanism breaks down at two critical stages for this buyer. First, unrealized gains and losses on A/R and A/P from Home Currency Adjustments are not posted to the general ledger or trial balance; they appear only as display rows in certain reports, which fails audit-trail requirements. Second, and more fundamentally, QBO has no native Cumulative Translation Adjustment (CTA) calculation or posting to Accumulated Other Comprehensive Income (AOCI)/equity, which is a mandatory component of ASC 830's current rate method for entities whose functional currency is CAD. There is also no native multi-entity consolidation engine, so translated CAD financials across this buyer's 8 entities cannot be rolled up into a USD reporting-currency ledger inside QBO; consolidation must occur offline in spreadsheets, recreating the exact manual close problem the buyer is trying to solve.

For a multi-entity professional services company replacing QuickBooks and spreadsheet-based allocations, D365 Finance delivers this requirement through its dedicated Cost Accounting module, which is architecturally separate from the General Ledger but feeds directly from it. The mechanism centers on 'statistical dimension members': non-monetary unit-based records that live in the Cost Accounting ledger and serve as allocation drivers. As Microsoft's official terminology documentation states, examples of statistical dimensions include the number of employees, the count of licensed software on each device, power consumption of each machine, or square meters for a cost center. These are precisely the buyer's two KPIs (headcount and square footage). For headcount, the HcmEmployment table holds a list of all employees and the cost centers that they work for, which D365 Finance can pull natively as a statistical measure via a provider template configured under Cost Accounting Ledger > Actual Version > Manage > Statistical Measures. For square footage, values are entered manually or imported via the Data Management tool. A statistical dimension member automatically becomes a predefined allocation base; it can be used as an allocation base in policies or as input in other types of allocation bases. Cost accountants then wire these statistical members into cost distribution or cost allocation policies: a statistical dimension and its members are used to register and control non-monetary entries in Cost Accounting; statistical dimension members can be used for two purposes: as an allocation base in policies such as cost distribution or cost allocation, and for reporting of non-monetary consumption. The multi-entity dimension is explicitly handled: the system recognizes that source tables where each record belongs to a separate legal entity will prompt the user to select the legal entity that transactions should be imported from.

For a $180M professional services and distribution company moving off QuickBooks and needing auditable overhead allocations across 8 entities, Business Central provides a native Statistical Accounts module that stores unit-based, non-monetary KPI values directly in the GL framework. A controller sets up dedicated statistical accounts (e.g., one for headcount, one for square footage), then posts period-end values via the Statistical Accounts Journal: as Microsoft's documentation states, you can track 'Employee headcount, Square footage' as number-based units per department or entity. These posted balances are then queryable by the Allocation Accounts engine: when configuring a variable allocation account, the user sets the 'Breakdown Account Type' field to 'Statistical Account,' causing BC to read the statistical balance for the chosen calculation period and proportionally split the cost across destination G/L accounts automatically. A parallel path exists in the Cost Accounting module, which supports both static allocation bases (e.g., fixed square footage ratios) and dynamic allocation bases (e.g., 'number of employees in a cost center') without requiring statistical accounts specifically. The result is that shared costs such as facilities rent or IT overhead can be distributed across the buyer's 8 legal entities using live headcount or square footage balances rather than manual spreadsheet percentages.

For a $180M multi-entity professional services and distribution company that needs headcount and square footage to drive intercompany cost allocations, QBO provides no workable mechanism. QBO's chart of accounts is strictly monetary: the only account types available are Income, Expense, Fixed Asset, Bank, Loan, Credit Card, and Equity. Intuit's own support team has confirmed this ceiling explicitly: "At this time, QuickBooks Online (QBO) doesn't yet offer an option for creating a Statistical Account" and the suggestion was submitted to product development as a future consideration. QBO Advanced does offer enhanced custom fields that can store numeric values, but custom fields are designed to track information on sales forms, purchase orders, expense forms, customer profiles, and vendor profiles and carry no connection to any allocation engine. Overhead allocation in QBO is entirely manual: when users ask how to allocate costs by a unit driver, the community answer is "I don't think Quickbooks will do that automatically, so you will need to periodically compute the percentage and make the journal entry." The only documented workaround is a contra-account journal entry hack, which a community accountant described as having already moved several clients off QuickBooks due to the inability to track statistics, noting the only workaround "is very clumsy" and requires exporting to Excel before presenting reports.

For a $180M professional services and distribution company expecting a ready-to-use customer portal where clients log in, view invoices, and pay online, D365 Finance does not ship that capability natively. The AR module tracks customer invoices and incoming payments internally, and the Collections workspace is staff-facing only. Microsoft's documented extensibility path is Power Pages (formerly Power Apps portals), which can surface D365 Finance invoice and settlement data to external customers via Dataverse virtual entities or dual-write sync: as Microsoft's own architecture guide explains, 'when changes happen in finance and operations, the integration syncs them to Dataverse; after Dataverse updates, Power Pages can read the data.' However, this is a build-and-configure project, not an out-of-the-box portal. The Microsoft-published Customer portal template that does exist is scoped to Supply Chain Management sales order processing, not AR invoice access and payment. ISV partners fill the practical gap: Versapay has a built-for connector to D365 Finance and Operations where, as Versapay documents, 'when you post an invoice in Dynamics 365 Finance, this will automatically populate in the customer portal, where customers can view their invoice and make a payment using a card or bank payment,' with the customer payment journal in D365 Finance updated automatically after payment. Avantiico's Finance Portal (also built on Power Pages) similarly enables customer invoice and settlement access natively connected to D365 F&SCM.

For a $180M professional services company expecting audited financials and self-service AR, Business Central's native capability stops well short of a true customer portal. Out of the box, BC supports per-invoice payment links: when a sales invoice is emailed as a PDF, there is a PayPal link in the email body and in the attached PDF document; if the customer chooses the link, the service page for their PayPal account opens showing payment details, and the customer can pay the invoice as any other PayPal payment. Business Central can register payments automatically if the seller has a Business Merchant account for the PayPal Commerce Platform, and when customers use the PayPal link, Business Central posts the entries and closes the document. However, this is a one-invoice-at-a-time, email-triggered mechanism with no customer login, no document history, and no account-balance visibility. Business Central does not natively offer a customer portal; that is where an add-on comes into play, providing instant access to a customer's account information. A true self-service portal, with customer login credentials, open and historical invoice access, and ACH or credit card payment, requires an AppSource ISV extension. Extensions such as iPayments give customers a branded self-service portal where they can log in to download and pay off invoices, and enable customers to view their account and payment history online. Blue Moon's Customer Invoice Portal similarly offers full integration with Business Central AR, customizable payment options, branded invoice presentation, and online payment via credit cards with flexible scheduled and auto-payment methods.

For this buyer's 8-entity, audit-bound professional services and distribution operation, QBO's customer-facing AR experience is built around QuickBooks Payments: the staff creates an invoice in QBO, enables online payments (credit card, ACH, PayPal, Venmo, Apple Pay), and emails it to the customer. With QuickBooks Payments (Merchant Services), you can securely email an invoice with a 'Pay now' button. The customer sees a 'Pay Now' button in the email; that button acts as an embedded payment link that connects directly to the invoice and updates records automatically once the payment is made. That is the full extent of the native customer-facing mechanism. The portal where customers can access account transactions is unavailable in QBO, and the feature to make a link or customer portal that can allow customers to access and update their billing information is currently unavailable. Persistent customer login, full invoice history, statement downloads, and self-service account management require a third-party add-on from the QBO App Store (GoToMyAccounts, BillerGenie, Paidnice, Invoiced, Method CRM), none of which are included in base QBO pricing.