MICROSOFT PRODUCT CAPABILITIES
Connect the close to the wider business.
Dynamics 365 Finance brings core accounting together with financial planning, cash management, and business performance capabilities. It supports organisations that need structured financial processes across multiple companies, currencies, and reporting requirements.
Accounting and close
Manage the general ledger, accounts payable and receivable, fixed assets, and financial close with defined workflows and controls.
Cash and collections
Follow cash and bank activity, customer balances, collections, and cash-flow forecasts to support liquidity decisions.
Planning and performance
Use budgets, financial reporting, and business performance capabilities to compare plans with actual results and investigate changes.
Tax and global operations
Configure legal entities, currencies, financial dimensions, and supported tax requirements so local operations feed a consistent group view.
Match Finance or Finance Premium to the role
Advanced business performance management and planning requirements shape edition choice. Agent use can require Copilot Credits, so identify the specific feature and users when selecting licences.
Put it to work with Braintree.
Braintree maps the chart of accounts and dimensions, designs approvals and reporting, and connects operational transactions to finance. Migration and testing cover the close, reconciliations, and the controls your team relies on.
Microsoft product guidance
Build financial control around your operating model
A finance implementation needs agreement on the chart of accounts, entity structure, approval responsibilities and reporting requirements. Braintree can map these decisions to the solution and identify where surrounding systems require integration.
✓
Define general ledger and entity structures before migration.
✓
Agree approval workflows and ownership of reconciliation exceptions.
✓
Document tax, statutory and group reporting requirements for configuration.
✓
Confirm the scope of project accounting, analytics and available AI assistance.
01
A shared financial model across the organisation
Dynamics 365 Finance fits organisations that need financial processes to remain consistent across entities, currencies and operating teams. The design begins with the ledger, chart of accounts, fiscal calendars and dimensions. These determine how transactions can be classified and compared; they are not simply technical setup choices made after the business process is finished.
For example, a group may need a common view of revenue while its subsidiaries keep different local operating responsibilities. The project must decide which accounts and dimensions are shared, how entities report, and which adjustments belong in consolidation. A new interface will not resolve contradictory definitions of department, project or cost centre.
02
Connect the transaction to the close
The general ledger receives the financial effect of operational and subledger activity. Accounts payable, receivables, bank management, fixed assets and other modules need posting rules and reconciliation responsibilities that agree with that ledger model. A transaction should be traceable from its originating document to the financial result.
A representative demonstration should include an invoice, its approval, payment, bank reconciliation and month-end review. Exceptions matter: a rejected payment, incorrect dimension or late adjustment reveals more about the design than a perfect transaction. The team should also see who can reopen or correct a record and how the action is reviewed.
03
Cash and reporting require controlled assumptions
Microsoft’s Finance insights cash forecasting documentation describes snapshots, scenario comparison and views across currencies or entities. These tools support the finance discussion; they do not remove the need to understand payment behaviour, unusual commitments or information outside the ERP. A forecast should make its assumptions reviewable.
Reporting needs to distinguish statutory, operational and management requirements. A board pack, a bank reconciliation and a departmental cost review may use related data but require different structures and controls. Tax and reporting configuration also need the organisation’s current requirements; buying the software does not automatically settle accounting treatment or regulatory responsibilities.
04
What the finance workstream should deliver
Braintree can map the existing finance model, migration scope and connected processes to the proposed implementation. The engagement should establish decision-makers from finance as well as technical owners, so configuration choices have accountable business approval.
Agree entity structures, charts, calendars, dimensions and posting rules.
Map opening balances, master records and the history needed after migration.
Define controls for journals, payments, reconciliations and period close.
Document interfaces to operational systems and the owner of each exception.
Test close and reporting scenarios with finance users before accepting the implementation.
EVIDENCE & DOCUMENTATION
See the work in context.
BEFORE YOU DECIDE
