Advanced features

When to use it: Implement Advanced Bank Reconciliation (ABR) when a client processes a high volume of daily bank transactions and manual tick-mark reconciliation is no longer sustainable.

Technical Setup

Dynamics 365 supports industry-standard banking formats out of the box. You must first acquire the correct format from the client's bank (like BAI2, MT940, or CAMT.053).

• Navigate to the Electronic Reporting workspace and import the required format configurations from the Microsoft global repository.
• Go to Cash and bank management > Setup > Advanced bank reconciliation setup > Bank statement format and map your imported ER format to a processing group.

Functional Setup

The core of ABR is the matching engine. You must define exactly how the system identifies a match between the bank file and the ERP ledger.

• Matching Rules: Define the granular logic. For example, a rule might state that the bank transaction date must match the ERP transaction date exactly, and the amount must match exactly.
• Matching Rule Sets: Group your rules sequentially. Best practice dictates running highly specific rules first (like matching by exact check number) and broad rules last (like matching by amount within a 3-day window).

Execution

To enable ABR for a specific bank account, navigate to the Bank accounts form and toggle Advanced bank reconciliation to Yes. Once enabled, you cannot revert to manual reconciliation for that account. During testing, keep "Reconcile after import" turned off. Once you validate that your rules catch 90 percent of transactions, turn it on to fully automate the daily reconciliation process.

When to use it: Required for global organizations operating across multiple tax jurisdictions, or shared service centers managing payables across subsidiaries.

Legal Entity Strategy

The first architectural decision is whether to split operations into multiple legal entities or use a single entity with financial dimensions. Use multiple legal entities when statutory reporting and tax ID requirements mandate hard data isolation. Use a single entity with a "Location" dimension if the operations share the same tax ID and statutory reporting boundary.

Currency Setup

Dynamics 365 tracks multiple currency layers for every transaction.

• Accounting Currency: The functional currency used for local statutory reporting.
• Reporting Currency: The secondary currency used for corporate rollups.

Configure automated exchange rate providers (like OANDA or Central Bank integrations) in the General Ledger setup to pull daily spot rates, eliminating manual data entry.

Operations and Month End

Configure Foreign Currency Revaluation (FX Reval) logic. At month end, consultants must ensure the system revalues open AP and AR invoices against the current exchange rate, posting unrealized gains or losses automatically.

When to use it: When distinct legal entities within the same Microsoft tenant buy and sell to each other, or allocate shared expenses.

Ledger Setup

To ensure clean consolidations, you must define unique "Due to" (Liability) and "Due from" (Asset) main accounts for each legal entity. Never use a single shared intercompany account, as it will cause a nightmare during the month-end elimination process.

Configuration Steps

Navigate to General ledger > Setup > Intercompany accounting. You must create an origin and destination pairing.

• Select the originating company and destination company.
• Define the debit and credit accounts.
• Consultant tip: Always use the "Create reciprocal relationship" button. This automatically generates the reverse configuration in the counterpart company, preventing manual typos.

Trade Setup

If the entities trade physical goods, you must set up intercompany customers and vendors. In the selling entity, create a customer record and toggle the Intercompany active flag. Link it directly to the corresponding vendor record in the purchasing entity. Define your auto invoicing policies so that when the selling entity ships the goods, the purchasing entity automatically receives the vendor invoice.

When to use it: At month end or year end when the parent company needs to generate aggregated financial statements across all global subsidiaries.

Methodology Choice

Dynamics 365 offers two main approaches to consolidation.

• Consolidate Online: A "hard" consolidation where subsidiary balances are physically copied into a dedicated Consolidation legal entity. Use this when you need a rigid, auditable ledger of the consolidated numbers or complex tiered currency translations.
• Financial Reporting: A "soft" consolidation managed entirely within Management Reporter. Use this when the subsidiaries share the same chart of accounts and you want real-time aggregated reporting without creating dummy ledger entries.

Eliminations

You cannot count intercompany revenue twice. You must configure Elimination Rules to reverse the "Due to" and "Due from" balances. It is best practice to post these eliminations into a separate "Elimination Entity" rather than muddying the parent company ledger.

When to use it: Mandatory during every implementation to ensure strict segregation of duties and pass external IT audits.

The Security Hierarchy

Do not assign users directly to granular permissions. D365 uses a strict hierarchy.

• Roles: Assigned to the user (like Accounts Payable Clerk).
• Duties: Assigned to Roles (like Maintain vendor invoices).
• Privileges: Assigned to Duties (like the specific technical permission to open the invoice form and click Save).

Extensible Data Security (XDS)

Standard security restricts access to menus and forms. XDS restricts access to actual rows of data. Use XDS when a manager should only see the sales orders for their specific region. This applies filtering at the database level, meaning the user cannot bypass it via Excel add-ins or custom reports.

Segregation of Duties

Navigate to the System Administration workspace and configure Segregation of Duties rules. Define conflicts, such as stating that a user who has the duty to "Maintain Vendors" cannot also have the duty to "Pay Vendors". The system will automatically block administrators from assigning both roles to a single employee, preventing fraud.

When to use it: To enforce strict business process approvals, such as requiring a manager to sign off on a Purchase Requisition before a Purchase Order is generated.

Architecture

Use the Workflow editor to design the routing logic. You can build serial approvals (Person A then Person B) or parallel approvals (Person A and Person B must both approve simultaneously). Build conditional branching to auto-approve low-value requests.

Position Based Routing

A critical consultant best practice is to route workflows to Job Positions rather than specific User IDs. If you route an approval to "John Doe", the workflow breaks the day John resigns. If you route it to the "VP of Finance" position, the system automatically routes the approval to whoever is assigned that position in the HR module today.

Troubleshooting

If workflows stall, check the batch framework. Workflows rely on a background batch job to process messages. If the batch job fails, all approvals stop. Always ensure the workflow batch group is assigned to a dedicated, healthy batch server.

When to use it: When deploying the ERP in countries with complex, government-mandated statutory reporting or electronic invoicing requirements.

Electronic Invoicing and Reporting

Many countries (like Italy, Brazil, and India) require businesses to send digital XML invoices directly to the government tax authority for real-time validation. Dynamics 365 handles this via the Electronic Reporting (ER) framework. Consultants must download the specific country configurations from Microsoft Lifecycle Services.

Global Strategy

When rolling out D365 globally, use a "Global Template" approach. Build the core chart of accounts and supply chain processes to be identical across all countries. Then, enable the specific localizations only for the legal entities operating in those countries. This ensures corporate reporting remains standardized while local accountants stay legally compliant.

When to use it: Throughout the testing phases (especially UAT) and when preparing the architecture for a high-volume go-live.

Batch Design

Performance degradation is rarely a system fault. It is usually a scheduling fault. Never schedule heavy batch jobs (like inventory closing or MRP) during peak user hours. Architect batch groups to run overnight, and dedicate specific server nodes to handle heavy integrations so they do not steal CPU from end users typing in sales orders.

Master Planning

Master Planning (MRP) is the heaviest process in D365. Consultants must migrate clients to the Planning Optimization Add-in, which offloads the heavy MRP calculations from the D365 SQL database into a dedicated microservice, reducing runtimes from hours to minutes.

Data Management

Establish a rigorous cleanup strategy. Enable the built-in cleanup batch jobs for database logs, staging tables, and batch history. If staging tables are left unchecked, they will bloat the database and severely impact read/write performance.

When to use it: Every single month. Microsoft forces continuous updates to the cloud environment, and consultants must manage the testing lifecycle.

The Cadence

Microsoft releases four major service updates a year. Clients must take at least two of them. You can pause an update, but you cannot pause two consecutive updates. Proactive Quality Updates (PQUs) are released monthly for security and cannot be paused.

Regression Suite Automation Tool (RSAT)

Because the system changes constantly, manual testing is impossible. Consultants must implement RSAT. RSAT allows you to record a task (like creating a sales order) and play it back automatically against the new Microsoft release. If the update breaks the sales order process, RSAT flags it immediately.

Environment Strategy

Never apply an update directly to Production. Always apply the Microsoft service update to a Tier 2 Sandbox environment first. Run your RSAT suite, validate your ISV integrations, and obtain formal sign-off from the business owners before scheduling the Production update window.