What is Dynamics 365 Finance?

Dynamics 365 Finance is Microsoft's enterprise-grade financial management application — the upper-tier counterpart to Business Central's finance module. It descends from the Dynamics AX general ledger and is aimed at organisations that operate across many legal entities, currencies, and jurisdictions, typically with revenues from a hundred million up into the multi-billions.

Multi-entity, multi-currency, multi-everything

Finance models a legal entity as the unit of statutory reporting, with its own chart of accounts, fiscal calendar, currencies, and posting layers. A tenant can hold hundreds of legal entities sharing master data through data sharing policies and a global address book, with intercompany accounting wired in so that transactions between entities balance automatically. Organization hierarchies model the reporting and approval structure across those entities, and the whole thing sits on a role-based security model built for exactly this scale of segregation of duties.

This is where the product earns its price. A group with 40 legal entities across Europe, LATAM, and APAC can share vendors, customers, items, and employees through data-sharing while keeping local statutory postings, local charts of accounts, and local reporting compliant. Businesses that started on one ERP per country and hit the wall trying to consolidate them are the archetypal Finance customer.

General ledger

A single shared chart of accounts can be reused across entities, layered with up to ten financial dimensions (Department, Cost Centre, Project, Region, Product Line, and so on) and analysed through Financial Reporting (the descendant of Management Reporter). Dimensions are set-based rather than segment-based, so a report can slice on any subset independently — a change from segment-based ledgers where the chart of accounts itself carried the analytical structure. Every posted document draws its number from a configured number sequence, and any entity trading in more than one currency layers in parallel currencies on top of the ledger.

Multiple posting layers (Current, Operational, Tax) let you post the same transaction differently for statutory and management views without a parallel ledger. The Tax layer is heavily used in jurisdictions where the tax view of an asset or a deferred revenue differs materially from the accounting view. The cost accounting module sits alongside the GL as a separate, non-statutory ledger for management costing views the posting layers alone don't cover.

Accounts payable and receivable

Vendor and customer invoicing, payment proposals, settlements with cash discounts and write-offs, ageing, and centralised payments across legal entities. Strong support for electronic invoicing through the Globalisation Studio's e-invoice profiles per country, bank automation through direct bank feeds or file-based statement import — see the Cash Management module and cash flow forecasting for the liquidity side — and AI-assisted matching for payments and invoices, the same OCR-driven pipeline covered in AP automation and OCR.

Vendor collaboration lets suppliers submit invoices directly through a portal; on the customer side, customer portals and B2B commerce integration cover self-service. US vendor payments over the reporting threshold trigger 1099 reporting, and payments in jurisdictions that tax at source need withholding tax configured before the first invoice posts.

Fixed assets and revenue recognition

Multiple depreciation books run in parallel per asset — tax, IFRS, US GAAP, and internal management can all coexist on the same physical asset. Proposals for depreciation, transfers, splits, and disposals are journal-driven; asset lifecycle costs (acquisition, capitalisation, disposal, impairment) roll up into the general ledger through configurable posting profiles. This is the same machinery Dynamics 365 for rental businesses leans on hardest, since a rental fleet's entire revenue model runs on getting asset depreciation and utilisation right.

The dedicated Revenue Recognition module covers ASC 606 and IFRS 15 with bundles, allocations, contract management, and residual-method treatment. It replaced the older Revenue Recognition in Sales and Marketing and is the current recommended path for subscription and services businesses — increasingly alongside the newer Subscription Billing module for recurring-contract billing itself. Lease accounting under the related IFRS 16 / ASC 842 standards is covered separately in IFRS 16 lease accounting.

Budgeting, planning, and consolidations

Budget control with optional commitment accounting stops purchase orders and expense reports that would overrun a budget bucket. Budget planning workflows let distributed contributors build a consolidated plan through Excel templates and route-based approvals — the same workflow engine that drives approvals across purchasing, expenses, and journals generally. Neither replaces a full corporate-performance-management tool (Anaplan, OneStream, Board), but for mid-complexity groups they're often sufficient.

Native consolidations of multiple legal entities into a reporting entity — with currency translation, intercompany eliminations, and adjustments — again cover moderate complexity without a separate CPM system. For very large or highly acquisitive groups, a specialised CPM product is still the norm.

Tax and regulatory

Country-specific localisations cover VAT / sales tax calculation, statutory reporting, electronic invoicing, and audit files (SAF-T, GDPdU, DATEV, SII) for dozens of countries — sales tax setup covers how the native tax engine and third-party tax services like Avalara actually get configured. Microsoft maintains the localisation packs, and the ISV ecosystem fills gaps where local formats change ahead of Microsoft's release cycle.

The Globalisation Studio and the underlying Electronic Reporting framework are configurable — a partner or in-house team can define a new e-invoice format or a statutory report without code, which matters as more countries roll out real-time e-invoicing mandates.

Licensing and implementation

Sold per user, with Full User, Activity User, and Team Member tiers. Attach licenses reduce the cost of adding a second Dynamics 365 app to users who already hold one. The Team Member license is genuinely restricted — read-only for finance, with narrow write access — so most core finance staff need a Full User.

Implementation almost always involves a global system integrator: Avanade, EY, Deloitte, PwC, Sikich, or a large regional partner. Projects run from six months for a subsidiary rollout to two years or more for a global template. Post go-live, the shared platform means Finance and Supply Chain roll forward together on Microsoft's release cadence — two major waves a year plus monthly service updates.

When Dynamics 365 Finance is the wrong fit

Below roughly a hundred million in revenue with a small handful of legal entities, Business Central's finance module — dimensions, posting groups, intercompany, consolidations — covers the same ground at a fraction of the licence cost and a fraction of the implementation timeline; Finance's ten financial dimensions and multi-book posting layers solve a complexity problem that a simpler group doesn't have yet. Above it, at the largest and most acquisitive multinationals, native budgeting and consolidations remain a starting point rather than a full corporate-performance-management replacement — expect to keep or add a dedicated CPM tool (Anaplan, OneStream, Board) once the group outgrows what Finance's planning tools do natively. Organisations already committed to SAP for their core ledger, with Finance evaluated only for a peripheral entity, should also weigh the integration cost of running two general ledgers against the case for a phased migration instead.

First-time buyer checklist

• Entity and currency count. Model how many legal entities, currencies, and statutory regimes the tenant needs today and in three years — this is the single biggest driver of whether Finance's shared chart of accounts and data-sharing model earn their cost.
• Dimension design. Decide the financial dimension set (Department, Cost Centre, Project, Region, Product Line) before configuration starts; retrofitting dimensions after go-live means re-tagging historical postings.
• Posting layers. Confirm whether the business needs the Tax posting layer alongside Current and Operational — jurisdictions where the tax view of an asset or deferred revenue diverges materially from the accounting view need it from day one.
• Localisation coverage. Check the Globalisation Studio and Electronic Reporting framework cover every country's e-invoicing and statutory-report format you operate in, or that a partner has a maintained localisation.
• CPM boundary. Decide up front whether native budgeting and consolidation are sufficient or whether a dedicated CPM tool is already required — bolting one on later after the group has grown into native tooling's limits is a harder migration.
• System integrator. Finance implementations are consulting-effort-dominated; choosing the right partner shapes the project as much as the product does.

Where to go next

Go deeper with financial dimensions in Dynamics 365 Finance, environments and LCS, and the update discipline in One Version and updates. Year-end close in F&O shows the periodic routines in practice. If you are deciding between tiers, Business Central vs Finance and Operations draws the line, and the Finance and Operations pricing page has current list prices.