# Solving Dynamics 365 — Finance & Supply Chain Management guides, full text > A practical reference for Microsoft Dynamics 365, Business Central, and the Microsoft business apps ecosystem — guides, comparisons, pricing, troubleshooting, and a glossary. 89 guides in this category. Author: Emil Björk, Microsoft business apps consultant, Gothenburg. Site index: https://www.solvingdynamics365.com/llms.txt. Every guide, every category: https://www.solvingdynamics365.com/llms-full.txt. --- # 1099 reporting for US in Dynamics 365 Finance How F&O handles US 1099 reporting — vendor classification, 1099 boxes, year-end generation, e-filing, and the recipient-copy distribution. Source: https://www.solvingdynamics365.com/guides/1099-reporting-in-f-and-o Section: Finance & SCM / Finance Published: 2026-06-20 Updated: 2026-08-25 In the United States, **1099 reporting** is the annual obligation to report payments made to certain types of vendors — independent contractors, professional services providers, attorneys, royalty recipients, interest recipients — to the **Internal Revenue Service (IRS)** and to the vendors themselves. Dynamics 365 Finance handles 1099 reporting natively for US-localised companies, with the workflow that turns transactional data into compliant filings. ## The 1099 forms Different forms apply to different payment types: - **1099-MISC** — miscellaneous income including rent, prizes, awards, medical / health payments. - **1099-NEC** — non-employee compensation; the dominant form for contractor payments (separated from MISC in tax year 2020). - **1099-INT** — interest paid. - **1099-DIV** — dividends paid. - **1099-K** — payments via third-party payment networks (Stripe, PayPal-style). - **1099-G** — government payments. - **1099-R** — distributions from pensions, retirement accounts. Each form has multiple **boxes** corresponding to different income categories within the form. ## Vendor 1099 classification Each vendor in F&O carries: - **Tax ID (TIN / EIN / SSN)** — the vendor's tax identifier; required for 1099 reporting. - **1099 form code** — which form applies (MISC, NEC, INT, etc.). - **1099 box** — which box within the form the payments report to. - **1099 minimum threshold** — payments below this amount per year aren't reported (default $600 for NEC, varies by form/box). Setting vendor 1099 classification correctly at onboarding is operationally critical — wrong classification at year-end leads to wrong filings. ## W-9 collection Best practice: collect a signed IRS **Form W-9** from every potentially-1099-eligible vendor before the first payment. The W-9 confirms the vendor's TIN and 1099 status. Without a valid W-9, the IRS requires backup withholding (typically 24%) on subsequent payments — substantial vendor friction. ## Backup withholding When backup withholding applies: - Each payment to the vendor withholds the configured percentage. - The withheld amount is remitted to the IRS separately. - Documented in F&O alongside the original payment. Most companies avoid backup withholding by collecting W-9s upfront; the cost of collecting upfront is much less than the operational burden of withholding and remittance. ## Year-end 1099 generation The annual workflow: 1. **Verify vendor data.** Audit every 1099-eligible vendor — TIN present, classification correct, address current. Vendors with errors hold up the year-end process. 2. **Validate transactions.** Identify all payments made during the tax year to 1099-eligible vendors. Confirm classifications. 3. **Run the 1099 statement.** F&O's **1099 statements** routine aggregates per vendor, per form, per box — preparing the report data. 4. **Review and adjust.** Some adjustments are typical: - Manual additions for non-AP payments (advance payments, payments made outside the system). - Manual exclusions for payments incorrectly classified. - Threshold checks. 5. **Generate the forms.** F&O produces: - **Vendor copies** — printable forms or digital PDFs distributed to each vendor. - **IRS filing** — the consolidated submission (paper or electronic). 6. **Distribute.** Vendor copies must reach vendors by January 31 of the following year for most forms. 7. **File with IRS.** Filing deadlines vary by form: - 1099-NEC: January 31. - 1099-MISC (paper): February 28. - 1099-MISC (electronic): March 31. - Penalties for late filing escalate by lateness duration. ## Electronic filing (e-filing) For 10+ forms, the IRS requires e-filing through their **FIRE** (Filing Information Returns Electronically) system or **IRIS** (newer Information Returns Intake System). F&O produces the file in the required format; the customer submits through the IRS portal. ## State 1099 Many US states also require 1099 reporting: - Some states participate in the **Combined Federal/State Filing Program (CFSF)** — federal filing also satisfies state. - Others require separate state filings with state-specific formats. F&O's localisation handles state-specific variations where the partner localisation has implemented them; verify per state. ## Corrections Issued 1099s that need correction: - **Corrected forms** — issued to vendor and IRS with a corrected indicator. - **Voided forms** — for filings that should be withdrawn entirely. Tracking correction history is part of the audit trail. **Common pitfalls.** - **Wrong vendor classification.** Treating a vendor as 1099-eligible when they shouldn't be (or vice versa) leads to wrong filings. - **Missing TINs.** Without a TIN, the form can't be filed. - **Late delivery to vendors.** Vendors who don't receive 1099s on time can't complete their own tax returns; relationship damage. - **Wrong box assignments.** Payments report under the wrong category. ## Operational reality US 1099 reporting is unglamorous but unforgiving. The IRS penalises errors and late filings. Year-end 1099 work should start in November (data clean-up) for January-end distribution. Mature operations have a documented runbook executed annually. --- # Alerts and notifications in Dynamics 365 Finance How F&O's alert framework surfaces important events — alert rules, due-date triggers, change events, delivery to action centre and email. Source: https://www.solvingdynamics365.com/guides/alerts-and-notifications-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-06-10 Updated: 2026-08-25 For users working in Dynamics 365 Finance and Supply Chain, much of the day-to-day intelligence comes from being told *when something happened* — a sales order shipped, a credit limit exceeded, a customer overdue, a production order completed, a workflow approval needed. The **alert framework** is the platform's built-in subscription mechanism that delivers these notifications without requiring custom integration. ## The model A **rule** specifies what to watch for. Each user can create rules against: - **Field changes** — when a specific field on a record changes (e.g. "alert me when this customer's credit limit is reduced"). - **Due dates** — when a record's due date approaches (e.g. "alert me 7 days before the sales order delivery date"). - **Creation / deletion** — when records of a type are created or deleted. - **Workflow events** — when a workflow stage transitions. Users create rules through the **Manage Alert Rules** action; admins can create system-wide rules that apply to all users matching criteria. ## Delivery Alerts deliver to: - **Action centre** — the bell icon in the F&O UI shows pending alerts. - **Email** — configurable per rule. - **Mobile push** — through the F&O mobile companion. - **Application Insights telemetry** — for system-level monitoring. A single rule can fire to multiple channels. **Common alert scenarios.** - **Credit risk** — alert credit manager when a customer's overdue balance exceeds a threshold. - **Delivery promises at risk** — alert customer service when a sales order's expected ship date is in the past with the order still unshipped. - **Inventory shortages** — alert procurement when stock falls below safety stock. - **Workflow timeouts** — alert manager when an approval hasn't been acted on within N days. - **Posting failures** — alert operations when batch job errors. - **High-value events** — alert leadership when a sales order over a threshold posts. ## Rules at scale F&O's alert framework is fine for individual user rules and a moderate number of system rules. For larger volumes — many users with many rules — performance can degrade because the framework checks every applicable rule on every change. For high-volume scenarios, alternative patterns: - **Power Automate flows** triggered by F&O events via virtual entities or Dual-write — more flexible, scales better. - **Application Insights alerts** — for system-level health rather than business events. - **Service Bus integration** — for downstream systems consuming events. ## Alert delivery preferences Users can configure per-rule: - Active hours (don't notify outside working hours). - Channels (Action Centre only, or also email). - Aggregation (one alert per event, or batched daily summary). Avoid alert fatigue — users overwhelmed with notifications start ignoring them, including the important ones. ## System-wide alerts Beyond per-user rules, system-wide alerts cover: - **Service health** — Microsoft-driven notifications for service issues. - **Critical batch failures** — operational-impact failures. - **Security events** — unusual access patterns, failed login attempts at scale. - **Capacity thresholds** — Dataverse storage approaching cap, API call usage approaching limit. These typically route to administrators or operations teams via configured action groups. ## Mobile and Teams Modern F&O integrates with Microsoft Teams for alert delivery: - An adaptive card in a Teams channel. - Interactive — user can act on the alert directly from Teams. - Coordinates with the broader Microsoft 365 notification surface. Mobile push notifications surface alerts on the user's phone, with one-tap navigation to the relevant record in the F&O mobile experience. **Limits.** - **Rule complexity** is bounded — sophisticated conditional logic across multiple records typically needs Power Automate. - **Visibility into rule firing** is limited — debugging "why didn't I get this alert" is harder than equivalent Power Automate flow run history. - **Performance at scale** — every change touches every applicable rule. **Common pitfalls.** - **Alert overload** — users create dozens of rules, get hundreds of alerts daily, ignore them all. - **Stale rules** — rules created for a long-gone process still fire and confuse users. - **No system-wide health alerts** — operations team finds out about problems from user reports rather than alerts. ## Operational discipline Curate alert rules deliberately. Audit periodically — retire what's not useful. Combine with Power Automate flows for complex cross-system orchestration. The framework is the daily-pulse mechanism for the operational team. --- # Allocations and allocation rules in Dynamics 365 Finance How F&O allocates costs and revenue across dimensions — ledger allocation rules, basis sources, percentage methods, and the periodic allocation cadence. Source: https://www.solvingdynamics365.com/guides/allocations-and-allocation-rules-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Updated: 2026-08-25 A central IT cost of $100,000/month needs to be spread across business units that benefit from it. A consolidated marketing spend gets reassigned to the brands that received the activity. Shared service costs need to push to the consuming departments. **Allocation rules** in F&O define how these distributions happen — automating what would otherwise be a manual journal exercise every period. ## The allocation problem Accounting captures cost where it's spent (a vendor invoice for IT services hits the IT department) but business analysis needs cost where it's consumed (each business unit's "true" IT cost). Allocations move postings from source dimensions to destination dimensions per defined rules. **Two flavours of allocation.** - **Ledger Allocation Rules** — the modern, configurable allocation engine. Period-end batch processing. - **Fixed allocation accounts** — older mechanism on individual accounts; less flexible, mostly being replaced. This article focuses on Ledger Allocation Rules. **Anatomy of an allocation rule.** - **Source** — what is being allocated. Defined by accounts, dimensions, or a journal type. - **Destination** — where it's being moved to. Defined by dimensions. - **Basis** — the proportion drivers (headcount, square footage, revenue %, prior period transactions). - **Method** — fixed percentage, basis-driven, formula. - **Posting** — offset account treatment. **Methods.** - **Fixed percentage** — distribute manually-specified percentages (40/30/30 across three BUs). - **Fixed weight** — weights (3:2:1) translated to percentages. - **Basis** — proportions computed from another data set (e.g. revenue per BU last month, headcount this month, transactions hit per BU). - **Spread evenly** — equal split across destination dimensions. - **Equally** — same as spread evenly. Basis methods are the most powerful — they adjust the allocation each period to current driver values, no manual update needed. **Basis sources.** - **Ledger balances** — prior period account balances (e.g. revenue) as the driver. - **Statistical measures** — non-financial measures (headcount, square footage) stored in F&O for this purpose. - **Formulas** — combinations of measures. Statistical measures are maintained per period — finance updates the headcount per department at month-end before running allocations. ## Source criteria What's being allocated: - **Main accounts** — IT cost account 6000. - **Financial dimensions** — only the IT department source. - **Currency** — only LCY. - **Date range** — current period. ## Destination dimensions How the destination is constructed: - **Pre-defined dimensions** — specific destination values. - **Wild-card** — all dimensions in scope. - **Derived** — destination dimensions calculated from the basis. **Running allocations.** 1. Source data is collected. 2. Basis is calculated per destination dimension combination. 3. Allocation amounts are computed. 4. The journal is proposed — review before posting. 5. Posting creates reversal entries on source and matching entries on destinations. Most teams run allocations as a sequenced step in the period close: after AR/AP, before consolidation. ## Step allocations Some costs flow through multiple steps — central → division → cost centres. Each step is a separate allocation rule; the order matters. F&O supports sequencing. ## Reciprocal allocations When two cost pools mutually allocate to each other (IT serves HR; HR serves IT), simple sequential allocation gets it wrong. Reciprocal allocation solves simultaneous equations to balance correctly. F&O supports reciprocal via specific rule configuration. ## Reversal and rerun If allocations need adjustment after posting: - **Reverse** the posted allocation. - **Adjust** the rule or basis. - **Re-run.** Always preserve the original posting as a reversed entry — audit trail of "what we allocated and why" matters for explainability. **Reporting.** - **Pre-allocation views** — show cost as originally posted, before reassignment. - **Post-allocation views** — show cost after allocation. Both views are usually needed: pre-allocation for fiduciary reporting (responsibility centre, where cost was incurred), post-allocation for managerial reporting (true business cost). **Common pitfalls.** - **Basis not updated.** Headcount or revenue measures stale; allocations use old proportions; results misleading. - **Allocation chain dependencies.** Step allocations run out of order; downstream rules see wrong source. - **Circular allocations not handled.** Without reciprocal logic, two-pool allocations settle wrong. - **Source/destination overlap.** A destination dimension is also part of source criteria; allocations cycle back. - **No reversal hygiene.** Failed allocations not reversed; cost reported both at source and at destination — double counted. ## Audit considerations Allocations are journal entries; auditors review the allocation rules and the basis data. Maintained allocation rule documentation (method, basis, last reviewed) helps audits move quickly. ## Practical scope Allocations are the right tool for repetitive period-end cost distributions. Strategic one-off cost reassignments (a project of restating prior periods) are usually better done as a discrete journal exercise — allocation rules are for the recurring, repetitive case. --- # AP automation and OCR in Dynamics 365 Finance How invoice automation works in F&O — vendor invoice journal, OCR extraction, three-way matching, approval workflow, and the partner ecosystem. Source: https://www.solvingdynamics365.com/guides/ap-automation-and-ocr-in-f-and-o Section: Finance & SCM / Finance Published: 2026-06-18 Updated: 2026-08-25 For enterprise organisations, accounts payable handles thousands of vendor invoices per month. Manual data entry from emailed PDFs is slow, error-prone, and expensive. **AP automation** — combining OCR for invoice data extraction, automated matching to purchase orders and receipts, and structured approval workflows — collapses the manual effort. Dynamics 365 Finance ships building blocks; partners deliver the operational platforms most enterprises use in practice. ## The vendor invoice journal F&O's central object for AP processing is the **vendor invoice journal** — an unposted holding area for invoices in process: - **Header** — vendor, invoice number, invoice date, due date, total. - **Lines** — what's on the invoice: line items, GL accounts, dimensions, taxes. - **Status** — Draft, Submitted, Approved, Posted, Cancelled. - **Attachments** — the original PDF for audit. - **References** — link to PO and receipt for three-way matching. Invoices in the journal aren't yet vendor-ledger entries; posting promotes them. **Capture — three options.** 1. **Manual entry** — a clerk reads the PDF and types the data. Slow, expensive, error-prone. Suitable only for very low volume. 2. **F&O native OCR** — Microsoft's built-in OCR (via AI Builder) reads the PDF and extracts vendor identity, invoice number, dates, totals, line items. The user reviews extracted data, corrects errors, then posts. Adequate for simple invoice layouts and low-to-moderate volume. 3. **Partner AP automation** — specialist platforms (Continia Document Capture, ExFlow, Documotor, Tungsten Network, ABBYY-based solutions) deliver: - High-accuracy OCR tuned for invoice layouts. - Per-vendor field-mapping templates that learn over time. - Three-way matching automation. - Sophisticated multi-step approval workflows. - Exception handling dashboards. - Integration to e-invoicing standards. For high-volume operations (hundreds to thousands of invoices weekly), partner AP automation is the practical choice. ## Three-way matching For invoices referencing purchase orders: - **PO** — what was ordered (quantities, prices, items). - **Receipt** — what physically arrived. - **Invoice** — what the vendor is billing. Matching all three before approving the invoice catches: vendor overbilling, missing receipts, mispriced lines, quantity discrepancies. F&O supports configurable tolerance thresholds — exact match, percentage variance, dollar variance. Mismatches outside tolerance route to exception handling. ## Approval workflow AP approval typically follows: - **Document validation** — completeness, vendor verification. - **Three-way match** — if PO-referenced, match the three. - **GL account assignment** — for non-PO invoices, the GL clerk assigns the right account. - **Department / cost-centre approval** — manager of the relevant cost centre signs off. - **Compliance review** — for high-value or unusual invoices. - **Final approval** — by AP lead or controller. Each step routes through F&O workflow with configurable conditions, escalation, and audit trail. ## Approval-on-mobile Approvers act from: - F&O web client. - F&O mobile app. - Microsoft Teams (with adaptive cards). - Email (action links). The multi-channel surface speeds approval cycles substantially. ## E-invoicing integration For jurisdictions with mandatory e-invoicing (Spain SII, Italy SDI, Mexico CFDI, Brazil NFe, EU's growing requirements), AP automation integrates with the country e-invoicing platforms: - Receive vendor invoices in structured e-invoice format directly (no PDF / OCR step). - Validate signatures and authenticity. - Process through the standard workflow. ## Posting Approved invoices post to: - Vendor ledger — creating the open AP entry. - General ledger — debit to expense / asset, credit to AP control. - Inventory ledger (if PO-referenced) — closing out the goods-received-not-invoiced accrual. - Project ledger (if project-referenced) — adding to project cost. The system enforces three-way match thresholds; over-tolerance differences require explicit acknowledgment. **Reporting and KPIs.** - **Days to approve** — workflow cycle time per invoice. - **Touchless rate** — % of invoices that flow PO → match → approve → post without manual intervention. - **Exception rate** — % that hit a mismatch or rejection. - **Early-payment discount capture** — invoices paid within the discount window vs not. - **Vendor-specific patterns** — vendors with consistent mismatches, late documentation, etc. **Common pitfalls.** - **Low OCR accuracy** — for poorly-formatted vendor invoices, OCR extraction is unreliable. Per-vendor templates help. - **Slow approval cycles** — invoices sit unapproved for weeks; late-payment penalties accumulate; vendor relationships strained. - **Three-way match tolerances too loose** — over-billing slips through. - **Three-way match tolerances too tight** — every legitimate variance becomes an exception. ## Operational reality AP automation is one of the highest-ROI projects in enterprise finance. Per-invoice processing cost typically drops from €20+ to under €5; cycle time from weeks to days. Most mid-to-large F&O customers run a partner AP automation platform alongside F&O's native capabilities. --- # Asset Management in Dynamics 365 Supply Chain How Dynamics 365 SCM's Asset Management module handles maintenance — work orders, preventive maintenance, condition monitoring, and the role of IoT. Source: https://www.solvingdynamics365.com/guides/asset-management-in-dynamics-365-scm Section: Finance & SCM / Finance Published: 2026-05-01 Updated: 2026-08-25 For asset-heavy operations — manufacturers with production equipment, utilities, transport fleets, building owners, energy companies — maintenance management is operationally critical. Downtime is expensive; reactive maintenance is more expensive than planned. Dynamics 365 Supply Chain Management ships an **Asset Management** module covering the full enterprise maintenance lifecycle. ## Asset registry A hierarchical **asset register** holds every maintainable asset: - **Asset** — a piece of equipment with identifier, model, location, criticality. - **Functional location** — where the asset lives (plant, line, area, building, room). - **Asset type and category** — classification for reporting and policy. - **Manufacturer, serial number, warranty** — for vendor management. - **Lifecycle status** — Active, In Storage, Disposed, Under Service. Assets are arranged in trees — a production line is a parent of its machines; a machine is a parent of its sub-assemblies; sub-assemblies are parents of components. Work orders attach at any level. ## Maintenance work orders The central object — a **work order** captures planned or unplanned maintenance work: - **Type** — Preventive, Corrective, Inspection, Improvement, Project. - **Asset / functional location** — what's being worked on. - **Description and detailed work** — what needs doing. - **Resources required** — internal technicians, external contractors, equipment. - **Materials required** — spare parts, consumables. - **Schedule** — start, end, priority, deadline. - **Status** — Created, Scheduled, In Progress, Completed, Posted. - **Actual time and materials** — captured as work progresses. ## Preventive maintenance Configurable **maintenance schedules** generate work orders automatically: - **Time-based** — every 90 days, every quarter, every year. - **Counter-based** — every 1,000 operating hours, every 100,000 miles, every 50,000 cycles. - **Condition-based** — when a sensor reading exceeds a threshold. - **Mixed** — whichever triggers first. Pre-defined **maintenance plans** bundle the required steps, parts, tools, and skills for each maintenance event, so the work-order template is reusable. ## Condition monitoring **Asset counters** track usage and condition values manually entered or auto-collected from IoT sensors. Thresholds trigger work orders when crossed. Common counters: operating hours, production count, temperature, vibration, pressure, oil quality. ## Spare parts Parts inventory ties to assets through **BOM-like structures** showing which parts apply to which assets. Work orders reserve and consume parts from inventory; stock-out warnings prompt re-ordering. ## Resource scheduling Maintenance resources have skills, certifications, and calendars. The schedule board (similar to Field Service) shows planned work orders against resources with conflict and load visibility. ## Cost accounting Every work order captures labour cost, materials cost, and external services cost. Total maintenance cost per asset, per asset class, per location feeds operational cost analysis. ## IoT integration Industrial IoT data through Azure IoT Hub feeds the condition-monitoring layer: - Real-time sensor values stream in. - Thresholds and ML anomaly detection trigger alerts. - Alerts auto-generate work orders. - Predicted failures drive preventive action before breakdown. This is the same pattern as **Connected Field Service** applied to internal assets rather than customer-installed equipment. **Reporting.** - **Asset performance** — uptime, MTBF, MTTR (mean time between failures, mean time to repair). - **Maintenance cost** — per asset, per type, per period. - **Compliance** — overdue preventive maintenance, audit-ready records. - **Reliability analysis** — patterns suggesting product or supplier issues. ## Where it fits Asset Management in SCM is enterprise-grade — comparable to dedicated CMMS (computerised maintenance management systems) like SAP PM, IFS Asset Management, IBM Maximo. Smaller operations may use simpler tools; SCM customers benefit from having maintenance integrated with the same ERP that handles finance, supply chain, and production. ## Operational reality Maintenance discipline is more important than the software. Configure the system thoughtfully; train the technicians; audit the data quality; review reports monthly. The software supports the discipline. --- # Batch jobs and batch groups in Dynamics 365 Finance How F&O's batch framework runs background processing — batch jobs, batch groups, schedules, server allocation, and operational monitoring. Source: https://www.solvingdynamics365.com/guides/batch-jobs-and-batch-groups-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-06-06 Updated: 2026-08-25 Dynamics 365 Finance and Supply Chain runs substantial background processing — periodic invoicing, master planning, inventory closing, electronic-reporting submissions, integration imports / exports. The **batch framework** is the platform's scheduler and execution engine; understanding it is essential to running a tenant at scale. ## Batch jobs A **batch job** is the unit of scheduled work. Each batch job: - **Caption** — human-readable description. - **Scheduled start** — when it first runs. - **Recurrence** — one-time, daily, weekly, monthly, hourly, or custom cron-style expressions. - **Status** — Scheduled, Executing, Ended, Error, Cancelled. - **Batch group** — assignment to a processing pool (see below). - **Tasks** — one or more units of work within the job. A single batch job can contain multiple **tasks**, each a separate process. Tasks run in defined sequence with dependencies; complex jobs orchestrate multi-step pipelines. ## Batch groups A **batch group** is a named processing pool that segregates batch jobs by purpose or priority: - **Default** — most batch work, general-purpose. - **High-priority** — for time-sensitive work that shouldn't wait behind lower-priority jobs. - **Long-running** — for jobs taking hours; isolated so they don't block shorter jobs. - **Integration** — for inbound / outbound integration processing. - **Reporting** — for report generation. - **Custom** — any business-specific pool. Each batch group has configured **parallelism** — how many threads / batch servers can run jobs in that group simultaneously. The split lets administrators allocate resources: critical integrations on a dedicated high-parallelism group; reporting on a lower-priority group. ## Batch servers Behind the scenes, **batch servers** are F&O application servers configured to process batch work. Each server is assigned to one or more batch groups; servers in the same group share the workload. Microsoft manages batch-server provisioning in SaaS F&O; the customer controls allocation through batch group configuration. ## Tasks and dependencies Within a batch job, tasks have dependencies — task B starts only after task A completes successfully. The model supports: - **Sequential** — A → B → C. - **Parallel** — A and B run concurrently, then C waits for both. - **Conditional** — task B runs only if task A succeeded; alternative task C runs if A failed. Complex multi-step nightly routines compose as task graphs within one batch job. **Common batch jobs.** - **Master planning runs** — typically nightly regenerative plans. - **Inventory closing** — month-end or quarter-end. - **Adjust Cost — Item Entries equivalent** — incremental cost recalculation. - **Currency revaluation** — period-end FX revaluation. - **Recurring invoicing** — subscription / recurring contract billing. - **Sales / purchase reservation cleanup** — release stale reservations. - **Electronic reporting submissions** — periodic statutory filings. - **Integration data exports** — to / from external systems. - **Job queue equivalent operations** — anything that doesn't need user interaction. ## Monitoring The **Batch History** workspace lists every batch job execution with: - Start time, end time, duration. - Status (success, failure, cancelled). - Detailed log per task. - Error messages and stack traces for failures. The **System administration** workspace surfaces batch health globally — currently running, queued, failed. Telemetry through Application Insights tracks long-term trends. **Failure handling.** - **Retry** — failed tasks can retry automatically per configured policy. - **Notification** — failures can trigger email or Teams notifications to operations. - **Manual intervention** — administrators can resume, restart, or skip failed tasks. - **Cascade behaviour** — a failed task can either halt subsequent tasks or skip and proceed. ## Throttling and resource management Heavy batch loads can compete with interactive users for resources. Manage through: - **Time-of-day scheduling** — heavy jobs during off-hours. - **Batch group allocation** — interactive-impacting jobs on isolated batch groups. - **Concurrent limits** per batch group. - **Job priority** within a group. **Common pitfalls.** - **Job piles up due to under-allocated batch group** — work queues but doesn't run because no server is available. - **Conflicting jobs with no isolation** — heavy inventory closing kills user-interaction performance. - **Failed jobs left in error** — operations team doesn't notice; downstream processes miss data. - **Schedule drift** — jobs scheduled to run at fixed times accumulate drift; reconsider scheduling weekly vs cron. ## Operational reality The batch framework is the operational engine of F&O. Configure batch groups thoughtfully; monitor execution daily; investigate failures promptly. Mature operations run hundreds of batch jobs daily without anyone noticing. --- # BOM versioning and engineering change in F&O How F&O handles BOM versioning, engineering change management, and the controlled evolution of product structures over time. Source: https://www.solvingdynamics365.com/guides/bom-versioning-and-engineering-change-in-f-and-o Section: Finance & SCM / Manufacturing Published: 2026-05-01 Updated: 2026-08-25 A manufactured product's [Bill of Materials](https://www.solvingdynamics365.com/glossary/bom) isn't static — components change, suppliers swap parts, design teams improve assemblies, regulations force substitutions, cost pressures drive material changes. Dynamics 365 Supply Chain Management handles this evolution through **BOM versioning** and **Engineering Change Management** — controlling who can change what, when changes apply, and how downstream operations honour the new design. ## BOM versions Each finished item can have multiple **BOM versions** — distinct BOM records for the same finished good, each with a validity window: - **From date** — when this version becomes effective. - **To date** — when this version is retired. - **Site** — different versions can apply per site (US production uses one BOM, EU production uses another). - **Status** — Approved, Active, Discontinued. When a production order is created for a date, the engine selects the BOM version valid for that date. Changing the design means activating a new version with a future effective date; production orders before the date use the old, after use the new. The transition is automatic. ## Multi-level BOMs Most real products are assembled from sub-assemblies, which have their own BOMs. Each level is versioned independently. A change to a sub-assembly's BOM cascades up — every parent BOM that references the sub-assembly is affected (though the engine resolves which version to use based on the date hierarchy). ## Routing versions Same model applies to **routings**. The same finished item can have multiple routing versions over time as operations change — new equipment, faster setup, restructured workflow. ## Engineering Change Management (ECM) Beyond simple versioning, **Engineering Change Management** adds formal control of the change process. Used in regulated, engineering-heavy, or PLM-integrated environments. The model: - **Engineering Change Request (ECR)** — someone proposes a change. Captured as a request with description, justification, scope (which products affected), priority. - **Review and approval** — workflow routes the ECR through stakeholders (design, manufacturing, procurement, quality, regulatory) for input and approval. - **Engineering Change Order (ECO)** — once approved, the ECR becomes an ECO that authorises specific changes to specific BOMs, routings, items, or formulas. - **Implementation** — the ECO drives the actual changes: new BOM versions created, items updated, routings revised, with effective dates aligning across the affected scope. - **Audit trail** — every step of the ECR/ECO lifecycle is logged with who, when, what. For pharma, medical devices, aerospace, automotive, and regulated industries, ECM is essential. For consumer goods or simpler manufacturing, basic BOM versioning may suffice. ## Item versioning Beyond BOMs, individual **items** can also be versioned in F&O — though more loosely. The item master holds the current value of each field; historical changes log to the change history rather than producing parallel item records. For "this item evolved" semantics, customers often create a new item rather than evolve the existing one. ## Integration with PLM Larger manufacturers run a dedicated **Product Lifecycle Management (PLM)** system — PTC Windchill, Siemens Teamcenter, Autodesk Fusion 360 Manage, Dassault Enovia — for design, CAD, document management, regulatory submission. PLM is the source of truth for design; F&O receives BOMs from PLM via integration. The pattern: - Design happens in PLM. - Approved designs export to F&O. - F&O production execution uses the released BOM version. Integrations exist for major PLM systems; the exchange typically covers BOMs, item masters, and engineering changes. ## Co-products / by-products and versioning Process manufacturing's co-product and by-product structures are versioned alongside formulas. A formula version captures the proportional ingredients, yields, and co/by-products as a unit; activating a new version changes them all together. **Common pitfalls.** - **Skipping versioning** — editing the same BOM repeatedly loses history. Production orders running with "current" BOM produce inconsistent results when the BOM changed mid-order. - **Future-dated versions without communicating** — the floor doesn't know the change is coming; surprises at the cutover date. - **ECM bypass for "quick" changes** — informal changes outside the ECM process undermine the audit trail and regulatory compliance. ## Operational reality Version discipline scales with manufacturing maturity. Smaller operations get by with basic BOM versions; complex products in regulated industries need full ECM. Match the rigour to the requirement. --- # Budget control in Dynamics 365 Finance How F&O's budget control enforces budgets at transaction posting — budget control rules, document overrides, the BC vs budgeting distinction. Source: https://www.solvingdynamics365.com/guides/budget-control-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Updated: 2026-08-25 **Budget control** in Dynamics 365 Finance enforces budget limits at transaction time — preventing or warning when a posting would exceed the approved budget for a dimension combination. It's distinct from **budgeting** (the planning process); budget control is the runtime enforcement. **The two concepts.** - **Budgeting** — the process of preparing budget figures: budget plans, budget revisions, approved budgets. - **Budget control** — the runtime mechanism that checks transactions against the budget at posting. A company can budget without budget control (the budget exists for reporting and variance analysis only). A company cannot budget-control without first having a budget. ## Why use budget control Public sector and government environments typically have legal requirements to not exceed appropriated budgets. Some private companies use it for cost discipline on capital projects, R&D programs, or shared service charge-backs. Most private companies do *not* use budget control — they review variance after the fact rather than blocking transactions in real time. ## Budget control configuration The setup includes: - **Budget control configuration parameters** — turn it on, define the start date. - **Budget cycle time spans** — the budget period (annual, quarterly, monthly). - **Budget models** — separate models for original, revised, transferred-in budgets. - **Budget classes** — what document types are budget-controlled (POs, vendor invoices, expense reports). - **Budget control rule** — define the allowable threshold (100% strict, 110% soft warn, etc.). - **Available budget formula** — what counts toward "used": confirmed orders, draft requisitions, received goods. ## Available budget formula The critical concept. When checking whether a $1,000 PO can be posted, the system computes available budget: - Original budget – preliminary commitments (requisitions) – firm commitments (POs) – actuals (invoices) – reserved (encumbrances) ± transfers. Each component is configurable. Different organisations define "available" differently: some count requisitions, some don't; some count goods receipts as actuals, some only invoices. ## Posting validation When a transaction is about to post: 1. Compute the budget control values per dimension combination affected. 2. Compute available budget. 3. Compare against the rule: - **Within budget** → post normally. - **Over the warning threshold** → display warning; user can still post. - **Over the strict threshold** → block posting; user must adjust or override. ## Override Authorised users can override block decisions with reasons captured. Override is audit-trail-tracked; override patterns reveal where budgets are systematically wrong. ## Dimension control Budget control operates at the **financial dimension** level: by department, by project, by cost centre, by program. The granularity determines whether you block at the program level (sum across multiple projects) or at the individual project level. Common pattern: enforce at the program level; report at the project level. ## The encumbrance pattern Public sector budget control often involves **encumbrances** — when a PO is approved, the budget is reserved (encumbered) even though no money has yet been spent. When goods are received, the encumbrance reduces and an actual increases. F&O supports this lifecycle natively for public sector deployments. **Budget planning vs operational budget.** - **Budget planning** — the multi-step process to create the budget: scenarios, what-if analysis, workflow approvals. - **Operational budget** — the approved budget that runtime budget control checks against. The output of budget planning is the operational budget; budget control reads only the operational budget. ## Budget revisions Mid-year budget changes (additional appropriations, transfers between programs) are recorded as **budget revisions**. Each revision is tracked; reporting shows original budget vs revised budget vs actuals. For public sector, revision audit trail is a compliance requirement. ## Budget transfers Moving budget from one dimension combination to another: - Source dimension loses budget. - Destination dimension gains budget. - Transfer document records the movement. Often subject to workflow approval — transferring funds between programs is a governance event. **Common pitfalls.** - **Budget control before stable budget process.** Implementing budget control without a clean budget creation process → control rejecting transactions because the budget is wrong. Sequence: stabilise budgeting, then add control. - **Too-granular dimensions.** Budget control at the lowest dimension level → many blocks for items that should aggregate at higher level. Use program/department, not specific G/L account. - **Available budget formula wrong.** Counting requisitions as committed when they shouldn't be → premature blocks. Adjust per policy. - **No override discipline.** Users override routinely without reasons; controls erode. - **Performance impact.** Budget control checks add posting overhead; for high-volume transactional environments, tune carefully. ## Private sector alternatives Most private companies skip budget control in favour of: - **Approval workflows on POs and invoices** — humans approve based on budget visibility but the system doesn't enforce. - **Periodic variance reports** — monthly review reveals over-runs after the fact. This soft approach is faster and less rigid; it requires managerial discipline rather than system enforcement. ## Public sector reality Government finance teams have stringent budget enforcement legal requirements. Budget control is the only practical answer; the implementation overhead is justified by the legal mandate. --- # Budget planning in Dynamics 365 Finance How F&O's budget planning module orchestrates the annual budget cycle — budget plans, scenarios, stages, workflow, and the integration with Excel and Power BI. Source: https://www.solvingdynamics365.com/guides/budget-planning-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Updated: 2026-08-25 The annual budget is one of the largest finance projects most organisations run — months of cross-functional input, multiple iterations, executive review, board approval. **Budget Planning** in F&O is the orchestration module that supports this process: defining the structure, gathering input from contributors, consolidating drafts, routing through stages, and producing the approved operational budget. ## Budget vs budget plan vs budget control Three distinct concepts: - **Budget plan** — the planning process: drafts, revisions, scenarios. - **Budget** — the approved output; what becomes the operational budget. - **Budget control** — runtime enforcement (separate topic). Budget planning ends when an approved plan is transferred to operational budget. **Architecture.** - **Budget planning process** — defines a budget cycle. - **Stages** — sequential steps (departmental input → finance review → executive review → board approval). - **Scenarios** — different versions (base, conservative, growth). - **Layouts** — templates defining the structure shown to contributors. - **Worksheets** — the Excel-like surface where amounts are entered. **The budget cycle.** 1. **Setup** — define stages, scenarios, layouts, contributors. 2. **Initiation** — create the budget plan; pre-populate from prior year + adjustments. 3. **Departmental input** — each manager enters their draft. 4. **Finance review** — consolidates; identifies issues. 5. **Executive review** — challenge, refine. 6. **Board approval.** 7. **Transfer to operational budget** — approved plan becomes the budget. Each stage has workflow approval; the system tracks who did what when. ## Layouts Define what contributors see: - **Rows** — accounts, dimensions, or hybrid. - **Columns** — periods (months, quarters), prior actuals, prior budget, variance. - **Calculation rules** — totals, percentages, ratios. A layout for a sales manager differs from one for a CFO; tailoring matters. ## Scenarios Parallel versions: - **Base case.** - **Stretch / growth.** - **Conservative.** - **Re-forecast** — mid-year revision. Contributors can fill multiple scenarios; comparison highlights sensitivity. ## Excel integration A signature feature: - Contributors can export their budget worksheet to Excel. - Edit in Excel — formulas, charts, modelling. - Import back to F&O. For executives more fluent in Excel than F&O, this is essential. The integration maintains data integrity through structured cells. ## Stage workflow Each stage has: - **Inputs** — what contributors can edit. - **Outputs** — what's locked when stage completes. - **Approvers.** - **Routing rules.** Movement between stages is controlled — finance can't bypass departmental input; executives can't override without protocol. **Allocations within budget planning.** - Top-down allocation — exec sets total; cascades to departments by formula. - Bottom-up roll-up — departments enter; aggregates to total. Many budgets combine both; top-down envelope with bottom-up detail. **Forecast vs budget.** - **Budget** — annual baseline. - **Forecast** — periodic updates reflecting current reality. Many organisations maintain a rolling forecast updated quarterly; F&O supports both as separate plans or as scenarios. **Power BI for budget reporting.** - Budget data flows to Power BI. - Side-by-side comparison with actuals. - Variance analysis dashboards. Standard reports + custom Power BI is the pattern. ## Driver-based budgeting Modern approach where budget is built from operational drivers: - Headcount × salary per role = total compensation. - Volume × unit price = revenue. - Volume × cost per unit = variable cost. Driver tables stored alongside budget; changes to drivers propagate to budget lines automatically. **Zero-based vs incremental.** - **Incremental** — last year + X% adjustment. - **Zero-based** — every line justified from zero. Zero-based is more rigorous, more effort. F&O supports both; the methodology is organisational choice. **Common pitfalls.** - **Budget plan never finalised.** Drafts iterate; stage never closes; operational budget delayed. - **Excel imports / exports out of sync.** Two versions of truth; reconciliation hell. - **Approval workflow bypassed.** Approvers sign for plans they didn't review; governance weak. - **No variance analysis.** Budget exists; nobody compares to actuals; budget becomes shelfware. - **Driver assumptions stale.** Driver-based model uses old volumes; budget doesn't reflect current trajectory. **Operational rhythm.** - **Setup** — pre-budget cycle definition. - **Cycle execution** — typically 8–12 weeks. - **Approved budget locked** — start of new fiscal year. - **Monthly variance review.** - **Quarterly re-forecast** (often). ## Strategic positioning Budget planning is one of finance's highest-stakes processes. F&O's module is full-featured but complex; investing in setup pays back across many budget cycles. For organisations with simpler needs (small businesses, single entity), the module may be overkill — Excel-based budgeting works fine. For enterprises with multiple legal entities, complex hierarchies, and demanding stakeholders, F&O Budget Planning is a real asset. The success of any budget process is more about discipline than software — clear timelines, accountable contributors, transparent decisions, post-cycle retrospectives. The tool supports the rhythm; the rhythm must come from leadership. --- # Call center channel in Dynamics 365 Commerce How the Commerce call center channel handles phone, catalog, and mail-order sales — customer service representatives, order taking, payment processing. Source: https://www.solvingdynamics365.com/guides/dynamics-365-commerce-call-center Section: Finance & SCM / Retail & commerce Published: 2026-05-01 Not every retail sale happens at a register or online. Catalog retailers, B2B sellers, subscription businesses, and many service-based commerce models rely on **call center sales** — customer service representatives taking orders by phone. **Dynamics 365 Commerce** models this as a distinct channel with its own configurations, workflows, and reporting. ## What a call center channel is A logical retail channel: - **Distinct from store and online channels.** - **Operated by CSRs (customer service representatives)** in a call center workspace. - **Phone-based or sometimes chat-based.** - **Order-centric** — orders captured during conversations, paid, fulfilled. Use cases: - **Catalog companies** — printed catalogs trigger phone orders. - **B2B distributors** — accounts call reps for orders. - **Subscription services** — initial subscription setup by phone. - **Specialty retail** — high-value or complex products requiring rep guidance. **Architecture.** - Channel database scoped to the call center. - CSRs use the **call center workspace** in F&O or D365 Commerce. - Same product catalog and pricing as other channels (with channel-specific overrides). - Same customer master. - Same inventory. ## Call center workspace The CSR's primary interface: - Search for customer or create new. - View customer history. - Build the order with line items. - Apply promotions and discounts. - Capture payment. - Process the order. - Manage holds, returns, and exchanges. The workspace is optimised for keyboard-driven, rapid order entry — different ergonomics from a graphical e-commerce site. ## Catalog management Catalog companies print physical or PDF catalogs: - **Source code** — identifier on catalog (or marketing campaign) that drives the call. - **Item references** — catalog item numbers map to system items. - **Promotional pricing** — specific to catalog campaign. When a customer calls, the source code helps the CSR know which catalog the customer is referencing — and which prices and promotions apply. ## Up-sell and cross-sell During order entry: - Suggested upgrades shown ("Premium version available for $X more"). - Cross-sell opportunities ("Customers who bought this also bought..."). - Bundle offers. CSR can accept or decline based on customer interest. The conversion-rate impact justifies the feature. **Order types.** - **Regular sale** — standard. - **Layaway** — partial pay, hold inventory. - **Subscription** — recurring shipment. - **Future ship** — delayed delivery. - **Continuity** — automatically renewing subscription series. Each has unique financial accounting and inventory commitment patterns. ## Payment processing Call center payment is high-risk — card not present, no signature, no chip. Patterns: - **Card token-based** — capture card via PCI-compliant entry; gateway returns token; token used for charge. - **Stored payments** — registered customers have saved cards; one-click charge. - **Manual capture** — CSR types card details into PCI-compliant entry; never written down. - **ACH / bank transfer** — for high-value B2B. **Fraud screening.** - Address verification (AVS). - Card verification value (CVV). - IP and behavioural risk scores. - Manual review queue for flagged orders. Call center fraud rates are higher than online (anonymous channel, manual entry); fraud controls compensate. ## Inventory commitment When the order is taken: - Inventory reserved at the warehouse. - If out of stock, options: - Backorder. - Substitute. - Cancel. - CSR sees real-time availability. **Shipping and fulfillment.** - Order routed to warehouse based on rules (closest, best stock). - Shipping method per customer preference and item characteristics. - Tracking info captured and emailed. Call center orders fulfill same as other channels — same warehouse, same shipping process. **Returns and exchanges.** - CSR handles return calls. - Issues RMA if needed. - Customer ships back; warehouse receives; refund processed. ## Customer history During the call, CSR sees: - Recent orders. - Open orders. - Returns. - Communications history. - Loyalty / lifetime value. Personal touch matters in call center sales — knowing the customer transforms the interaction. ## Continuity programmes Subscription-style: - Customer signs up for monthly box. - Auto-charge each month. - Auto-ship. - Cancellation handling. Continuity revenue is a meaningful portion of catalog company revenue; the system must manage the lifecycle reliably. **Reporting per channel.** - **Sales by source code** — which catalog or campaign drove revenue. - **CSR performance** — orders per hour, conversion rate, average order value. - **Channel comparison** — call center vs online vs store. - **Backlog and aging** — orders awaiting fulfillment. ## Integration with telephony Optional but common: - Caller ID looks up customer automatically. - Click-to-dial outbound. - Call recording for QA. - Integration with contact center platform. **Common pitfalls.** - **Source code drift.** CSRs forget to capture; marketing attribution wrong. - **Inventory commitment race conditions.** Two CSRs see same stock; both commit; one fails. - **Pricing overrides too easy.** CSRs giving discounts without authorisation; margin leakage. - **No QA on call recordings.** Recordings exist but no one reviews; coaching opportunity lost. - **Continuity opt-in confusion.** Customer didn't realise they signed up for recurring; complaints. - **Card decline handling poor.** Order goes into limbo; customer not notified; revenue lost. ## Operational discipline Call center sales is a measured business — conversion rate, average order value, items per order, calls per hour. Mature operations have dashboards per CSR and per shift, with coaching tied to specific metrics. The system supports the operation; the operational rhythm is the difference between a profitable channel and a money-losing one. ## Strategic positioning The call center channel is unfashionable but profitable for the right businesses. Some retailers (Land's End, L.L. Bean, gardening catalogs) drive significant revenue through it. Some B2B sellers run almost exclusively through it. D365 Commerce treats it as a first-class channel — same data, same fulfillment, integrated reporting. For organisations with this sales motion, the depth of capability is meaningful; for others, the call center channel is irrelevant. --- # Cash flow forecasting in Dynamics 365 Finance How F&O forecasts cash flow — cash flow forecast configuration, dependent transactions, scenario modelling, and the rhythm of weekly cash management. Source: https://www.solvingdynamics365.com/guides/cash-flow-forecasts-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Cash is what keeps a business running; running out of cash is a hard failure mode that even profitable businesses experience. **Cash flow forecasting** in F&O projects expected cash inflows and outflows over coming periods, giving the finance team visibility into upcoming squeezes or surpluses. The configuration is detailed; the operational discipline of using the forecast is where value materialises. ## Forecast scope A cash flow forecast aggregates: - **Opening cash balance** — bank accounts. - **Expected inflows** — sales orders to be invoiced, AR to be collected, etc. - **Expected outflows** — AP to be paid, payroll, taxes, etc. - **Period-end position** — projected balance. Over weeks or months, the forecast shows the cash trajectory. ## Cash flow forecast configuration Two main components: - **Cash flow forecast** — the master record naming the forecast. - **Dependent forecast configurations** — what feeds into it. Dependent configurations include: - Sales order forecasts. - Purchase order forecasts. - Vendor invoice forecasts. - Customer invoice forecasts. - Project transactions. - Recurring transactions (payroll, rent). - Subscription billing. - Manual entries (planned investments, financings). Each dependent configuration specifies which records flow in, how they're timed (by due date, by payment date), and what's included. **Timing methodology.** - **Sales orders** typically forecast by expected shipment + payment terms → invoice date. - **AR open invoices** forecast by due date + customer payment behaviour (historically delayed?). - **AP open invoices** forecast by due date + our payment plan. - **Purchase orders** forecast by expected receipt + vendor terms. The configuration includes adjusters — "customer X pays 10 days late on average" — to refine forecast accuracy. **Forecast horizon.** - **Weekly** — typical for short-term cash management. - **Monthly** — for medium-term planning. - **Quarterly** — for strategic reviews. Different forecasts can exist with different horizons and frequencies. ## Calculate Cash Flow Forecast The batch: - Runs against configured forecasts. - Pulls current data per dependent configuration. - Computes projected daily / weekly / monthly cash flows. - Updates the forecast tables. Result: a calendar of projected inflows and outflows; cumulative cash position. ## Scenario analysis "What if" modelling: - Multiple forecast versions. - "Base case" — current plan. - "Conservative" — slower collections, faster payments. - "Optimistic" — accelerated collections. - "Stress test" — major customer defaults. Comparison between scenarios reveals sensitivity and risk. **Inflow specifics.** - **Customer invoices outstanding** — by due date and customer behaviour. - **Sales orders not yet invoiced** — based on expected ship date. - **Subscription renewals** — for SaaS-like businesses. - **One-off receipts** — capital infusions, asset sales. **Outflow specifics.** - **Vendor invoices outstanding** — by due date and our payment policy. - **Purchase orders not yet invoiced** — expected receipt and vendor terms. - **Payroll** — recurring per period. - **Tax payments** — scheduled per tax type. - **Loan payments** — debt service. - **Investment / capex** — capital outlays. ## Currency Multi-currency forecast: - Bank accounts in various currencies. - FX assumed (current rates or forecast rates). - Consolidation to reporting currency. For multinational treasury operations, currency dynamics are part of cash forecasting. **Reporting.** - **Daily cash position** — today's actual balance. - **Weekly forecast** — 4–13 week rolling. - **Variance analysis** — actual vs forecast per week. - **Cash conversion cycle** — days sales outstanding, days payable outstanding, days inventory outstanding. Mature treasury operations have a dashboard with these metrics; checked daily. ## Integration with treasury management Larger organisations use specialty treasury management systems (Kyriba, FIS Quantum) for: - Bank account management. - FX hedging. - Investment of excess cash. - Debt management. F&O integrates via reports and APIs; treasury system overlays. **Common pitfalls.** - **Forecast not refreshed.** Static forecast vs dynamic reality; useless. - **Customer payment behaviour static.** Average days payable assumed; specific customer trends ignored. - **Manual entries forgotten.** Planned investment not added; surprise outflow. - **No variance review.** Forecast vs actual not compared; forecast quality doesn't improve. - **Single base case.** No scenarios; risk hidden. - **Stale FX rates.** Currency exposures miscalculated. **Operational rhythm.** - **Daily** — actual cash position check. - **Weekly** — forecast refresh and review. - **Monthly** — variance analysis; scenario update. - **Quarterly** — full forecast review with leadership. The cadence is the forecast's value — without it, the static forecast becomes stale and ignored. **Cash flow forecast vs budget.** - **Budget** — annual financial plan; P&L oriented. - **Cash flow forecast** — cash position over time; treasury oriented. Both are needed; different lenses on similar underlying business. ## Strategic positioning Cash flow forecasting is the discipline that prevents liquidity crises. The F&O module is comprehensive; the operational rhythm around it determines value. For organisations with seasonal cash dynamics, growth-driven working capital needs, or refinancing pressures, a robust forecast process is essential. For others, monthly forecasts are sufficient. Invest in the configuration upfront, in the weekly rhythm operationally, and in the leadership engagement with the forecast strategically. --- # Catch weight items in Dynamics 365 SCM How F&O handles variable-weight inventory like meat, cheese, and produce — the dual unit-of-measure model, catch weight tags. Source: https://www.solvingdynamics365.com/guides/catch-weight-items-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 A box of beef weighs about 18kg — but actually 17.642kg or 18.193kg depending on the box. The customer is invoiced for actual weight, but the warehouse counts and ships in boxes. This dual-unit reality — count one way, weigh another — is what **catch weight** handling in F&O addresses. Without catch weight, every box would have to be created as a unique item with its actual weight, which is operationally absurd. **The two units of measure.** - **Inventory unit** — what you count. Typically "EA" (each), "BOX", or "CTN". - **Catch weight unit** — what you weigh and price. Typically "KG", "LB". The item is set up with both. Each transaction line carries both quantities: a sales line might be 5 EA @ 87.5 KG at $4.20/KG. ## Item setup On the **Released Product**, enable catch weight: - **Catch Weight Item = Yes**. - **Inventory Unit** — counting unit. - **Catch Weight Unit** — weighing unit. - **Nominal Quantity** — expected weight per inventory unit (18 KG per BOX). - **Minimum Quantity / Maximum Quantity** — allowable variance (16–20 KG per BOX). The nominal lets the system pre-fill expected weight; the min/max constrains capture to flag obvious errors. ## Operational capture Every inbound and outbound transaction prompts for actual weight: - **Purchase receipt** — operator captures actual weight of received boxes. - **Production output** — actual weight per finished good unit. - **Inventory adjustment** — actual weight when adjusting count. - **Sales picking** — actual weight per picked unit. - **Production consumption** — actual weight consumed. Scale integration (electronic weigh scales connected to the warehouse mobile device or terminal) automates capture; without it, manual weight entry is the norm. ## Pricing Trade agreements (price lists) are typically per catch weight unit (per KG, per LB) — the inventory unit (BOX) is just the handling unit, but invoicing is by weight. A 5-BOX line at $4.20/KG with captured weight 87.5 KG bills at $367.50. ## Inventory valuation Both quantities are tracked at every step: - **On-hand** in inventory unit (250 BOX) and catch weight unit (4,500 KG). - **Cost** can be per inventory unit or per catch weight unit depending on costing setup. The cost engine handles both — most food companies cost per KG for accuracy. ## Lot-based variability Each lot of a catch weight item can have its own weight characteristics. Combined with item tracking (lot/serial), full traceability of weight per lot is captured: lot ABC has 50 BOX totalling 905 KG; lot DEF has 50 BOX totalling 890 KG. Same SKU, different per-unit weights. ## Catch weight tag Some operations track individual unit weights through a **catch weight tag** — a barcode label printed at production or receipt, capturing the specific unit's weight. When the unit is sold, the tag is scanned and the system pulls the exact weight. This is the high-end pattern for traceability and accurate invoicing. ## Reservation and picking Catch weight complicates reservation: - Reserving 100 KG when each box is 17.5–18.5 KG means reserving 5 or 6 BOX. - Picking might short or over the reservation weight; the order is adjusted at confirmation. The reservation engine has catch-weight aware logic, but warehouse picking flows need to handle the variability — the picked weight is rarely the planned weight to the gram. ## Integration with WMS Mobile warehouse devices integrated with scales capture weights in line with pick/put-away. Without integration, operators handwrite weights and key them in later — error-prone and slow. **Common pitfalls.** - **Catch weight added to existing item.** Switching an item from non-catch-weight to catch-weight is operationally painful; existing inventory must be re-weighed. - **Variance limits too tight.** Real-world weights exceed the min/max; receipts blocked; warehouse frustration. - **Variance limits too loose.** Bad data slips in; weight totals wrong. - **Pricing unit confusion.** Trade agreement set per BOX instead of per KG; invoices wrong. - **Costing unit mismatch.** Costed per BOX (nominal weight) but sold per KG (actual weight); margin calculation noisy. ## Regulatory compliance Food traceability (FSMA, EU Reg 178/2002) often requires per-lot weight tracking for recall scenarios — knowing exactly how much weight was distributed to which customers per lot. Catch weight + item tracking achieves this in F&O. ## When you need it Catch weight is essential for: meat, poultry, fish, cheese, fresh produce, bulk chemicals, anything weighed in handling units that vary. It's overkill for items that are dimensionally fixed. ## Operational discipline Catch weight depends on accurate weight capture at every step. Scale integration, operator training, and exception monitoring (weights outside expected variance) are essential. Without that discipline, the precision the module enables is illusory. --- # Chain of Command extension model in F&O How Chain of Command lets X++ developers extend F&O standard logic safely — wrap methods, call next, and the upgrade-safe pattern. Source: https://www.solvingdynamics365.com/guides/chain-of-command-extension-model-in-f-and-o Section: Finance & SCM / AL & X++ development Published: 2026-06-08 In the modern Dynamics 365 Finance and Supply Chain platform, customisation happens through **extensions** — separate models that augment Microsoft's standard code without modifying it directly. **Chain of Command (CoC)** is the X++ language pattern that makes this work safely: an extension method *wraps* a standard method, runs its own logic, and calls *next* to continue the standard execution. The result is upgrade-safe customisation that survives platform updates. ## The pre-extension world In Dynamics AX (the predecessor to F&O), customisation typically meant editing Microsoft's code directly — adding lines to `salesTable.insert()` or `purchTable.update()`. This made upgrades painful: every customisation had to be re-merged with the new platform version, and the more customisations, the worse the upgrade. ## The extension model Modern F&O forbids direct modification of Microsoft objects. Instead, developers write extension models that add or modify behaviour through: - **Class extensions** — add methods or fields to standard classes. - **Table extensions** — add fields, methods, indices, relations. - **Form extensions** — add fields, controls, datasources. - **Chain of Command** — wrap standard methods to inject custom logic. ## Chain of Command — the mechanics A CoC method in an extension class: ```x++ [ExtensionOf(classStr(SalesTableForm))] final class SalesTableForm_Extension { public void init() { // Custom code before standard method info("About to init"); next init(); // Call the standard method // Custom code after standard method info("Finished init"); } } ``` The `[ExtensionOf]` attribute tells the compiler the class wraps `SalesTableForm`. The method name matches a standard method; `next init()` calls the next implementation in the chain — eventually reaching Microsoft's standard. The extension method can do work before, after, or instead of (by omitting `next`). ## The chain Multiple extensions can wrap the same method. They form a chain: - Microsoft's standard at the base. - Extension A wraps it. - Extension B wraps Extension A. - The user-facing call goes through B → A → standard. Each extension's `next` calls the next layer down. The order is determined by the model installation order; deterministic but customers don't typically design for specific chain orders. **What can be wrapped.** - **Public and protected methods** of standard classes, forms, and tables. - **Static methods** — also wrappable. - **`new` and `dispose` methods** — for lifecycle injection. - **Form-level methods** — for UI behaviour modification. Private methods cannot be wrapped — they're encapsulated implementation details. **Common CoC patterns.** - **Pre-validation** — wrap `validateWrite()` to add custom validation rules. Call `next` only if custom rules pass. - **Post-creation hooks** — wrap `insert()` to do follow-on actions (notifications, integration triggers) after successful insert. - **Behavioural override** — wrap `update()` to suppress or modify standard behaviour under specific conditions, then conditionally call `next`. - **Audit logging** — wrap any modify method to log changes to a custom audit table. - **Integration triggers** — wrap post-completion methods to trigger external integrations. ## CoC vs event handlers F&O supports two related patterns: - **Chain of Command** — wraps methods; can modify the call chain before, after, or instead of. - **Event handlers** — subscribe to predefined events; can't suppress or modify the call chain, only observe. CoC is more powerful (can intercept and modify); event handlers are more isolated (purely observational). Choose based on whether you need to alter behaviour or just react to it. ## Performance and overhead Each CoC layer adds a small overhead — method-call indirection through the chain. For high-frequency methods (called millions of times), CoC overhead can add up. Profile if a heavily-wrapped method becomes a bottleneck. ## Upgrade safety This is the whole point. When Microsoft releases a new platform version: - Standard code changes — CoC wraps it as before; chain continues to work unless Microsoft removed or renamed the wrapped method. - New behaviour — CoC extensions still apply; the new behaviour layers in alongside. - Breaking changes — Microsoft documents deprecated methods; CoC code referencing them needs update. For the most part, CoC code survives platform updates without modification — the dramatic improvement over the AX-era customisation model. **Common pitfalls.** - **Forgetting `next`** — the extension intercepts and never calls Microsoft's code. Side effects may surprise. - **Calling `next` in wrong position** — putting custom logic after `next` when it should be before, or vice versa. - **Order-dependent chains** — when multiple extensions wrap the same method, behaviour can depend on installation order. Avoid. - **Long-running CoC** — heavy work inside a wrap can slow the standard operation. ## Operational reality CoC is the foundation of modern F&O customisation. Developers fluent in it produce maintainable, upgrade-safe extensions; those who try to revert to direct modification cannot in the SaaS model. The discipline pays back across years of platform updates. --- # Clienteling in Dynamics 365 Commerce How clienteling works in Dynamics 365 Commerce — associate-facing tools, customer profile, recommendations, and the integration with marketing and service. Source: https://www.solvingdynamics365.com/guides/clienteling-in-dynamics-365-commerce Section: Finance & SCM / Retail & commerce Published: 2026-05-01 **Clienteling** is the practice of turning a store associate into a personal service agent for individual customers — knowing the customer's history, preferences, recent interactions, wish list, and using that knowledge to deliver a personalised in-store experience. Dynamics 365 Commerce makes clienteling first-class through the **Store Commerce app**, with tools designed to turn a till operator into a personal shopper. ## The customer profile When an associate pulls up a customer in Store Commerce, they see: - **Recent purchases** across channels — what the customer bought in-store and online, across the company. - **Returns history** — what came back and why. - **Loyalty tier and points balance** — current status with the loyalty programme. - **Wishlist and saved items** — what the customer has marked for future purchase. - **Preferences** — sizes, brands, dietary restrictions, communication preferences. - **Recent interactions** — service cases, complaints, recent emails, recent in-store visits. - **Open orders** — current orders in any status — placed online for pickup, shipped, awaiting receipt. - **Spending patterns** — total spend this year, average order value, frequency. This view bridges what customer service / CRM / loyalty systems usually scatter across multiple tools. ## Personalised recommendations Combined with AI-driven recommendations, the associate sees product suggestions for the customer: - **Based on purchase history** — "customers who bought what you bought also bought…". - **Based on browsing** — items the customer viewed online but didn't buy. - **Cross-sell** — complements to recent purchases. - **Replenishment** — items the customer regularly reorders. The associate uses these as conversation starters, not robotic scripts. ## Outreach Clienteling supports proactive communication: - **Save the sale** — when a customer browses online and leaves, the associate can reach out with a personalised note. - **Birthday / anniversary outreach** — automated or manual based on customer profile. - **New arrival notifications** — when products matching a customer's preferences arrive, prompt the associate. - **Post-purchase follow-up** — care instructions, thank-you, satisfaction check. Outreach happens via the customer's preferred channel (email, SMS, WhatsApp, even physical mail), with templates that personalise to the recipient. ## Appointment booking Customers can book in-store appointments — personal shopping sessions, consultations, fitting appointments — through the customer-facing portal. Associates see the day's appointments on their dashboard and prepare ahead of arrival. ## Sales attribution Sales the associate makes (whether at the till or remote via order-from-home flows) attribute to the associate for commission and performance recognition. The data drives store-level performance management. ## Integration with marketing Customer Insights – Journeys campaigns reach clienteling-tier customers with channel preferences honoured. The clientelling-aware associate sees recent marketing touches so the conversation isn't disconnected. ## Integration with service Open cases or recent complaints from Customer Service surface in the customer profile — the associate knows that the customer was on the phone with support last week, can acknowledge it, follow up gracefully. **Common patterns.** - **High-touch retail** — luxury, jewellery, beauty, fashion — where clienteling drives meaningful revenue. Associates own a book of named customers. - **B2B retail** — wholesale showrooms where the same buyer-customers return regularly. - **Specialty stores** — categories where product knowledge and customer relationship matter (wine, cigars, art, audiophile). ## Where it fits less Fast-moving, low-touch retail (convenience stores, fast fashion) where transactions are anonymous and high-volume. Clienteling overhead doesn't pay back. ## Operational reality Clienteling is as much about culture as software. Associates need to value the relationship; managers need to coach toward it; metrics need to reward repeat-customer business not just one-time transactions. The technology supports the discipline. --- # Co-products and by-products in Dynamics 365 Supply Chain How F&O handles process manufacturing's multi-output reality — formulas, co-product allocation, by-product accounting, and the integration with planning. Source: https://www.solvingdynamics365.com/guides/co-products-and-by-products-in-f-and-o Section: Finance & SCM / Manufacturing Published: 2026-05-01 In process manufacturing, a single production run often produces *multiple* outputs from the same inputs — meat processing yields prime cuts and trimmings; oil refining produces multiple fractions; chemical synthesis generates targeted products and unavoidable side products. Dynamics 365 Supply Chain Management's **co-products** and **by-products** capabilities handle this multi-output reality natively, where discrete manufacturing's BOM model would force awkward workarounds. **The distinction.** - **Co-product** — a deliberately-produced output with significant economic value, planned for and intended. Co-products are why the production runs. In meat processing, prime cuts and trimmings are both co-products of butchery — both are intended commercial outputs. - **By-product** — an unavoidable output of the process, typically of lower or marginal value. By-products aren't why the production runs but they're unavoidable. In meat processing, bone meal might be a by-product. In oil refining, sulfur extraction produces sulfur as a by-product (though increasingly commercially valuable, so the line blurs). The distinction matters for cost accounting — co-products typically share production cost in proportion to their value (or other allocation basis); by-products typically credit production cost (recovery) rather than absorbing it. ## Formulas and outputs A **formula** in F&O describes a process production run: - **Input lines** — ingredients consumed with proportional quantities and yields. - **Output lines** — the products produced: - **Primary product** — the main intended output. - **Co-products** — additional intended outputs. - **By-products** — unavoidable secondary outputs. Each output has a yield (how much is produced per batch), a cost allocation rule, and inventory handling. **Cost allocation.** - **Co-products** — production cost is allocated across them by one of several rules: by value (relative selling price), by volume, by weight, by fixed percentage, by user-defined formula. The total production cost is split proportionally. - **By-products** — typically use **cost reduction** — the by-product's nominal value reduces the production cost absorbed by the primary product. By-product nominal value is configurable per item. The choice of allocation rule affects margin reporting per output. For commodity processing (oil refining), the allocation rule materially affects which products appear profitable. ## Planned co-products in batch orders Process **batch orders** (the process-manufacturing equivalent of production orders in discrete) plan inputs and outputs together. Planning a batch produces all the outputs simultaneously — you can't choose to make just the primary without also making the co-products and by-products. This has supply-chain implications: planning to make primary product A produces co-product B automatically, increasing B's inventory regardless of whether B is in demand. Master planning has to balance the co-product output against demand for all outputs. ## Co-product master planning The planning engine considers all outputs: - Demand for primary product A pulls batch orders that also produce co-product B. - Demand for co-product B is partially or fully covered by the batches running for product A. - If B has higher demand than A's batches produce, additional batches are planned solely for B (or alternative formulas if available). - If B has lower demand than is produced, B accumulates in inventory. The complexity multiplies with multiple co-products; planning configuration deserves careful attention. ## Catch weight Process manufacturing often combines co-product output with **catch weight** — products priced per unit but inventoried by weight (a cheese wheel = 1 piece but with variable kg per piece). Catch weight tracks both unit and weight; pricing per weight, inventory per piece. Common in dairy, meat, fish. ## By-product disposal Some by-products have zero or negative value (waste streams). Those need accounting for disposal cost, possibly with environmental compliance reporting alongside the operational data. ## Yields and shrinkage A formula's yield is configurable (e.g. 1000 kg input → 950 kg primary + 30 kg by-product + 20 kg shrinkage / waste). Actual yield variance from formula is posted as variance. Operational discipline tracks formula yields vs actual to identify process improvements or formula adjustments. **Common pitfalls.** - **Treating co-products as separate production runs** — separate orders for each output with manual coordination, fragile and expensive. - **By-product cost-reduction value out of date** — by-product's market value changed; the configured value doesn't reflect reality; margin reporting becomes wrong. - **Catch-weight items modelled without catch weight** — pricing and inventory go wrong on every transaction. ## Operational reality Process manufacturing in F&O is one of the deepest configuration areas. Engage a partner with proven process-manufacturing experience; pilot carefully; iterate on the formula structure as actual operations reveal what works. --- # Consignment inventory in Dynamics 365 SCM How F&O handles consignment inventory — vendor-owned stock on customer premises and customer-owned stock at our locations, the accounting and operational rules. Source: https://www.solvingdynamics365.com/guides/consignment-inventory-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 **Consignment inventory** is stock physically held by one party but legally owned by another. The vendor places goods at the customer's warehouse; ownership transfers only when the customer consumes them; cash settles after consumption. F&O has native consignment support in two directions — vendor-owned consignment at your locations (you hold) and your-owned consignment at customer locations (they hold) — with distinct workflows for each. **Why companies use consignment.** - **Vendor side** — keeps stock at the customer's hand without forcing a sale; customer can't run out, vendor doesn't carry the AR. - **Customer side** — no inventory ownership, no carrying cost, no obsolescence risk until consumed; cash only flows when value is realised. It's a working capital and risk-sharing arrangement. Common in automotive (tier-1 suppliers consign to OEMs), MRO consumables (Grainger-style vendor-managed), and high-value commercial inventory. ## Vendor-owned consignment in F&O You hold the stock; the vendor owns it. Setup: - A separate **location** or **warehouse** flagged as consignment. - Items configured to recognise consignment. - Vendor agreement structure (consignment replenishment order). Workflow: 1. **Consignment replenishment order** — a special PO type that brings vendor stock into your location without posting an inventory financial transaction. Stock arrives, on-hand increases at your location, but the inventory G/L account does *not* increase; the items are not yet owned. 2. **Consumption** — when the items are consumed (issued to a production order, sold to a customer), an **inventory ownership change journal** posts. This recognises: - Inventory ownership transfer from vendor to your company. - Vendor invoice receipt (typically auto-generated against the consignment vendor). - The financial entries that would have happened on a normal purchase. 3. **Settlement** — the vendor invoice is paid normally through AP. The trick is the **deferred ownership recognition**. Inventory on-hand counts the consignment stock; inventory value does not. **Two reporting realities.** - **Physical on-hand** — includes consignment stock. - **Financial on-hand** — excludes consignment stock until consumed. Standard reports show physical; financial reports filter out consignment. Mixing them up leads to wrong asset valuations or wrong availability calculations. ## Customer consignment — your stock at their location F&O models this with: - A site / warehouse representing the customer location. - Transfer orders move stock from your DC to the customer's consignment warehouse — ownership stays with you. - Sales are reported when the customer consumes — typically by importing customer consumption reports as sales orders against the consignment warehouse. ## Consumption-based billing Two patterns: - **Customer self-reports consumption** — customer uploads a periodic file; F&O imports it as sales orders, invoices generated. - **Vendor-managed inventory (VMI)** — vendor sends a replenishment proposal; customer confirms; vendor invoices for the delta. Both depend on accurate consumption data and trust between parties. ## Pricing Consignment doesn't change pricing logic — sales prices apply at consumption time per the trade agreements in place at that date. Some contracts include price protection (the price at delivery, not at consumption) for stable budgeting; F&O supports both via trade agreement effective dates. ## Replenishment For high-volume consignment locations, automated replenishment is standard: - Min/Max coverage on the consignment warehouse triggers replenishment when below min. - Transfer orders or vendor consignment POs auto-suggested. - Vendor-managed inventory: vendor reads our consumption data via EDI/API, sends shipment without our PO. ## Returns and obsolescence Consigned stock that doesn't sell: - **Returned to vendor** — vendor-owned consignment can be returned without financial transaction (we never owned it). - **Customer returns at customer site** — typically a periodic reconciliation, with credit notes for damaged or unsold stock. - **Obsolete consignment** — handled by negotiation; contractual terms determine ownership transfer or scrap. **Common pitfalls.** - **Treating consignment as normal stock.** Posting financial transactions at receipt; vendor stock booked as asset; messy reversals later. - **No consumption discipline.** Items consumed without journal entry; physical and financial diverge over time. - **Reconciliation skipped.** Periodic confirms between physical count, vendor records, customer records prevent year-end surprises. - **Mixing ownership in one bin.** A bin holding both consignment and owned stock; ownership tracking breaks. - **Tax treatment confusion.** Consignment crossing borders has complex VAT/customs implications; consult tax advisors. ## Operational discipline Consignment requires more accounting attention than normal inventory because the physical and financial worlds are deliberately decoupled. The reward is working capital advantage and stronger commercial relationships, but only with discipline in posting, reconciliation, and reporting. --- # Consolidations in Dynamics 365 Finance How F&O handles financial consolidation across legal entities — consolidation companies, methods, elimination rules, currency translation. Source: https://www.solvingdynamics365.com/guides/consolidations-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 For multi-entity groups, consolidated financial statements show the group as a single economic entity. F&O's **Consolidation** module handles much of this natively — collecting subsidiary data, translating currencies, aggregating to a consolidation company. For groups with simpler structures, F&O alone may suffice; for complex groups, dedicated consolidation platforms (OneStream, BPC, Tagetik, Anaplan) layer on top. **The architecture.** - **Subsidiary legal entities** — each with its own ledger. - **Consolidation company** — a dedicated F&O legal entity for consolidated results. - **Consolidation account groups** — the chart of accounts for consolidated reporting. - **Account mappings** — subsidiary accounts to consolidation accounts. The consolidation company doesn't operate transactional business — it's a reporting entity. **Consolidation methods.** - **Purchase (acquisition)** — full consolidation; subsidiary fully owned or majority-owned. - **Equity** — for significant influence (typically 20–50%); single line "investment in associate." - **Proportional** — for joint ventures. - **Pooling of interests** — historical method. Each method affects how subsidiary numbers flow into consolidated. ## Currency translation For multi-currency groups: - **Closing rate** — balance sheet items. - **Average rate** — P&L items. - **Historical rate** — equity items. Translation differences accumulate as Cumulative Translation Adjustment (CTA) in equity — IFRS / US GAAP requirement. **The consolidation process.** 1. Subsidiary periodic closes complete. 2. Consolidation company runs the consolidation routine. 3. Subsidiary balances pulled (via direct database read in same tenant or file import across tenants). 4. Currency translation applied. 5. Account mapping applied. 6. Consolidation entries posted to consolidation company. This is automated; the manual steps are typically the elimination journals (next). ## Eliminations Cross-entity transactions need elimination: - **Intercompany sales / COGS** — reverse on both sides. - **Intercompany AR / AP** — net to zero. - **Intercompany dividends** — eliminate. - **Investment in subsidiary** — eliminate against subsidiary equity. - **Unrealised intercompany profit in inventory** — defer. - **Goodwill calculation** — recognised at acquisition. F&O can record elimination journals, but doesn't automate them — elimination rules are manual. ## Intercompany reconciliation Before eliminations: - AR of Entity A toward Entity B = AP of Entity B toward Entity A. - Sales of Entity A to Entity B = COGS of Entity B from Entity A. If they don't match, the elimination won't net to zero; investigate. Mature finance teams reconcile intercompany monthly as a pre-consolidation step. ## Account mappings Subsidiary accounts often differ from group: - Subsidiary local chart for statutory reporting. - Group consolidation chart for IFRS or US GAAP. - Mapping rules per subsidiary. The mapping is maintained per subsidiary; new accounts must be mapped or they go to a "unmapped" suspense. ## Minority interest (non-controlling interest, NCI) For partially-owned subsidiaries: - Subsidiary's profits split between parent's share and NCI. - NCI shown as separate equity line. - F&O can capture but elimination logic is manual. ## Goodwill Difference between acquisition cost and net assets acquired: - Recognised on consolidation. - Tested for impairment annually. - Manual journal entries in consolidation company. **Reporting at consolidation.** - **Consolidated trial balance.** - **Consolidated P&L.** - **Consolidated balance sheet.** - **Consolidated cash flow statement** — requires additional analysis. - **Notes and disclosures** — for IFRS / GAAP reporting. Cash flow at group level is the hardest — F&O has cash flow at entity level; group cash flow typically built in Excel or Power BI. **Comparison with dedicated consolidation tools.** - **OneStream, BPC, Tagetik** — purpose-built; full eliminations automation, multi-method support, disclosure management. - **F&O native** — basic consolidation; manual eliminations; limited disclosure features. For groups with fewer than 10 entities and simple intercompany flows, F&O native is sufficient. For groups with 50+ entities, complex eliminations, M&A activity, dedicated tools win. ## Multi-tenant scenarios When subsidiaries are on separate F&O tenants: - File-based import for consolidation. - More complex; longer cycle. - Greater opportunity for reconciliation gaps. Single-tenant multi-entity consolidation is significantly easier. **Common pitfalls.** - **Manual eliminations not automated.** Each cycle re-types the same eliminations; errors creep in. - **Account mapping drift.** New subsidiary accounts unmapped; sit in suspense. - **Currency rate errors.** Wrong rate applied; consolidation off by material amounts. - **No reconciliation discipline.** Intercompany not reconciled before consolidation; eliminations imbalanced. - **Late close cascades.** Subsidiary close delayed; consolidation delayed. **Operational rhythm.** - **Monthly** — consolidation cycle. - **Quarterly** — full review with audit-level rigour. - **Year-end** — audited consolidated financial statements. For quarterly reporting companies (most public companies), the rhythm is rigorous; first 5 business days of next month is a typical target for monthly consolidation. ## Strategic positioning F&O consolidation is functional and improving each wave. For most multi-entity groups using F&O across all entities, it covers the core need. For complex groups with frequent M&A, multi-currency exposure, or sophisticated disclosure needs, augmenting with a dedicated consolidation platform is common. The decision: scope of complexity vs investment in tooling. F&O's strength is integration with the source data; dedicated tools' strength is the depth of consolidation features. Combined intelligently, the architecture serves both operational accuracy and reporting demands. --- # Cost management and inventory closing in F&O How Dynamics 365 Supply Chain handles inventory costing — closing runs, recalculation, marking, and the differences from Business Central. Source: https://www.solvingdynamics365.com/guides/cost-management-and-inventory-closing-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 Where Business Central runs Adjust Cost — Item Entries as a routine, **Dynamics 365 Supply Chain Management** has a deeper, more configurable inventory costing engine centred on the **inventory closing** process. Understanding it is essential for anyone running F&O at scale. ## The cost-management module F&O's **Cost Management** workspace coordinates: - **Item models** — costing methods per item (FIFO, LIFO, Weighted Avg., Date, Standard Cost, Moving Average). - **Closing runs** — periodic recalculation of inventory costs to ensure inbound costs flow to outbound transactions. - **Adjustments** — manual corrections to specific item ledger entries. - **Inventory recalculation** — without locking inventory, recalculate cost without closing the period. - **Marking** — manually link specific outbound transactions to specific inbound layers (for serial-tracked or specific costing scenarios). - **Cost rollups** — for standard-cost items, roll up component costs to finished goods. ## Inventory closing The headline operation. **Inventory closing** is a date-bound process that: 1. Identifies all open inventory transactions up to a chosen closing date. 2. Matches outbound transactions to inbound transactions based on the item's costing method (FIFO matches earliest open inbound; LIFO matches latest; Weighted Avg. computes the moving average). 3. Posts adjustment entries to reconcile cost. 4. Locks inventory transactions before the closing date — they cannot be edited without explicit reopening. This is more powerful than BC's adjustment routine: it produces a **closed period of inventory transactions** that auditors can trust, with locked records. ## Per-item closing Closing can run for selected items only — useful when investigating discrepancies on one item without disturbing the whole inventory. ## Inventory recalculation A lighter-touch alternative that re-runs cost matching without locking transactions. Used for mid-period sanity checks or for ongoing operations where closing would be premature. ## Marking **Manual marking** lets users explicitly bind a specific outbound transaction to a specific inbound layer. The classic use case: a unique high-value purchase (a specific machine) sold to a specific customer — the user marks the sale against the specific purchase, regardless of FIFO/LIFO order. Marking overrides the standard costing logic for that pair. ## The standard-cost item model Standard cost items work differently. Each item has a configured standard; inbound and outbound post at the standard; variances post to designated variance accounts. The annual standard-cost roll updates the standards (similar to BC's standard cost worksheet but more deeply integrated with manufacturing). Closing reconciles standard inventory to actual when actual deviates substantially. ## Moving average An incremental Weighted Avg. variant where each receipt updates the moving average and outbounds post at the current moving average. Less precise than Weighted Avg. at closing but provides real-time cost visibility on every transaction. ## FIFO with date FIFO with explicit date control — combines date and FIFO order, so deliveries late but recorded earlier still match correctly. ## The GL impact Closing posts adjustment entries to: - Inventory account (asset side). - Cost of Goods Sold account (P&L side). - Variance accounts (for standard cost items). - Inventory revaluation accounts (when standards change). Period-end reconciliation between the *Inventory* GL account and the *Inventory Valuation* report should match to the penny after closing. **Common pitfalls.** - **Closing not run regularly** — inventory cost drifts; COGS becomes unreliable. - **Marking abused** — too many manual marks make audit complex. - **Standard cost variances unallocated** — large variances accumulate in variance accounts without analysis. - **Closing run during operations** — locks inventory, disrupts shipping. Schedule during quiet windows. ## Operational discipline Run inventory recalculation weekly; run inventory closing monthly (or quarterly for low-volume operations). Reconcile inventory to the GL every close. Don't let unallocated variances accumulate; investigate large ones each close. --- # Credit and collections management in Dynamics 365 Finance How F&O's Credit and Collections module handles customer credit risk, dunning, payment-promise tracking, and collections workflow. Source: https://www.solvingdynamics365.com/guides/credit-and-collections-management-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 For mid-to-large B2B operations, customer credit management is operationally significant — granting too much credit risks bad debt; granting too little blocks sales. Dynamics 365 Finance ships a dedicated **Credit and Collections** module to structure both sides: credit-limit management before sales happen, and active collections after invoices age. ## The credit-management side Every customer carries: - **Credit limit** — the maximum exposure F&O will permit before warning or blocking. - **Credit limit type** — Balance (open AR), Balance + Open Orders, custom calculations. - **Credit hold reason** — current credit status with reason code. - **Risk score** — assigned manually or from external credit-bureau integration. - **Insurance coverage** — for customers with trade-credit insurance. - **Payment history** — average days past due, longest delinquency, dispute rate. When a sales order is created or released, F&O evaluates the customer's exposure against the limit. Configurable rules can: - **Block** the order from posting until credit is approved. - **Warn** the user but allow posting. - **Auto-release** if exposure is under threshold. - **Route to credit manager** for review with one-click approve / decline. ## Credit limit adjustments Manual adjustments to credit limits are tracked with effective dates, approver, and reason — a compliance-friendly audit trail. Workflow can route increases through approval (credit manager, CFO depending on size). ## Trade-credit insurance F&O can integrate trade-credit-insurance coverage limits — Atradius, Coface, Euler Hermes-style policies — so that insured-customer exposure under the insurance limit is treated differently from uninsured. ## The collections side **Collections** organises post-due-date follow-up: - **Collections agent** — each customer can be assigned to a collections specialist. - **Aging snapshot** — daily or weekly snapshot of customer balances by aging bucket. - **Collection cases** — formal case records for customers in collection, with status, notes, activities, contacts. - **Payment promises** — recorded commitments by the customer to pay by a date. Aging routines respect promised dates; broken promises escalate. - **Activities** — phone calls, emails, letters, dispute investigations. - **Disputes** — formal customer disputes about invoiced amounts, tracked separately from genuinely overdue. ## Dunning F&O's **dunning** (the formal escalation series) extends beyond BC's reminders: - **Multi-level dunning** — formal letters at each escalation, with configurable text per level. - **Combined for the customer** — one dunning letter per customer covering all their overdue invoices. - **Interest calculation** — overdue interest computed and optionally posted. - **Legal handover** — final level can trigger handover to external collections agencies. - **Dunning in customer's language** — multi-language letter templates. ## Workspace and operational view The **Collections workspace** gives collections agents: - A list of their assigned customers ranked by exposure or aging. - One-click drill-down to customer details. - Activity capture inline (call notes, email logs). - Payment-promise tracking. - Aging view per customer with click-through to specific invoices. ## Dispute management **Disputes** track customer-reported issues with specific invoices: - Invoice line(s) under dispute. - Reason and explanation. - Assigned investigator. - Status (Open, Resolved, Credit Issued, Customer Withdrew). - Resolution amount. Disputed amounts are excluded from regular collections work — collections agents chase undisputed balances; dispute investigators resolve disputes; resolved disputes go back into collections or close with a credit memo. **Reporting.** - **Days Sales Outstanding (DSO)** — overall and per customer segment. - **Aging summary and detail** — across customers, agents, regions. - **Payment promise performance** — kept vs broken promises by customer. - **Collections agent dashboards** — current portfolio, recent activities, recovery rate. - **Bad-debt and write-off analysis**. **Power BI templates** ship with the module for deeper analytics. ## Integration Credit and collections integrate with Sales — pipeline opportunities reference customer credit status; customer credit holds visible in CRM. Customer Service cases linked to disputed invoices give context. ## Where it fits and where it doesn't F&O's collections module is enterprise-grade — substantially deeper than BC's reminder mechanism. For SMBs on BC, BC's reminders plus a collections ISV add-on (Cashbook, Continia Collections) is typically right-sized. For enterprise volume and complex collections operations, F&O's built-in is the strong default. ## Operational reality Collections discipline drives cash flow more than any other operational lever in many businesses. Configure thoughtfully; staff the function appropriately; measure relentlessly. --- # Custom services and OData endpoints in F&O How to expose Dynamics 365 Finance / SCM functionality to external systems — custom services in X++, OData endpoints from data entities. Source: https://www.solvingdynamics365.com/guides/custom-services-and-odata-in-f-and-o Section: Finance & SCM / AL & X++ development Published: 2026-06-12 Dynamics 365 Finance and Supply Chain integrates with external systems through several API surfaces. Two are particularly important for custom integration work: **custom services** (developer-built X++ services that expose specific operations) and **OData endpoints** (automatic REST endpoints generated from data entities). Knowing which to use for which scenario matters. **OData endpoints from data entities.** Every **data entity** in F&O — and most standard entities ship with the platform — is automatically exposed as an OData v4 endpoint: ``` https://.dynamics.com/data/Customers https://.dynamics.com/data/SalesOrderHeaders https://.dynamics.com/data/PurchInvoiceLines ``` Standard OData semantics apply — `$filter`, `$select`, `$expand`, `$orderby`, `$top`, `$skip`, with full CRUD operations via GET / POST / PATCH / DELETE. **Strengths:** - **Zero developer work** beyond enabling entities — generated automatically. - **Standard OData** — broad tool support. - **Documented** — the OData metadata is queryable. - **Versioned** — data entities have versions; new versions add fields without breaking old consumers. **Weaknesses:** - **CRUD-focused** — fine for "create a sales order", less natural for "run a specific business operation". - **Side-effect operations** are awkward — confirming an order, posting a journal, releasing a production order don't map cleanly to PATCH semantics. - **Performance** — large bulk operations through OData are slower than equivalent custom services. **Custom services.** A **custom service** in F&O is a developer-built X++ service that exposes specific operations. The pattern: 1. Define a **service contract** — a class with `[DataContract]`-marked methods defining the operation's inputs. 2. Define a **service implementation** — the X++ class that executes the logic. 3. Define a **service group** — a deployment unit grouping related services. 4. Deploy the service group — F&O exposes the services at endpoint URLs. The result: operations like `PostSalesInvoice`, `ReleaseProductionOrder`, `CalculateCustomerBalance` can be called from external systems as HTTP / SOAP / OData-style endpoints. Inputs are typed; outputs are typed; F&O handles authentication, serialisation, and error responses. **Strengths:** - **Tailored to business operations** — natural for action-oriented integrations. - **Encapsulation** — internal logic is wrapped; external callers don't need to understand the internal data model. - **Performance** — direct X++ execution; can be optimised for specific scenarios. - **Atomic transactions** — multi-step operations run inside a single F&O transaction. **Weaknesses:** - **Developer effort** — must be written in X++ and deployed. - **Versioning discipline** — service contracts evolve; consumers must adapt. - **Less discoverable** than OData metadata. **Choosing.** - **Read-heavy or simple CRUD** → OData endpoints from data entities. - **Business-operation invocation** (post, release, approve, calculate) → custom services. - **High-volume bulk operations** → custom services with batch input. - **Reporting and analytics extraction** → OData (or better: data lake / Synapse Link). ## Authentication Both surfaces authenticate via **Microsoft Entra ID** OAuth 2.0 — typically service-principal authentication for system-to-system calls. The same Entra app registration grants access to both OData and custom services. ## Throttling F&O API call limits apply to both: - **Priority-based throttling** — non-priority calls slow down or queue when the tenant approaches limits. - **Burst limits** — short-term spike capacity beyond sustained rates. - **Per-user limits** — when calls are made as a specific user identity. Heavy integration traffic should respect throttling — implement exponential backoff on 429 responses. **Operational considerations.** - **Logging** — both surfaces emit telemetry through Application Insights. Configure tracing for debugging. - **Versioning** — data entities have built-in versioning; custom services need manual version management (often through deployment of new service variants alongside the old). - **Documentation** — for custom services, maintain external API documentation; OData has self-describing metadata. ## Modern alternatives for analytics workloads For analytics consumption — extracting F&O data for reporting, BI, data warehousing — **Synapse Link for F&O** is the modern path. It streams F&O changes to OneLake near-real-time; consumers query OneLake instead of hitting F&O's API. Vastly more efficient for analytics; preserves F&O's interactive performance for operational users. **Common pitfalls.** - **OData polling for change detection** — chatty, throttling-prone. Use Synapse Link or business events instead. - **Custom services without versioning strategy** — breaking changes cascade to consumers. - **No throttling handling on consumers** — integration randomly fails under load. ## Operational reality Mature integrations use both: OData for entity access, custom services for business operations, Synapse Link for analytics. Each tool for its job. --- # Customer self-service in Dynamics 365 Finance and SCM How customer-facing portals integrate with F&O — order placement, account status, statements, and the patterns that drive customer satisfaction at scale. Source: https://www.solvingdynamics365.com/guides/customer-self-service-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 For B2B operations selling to many customers, **customer self-service** is increasingly table-stakes. Customers expect to see their orders, account balance, invoices, and shipping status without having to call. They expect to place repeat orders without sales rep involvement. Done well, customer self-service reduces customer-service cost and improves satisfaction simultaneously. ## The architecture F&O customer self-service is built on **Power Pages portals** sitting in front of F&O's customer-side data — orders, invoices, deliveries, statements, products. The portal authenticates customer users against their own organisation's identity provider (or local accounts), scopes data per the authenticated user's customer record, and exposes a curated set of capabilities. **Common self-service capabilities.** - **Order placement.** Browse the product catalogue with the customer's contracted prices; add to cart; submit as a sales order. The order arrives in F&O as a draft awaiting confirmation, or auto-confirmed for trusted customers. - **Order status.** View open and historical orders with line-level detail, shipping status, tracking numbers, expected delivery, invoice status. - **Reorder.** One-click reorder of previous orders, optionally with quantity adjustment. The most-used feature for repeat B2B customers. - **Saved orders / shopping lists.** Pre-built lists of frequently-ordered items the customer can use as templates. - **Quotes and approvals.** Receive sales quotes for approval; accept or reject; track quote-to-order conversion. - **Invoices and statements.** View posted invoices, download PDFs, view aged statements, see payment status. - **Payments.** Make online payments through integrated payment processors against open invoices. - **Returns.** Initiate a return request, get an RMA, track the return. - **Account profile.** Update contact information, shipping addresses, payment methods, communication preferences. - **Product information.** Detailed product specs, datasheets, manuals, certifications. ## Customer hierarchies B2B customers often have multiple buyers across multiple locations. The portal supports the hierarchy: a parent-company user sees orders for all child accounts; a location-specific user sees only their location's orders. Permission roles configure the scope. ## Contracted prices Pricing in the portal honours **sales agreements** and customer-specific price lists. The customer sees their negotiated price, not the public catalogue price. ## Inventory visibility Real-time stock availability shows on the product page — in-stock now, expected restock dates, alternative items. Customers can decide whether to order or wait. ## Catalogue management The catalogue exposed in the portal can be: - **Full catalogue** — every product the company sells. - **Customer-specific subset** — only products the customer is contracted to buy. - **Hierarchy-filtered** — different catalogues per customer tier or industry. Configuration controls per-customer visibility. ## Approval workflow inside the customer Many B2B customers require internal approval before submitting an order. The portal supports buyer roles where requesters submit, approvers approve, and only approved orders post to F&O. ## Integration with Sales Customer activity in the portal — quote views, abandoned carts, repeat-order patterns — can flow to Dynamics 365 Sales as signals for the account manager. ## Mobile The portal is responsive; mobile-friendly experience handles the on-the-go customer placing emergency reorders, viewing tracking, or paying invoices. **Common patterns.** - **Reorder-heavy customers** — distributors, wholesalers — get a stripped-down portal focused on fast reorder. - **Configure-to-order customers** — manufacturers, equipment buyers — get richer product configurators. - **Long-tail customers** — small-volume buyers — get self-service onboarding to reduce per-customer cost of acquisition. ## Operational reality The biggest portal mistake is launching without serious change management for customers. Customers who never used a portal need education and gentle onboarding. Pair launch with sales rep outreach to top customers; give them tutorials, video walkthroughs, and one-on-one support for the first weeks. --- # Data entities and the Data Management Framework How bulk data import, export, and integration work in Dynamics 365 Finance and SCM — entities, projects, and the recurring integration pattern. Source: https://www.solvingdynamics365.com/guides/dynamics-365-data-entities-and-dmf Section: Finance & SCM / Overview & platform Published: 2026-05-01 The **Data Management Framework (DMF)** is Dynamics 365 Finance and Supply Chain's tool for bulk import and export. Where Dual-write handles synchronous, transactional sync, DMF handles batch — initial migrations, large recurring loads, and exports for downstream systems. ## Data entities A **data entity** is a denormalised view of one or more underlying tables, presented as a single shape with stable field names. Microsoft ships hundreds — customer, vendor, item, sales order header, sales order line, sales tax, fixed asset, GL journal voucher, project transaction, and so on. Entities are versioned so consuming integrations don't break when the underlying database evolves. ## Data Management workspace The **Data Management** workspace in F&O is where users define **data projects** — collections of entities with mappings, filters, and source format (CSV, XML, Excel, ODBC) — and run import or export jobs. A project can be a one-off load or a recurring scheduled run. ## Import An import project maps incoming source columns to entity fields, validates the data, and either commits in bulk or stages for review. **Composite entities** import related tables together (e.g. sales order header + lines + charges as one transactional unit). The framework provides error handling: rows that fail validation are quarantined for correction without blocking the rest of the batch. ## Export An export project pulls entity data out as CSV, XML, or to an Azure SQL endpoint. Exports can be filtered, scheduled, and incremental (delta-only based on a change timestamp). ## Recurring integrations The **Recurring Integrations** API exposes data projects as HTTP endpoints, so external systems can `POST` import payloads or `GET` export results on a schedule. The pattern: external app pushes a CSV to the F&O endpoint every hour; F&O queues the import for processing. ## The BYOD pattern (deprecated) *Bring Your Own Database* exported entity data into a customer-owned Azure SQL Database. BYOD is being phased out in favour of **Synapse Link** and **Microsoft Fabric**, which stream F&O tables into a lakehouse without requiring data entities as the export shape. ## Performance DMF jobs can run in parallel threads, configurable per project. Large initial loads (millions of rows) are tuned with parallel processing, narrow batch sizes, and selective indexes. A reasonable initial customer migration loads in hours, not days, when tuned. ## Best practice Use Dual-write for synchronous CRM ↔ ERP sync, DMF for batch ETL and high-volume migrations, and Synapse Link or Fabric for analytics export. --- # Demand planning in Dynamics 365 Supply Chain Microsoft's Demand Planning module — statistical forecasting, collaboration, scenarios, and the path from forecast to MRP. Source: https://www.solvingdynamics365.com/guides/dynamics-365-demand-planning Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 **Demand Planning** is Dynamics 365 Supply Chain Management's modern forecasting module, built natively on the Power Platform with embedded AI. It replaces an older, less-loved Demand Forecasting tool with a cleaner UX and a real planner workspace. ## The model A demand plan is structured around **dimensions** — typically item, location, customer or channel, and time bucket — and **measures** — historical sales, statistical forecast, collaborative forecast, final consensus forecast. Planners work in a grid that pivots across the dimensions, much like a planning spreadsheet, but backed by versioning, audit, and AI. ## Data inputs Historical sales transactions flow in from F&O. External signals (marketing campaigns, promotional plans, weather, macroeconomic indicators) can be loaded as additional measures through Dataverse or Power Automate. Open orders, planned orders, and inventory positions are pulled live from F&O for sanity checks. ## Statistical forecasting Built-in **forecasting models** include moving averages, exponential smoothing, ARIMA, and ML-based ensembles. Planners run the engine for a horizon, evaluate accuracy against held-out history (MAPE, WAPE), and select the best-fit model per item-location. The system can also recommend a model per series. ## Collaboration Sales and operations planning (S&OP) requires multiple stakeholders to contribute. Demand Planning supports **collaborative inputs** — sales teams override the statistical forecast for known opportunities; marketing layers campaign uplifts; finance applies budget alignment. Each contribution is tracked and the final consensus is calculated. ## Scenarios Planners can clone a baseline forecast into **what-if scenarios** — promotional uplift, supply constraint, market expansion — and compare side by side without disturbing the production plan. ## Outputs The final consensus forecast publishes to F&O as forecast lines that feed **master planning** (the supply-side engine). Forecast lines respect time fences, lead-time offsets, and consumption rules so MRP doesn't double-count actual orders against the forecast. ## Workflow Built-in approval workflow routes the published forecast through configurable approvers before it lands in F&O. ## Reporting Power BI templates ship with the module, covering forecast accuracy, bias, drift, and consensus variance. ## Where it stops Sophisticated S&OE (sales and operations execution), causal modelling, or supply-side scenario engines often combine Demand Planning with a third-party tool. For mid-market manufacturing and distribution, the built-in module is fully sufficient. --- # Discounts and pricing in Dynamics 365 Commerce How Commerce handles retail pricing and discounting — base prices, trade agreements, discount engines, and the rules that govern complex promotional logic. Source: https://www.solvingdynamics365.com/guides/discounts-and-pricing-in-commerce Section: Finance & SCM / Retail & commerce Published: 2026-05-01 Retail pricing is some of the most complex logic in any ERP. A customer scanning a product at the till should see the right price, with the right active promotion, with the right customer-tier discount, with the right tax — all computed in milliseconds. Dynamics 365 Commerce has one of the most sophisticated discount engines in mid-to-large retail; understanding it is essential to deploying it well. ## Base price hierarchy Every product has a price determined by walking a hierarchy: 1. **Trade agreement** — customer-specific or customer-group-specific pricing. 2. **Channel-specific price** — the store / e-commerce site's overriding price for the product. 3. **Sales price** on the product master. The most specific applicable rule wins. Customer-specific overrides channel-specific; channel-specific overrides master. ## Trade agreements **Trade agreements** are pricing and discount rules attached to: - **Item** + **Customer** combinations. - **Item group** + **Customer group** combinations. - **All items** + **All customers** (broad rules). - Date ranges per rule (promotional pricing with effective dates). A customer can have many trade agreement lines; the engine picks the best applicable price or discount automatically. ## Discount engines Beyond base prices, **discounts** apply additional reductions: - **Simple discount** — fixed % off or fixed amount off. - **Quantity-based discount** — buy 3, get 10% off. - **Mix-and-match discount** — buy any 3 items from category X, pay for 2. - **Threshold discount** — spend over €100 and get 15% off the total. - **Multiple-buy discount** — buy product A and get product B at discount. Each discount has: - **Discount code** — unique identifier. - **Validity period** — start and end dates. - **Concurrency** — can this discount stack with others (e.g. customer loyalty + promotional discount) or is it exclusive. - **Channel filter** — which channels (stores, e-commerce, B2B) the discount applies to. - **Customer filter** — which customer groups. - **Item filter** — which items or categories. ## Concurrency When multiple discounts apply to a transaction, the engine evaluates **concurrency** — which can combine and which are exclusive. Configurable per discount; typical patterns: - Loyalty discount stacks with promotional discount (additive). - Customer-tier discount and promotional discount: most specific wins (no stacking). - Manager override: replaces all other discounts. ## Loyalty Loyalty programs integrate with the discount engine: - **Tier-based** — Bronze members get 5%, Silver 10%, Gold 15%. - **Point accrual and redemption** — earn points on purchases; redeem points as discount. - **Birthday rewards** — special offers around customer birthdays. - **Threshold-based** — spend €X this quarter and earn a discount. ## Coupons **Coupons** are codes the customer enters or presents at checkout (manual entry, barcode scan, mobile-app reveal). The coupon validates against rules (one-time use, multi-use, customer-specific, channel-specific) and applies its associated discount. ## Tax interaction Tax in retail is complex (sales tax in the US, VAT in EU, GST elsewhere). The pricing engine handles tax-inclusive or tax-exclusive pricing per channel, with tax computed on either the gross or net price based on configuration. ## Performance The engine runs at the till in real time; it must compute correctly in milliseconds. The store-level cache holds active prices and discounts so offline operations don't lose pricing. **Common pitfalls.** - **Discount stacking surprise** — too-generous concurrency lets every discount stack, eroding margin. - **Conflicting trade agreements** — overlapping rules without clear precedence produce inconsistent prices. - **Expired discounts not removed** — old promotions linger and confuse staff. - **Customer-tier overrides** — VIP customers' tier discount unintentionally overridden by a generic promotional discount. ## Operational discipline Test every promotion at the till before going live. Document concurrency rules clearly. Review the discount catalogue quarterly to retire stale rules. The engine is powerful enough to do almost anything; that's the danger as much as the strength. --- # Discrete vs process vs lean manufacturing in F&O How Dynamics 365 Supply Chain supports three manufacturing modes — what each one is, when they apply, and how they coexist in a single tenant. Source: https://www.solvingdynamics365.com/guides/discrete-vs-process-vs-lean-manufacturing-in-f-and-o Section: Finance & SCM / Manufacturing Published: 2026-05-01 Dynamics 365 Supply Chain Management supports three distinct manufacturing modes — **discrete**, **process**, and **lean** — that can coexist in a single tenant on a single environment. Choosing which mode applies per item drives the entire production-execution behaviour for that item. Many F&O customers run two modes side by side, with each suiting different production lines or business divisions. ## Discrete manufacturing The classic batch production model. Used for products that are *built* — assembled from discrete components into discrete finished units. Examples: vehicles, electronics, furniture, machinery, medical devices, consumer goods packaging. - **Production BOMs** define the components. - **Routings** define operations on work centres. - **Production orders** execute the build, with consumption journals capturing material usage and output journals capturing finished units. - **Cost** flows component-by-component into WIP, then into the finished item on completion. Discrete is appropriate when each finished unit is countable and tracked individually (e.g. one car, one laptop, one chair). The production order pattern matches the work: a planned quantity, components consumed, finished units output. ## Process manufacturing For products that are *made* through chemical, biological, or physical processes. Examples: food, beverage, pharma, chemicals, cosmetics, paint, lubricants. Different from discrete because: - **Formulas** replace production BOMs. Formulas have proportional ingredients that scale with batch size, plus yield factors (a 1000 kg batch input doesn't necessarily produce 1000 kg of output). - **Co-products and by-products** — a single batch can produce multiple finished items simultaneously (process meat: cuts, trimmings, bone-meal byproduct). The cost allocation across co-products is itself a configuration concern. - **Catch weight** — items priced per unit but inventoried by weight (one cheese wheel = 1 piece but variable kg). Critical for meat, fish, cheese, produce. - **Batch attributes** — fat %, alcohol %, pH, brix — attached to each batch, available for pricing, picking, and customer-spec filtering. - **Shelf life** — manufacturing date and expiry date per batch, with FEFO (first expired first out) picking. - **Quality** — process industries have substantial quality testing; integrated quality management associates test results with batches. Process is appropriate when output is continuous, with variability per batch, with co-products / by-products, with shelf-life concerns. ## Lean manufacturing A different paradigm — pull-based replenishment, kanban-style. Used in repetitive manufacturing environments where the same products are made continuously: automotive, electronics, fast-moving consumer goods. - **Production flows** define the steps in a value stream. - **Kanban rules** define what triggers replenishment — withdrawal kanbans (move material from inventory to consumption point), production kanbans (start production when WIP runs low). - **Kanban cards** are visual or electronic signals that drive operations without large planned production orders. - **Heijunka boards** balance production to demand. Lean is the right pattern when production is high-volume, repetitive, and where small batches with frequent replenishment fit operations better than large MRP-driven production orders. ## Mixing modes A single F&O tenant can run all three. A consumer-goods manufacturer might make the chemicals (process), assemble the packaging (discrete), and run the packaging line (lean). Each item is tagged with its **production type** that drives the engine's behaviour for that item. ## Cost accounting across modes Standard cost works across all three; actual cost works across all three. The cost reconciliation at period close treats each mode's WIP, components, and outputs correctly. **Common pitfalls.** - **Wrong production type for the item** — using discrete for a process-style operation produces no useful planning; using process for a discrete item over-engineers. - **No clear conversion factor** for catch weight — products mispriced or mis-stocked. - **Mixed-mode plants without clear policy** — operators confused about which orders to handle which way. ## Operational reality The implementation work scales with the number of modes used. Single-mode operations land cleanly; multi-mode operations need substantially more design, training, and ongoing process discipline. ### Frequently asked questions **Can one Supply Chain Management environment run discrete, process, and lean manufacturing at once?** Yes. Each item carries a production type that drives the engine's behaviour, so a consumer-goods manufacturer can make chemicals in process mode, assemble packaging in discrete mode, and run the packaging line lean, all on one site. **What is the difference between a production BOM and a formula?** A production BOM lists discrete components for a countable finished unit. A formula has proportional ingredients that scale with batch size, yield factors, co-products and by-products, and often catch-weight and shelf-life handling — the process manufacturing model. **When is lean manufacturing the right mode?** For high-volume, repetitive production where kanban-driven pull replenishment fits better than large MRP-planned production orders — automotive, electronics, fast-moving consumer goods. Production flows and kanban rules replace planned orders. **What is catch weight?** Items priced per unit but inventoried by weight — a cheese wheel is one piece but a variable number of kilograms. It is essential for meat, fish, cheese, and produce, and a missing conversion factor is a classic process-manufacturing implementation error. --- # Dual-write integration between F&O and Dataverse How Microsoft's Dual-write framework synchronises Finance/SCM data with Dataverse — table maps, initial sync, and operational realities. Source: https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-integration Section: Finance & SCM / Overview & platform Published: 2026-05-01 Updated: 2026-09-06 ### Key facts - Dual-write fires synchronously on save in each system — a successful F&O save also writes to Dataverse and waits for the acknowledgment, and vice versa, rather than syncing on a delay. - Each map declares a direction (F&O to Dataverse, Dataverse to F&O, or bi-directional); customer-facing entities are commonly bi-directional, while single-authority master data such as items is typically one-directional. - An initial sync copies historical data in bulk, typically F&O to Dataverse, before live operation begins, and is run from Lifecycle Services. - Extending a standard map to add project-specific fields is the preferred approach over building a fully custom map, because an extended map still inherits the fixes and schema updates Microsoft ships to the base map. - Because dual-write runs synchronously, a silent backlog is worse than a visible one — a source-system save can succeed while the counterpart write keeps failing and retrying, so monitoring the error queue and latency matters more than watching for outright failures. **Dual-write** is Microsoft's near-real-time integration between **Dynamics 365 Finance and Supply Chain Management** (the F&O apps) and **Microsoft Dataverse** (under the CRM apps and the Power Platform). It exists because F&O has its own database that's not Dataverse, so customers running both CRM and ERP need the same Account, Contact, Product, and Order tables to stay in sync between the two systems. ## The model Dual-write defines **maps** — pairs of tables, one in F&O and one in Dataverse, with a field-level mapping between them. Microsoft ships dozens of standard maps (customer, vendor, product, sales order, sales invoice, employee, work order, project). Custom maps can extend the standard ones or add net-new tables. ## Direction Each map declares a *direction*: F&O → Dataverse, Dataverse → F&O, or bi-directional. Bi-directional is common for customer-facing entities (a customer added in Sales appears in Finance, and vice versa). Master data with a single authority (e.g. items maintained in F&O) is typically one-directional. ## Near-real-time Dual-write fires synchronously on save in each system. A successful F&O save also writes to Dataverse and waits for the acknowledgment; a Dataverse save writes to F&O. If the partner system is unavailable, the save fails or queues for retry, depending on the map's configuration. ## Initial sync Before live operation, an **initial sync** copies historical data in bulk in one direction (typically F&O → Dataverse). Initial sync is a sizeable operation for large datasets and is run from LCS. ## Plays well with CDM Dataverse tables in dual-write are aligned with the Common Data Model, so the same Dataverse Account is shared across Dual-write to F&O, Customer Insights, Sales, and Customer Service. **Pitfalls.** - **Latency under load.** A burst of F&O posting can backlog Dual-write, with downstream apps seeing data minutes after the source. Monitor the queue. - **Schema drift.** Map definitions must track schema changes in both F&O and Dataverse. A new required field on either side breaks the map until updated. - **Validation differences.** Both systems have their own validation; rejected writes need a retry strategy. ## Standard maps at a glance | Domain | Example maps | Typical direction | |---|---|---| | Party data | Customer, Vendor, Contact, Worker | Bi-directional (both systems create and edit) | | Product | Released product, Product master | F&O → Dataverse (F&O is the system of record for items) | | Sales | Sales order, Sales order line | Bi-directional (Sales app creates, F&O fulfils and invoices) | | Project | Project, Project task | Bi-directional (Project Operations and F&O Project management) | | Case/Service | Work order, asset | F&O/Field Service → Dataverse depending on which app owns the record | Not every table needs dual-write — a table with a single authoritative system and no CRM-side consumer of that data (a purely internal F&O configuration table, say) should stay in F&O only. Turning on dual-write for tables nothing downstream reads adds sync overhead and failure surface for no benefit. ## Extending a standard map vs building a custom one Microsoft's standard maps cover the common fields for each entity, but a project's own required fields — a custom customer attribute, an industry-specific product field — usually aren't in the standard mapping. Dual-write supports **extending** a standard map by adding fields to it, which is the preferred approach when the entity itself is standard and only the field list is incomplete. Reach for a fully **custom map** only when the entity itself doesn't exist in the standard set at all; extending is lower-maintenance because it inherits fixes and schema updates Microsoft ships to the base map, where a custom map is entirely the implementation team's to maintain. ## Monitoring and alerting Dual-write exposes sync status and error logs through both the Dataverse **Dual-write** admin app and F&O's own integration monitoring. A healthy operational setup alerts on: a rising error queue (writes failing and retrying without resolving), growing latency (the gap between a save and its counterpart appearing on the other side), and any map that's been disabled (deliberately or due to a fatal schema mismatch) without anyone noticing. Because dual-write runs synchronously on save, a *silent* backlog is worse than a *visible* one — users on the source system see their save succeed even while the counterpart write is failing, so nobody notices the drift until a report on the other side looks wrong. ## Where it fits Dual-write is the canonical choice for customers running F&O alongside CRM-side D365 apps. For F&O integrations that don't need Dataverse — pure ERP-to-ERP, ERP-to-EDI — use the Data Management Framework or the F&O REST API instead. ## Where to go next When it misbehaves, [dual-write troubleshooting patterns](https://www.solvingdynamics365.com/guides/integrating-with-dual-write-troubleshooting-patterns) gives the diagnostic order and [dual-write sync errors](https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-sync-errors) decodes the messages. [Master data services vs dual-write](https://www.solvingdynamics365.com/guides/master-data-services-vs-dual-write) covers the alternatives, [how Dynamics 365 apps connect](https://www.solvingdynamics365.com/guides/how-dynamics-365-apps-connect) the architectural context, and [what is Microsoft Dataverse](https://www.solvingdynamics365.com/guides/what-is-microsoft-dataverse) the platform on the other side. --- # Dual-write sync errors Dual-write errors between Finance and Operations and Dataverse decoded — lookup not found, company missing, integration key conflicts, validation failures. Source: https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-sync-errors Section: Finance & SCM / Troubleshooting Published: 2026-09-03 Dual-write errors have a shape: a specific message on one side of the integration, a cause on the other, and a fix that is almost always about setup order, reference data, or the application user rather than about the map itself. This reference lists the messages that recur, where each appears, and what to do. The diagnostic method — reference data before transactions, one map at a time — is in [dual-write troubleshooting patterns](https://www.solvingdynamics365.com/guides/integrating-with-dual-write-troubleshooting-patterns); the architecture in [Dynamics 365 dual-write integration](https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-integration). ## Where to look - **Initial sync:** in Finance and Operations, Data management > Dual-write > select the map > Execution details. Each run shows rows processed and rows failed with the error per row. - **Live sync, F&O to Dataverse:** the Dual-write errors table in Dataverse (Integration Errors view in the Dual-write admin experience), plus the Dataverse async operation log for plug-in failures on the receiving table. - **Live sync, Dataverse to F&O:** the F&O side logs the failed write against the business event / integration log; the Dataverse row keeps a sync status. - **Map state:** Dual-write page in F&O or the Dual-write admin app in Dataverse — Running, Not running, Paused, and the error count. ## Setup and dependency errors ### "Referenced record not found" / "Lookup value for field X could not be resolved" / "Could not find target row" **Symptom.** Customer, product, or order rows fail in initial or live sync naming a lookup field. **Cause.** The referenced row — currency, unit of measure, customer group, payment terms, site, warehouse, sales tax group — does not exist in the target because its map has not run, or ran with a filter that excluded it. Dual-write does not create references on the fly. **Fix.** Run the reference-data maps first in the documented dependency order (legal entities and companies, then currencies, units, countries and other reference tables, then parties, customers, vendors, products, then transactions). Re-run the failing map. **Prevention.** Initial sync one map at a time, verifying each is clean before the next, and never run a transactional map before its references. ### "Company X does not exist in Dataverse" / "cdm_company not found" / the company lookup is empty **Symptom.** Everything fails for one legal entity. **Cause.** The Company (cdm_company) map has not run for that legal entity, or a row was created in Dataverse without a company value. Nearly every dual-write table carries a company lookup. **Fix.** Run the Companies map first; on Dataverse forms for synced tables, default the company field and make it required with a business rule. ### "Integration key" / "An item with the same key has already been added" / alternate key violation 0x80040237 **Symptom.** Rows fail with duplicate-key messages, or duplicates appear on one side. **Cause.** The same business record exists on both sides from earlier manual entry or a previous integration, with keys that do not match the map's integration key. Dual-write cannot decide they are the same record. **Fix.** Decide the master per table, align keys with a one-off data fix (update the Dataverse alternate key values to match F&O's, or vice versa), delete the orphaned duplicates, then re-run initial sync for that map. **Prevention.** Clean both sides before the first sync; [Dataverse alternate keys](https://www.solvingdynamics365.com/guides/dataverse-alternate-keys) covers how the keys work. ### Number sequences: rows created in Dataverse fail in F&O with a blank or rejected number **Cause.** A record created on the Dataverse side arrives in F&O without an F&O-generated number, and the F&O number sequence for that record type is not configured for the way the map supplies the key (manual entry not allowed, or the Dataverse autonumber not set up). **Fix.** Follow Microsoft's per-entity guidance on number sequences for dual-write — typically configuring the number sequence to accept the value the map provides, or generating the number in Dataverse with an autonumber column that matches the F&O format. ## Validation errors ### "Validation failed" / "Field X must be filled in" / "Cannot edit a record in Table (Y). Field Z must be filled in." **Symptom.** Live sync writes fail with F&O or Dataverse field validation messages. **Cause.** The target enforces a mandatory field the source did not supply — business-required columns in Dataverse, mandatory fields on the F&O entity, or a value F&O's validation rejects (an address without a country, a customer group not in the target company). Legacy data that F&O tolerated in place fails when it is re-validated on the way out. **Fix.** Read the field named. Either map a source for it, set a default in the map (the transform column), or cleanse the source data. For F&O data quality, filter the map to exclude offending rows until they are fixed. **Prevention.** Validate mandatory fields on both sides before enabling a map; align required-field rules across the two systems. ### "The record is being modified by another process" / concurrency and conflict errors **Cause.** Both sides changed the same row within the sync window, or a plug-in or flow on the Dataverse side updates the row dual-write just wrote, which loops back. **Fix.** Check the conflict resolution setting on the map; find plug-ins and flows on the synced table that write to it and exclude dual-write's application user from their triggers (check the initiating user, or use a filtering attribute). **Prevention.** Design plug-ins and flows on synced tables knowing dual-write writes to them — see [master data services vs dual-write](https://www.solvingdynamics365.com/guides/master-data-services-vs-dual-write) for the loop pattern. ### "Value is not valid for option set" / choice mismatch **Cause.** The map's value transformation between an F&O enum and a Dataverse choice is incomplete — a new enum value on one side without a matching choice on the other. **Fix.** Add the value to the transform on the map and, if needed, the choice in Dataverse. ## Security and application user ### "Principal user is missing prvXxx privilege" — 0x80040220 / "Access denied" on the Dataverse side **Symptom.** A map fails entirely, or fails for one table, with a privilege error. **Cause.** The dual-write application user in Dataverse lacks the privilege. A custom table added to a map without updating the app user's role, a field-level security profile that excludes the app user, a new security role assignment that removed a needed one, or the app user disabled. **Fix.** Check the application user's roles (the Dual-write app user roles Microsoft installs, plus a custom role for custom tables) and any field-level security profiles on the table; enable the user if disabled. **Prevention.** Every custom table added to a map comes with a role change for the app user. [Dataverse security model](https://www.solvingdynamics365.com/guides/dataverse-security-model) covers roles and profiles. ### "The user is not a member of the organization" / 401 from Dataverse **Cause.** The application user was removed from the environment, or the environment was copied and the app user was not recreated. **Fix.** Recreate the application user for the dual-write app registration and assign roles; relink the environments if the copy broke the link. ### Authorisation errors on the F&O side **Cause.** The Dataverse-side integration identity is not registered in F&O's Microsoft Entra applications, or lacks the security role for the entities in the map. **Fix.** Register the app in F&O under System administration > Microsoft Entra applications with an appropriate user and role. ## Map state and schema ### Map shows Not running / stops after errors **Symptom.** Live sync silently stopped; the map's state is Not running. **Cause.** Dual-write stops a map after a schema change on either side, after an environment refresh, upgrade, or F&O service update, or when the live-sync error threshold is hit. **Fix.** Open the map, use Refresh tables (or Refresh entities) to pick up schema changes, review and resolve the logged errors, then Run. Maps do not restart themselves. **Prevention.** Put "check dual-write map states" in the post-update checklist for every F&O service update and Dataverse solution deployment — [One Version and updates](https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates) covers the cadence. ### "Field X does not exist in entity Y" / "Column not found" after adding a field **Cause.** A field was added to the F&O entity or the Dataverse table and the map's cached schema is stale; or a custom field was added to a map but the entity extension was not deployed to this environment. **Fix.** Refresh the map's schema, add the mapping, deploy the entity extension, restart. ### Initial sync times out or stalls **Cause.** Volume: a large table synced in one batch during a busy period competes with F&O batch jobs and the Dataverse async service. **Fix.** Filter initial sync by legal entity, date range, or group and run batches in a quiet window; skip initial sync for maps whose data already matches and start live sync only. ### Environment link errors: "Environments are not linked" / "The linked environment does not match" **Cause.** An F&O environment was refreshed from another (production to sandbox), and the dual-write link now points at the wrong Dataverse environment, or vice versa. **Fix.** Unlink and relink the correct pair from Lifecycle Services / the Power Platform admin centre; recreate the application user; refresh and restart maps. Never relink a sandbox to production Dataverse. **Prevention.** A refresh checklist that includes dual-write relinking; [Dynamics 365 Finance environments and LCS](https://www.solvingdynamics365.com/guides/dynamics-365-finance-environments-and-lcs) covers the refresh process. ## Reading the pattern If many maps fail at once, it is the application user, the environment link, or a company row. If one map fails for every row, it is a schema or reference-data problem. If a map fails for a few rows, it is data quality or a key conflict. If a map worked and then stopped, it is a schema change, an update, or an error threshold. Start with which of those four you have, and the specific message above will confirm it. ### Frequently asked questions **Where do dual-write errors appear?** Three places: the map's Execution details in the Dual-write page in Finance and Operations for initial sync; the Dual-write errors table in Dataverse and the Integration Errors view for live sync in that direction; and the F&O business event and batch logs for live sync from Dataverse to F&O. Check the side that received the write. **What does 'lookup not found' or 'referenced record does not exist' mean in dual-write?** The row a lookup points at — currency, customer group, unit, site, warehouse, payment terms — has not been synced to the target yet. Dual-write is strict about lookups. Sync the reference maps first in Microsoft's documented dependency order, then re-run the failing map. **Why does a map that worked yesterday fail today with a privilege error?** The dual-write application user in Dataverse lost a privilege — a new custom table was added to a map without the app user's role covering it, a field-level security profile was added, or the app user was disabled. Check the Dual-write app user's roles and the table's field-level security before anything else. **Why is the map in a Not running state?** Maps stop after a schema change on either side, after an error threshold on live sync, or after an environment refresh or upgrade. Refresh the entities in the map to pick up the schema, resolve the logged errors, and start the map again — it does not restart itself. --- # Dynamics 365 Commerce explained Microsoft's unified retail platform — head office, store POS, e-commerce, omnichannel order management, and clienteling — and who it's actually for. Source: https://www.solvingdynamics365.com/guides/dynamics-365-commerce-explained Section: Finance & SCM / Retail & commerce Published: 2026-05-01 Updated: 2026-08-30 ### Key facts - Dynamics 365 Commerce requires Finance and Operations underneath it — head-office merchandising, pricing, assortments, and statement posting all live in F&O, so it is not a standalone product. - Stores, e-commerce, and the call centre talk to a Commerce Scale Unit rather than F&O directly, which keeps channels trading even when head office is busy or briefly unreachable. - Products, prices, and assortments reach channels through scheduled Commerce Data Exchange jobs, which is why a price change does not appear at the till the moment it is saved. - Mid-market retailers typically run the built-in e-commerce storefront, while larger retailers go headless — keeping Commerce as the product, price, and order engine behind their own front end via the Commerce Scale Unit APIs. - Commerce targets roughly ten stores up to thousands of stores; a three-store retailer or e-commerce-only brand is better served by Business Central plus a retail ISV or a Shopify-class storefront. **Dynamics 365 Commerce** is Microsoft's unified retail application, descended from the Dynamics AX Retail module (and briefly named Dynamics 365 for Retail — that history is in [its own guide](https://www.solvingdynamics365.com/guides/dynamics-365-for-retail)). It is a full retail platform: head-office merchandising, store point-of-sale, e-commerce, call centre, omnichannel order management, and customer engagement — all running on the same data model as [Finance](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-finance) and [Supply Chain Management](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-supply-chain). That last clause is the entire pitch. Most retail stacks are a federation: one vendor's POS, another's e-commerce, a third's OMS, an ERP behind them, and a career's worth of integration glue between. Commerce collapses the stack — the item you merchandise, the price you promote, the stock you promise, and the ledger you post to are one system. Whether that consolidation is worth the implementation effort is the real evaluation question, and this guide tries to give you enough shape to answer it. ## The architecture in one paragraph Commerce is not a monolith sitting inside F&O. Head office lives in F&O; the channels — stores, e-commerce, call centre — talk to a **Commerce Scale Unit (CSU)**, a channel-facing runtime that serves the Retail Server APIs, holds the channel database, and keeps trading even when head office is busy or briefly unreachable. Data moves between head office and channels through **Commerce Data Exchange (CDX)** — scheduled distribution jobs pushing products, prices, and assortments down, and pulling transactions up for statement posting. Understanding this hub-and-spoke shape explains most of Commerce's operational behaviour, including why a price change doesn't hit the tills the second you save it. The data flows are covered in depth in [retail channel data management](https://www.solvingdynamics365.com/guides/retail-channel-data-management). ## Head office Merchandising is managed centrally in F&O: category hierarchies, product attributes, catalogues, **assortments** (which products each channel carries), pricing, and promotions. Store operations — shifts, cash management, statement posting back to the general ledger — are configured here too; the operational day-to-day is covered in [store operations](https://www.solvingdynamics365.com/guides/dynamics-365-commerce-store-operations). The discount engine deserves its reputation: threshold, quantity, mix-and-match, and tender-based discounts with concurrency rules deciding what happens when several apply at once. Powerful, and easy to configure into unprofitability — see [discounts and pricing in Commerce](https://www.solvingdynamics365.com/guides/discounts-and-pricing-in-commerce). ## Point of sale The current POS client is the **Store Commerce app**, which superseded the older Modern POS; a browser-based variant covers thin-client scenarios. The POS works offline against a channel-side database and syncs when connectivity returns — essential for stores in flaky-network reality. Hardware (cash drawers, printers, scanners, payment terminals) connects through the Hardware Station. The full POS story, including device management across hundreds of stores, is in [Modern POS in Dynamics 365 Commerce](https://www.solvingdynamics365.com/guides/modern-pos-in-dynamics-365-commerce). The same client doubles as a **clienteling** tool: associates pull up cross-channel purchase history, preferences, and wish lists, and act on them mid-conversation — the till as a service tool, not just a payment terminal. See [clienteling in Dynamics 365 Commerce](https://www.solvingdynamics365.com/guides/clienteling-in-dynamics-365-commerce). ## E-commerce Commerce ships a managed e-commerce platform: content management with a visual site builder, B2C storefronts, B2B portals with account hierarchies and catalogue-based pricing, search, and checkout — deployed as part of the Commerce environment. In practice the market splits: mid-market retailers run the built-in storefront; larger ones go **headless**, keeping Commerce as the engine (products, prices, inventory, orders through the CSU APIs) and building the front end on their own stack. Both are legitimate; the headless route costs more and frees your front-end roadmap from Microsoft's release cadence. ## Call centre and omnichannel orders The **call centre** channel gives phone-order teams a keyboard-optimised order entry experience with the same pricing and promotions as every other channel — plus retail-specific machinery like catalogue source codes and continuity orders. Details in [the Commerce call centre guide](https://www.solvingdynamics365.com/guides/dynamics-365-commerce-call-center). Across channels, one order can be fulfilled any way the customer wants: buy online, pick up in store; return in store what was bought online; ship from store when the warehouse is out. Cross-channel inventory visibility comes from Supply Chain Management, and order orchestration is configurable rather than hard-coded. ## Loyalty Multi-tier loyalty with points accrual and redemption rules configured centrally and honoured across every channel — the store, the web shop, and the call centre read the same balance. Design decisions and gotchas are in the [retail loyalty deep dive](https://www.solvingdynamics365.com/guides/retail-loyalty-program-deep-dive). ## Who it's for — and who it isn't Commerce targets mid-size to large retailers — roughly the 10-stores-to-thousands range — that want omnichannel from one platform and are (or are becoming) an F&O shop, since Commerce presumes the F&O foundation. Grocery, fashion, speciality, and increasingly B2B-heavy distributors selling through portals all fit. Microsoft packages the retail story, with Commerce at its centre, under [Microsoft Cloud for Retail](https://www.solvingdynamics365.com/guides/microsoft-cloud-for-retail). Who it isn't for: a 3-store retailer or an e-commerce-only brand. That profile fits [Business Central](https://www.solvingdynamics365.com/guides/what-is-business-central) plus a retail ISV or a Shopify-class storefront at a fraction of the cost and timeline. And at the very top end, global retailers sometimes keep a specialist OMS or POS estate and use F&O behind it — a legitimate architecture, just not the unified one. Licensing follows the F&O pattern: per-user Commerce licences on the operations side, with e-commerce and scale-unit capacity as add-ons. Budget the implementation in quarters, not weeks — this is an ERP-grade project with stores attached. ## The trade-off The honest summary: Commerce is a substantial commitment — multi-month to multi-year, with real infrastructure and partner-skill requirements — and the payoff is genuine omnichannel from one database, which point-solution stacks chronically promise and rarely deliver. If you're already committed to F&O and run real stores, it belongs on the shortlist. If you're not, the F&O prerequisite is the first decision to make — start with [Business Central vs Finance and Operations](https://www.solvingdynamics365.com/guides/business-central-vs-finance-and-operations). ### Frequently asked questions **What is a Commerce Scale Unit?** The channel-facing runtime that serves the Retail Server APIs and holds the channel database, so stores, e-commerce, and the call centre keep trading even when head office in Finance and Operations is busy or unreachable. Data moves between the two through Commerce Data Exchange distribution jobs. **Why does a price change not appear at the till immediately?** Because Commerce is hub-and-spoke. Prices, products, and assortments reach channels through scheduled Commerce Data Exchange jobs, and transactions come back the same way for statement posting. Timing follows the job schedule, not the save button. **Does Dynamics 365 Commerce require Finance and Operations?** Yes. Head office — merchandising, pricing, assortments, statement posting — lives in Finance and Operations, and Commerce presumes that foundation. A retailer not already committed to F&O has to make that decision first. **Should I use the built-in e-commerce storefront or go headless?** Mid-market retailers typically run the built-in storefront. Larger ones go headless, keeping Commerce as the engine for products, prices, inventory, and orders through the Commerce Scale Unit APIs while building their own front end — more expensive, but it frees the front-end roadmap from Microsoft's release cadence. **Is Commerce right for a small retailer?** No. A three-store retailer or an e-commerce-only brand is better served by Business Central plus a retail ISV or a Shopify-class storefront. Commerce targets roughly ten stores to thousands and should be budgeted in quarters, not weeks. --- # Dynamics 365 Finance environments and Lifecycle Services How environments work in Dynamics 365 Finance and Supply Chain — Tier 1 through Tier 5, the role of Lifecycle Services, and the move to managed environments. Source: https://www.solvingdynamics365.com/guides/dynamics-365-finance-environments-and-lcs Section: Finance & SCM / Finance Published: 2026-05-01 Updated: 2026-08-31 ### Key facts - F&O sandboxes are sized by tier — Tier 1 is a single-box dev environment, Tier 2 is a multi-box high-availability sandbox close to production scale, and Tier 3-5 scale further for very large customers. - Tier 1 sandboxes can be self-deployed from Lifecycle Services in hours, while Tier 2+ sandboxes and production are provisioned by Microsoft as part of FastTrack onboarding with paperwork and lead times. - Custom code, configuration, and reports move through LCS as deployable packages built in Visual Studio — there is no direct dev-to-production publish, only the staged package process. - New deployments increasingly land in the unified admin experience, where F&O environments are created and managed from the Power Platform admin centre on Dataverse-linked infrastructure, though LCS remains real for the existing installed base. - Sandboxes beyond a minimum included set are paid add-ons, and every environment rides the same continuously-updated application under the One Version policy, so updates apply sandbox-first. Environments in Dynamics 365 Finance and Supply Chain Management (collectively, the *Finance and Operations* apps) are more involved than in Business Central. They're sized as named **tiers**, provisioned through **Lifecycle Services (LCS)**, and operated under a mixed responsibility model that customers and partners both need to understand. ## Environment tiers Sandboxes are sized by tier, where the tier indicates infrastructure scale rather than just function: - **Tier 1** — a single-box development environment running on one Azure VM. Suitable for code work, not for realistic data volumes or concurrent users. - **Tier 2** — a multi-box, high-availability sandbox close to production scale, used for UAT, load testing, and golden-config builds. Every Finance/SCM project gets at least one Tier 2. - **Tier 3, 4, 5** — progressively larger sandboxes for very large customers. - **Production** — Microsoft-managed, high-availability, with a defined SLA. A typical mid-size project runs one production, two Tier 2 sandboxes (UAT plus a golden-configuration build), and a handful of Tier 1 dev boxes — one per developer, since Tier 1 machines don't share well. Large programmes add a dedicated Tier 2+ for performance testing with production-scale data. The tier decision is hard to reverse cheaply, so size the topology during contracting, not after: it appears on the licence bill. ## Provisioning Tier 1 sandboxes can be self-deployed from LCS in hours. Tier 2+ sandboxes and production are provisioned by Microsoft as part of FastTrack onboarding, with paperwork and lead times. ## Lifecycle Services (LCS) LCS is the cloud portal where customers and partners manage F&O implementations — project workspaces, environment requests, deployment of code packages, application of platform updates, support ticket management, the Business Process Modeller, the BPM-Task Recorder integration, and asset libraries. Every Finance/SCM environment is registered to an LCS project. ## Deployable packages Custom code, configuration, and reports flow through LCS as **deployable packages** built from Visual Studio. A package is uploaded to LCS, then applied to an environment by an authorised user. There is no direct dev → prod publish; everything goes through the staged process. ## Database refresh LCS handles **point-in-time copy** of production to sandbox for testing with real data, with golden-record masking for sensitive fields. The reverse path (sandbox → prod) is limited and tightly controlled. ## Database refresh discipline Two practices separate calm projects from chaotic ones. First, schedule refreshes on a cadence (monthly UAT refresh is common) rather than on demand — every refresh wipes sandbox-only data, users' saved views, and any test setup, so surprise refreshes burn tester goodwill fast. Second, script the post-refresh steps: re-pointing integration endpoints away from production URLs, disabling outbound email and [batch jobs](https://www.solvingdynamics365.com/guides/batch-jobs-and-batch-groups-in-f-and-o) that would fire against real customers, and re-applying test accounts. A production-copy sandbox that still holds live payment-file configurations is an incident waiting to happen. This is a core part of [test data management](https://www.solvingdynamics365.com/guides/test-data-management-for-dynamics-365). ## The move away from LCS The direction of travel is unambiguous: F&O environments are becoming ordinary Power Platform environments. New deployments increasingly land in the **unified admin experience**, where environments are created and managed from the Power Platform admin centre, run on Dataverse-linked infrastructure, and pick up capabilities the classic model lacked — self-service copy and restore, Power Platform-style backup, and one security and ALM story across F&O and Dataverse. LCS remains real for the large installed base — deployable packages, existing project workspaces, and Tier 2+ operations still live there — but treat any new capability investment in LCS-specific tooling with suspicion. For a new implementation, ask the partner explicitly which model the project will deploy on; the answer changes the run-book you'll operate for years. See [run-book operations after go-live](https://www.solvingdynamics365.com/guides/run-book-operations-after-dynamics-365-go-live) for what that operating rhythm includes. ## Environments and One Version Every environment rides the same continuously-updated application under the [One Version](https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates) policy. Practical consequence: updates are applied sandbox-first, and the update calendar becomes part of environment planning — a UAT cycle that straddles a platform update tests two different versions unless you pin the schedule deliberately. Keep at least one sandbox a version ahead of production during update windows, and fold the update rhythm into [release management](https://www.solvingdynamics365.com/guides/release-management-for-dynamics-365). ## Cost Sandboxes beyond a minimum included set are paid add-ons — a Tier 2 is a material line item, which is why topology belongs in the commercial negotiation. Resist the temptation to save money by sharing one Tier 2 between UAT and golden configuration on an active project; the scheduling collisions cost more than the environment. Plan environment topology and SKUs early, alongside the wider [environment strategy](https://www.solvingdynamics365.com/guides/environment-strategy-for-dynamics-365-projects). --- # Electronic Reporting (ER) in Finance & Operations How the Electronic Reporting framework in Dynamics 365 Finance and SCM generates statutory filings, e-invoices. Source: https://www.solvingdynamics365.com/guides/electronic-reporting-in-f-and-o Section: Finance & SCM Published: 2026-08-31 Every jurisdiction wants something structured out of your ERP — a VAT return in the tax authority's XML, an e-invoice in the national schema, a payment file your bank will accept, a SAF-T audit export. Historically that meant hard-coded, per-country report code that only Microsoft or a developer could change. [Electronic Reporting (ER)](https://www.solvingdynamics365.com/glossary/electronic-reporting) is Dynamics 365 Finance and Supply Chain Management's answer: a configurable engine where the *format* of an output is data, not code — versioned configurations that can be imported, extended, and updated without touching X++. If you run F&O in more than one country, ER is not optional plumbing; it's the layer your statutory compliance actually lives in, and it deserves a named owner. ## The three-layer configuration model An ER solution is a small stack of configurations, each a separate, versioned artefact: 1. **Data model** — an abstract, business-level description of the information a document needs (an "invoice" with parties, lines, taxes), independent of both F&O's tables and the output format. 2. **Model mapping** — binds the data model to real F&O data sources: tables, entities, calculated fields. This is the layer that knows where amounts and VAT numbers live. 3. **Format** — describes the physical output (XML elements, JSON structure, fixed-width positions, Excel or Word layouts for configurable business documents like customer invoices) and maps each node back to the data model. The separation is the point. When a tax authority revises its schema, only the format changes; when you customise a table, only the mapping needs attention. Formats also support **derived configurations**: you extend Microsoft's format with your changes in a child version, and when Microsoft ships an update you *rebase* rather than re-implement — the same upgrade-safe philosophy as AL extensions or F&O's own extension model, applied to file layouts. ER runs in both directions. Outbound covers the statutory catalogue — VAT declarations (UK MTD among them, feeding [the F&O tax engine](https://www.solvingdynamics365.com/guides/the-f-and-o-tax-engine)), EU sales lists and [Intrastat](https://www.solvingdynamics365.com/guides/intrastat-reporting-in-f-and-o), SAF-T, e-invoicing formats like Italy's SDI or Mexico's CFDI, and payment files from SEPA credit transfers to [positive pay](https://www.solvingdynamics365.com/guides/positive-pay-files-in-f-and-o). Inbound lets the same machinery *parse* structured files — bank statements (camt.053), payment returns — into F&O. ## Where configurations come from Almost never from you. Microsoft maintains hundreds of localisation configurations and publishes them through a **global repository**, historically surfaced via LCS and the Regulatory Configuration Service and now consolidated under the **Globalization Studio** umbrella in the product itself. The working model is: import Microsoft's configuration for your country and document type, and only create a derived version if you genuinely need a deviation (a bank that wants a non-standard reference field, a customer-specific e-invoice extension). Each configuration carries a **configuration provider** identity. Leave Microsoft's configurations owned by Microsoft and put your derived versions under your own provider — it's what makes "which of this is ours?" answerable two years later. ## Running ER without drowning The framework is sound; the operational failure modes are predictable: - **Version drift.** Tax authorities and banks change schemas on their schedule, and Microsoft ships updated configurations continuously — outside the application release cadence. If nobody watches for updates, you find out from a rejected filing. Make checking for new versions of your active configurations a monthly task with a named owner, and treat configuration updates like small changes: import to a sandbox, test with real documents, then promote. - **Configurations are not in your ALM pipeline by default.** They move as exported XML files or repository imports, not in the deployable package. Decide deliberately how they travel from sandbox to production — who exports, who imports, where the file is archived — or production quietly runs a different version than what was tested. - **Editing Microsoft's version directly.** Change the base configuration instead of a derived one and the next Microsoft update becomes a merge headache or an overwrite. Derive, always. - **Treating ER as a developer-only tool.** The format designer is genuinely usable by a strong functional consultant, and the people who understand the statutory requirement are usually functional. Teams that route every ER tweak through X++ developers pay in both queue time and translation errors. ## When ER is the wrong tool ER excels at structured, document-shaped, compliance-driven outputs. It is not a BI layer — analytical reporting belongs in the [Finance reporting stack](https://www.solvingdynamics365.com/guides/dynamics-365-finance-reporting-tools) — and it's not an integration platform: recurring high-volume data exchange with other systems is [DMF and data entities](https://www.solvingdynamics365.com/guides/data-management-framework-deep-dive) territory, and event-driven integration belongs to the platform's messaging patterns. The rule of thumb: if a government, bank, or trading partner prescribes the file's exact shape, ER; if you control both ends, use the integration surfaces built for it. The strategic reason to invest a little in ER literacy: e-invoicing and digital reporting mandates are spreading, country by country, and each new mandate lands on this framework. An implementation that knows how to import, derive, test, and promote ER configurations absorbs the next mandate as routine maintenance; one that doesn't turns each into a mini-project. --- # F&O batch job and workflow errors Why a Finance and Operations batch job or workflow gets stuck or fails — batch server, queue, and workflow errors decoded. Source: https://www.solvingdynamics365.com/guides/f-and-o-batch-job-and-workflow-errors Section: Finance & SCM / Troubleshooting Published: 2026-09-06 Finance and Operations runs two separate background systems that generate their own error classes: the **batch framework**, which schedules and executes recurring or one-off background tasks across a pool of batch servers, and the **workflow engine**, which routes approval-style business processes between users. Both can silently stall rather than fail loudly, which is why monitoring matters as much as error-message decoding. ## A batch job stuck in "Waiting" and never picked up **Symptom.** A batch job is queued but never transitions to "Executing," sometimes for hours. **Cause.** No batch server with an appropriate batch group assignment is available to pick it up — either all batch servers are busy with higher-priority or long-running jobs, or the job's configured batch group isn't served by any currently-running batch server thread. **Fix.** Check the System Administration batch server configuration for which batch groups each server processes, and confirm at least one server actively serves the group this job is assigned to. Increase batch server threads or rebalance batch groups if a specific group is consistently starved. **Prevention.** Design batch groups deliberately around job priority and expected runtime (a fast, frequent group separate from a slow, occasional one) so a long-running job in one group can't starve unrelated quick jobs waiting in the same queue. ## Batch job fails with an unhandled exception, retries automatically, fails again **Symptom.** A batch job's history shows repeated failures with the same underlying exception, each attempt identical to the last. **Cause.** The job hit a genuine data or code error that a retry doesn't fix — a locked record, a validation failure against specific data, or a bug in the job's own X++ code. Automatic retry (where configured) only helps with genuinely transient failures like a momentary connectivity blip. **Fix.** Read the actual exception in the batch job's history (not just "failed") to find the real cause, and fix the underlying data or code issue rather than relying on further retries. **Prevention.** Set a sensible maximum retry count rather than unlimited retries for jobs prone to data-related failures — an infinitely-retrying job that will never succeed just wastes batch server capacity that other jobs need. ## Workflow stuck with no pending approver notified **Symptom.** A record (a purchase requisition, an expense report) shows as "In review" or "Pending" in a workflow, but the expected approver never receives a notification and can't find it in their work items. **Cause.** Most commonly a workflow configuration issue: the approval hierarchy or role-based assignment resolved to nobody (an empty manager field, a role with no members), or the workflow's notification settings are misconfigured separately from the assignment itself. **Fix.** Check the workflow history for the specific step and who (if anyone) it assigned the work item to; if it resolved to no one, fix the underlying hierarchy or role membership gap and either restart or manually reassign the stuck instance. **Prevention.** Build a fallback assignment (an escalation after N days with no action, or a default approver when a hierarchy lookup returns empty) into every approval workflow design — a workflow with no fallback for missing data will eventually strand a record with nobody able to act on it. ## "Cannot edit a record in a closed period" style batch failures during period-end **Symptom.** A batch job that posts or recalculates transactions fails during or immediately after a period close, citing a closed period. **Cause.** The batch job was scheduled to run against a period that closed (deliberately, as part of the close process) between when it was queued and when it executed. **Fix.** Reschedule the job against the correct open period, or coordinate the period-close timing with any recurring batch jobs so they don't overlap the close window. **Prevention.** Document which recurring batch jobs touch financial periods and explicitly pause or reschedule them around the close calendar, rather than discovering the conflict when a job fails mid-close. ## Where to go next The wider release and update cadence these background systems run inside is covered in [One Version and updates in Finance and SCM](https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates). For the data-movement side specifically, see [the Data Management Framework](https://www.solvingdynamics365.com/guides/data-management-framework-deep-dive) and [year-end close in F&O](https://www.solvingdynamics365.com/guides/year-end-close-in-f-and-o) for the period-close context above. ### Frequently asked questions **Why does a batch job show as 'Executing' but never finish?** Usually a batch server-side crash or timeout that didn't clean up the job's status correctly, or a genuinely long-running job (a large data recalculation) that's still working but past the point most people expect. Check the batch job's history and the AOS event log before assuming it's stuck versus just slow. **Is a workflow error the same as a batch job error?** No — batch jobs are Finance and Operations' background task scheduler (recalculations, imports, posting routines), while workflows are the business-process approval engine (purchase requisition approvals, and similar). They share some infrastructure but fail for different reasons and are diagnosed in different places. --- # F&O data entity import and export errors Why a Data Management Framework import or export fails in Finance and Operations — staging, validation, and mapping errors decoded. Source: https://www.solvingdynamics365.com/guides/f-and-o-data-entity-import-export-errors Section: Finance & SCM / Troubleshooting Published: 2026-09-06 The **Data Management Framework** (DMF) moves data in two stages — records land in a **staging table** first, where they're validated against the target entity's business logic, and only records that pass staging are written to the real Finance and Operations tables. Understanding that two-stage model is the key to reading every DMF error correctly: the error is almost always a staging-validation rejection, not a database-level failure. ## Import shows "Error" with records rejected at staging **Symptom.** A data project's execution finishes with a mix of successful and rejected records, and the rejected count is nonzero. **Cause.** One or more rows failed a business validation the target entity enforces — a missing required field, a reference to a code (a customer group, an item number) that doesn't exist in this legal entity, or a value outside an allowed range. **Fix.** Open the staging table view for the failed rows (available from the data project's execution history) to see the specific validation message per row, fix the source file or mapping, and re-run the import — DMF only reprocesses failed rows on a retry, not the ones that already succeeded. **Prevention.** Validate reference data (customer groups, item numbers, dimension values) exists in the target legal entity *before* a large import, not after discovering the gap through hundreds of rejected rows — a small pre-check script or a manual spot-check of the reference tables catches this class of failure cheaply. ## "Sequence contains no elements" or similar .NET-style exceptions during import **Symptom.** An import fails with a raw exception message that doesn't look like a business validation error — a stack trace or a generic .NET exception type. **Cause.** This usually indicates the entity's underlying code (its data entity class, or a plug-in/customisation on top of it) hit an unexpected condition the standard validation didn't anticipate — often a genuinely malformed source file (wrong column count, an encoding issue) rather than a business rule violation. **Fix.** Check the source file's structure exactly matches the entity's expected format (column names, required columns present, correct file encoding), and check whether a customisation on the entity is involved if the standard entity alone wouldn't produce this error. **Prevention.** Always import a small test batch (a handful of rows) before running a full file through a new or changed data entity mapping — a structural mismatch shows up immediately on a small batch instead of after processing thousands of rows. ## Export produces fewer rows than expected, no error shown **Symptom.** An export from a data entity completes successfully but the row count is lower than the source table's actual row count. **Cause.** Data entities apply their own filtering and security context — a legal-entity-scoped entity only exports the legal entity the export is run under, and some entities apply additional implicit filters (active records only, a specific status) that aren't obvious from the entity name alone. **Fix.** Check the entity's underlying query definition (or documentation) for implicit filters, and confirm the export was run under the intended legal entity context. **Prevention.** When building an integration against a data entity for the first time, verify the exported row count against a manually-run query with the same intended scope before trusting the entity's default behaviour matches expectations. ## Recurring integration job silently stops running **Symptom.** A scheduled recurring data-project integration (file-drop or HTTP-triggered) that ran reliably stops producing new imports/exports, with no error surfaced anywhere obvious. **Cause.** Recurring integrations depend on the batch framework underneath — see [F&O batch job and workflow errors](https://www.solvingdynamics365.com/guides/f-and-o-batch-job-and-workflow-errors) — so a stalled batch server or a starved batch group silently stops the recurring job the same way it would any other batch task. **Fix.** Check the recurring data job's batch history the same way as any batch job, not just the data project's own configuration screen. **Prevention.** Monitor recurring integration jobs' last-successful-run timestamp explicitly (an alert if it exceeds the expected interval) rather than assuming "no error" means "still running." ## Where to go next The framework itself is covered in [the Data Management Framework](https://www.solvingdynamics365.com/guides/data-management-framework-deep-dive), and the near-real-time alternative in [dual-write integration between F&O and Dataverse](https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-integration). ### Frequently asked questions **Where do I actually see the error for a failed DMF import?** The data project's execution history shows a per-record status, and the staging table view (accessible from the data project) shows the specific validation error per row — the summary status alone ('Error') rarely says enough to fix anything; always drill into the staging-level detail. **Does a partially-failed import leave bad data behind?** No — records that fail validation are rejected at the staging step and never reach the target table; only records that pass validation are actually inserted or updated. A partial failure means some rows succeeded and some didn't, not that failed rows landed corrupted. --- # Finance and Operations and the Power Platform How Dynamics 365 Finance and Supply Chain extend through the Power Platform — virtual entities, Power Automate, Power Apps, and AI Builder. Source: https://www.solvingdynamics365.com/guides/finance-and-operations-and-the-power-platform Section: Finance & SCM / Overview & platform Published: 2026-05-01 Dynamics 365 Finance and Supply Chain Management (F&O) didn't start life on the Power Platform — they were built on their own database and their own X++ runtime, and they remain there today. But Microsoft has, over several years, wired the Power Platform deeply into F&O so customers can extend, automate, and analyse without writing X++. ## Virtual entities F&O exposes its data entities to Dataverse as **virtual entities** — they look and behave like Dataverse tables but live in the F&O database. Power Apps, Power Automate, Copilot Studio, and Power BI can all read and (where supported) write through them. Virtual entities don't replicate data, so there's no latency or storage cost beyond F&O itself; the trade-off is that operations are bounded by F&O API throughput. ## Power Automate The Power Automate connector for F&O supports common operations on data entities. The most useful pattern: trigger a flow on an event in another system (a Slack message, a Form submission, a Logic Apps webhook) and create/update an F&O record without writing custom code. Heavy bulk work still belongs in DMF, but transactional automation is right at home in flows. ## Power Apps Canvas Power Apps over F&O virtual entities deliver purpose-built front ends — expense submission on mobile, warehouse-floor look-ups, executive dashboards — without putting the heavy F&O UI in front of a casual user. ## Embedded apps F&O pages can **embed Power Apps inline**, so an extension on a vendor card might show a canvas app fetching from an external system, with the same single sign-on. The reverse is also true: F&O views embed in model-driven Power Apps over Dataverse. ## AI Builder AI models trained in **AI Builder** (object detection, form processing, prediction) are callable from Power Automate flows that read or write F&O data. The classic use case: scan vendor invoices, extract line data with form processing, post the result as a draft vendor invoice in F&O. ## Microsoft Fabric F&O data flows into **OneLake** through Microsoft's **Synapse Link** for analytics, where Power BI and other Fabric tools query it without touching F&O. This is replacing the older Export to Data Lake (Synapse) and BYOD patterns. ## Copilot F&O ships with embedded copilots for finance and supply chain tasks; customers extend the experience with **Copilot Studio** agents that combine F&O data with other systems. ## Net effect Modern F&O implementations layer the Power Platform on top instead of building X++ where they can. It's faster, cheaper, and survives Service Updates better. --- # Finance and Operations database synchronization errors Why an X++ table or field change fails to synchronize into the SQL database in Finance and Operations — and how to read the sync log. Source: https://www.solvingdynamics365.com/guides/finance-and-operations-database-synchronization-errors Section: Finance & SCM / Troubleshooting Published: 2026-09-06 Every X++ table, field, or index change is metadata until a **database synchronization** turns it into real SQL Server schema — column additions, index rebuilds, foreign-key constraints. Sync failures are almost always the schema disagreeing with either the data already in the table or another object's metadata, not a transient platform fault. ## "Table X could not be synchronized. SqlException: … cannot insert the value NULL" **Symptom.** Synchronization fails on a table where a field was changed from optional to mandatory (or a new field was added as `NoNo` — not nullable), and existing rows already have a null in that column. **Cause.** SQL Server refuses to apply a `NOT NULL` constraint to a column that already contains nulls; synchronization does not backfill data on your behalf. **Fix.** Either give the field a default value and run an update job to backfill existing rows before changing its "mandatory" property, or keep the field nullable in the extended data type / field properties until a data-fix job has run. **Prevention.** Treat "make an existing field mandatory" as a two-step release (ship the data fix first, flip the property in a later deployment), never a single same-day change on a table with production rows. ## "Cannot create the clustered index … because it conflicts with the existing…" / index/key conflicts **Symptom.** Synchronization fails when a table's primary index or a unique key definition changes and existing rows would violate the new constraint (duplicate values that only become invalid under the new key). **Cause.** SQL Server cannot build a unique or clustered index over data that already contains duplicates or NULLs where the new definition disallows them. **Fix.** Query the table for the actual duplicate rows the new index would reject, resolve or archive them, then re-run synchronization — the sync error message names the table and index but not the offending rows, so this always needs a manual data check first. **Prevention.** Run schema changes that add or tighten a unique key against a refreshed copy of production data in a sandbox tier before scheduling the change for a live environment. ## Full synchronization runs for a very long time or appears to hang **Symptom.** A full database synchronization (rather than an incremental sync of just the changed objects) takes hours, or the deployment/build pipeline step running it times out. **Cause.** Full sync recompiles metadata and reconciles schema for every table in the application, which scales with the number of customizations and the size of the environment's metadata store — it is a different order of magnitude of work from an incremental sync of one changed table. **Fix.** Prefer incremental synchronization (synchronizing only the specific tables touched by the change) for routine development and reserve full synchronization for major version upgrades or after a bulk metadata import, where Microsoft's guidance is to expect it to run considerably longer. **Prevention.** Schedule full-synchronization steps in a build or release pipeline with a generous timeout and outside business hours, rather than assuming it behaves like an incremental sync of a handful of tables. ## Synchronization succeeds but the application still shows the old schema **Symptom.** Synchronization completes without error, but a form, report, or data entity built on the changed table still behaves as if the old field or index is in place. **Cause.** Application object caches (the AOS metadata cache, or a cached data entity/view built on the changed table) were not refreshed after the underlying table changed, so the running application server is still serving stale metadata. **Fix.** Restart the AOS service (or recycle the environment, in a cloud-hosted Tier) after a successful synchronization that changed a table's shape, and rebuild any data entity or view that depends on the changed table. **Prevention.** Make "restart AOS after a schema-changing deployment" a standard step in the deployment checklist rather than a step someone remembers only after hitting this. ## Where to go next The broader X++ extension model this schema sits under is in [F&O X++ language](https://www.solvingdynamics365.com/guides/f-and-o-x-plus-plus-language); data movement in and out of these tables is covered in [F&O data entity import/export errors](https://www.solvingdynamics365.com/guides/f-and-o-data-entity-import-export-errors) and [Data Management Framework deep dive](https://www.solvingdynamics365.com/guides/data-management-framework-deep-dive). ### Frequently asked questions **Why does Finance and Operations need a separate synchronize step at all?** X++ tables and fields are metadata-first — you define the table in the Application Explorer, and synchronization is the step that generates the matching SQL schema (columns, indexes, foreign keys) from that metadata. Nothing in the database changes until synchronization runs, which is also what makes a bad schema change safe to catch before it reaches a shared environment. **Is it safe to synchronize in a Tier-2 (UAT/production-class) environment the same way as a developer VM?** Full synchronization is a heavier, more disruptive operation than in a personal dev VM — it can lock tables and take much longer against real data volumes, so it is normally run through a scheduled deployment window or the environment's build/release pipeline rather than triggered ad hoc by a developer. --- # Financial dimensions in Dynamics 365 Finance How financial dimensions work in Dynamics 365 Finance — global dimensions, account structures, default dimensions. Source: https://www.solvingdynamics365.com/guides/financial-dimensions-in-dynamics-365-finance Section: Finance & SCM / Finance Published: 2026-05-01 ### Key facts - Dynamics 365 Finance allows up to ten financial dimensions, compared with up to eight global dimensions in Business Central. - Entity-backed dimensions source their values from an existing F&O entity (Customer, Vendor, Site, Warehouse, Worker, Project), so the dimension value is the entity's own ID rather than a separately maintained code. - An account structure enforces, at posting time, which dimensions are required and in what combination for a given GL account range — wrong combinations are blocked rather than merely flagged. - Default financial dimensions on a master record can be fixed (never overridable) or flexible (overridable at the transaction line), and default-priority rules decide which master's defaults win when several appear on one transaction. - Dimension values unused for 12 months are the usual candidates for deactivation, and the general design advice is to work back from the reports the business needs rather than reaching for all ten dimensions. Where Business Central has up to eight global dimensions, **Dynamics 365 Finance** allows up to ten **financial dimensions**, with a richer account-structure model on top. Designing the dimension framework is one of the most consequential decisions of any F&O implementation — it sets the reporting flexibility for the next decade. ## Financial dimensions Each dimension represents an analytical axis — Department, Cost Centre, Project, Region, Brand, Activity, etc. Dimensions have *values* (the codes within the dimension) and metadata (descriptions, defaults, validations). **Two flavours of dimensions.** - **Custom dimensions** — codes maintained in the dimension table. Used for axes that don't naturally exist as Dataverse-like entities (Cost Centre, Activity, Project Code if not using full Project Operations). - **Entity-backed dimensions** — the dimension is sourced from an existing F&O entity (Customer, Vendor, Item, Worker, Project). The dimension value *is* the entity's ID. Powerful: a Customer dimension means transactions automatically tag the customer without manual entry. Common entity-backed dimensions: Customer, Vendor, Site, Warehouse, Worker, Project. ## Account structures This is where F&O surpasses BC. An **account structure** defines, for a given GL posting, which dimensions are required and in what combination. The structure is a set of **segments** where each segment lists allowed values and the relationships between segments. Example: an account structure might specify that for revenue accounts (411xxx), the Department segment must come from a list of operational departments, and the Project segment must be non-empty. For balance-sheet accounts (1xxx), no Project is allowed. The system enforces the structure at posting time — wrong combinations are blocked. The complementary mechanism that decides *which* main account a given subledger transaction hits in the first place is [posting profiles](https://www.solvingdynamics365.com/guides/dynamics-365-posting-profiles); dimensions and account structures constrain the result, posting profiles determine it. ## Advanced rules Beyond the basic account structure, **advanced rules** add conditional logic: when a specific account is used, require additional dimensions or constrain values. Used for compliance and statutory regimes that require dimension scrutiny on specific account types. ## Default financial dimensions Each master record (Customer, Vendor, Item, GL Account, Worker, Project, Site) carries **default financial dimensions** that flow onto transactions where the master is used. Defaults can be **fixed** (cannot be overridden) or **flexible** (the user can override at the transaction line). ## Default priority When multiple masters appear on the same transaction (a sales line involves customer, item, salesperson), the **default priority** rules decide which master's defaults win for each dimension. Configure these carefully — wrong priority assigns the wrong cost centre on every transaction. ## Derived dimensions F&O can derive a dimension value from a formula or lookup — e.g. derive Region from the Customer's address. Reduces manual entry; introduces dependencies. ## Reporting dimensions When reporting, dimensions can be: - **Flat-rolled** — view spending across all dimensions on a single account, summed. - **Sliced** — view spending broken down across one or more dimensions side by side. - **Combined** — multiple dimensions intersect in pivot-style reports. Both Financial Reporting and Power BI consume the dimension structure. **Design discipline.** - Start from the management reports the business needs. Work backwards to the dimensions required. - Don't reach for ten dimensions when six will do. More dimensions slow performance and increase data-entry burden. - Document the dimension semantics — what each value means, what counts as a valid combination — so the design survives staff turnover. - Revisit annually — dimension values that haven't been used in 12 months are usually candidates for deactivation. ## Where to go next Dimensions are set up per [legal entity](https://www.solvingdynamics365.com/guides/legal-entity-setup-in-f-and-o) and exercised on every [general journal entry](https://www.solvingdynamics365.com/guides/general-journal-entry-workflow-in-f-and-o); they are what [budget control](https://www.solvingdynamics365.com/guides/budget-control-in-f-and-o) enforces against and what the [reporting tools](https://www.solvingdynamics365.com/guides/dynamics-365-finance-reporting-tools) slice by. For the Business Central counterpart — a different model with a similar purpose — see [dimensions design in Business Central](https://www.solvingdynamics365.com/guides/business-central-dimensions-design). --- # Fiscal calendar setup in Dynamics 365 Finance How fiscal calendars are configured in F&O — periods, years, multiple calendars per ledger, and the implications for posting, closing, and reporting. Source: https://www.solvingdynamics365.com/guides/fiscal-calendar-setup-in-f-and-o Section: Finance & SCM / Finance Published: 2026-06-22 Every legal entity in Dynamics 365 Finance posts transactions against a **fiscal calendar** that defines its accounting periods. Configuring fiscal calendars correctly at implementation is one of those decisions that's mundane to make and painful to reverse — the calendar shapes period close, reporting, and posting permissions for years. **The model.** - **Fiscal calendar** — a top-level container of fiscal years. - **Fiscal year** — typically 12 months but can be longer or shorter (e.g. a stub year during transitions). Has a start date and end date. - **Period** — a month within the year (typically), with start and end dates and a closing offset for the close window. - **Module-specific status per period** — each module (General Ledger, Inventory, Bank, Fixed Assets, etc.) can have its own period status (Open, On Hold, Closed) per period. ## Multiple calendars F&O supports multiple fiscal calendars in one environment: - **Statutory calendar** — the calendar aligned to local tax / regulatory periods. - **Group reporting calendar** — the calendar aligned to the parent company's reporting cadence (often different from the subsidiary's statutory calendar). - **Tax calendar** — for jurisdictions requiring a separate tax calendar. Each ledger references one fiscal calendar; multiple ledgers can share a calendar. **Fiscal year structure.** - **Calendar year** — Jan-Dec. Most common in commercial contexts. - **Non-calendar year** — e.g. April-March (UK statutory for some sectors, Japan), July-June (Australian government, some commercial), August-July, etc. - **52/53-week year** — retailers and some industries use 13 four-week periods plus an occasional extra week year. Microsoft supports this via dedicated configurations. - **Stub year** — when transitioning between fiscal-year structures, a stub year of unusual length (e.g. 3 months, 15 months) bridges. **Period structure.** - **12 calendar months** — standard. - **13 four-week periods** — for 52/53-week retailers. - **52 weeks** — granular retail. - **52 weeks + Period 13** — for 4-4-5 retail accounting calendars. ## Open and close per module A period can be: - **Open** for all modules — transactions can post anywhere. - **Closed** for GL but **Open** for Inventory — finance has locked the period but warehouse adjustments still allowed. - **Closed** entirely — no posting in any module. - **On hold** — only privileged users can post; used for the close window. This module-level granularity supports the typical close sequence: close sub-ledgers in order, lock GL last. **Year-end implications.** - **Fiscal year boundary** is when **year-end close** runs (income statement closed to retained earnings). - **Period 12 close** is the last regular period; reports for the year typically run through this. - **Closing date entries** post on the special closing-date pseudo-position (after regular Period 12 transactions but before fiscal year boundary). - **New fiscal year** must exist (be created) before posting in it can happen. ## Adjusting periods Some configurations include an **adjusting period** after Period 12 specifically for year-end adjustments (audit adjustments, accruals identified post-close). The adjusting period has its own date range and posting controls. ## Closing offset Each period has a **closing offset** — how many days after the period end the close window remains open. Configurable per period; controls when the period auto-closes if not manually closed first. ## Multi-entity considerations Multi-entity groups face calendar complexity: - **Same calendar across entities** — simplest; close all entities together; consolidate cleanly. - **Different calendars per entity** — common when subsidiaries have local statutory calendars; close happens per entity; consolidation has timing offsets. - **Parallel statutory and group calendars** — each entity reports on its statutory calendar to local authorities and on the group calendar for consolidation. Requires careful configuration. **Configuration discipline.** 1. **Get the fiscal calendar right at implementation.** Changing it later is invasive. 2. **Create future fiscal years well in advance** — at least a year ahead, ideally two. 3. **Document the close cadence per period** — when each sub-ledger closes, when GL closes, when adjusting period opens / closes. 4. **Communicate close-window restrictions** to users; surprise posting failures are demoralising. **Common pitfalls.** - **Missing future fiscal years** — first posting in a new year fails because the year doesn't exist yet. - **Wrong calendar attached to a new entity** — entity reports on a calendar that doesn't match its statutory requirements. - **Module status drift** — sub-ledgers closed but GL still open lets late posts hit the wrong period. - **Statutory vs reporting calendar confusion** — entity's statutory date is correct but the group sees a different "as-at" date. ## Operational reality Fiscal calendar setup is a one-time architectural decision with lasting impact. Engage the controller and the implementation partner together; verify against statutory requirements per entity; document the resulting configuration. --- # Fixed assets in Dynamics 365 Finance and Operations How F&O handles fixed assets — books, depreciation profiles, acquisitions, disposals, and the integration with project, purchase, and tax accounting. Source: https://www.solvingdynamics365.com/guides/fixed-assets-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 A factory machine, a server rack, an office building, a fleet of trucks — fixed assets are capital expenditures depreciated over their useful life. F&O's **Fixed Assets** module captures the full lifecycle: acquisition, depreciation, revaluation, disposal — with multi-book support for parallel tax and financial reporting. **Core entities.** - **Fixed Asset** — the asset record. - **Asset Group** — grouping for default depreciation profiles, accounts. - **Book** — a "view" of the asset with its own depreciation method. - **Depreciation Profile** — straight-line, declining-balance, etc. - **Depreciation Convention** — half-year, full-month, etc. ## Multi-book architecture A single asset can have multiple books: - **Current (current book)** — financial reporting per GAAP/IFRS. - **Tax (tax book)** — tax depreciation per local rules. - **Statutory** — country-specific reporting. - **Custom** — managerial purposes. Each book has its own depreciation method, life, and posting. The asset accumulates value differently per book. ## Why multi-book matters Tax rules and accounting rules diverge: - Tax may allow accelerated depreciation (Section 179, bonus depreciation in US). - Accounting may require straight-line for matching. - Different lives, different methods. Without multi-book, you'd run separate systems for tax and accounting. F&O integrates both. **Depreciation methods.** - **Straight-line** — equal amount per period. - **Declining balance** — higher early, lower later. - **Sum-of-years digits** — accelerated. - **Units of production** — based on usage. - **Manual** — operator enters. Each method's parameters configured per profile; profiles assigned to asset books. ## Acquisition When an asset is acquired: - **From purchase order** — receipt creates asset acquisition. - **Manual entry** — fixed asset journal directly. - **From project** — capitalised from a project's costs. - **From inventory** — inventory transferred to fixed assets. Each path posts: - Asset value to balance sheet (debit). - Vendor payable or cash (credit). ## Depreciation runs A periodic batch: 1. Identify assets with active depreciation. 2. Calculate depreciation per book per period. 3. Post depreciation expense (debit) and accumulated depreciation (credit). Run monthly typically; some assets require daily for short-lived items. ## Asset revaluation Adjustments after initial recording: - **Write-up** — increase value (asset improvement, market revaluation). - **Write-down** — decrease (impairment). Posted via specific journals; affects future depreciation. ## Disposal When an asset is retired or sold: - **Sale** — asset value out, sales price in, gain/loss to P&L. - **Scrap** — asset value out, loss to P&L. - **Transfer** — to another entity or fund. The disposal journal handles the accounting; tax book may show different gain/loss than current book. ## Asset groups and default values Asset groups simplify configuration: - All "Buildings" — straight-line 30 years. - All "Computers" — straight-line 3 years. - All "Vehicles" — declining-balance 5 years. New assets inherit defaults from their group; can be overridden per asset. ## Integration with projects For long-build assets: - Construction in progress (CIP) accumulates project costs. - On completion, CIP transfers to fixed asset. - Depreciation starts from in-service date. This handles building, manufacturing line install, multi-month asset constructions. **Integration with maintenance.** - Service work orders posted against the asset. - Maintenance costs tracked; not capitalised (usually). - Asset uptime / utilisation tracked. For mining, manufacturing, fleet operations, this integration matters. **Tax depreciation specifics.** - **US** — MACRS (Modified Accelerated Cost Recovery System) classes, bonus depreciation, Section 179. - **EU** — country-specific rules. - **Asia-Pacific** — varies. F&O's tax book handles local rules with appropriate localisations. ## Component depreciation (IFRS) IFRS requires separate depreciation of significant components: - A building's roof depreciated differently than the building shell. - F&O supports parent-child asset structures for components. Component accounting adds complexity but is required for IFRS-reporting entities. ## Mass disposal and mass acquisition For fleet operations: - 50 trucks acquired together — mass acquisition. - 30 retired together — mass disposal. Batch journals handle these efficiently. **Reporting.** - **Asset register** — full list of active assets with values. - **Depreciation forecast** — future depreciation by period. - **Disposal report** — gains/losses. - **Asset transactions** — full ledger per asset. For auditors, the asset register is the canonical source; reconciles to balance sheet. **Common pitfalls.** - **Tax book missed.** Only current book set up; tax depreciation manual; compliance risk. - **Acquisitions through wrong path.** Direct journal entries bypass asset module; asset register incomplete. - **Disposals not posted.** Asset still depreciating after sale; balance sheet wrong. - **Component accounting skipped.** IFRS non-compliance for buildings and complex assets. - **In-service date missing.** Depreciation starts wrong; period overstates. ## Strategic positioning Fixed asset accounting is a core finance discipline. F&O's module is comprehensive and handles most scenarios; for very complex environments (oil and gas with depletion accounting, real estate with multiple component layers, government with fund accounting), specialty extensions or external systems may complement. For most enterprises, F&O Fixed Assets handles the lifecycle natively with appropriate setup. The investment in configuring books, profiles, and conventions at deployment pays back through automated, audit-ready depreciation processing for years. --- # Form extensions in Dynamics 365 Finance and Operations How to extend forms in F&O — extending standard forms, adding controls and groups, handling events, and avoiding common form-extension pitfalls. Source: https://www.solvingdynamics365.com/guides/f-and-o-form-extensions Section: Finance & SCM / AL & X++ development Published: 2026-05-01 Forms in F&O are the visible surfaces of the application — pages users interact with. Adding a field to a vendor card, a new button to a sales order, custom logic on field changes — all of these are done through **form extensions**. They're a core extensibility mechanism; mastering them is essential for productive F&O development. ## The extension model F&O doesn't allow modifying the standard form directly. Instead: - Create a **Form Extension** object in your model. - Reference the standard form being extended. - Add controls, change properties, add event handlers. - At runtime, F&O renders the standard form plus the extension's contributions. This enables Microsoft to update the standard form without breaking your additions. **What you can extend.** - **Add new controls** — fields, buttons, groups, tabs. - **Move controls** within the layout (with limitations). - **Change properties** of existing controls (caption, visibility). - **Add event handlers** — pre/post on form methods. - **Add data sources** — additional tables joined. - **Add menu items** to the form's command bar. **What you cannot do.** - **Delete standard controls.** Hide via Visible = No; cannot remove. - **Reorder major sections** freely; some constraints. - **Override standard methods completely** — you can extend via Chain of Command but not replace. The constraints maintain forward compatibility. **Adding a field.** 1. Create form extension for the form. 2. Add an Extension control of type Field. 3. Bind to a data source field (either standard or your custom table extension). 4. Position via the design surface. The extension's controls are visually merged with the standard form at runtime. ## Adding a tab page Common pattern: - Add a `Tab` control. - Add `TabPage` for new tab. - Inside, group controls relevant to the new functionality. Place tabs in a logical position — typically after standard tabs. **Adding a button.** - Add a `Button` control. - Bind to a menu item action (which targets a class with main method). - Set position, caption, image. The button's click invokes the menu item; the menu item invokes a class method. ## Event handlers in form extensions When you need code triggered by form events: ```x++ class MyFormEventHandler { [FormDataSourceEventHandler(formDataSourceStr(CustTable, CustTable), FormDataSourceEventType::Written)] public static void CustTable_OnWritten(FormDataSource sender, FormDataSourceEventArgs e) { // logic when CustTable is written } } ``` Decorators specify the form, data source, and event. Methods are static. **Common form events.** - **OnInit / OnInitializing** — form startup. - **OnActivated** — when form becomes active. - **OnClosing** — closing. - **OnFieldModified** — field changed. - **OnDataSourceWritten** — record saved. - **OnClicked** — control clicked. Each has specific signature and use case. ## Chain of Command on form controls For overriding behaviour: ```x++ [ExtensionOf(formStr(CustTable))] final class CustTable_Extension { public void clicked() { // pre-logic next clicked(); // post-logic } } ``` `next clicked()` invokes the original method; logic wraps it. ## Data source extensions Add a new table to the form's data sources: - Link to existing data source via join. - New table accessible from form context. - New controls bind to the new data source. Useful when standard form's data set is insufficient. ## Visibility and enablement Often more useful than adding new controls: - Hide a button users shouldn't use. - Disable based on record state. - Show / hide tabs based on permissions. These small UX changes can significantly improve user experience. ## Form patterns F&O has standard form patterns: - **List page** — grid with filters. - **Details master** — single record with sections and tabs. - **Transaction details** — header + lines. - **Workspace** — KPI-driven landing page. Extending forms requires understanding the pattern; e.g., adding a tab to a list page works differently than to a details form. **Form personalisation vs extension.** - **Personalisation** — per-user; users adjust their views. - **Extension** — per-tenant code; everyone sees. Don't use extensions for things users could personalise; reserve for true customisation needs. **Performance considerations.** - **Heavy event handlers** slow form opening. - **Cross-table queries** in handlers — careful. - **Lazy load** patterns — show data only when tab is opened. **Common pitfalls.** - **Overcomplicated extensions.** Many extensions stacking; form behaviour unpredictable. - **Hidden controls.** Setting Visible=No without context; users confused. - **Event handler not firing.** Wrong event signature; debugging confused. - **Conflicting extensions.** Two extensions modify same control; last one wins (sometimes). - **No labels.** Custom controls without labels; non-accessible. - **Permission gaps.** New controls visible to users who shouldn't see them; security review. ## Testing Form extensions should be tested: - Open form in each role. - Verify visibility / enablement. - Test event handlers. - Performance on opening. Manual testing essential; automated UI testing is heavier in F&O. **Best practices.** - **One extension per functional area** — don't stuff everything in one extension. - **Document the extension** — what it adds, why. - **Clear naming** — `CustTable_Extension_LoyaltyFields` vs cryptic. - **Version per release** — tied to your codebase versioning. ## Strategic positioning Form extensions are how F&O is tailored to specific business needs. They're a core developer skill. Mastery includes understanding the extension model, the event system, the form patterns, and the maintenance discipline. Over a project's lifetime, accumulated form extensions become significant code; treating them with the same engineering rigour as any production code — review, testing, documentation — keeps the customisation maintainable. Without discipline, accumulated extensions become a tangle no one wants to touch. --- # General journal entry workflow in Dynamics 365 Finance How a general journal is captured, validated, approved, and posted in F&O — daily journals, voucher numbers, line types, financial dimensions. Source: https://www.solvingdynamics365.com/guides/general-journal-entry-workflow-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Posting a journal entry is the bread-and-butter of finance work in F&O. The workflow has more validation, approval, and audit-trail steps than it appears at first glance — understanding them is the difference between a clean monthly close and a queue of stuck postings. **General journal architecture.** - **Journal name** — a template defining defaults (voucher series, posting layer, currency, approval workflow, default account/offset). Examples: `GenJrn` for general; `Adjmt` for adjustments; `Accruals` for accruals. - **Journal** — an instance of a journal name; one journal per day or per close step typically. - **Journal lines** — the actual debit/credit entries. ## Creating a journal From `General ledger → Journal entries → General journals`: 1. Click `New`, pick a journal name. 2. The system generates a **journal number** (sequence per journal name). 3. Enter lines. ## Line structure Each line has: - **Date** — posting date. - **Voucher** — the voucher number; multiple lines can share a voucher if they balance. - **Account type and Account number** — Ledger, Customer, Vendor, Bank, Fixed Asset, Project. - **Debit / Credit** amounts. - **Offset account type and number** — the contra side. - **Description** — narrative. - **Financial dimensions** — department, cost centre, project, etc. - **Currency / Exchange rate** — for foreign currency entries. - **Tax group / Tax code** — when tax applies. ## Account types F&O extends the basic G/L model to allow account types beyond Ledger: - **Ledger** — direct G/L posting. - **Customer / Vendor** — posts via the AR/AP subledger; creates a vendor or customer ledger entry. - **Bank** — creates a bank ledger entry. - **Fixed Asset** — creates a fixed-asset transaction. - **Project** — posts to project actuals. Multi-type single-voucher entries are common: a vendor invoice journal has Vendor and Ledger lines; a fixed asset acquisition has Fixed Asset, Vendor, and Ledger lines. ## Voucher and balance The voucher is the grouping unit: - All lines with the same voucher must net to zero (debits = credits). - The voucher series is configured per journal name. - One journal can contain multiple vouchers. Posting validates the balance per voucher before committing. ## Validation chain Before posting: 1. **Field validation** — required fields, valid values, date in open period. 2. **Account validation** — account exists, not blocked, dimension combinations allowed. 3. **Tax validation** — taxes computed and balanced. 4. **Voucher balance check** — debits = credits per voucher. 5. **Period status** — period must be open or sub-ledger-open. 6. **Approval status** — approved if workflow required. Any error stops the post; the journal returns to draft. ## Approval workflows Many companies route journals through approval before posting: - **Conditional workflows** — only journals above threshold or in certain categories require approval. - **Approval levels** — single approver, multi-step, or parallel. - **Delegation** — when an approver is out of office. Approval workflow is configured in the journal name; per-instance overrides are not allowed. ## Posting restrictions Various controls limit who can post what: - **User group on journal name** — only certain user groups can use the journal. - **Posting layer** — Current, Operations, Tax — restricts which layer the journal posts to. - **Single voucher number per posting** — prevents one journal from posting multiple vouchers (forces structural cleanliness). ## Recurring journals A common need: posting the same accrual or allocation every month. **Recurring journal lines** save the template; per period, create a journal from the template, adjust amounts, post. ## Reversing entries For accruals, the **reverse entry** flag posts a reversing journal in the next period automatically. Avoids manual reversal of the prior month's accrual. ## Approval audit trail Every approval action is logged: - Who submitted. - Who approved (or rejected). - Comments. - Timestamps. Auditors look for evidence of approval before posting; the audit trail is the evidence. **Common pitfalls.** - **Wrong journal name selected.** Different journal names have different defaults, dimensions, approval workflows; using the wrong one bypasses controls. - **Unbalanced voucher.** Posting fails; user gets a cryptic error; the cause is usually one line missing its offset. - **Dimension combinations invalid.** F&O's account structure rules can disallow certain account+dimension combinations; posting fails until corrected. - **Posted into closed period.** Auto-routing to next open period or rejection per setup. - **Posted to wrong posting layer.** Tax adjustments to Current layer rather than Tax; reporting mismatches. ## Posted vs draft A journal exists in three states: - **Open** — being edited. - **Posted** — committed; voucher numbers are now permanent. - **Rejected / not approved** — workflow returned for changes. Once posted, a journal can't be edited; corrections require a reversing journal. ## Operational rhythm Daily journals for routine activity (cash transfers, accruals); monthly journals for period-end adjustments; quarterly journals for tax reconciliations. A well-designed journal name taxonomy makes this rhythm sustainable; ad-hoc journal posting in a single "General" journal name makes audit trails painful. --- # IFRS 16 lease accounting in Dynamics 365 Finance How F&O handles IFRS 16 / ASC 842 lease accounting — right-of-use assets, lease liabilities, amortisation, and the integration with general ledger. Source: https://www.solvingdynamics365.com/guides/ifrs-16-lease-accounting-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 **IFRS 16** (and its US equivalent **ASC 842**) fundamentally changed lease accounting — operating leases that previously stayed off the balance sheet must now be capitalised as **right-of-use (ROU) assets** with corresponding **lease liabilities**. Dynamics 365 Finance includes lease accounting capability natively, replacing the spreadsheet-based lease management many companies relied on pre-2019. ## The accounting change Pre-IFRS 16, operating leases were P&L-only — monthly rent expense, no balance-sheet presence. Post-IFRS 16, every lease (above de minimis thresholds for short-term and low-value items) creates: - A **right-of-use asset** on the balance sheet — the value of the lessee's right to use the asset over the lease term. - A **lease liability** on the balance sheet — the present value of future lease payments. - **Depreciation expense** on the ROU asset over the lease term. - **Interest expense** on the lease liability (unwinding the discount). The split between depreciation and interest produces a front-loaded P&L expense pattern, different from the straight-line rent expense pattern of operating leases. ## F&O's lease module The **Asset leasing** module (part of Finance) handles the full lifecycle: - **Lease record** — captures the lease contract: lessee entity, asset description, start / end dates, payment schedule, discount rate, lease term, renewal / termination options, residual value if any. - **Initial recognition** — computes the present value of future payments, books the ROU asset and lease liability. - **Periodic accounting** — generates monthly depreciation and interest entries automatically. - **Payment posting** — when actual lease payments are made, F&O reduces the liability and posts the cash outflow. - **Modifications** — when the lease changes (extension, scope change, renegotiation), the module remeasures the liability and ROU asset. - **Termination** — when the lease ends or is terminated early, the remaining ROU asset and liability are reversed. **Configuration.** - **Discount rates** — the rate used to compute present value. Typically the incremental borrowing rate; configurable per lease or per company. - **Lease classification** — IFRS 16 broadly treats all leases as finance leases for lessees (no operating-lease distinction); ASC 842 retains the operating vs finance distinction. F&O supports both. - **Index-linked leases** — common in commercial property leases where rent escalates with CPI. F&O can handle indexation as remeasurements at each index date. - **Variable payments** — non-fixed payments (turnover-based rent, usage-based) are typically expensed as incurred rather than capitalised; configurable. - **Short-term and low-value exemptions** — IFRS 16 allows expensing short-term leases (under 12 months) and low-value leases without capitalisation. F&O honours the exemptions per configured policy. ## Disclosures and reporting Standard reports cover: - ROU asset register with current value, accumulated depreciation, useful life. - Lease liability schedule with current and non-current splits, future cash flows by year. - Lease expense breakdown — depreciation, interest, variable payments, short-term lease expense. - Maturity analysis — cash payments by year for the next several years. - Reconciliation of opening to closing balances. These map directly to IFRS 16 disclosure requirements in the financial statements. ## Multi-currency and indexation Cross-border leases (e.g. UK company leasing a German office in EUR) require: - Initial recognition at the contract-date FX rate. - Monthly re-measurement of the liability at period-end rate. - FX gain/loss recognised in P&L. Index-linked rent escalations are remeasurements at each indexation event, with the cumulative adjustment booked. ## Audit trail Every lease modification, remeasurement, and posting generates audit records. The lease module is one of the more audit-intensive areas of F&O for IFRS-reporting customers. **Common pitfalls.** - **Wrong discount rate** — the rate is one of the most consequential parameters; getting it wrong materially affects every lease's present value. - **Missing index-linked clauses** — leases with escalation that aren't configured for indexation under-state long-term liability. - **Modifications not posted timely** — lease changes that aren't reflected promptly produce wrong balance-sheet positions. - **Service components mixed with lease components** — IFRS 16 only requires capitalisation of the *lease* component; bundled service fees may not. The module supports separation; configure carefully. ## Operational reality Lease accounting is finance-team work, not operations. Engage the controller / financial reporting lead during setup; align with audit firm on configuration choices; document the policy. Done well, lease accounting is one of the smoother IFRS-compliance areas; done badly, it's an annual audit finding. --- # Intercompany trade in Dynamics 365 Finance & Operations How F&O models cross-legal-entity transactions — intercompany chains, mirrored sales/purchase orders, intercompany pricing. Source: https://www.solvingdynamics365.com/guides/intercompany-trade-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 A group with multiple legal entities (one per country, one per business unit, or one per regulatory regime) often has goods, services, or financial flows moving between entities. **Intercompany trade** in F&O models these flows as paired transactions in two legal entities, with automation that keeps them in sync, and with intercompany elimination support for consolidation. ## The basic pattern Entity A sells to Entity B. F&O can model this as: - A **sales order** in Entity A (the seller). - A **purchase order** in Entity B (the buyer). - Both orders linked; updates flow between them. Without F&O intercompany automation, each entity would have to manually create its side; with automation, creating one creates the other. **Setup.** 1. **Intercompany customer / vendor relationships** — Entity A holds Entity B as a customer (and vice versa, B holds A as a vendor). 2. **Intercompany trading partner** records define each direction's defaults: cost mark-up, allowed document types, currency. 3. **Item mappings** — sometimes the same product has different item numbers in different entities; mapping reconciles them. 4. **Default sites and warehouses** — where intercompany orders ship from and to. ## Intercompany sales/purchase order pairing When a purchase order is created in Entity B with vendor = Entity A's intercompany vendor: 1. The purchase order is created in Entity B. 2. A linked sales order is automatically generated in Entity A. 3. Confirmation, picking, and shipping in Entity A trigger receipt updates in Entity B. 4. Invoice in Entity A creates a purchase invoice in Entity B automatically. This bidirectional sync is the headline efficiency: cross-entity orders become near-zero rekeying. ## Intercompany pricing Transfer pricing rules (the regulatory-driven question of "at what price do related entities transact") are configured per partner pair: - **Cost plus** — markup on cost. - **Resale minus** — discount on customer-facing price. - **Fixed price** — negotiated price. For tax compliance, transfer pricing must be defensible against regulatory standards (OECD guidelines, BEPS). F&O captures the price; the policy and documentation are the tax team's responsibility. ## Direct delivery A pattern where the goods physically ship from Entity A directly to Entity B's customer, but financially flow through Entity B. F&O handles this as: 1. End customer order in Entity B (sales order). 2. Intercompany sales order in Entity B pulls from Entity A. 3. Entity A's direct delivery ships goods straight to the end customer; the paperwork shows the chain. Direct delivery saves shipping cost and time while keeping the legal entity flows correct. ## Intercompany inventory transfers For goods moved between entities without a sale (rebalancing stock): - A **transfer order** between sites within one entity is the simplest case. - A **cross-entity transfer** is modeled as a sales order in the source and a purchase order in the destination, at zero margin or cost-only. ## Intercompany services Entity A provides shared services (IT, finance) to Entity B. Modeled as service items (non-stocked) on intercompany sales/purchase orders, billed periodically. Pricing follows the transfer pricing policy. ## Intercompany journals For financial-only movements (recharges, allocations, loans), the **intercompany journal** posts to both entities simultaneously — a single posting creates G/L entries in two ledgers with matching offsets. ## Intercompany AR/AP reconciliation Periodic reconciliation ensures that Entity A's AR balance with Entity B equals Entity B's AP balance with Entity A: - Trial balance per intercompany pair, by currency. - Reconciliation differences identified and resolved. - Reconciliation report fed to consolidation as starting evidence. Without reconciliation, consolidation elimination journals miss amounts and consolidated financials carry residual intercompany balances. ## Intercompany chains A multi-step chain (Entity A → Entity B → Entity C) is supported but adds complexity. Each link is a paired transaction; the chain is constructed by linking orders explicitly. ## Tax and customs Cross-border intercompany trade triggers: - **VAT/customs** at the border. - **Withholding taxes** on services and royalties. - **Transfer pricing documentation** for tax authorities. F&O's tax engine handles VAT/customs; transfer pricing documentation is typically managed in dedicated tax tools. ## Consolidation flow Intercompany transactions flow into consolidated reporting: - Each entity's GL is consolidated normally. - **Elimination journals** in the consolidation company reverse intercompany sales/COGS and intercompany AR/AP. - Reconciled intercompany balances net to zero in eliminations; un-reconciled balances flag the gap. **Common pitfalls.** - **Inconsistent item codes.** Same product, different numbers; mapping missing; intercompany orders fail. - **Trade agreement gaps.** Intercompany prices not set; defaults to zero or to external customer pricing; transfer pricing wrong. - **Reconciliation skipped.** Differences accumulate; year-end consolidation has gaps. - **No process for intercompany returns.** Returns paths exist but rarely tested; first real return causes confusion. - **Document type proliferation.** Some teams create custom intercompany documents to add fields; complicates upgrades. ## Operational rhythm Daily order syncing is automatic. Monthly intercompany reconciliation is a finance team task — one per pair, formalised and signed off. Quarterly transfer pricing review is a tax/finance joint task. Year-end consolidation pulls all of this together. --- # Intrastat reporting in Dynamics 365 Finance How F&O handles EU Intrastat reporting — the statistical declaration of intra-community trade, configuration, exception handling, and country variations. Source: https://www.solvingdynamics365.com/guides/intrastat-reporting-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 **Intrastat** is the EU's statistical reporting system for intra-community trade — every EU business above a threshold must declare its arrivals (purchases from other EU countries) and dispatches (sales to other EU countries) periodically, by commodity code, country, weight, value, and transport mode. Dynamics 365 Finance handles Intrastat natively for EU country localisations, with configurable thresholds, exception handling, and direct submission to tax authorities. ## The model Each intra-community transaction (a sale to a customer in another EU country, a purchase from a vendor in another EU country) automatically generates **Intrastat data** at posting time: - **Commodity code** — the EU Combined Nomenclature code identifying the goods. - **Country of origin** — where the goods were made (different from where they're shipped from). - **Country of destination / dispatch** — where they're going / coming from. - **Statistical value** — typically the invoice value adjusted for transport cost. - **Net weight** — the goods' weight in kilograms. - **Quantity in supplementary unit** — for commodities measured beyond weight (pieces, litres, m², etc.). - **Transport mode** — sea, rail, road, air, post, fixed installation, inland waterway, own propulsion. - **Transaction nature** — the type of transaction (sale, return, free movement, processing, etc.). - **Statistical procedure** — country-specific codes for special cases. ## Setup Configuring Intrastat involves: - **Item commodity codes** — every product traded intra-EU needs a code. Maintained on the product card; auto-applies to transactions. - **Country of origin** per item — for goods imported then resold, the origin is the original manufacturing country, not the seller's country. - **Vendor / customer country** — for partner classification. - **Transport modes** per shipping method. - **Transaction nature codes** mapped to sales/purchase types. - **Statistical value adjustments** — typical formula adding transport and incidental costs to invoice value. ## The periodic declaration Intrastat is submitted monthly (in most EU countries; some allow quarterly for small filers). F&O's **Intrastat journal** routine: 1. Collects all intra-EU transactions posted in the period. 2. Aggregates per commodity code, country, transaction nature. 3. Allows exception handling — manual additions, exclusions, corrections. 4. Generates the country-specific submission file or report. The output format varies by country — XML for some, CSV for others, paper for the smallest jurisdictions. **Electronic Reporting (Globalization Studio)** handles country-specific formats. **Country variations.** - **Threshold differences** — each country sets its own value threshold below which Intrastat isn't required. Below threshold means no declaration; above means full reporting. - **Two-way vs one-way thresholds** — some countries have different arrival vs dispatch thresholds. - **Special procedures** — some countries require additional codes (delivery terms, port of entry, customs procedure). - **Submission portal** — each country has its own submission system (HMRC in UK pre-Brexit, INSEE / DGDDI in France, ISTAT in Italy, Statistics Sweden, etc.). ## Brexit complication The UK exited Intrastat for outbound dispatches at end of 2021; arrivals continued for a transition period. UK businesses now use a different mechanism for trade with the EU. Northern Ireland has its own arrangements under the Northern Ireland Protocol. **Exception handling.** - **Triangulation** — A in Country 1 invoices B in Country 2 for goods shipped directly from C in Country 3 to B. Requires specific Intrastat coding. - **Free movements** — goods moved between own subsidiaries without sale; reported under specific transaction codes. - **Returns** — return shipments coded as such. - **Sample / promotional goods** — typically excluded from thresholds. - **Lease and rental** — special treatment. ## Reconciliation Intrastat values shouldn't dramatically diverge from VAT return values — Intrastat dispatches relate to zero-rated EU sales; arrivals relate to reverse-charge purchases. Comparison reports flag mismatches for investigation before submission. ## Penalties Late or wrong Intrastat submissions trigger country-specific penalties — typically minor financial penalties initially, escalating with repeated failure. The compliance bar is meaningful. **Common pitfalls.** - **Missing commodity codes on items** — transactions can't be classified and miss the report. - **Wrong country of origin** — most common mistake for goods resold across borders. - **Forgetting threshold monitoring** — businesses that grow past the threshold miss the registration moment. ## Operational reality Intrastat reporting is a monthly ritual; configure cleanly during implementation; automate the routine; review exceptions before submission. --- # Inventory classification and ABC analysis in F&O How F&O classifies inventory by value, volume, and margin — the ABC analysis routine, classification codes. Source: https://www.solvingdynamics365.com/guides/inventory-classification-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 A warehouse with 20,000 SKUs cannot manage every item the same way. Inventory classification — typically **ABC analysis** by value, volume, and margin — is the structural foundation for applying differentiated policies: tight control on high-value items, loose policies on low-value, and varied review cadences in between. F&O has the analysis routines and the classification fields; the work is in using them. ## The Pareto principle A familiar pattern: ~20% of items typically generate ~80% of revenue or inventory value. Inventory classification operationalises this: - **A items** — high value or high movement; the 20% that matters most. - **B items** — moderate value or movement; the next 30%. - **C items** — low value, low movement; the remaining 50%+. Three dimensions usually matter: - **By value** — inventory carrying value ranking. - **By volume** — consumption volume ranking. - **By margin** — profit contribution ranking. An item can be A by value but C by volume (high-value low-velocity) — different management implications than an A by both (high-value high-velocity). ## The ABC analysis routine F&O's inventory analysis function: 1. Reads transactional data over a configurable period. 2. Ranks items by the chosen criterion (value, volume, margin). 3. Cumulative percentage calculated. 4. Cutoff points assign A/B/C classification. Typical cutoffs: A = top 80% cumulative, B = next 15%, C = bottom 5% — but configure per company strategy. ## Classification fields on the item Each item carries: - **ABC Value** — A/B/C classification by value. - **ABC Margin** — by margin contribution. - **ABC Carrying Cost** — by carrying cost. - **ABC Revenue** — by revenue. These fields are updated by the ABC analysis batch. They become filters in queries, planning policies, and reports. **Using classification to differentiate policy.** - **A items** — Min/Max coverage with low safety stock buffer; planner attention; weekly cycle count; tight inspection. - **B items** — Period coverage; monthly cycle count; sample-based inspection. - **C items** — Two-bin kanban or visual reorder; quarterly cycle count; minimal inspection. The policy differentiation translates "we have 20,000 SKUs" into "we actively manage 200 items and rule-based the rest." ## XYZ analysis A complementary classification: - **X items** — predictable, low demand variability. - **Y items** — moderately variable. - **Z items** — highly variable, unpredictable. Combined: ABC by value × XYZ by variability = 9 classes with different policies. AX (high value, predictable) → tight Min/Max with low safety stock; CZ (low value, unpredictable) → buffer stock high, automated reorder. F&O doesn't have native XYZ but the calculation can be done in Power BI or a custom field. ## Cycle counting frequency Classification drives cycle count cadence: - **A items counted monthly.** - **B items counted quarterly.** - **C items counted annually.** The total counting work is concentrated where it matters most. The cycle count planner field on the item drives the counting calendar. ## Inspection frequency Quality association rules can reference ABC classification — A items get 100% inspection from new vendors, C items get sample inspection. ## Reorder review cadence A planner reviewing thousands of items can't go deep on each one. Classification tells them where to focus: - **A items** — weekly individual review. - **B items** — exception-based review when action messages fire. - **C items** — rule-based replenishment, monthly summary review only. ## Reclassification Items move between classes as demand patterns shift. The ABC analysis should re-run periodically: - **Quarterly** for stable businesses. - **Monthly** in fast-moving markets. - **After major product launches or discontinuations** — affected items need immediate reclassification. Without reclassification, classifications become stale and the differentiated policies misallocate attention. **Combining with other taxonomies.** - **Product group** — what kind of item. - **Item group** — accounting/posting groupings. - **Coverage group** — planning parameters. - **ABC class** — value/volume classification. These are orthogonal axes. An item belongs to a product group and a coverage group AND has an ABC class. Reporting and policy can slice along any axis or combination. **Common pitfalls.** - **One-off classification.** Run at go-live, never refreshed; classifications drift from reality. - **Classification not linked to policy.** Items are classified but treated identically; the analysis is decorative. - **One-dimensional view.** Only classifying by value misses high-volume, low-value SKUs that drive operational cost. - **Boundary items flipping.** Items near the A/B threshold move between classifications every quarter; policy oscillates. Mitigation: hysteresis (require a confirmed shift over 2+ periods to reclassify). - **C items ignored.** "It's just C" becomes an excuse for poor management; in aggregate, C items can still represent significant carrying cost. ## The strategic value Inventory classification is a free analytical tool that costs almost nothing to run and yields material improvements in working capital, service level, and operational efficiency when policies are genuinely differentiated. The biggest miss is treating it as a reporting exercise rather than as the foundation of operational discipline. --- # Inventory dimensions in Dynamics 365 Supply Chain How inventory dimensions structure item identity in F&O — storage, tracking, product dimensions, and the consequence of dimension design. Source: https://www.solvingdynamics365.com/guides/inventory-dimensions-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 In Dynamics 365 Supply Chain Management, **[inventory dimensions](https://www.solvingdynamics365.com/glossary/inventory-dimension)** are the structural concept that gives each physical unit of inventory its specific identity. They go beyond a simple "item × quantity" model — an item plus storage dimensions plus tracking dimensions plus product dimensions uniquely identifies a piece of inventory. The choices made about which dimensions to use materially affect how the warehouse operates, how planning works, and how reporting tells stories. **Three dimension groups.** 1. **Product dimensions** — make one item different from another within the same "product master". Example: a T-shirt is a product master; variations by **Size**, **Colour**, **Configuration**, **Style** are product dimensions. Each combination of product dimensions is a distinct *item* for inventory purposes. Configuration and Style support engineer-to-order patterns where variants are generated from rules; Size and Colour support fashion/retail. 2. **Storage dimensions** — *where* the inventory is held. **Site**, **Warehouse**, **Location** (bin), **Inventory status**. Storage dimensions track physical placement; the same item-with-product-dimensions can exist at multiple storage locations simultaneously. 3. **Tracking dimensions** — properties that make individual units within a storage location distinguishable. **Batch number**, **Serial number**, **Owner** (consignment), **Licence plate**, **Inventory status**. ## Dimension activation Each dimension is configured per item to be **active** or not. An item with only Site + Warehouse storage dimensions has simple inventory; an item with Site + Warehouse + Location + Licence Plate + Batch + Serial has every unit precisely identified. Costing, planning, picking, and posting all respect the active dimensions. ## Dimension hierarchy Inventory drilldowns roll up across the dimension axes: ``` Item Master → Product Dimensions (Size = L, Colour = Blue) → Site (US) → Warehouse (WH-East) → Location (Aisle 5, Bin B-12) → Licence Plate (LP-12345) → Batch (B-2026-Q3-007) → Serial (S-987654) ``` Each level adds specificity. Reports can summarise to any level — "total inventory of L Blue T-shirts across all warehouses" vs "specific serial in specific bin". **Implications for transactions.** - **Picking** — a pick instruction must identify enough dimensions to locate the inventory unambiguously. For high-precision items (serial-tracked), the picker scans the serial; for bulk items, just the location. - **Reservation** — reservations bind at the active-dimension level. Reserve "this serial for this customer" vs "5 units of this item, any serial". - **Costing** — cost is tracked at the activated dimension granularity. FIFO across serials gives per-serial cost; FIFO at item-level gives aggregate cost. - **Planning** — MRP works at the planning dimension granularity. Different sites can have different plans; different colours can have different demand. ## Inventory status A specific dimension worth highlighting. **Inventory status** is a dimension flag like *Available*, *Quarantine*, *Reserved-Damaged*, *Pending-QC*. Status drives whether inventory is available for picking; quarantined batches don't ship. Configured per item, activated for tracking dimension. ## Costing dimension setup Beyond *active* / *inactive*, dimensions can be flagged as **costing dimensions** — included in cost-layer matching. The standard pattern: Site is costed (different cost per region); Warehouse is not (same item costs the same across warehouses in a region). Configuring costing dimensions wrong produces strange cost behaviour at posting. ## The trade-off More dimensions = more precision but more operational overhead. Activating Serial on every item means scanning every unit at every transaction; activating it only on high-value or regulatory-required items keeps operations efficient. Most implementations: - Site, Warehouse, Location active on every item. - Batch active on food, pharma, chemicals, regulated industries. - Serial active on high-value or compliance-regulated items (equipment, electronics). - Licence plate active in advanced WMS scenarios. ## Operational reality Design dimensions per item category, not uniformly across the catalogue. The warehouse-floor people know what they need to track; the design should match their reality. --- # Inventory replenishment policies in Dynamics 365 SCM How replenishment policies work in F&O — min/max, period order quantity, fixed quantity. Source: https://www.solvingdynamics365.com/guides/inventory-replenishment-policies-in-scm Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 Inventory replenishment is the day-to-day question of *when to order how much*. Dynamics 365 SCM answers it through **coverage groups** — named policy bundles linked to items (and optionally per warehouse) that drive the master planning or Planning Optimization engine. Choosing the right coverage group per item category is the foundational supply chain decision. ## Coverage codes A coverage group specifies one of: - **Period** — group demand into periods of N days; create one planned order per period covering that period's net demand. - **Requirement** — create a planned order per demand transaction. Smallest order sizes but most order overhead. - **Min/Max** — maintain inventory between minimum (reorder point) and maximum levels. Planning replenishes to max when min is breached. - **Manual** — planning makes no suggestion; planner manages by exception. ## Period coverage Best for items with steady demand and reasonable lead time. Parameters: - **Coverage period** — e.g. 7 days. - **Negative days** — how far past the demand date the system can still consume from existing supply before suggesting more. - **Positive days** — how far future supply can satisfy current demand. A weekly period order means each Monday the system suggests one order covering the week's net demand. Reduces order count vs requirement-based. ## Requirement coverage Best for engineer-to-order, large-value, or low-volume items where pegging demand to supply matters more than order consolidation. Every demand creates its own supply suggestion. ## Min/Max coverage Best for fast-moving, low-value items where the cost of carrying safety stock is less than the cost of stockouts. Parameters: - **Minimum quantity** — reorder point. - **Maximum quantity** — order-up-to level. - **Minimum / Maximum keys** — reference to date-dependent profiles for seasonality (e.g. higher min during holiday). - **Multiple** — order quantity rounding (cases of 12). The engine watches on-hand + on-order; when projected balance dips below min, an order suggestion brings it back to max. **Coverage group fields beyond coverage code.** - **Safety stock** — extra buffer above the minimum. - **Reorder margin** — additional days of lead time buffer. - **Lead time** — purchase or production lead time used in plan calculation. - **Calendar** — working calendar to compute delivery dates. - **Time fence** — how many days into the future planning produces suggestions. - **Action message time fence** — when planning produces "expedite" or "delay" messages on existing supply. - **Forecast plan** — which forecast plan the item consumes from. ## Item coverage At the item level, you can override the default coverage group per warehouse or even per dimension combination. A SKU might be Min/Max in the central DC and Requirement in regional DCs. ## Allocation keys When forecast is at family level but planning is at SKU level, **allocation keys** distribute the family forecast to SKU forecast based on historical percentages. Coverage group dictates how the SKU forecast then drives replenishment. ## ABC analysis and coverage choice A common heuristic: - **A items (top 20% by value)** — Min/Max or Period with tight parameters; high attention. - **B items** — Period; moderate parameters. - **C items** — Min/Max or kanban with loose parameters; minimal attention. Periodically re-classify; items move between categories as demand patterns shift. ## Planning Optimization vs classic master planning Coverage group parameters apply to both. Planning Optimization (the modern in-memory engine) processes them faster and supports incremental runs; classic master planning batch-processes the full plan. Both yield similar suggestions; the engine choice is a performance and architecture decision. **Common pitfalls.** - **One coverage group for everything.** Coverage groups should be a thoughtful taxonomy (3–10 named groups), not a one-size-fits-all. - **Lead times wrong.** The single biggest cause of bad suggestions. Audit lead times annually; reality drifts from the system. - **Min/Max levels never adjusted.** A reorder point set at go-live and never reviewed becomes wrong as volumes change. Build a quarterly review. - **Safety stock everywhere.** Stacking safety stock on top of period coverage and lead time buffers inflates inventory without clear benefit. - **Time fences misunderstood.** A short time fence creates churn (suggestions every day); too long misses real-time changes. Tune per item category. ## The art beyond the parameters Replenishment policy choice is half the story; the other half is the planner's discipline to act on the system's messages (expedite, delay, postpone). A coverage group that produces good suggestions only matters if someone executes them on time. --- # Legal entity setup in Dynamics 365 Finance How to configure legal entities in F&O — corporate identity, country localisation, GL setup, posting profiles, dimension structure. Source: https://www.solvingdynamics365.com/guides/legal-entity-setup-in-f-and-o Section: Finance & SCM / Finance Published: 2026-06-24 A **legal entity** in Dynamics 365 Finance is the unit of statutory accounting — one set of statutory books, one tax ID, one consolidated set of financial statements. Configuring a new legal entity is a substantial implementation task; understanding the layers of setup is essential to getting it right. **Identity and incorporation.** - **Name** — the formal legal name as registered. - **Legal entity ID** — a short code used throughout F&O. - **Address** — the registered office. - **Country** — drives statutory regulations and the country localisation. - **Tax registration numbers** — VAT, EIN, country-specific tax IDs. - **Currency** — the entity's primary statutory currency. - **Reporting currency** — optional secondary currency for group-level reporting (see the parallel currencies guide). ## Country localisation Each legal entity belongs to a country whose localisation drives much of the configuration: - **Tax engine setup** — VAT codes, sales tax codes, withholding tax codes per country regulations. - **Statutory reports** — VAT returns, intrastat, SAF-T, country-specific filings. - **Electronic reporting (Globalization Studio) configurations** — for e-invoicing, payment files, tax submissions per country format. - **Document layouts** — invoice templates conforming to country statutory format. - **Number sequences** — some countries require continuous, gap-free sequences for invoices. Microsoft ships localisations for ~20 countries; partner localisations cover most others. ## Chart of accounts Each entity references a **chart of accounts**: - **Shared across entities** — common in multi-entity groups where consolidation matters. The shared CoA simplifies eliminations and reporting. - **Per-entity CoA** — when entities have substantially different account structures (different industries, different countries with different statutory account standards). In F&O, the CoA is independent of the entity; one CoA can serve many entities. Choose the model deliberately at implementation. ## Account structures and posting profiles Beyond the CoA, the **account structure** defines required dimensions per posting (see the financial dimensions guide). And **posting profiles** map sub-ledger transactions to GL accounts: - **Customer posting profile** — how AR settlements hit the GL. - **Vendor posting profile** — how AP settlements hit the GL. - **Inventory posting profile** — how inventory movements hit the GL. - **Fixed asset posting profile** — how depreciation, acquisition, and disposal hit the GL. - **Project posting profile** — how project costs and revenue hit the GL. Each profile is configured per legal entity per scenario; designing them takes substantial implementation time. ## Dimension structure Each entity references a dimension structure — Department, Cost Centre, Project, Region, etc. Multi-entity tenants commonly share dimensions for consistent reporting but can vary per entity where structures differ. ## Bank accounts Each entity has its own bank accounts: - Operating accounts. - Payroll accounts. - Escrow / trust accounts. - Tax-remittance accounts. - Intercompany accounts. Bank account configuration includes the bank's name, account number, IBAN, payment file formats, statement formats. ## Vendor and customer master data Each entity has its own: - Customer master — though many customers can be shared across entities through **shared services** or **master data management** patterns. - Vendor master — same; shared common vendors with per-entity payment terms and bank details. ## Employees and workforce Workers can be associated with one or more entities — common when staff perform work across entities. Time sheets and expenses can post to projects in different entities. ## Intercompany For multi-entity operations: - **Intercompany counterparties** — defined per legal entity pair, specifying GL accounts for IC postings. - **Intercompany sales / purchases** — automatically generate counter-documents in the partner entity. - **Centralised payments** — one entity can pay vendor invoices for another entity, with IC accounting reconciling. ## Consolidation Multi-entity groups consolidate into a **consolidation company** — a special entity that aggregates subsidiary results into group financial statements: - Each subsidiary uploads its trial balance to the consolidation entity. - Currency translation applies (different entities may have different statutory currencies). - Eliminations remove intercompany transactions. - Adjustments apply for group-specific accounting policies. **Implementation sequence.** 1. Establish the country localisation foundations. 2. Configure CoA, dimensions, account structures. 3. Configure posting profiles for all relevant sub-ledgers. 4. Set up bank accounts, vendors, customers (typically through migration). 5. Configure tax (VAT, sales tax, withholding) per country requirements. 6. Configure financial reporting and statements per local statutory format. 7. Configure intercompany if multi-entity. 8. Validate through cycle 1 of mock posting before go-live. **Common pitfalls.** - **Underestimating localisation setup time** — each new country can be weeks of work. - **Inconsistent CoA across entities** — consolidation breaks; manual reconciliation perpetually. - **Wrong posting profiles** — every transaction posts to the wrong account; year-end reveals the damage. - **Missing tax setup** — invoices post with wrong VAT; statutory filings inaccurate; penalties accumulate. ## Operational reality Setting up a new legal entity is a 2–6 week implementation effort for a country with a strong localisation; 2–4 months for countries with partial coverage; longer for greenfield localisations. Plan accordingly when expanding internationally. --- # Lifecycle Services (LCS) explained What LCS does for Dynamics 365 Finance and Supply Chain projects — workspaces, environments, deployable packages, BPM, and support. Source: https://www.solvingdynamics365.com/guides/dynamics-365-lifecycle-services-explained Section: Finance & SCM / Overview & platform Published: 2026-05-01 Updated: 2026-08-31 **Lifecycle Services (LCS)** is the operational portal for Dynamics 365 Finance and Supply Chain Management implementations. If Microsoft 365 admin centre manages users, LCS manages the application lifecycle: environments, code, updates, and support. Anyone working on a Finance/SCM project will live in LCS daily. ## Projects Everything in LCS belongs to a **project workspace** — a logical container for a single implementation or operations engagement. A project has a *type* (Implementation, Migrate, etc.), an Azure subscription mapped to it for environment hosting (for sandboxes that need it), an LCS partner, and roles assigned to users (Project owner, Environment manager, Developer, etc.). ## Environments From the project, environments are requested, provisioned, started, stopped, deallocated, and decommissioned. Each environment has a lifecycle screen showing its state, the platform and application versions running, and a history of changes. ## Deployable packages Custom code and binary content move into environments as **deployable packages** built from a developer's Visual Studio. The developer uploads the package to the LCS **asset library**, then an authorised user applies it to an environment. There is no direct deploy from VS to production. ## Updates Microsoft's platform and application updates flow through LCS as packages. Customers can preview, schedule, and apply them per environment. LCS shows which environments are on which version. ## Business Process Modeller (BPM) The [Business Process Modeller](https://www.solvingdynamics365.com/glossary/business-process-modeller) is a library of standard business processes (procure-to-pay, order-to-cash) maintained as flow diagrams in LCS. Customers walk through the standard process, mark fit vs gap, and link to BPM tasks recorded with the **Task Recorder** — which captures user actions in the application as reusable scripts for training and testing. Those recordings matter beyond documentation: they are the input format for **RSAT** (Regression Suite Automation Tool), which replays them as automated regression tests against sandbox environments — the standard way F&O customers survive the mandatory update cadence without manually retesting everything twice a year. ## Issue search A searchable knowledge base of known issues, hotfixes, and platform releases, with the ability to file support tickets that route to Microsoft. ## Asset library Beyond deployable packages, the asset library stores GER configurations, data packages, BPM exports, and other artefacts shared across the project team. ## Working in LCS without hurting yourself A few practices separate calm F&O projects from ones that fight their tooling: - **Treat LCS roles as production access.** An Environment manager can refresh a sandbox from production or apply a package; that's the power to destroy a test cycle or leak production data into a loosely-controlled environment. Assign roles per person, prune leavers, and keep the partner's access reviewed like any other privileged account. - **Name and version asset-library uploads.** The asset library accumulates dozens of deployable packages with names like `Final_v2_new`. Adopt a convention (build number, date, branch) on day one — during a production incident, "which package is actually running" must be answerable in seconds. - **Schedule updates, don't absorb them.** Microsoft's [One Version cadence](https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates) means updates arrive whether you plan or not. Use the update settings to pin a predictable window, run the update through a sandbox with RSAT first, and keep one environment a version ahead for early warning. - **File support tickets through LCS with the diagnostics attached.** Tickets raised through the project workspace carry environment context Microsoft can act on; tickets raised cold start with a week of "please provide your environment ID". ## The transition to the Power Platform admin center Microsoft is retiring LCS for customer projects in stages and moving its functions into the **Power Platform admin center** (PPAC), aligning F&O with Dataverse and the rest of the Dynamics 365 estate. New F&O environments are increasingly provisioned and managed as *unified* environments in PPAC — same portal as Dataverse environments, same admin model — and capabilities like environment operations, update management, and history have been landing there wave by wave, while some classic LCS features (BPM among them) are being deprecated outright rather than ported. Practically: if you run an existing implementation, expect a hybrid period where you touch both portals, and follow Microsoft's migration guidance per feature rather than assuming a flag-day switch. If you're starting a new project, learn the PPAC-first model and treat LCS knowledge as transitional. The environment-planning side of this — what topology to run and where each piece is managed — is covered in [Finance environments and LCS](https://www.solvingdynamics365.com/guides/dynamics-365-finance-environments-and-lcs). --- # Machine learning forecasting in Dynamics 365 Supply Chain How the demand forecasting service in D365 SCM uses Azure ML — historical demand, parameter tuning. Source: https://www.solvingdynamics365.com/guides/machine-learning-forecasting-for-d365-supply-chain Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 Demand forecasting in Dynamics 365 Supply Chain Management runs as an Azure Machine Learning service that consumes historical demand data and produces statistical forecasts at item, item-warehouse, item-customer, or item-allocation-key granularity. Done right, it replaces manual planner spreadsheets with a baseline forecast that planners adjust rather than generate. Done badly, it produces numbers nobody trusts and gets switched off in month two. ## Architecture The flow is one-way push, batch: 1. F&O exports demand history (sales orders, transfer demand, configurable filters) to Azure storage. 2. Azure ML reads the data and runs the configured algorithm. 3. The forecast result is imported back into F&O as a baseline demand forecast. 4. Planners review, accept, or override forecasts in F&O. The Azure ML side is operated by Microsoft as part of the SCM service — customers don't manage the model, but they configure parameters that affect the algorithm choice. **Algorithms available.** - **ARIMA** — autoregressive integrated moving average; strong for stable demand with trends. - **ETS** — exponential smoothing; strong for seasonality. - **STL Decomposition** — separates trend/seasonality/residual; good visibility for planner trust. - **Forecasting Tree** — non-parametric tree model for complex patterns. The service runs all algorithms and picks the best by error metric (typically MAPE or RMSE) per item-location combination. Customers can override. **Parameters that matter.** - **Forecast horizon** — how many periods ahead. - **Forecast frequency** — daily, weekly, monthly buckets. - **Historical horizon** — how much history to consider. - **Confidence threshold** — minimum confidence required to use the forecast; below that, fall back to a heuristic or planner manual. - **Missing value substitution** — zero-fill, average-fill, interpolation. - **Outlier removal** — Z-score threshold for outlier elimination. Outlier handling is the most under-considered parameter. A pandemic-driven spike, a one-off bulk order, or a stockout disrupting normal demand all corrupt the history; outlier removal cleans them up before the algorithm sees them. ## Granularity Forecasts can be at: - **Item only.** - **Item + Site.** - **Item + Site + Warehouse.** - **Item + Site + Allocation Key** — for downstream allocation across DCs. Finer granularity = more accuracy potential but more data sparsity per series. Items with low volume at a granular level produce noisy forecasts; aggregate higher. ## The planner override pattern F&O presents forecasts in the **Demand Forecasting Workspace**. Planners can: - Accept the ML number as-is. - Multiply by a percentage (sales sees a 10% promotional lift coming). - Hard-override a specific period (a known one-time order). - Replace with a manual forecast entirely. Best practice: ML produces the baseline, planners add the intelligence ML doesn't have. The override audit trail records who changed what and why. ## Forecast accuracy Standard KPIs: - **MAPE** — mean absolute percent error. - **Bias** — systematic over- or under-forecast. - **WAPE** — weighted absolute percent error (weighted by volume so big items count more). Track accuracy by item, by category, by planner-overridden vs ML-baseline. The accuracy report is the credibility tool — without it, planners revert to spreadsheets. ## Integration with master planning Once the forecast is accepted, it flows into the demand side of **master planning** (or Planning Optimization). Master planning consumes forecasts plus sales orders, runs supply suggestions (purchase, transfer, production), and creates planned orders. Forecasts beyond the firmed horizon drive long-lead procurement; sales orders inside the firmed horizon drive short-term operations. ## Forecast consumption When a real sales order lands in a forecast period, the forecast is **consumed** by the sales order — net demand becomes max(forecast, actual). Configurable consumption rules govern this; tuning matters in fast-cycling businesses to prevent double-counting demand. **Common pitfalls.** - **Garbage historical data.** Returns, cancellations, and inter-company transfers polluting the sales history → wrong forecast. Clean the input. - **Granularity mismatch.** Item-level forecast at the SKU but planning at the family level; reconcile. - **One-time events not flagged.** A massive promotional event one year ago that won't recur is treated as a normal high-demand pattern; outlier removal must catch it. - **No accuracy tracking.** Without it, planners stop trusting the system; ML becomes shelfware. - **Algorithm choice locked in.** Different item categories need different algorithms; let the service pick per-series. ## Operational reality ML forecasting is a tool, not a replacement for planning judgement. The teams that get value from it use it as the conversation starter, not the answer. --- # Master Data Services vs Dual-Write for Dynamics 365 How Master Data Services and Dual-Write differ as integration patterns between F&O and Dataverse — strengths, weaknesses, and the architectural choices. Source: https://www.solvingdynamics365.com/guides/master-data-services-vs-dual-write Section: Finance & SCM / Overview & platform Published: 2026-05-01 Connecting Dynamics 365 Finance and Operations (back-office ERP) with Dataverse-based Customer Engagement apps (CRM, Customer Service, Field Service) is a frequent architectural requirement. Two patterns dominate: **Dual-Write** (Microsoft's purpose-built bidirectional sync) and **Master Data Services / Master Data Integrator** (older patterns, mostly one-way). Knowing which to use when matters. **The integration problem.** - F&O has its own data — customers (in F&O's CustTable), items, etc. - Dataverse has Customer Engagement's data — Accounts, Contacts, Products. - Same business entity (a customer) lives in both. - Changes in one need to flow to the other. Without a sync mechanism, manual re-entry happens; data diverges; chaos ensues. ## Dual-Write Microsoft's purpose-built sync: - **Bidirectional** — changes flow both ways. - **Real-time** — within seconds. - **Built into F&O** — configurable; enabled per entity. - **Maps F&O entities to Dataverse entities** — Customer → Account, etc. - **Initial sync** — bulk one-time populating; ongoing changes incremental. - **Conflict resolution** — defined rules when both sides change. For organisations running F&O + Customer Engagement, Dual-Write is the canonical integration. **Dual-Write architecture.** - F&O writes change events to its internal queue. - Dual-Write service reads queue. - Translates F&O record to Dataverse representation per mapping. - Writes to Dataverse. - Mirror path for Dataverse → F&O. Each entity has a configurable map; standard maps shipped by Microsoft; customisable for extensions. **Dual-Write mapping configuration.** - **F&O entity** — source. - **Dataverse table** — target. - **Field mappings** — per-column. - **Filters** — only sync certain records. - **Direction** — one-way or two-way. - **Initial sync vs running sync** — separate configuration. Standard mappings cover common entities; custom entities need custom mappings. **Common Dual-Write entities.** - Customer / Account - Vendor / Account (with different role) - Released Product / Product - Sales Order - Quotation - Invoice (less commonly) - Contact - Address - Employee / Contact (with Worker role) The list expands per wave. ## Master Data Services (MDS) The older pattern: - Microsoft's enterprise master data management product (SQL Server-based). - Hub-and-spoke; MDS is the authoritative source. - F&O and Dataverse both subscribe to MDS. - Less integrated with Dynamics; manual configuration. Mostly legacy now; Dual-Write supersedes for Dynamics-specific scenarios. ## Master Data Integrator (older Dynamics-specific tool) Historical: - Pre-Dual-Write integration between F&O and Customer Engagement. - File-based, slower, batch-oriented. - Largely deprecated; Dual-Write is the replacement. **Dual-Write strengths.** - Real-time bidirectional. - Native to Dynamics; minimal external infrastructure. - Standard mappings for common entities. - Conflict resolution built in. - Microsoft-supported. **Dual-Write limitations.** - Bound to Dataverse-F&O pair; not for non-Dynamics destinations. - Mapping complexity for custom entities. - Performance issues at very high volumes (>10K changes per minute). - Initial sync of large data sets can take days. - Schema changes break mappings; coordination needed. **Alternative patterns.** - **Custom integration via Azure Service Bus** — for complex scenarios beyond Dual-Write's reach. - **ADF pipelines** — for batch sync rather than real-time. - **APIs direct** — F&O and Dataverse APIs called directly from custom code. Each has its place; Dual-Write should be the default for F&O↔Dataverse sync. ## Conflict resolution When both sides change a record simultaneously: - **Last write wins** — default. - **Source priority** — one side authoritative for specific fields. - **Manual review** — for conflicts, queue for human resolution. Configurable per entity / per field. ## Monitoring Operational health: - **Dual-Write admin pages** — sync status per entity. - **Failed syncs** — exception queue. - **Latency metrics** — how fast changes flow. Without monitoring, sync issues compound; data diverges silently. ## Schema evolution When entities change: - New field added in F&O → Dual-Write mapping needs update. - New field added in Dataverse → similar. - Field renamed → mapping breaks. Coordinate schema changes; test mappings; deploy together. **Common pitfalls.** - **No initial sync planning.** Skipping initial bulk; running data desynchronised. - **Mapping gaps.** Some fields not mapped; data divergence on un-mapped fields. - **Conflict resolution untuned.** Last-write-wins for every field; legitimate updates overwritten. - **No monitoring.** Failures accumulate; nobody notices until reconciliation reveals divergence. - **Heavy plug-ins on Dataverse side.** Dual-Write writes; plug-in fires; updates F&O; loop. - **Performance under load.** Heavy F&O batch creates lag in Dataverse view. ## Strategic positioning For organisations running both F&O and Customer Engagement on Dynamics 365, Dual-Write is the canonical integration pattern. Plan and execute it thoughtfully; the initial setup investment pays back continuously. For organisations with non-Dynamics destinations (Salesforce, ServiceNow), or with complex multi-system integrations, Dual-Write doesn't apply directly; custom patterns via Service Bus or Power Automate fill the gap. Master Data Services has its niche for enterprise MDM but is increasingly secondary to Dual-Write for Dynamics-specific needs. Choose based on the actual integration topology; don't force tools beyond their natural fit. ### Frequently asked questions **What is dual-write?** Microsoft's built-in, bidirectional, near-real-time synchronisation between Finance and Operations entities and Dataverse tables — Customer to Account, Released Product to Product, sales orders, quotations, contacts, addresses — with shipped maps, initial sync, and configurable conflict resolution. **Is Master Data Services still relevant?** Only for enterprise master data management beyond the Dynamics pair. For F&O-to-Dataverse sync it has been superseded by dual-write, and the older Master Data Integrator is largely deprecated. **What are dual-write's limits?** It only connects Dataverse and F&O, custom entities need custom maps, very high change volumes strain it, initial sync of large data sets can take days, and schema changes on either side break maps unless coordinated. **What causes dual-write to loop?** A heavy plug-in on the Dataverse side that fires on a dual-write write, updates the record, and sends the change back to F&O. Design plug-ins and flows on synced tables with dual-write in mind. **When should I not use dual-write?** When the destination is not Dynamics — Salesforce, ServiceNow, a data warehouse — or when integrations span many systems. Azure Service Bus, Data Factory pipelines, or direct API calls fill that gap. --- # Master planning groups in Dynamics 365 Supply Chain How master planning groups configure replenishment behaviour per item in F&O — coverage groups, item allocation keys, and the policies that shape MRP. Source: https://www.solvingdynamics365.com/guides/master-planning-groups-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 In Dynamics 365 Supply Chain Management's planning engine (whether the modern **Planning Optimization** or the legacy MRP), the behaviour of replenishment for any given item is determined by several groupings — **item coverage groups**, **item allocation keys**, **planning groups**, and policy-driving parameters. Understanding the layered configuration is essential to producing a planning system that doesn't fight your operations. ## Coverage groups (item coverage settings) The most consequential setting per item. A **coverage group** defines: - **Coverage code** — the replenishment policy: - **Period** — top up at end of each period. - **Requirement** — plan exactly to demand (true MTO). - **Min/Max** — top up when below minimum, to maximum. - **Manual** — no automated planning suggestions. - **Coverage time fence** — how far out the engine plans. 30 days, 90 days, etc. - **Lead times** — minimum production / purchase lead time the engine assumes. - **Safety stock** — buffer level the engine treats as unavailable. - **Safety margin** — extra time padding for receipts. - **Reorder quantity rules** — minimum order quantity, lot multiple, maximum order quantity. Each item is assigned to a coverage group; the group's settings drive how the engine plans for that item. ## Item coverage records For more nuanced control, **item coverage** records override the coverage group at the item-and-warehouse level. A item might have a default coverage group setting at the company level, but at warehouse W01 (a high-volume customer site), use different settings — e.g. tighter safety stock, different reorder rules. ## Item allocation keys When demand comes from a **forecast** at an aggregated level (e.g. forecast 1,000 units of a product family for Q1), the **item allocation key** distributes that aggregate forecast across specific items in the family. A 60/30/10 allocation key spreads the 1,000 across Item A (600), Item B (300), Item C (100). The aggregate forecasting + allocation key pattern is how to forecast realistically without forecasting every SKU individually. ## Planning groups **Planning groups** group items with similar planning behaviour for the engine's scheduling efficiency. The Planning Optimization engine can run plans for individual planning groups, useful for very large item portfolios where running everything at once would be costly. ## Master plans A **master plan** is the *named planning scenario* — Static (the production plan), Dynamic (the simulation plan). Different master plans can be run with different parameters; the production master plan is what feeds purchase requisitions and planned production orders. ## Forecast plans A **forecast plan** is a separate named scenario for forecasting purposes — typically the demand forecast feeding the production plan. ## Coverage dimensions What's the granularity of planning? - **Item** — plan one number per item across the company. - **Item + Site** — plan per item at each site. - **Item + Warehouse** — plan per item at each warehouse. - **Item + Site + Warehouse + Batch** — finest granularity. Configured per item; affects the volume of planning data and the engine's runtime substantially. **Common design pitfalls.** - **One coverage group for all items** — every item gets the same policy regardless of profile. ABC analysis should drive different policies per velocity tier. - **Min/Max without periodic review** — minimum / maximum levels become outdated as demand shifts; review quarterly. - **Forecasts without item allocation** — coarse forecasts produce coarse planning suggestions. Allocate appropriately. - **Coverage time fence too short** — supply doesn't materialise in time for visible demand. ## Operational discipline Design coverage groups by item profile (A-class, B-class, C-class, MTO, slow-moving). Document the policy choice per group. Review quarterly against actual performance. Tune. ## Where it stops Very sophisticated planning (multi-echelon optimisation, simultaneous capacity-and-material constraints, complex scenario modelling) sometimes exceeds the configurable engine and needs partner APS. For mainstream mid-to-large manufacturing and distribution, well-tuned master planning groups in F&O are sufficient. --- # Master planning runs in Dynamics 365 Finance and Operations What master planning actually does in F&O — the regenerative vs net change run, planned orders, action messages, and how the engine produces a supply plan. Source: https://www.solvingdynamics365.com/guides/master-planning-runs-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 ### Key facts - F&O offers two master planning engines: classic master planning, which batch-processes the whole plan on the SQL database, and Planning Optimization, a newer in-memory Azure service that runs orders of magnitude faster and supports incremental runs. - Regenerative runs recalculate every item in scope and are typically scheduled nightly or weekly, while net-change runs recalculate only items whose net requirement changed and can run hourly or continuously. - For manufactured items, master planning recursively explodes BOMs — finished-good demand generates a planned production order, which generates demand for each component, recursing through multi-level BOMs until raw materials. - A time fence prevents the engine from changing existing orders within a defined near-term window without explicit planner action, and a separate action-message time fence prevents it from even producing recommendations in that window. - On 10,000-plus items, classic master planning can run for hours where Planning Optimization completes in minutes, which by itself often justifies migrating from classic on large supply chains. **Master planning** is the F&O engine that turns demand (sales orders, transfers, forecasts) and existing supply (on-hand, purchase orders, production orders) into a coherent supply plan — planned purchase orders, planned production orders, planned transfer orders, and action messages on existing supply. Master planning runs are a daily or hourly rhythm in most production deployments. **Two engines.** - **Classic master planning** — the legacy engine, runs on the F&O SQL database, batch-processes the whole plan. - **Planning Optimization** — the newer in-memory service, runs in Azure, much faster, supports incremental runs. Both follow the same conceptual model. Planning Optimization is the strategic direction; new deployments should start there unless they need a feature that classic supports but PO doesn't (still a shrinking list). ## The master plan record A master plan defines the run: - **Time fence** — how far into the future planning suggests orders. - **Coverage codes inheritance** — defaults if items don't specify. - **Calculations to include** — sales orders, forecasts, transfers, BOMs, kits. - **Filters** — items, sites, warehouses to include. A typical setup has two plans: - **Static plan** — read-only, used by procurement to firm purchase orders. - **Dynamic plan** — recalculated frequently, used by planners for what-if and short-term decisions. Some teams run a third **simulation plan** for scenario analysis. **Regenerative vs net-change.** - **Regenerative** — recalculates everything for every item in scope. Heavier; usually nightly. - **Net change** — recalculates only items whose net requirement changed since last run. Lighter; hourly. Planning Optimization handles incremental more efficiently than classic. Regenerative every weekend, net-change every hour or even continuously is the typical cadence. **What the engine produces.** - **Planned orders** — suggestions: planned purchase, planned production, planned transfer, planned kanban. - **Action messages** — recommendations on existing supply: advance, delay, increase, decrease, cancel. - **Futures messages** — alerts that promised dates can't be met. - **Capacity warnings** — if scheduling reveals overload. Planners review in the **Planned Orders** workspace. Firming a planned order converts it to the real order (purchase, production, transfer); action messages drive amendments to existing orders. ## Pegging The link from supply to demand. Every planned order traces to the demand it covers, and every demand traces to its supply. The **Pegging tree** view shows: this sales order → this planned production → this planned purchase. Pegging visibility is invaluable for impact analysis when a vendor delays. ## BOM explosion For manufactured items, master planning recursively explodes BOMs: 1. Demand for finished good → planned production order. 2. Production order needs components per BOM → demand for each component. 3. Each component → existing supply or new planned order (purchase, production, transfer). 4. Multi-level BOMs recurse until raw materials. The explosion respects: - **Production routes** for lead time calculation. - **Production calendars** for capacity. - **BOM versions** active on the planned production date. ## Forecast consumption As real sales orders land in forecast periods, they consume the forecast. Master planning sees the net demand (max of forecast remaining, actuals). Without consumption, demand doubles. **Lock periods and frozen zones.** - **Time fence** — the window within which the engine doesn't change existing orders without explicit planner intervention. - **Action message time fence** — the window within which the engine doesn't even produce action messages. These prevent constant rescheduling of imminent operations. **Performance.** - **Classic master planning** on 10K+ items can run for hours. Mitigations: index tuning, batch parallelism, scoped plans. - **Planning Optimization** on the same volume runs in minutes — orders of magnitude faster because it's an in-memory service. For large supply chains, PO performance often justifies the migration from classic by itself. **Common pitfalls.** - **Stale forecasts.** Engine produces precise suggestions for a forecast nobody believes any more. - **Lead times wrong.** Suggested orders due dates miss reality; planners override constantly. - **Coverage codes default-only.** No item-level tuning; one-size-fits-all suggestions. - **Ignoring action messages.** Hundreds of action messages every day; planners triage by ignoring most. Build a discipline of working messages or accept that the engine will inflate exception backlogs. - **Pegging not used.** Planners override without understanding downstream consequences; supply chain becomes opaque. ## The operational rhythm Daily morning planner stand-up: review last night's regenerative results, work the top action messages, firm the next 24 hours of planned orders. Master planning is a tool for the planning rhythm — not a substitute for planner judgement, but a force-multiplier for it. ## Where to go next The engine behind the run is [Planning Optimization](https://www.solvingdynamics365.com/guides/dynamics-365-planning-optimization); the parameters that shape it are [master planning groups](https://www.solvingdynamics365.com/guides/master-planning-groups-in-f-and-o) and [replenishment policies](https://www.solvingdynamics365.com/guides/inventory-replenishment-policies-in-scm); the demand signal comes from [demand planning](https://www.solvingdynamics365.com/guides/dynamics-365-demand-planning). Planned production orders hand off to [production scheduling](https://www.solvingdynamics365.com/guides/production-scheduling-in-f-and-o). --- # Modern POS in Dynamics 365 Commerce How Modern POS works in Dynamics 365 Commerce — channel architecture, offline mode, peripherals, and the differences from Cloud POS. Source: https://www.solvingdynamics365.com/guides/modern-pos-in-dynamics-365-commerce Section: Finance & SCM / Retail & commerce Published: 2026-05-01 For retailers running Dynamics 365 Commerce, the in-store cash register is **Modern POS (MPOS)** — a Windows-based point-of-sale application that runs on store-level tills, handheld devices, and tablets, with full offline capability when connectivity drops. Understanding its architecture is essential for any retail implementation. ## The architecture Modern POS is a Universal Windows Platform app installed on Windows PCs, tablets, or handhelds. Each store runs a **Retail Server** (in-store or cloud-hosted) that proxies between MPOS and the head-office Commerce environment. The flow: ``` MPOS → Retail Server → Head Office (Commerce / F&O) ``` When the head office is unreachable, MPOS continues operating against the **store database** — a local SQLite copy synced from head office that holds the current product catalogue, prices, promotions, customer data, and inventory. ## Offline mode This is the differentiator. When the connection to the Retail Server drops: - The till keeps ringing sales against the local database. - Transactions queue locally for upload. - Customer lookups, loyalty checks, and most operations work locally. - Some operations (payment via online gateways, complex price overrides requiring approval) may pause. When connectivity returns, queued transactions sync up to head office, and any pending downloads (new prices, new products, new customers) sync down. The pattern survives spotty connectivity, brief network outages, and even multi-day disruptions without losing transactions. ## Channel data exchange A scheduled service called **Commerce Data Exchange (CDX)** synchronises data between head office and stores in both directions: - **Down to store**: product catalogue, prices, promotions, customers, gift cards. - **Up from store**: transactions, inventory adjustments, time clock entries, customer registrations. CDX runs on a configurable schedule per store; high-volume stores run more frequently. ## Peripherals Modern POS speaks to a wide range of retail hardware through the **Hardware Station** — a separate service running on the till that manages: - Receipt printers. - Barcode scanners. - Cash drawers. - Customer-facing displays. - Payment terminals (chip-and-PIN, contactless, NFC). - Scales (for weight-based goods). - Magnetic stripe readers. - Signature capture pads. Hardware drivers are certified per device; the device-and-driver catalogue is published by Microsoft and the hardware OEMs. ## Functions The cashier experience covers: - **Transactions** — scan or look up items, apply discounts (rule-based or manual with override approval), accept payment (any tender configured), produce receipt. - **Returns** — with-receipt return (lookup posted transaction), no-receipt return (with manager override). - **Customer lookup and creation** — at the till; ties transactions to loyalty. - **Gift cards** — issue, top up, redeem. - **Loyalty** — earn and redeem points inline. - **Order from store** — create a sales order for items not in store; ship from another location or central warehouse. - **Pickup at store** — fulfil online orders. - **Cash management** — opening float, mid-shift counts, end-of-shift closeout, deposits. - **Time clock** — staff clock in / out, with hours flowing to payroll. - **Reporting** — basic in-store reports for managers. ## Cloud POS A parallel browser-based POS — **Cloud POS** — runs the same functionality in a web browser, suitable for tablets and lighter-weight terminals without the Windows installation overhead. Cloud POS has fewer offline capabilities (depends on internet for most operations). ## Store Commerce app A newer iteration of the in-store experience, designed for modern Android and iOS-friendly hardware, with an updated UI and clienteling features. Microsoft is investing in Store Commerce as the strategic direction; Modern POS remains supported but new builds increasingly start with Store Commerce. ## Operational reality Retail POS implementations are unforgiving — the till is the most-watched part of any retail operation. Pilot in one store before rolling out; train cashiers extensively; test offline scenarios deliberately before go-live. --- # Number sequences in Dynamics 365 Finance and SCM How number sequences work in Dynamics 365 Finance and SCM — scope, continuous vs non-continuous, manual override, and statutory gap-free requirements. Source: https://www.solvingdynamics365.com/guides/number-sequences-in-finance-and-operations Section: Finance & SCM / Finance Published: 2026-05-01 Dynamics 365 Finance and SCM generates unique identifiers — voucher numbers, document numbers, master-record IDs — through a **number sequence** framework that's more elaborate than Business Central's. Understanding its scope and operating mode matters for statutory compliance, performance, and avoiding the silent gaps that can become audit findings. ## The model A **number sequence** has: - A **code** — the identifier of the sequence. - A **scope** — Shared, Company, Legal entity, Operating unit. Determines whether different companies share or have separate sequences. - A **segmentation** — the structure of the generated number, combining alphanumeric prefixes, constants, and the numeric counter. - A **counter range** — first, last, current, format. - **Continuous or non-continuous** — see below. - **Manual entry allowed** — whether users can override the auto-generated number. - **Allow changes** — whether the sequence definition can be edited after use. ## Segmentation A number sequence's output is built by concatenating segments. Examples: - `INV-{0000000000}` — produces INV-0000000001, INV-0000000002, etc. - `{Year}-{Company}-{0000000}` — produces 2026-FIN-0000001, 2026-FIN-0000002. - Year and company segments are dynamic and re-evaluated at each generation. Different segmentations can be applied per scope or per condition (e.g. invoice prefix per legal entity). **Continuous vs non-continuous.** - **Continuous** — the sequence guarantees no gaps. Each number generation reserves a number; if the using transaction fails to commit, the number is *not* released — but the system tracks reservation and uses sophisticated handling to minimise gaps. Continuous sequences are statutorily required in many jurisdictions for posted document numbering (especially invoices), and the trade-off is performance: continuous sequences serialise number generation, causing locks at high concurrency. - **Non-continuous** — the sequence trades gap-freeness for performance. Numbers are allocated in batches per user/session; gaps appear if a session ends without consuming all reserved numbers. Acceptable for internal-only document numbering where gaps are immaterial. Choose continuous for any externally-visible, statutorily-relevant numbering (sales invoices in EU jurisdictions, e-invoicing references, customer-facing PO numbers). Choose non-continuous for high-volume internal numbering (journal voucher numbers, item ledger entries) where performance matters more. ## Manual override Most number sequences allow manual entry where the auto-generated number can be overridden. Useful for migration; risky in steady-state because it allows user-controlled gaps and duplicates. Tighten to "automatic only" after go-live wherever statutory compliance allows. ## Per-company vs shared Set the **scope** carefully: - **Shared** — the same sequence across all companies in the tenant. Used for cross-company references. - **Company** — separate sequence per company. Used for company-internal numbering. - **Legal entity** — separate per legal entity. The most common. ## Renaming and resetting Once used, sequences should not be reset or restructured — historical references in audit trails depend on the existing numbering. Plan for several years of growth in the initial range. **Operational pitfalls.** - **Reaching the upper bound.** A sequence configured 1–999999 hits the wall after a million transactions. Configure realistic ranges with year prefixes that segment naturally. - **Statutory gap-free requirement missed.** Setting an invoice sequence non-continuous in a country that requires gap-free invoicing triggers audit findings. Verify country requirements. - **Performance lock under load.** Continuous sequences serialise; high-concurrency transactional environments need careful tuning. ## Audit Every generated number is logged; gaps in continuous sequences are investigable. --- # One Version and updates in Finance and SCM How Microsoft's One Version policy works for Dynamics 365 Finance and Supply Chain — Service Updates, pause windows, and the upgrade obligation. Source: https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates Section: Finance & SCM / Overview & platform Published: 2026-05-01 Updated: 2026-09-06 ### Key facts - Every Finance and Supply Chain Management production environment, on every tenant, is kept on a current platform version under the One Version policy — there is no option to remain indefinitely on an older version. - Service Updates ship roughly every six weeks, about eight per year, bundling new features, fixes, and platform changes across the tenant base. - Customers can pause a Service Update for a limited number of cycles per calendar year, per environment, through Lifecycle Services — typically to skip year-end close — after which the maximum pause is consumed and the update applies automatically. - Platform updates (runtime and infrastructure changes) are mandatory and continuous, separate from Application updates (Finance/SCM standard code changes), which follow the Service Update cadence. - Thin chain-of-command extensions rather than deep copy-and-modify customisation are the single biggest predictor of a quiet Service Update cycle, since compiled X++ extending standard logic is where breaking changes surface most. Dynamics 365 Finance and Supply Chain Management run under Microsoft's **One Version** service-update policy: every production environment, in every region, on every tenant, is updated to a current platform version on a fixed cadence. Customers have limited flexibility around timing and *no* ability to remain indefinitely on an older version. This is one of the biggest cultural differences from on-premise AX. ## The cadence Microsoft ships **Service Updates** roughly every six weeks — about eight per year — each bundling new features, fixes, and platform changes. Service Updates apply in a rolling fashion across the tenant base; customers can choose between channels (e.g. *General* vs *Early access*) for some control over which release lands when. ## Pause windows Customers can **pause** Service Updates for a small number of cycles in a calendar year, deferring an update — typically used to skip a busy period like year-end close. After the maximum pause is consumed, the update applies automatically. The pause is per-environment and configured through LCS. ## Service Update vs Application/Platform update *Platform* updates are runtime and infrastructure changes — these are mandatory and continuous. *Application* updates change Finance/SCM standard code; these are part of the Service Update bundle and follow the same cadence. ## Custom code obligations Custom code (X++ extensions, integrations, reports) compiled against an older platform may break against a newer one. Microsoft's tools include **Code Upgrade** services in LCS that scan custom code for breaking changes ahead of a service update. ## Quality assurance Microsoft pre-tests Service Updates against a sample of customer environments and gates rollout by region. Customers should still run their own regression suite against the **preview** service update on a sandbox before applying to production. ## Why One Version Microsoft cannot economically support hundreds of AX versions in production for decades. One Version is the price of SaaS: you get continuous improvements, security patches, and uniform support, in exchange for keeping current. The discipline is real but the rewards — performance gains, AI features, regulatory updates — accrue without big-bang upgrades. ## Operational reality Mature Finance/SCM customers treat each Service Update as a small ops task: install in sandbox a week or two ahead, run the regression suite, brief power users on new features, accept production rollout. With practice it becomes routine. ## The One Version release cycle at a glance | Stage | Who runs it | Typical timing | |---|---|---| | Preview build published | Microsoft | ~2-3 weeks before general rollout | | Install on sandbox, run regression suite | Customer / partner | As soon as preview is available | | Code Upgrade scan (X++ breaking changes) | Customer / partner via LCS | Alongside sandbox testing | | Brief power users on visible changes | Customer | Days before production rollout | | General rollout to production | Microsoft, per tenant's channel/region | Rolling, over the release window | | Pause window (optional) | Customer, via LCS | Declared ahead of the cycle it applies to | ## What actually breaks The features most likely to surface a real regression are the ones closest to customisation: chain-of-command extensions on standard classes, event handlers subscribing to platform events whose signature changed, and reports built against data entities that had fields added, renamed, or reshaped. Pure configuration (number sequences, workflows, security roles) rarely breaks; compiled X++ extending standard logic is where Code Upgrade scans earn their keep. A thin extension layer — small, focused chain-of-command overrides rather than deep copy-and-modify customisation — is the single biggest predictor of a quiet Service Update cycle. ## Channels and staggered rollout Microsoft doesn't push every tenant to a new Service Update on the same day even within a chosen channel — rollout is staggered by region and cohort so that a problem caught in an early wave can be halted before it reaches every customer. This means two tenants on the same channel can be a few days apart on the same nominal version; it is normal, not a sign of a misconfigured environment, and it's one reason the sandbox-first-then-production sequence matters more than watching a specific calendar date. ## Where to go next Service updates land through [environments and LCS](https://www.solvingdynamics365.com/guides/dynamics-365-finance-environments-and-lcs) and are absorbed through [release management](https://www.solvingdynamics365.com/guides/release-management-for-dynamics-365) and [test automation](https://www.solvingdynamics365.com/guides/test-automation-for-dynamics-365). Custom [X++](https://www.solvingdynamics365.com/guides/f-and-o-x-plus-plus-language) is what needs checking each cycle. The 2026 change to how Microsoft communicates the roadmap — without changing this cadence — is in [the 2026 wave 2 guide](https://www.solvingdynamics365.com/guides/dynamics-365-2026-wave-2-release-highlights). ### Frequently asked questions **What is One Version?** Microsoft's service-update policy for Finance and Supply Chain Management: every production environment on every tenant is kept on a current platform version on a fixed cadence, with limited timing flexibility and no option to stay on an older version indefinitely. **How often do service updates arrive?** Roughly every six weeks — about eight a year — bundling features, fixes, and platform changes, rolled out across the tenant base with channel choices for some control over timing. **Can I pause a service update?** For a limited number of cycles per calendar year, per environment, through Lifecycle Services — typically to skip year-end close. Once the maximum pause is consumed, the update applies automatically. **How do I protect custom X++ code?** Run the LCS Code Upgrade tooling to scan for breaking changes, install the preview service update on a sandbox a week or two ahead, and run your regression suite before production rollout. --- # Organisation hierarchies in Dynamics 365 Finance and SCM How organisation hierarchies work in Dynamics 365 Finance and SCM — legal entities, operating units, departments, and the security and reporting they enable. Source: https://www.solvingdynamics365.com/guides/organization-hierarchies-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 The **organisation hierarchy** in Dynamics 365 Finance and Supply Chain Management is the structural backbone of how the system understands the customer's company structure. Security, financial dimensions, intercompany, reporting, workflow routing, and budgeting all hang off it. Getting it right at implementation pays back forever. **The building blocks.** - **Legal entity** — the unit of statutory accounting. One legal entity = one set of statutory books, one tax ID, one set of GL postings. A multinational with subsidiaries in five countries has at least five legal entities. - **Operating unit** — a non-legal-entity organisation unit used for management and operational segmentation: cost centre, value stream, business unit, department, team. Operating units don't have their own GL; they're an analytical / operational layer. - **Department** — a specific type of operating unit, commonly used as a default financial dimension. - **Cost centre** — another operating unit type, used for cost accumulation. - **Worker** — F&O's HR concept of an employee; workers map into operating units through positions. ## Hierarchies Organisations are connected through **hierarchies** — defined trees that express the relationship between organisation units. F&O supports **multiple parallel hierarchies** for different purposes: - **Legal hierarchy** — legal-entity ownership structure (parent owns subsidiary). Used for consolidation and intercompany. - **Reporting hierarchy** — management reporting structure (e.g. global → region → country → operating unit). May differ from the legal structure. - **Manager hierarchy** — HR-style management reporting structure (people report to people). Used for workflow assignment. - **Cost centre hierarchy** — budget and cost roll-up structure. The same operating unit can appear in multiple hierarchies with different parents. ## Why parallel hierarchies matter Legal structure (who owns what) is rarely the same as management structure (who is responsible for what), which is rarely the same as cost centre structure (where spend is tracked). Forcing all three into one tree creates compromise; parallel hierarchies let each view be honest. ## Effective dates Hierarchies are *time-aware*: an org unit can move between parents on a specific date, and historical reporting respects the structure at the historical date. Reorgs don't destroy history. ## Security through hierarchies Security roles can be scoped to specific org units in a hierarchy — "Cost Centre Manager for Operating Unit X and its descendants". The hierarchy is what makes scope feasible without listing every entity manually. ## Workflow assignment Approval routing uses the manager hierarchy to walk up the chain until an approver with sufficient authority is found. Configure the hierarchy realistically; gaps create routing failures. ## Financial dimensions and hierarchies Most customers configure key org units (departments, cost centres) as **entity-backed financial dimensions** — so transactions automatically tag the relevant org unit, and the hierarchy can roll up reporting. ## Consolidation Consolidation companies in F&O reference the legal hierarchy to determine subsidiary inclusion, ownership percentages, and currency translation. **Common design pitfalls.** - **Too few hierarchies.** Forcing legal, reporting, and cost views into one tree compromises all three. - **Too many hierarchies.** Beyond five or six, complexity overtakes value. - **Reorgs not handled with effective dates.** Just renaming or re-parenting in place destroys historical comparability. - **Department dimension not aligned with hierarchy.** Reporting roll-ups break when the dimension's parent doesn't match the hierarchy's structure. ## Maintenance Org hierarchies need maintenance as the business changes — quarterly review keeps them aligned. --- # Parallel currencies in Dynamics 365 Finance How Dynamics 365 Finance handles parallel reporting currencies — accounting currency, reporting currency, and tax currency, with the consolidation implications. Source: https://www.solvingdynamics365.com/guides/parallel-currencies-in-finance-and-operations Section: Finance & SCM / Finance Published: 2026-05-01 Dynamics 365 Finance handles multi-currency natively, and where Business Central supports an additional reporting currency, F&O takes it further with up to four parallel currencies on every transaction. Understanding which currency is which prevents many of the most embarrassing reporting errors at consolidation. **The currency dimensions of a transaction.** - **Transaction currency** — the currency the transaction itself was conducted in. A purchase invoice from a German supplier is in EUR. - **Accounting currency** — the legal entity's primary statutory currency. The Spanish subsidiary's accounting currency is EUR; the US subsidiary's is USD; the Swedish subsidiary's is SEK. Every GL posting in the entity is stored in accounting currency. - **Reporting currency** — a second parallel currency to accounting currency, typically the parent group's currency. Configured per legal entity. Every GL posting is also stored in reporting currency at the same time, using rates from the configured exchange-rate type. The result: a Spanish subsidiary's GL can produce reports in both EUR (statutory) and USD (group reporting) without consolidation FX translation. - **Tax currency** — for some country localizations, statutory reporting requires a third currency layer (e.g. local-tax-authority currency in a foreign-currency-economy country). Configured per legal entity. ## Exchange-rate types Different transactions can use different rates. F&O has multiple **exchange rate types** — Spot, Average, Period-end, Budget, etc. Each transaction type can be configured to use a specific rate type for accounting-currency conversion and a different rate type for reporting-currency conversion. ## The exchange-rate table Rates are maintained per rate type, per currency pair, per starting date. Manual entry, file import, or service-based feeds (Microsoft ships connectors for some central banks, partner ISVs publish more). Rates have starting dates so historical postings re-translate consistently. ## Revaluation Period-end revaluation runs separately for accounting-currency open balances (e.g. open AR/AP in foreign currency converted at period-end rate to accounting-currency) and for reporting-currency revaluation (the same balances re-translated to reporting currency at the new rate). ## Realised FX When a foreign-currency invoice is settled at a different rate, realised FX gain/loss posts. F&O posts it in both accounting and reporting currency, with the correct calculation in each. ## Consolidation When the parent consolidates subsidiaries, two options: - **Consolidation in F&O.** Source companies feed their trial balances (in their accounting currency, often *plus* their reporting currency for the parent's view) into a designated consolidation company. F&O applies currency translation at consolidation-rate types (current rate, historical rate, average rate as configured), eliminations, and adjustments to produce group financials. - **Consolidation outside F&O.** Larger groups feed F&O data into a dedicated consolidation tool (OneStream, Workiva, Hyperion, SAP BPC) for sophisticated consolidation logic. F&O acts as the source. ## Subsidiaries with parent reporting currency in operating data A common pattern: every subsidiary's reporting currency is set to the parent's group currency. Each subsidiary's GL is queryable directly in group currency without consolidation. Operational dashboards in Power BI work across the group without complex transformations. **Common pitfalls.** - **Setting reporting currency only at the end of year 1.** Now reporting currency starts from year 2, leaving year 1 with no historical group-currency baseline. Set reporting currency from go-live. - **Inconsistent exchange-rate types.** Different rate types on different transactions produce non-reconcilable totals. Standardise. - **Manual rate maintenance.** Forgotten rate updates cause posting failures or wrong rates. Use automated rate feeds. --- # Periodic processes in Dynamics 365 Finance and SCM The recurring routines that drive month-end, year-end, and ongoing operations in F&O — period close, posting flushes. Source: https://www.solvingdynamics365.com/guides/periodic-processes-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Dynamics 365 Finance and SCM runs a substantial library of **periodic processes** — batch routines that handle period close, post pending transactions, recalculate balances, generate statutory reports, and maintain operational data. Knowing which to run when separates well-operated tenants from chaotic ones. ## The four cadences Most periodic processes fall into one of four cadences: - **Daily** — operational continuity routines. - **Weekly** — operational hygiene and lighter reconciliations. - **Monthly** — period close. - **Quarterly / Annually** — statutory and long-cycle. **Daily processes.** - **Master planning runs** — depending on the operation, planning runs nightly to refresh supply against demand. - **Cost recalculation (incremental)** — keep inventory costs current. - **Currency exchange rate import** — fetch the day's rates. - **Sales / purchase order picking and shipping** — ongoing operations. - **Bank statement imports** — for tenants with bank feeds. - **Job queue health checks** — review failed batches. **Weekly processes.** - **Customer / vendor balance reconciliation** — verify sub-ledger to GL match. - **Bank reconciliation** — for tenants without daily feeds. - **Production order closures** — close finished production orders for cost realisation. - **Project WIP recalculation** — keep project cost accruals current. - **Reservations review** — clean up stale reservations on cancelled orders. ## Monthly processes — the period close The full month-end sequence: 1. **Cut-off and accrual posting** — record accruals for goods received but not invoiced, services consumed but not billed, payroll provisions. 2. **AP / AR reconciliation** — sub-ledger to GL match. 3. **Bank reconciliation** — all active bank accounts. 4. **Foreign currency revaluation** — period-end rate revaluation of open foreign-currency balances. 5. **Fixed asset depreciation** — calculate and post period depreciation. 6. **Inventory closing or recalculation** — reconcile inventory costs. 7. **Project recognition** — post project revenue and cost recognition per the configured rules (percentage-of-completion, milestones). 8. **Cost accounting allocation** — run primary, secondary, tertiary allocations. 9. **VAT / sales tax settlement** — calculate and post period VAT. 10. **Intercompany reconciliation** — verify intercompany balances match across legal entities. 11. **Period-end reporting** — financial reports, management dashboards. 12. **Period closure** — lock the period for posting. **Quarterly / annual processes.** - **Statutory reporting** — country-specific VAT returns, intrastat, SAF-T, electronic invoicing summaries. - **Year-end close** — roll P&L to retained earnings, close fiscal year, open new year. - **Annual cost roll** — refresh standard costs for the new year. - **Audit data exports** — auditor data dumps. - **Asset book reconciliation** — verify FA register against GL. - **Inventory full physical count** — for organisations not running cycle counting. ## Batch framework Most periodic processes run through F&O's **batch framework** — configurable jobs with start times, recurrence, parallel batch groups, and retry policies. The batch framework is the F&O equivalent of BC's job queue, with finer granularity for high-volume tenants. ## Monitoring **System administration** workspace shows batch history, failed jobs, queued work, and execution time trends. Configure alerts on: - Jobs that fail repeatedly. - Jobs that exceed expected duration substantially. - Queue depth growing unboundedly. **Common pitfalls.** - **Process documentation gaps** — when the controller leaves, nobody knows the close sequence. Document the runbook. - **Failed jobs not investigated** — batch errors silently accumulate. Daily check. - **Out-of-sequence runs** — running inventory closing before WIP recognition produces wrong cost. Honour dependencies. - **Missing year-end tasks** — first-year operations miss year-end steps that the team learns the hard way. ## Operational reality Period close is the test of operational maturity. A tenant that closes cleanly in 3 working days has well-tuned periodic processes; a tenant that takes 10 days has work to do. --- # Planning Optimization in Dynamics 365 Supply Chain How Planning Optimization replaced the legacy MRP engine — in-memory architecture, scalability, scope, and migration considerations. Source: https://www.solvingdynamics365.com/guides/dynamics-365-planning-optimization Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 **Planning Optimization** is the modern master-planning engine in Dynamics 365 Supply Chain Management. It replaced the legacy AX-era MRP engine that struggled with large data volumes and long-running planning runs. The new engine is in-memory, parallelised, and dramatically faster — but it has scope differences worth knowing. ## Architecture Planning Optimization runs as a separate Microsoft-managed Azure service, not in the F&O application tier. F&O streams the planning-relevant data (items, BOMs, routings, on-hand, open orders, forecasts, parameters) to the service; the service computes; the results flow back as planned orders, action messages, and reschedules. Because the engine is in-memory and runs in parallel, it can process plans for hundreds of sites and millions of items in minutes rather than hours. ## Net change and regenerative The service supports both **net change** plans (only items affected by a recent transaction are replanned) and **regenerative** plans (everything from scratch). Net change makes near-real-time MRP feasible for very large catalogues. ## Filtering Plans can be filtered by site, product, or any combination — useful for running a fast plan on a single site while keeping the global plan unchanged. ## Forecast consumption Forecast plans feed Planning Optimization through forecast time fences and consumption rules. The engine honours both global and per-coverage-group parameters. ## Action messages Output mirrors the legacy engine: *New*, *Increase*, *Decrease*, *Reschedule earlier*, *Reschedule later*, *Cancel*. Planners review and accept through the planning workbench in F&O. ## What's not yet covered Planning Optimization has parity for *most* AX MRP scenarios, but some specialised features remain on the legacy engine in some implementations: certain co-product / by-product configurations, intercompany advanced features, and some country-specific localizations. Microsoft publishes a feature-parity matrix; check before assuming everything ports cleanly. ## Co-existence During migration, customers can run **both engines** in parallel against the same data, compare results, and switch once parity is confirmed. This is the standard transition pattern from legacy MRP to Planning Optimization. ## Manufacturing scheduling Planning Optimization handles infinite-capacity material plans. **Finite capacity scheduling** (gantt-style scheduling on constrained work centres) remains a separate concern — typically run with the *Scheduling* engine or a partner scheduling product on top of the material plan. ## Net result A four-hour overnight MRP becomes a fifteen-minute job. Planning frequency goes from nightly to multiple times a day, and planners spend less time waiting and more time analysing. --- # Positive pay files in Dynamics 365 Finance How F&O generates positive pay files for bank fraud prevention — file formats, daily transmission, reconciliation, and the typical bank-specific variations. Source: https://www.solvingdynamics365.com/guides/positive-pay-files-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 **Positive pay** is a bank fraud-prevention service: each day, the company sends the bank a list of legitimately issued checks; the bank rejects any check presented that's not on the list. For US companies with check-based AP, positive pay is the standard control. F&O supports positive pay file generation through configurable data exchanges. **The threat being mitigated.** - **Check fraud** — stolen checks, altered amounts, counterfeit checks presented for payment. - **Without positive pay** — bank pays anything that looks like a valid check. - **With positive pay** — bank validates against the issuer's daily list. For companies issuing thousands of checks monthly, positive pay is essential. ## Positive pay file contents Typical fields per record: - Account number. - Check number. - Check amount. - Issue date. - Payee name. - Void status (for cancelled checks). The bank validates each presented check against the file. **Configuration in F&O.** - **Bank account** flagged for positive pay. - **Bank file format** configured (data exchange definition). - **Positive pay record** generated on check issuance. When a check is printed, a positive pay record is created. End-of-day, the records flow to a file. ## Generating the file **Generate positive pay file** action: 1. Selects records since last submission. 2. Formats per bank's specification. 3. Outputs file (CSV, fixed-width, XML, etc. depending on bank). 4. Marks records as submitted. ## Bank-specific formats Every bank has its own format: - **Chase** — specific layout. - **Bank of America** — different. - **Wells Fargo** — different again. - **JPMorgan** — different. F&O ships with templates for major banks; customisation needed for others. The configuration is a data exchange definition mapping F&O records to bank's expected fields. **Transmission methods.** - **Bank portal upload** — manual; operator uploads daily. - **FTP/SFTP** — automated transmission to bank's SFTP server. - **Bank API** — modern; programmatic. - **EDI** — for some banks. Automation reduces operational burden; without it, daily manual upload is a chore. ## Exceptions When the bank receives a check not on the list: - **Exception alert** to the company. - **Hold for review** — company decides accept or reject. - **Timeout default** — if no response, bank's default (often reject). The company reviews exceptions daily; legitimate checks (rare misses) get authorised, fraudulent ones rejected. ## Stop payments When a check is voided: - Stop payment record sent to bank. - Bank rejects if presented. - Positive pay file may include void instructions. **Reverse positive pay vs payee positive pay.** - **Standard positive pay** — match on account, check number, amount. - **Payee positive pay** — also match payee name; harder to defeat. Many banks offer both tiers; payee positive pay is stronger but requires accurate payee name capture. ## Daily transmission rhythm Critical: - Send positive pay file BEFORE any check could be presented. - Banks typically require file by 8 AM or so for that day's presentments. - Late files = checks presented before listing = potential acceptance of fraudulent items. The cutoff is bank-specific; verify and respect. ## Reconciliation against bank Beyond positive pay: - Bank statement received daily / monthly. - Match cleared checks against F&O bank ledger. - Investigate items not matching. Positive pay catches fraudulent checks at presentment; bank reconciliation catches issues post-clearing. ## ACH positive pay Beyond checks, ACH transactions can also use positive pay: - ACH originators authorised. - Unauthorised ACH debits blocked. F&O supports ACH positive pay configuration similarly. **Implementation considerations.** - **Bank partnership** — bank must support positive pay (most do). - **File format provisioned** — bank's specification implemented in F&O. - **Transmission method** — FTP / API setup. - **Exception handling process** — who reviews exceptions, how quickly. **Common pitfalls.** - **File late.** Daily transmission missed; window of fraud opportunity. - **Format errors.** File rejected by bank; checks not validated; revert to manual. - **Stop payment not transmitted.** Voided check reaches bank; pays out as positive pay-listed. - **Payee name mismatch.** "John Smith" vs "Smith, John"; payee positive pay flags legitimate checks. - **No exception review.** Bank rejects valid checks; vendor calls; AP scrambles. - **Manual override drift.** Operator approves exceptions routinely without analysis. **Operational rhythm.** - **Daily** — file transmission, exception review, monitoring. - **Weekly** — process audit; missed file investigations. - **Monthly** — reconcile bank's records of presented vs our records of issued. ## Strategic positioning Positive pay is a high-leverage fraud control — relatively cheap to set up, dramatically reduces check fraud risk. For any US company issuing checks at scale, it's a standard expectation. F&O supports it natively with appropriate bank format configuration; the operational discipline of timely transmission and exception review is what makes it effective. The decision to NOT use positive pay rarely makes sense for check-issuing companies; the implementation is small, the protection material. --- # Posting profiles in Dynamics 365 Finance The posting-profile mechanism in Dynamics 365 Finance — how transactions translate into GL entries, and why getting them right matters. Source: https://www.solvingdynamics365.com/guides/dynamics-365-posting-profiles Section: Finance & SCM / Finance Published: 2026-05-01 A **posting profile** in Dynamics 365 Finance is a configuration object that tells the system which GL accounts to use when a sub-ledger transaction posts. Sub-ledgers (customers, vendors, fixed assets, inventory, sales tax, banks, projects) all have posting profiles. They're how F&O bridges the operational world of invoices, receipts, and shipments to the accounting world of double-entry GL. ## The pattern Each sub-ledger has a default posting profile, plus the ability to attach more specific profiles to *groups* or *individual records*. For customers, for example, you might have a default profile pointing AR control to GL 1500-Receivables, an export-customer profile pointing AR control to 1510-Export Receivables, and an inter-company profile pointing AR control to 1520-IC Receivables. F&O picks the most specific match at posting time. ## What's in a profile A vendor posting profile names the GL accounts for: - Summary account (AP control) - Settlement account (where settlements net) - Liability for discount - Arrival account (goods received not invoiced) - Charges accounts - And more, depending on the modules in use. ## Why it matters Posting profiles are the single biggest source of GL posting errors after dimensions. A miscoded posting profile sends thousands of transactions to the wrong account, often only discovered at period-end when the trial balance won't reconcile. Mass-correcting requires either reversing and reposting transactions or running a reclassification journal — both are heavy operations. ## Group versus specific Posting profiles default at the *group* level (Customer Group, Vendor Group, Item Group, Bank Group). Resist the urge to override at the individual record level — it scatters configuration and makes auditing nearly impossible. Define groups for every meaningful classification, attach profiles at the group, and override at the record only when there's an explicit, defensible reason. ## Currency and dimensions Profiles can vary by currency (e.g. AR for EUR customers vs SEK customers) and can carry default dimension values that propagate to posted entries. ## Audit Every GL transaction stores a reference back to the source document, so auditors can trace from a GL line to the originating sub-ledger transaction and to the profile that mapped them. Reverse drill is one of the most-used troubleshooting tools. ## Design discipline Map out the posting profile design as part of CoA design, not as an afterthought. Two days early saves two weeks late. --- # Production scheduling in Dynamics 365 Supply Chain How scheduling works in Dynamics 365 SCM — operations vs job scheduling, finite vs infinite capacity. Source: https://www.solvingdynamics365.com/guides/production-scheduling-in-f-and-o Section: Finance & SCM / Manufacturing Published: 2026-05-01 Production scheduling in Dynamics 365 Supply Chain Management has more dials than any other module. The scheduling decisions made at implementation determine whether the system supports the planner's job or fights it every day. **Two scheduling layers.** - **Master planning** — high-level material and capacity plans across the planning horizon. Driven by **Planning Optimization** (the modern engine that replaced the legacy MRP). Outputs planned production orders sized to match demand and constrained by lead times. - **Production scheduling** — the operation-level sequencing of work on specific work centres, with start times, end times, and resource allocations. This is the planner's daily working surface. ## Operations vs job scheduling When a production order is firmed and released, it can be scheduled in two granularities: - **Operations scheduling** — schedules each routing operation as a whole, with single start and end times. Faster, less granular. Suitable when the work centre capacity is the main concern and within-operation sequencing isn't critical. - **Job scheduling** — schedules each job (a single occurrence of an operation on a specific work centre) at the lowest level, with full precedence and sequencing. Slower to compute, much more accurate. Required for any scenario where minute-level sequencing matters (e.g. tight changeovers between SKUs). **Finite vs infinite capacity.** - **Infinite capacity** — the scheduler ignores work-centre capacity limits. Useful for planning what *should* happen given demand; less useful for committing to delivery dates. - **Finite capacity** — the scheduler respects work-centre calendars and existing load. Operations that can't fit get pushed out. Required to produce realistic delivery dates. Most production environments switch on finite capacity from day one; the trick is configuring the calendars and capacities accurately. ## Forward vs backward scheduling A production order can be: - **Forward scheduled** from a start date — operations begin at the start date and run forward; the finish date is computed. - **Backward scheduled** from a finish date — operations are scheduled to end on the finish date; the start date is computed. The choice depends on the business need. Make-to-stock production with no specific delivery date forward-schedules from earliest start. Make-to-order with a customer delivery date backward-schedules from the required ship date. ## The Gantt chart F&O's production scheduling Gantt chart visualises operations across work centres and time. Planners drag operations to reschedule, hold operations to free capacity, and assess load by work centre. The Gantt is functional but not as polished as dedicated APS (Advanced Planning and Scheduling) tools. ## Constraints not covered Out of the box, F&O's scheduler handles work-centre capacity, calendars, and operation duration. It does *not* natively handle: - **Material constraints** — the scheduler assumes material will be available. Real shortages aren't reflected automatically. - **Sequence-dependent setup times** — switching from product A to product B vs A to C may take different setup times; the standard engine doesn't model this. - **Tooling and labour constraints** as independent resources. - **Campaigning** — running batches of similar SKUs together to minimise changeovers. For these, customers add **partner APS solutions** (Asprova, PlanetTogether, Preactor, Simio) that integrate to F&O. ## Master scheduling cadence Most operations run a regenerative or net-change plan nightly; finite scheduling of the planning horizon runs in the morning. The shop-floor sees a stable, realistic plan when they start work. ## Where ROI compounds Finite, accurate scheduling moves on-time delivery from "we missed several this week" to "we hit them" — and the difference compounds in customer relationships and inventory cost. --- # Public sector features in Dynamics 365 How Dynamics 365 Finance supports public-sector accounting — fund accounting, budget control, encumbrance, grants, and compliance. Source: https://www.solvingdynamics365.com/guides/dynamics-365-public-sector-features Section: Finance & SCM / Public sector Published: 2026-05-01 Dynamics 365 Finance ships a **Public Sector** feature set that turns the standard ERP into a government-grade fund-accounting system. Public-sector finance is fundamentally different from commercial finance — fund-balance accounting, mandatory budget control, encumbrance, and stricter audit — and these features are how F&O reaches that bar. ## Fund accounting Public bodies don't run a single P&L; they account by **fund**, where each fund is a self-balancing set of accounts representing a programme, grant, or restricted purpose. Public Sector mode adds **derived financial hierarchies** that classify GL postings by fund, function, programme, and other public-finance dimensions, with intra-fund balance enforcement. ## Budget control General Public Sector users run **budget control** in *hard-stop* mode — a transaction that would exceed its budget line is blocked at entry, not warned. Budget control checks happen at multiple points (requisition, purchase order, invoice) with configurable rules. Funds are released and consumed throughout the year and reconciled at period-end. ## Encumbrance and pre-encumbrance When a purchase requisition is approved, F&O posts a **pre-encumbrance** against the budget — money set aside but not yet committed. When the requisition becomes a purchase order, the pre-encumbrance converts to an **encumbrance**. When the vendor invoice arrives, the encumbrance is relieved and an actual expense posts. This three-stage commitment accounting is mandatory in most public-sector environments. ## Grants management Awards, sub-awards, billing schedules, and grant-specific budget tracking. Costs incurred against a grant can be allocated and billed back to the granting authority through standard or custom rules. ## Year-end procedures Public-sector year-end carries forward open encumbrances, closes the fund balances, and produces the required statutory disclosures. The standard close routines extend with public-sector-specific steps. ## Procurement compliance Public-sector procurement often requires open competitive bidding, vendor pre-qualification, and audit trails for every step. F&O's Procurement and Sourcing module is the workhorse here, configurable for the bidding rules of the jurisdiction. ## Vendor 1099 (US) and equivalents Year-end vendor reporting for tax authorities ships standard for the US (1099) with localization variants for other countries. ## Where it fits Federal, state/provincial, and large municipal governments are the target. Smaller public bodies (small cities, school districts) can run Public Sector but the implementation cost is meaningful — for very small public organisations, Business Central with a fund-accounting ISV add-on is sometimes the more proportionate fit. --- # Purchase requisitions and approvals in Dynamics 365 Finance How F&O's purchase requisition workflow handles requesters, approvers, conversion to PO, and the integration with procurement policy and budget control. Source: https://www.solvingdynamics365.com/guides/purchase-requisitions-and-approvals-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-06-16 For enterprise organisations, every meaningful spend should start as a **purchase requisition** — a formal request from an employee asking the organisation to commit to buying something. The requisition routes through approval, gets approved (or rejected), and then converts to a purchase order that the procurement team executes. Dynamics 365 Finance handles the full lifecycle. ## The requester experience An employee identifies a need: - Buy office supplies. - Engage a contractor. - Purchase software licences. - Order equipment. - Pay for training. Through a self-service workflow (often via a Power Apps interface or directly in F&O), the requester: 1. **Creates the requisition** — selects items / services from the catalogue, enters details, attaches supporting documents (quotes, justifications). 2. **Submits** — the workflow engages. 3. **Tracks** the requisition's status as it moves through approval. 4. **Receives notification** when approved (or rejected with reason). ## The approval workflow F&O's workflow engine routes the requisition: - **Manager approval** — first line, the requester's direct manager. - **Budget check** — does the requested amount fit within the cost-centre's available budget? - **Procurement category approval** — different category-specific approvers (IT requisitions to IT lead, HR requisitions to HR lead). - **Threshold-based escalation** — over €10,000 requires director; over €50,000 requires VP; over €100,000 requires CFO. - **Compliance review** — for specific scenarios (contractor engagements need legal review). The exact routing is configured per organisation; F&O's workflow engine accommodates substantial complexity. **Approval responses.** - **Approve** — moves to the next step or, if final, marks requisition approved. - **Reject** — requester is notified; requisition can be re-submitted with changes. - **Request change** — the approver asks for modifications before approving. - **Delegate** — pass to a substitute approver. - **Recall** — the requester withdraws their request. Each action is logged with timestamp, comments. ## Budget control integration For organisations using **budget control** (mandatory in public sector, common in cost-controlled commercial operations): - The requisition's projected expense reserves budget on submission (pre-encumbrance). - Approved requisition converts pre-encumbrance to encumbrance. - The encumbrance commits budget against the cost centre. If submitting a requisition would exceed available budget, the workflow either blocks (hard-stop) or warns (soft, requires override). Public Sector configurations typically run hard-stop. ## Procurement category management Spend is classified into **procurement categories** — a hierarchical taxonomy: - IT > Software > SaaS subscriptions. - IT > Hardware > Laptops. - HR > Recruitment > Headhunter fees. - Marketing > Events > Sponsorships. Categories drive: - Approval routing — different categories to different approvers. - Catalog visibility — what items / services requesters can see. - Reporting — spend analysis by category. - Sourcing policy — preferred-vendor rules per category. ## Vendor management Approved requisitions can be sourced from: - **Preferred vendors** — pre-qualified with negotiated pricing. Default for many categories. - **New vendors** — requires vendor onboarding workflow first (financial, compliance, regulatory checks). - **Punch-out catalogues** — for commodity items, requesters browse external vendor catalogues (Amazon Business, vendor-specific portals) with prices and details flowing back into F&O. ## Conversion to purchase order Once a requisition is approved, the procurement team: - **Manually converts** — reviews and creates the PO. - **Auto-converts** — for low-value, low-risk categories, the system auto-creates the PO without manual intervention. - **Combines requisitions** — multiple small requisitions for the same vendor can combine into one PO. The PO becomes the formal commitment to the vendor. **Procurement controls beyond requisitions.** - **Three-way matching** — at invoice posting, F&O matches the invoice to the PO and the receipt; mismatches require explicit override. - **Contract compliance** — POs reference framework contracts; pricing pulls from agreed rates. - **Receiver reporting** — once goods arrive, they're received against the PO; this triggers accruals. **Reporting.** - **Open requisitions** — pending approval per stage. - **Approved-but-not-converted** — requisitions waiting for procurement. - **Spend by category** — analytical view of procurement activity. - **Average approval cycle time** — workflow performance. - **Off-contract spend** — requisitions sourced outside preferred vendors. **Common pitfalls.** - **Approval workflow too complex** — every step requires sign-off; requisitions take weeks. - **Insufficient category structure** — everything is "Other"; reporting is useless. - **No conversion automation** — every requisition manually converted; procurement is a bottleneck. - **Catalogue out of date** — requesters can't find what they need; raise ad-hoc requisitions. ## Operational reality Mature procurement processes route the bulk of spend through structured requisitions; only true emergencies bypass. The discipline produces visibility, control, and cost savings — usually several percent of total procurement spend. --- # Quality management in Dynamics 365 SCM How F&O's quality management module handles inspection plans, quality orders, nonconformance, and the link from quality data to operational decisions. Source: https://www.solvingdynamics365.com/guides/quality-management-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 For regulated industries (food, pharma, medical devices) and quality-sensitive operations (automotive, electronics), F&O's **Quality Management** module captures the inspection and nonconformance workflows that determine whether incoming, in-process, and outbound material can be used. Done right, it ties directly into operational decisions — block, release, rework, scrap. **Core entities.** - **Test** — a specific measurement (dimensional, chemical, visual). - **Test group** — a collection of tests applied together. - **Quality association** — defines when a quality order is auto-created (e.g. on receipt of items in this group from these vendors). - **Quality order** — the actual inspection record, with results per test, disposition, and follow-up actions. - **Nonconformance** — a captured defect with root cause analysis fields and corrective action. ## Quality associations The auto-creation rules: - **Event** — Purchase receipt, Production reporting as finished, Inventory transaction, Sales picking, etc. - **Reference** — item group, item, vendor, customer, or specific products. - **Sampling plan** — full inspection, percentage, fixed quantity. - **Test group** — which tests to run. Quality association rules are the engine that translates "we always inspect first lot from any new vendor" into automatic quality orders without operator decision. **Sampling plans.** - **100%** — every unit. - **Quantity per lot** — fixed sample size. - **Percentage** — proportional sample. - **Acceptance sampling (AQL)** — statistical sampling per ISO 2859 or military standards. The right plan depends on test cost and consequence of escape. Visual checks may be 100%; destructive testing is small samples. **The inspection workflow.** 1. Quality association fires; quality order is created. 2. The inspected quantity is segregated to a quarantine warehouse or quarantine bin until disposition. 3. Quality engineer runs the tests, records results per test line. 4. The system evaluates pass/fail per test against limits. 5. Overall disposition is set: **Pass**, **Fail**, **Conditional**. 6. Disposition drives next steps: release to stock, return to vendor, rework, scrap. ## Quarantine integration Items being inspected are typically segregated to a **quarantine warehouse** or **quarantine bin**. Until the quality order is dispositioned, the material is not available for normal operations. The integration is automatic with warehouse-managed receipts: receipt → quarantine, quality order pass → move to normal inventory. ## Nonconformance A failed quality result, or a problem discovered downstream, generates a **nonconformance**: - **Problem type** — internal, customer, vendor. - **Diagnosis** — what was found. - **Cause** — root cause (5 Whys, fishbone analysis fields). - **Operations** — corrective actions taken (rework, scrap, return, accept with deviation). - **Costs** — labour and material costs of the response. Nonconformance records aggregate into supplier scorecards (vendor X has Y nonconformances/quarter) and trend analysis. ## Corrective and preventive actions (CAPA) For regulated industries, nonconformance leads to formal CAPA — actions designed to prevent recurrence. F&O has CAPA fields but for FDA-regulated environments, dedicated CAPA software is often layered on top. ## Certificate of analysis (CoA) Quality results can be printed as a Certificate of Analysis sent to customers with shipments — proof of test results. Configure the report to pull from quality order data, sign off by quality manager, attach to shipping. ## Production integration In manufacturing: - **In-process inspections** — quality orders triggered at specific operations. - **Final inspection** — before reporting production complete. - **Statistical process control** — measurements tracked over time; trends visible. ## Vendor integration Quality data informs vendor management: - **Supplier scorecard** — pass rate, defect rate, response time. - **Vendor approval status** — restricted, approved, preferred. - **Inspection level** — first-article inspection for new items, reduced inspection for proven items. **Common pitfalls.** - **Quality associations too narrow.** Missing items not covered → inspection skipped. - **Tests poorly defined.** Vague test descriptions; results inconsistent across inspectors. - **No quarantine discipline.** Items released to stock before disposition; operational risk. - **Nonconformance not analysed.** Records accumulate, no trend analysis, no CAPA — quality module becomes paperwork. - **CoA out of sync with results.** A CoA prepared at receipt sent later doesn't reflect any retests — process must enforce final result on CoA. ## Operational rhythm Quality data is most valuable when reviewed regularly: weekly nonconformance trends, monthly vendor scorecard reviews, quarterly process capability analysis. The module is a tool for those rhythms — without the rhythm, it's data collection without action. ## When it's not enough Pharma GxP environments often need eQMS systems (Veeva, MasterControl, Tracewise) layered on top for validated audit trails, electronic signatures, and regulatory submission. F&O integrates with these via APIs. The same pattern — F&O handling operational quality data with a specialised system layered on top for the industry's own compliance regime — shows up in [Dynamics 365 for food and beverage](https://www.solvingdynamics365.com/guides/dynamics-365-for-food-and-beverage) (batch traceability and food-safety audits) and [Dynamics 365 for aerospace](https://www.solvingdynamics365.com/guides/dynamics-365-for-aerospace) (AS9100 quality standards and configuration management). --- # Reporting tools in Dynamics 365 Finance The reporting stack in Dynamics 365 Finance — Financial Reporting, electronic reporting, Power BI, and where each one fits. Source: https://www.solvingdynamics365.com/guides/dynamics-365-finance-reporting-tools Section: Finance & SCM / Finance Published: 2026-05-01 Dynamics 365 Finance ships with several reporting tools that overlap on the edges. Picking the right tool for each job is the difference between a clean reporting stack and a sprawl of one-off reports nobody trusts. ## Financial Reporting A row-and-column reporting engine descended from Management Reporter (and FRx before it), built specifically for financial statements: P&L, balance sheet, cash flow, statutory disclosures. Reports are designed in a web UI inside F&O, executed against the GL with full dimension support, and rendered on screen or exported to PDF/Excel. The right tool for management accounts and statutory reporting, period. ## Electronic Reporting (GER) Microsoft's **Globalization Studio / Electronic Reporting** is a configurable, no-code framework for generating structured outputs in fixed formats — XML, JSON, fixed-width — and consuming the same in. It's used for **statutory e-invoicing**, country tax filings, SAF-T exports, payment file generation (SEPA, BACS, ACH), and bank statement imports. ER configurations are sourced from a global repository so customers and partners can share country implementations. ## Power BI Self-service interactive analytics. F&O ships pre-built **Power BI apps** for finance, supply chain, sales, and retail. Customers extend or replace them with their own datasets. Power BI is the right tool for dashboards, exploratory analytics, and any visualisation that goes beyond tabular financial reports. ## Microsoft Fabric and Synapse Link **Synapse Link for Dataverse** and **Microsoft Fabric** stream F&O data into a lakehouse where it can be combined with non-Microsoft sources, transformed with notebooks, and consumed by Power BI or other tools. The right pattern when reporting needs F&O data joined with non-Dynamics data, or when transformations exceed what Power BI's model can do directly. ## SSRS reports The legacy **SQL Server Reporting Services** reports inside F&O (invoices, packing slips, statements) still exist. They're typically used for transactional documents printed and emailed at posting time. Customisation of standard SSRS reports is done in Visual Studio. ## Where it stops Workforce analytics, complex consolidation reporting, and demand sensing usually combine **Power BI + Fabric + an analytical model** rather than relying on F&O's built-in tools alone. Treat F&O's built-ins as the source of truth and Fabric/Power BI as the analytical surface. ## Practical guidance Statutory financials → Financial Reporting. Country filings → Electronic Reporting. Operational dashboards → Power BI. Customer documents → SSRS. Cross-system analytics → Fabric. --- # Retail channel data management in Dynamics 365 Commerce How D365 Commerce manages data flows between HQ and channels — channel databases, sync jobs, distribution schedules, and operational reliability. Source: https://www.solvingdynamics365.com/guides/retail-channel-data-management Section: Finance & SCM / Retail & commerce Published: 2026-05-01 In Dynamics 365 Commerce, **channel data management** is the discipline of keeping store, POS, and online channels synchronised with the headquarters (F&O) master data and transactional records. The architecture is distributed; each channel has its own database; data flows in defined patterns. Mastering this is essential for any Commerce deployment. **The architecture refresher.** - **HQ** — F&O instance with master data and consolidated reporting. - **Commerce Scale Unit (CSU)** — cloud (or on-premise) mediator. - **Channel database** — per-store (or per-pool); local data store. - **POS / online clients** — access channel database. Data flows: master from HQ → CSU → channel; transactions from channel → CSU → HQ. **What flows from HQ to channels.** - **Products and prices** — current catalog. - **Customers** — customer master. - **Employees** — store associates with their permissions. - **Tax rates and tax groups.** - **Channels and store configurations.** - **Promotions and discounts.** - **Loyalty programs and customer balances.** - **Currency and exchange rates.** Each data type has its own sync job. ## Distribution schedules Per-data-type schedules: - **1010 (Channel configuration)** — infrequent. - **1020 (Customer)** — every few hours. - **1040 (Discounts)** — frequent (promotions change often). - **1050 (Loyalty)** — frequent. - **1070 (Tax)** — moderate. - **1090 (Bar codes)** — infrequent. The schedule configured per job; frequencies tuned to data volatility. **What flows from channels to HQ.** - **Sales transactions** — every sale. - **Tender entries** — payment details. - **Inventory movements** — receipts, transfers. - **Customer additions** — new customers created at store. - **Audit events** — operator activities. The **P-job (1090 transaction collection)** pulls transactional data from CSU to HQ. **Pull vs push.** - **Push** — HQ initiates; sends to CSU; CSU stores; channel pulls when online. - **Pull** — channel asks CSU; CSU asks HQ. Most flows are push (HQ to channel). Transactional flow is pull-based (channel to CSU, then HQ pulls from CSU). ## Real-time service (RTS) Some operations need real-time HQ: - **Customer lookup** — current balance. - **Inventory check** — real-time stock. - **Order status** — cross-channel. RTS bypasses the channel DB for live HQ queries. Slower than channel DB but always current. **Offline mode resilience.** - Channel DB has enough data for autonomous operation. - Lost connection to CSU → channel runs from local DB. - Transactions captured locally. - Reconnection → transactions sync up. The offline pattern is critical for retail uptime. ## Job execution Sync jobs in F&O batch processing: - **Job groups** — bundle related jobs. - **Schedule** — cron-like. - **Logging** — job execution history. - **Error handling** — retry on failure. Most stores have specific job groups they participate in. ## Initial download / channel reload When a channel is first set up: - Bulk download of all required data. - Can take hours for large catalogs. - Subsequent updates incremental. For a new store, initial reload is a planned event. **Common scenarios.** - **New product added at HQ** — distribution job runs; appears in channel after few minutes. - **Promotion activated** — distribution to all stores within configured frequency. - **Price changed** — same. - **Customer makes purchase** — captured at POS; transferred via P-job to HQ. - **HQ receives the transaction** — posts customer ledger, item ledger, financial entries. **Latency considerations.** - Master data → channel: minutes to hours depending on job. - Channel → HQ: minutes via P-job. - Online → channel: real-time-ish. - Real-time queries (RTS): seconds. For end customers, "current" data within minutes is usually acceptable; not all data is real-time. **Common pitfalls.** - **Job schedule too infrequent.** Prices change but stores see old prices for hours. - **Channel DB drift.** Manual changes at channel diverge from HQ; resolution painful. - **Failed jobs unnoticed.** Sync stops; data stale; customers see wrong prices. - **P-job backlog.** Channel-to-HQ flow stalls; transactions accumulate. - **Initial load takes too long.** Storeopen delayed. - **Wrong channel configuration.** Store has wrong job groups; missing data. **Monitoring.** - **Job execution dashboard** — last run, success / failure. - **Channel database state** — heartbeat from each channel. - **Transaction backlog** — pending sync. - **RTS availability** — uptime metric. Without monitoring, sync issues surface as user-reported problems hours or days late. **Performance considerations.** - **Heavy product catalogs** stress sync — design with locale / channel filtering. - **Frequent promotion changes** drive heavy job traffic. - **Channel database size** — for large catalogs, channel DB can be large; SSD recommended. **Operational rhythm.** - **Daily** — monitor sync health. - **Weekly** — review failed jobs; fix root causes. - **Monthly** — review job schedule appropriateness. - **At store open** — verify channel data fresh. ## Strategic positioning Channel data management is the operational core of D365 Commerce. The patterns are mature; the discipline is constant. Mature retail operations have dashboards, alerts, and runbooks for sync issues. The investment in setup and monitoring pays back continuously through smooth store operations and accurate cross-channel commerce. Skip this and the operations suffer in subtle, customer-visible ways — old prices, stale promotions, missed loyalty. --- # Retail loyalty programs — a deep dive How D365 Commerce models loyalty — schemes, tiers, points, rewards, redemption, and the integration across channels for unified loyalty experience. Source: https://www.solvingdynamics365.com/guides/retail-loyalty-program-deep-dive Section: Finance & SCM / Retail & commerce Published: 2026-05-01 Loyalty programs are central to modern retail strategy — driving repeat purchases, increasing basket size, capturing customer identity for marketing. **Dynamics 365 Commerce** has a flexible loyalty engine supporting tiered programs, multi-currency points, partner redemptions, and unified cross-channel experience. Implementing it well requires understanding both the configuration and the operational details. **Core loyalty entities.** - **Loyalty Program** — the named program (e.g., "VIP Rewards"). - **Loyalty Schemes** — earning rules. - **Loyalty Tiers** — Silver / Gold / Platinum levels. - **Reward Points** — the points/currency earned. - **Loyalty Card** — customer's identifier in the program. - **Loyalty Customer** — customer participating. ## Earning rules Configurable schemes: - **Points per dollar** — 1 point per $1 spent. - **Tier-based earning** — Gold members earn 2× points. - **Category-based** — bonus points on specific products / categories. - **Promotional periods** — temporary multipliers. - **Birthday bonus** — extra points on customer birthday month. - **Sign-up bonus** — initial points for joining. Each scheme has criteria (channel, product, customer attribute) and a points formula. ## Tiers Status levels: - Tier qualification — typically annual spend or points threshold. - Tier benefits — earning rate, access to exclusive products, free services. - Tier maintenance — minimum activity to retain status. - Tier expiration — points expire if customer inactive. Tiers create aspirational dynamics — customers strive for next tier. ## Redemption How points become rewards: - **Discount at POS** — points reduce purchase price. - **Free items** — redeem points for specific products. - **Tier upgrades** — temporary higher tier. - **Partner rewards** — points redeemed at partner vendors. - **Charitable donation** — points converted to charity. The redemption catalog is configurable; rewards added and removed seasonally. ## Cross-channel Loyalty must work seamlessly: - **Store POS** — earn and redeem at register. - **Online** — at e-commerce checkout. - **Mobile app** — track points, browse rewards. - **Call center** — agent applies points. D365 Commerce's channel architecture ensures loyalty state synchronises across channels. ## Loyalty card Identifies the customer: - Physical card with number / barcode. - Mobile app digital card. - Phone number / email as identifier. At POS, scan card → loyalty profile loaded → earn / redeem applied. ## Anonymous customers Pre-registered customers: - Earn points to a temporary card. - Activate by registering later. - Points carry over. Captures customer identity from non-loyalty members. ## Promotions and loyalty interaction Loyalty earning often interacts with promotions: - Promotion gives discount; do customers earn points on pre- or post-discount price? - Configurable per scheme. - Best practice: earn on post-discount; customers grumble otherwise. ## Multi-program A customer can be in multiple programs: - Standard rewards program. - Premium credit-card-linked program. - Partner programs. Each program has its own points; customer sees combined. **Points expiration.** - **Rolling expiration** — points expire 12 months after earning. - **Annual cycle expiration** — points expire at year-end. - **Tier-dependent expiration** — higher tiers get longer expiration. Expiration drives engagement but frustrates if too aggressive. ## Reward catalog Items / discounts customers can redeem: - Stocked items with point prices. - Vouchers (10% off). - Experiences (free coffee, free shipping). - Charity options. Catalog management is operational work — keeping rewards fresh and aspirational. **Reporting and analytics.** - **Active loyalty members** — engaged in last 90 days. - **Tier distribution** — % at each tier. - **Points liability** — outstanding points × redemption value (a balance sheet item). - **Redemption rate** — % of earned points redeemed. - **Lift analysis** — loyalty members vs non-members spend. These metrics drive program design decisions. ## Integration with Customer Insights Loyalty data flows to Customer Insights: - Profile enriched with loyalty status. - Segments by tier, by activity. - Journey orchestration triggered by loyalty events (tier upgrade, points expiring). The combination of Commerce + Customer Insights produces personalised loyalty marketing. **B2C considerations.** - **GDPR compliance** — loyalty data is personal data. - **Right to forget** — anonymise loyalty history on request. - **Consent** — explicit opt-in. **Common pitfalls.** - **Overcomplicated tier structure.** Too many tiers; customers confused. - **Reward catalog stale.** Same rewards for years; engagement drops. - **Points liability ignored.** Significant balance sheet item; financial reporting must account. - **Cross-channel sync fails.** Customer earns online but POS doesn't see it; frustration. - **Tier requalification surprises.** Customer drops tier unexpectedly; complaints. - **Promotion / loyalty interaction unclear.** Earning rate ambiguous; trust eroded. **Operational rhythm.** - **Daily** — monitor for anomalies (point gaming, fraud). - **Monthly** — segment analysis, marketing campaigns. - **Quarterly** — catalog refresh. - **Annual** — tier recalibration; expiration runs. ## Strategic positioning Loyalty is one of retail's strongest competitive tools when done well. D365 Commerce's loyalty engine is configurable and capable; the design (tier structure, earning rules, rewards) matters more than the underlying mechanics. Invest in research before launching: customer preferences, competitive benchmarks, financial modelling of liability. A well-designed program drives material revenue uplift; a poorly designed one frustrates customers and produces a balance sheet headache without commercial benefit. --- # Sales and purchase agreements in F&O How Dynamics 365 Supply Chain handles sales and purchase agreements — commitments, releases, fulfilment tracking, and the integration with planning. Source: https://www.solvingdynamics365.com/guides/sales-and-purchase-agreements-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 **Sales agreements** and **purchase agreements** in Dynamics 365 Supply Chain Management are the formal mechanism for long-term commitments between two parties — frame agreements where a quantity, period, and price are fixed, and individual orders are "released" against them over time. They replace the older Business Central concept of *blanket orders* with a richer commitment model. ## The shape of an agreement A **sales agreement** is a parent record carrying: - **Customer** — who's committing to buy. - **Effective period** — start and end dates of the commitment. - **Default fields** — payment terms, delivery terms, currency, etc. - **Lines** — what's being committed to: - **Product Quantity Commitment** — "buy 1000 units of Product A over the period". - **Product Value Commitment** — "buy €100,000 worth of Product A". - **Product Category Quantity Commitment** — quantity across a category. - **Product Category Value Commitment** — value across a category. - **Value Commitment** — overall value across all products. **Purchase agreements** mirror the structure on the procurement side. ## Releases Against an agreement, **release orders** are created — standard sales orders (or purchase orders) referencing the agreement. Each release decrements the agreement's remaining quantity or value. The system enforces: - Cannot release more than the committed amount. - Cannot release outside the effective period. - Pricing comes from the agreement (overriding the customer's standard price list). - Other terms (payment, delivery) default from the agreement. ## Fulfilment tracking The agreement view shows progress: committed, released, delivered, invoiced, remaining. Visibility for both sides: - The customer-facing salesperson knows how much of the customer's commitment is still to release. - The supply-chain side plans against the *expected* releases, not against ad-hoc orders. ## Integration with planning Master planning honours sales agreements — the planning engine can forecast against open agreement quantities, ensuring supply is in place to meet the commitment. The forecast pattern: if the customer committed to 1000 units over the year, the planner expects ~250 per quarter and pre-positions supply. ## Purchase-side mirror Purchase agreements work the same. A frame deal with a key supplier — "we'll buy 50,000 units of raw material A this year at €5/unit" — creates a purchase agreement; individual purchase orders release against it; supplier price honoured for the duration regardless of market movement. ## Pricing Agreement pricing can be: - **Fixed** — the agreed price holds for the duration. - **Discount %** — discount off the standard price list at release time. - **Markup %** — for cost-plus arrangements. - **Tiered** — different prices at different volume bands within the commitment. ## Renewals Agreements expire on the end date. Renewal workflows in Power Automate can prompt the salesperson 30/60/90 days before expiry to negotiate the next year's commitment. ## Reporting Sales agreement reports: - **Customer commitment summary** — what every customer is committed to. - **Fulfilment progress** — % consumed across active agreements. - **At-risk agreements** — agreements where the customer hasn't released enough to consume the commitment, suggesting expiry without full delivery. - **Pricing analysis** — actual vs committed price across the portfolio. **Common pitfalls.** - **Agreements that drift** — released against but never tracked to closure; expire silently. - **Pricing misalignment** — agreement price changed after creation; some releases at old price, some at new. - **Multi-currency complications** — agreement in customer currency but cost in supplier currency; FX swings between commitment and fulfilment. ## Operational reality Agreements demand discipline — formal commitment management, active tracking, scheduled renewals. The reward is predictable revenue and supply, and tighter customer/supplier relationships. The cost is the operational discipline; ignored, the agreements become bureaucratic noise. --- # Sales tax setup in Dynamics 365 Finance How to configure US-style sales tax in F&O — tax authorities, tax codes, tax groups, item tax groups, and the integration with Avalara / Vertex. Source: https://www.solvingdynamics365.com/guides/sales-tax-setup-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 Updated: 2026-09-06 US-style **sales tax** is fundamentally different from European-style VAT. Where VAT is harmonised across countries with standard rates, sales tax in the US is fragmented — 45 states, thousands of local jurisdictions (county, city, special districts), each with their own rates, taxable categories, and exemptions. Dynamics 365 Finance supports US sales tax natively and integrates with **Avalara** and **Vertex** for the deep complexity most US operations face. ## The F&O native engine The native sales tax engine works through: - **Sales tax authorities** — the regulator (state, county, city). Each has a tax-payment recipient configured. - **Tax codes** — specific rates for specific authorities. e.g. NY State 4%, NYC City 4.5%, NY MCTD 0.375%. - **Tax groups** — bundles of tax codes that combine for a given customer / location. A New York City customer gets the NY State + NYC + MCTD group. - **Item sales tax groups** — bundles of tax codes that apply to a given item. Most goods are taxable; some (groceries, prescription drugs in many states) are exempt. - **Intersection** — the customer's tax group × the item's item tax group = which tax codes actually apply. - **Settlement periods** — when each authority's tax is settled and remitted. ## The challenge of US sales tax Sourcing — which jurisdiction applies — depends on whether the state uses **origin-based** sourcing (where the seller is located) or **destination-based** sourcing (where the customer receives). Most states are destination-based; this means a single seller must compute tax based on the customer's address, with potential exposure across thousands of jurisdictions. ## Nexus A seller has **tax nexus** in a state — and must collect tax there — if they have physical presence, economic presence (revenue / transaction thresholds, post-**South Dakota v Wayfair** 2018), or specific business activities. Determining nexus is a tax-advisory question; F&O collects tax in jurisdictions configured to be in scope. ## Why Avalara / Vertex The native engine handles tax computation if you maintain the rates and rules manually. For a seller selling into 5 states with 10 jurisdictions, manual maintenance is feasible. For a seller selling nationwide, with rates that change frequently, with product-specific taxability rules, and with exemption certificate management — manual maintenance is infeasible. **Avalara** and **Vertex** are tax-engine SaaS platforms that maintain the rates / rules and provide API-level tax computation. **The integration pattern with Avalara / Vertex.** 1. F&O has a configured Avalara / Vertex connector. 2. At sales-order creation (and re-validation at posting), F&O calls Avalara / Vertex with the transaction details: ship-to address, ship-from address, products, customer category, exemption certificate ID. 3. Avalara / Vertex returns the tax computation: which authorities, which rates, which exemptions, total tax. 4. F&O stores the tax computation on the transaction. 5. At posting, the tax posts to the standard sales tax accounts but with the Avalara / Vertex breakdown. 6. Periodic returns: Avalara / Vertex can file directly to authorities (Avalara Returns) or provide return-prep data for the seller's tax team. ## Exemption certificates Many B2B transactions are exempt — wholesalers, manufacturers, resellers, non-profits, government. Exemption certificates document the buyer's exempt status. Avalara CertCapture / Vertex Returns / similar tools manage the certificate lifecycle — capture, verification, expiry, renewal, audit. **Special rules.** - **Tax holidays** — states declare temporary exemptions for specific products in specific periods (back-to-school, hurricane preparedness). - **Tax-included pricing** — some B2C scenarios price tax-inclusive; F&O supports though most B2B is tax-exclusive. - **Marketplaces** — sellers via Amazon / eBay / Walmart marketplaces typically have the marketplace collect tax on their behalf; the seller's F&O records the marketplace-collected tax separately. - **Digital goods** — taxability varies wildly by state for digital products and services. ## Compliance and audits US sales tax audits are rigorous. Documentation requirements: - Every taxable transaction with full breakdown. - Every exempt transaction with the supporting certificate. - Periodic returns filed on time per authority. - Reconciliation between collected tax and paid tax. ## Operational reality US-based F&O implementations almost always integrate with Avalara or Vertex. The native engine is functional but isn't built for nationwide US complexity at scale. Plan for the integration from day one. --- # Store operations in Dynamics 365 Commerce How D365 Commerce runs physical store operations — the channel database, offline mode, daily routines, cash management, inventory, and the integration with HQ. Source: https://www.solvingdynamics365.com/guides/dynamics-365-commerce-store-operations Section: Finance & SCM / Retail & commerce Published: 2026-05-01 A retail store needs to keep running when the network drops, the head office is asleep, and the holiday rush hits unexpected volume. **Dynamics 365 Commerce** runs store operations on a distributed architecture — channel databases at each store, replicated transactions to HQ, and POS clients that fall back to offline mode when needed. Understanding the data flow and operational rhythms is essential for any Commerce deployment. **Architecture overview.** - **Headquarters (HQ)** — F&O instance holding master data and consolidated reporting. - **Channel database** — store-level SQL database with the data the store needs. - **Modern POS (MPOS)** — POS application on store terminals. - **Cloud POS** — browser-based version for tablets and back-office PCs. - **Commerce Scale Unit (CSU)** — cloud service or on-premise unit that mediates between POS and HQ. Data flows: master from HQ → CSU → channel DB → POS; transactions from POS → channel DB → CSU → HQ. ## Channel database Per store (or per shared physical network of stores). Holds: - Products and prices effective at that store. - Customer records. - Pending and completed transactions. - Employees and permissions. - Inventory levels. The store can run autonomously against this database when the network is down. ## Offline POS When the connection to CSU drops: - POS continues operating against the channel DB. - Transactions captured locally. - On reconnection, transactions sync to HQ. The threshold for offline behaviour: if CSU is unreachable for N seconds, POS goes offline. Reconnection automatically re-syncs. **Daily store routines.** - **Open store** — first transaction of the day; cash drawer set up. - **Tender declaration** — operator declares starting cash. - **Transactions throughout the day.** - **Shift change** — cashier signs off; new cashier signs on; drawer balanced. - **End-of-day** — final tender declaration; cash reconciliation. - **Close store** — settle drawers, run reports, prepare deposit. Each routine is enforced via store workflow. ## Transactions Beyond standard sale: - **Returns** — with or without original receipt. - **Exchanges.** - **Layaway** — partial payment, hold inventory. - **Special orders** — sell items not in stock. - **Customer orders** — for delivery vs in-store pickup. The POS handles each transaction type with appropriate UI and accounting. ## Inventory at store level Critical question: where's the stock? - **On-hand** — physical at store. - **In transit** — being transferred between stores or from DC. - **Reserved** — customer order or hold. - **Damaged / quarantined.** POS shows real-time on-hand from the channel DB. Replenishment to the store happens via transfers from DCs. ## Cash management Stores handle cash: - **Cash drawer per terminal** — count on open, count on close. - **Float / starting cash** — set at open, reconciled at close. - **Drops** — moving cash to safe during the day. - **Bank deposit** — end-of-day cash to bank. - **Loomis/Brink's pickup** — cash-in-transit handling. Cash reconciliation is a core finance control — discrepancies investigated immediately. ## Pricing and promotions Real-time pricing engine at POS: - **List price** from product master. - **Trade agreements** — store-specific pricing. - **Promotions** — active promo applied automatically. - **Discount overrides** — manager-approved overrides. - **Loyalty rewards** — points applied. Promotions and pricing fully cached in the channel DB so they work offline. ## Loyalty Loyalty data: - **Customer profile** with loyalty card. - **Points balance.** - **Tier status.** - **Rewards earned.** At POS, scanning the loyalty card pulls profile; points earned and burned in transactions. **Returns processing.** - **With receipt** — easy; identify original transaction. - **Without receipt** — manager approval; refund to gift card or store credit; restocking inspection. - **Damaged returns** — additional processes for quality assessment. - **Cross-channel** — online purchase returned at store; "endless aisle." The return policy is configurable; system enforces. **Workforce management.** - **Schedules** — store managers schedule employees. - **Clock in/out** — at POS or dedicated time clock. - **Hours tracking** — for payroll. - **Compliance** — break requirements, minor work restrictions. Integration with HR for employee master; with payroll for hours. **End-of-day procedures.** 1. Final transactions of the day completed. 2. Each cashier counts down drawer; variance recorded. 3. Manager reviews and approves variances. 4. Final reports printed (sales summary, tender, refunds). 5. Cash deposited or secured. 6. Channel DB syncs to HQ. This is a 30–60 minute routine per store, often a frustration point if the system is slow. **Common pitfalls.** - **CSU connectivity flakey.** Frequent offline-mode transitions; data sync issues; reconciliation problems. - **Channel DB drift.** Master data not syncing from HQ; store sees wrong prices. - **Cash variance ignored.** Small daily variances accepted; over months become significant. - **Offline transactions stuck.** Some transactions not syncing back when online; investigation needed. - **Performance issues at POS.** Hardware aging; transactions slow; checkout queues form. - **Wrong tax rates.** Tax configuration off; charges incorrect; reconciliation pain at month end. ## Operational rhythm Daily open/close routines per store; daily sync to HQ; weekly inventory adjustments; monthly cycle counts; monthly P&L per store. Mature retail operations have well-defined runbooks and clear ownership of each routine. ## Strategic positioning Retail store operations are the front line of customer experience. Reliability matters — a POS that crashes during checkout loses sales and frustrates customers. The distributed architecture of Commerce is designed for resilience, but it requires attention to ensure each store stays in sync with HQ and that offline-mode transitions are seamless. Investment in store-level operations (training, hardware, network) pays back directly in customer satisfaction and revenue. --- # Subscription billing in Dynamics 365 Finance Microsoft's Subscription Billing module — recurring contracts, revenue recognition, billing schedules, and where it fits in the F&O stack. Source: https://www.solvingdynamics365.com/guides/dynamics-365-finance-subscription-billing Section: Finance & SCM / Finance Published: 2026-05-01 **Subscription Billing** is a relatively recent addition to Dynamics 365 Finance, built to handle the recurring-revenue, contract-driven business models that are now common across software, telecoms, equipment-as-a-service, and B2B services. It replaces a long history of customer-built workarounds for handling subscriptions in AX/F&O. ## Three integrated components Subscription Billing combines three working units: 1. **Recurring Contract Billing** — manages contracts, billing schedules, mid-term changes (add/remove products, prorations, upgrades/downgrades), and renewals. 2. **Revenue and Expense Deferrals** — manages straight-line and milestone deferrals of revenue or expense across periods, automating the journals. 3. **Multiple Element Allocations** — handles the ASC 606 / IFRS 15 problem of allocating contract revenue across performance obligations when a contract bundles multiple products or services. ## Contracts A subscription contract holds the customer, term, billing cadence, products, prices, discounts, and any special clauses. Contracts can be billed monthly, quarterly, annually, on milestones, or on usage. Mid-term changes (adding a seat, upgrading a tier, partial cancellation) prorate automatically. ## Revenue recognition Revenue recognition is decoupled from billing — invoicing a customer for an annual contract doesn't recognise twelve months of revenue at once. The deferral component spreads revenue across the contract period to comply with accounting standards. Performance-obligation-based recognition handles bundled contracts. ## Usage billing For consumption-based components, usage data feeds Subscription Billing through a Data Management interface or an API, where it's priced and billed alongside the recurring component on the same invoice. ## Pricing Tiered pricing, volume discounts, ramp-ups, and prepaid balances are all configurable without custom code. ## Integration with the rest of F&O Subscription Billing posts to the standard AR sub-ledger, so customer balances, payments, and statements work as normal. Revenue recognition entries land in the GL with deferred-revenue control accounts and recognised-revenue accounts mapped by product. ## Reporting ARR (annual recurring revenue), MRR (monthly recurring revenue), churn, contract value, and waterfall reports are produced via Power BI templates that ship with the module. ## Where it doesn't fit Very high-volume B2C subscriptions (tens of millions of subscribers) typically sit better with a dedicated subscription platform (Stripe Billing, Zuora) that feeds F&O the financial summary. For B2B subscription businesses up to mid-market, Subscription Billing is increasingly the right answer in-product. --- # The Cash Management module in Dynamics 365 Finance How F&O's Cash Management handles cash positions, bank reconciliation, payment processing, and cash flow forecasting at enterprise scale. Source: https://www.solvingdynamics365.com/guides/cash-management-module-in-f-and-o Section: Finance & SCM / Finance Published: 2026-06-14 For enterprise finance teams, **cash management** is daily operational work — knowing the current bank balance across many accounts, forecasting near-term liquidity, reconciling bank statements, processing payments, managing FX exposure. Dynamics 365 Finance's **Cash and Bank Management** module covers the operational layer. ## Bank accounts Each bank account is a master record with: - **Identifier** — account number, routing details, IBAN, SWIFT/BIC. - **Currency** — the account's base currency. - **Bank** — the financial institution. - **Type** — operating, savings, escrow, payroll, intercompany. - **Posting profile** — GL accounts for bank activity. - **Bank statement format** — for import (camt.053, MT940, BAI2, country-specific). - **Payment file formats** — for outbound payment generation. - **Approval thresholds** — for payment authorisation. Multi-currency operations have multiple bank accounts per currency; multi-entity groups have many bank accounts per entity. ## Bank statement import Daily or weekly: - **Live bank feeds** — partner connectors (Yodlee, Token, country-specific bank-feed services) automate import. - **MT940 / camt.053** — uploaded files for banks supporting standard SWIFT or ISO 20022 formats. - **CSV / custom formats** — bank-specific exports with mapping configuration. The imported statement lines feed into reconciliation. ## Bank reconciliation Reconciling F&O's bank account ledger against the bank statement: 1. Import the statement. 2. Auto-match statement lines to bank ledger entries by amount, date, reference. 3. Manual match unmatched lines. 4. Post journal entries for items only the bank knows about — fees, interest, direct debits, returned items. 5. Reconcile balance differences. 6. Post the reconciliation; bank ledger entries marked closed. AI-assisted matching (Copilot) suggests matches for ambiguous lines; the user accepts, modifies, or rejects. ## Payment processing Outbound payments to vendors / employees / others through: - **Payment proposals** — system identifies vendor invoices due for payment, proposes a payment batch. - **User review** — adjust amounts, exclude entries, override priorities. - **Bank file generation** — SEPA pain.001, Bacs, ACH NACHA, Bankgirot (SE), country-specific formats. - **Posting** — payment journal posts; vendor ledger settled; bank ledger reduced. - **Bank approval workflows** — many banks require dual-approval for high-value payments; F&O integrates with bank workflow. ## Inbound payments Customer payments arrive through: - **Bank feed** — incoming credits identified and applied. - **Manual entry** — for receipts not yet on the bank statement. - **Direct debit reversal** — failed direct debits returned to open AR. - **Lockbox** — for organisations with bank-provided customer-payment lockbox services, automated import. ## Cash flow forecast F&O's cash flow forecast considers all liquidity signals: - **Opening bank balances** — across all accounts in all currencies. - **Receivables** — open AR with due dates. - **Payables** — open AP with due dates. - **Sales orders** — open with planned shipment / invoice dates. - **Purchase orders** — open with planned receipt / invoice dates. - **Service contracts** — recurring revenue commitments. - **Capital projects** — planned cash outflows. - **Loan repayments and interest** — recurring debt servicing. - **Tax accruals** — periodic tax payments. The forecast aggregates per period (daily near-term, weekly medium-term, monthly long-term), per currency, per entity. Power BI templates visualise. ## FX exposure For multi-currency operations: - **Position per currency** — net exposure across all accounts. - **Open forex contracts** — hedges in place. - **Period-end revaluation** — translate foreign-currency balances at period-end rates, post FX gain / loss. - **Realised FX** — when foreign-currency invoices settle at different rates from booking. For sophisticated treasury operations (hedging strategy, FX optionality, intra-day position management), customers integrate a dedicated treasury platform alongside F&O. ## Intercompany cash management Multi-entity groups have inter-company cash flows — entity A funds entity B's working capital, intra-group loans, central treasury sweep. F&O supports: - **Centralised payments** — entity A pays vendor invoices for entity B; IC accounting reconciles. - **IC cash transfers** — programmatic moves between entities. - **Pooling structures** — for groups with notional or physical cash pooling. **Reporting.** - **Cash position dashboard** — current balance per account, total, by currency. - **Daily / weekly cash forecast.** - **Bank reconciliation status** — which accounts reconciled, which behind. - **FX exposure summary.** - **Treasury KPIs** — DSO, DPO, working capital metrics. **Common pitfalls.** - **Bank feeds not configured** — daily reconciliation work is manual. - **Payment file format mismatched to bank** — payments rejected; vendor relationships strained. - **Stale reconciliations** — accumulating unreconciled items become harder to investigate. ## Operational reality Cash management discipline drives working capital efficiency. Modern enterprise F&O implementations integrate live bank feeds, run daily reconciliation, and feed forecasts that the CFO actually trusts. --- # The Cost Accounting module in Dynamics 365 Finance How Cost Accounting differs from financial accounting in F&O — cost objects, allocation hierarchies, statistical dimensions, and management reporting. Source: https://www.solvingdynamics365.com/guides/the-cost-accounting-module-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 **Cost Accounting** in Dynamics 365 Finance is a separate, parallel ledger purpose-built for management accounting — operating cost allocation, profitability analysis by product / customer / region, and the analytical reporting that financial accounting on its own can't deliver cleanly. It's one of the most underused modules in F&O and one of the most powerful when adopted. ## Why a separate ledger Financial accounting answers external questions — statutory P&L and balance sheet for tax authorities, auditors, regulators. Cost accounting answers internal questions — which products are profitable, which customers cost too much to serve, which cost centres run efficiently. These two views need different rules: - **Cost reallocation across periods** — match operational costs to the periods they actually drove value, not just when the invoice posted. - **Different cost hierarchies** — financial sees by GL account; management sees by product category or customer segment. - **Cost allocation across cost objects** — IT cost shared across departments; marketing cost allocated to product lines. - **Imputed costs** — opportunity cost, depreciation by management methodology, deemed cost of capital. Forcing all of this into the financial ledger pollutes statutory accounts. The cost accounting module gives a separate, audit-trailed analytical view. **The cost-accounting data model.** - **Cost element dimension** — the cost categories you analyse (Salary, Travel, Equipment, Utilities, etc.). Map to GL accounts but groupings can differ from the chart of accounts. - **Cost object dimension** — what bears the cost (Cost Centre, Profit Centre, Project, Product, Customer Segment). Can include hierarchical structures. - **Statistical dimensions** — non-monetary measures used to drive allocations (Headcount, Square Metres, Production Units, Machine Hours). ## Source of cost data Cost accounting *consumes* data from financial accounting — GL postings are copied into the cost-accounting ledger periodically. Within cost accounting, the data is transformed and reallocated without changing the source. ## Allocation hierarchies The core of cost accounting: 1. **Primary allocation** — IT cost (in a service cost centre) split across operational cost centres based on a driver like headcount or laptop count. 2. **Secondary allocation** — allocated cost in operational centres further reallocated to product lines, customer segments, or projects. 3. **Tertiary allocation** — cumulative allocation to derive product profitability or customer profitability. Allocations cascade through configurable hierarchies, with full audit of each allocation step. ## Statistical dimensions as drivers Statistical dimensions don't represent money — they represent volume metrics that drive allocation. Headcount drives HR cost; Machine Hours drive production overhead; Square Metres drive facility cost. Values are entered periodically or loaded automatically from operational systems. ## Cost rates Cost rates apply to statistical dimensions to compute imputed cost — e.g. an internal hourly rate for a resource type used for project cost capture. ## Reporting Pre-built cost reports cover: - **Cost statement** — like a management P&L by cost element and cost object. - **Cost analysis** — drill down by hierarchy to find anomalies. - **Cost-centre performance** — actual vs budget, by period. - **Product profitability** — revenue – cost across the cost-accounting view. - **Customer profitability** — same logic at customer or segment level. Power BI templates ship with the module for richer visualisation. ## When to adopt Cost Accounting pays back when: - Cost allocations across cost centres / products / customers are material to decisions. - Management reporting needs cost views that the chart of accounts can't naturally produce. - The organisation has dedicated controllers willing to maintain the configuration. ## When not For small, simple operations where the GL with dimensions answers most management questions, Cost Accounting adds complexity without proportional benefit. Adopt when the gap becomes painful. ## Operational reality Cost Accounting is a configuration-heavy module. Budget a focused implementation (a few weeks for a controller and consultant) and maintain it as ongoing controller work. Done well, it transforms management visibility. --- # The Data Management Framework (DMF) in F&O How F&O's Data Management Framework moves data in and out — data projects, data entities, source/staging/target, recurring integrations. Source: https://www.solvingdynamics365.com/guides/data-management-framework-deep-dive Section: Finance & SCM / Overview & platform Published: 2026-05-01 ### Key facts - F&O ships with roughly 1,800 standard data entities, each exposing a denormalised, canonical view over one or more underlying tables for import, export, and integration. - Every import moves through three stages — source, staging (with field-level validation), and target — and errors at each stage are isolated so failed records can be reprocessed without re-running the full job. - For high-volume recurring integrations, batch APIs are preferred over OData, because OData throttles aggressively under load. - Standard entity import runs at roughly 1,000-10,000 records per minute; set-based processing skips per-record business logic for higher throughput, and large migrations often need individually tuned or partner-extended entities. - Direct-SQL data loading is not a supported pattern on F&O and breaks with platform updates — production integration is expected to run through DMF data entities. The **[Data Management Framework (DMF)](https://www.solvingdynamics365.com/glossary/dmf)** is the structural foundation of every bulk data move in Dynamics 365 Finance and Operations — initial migration, ongoing integrations, exports for reporting, and recurring file-based exchanges. Understanding its core entities (data entities, data projects, staging) is essential for anyone touching F&O integration work. ## Data entities A **data entity** is a denormalised view over one or more F&O tables, exposing a canonical structure suitable for external interchange. F&O ships with ~1,800 standard data entities — `CustomerV3`, `VendorsV2`, `ReleasedProductCreationV2`, `SalesOrderHeaderV4` — covering most master data and most documents. Each entity has: - A **public name** (used in URLs and APIs). - A **target structure** (how it maps to underlying tables). - A **staging table** (intermediate landing area for imports/exports). - A **set of mapping rules** (per source format). ## Data projects A **data project** is a configured import or export job. It contains: - **Source format** — Excel, CSV, XML, ODBC, AX 2012, JSON. - **Entities** — which data entities are in scope. - **Mapping** — how source columns map to entity fields. - **Filters** — what subset of records. - **Sequence** — order of entity processing (matters for FK dependencies). Projects are reusable: build once, run repeatedly. Each execution becomes a **job**. ## Source → Staging → Target The import flow is three-stage: 1. **Source** — the input file or feed. 2. **Staging** — the data entity's staging table; intermediate landing with field-level validation. 3. **Target** — the actual F&O tables; the entity's `insert/update` business logic runs. Errors at each stage are isolated: source parse errors don't corrupt staging; staging validation errors don't corrupt target. Failed records can be reprocessed without re-running the full job. ## Export is the reverse Target tables → staging → source format file or feed. ## Data templates Pre-configured data project sets shipped by Microsoft for common scenarios: - **All customer data** — customers, addresses, contacts, etc. - **All financial data** — chart of accounts, dimensions, opening balances. - **All inventory data** — items, BOMs, routes, prices. Templates are a good starting point; production projects usually need customisation. ## Recurring integrations Beyond manual project execution, F&O supports recurring integrations: - **Recurring data jobs** — pre-configured DMF projects scheduled or triggered. - **OData-based** — REST endpoints for entity-based data access. - **Batch APIs** — bulk data movement via REST. For high-volume recurring integrations, batch APIs are preferred over OData per-record approach — OData throttles aggressively under load. ## Entities vs OData The same data entities serve: - **Batch DMF jobs** — bulk imports/exports via files. - **OData APIs** — record-by-record CRUD operations. - **Custom services** — programmatic invocation. - **Power Platform connectors** — Power Automate / Power Apps use OData behind the scenes. A consistent entity layer means the same logical record type is accessible through multiple channels — Power Apps reads the customer entity; an integration writes via batch DMF; both see the same data structure. ## Composite entities Some data entities aggregate multiple related entities into a single payload (e.g. a sales order with header, lines, charges in one record). Useful when downstream systems prefer one structure per business document. **Entity import performance.** - **Standard entities** — moderate performance; suitable for ~1,000–10,000 records per minute. - **Set-based processing** — high performance; entities marked as set-based skip per-record business logic. - **Bulk import** — entire data sets in dedicated jobs; performance varies by entity complexity. For large migrations (millions of records), entities are tuned individually — some standard entities don't scale and need partner extensions or direct SQL preparation. **Common pitfalls.** - **Mapping errors.** Source column names don't match staging fields; silent data drops or import errors. Test mappings with small samples. - **Dependency ordering.** Loading sales orders before customers exist; FK violations. Always sequence entities respecting dependencies. - **Staging accumulation.** Old staging records not cleaned; performance degrades. Schedule staging cleanup. - **No error handling.** Failed records silently dropped; downstream confusion. Always extract error logs and reconcile. - **Tier 1 testing not representative.** A migration that works in a Tier 1 dev environment may fail in Tier 2 SAT or production due to data volumes and parallel batch contention. Test with production-scale data on Tier 2. **Source format gotchas.** - **CSV** — character encoding (UTF-8 vs ANSI), delimiter handling, embedded commas. - **Excel** — date formats, leading zeros stripped, formula evaluation. - **XML** — schema mismatches. Standardise on UTF-8 CSV or composite entity XML for predictability. ## Operational rule Production data integration on F&O is built on DMF entities. Custom direct-SQL approaches are not supported and break with platform updates. Stay on the standard pattern — use entities, build data projects, schedule recurring jobs, handle errors explicitly. ## Where to go next The entities DMF moves are described in [data entities and DMF](https://www.solvingdynamics365.com/guides/dynamics-365-data-entities-and-dmf); the near-real-time alternative for Dataverse is [dual-write](https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-integration); the orchestration layer many projects put around it is [Azure Data Factory](https://www.solvingdynamics365.com/guides/azure-data-factory-with-dynamics-365). For the project view, [data migration strategy](https://www.solvingdynamics365.com/guides/data-migration-strategy-for-dynamics-365), and for exposing logic rather than data, [custom services and OData in F&O](https://www.solvingdynamics365.com/guides/custom-services-and-odata-in-f-and-o). --- # The Dynamics 365 Finance and SCM security model How role-based security works in Dynamics 365 Finance and SCM — duties, privileges, roles, segregation of duties, and extensible data security. Source: https://www.solvingdynamics365.com/guides/dynamics-365-finance-security-model Section: Finance & SCM / Finance Published: 2026-05-01 Dynamics 365 Finance and Supply Chain use a layered, role-based security model derived from AX 2012. It's powerful, expressive, and considerably more complex than Business Central or the CRM apps. Understanding the hierarchy is essential. **The four layers.** 1. **Privileges** — the lowest level. A privilege grants access (read, create, update, delete, perform action) on one or more *securable objects* — menu items, fields, tables, services, reports. Privileges are the building blocks; Microsoft ships hundreds. 2. **Duties** — a logical group of privileges that together let a user perform a job task: *Maintain customer invoices*, *Approve vendor payments*, *Inquire into ledger balances*. Duties are how you express "this job does these things". 3. **Roles** — a job role assembled from duties: *Accounts Payable Manager* contains *Maintain vendor master*, *Approve vendor invoices*, *Inquire into AP*, etc. Users are assigned to roles. 4. **Process cycles** — the highest level, grouping duties by business process for documentation purposes. Process cycles don't affect runtime security. ## Why the layers This structure lets Microsoft ship roles and customers compose them without rewriting privileges. A customer rarely creates privileges; they assemble duties, occasionally extend roles, and assign users. ## Segregation of duties (SoD) F&O has a built-in **SoD framework**. Administrators declare which pairs of duties are conflicting (e.g. *Maintain vendor master* + *Approve vendor payments*) and the system blocks any role assignment that would violate them, surfacing the conflict for resolution. ## Extensible Data Security (XDS) Beyond menu/object security, **XDS** restricts data at the row level — e.g. "salespeople see only customers in their region". XDS policies are defined as queries on the underlying tables and apply automatically wherever those tables are queried, including in custom reports. ## Organisation hierarchy Most security ties back to the **organisation hierarchy** — legal entities, operating units, departments, cost centres. Roles can be scoped to one or many entities; a user assigned to a role across multiple entities sees consolidated lists where appropriate. ## Effective access tool F&O provides an effective-access tool that, given a user, shows every securable object they can reach and the role chain that granted it. Use it to debug "why can I see/not see this?". ## Practical advice Start from Microsoft's shipped roles, copy them, edit the copies. Define SoD policies early. Don't grant the *System Administrator* role to anyone in production except true admins — it bypasses all security. --- # The Dynamics 365 Finance tax engine How tax calculation works in Dynamics 365 Finance — tax codes, tax groups, item tax groups, the Globalization tax service, and country-specific localizations. Source: https://www.solvingdynamics365.com/guides/the-f-and-o-tax-engine Section: Finance & SCM / Finance Published: 2026-05-01 Tax calculation in Dynamics 365 Finance is one of the more configuration-dense areas of the product. Multi-country operations, complex rate structures, statutory reporting variations, and the recent move toward Microsoft's **Globalization Studio** tax service all demand careful design. ## The classic engine F&O's classic tax engine — descended from AX — works by intersecting two classifications on each transaction line: - **Tax group** — assigned to customer or vendor; defines the tax codes that apply for that trading partner's relationship (domestic VAT, export, EU intra-community, reverse charge, etc.). - **Item tax group** — assigned to item or service; defines the tax codes that apply for what's being sold or bought (standard rated, reduced rated, exempt, etc.). The intersection gives the **tax code** to apply, which carries the rate, the ledger accounts for tax payable and recoverable, and the reporting classification. ## Tax codes and tax periods Tax codes have rates, posting accounts, and validity periods. Multiple rates per code over time (e.g. VAT rate changes) are managed by date-ranged versions. **Tax periods** define VAT/sales-tax return periods with start, end, and status (open / closed / submitted). ## Tax calculation steps When a transaction line is created, the engine: 1. Looks up the trading partner's tax group. 2. Looks up the item's tax group. 3. Finds the intersection in the *tax code on the tax group lines*. 4. Calculates the tax amount (line × rate, with proration for partial line discounts). 5. Posts to the configured tax payable/recoverable accounts. ## Multi-step tax Some jurisdictions require multi-step calculation — e.g. US state tax on top of local tax, or layered VAT-plus-environmental-fee. The classic engine supports this through chained tax codes. ## The Tax Calculation service (Globalization) Microsoft's modern, configurable tax calculation service is built around the **Globalization Studio**. The Tax Calculation service is hosted in Azure, configured per country with electronic-reporting (GER) templates, and called by F&O at transaction time. The service supports: - Complex multi-step calculations beyond the classic engine. - Country-specific rules without hard-coding into F&O. - A configurable rule engine in the Globalization Studio. The new service is the strategic direction; for most established F&O customers, the classic engine remains in use, with migration planned over time. ## Country localizations Country-specific tax reporting (VAT returns, intrastat, SAF-T, real-time invoice reporting in Spain/Italy/Hungary, e-invoicing in Mexico/Brazil, OSS for EU B2C) is delivered either by Microsoft (for the major countries) or by partner ISVs. The Electronic Reporting (GER) engine renders the actual report files; the underlying tax data comes from the calculations described above. ## External tax engines For US sales tax with thousands of jurisdictions, customers integrate **Avalara** or **Vertex** — third-party tax engines that hold up-to-date jurisdiction rules. F&O calls the external service at posting; the result is stored as tax transactions in F&O. **Common pitfalls.** - **Wrong intersection setup.** New customer or item without correct tax-group assignment posts incorrect tax silently. - **Rate change without versioning.** Updating the same tax code in place affects historical transactions on reprint; always version with effective dates. - **Localization without specialist help.** Each country has nuances; rely on an experienced country implementer. --- # The Global Address Book in Dynamics 365 Finance & Operations How the Global Address Book unifies parties across customers, vendors, contacts, and workers in F&O — party types, role assignments. Source: https://www.solvingdynamics365.com/guides/global-address-book-in-f-and-o Section: Finance & SCM / Overview & platform Published: 2026-05-01 A single individual or organisation might be a **customer** for one legal entity, a **vendor** for another, a **business contact** in CRM-style scenarios, and the **employer** of internal **workers**. Without a unifying model, the same party gets recorded multiple times with slight variations, and analytics lose coherence. F&O's **Global Address Book (GAB)** is the cross-legal-entity store that holds parties once and assigns them roles. ## Core entity: Party A **party** in GAB is a person or organisation. Each party has: - **Type** — Person or Organisation. - **Name and address details.** - **Contact information** — phone, email, URLs. - **Identification numbers** — VAT registration, DUNS, government IDs. - **One or more roles** — Customer, Vendor, Contact, Worker, Competitor, Other. A party can hold multiple roles simultaneously: organisation Acme Corp is a Customer in three legal entities and a Vendor in one. Each role is a separate record in the role-specific table (Customer, Vendor) but linked back to the same party. ## Why this matters Reconciling "who's who" across customer master, vendor master, and worker records becomes one query — joining through the party. Master data quality programs operate at party level; data quality fixes propagate to all roles. ## Cross-legal-entity sharing GAB is **enterprise-wide** — one address book across all legal entities in the F&O tenant. A customer created in Legal Entity A can be activated as a customer in Legal Entity B by adding the customer role for that entity, reusing the underlying party. This is a structural advantage F&O has over many ERPs: one global identity, locally activated as needed. ## Address book hierarchy The hierarchy: - **Default global address book** — the single shared book. - **Custom address books** — optional sub-books for specific scopes (e.g. "Legal" address book for in-house counsel use). Most installations use only the default book. Custom books are for unusual segregation requirements. ## Addresses on parties Each party can have multiple **postal addresses**, each with: - **Purposes** — Invoice, Delivery, Statement, Statutory, Multiple. - **Effective from/to dates** — addresses can age in/out. - **Primary flag** — designates the default for a purpose. When a customer record is created, addresses are derived from the party's address book entries — but can be overridden at customer level if needed for that legal entity's relationship. ## Names and translations A party may have: - **Primary name** — the canonical name. - **Translations** — alternative-script names (Chinese, Arabic) for global vendors. - **Alternative names** — DBA, "trading as", historical names. Search across all name variants is supported, useful for finding an organisation whose name has shifted over time. ## Contact persons A **contact** in GAB is a person party linked to an organisation party via a role. This person is "the buyer at Acme" but also exists as a party in their own right — they could later become a vendor contact at a different organisation. Maintaining contacts at party level rather than per-customer-per-LE prevents duplicate contact records. ## Workers and HR Internal employees are also parties. The worker party is linked to an HR worker record (in the HR module) or a project worker (in Project Operations). Same person, different roles. ## Duplicate detection Adding a new party with a name similar to an existing party triggers duplicate warnings. The match algorithm uses name similarity, address proximity, and identifier overlap. Manual review confirms or rejects the duplicate. ## Merge If two parties turn out to be the same: - **Merge function** moves all role assignments to one surviving party. - Transactions, addresses, contacts all redirect. - The merged-away party is marked inactive but retained for audit history. Use with care — merge is hard to undo. ## Integration with Dataverse and CDS When F&O integrates with the Power Platform via **Dual-Write**, the GAB party model maps to Dataverse's Account and Contact tables. The party identifier becomes a key bridging both sides. This dual-write is the underlying plumbing for the unified "Dynamics 365" experience. **Common pitfalls.** - **Creating duplicates in workflow.** Sales rep creates a customer without checking if the party already exists; duplicate party emerges; reconciliation later is painful. - **Address divergence.** Addresses overridden at customer level drift from the party master; cross-LE reporting shows different addresses. - **Forgotten role activation.** A customer exists in LE A; LE B starts trading with the same customer but creates a new party instead of activating the existing one. - **GAB performance at scale.** Very large GAB (millions of parties) can slow address book lookup; index tuning and archiving stale parties helps. - **Merge ambiguity.** Merging two parties where one has high-value historical data; merge logic preserves the surviving party's data — picking the wrong survivor loses history. **Operational disciplines.** - **Master data ownership** — a single team owns party creation across all LEs, with workflow approval and duplicate-check enforcement. - **Periodic dedupe runs** — duplicate detection runs against the full GAB, flagging probable duplicates for review. - **Identifier governance** — VAT numbers, DUNS, government IDs collected and used as primary match keys. ## The unifying value GAB is one of F&O's more architecturally interesting features — a global identity model that few competitors match. The implementation upside (data quality, cross-LE analytics, integration simplicity) only materialises with master data discipline; without it, GAB becomes another store of duplicates. --- # The Landed Cost module in Dynamics 365 SCM How the Landed Cost module captures the true cost of imported goods — voyages, shipping containers, charges, allocation methods. Source: https://www.solvingdynamics365.com/guides/landed-cost-module-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 For companies importing goods internationally, the purchase price is only part of the cost. Freight, insurance, duties, brokerage, port charges, and inland transportation add 10–30% to the unit cost — and that "landed cost" is what should appear on the inventory valuation, not just the supplier invoice. The **Landed Cost** module in Dynamics 365 SCM models this end-to-end. ## Why a separate module The classic F&O **Misc Charges** mechanism lets you add charges to a purchase order, but it doesn't model: - Multiple shipments converging into one voyage. - Charges incurred against a container, not a single PO. - Cost allocation across many POs and many lines. - Cost-as-of dates differing from invoice posting dates. Landed Cost adds **voyages**, **containers**, and **cost types** as first-class entities that aggregate across purchase orders. **Core entities.** - **Voyage** — a vessel's trip from origin to destination, with a departure and arrival date. - **Container** — a shipping container within a voyage, holding cargo. - **Folio** — a grouping of charges (often per shipment). - **Cost type** — a category of charge (sea freight, insurance, duty, broker fee). - **Cost allocation method** — how a charge is distributed (by weight, volume, value, quantity, equal split). **Workflow.** 1. Purchase orders are created normally. 2. A **shipping container** is created and PO lines assigned to it; the system computes total weight, volume, value per container. 3. The container is added to a **voyage**. 4. Estimated charges are recorded against the voyage or container (sea freight estimate, broker estimate, duty estimate). These flow into estimated landed cost on each PO line. 5. When the goods arrive, the receipt posts at estimated landed cost. 6. Actual invoices arrive over weeks (freight, duty, broker). Each is recorded against the voyage or container as actual charges. 7. Cost adjustment routines reconcile actuals vs estimates and post the variance. ## Allocation methods For each charge, choose: - **By weight** — heavy items absorb more. - **By volume** — voluminous items absorb more. - **By value** — high-value items absorb more. - **By quantity** — flat per unit. - **By equal share** — flat per PO line. The right method per charge type matters: freight is usually weight or volume; insurance is usually value; duty is per-line per-tariff. A landed cost setup that uses one method for everything is naive. ## Estimated vs actual Estimates flow into inventory cost immediately at receipt — without estimates, inventory is valued at supplier price only. When actuals arrive: - **Variance** = actual - estimate per cost type. - **Adjustment routine** processes the variance into existing inventory and COGS for already-sold items. - **Variance accounts** capture systematic over- or under-estimation patterns. ## Duty and customs Country-specific tariff codes and duty rates drive duty calculation. Landed Cost can compute duty per line based on Harmonised System (HS) codes and country of origin, integrating with customs declaration data. For complex customs, partner extensions (Avalara, Vertex landed cost) layer on top. ## Multi-currency Cost types are typically denominated in different currencies — sea freight in USD, broker fees in local. The module handles per-currency conversion at the appropriate rate (charge date, receipt date, or invoice date — configurable). **Reporting.** - **Voyage cost analysis** — total landed cost per voyage, broken down by cost type. - **Container utilisation** — value vs capacity. - **Variance by cost type and supplier** — where estimates routinely miss. This reporting is where landed cost yields ROI — identifying which trade lanes, which freight forwarders, which products consume more cost than expected. ## Integration with inventory cost Landed Cost integrates with the F&O **cost engine**: - Inventory close runs respect landed cost adjustments. - FIFO/Weighted Average calculations use the landed cost, not just supplier price. - COGS at the moment of sale reflects the most current landed cost calculation. **Common pitfalls.** - **Estimates too optimistic.** Persistent under-estimation; variances always negative; finance distrusts the module. - **Allocation method mismatch.** All charges allocated by value; freight on a low-value bulky item is wrong. - **Cost type proliferation.** Dozens of cost types where five would do; reconciliation becomes painful. - **Late actuals.** Invoices arriving months later; inventory has already been sold; adjustments hit COGS unexpectedly. - **Integration with broker spreadsheets.** Broker provides duty in Excel; manual re-keying introduces errors. Build an import process. ## Operational rhythm A monthly landed cost close: confirm all voyages with departures in the month are estimated; reconcile any actuals received; post adjustments. A quarterly variance review identifies systematic estimation issues. ## When to use it If imports are >5% of cost and >20% of inventory by value, Landed Cost pays back. For occasional imports, the simpler Misc Charges approach is sufficient. --- # Tracking dimensions in Dynamics 365 Supply Chain How batch, serial, owner, and licence plate tracking work in F&O — operational impact, traceability, and the trade-offs of each. Source: https://www.solvingdynamics365.com/guides/tracking-dimensions-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 Of the inventory dimensions in Dynamics 365 Supply Chain Management, **tracking dimensions** are the ones that give individual units their distinct identity. Configuring them well — batch on food and pharma, serial on high-value items, licence plate in advanced warehousing — supports the traceability and operational requirements without imposing unnecessary overhead. ## Batch tracking A **batch** (or *lot*) groups units produced or received together — same production run, same supplier delivery, same harvest. Each batch has: - **Batch number** — unique identifier. - **Manufacturing date** — when produced. - **Expiry date** — for perishable items. - **Best-before date** — for food / pharma. - **Batch attributes** — fat %, alcohol %, brix, pH, etc. for process industries. - **Inventory status** — Available, Quarantined, etc. Picking can be **FEFO** (first-expired-first-out) to prioritise oldest stock; reservations can target specific batches. Traceability reports show full history per batch — where it came from, what was made from it, where each unit went. Used in: food, beverage, pharma, chemicals, cosmetics, building materials, paint, lubricants. ## Serial tracking A **serial number** uniquely identifies each individual unit. Each serial has: - **Serial number** — unique identifier. - **Manufacturing date** — when produced. - **Warranty start / end dates** — for service tracking. - **Inventory status**. Every transaction touching the unit references the serial: receipt, transfer, pick, ship, return. The result is full chain-of-custody — given any serial, you can trace exactly where it's been and what's happened to it. Serial tracking has substantial overhead — every scan, every receipt, every pick requires the serial. Reserved for items where it justifies the cost: - High-value items (industrial equipment, vehicles, jewellery). - Compliance-regulated items (medical devices, aerospace components, certain electronics). - Items with warranty obligations. - Items where authenticity matters (luxury goods). ## Owner tracking (consignment) **Owner** is a dimension that tracks who actually owns the inventory — useful for **consignment** scenarios where inventory is physically held but not yet sold: - **Vendor-managed inventory (VMI)** — supplier owns the stock until you consume it. - **Consignment to customer** — you ship stock to a customer's site but it remains yours until the customer uses it. - **Multi-owner shared warehousing** — 3PL operations where one warehouse holds inventory for multiple owners. Owner tracking lets the warehouse manage physical inventory while accounting recognises legal ownership correctly. ## Licence plate (LP) A **licence plate** is a label identifying a physical unit of multiple items — a pallet, a tote, a carton, a shipping container. Operations on the LP cascade to its contents: scan one LP, move 50 items in one action. Licence plates are essential in advanced WMS scenarios: - Receiving where supplier consolidates many items on one pallet. - Cross-docking where shipments transit a warehouse without put-away. - Bulk picking where one LP holds an entire customer order. LPs can nest — a pallet LP contains carton LPs that contain item-level LPs. Operations at any level cascade to children. ## Combining tracking dimensions Items can have multiple tracking dimensions active simultaneously: batch + serial (medical devices in batches with each unit serialised), batch + owner (consignment of specific batches), serial + licence plate (serialised items consolidated on a pallet for shipping). ## Item tracking setup Per item, configure: - **Which tracking dimensions are active.** - **Capture-required setup** — must serial be entered at receipt? At pick? At shipment? At return? - **Auto-generation rules** — serial / batch numbers generated automatically per pattern, or required to enter manually. **Operational implications.** - **Receipt** — more dimensions = slower receipt. Mobile scanners help. - **Shipping** — tracked items require scan validation at pick / pack / load. - **Quality / quarantine** — entire batches can be quarantined and released atomically. - **Recall** — given a problem batch, the system identifies every customer who received it. - **Cost** — tracked-dimension granularity affects cost accounting precision. ## Operational reality Activate tracking only where the value justifies. A consumer-goods distributor with simple SKUs doesn't need serial tracking; an industrial-equipment distributor probably does. Audit per item category. --- # Trade allowance and rebate management in F&O How trade allowance and rebate programs work in Dynamics 365 SCM — funds, deals, accruals, claims, and the integration with sales and finance. Source: https://www.solvingdynamics365.com/guides/trade-allowance-and-rebates-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 For wholesale distributors, consumer-goods manufacturers, and retailers, **trade allowances and rebates** are a large slice of the commercial relationship — supplier-funded promotions, volume rebates, retroactive discounts, marketing allowances, slotting fees. Done well, they're a strategic lever; done badly, they're an unreconciled mess that eats margin. Dynamics 365 Supply Chain Management ships a **Trade Allowance Management** module to keep them visible. ## The conceptual model A trade-allowance program is: - A **fund** — money the supplier is providing for a defined purpose (e.g. Q3 promotional support, volume rebate on certain SKUs). - A **trade allowance agreement** — the rules: who's eligible (customers, customer hierarchy), what's covered (items, item categories), what's earned (% of sales, fixed amount, volume bands), and what's required to earn it (proof-of-performance, sales volume threshold). - **Accruals** — the periodic recording of *earned but unpaid* allowance against transactions as they happen. - **Claims** — the formal request from the customer for payment of the accrued amount, with supporting evidence. - **Settlements** — the actual payment (or credit memo) that closes the claim. ## Funds A **fund** holds the budgeted amount the supplier has allocated. Funds can be customer-specific, customer-group-specific, or product-specific. They have validity periods and status (open, closed). Spending is tracked against the fund, so the supplier sees committed vs available. ## Agreements A **trade allowance agreement** binds a fund to specific customers and products with the calculation rule. Examples: - Volume rebate: "Customer X earns 2% on sales of Item Category Y exceeding 100,000 units in Q3". - Promotional allowance: "Customer X receives 5,000 EUR for end-cap display of Item Z in March". - Slotting fee: "Customer X receives a one-time 25,000 EUR for new product listing". Multiple agreements can run in parallel for the same customer. ## Accruals As sales transactions happen, the system **accrues** the relevant trade allowance. A sale of 1,000 units of Item Y to Customer X automatically accrues 2% × revenue against the volume rebate agreement (if Customer X has earned enough). Accruals post to a **trade allowance accrual GL account** — typically a contra-revenue or expense-side balance — recognising the liability before the customer claims. ## Claims processing When the customer claims (typically monthly or quarterly), the supplier reviews the claim against the accrued amount, validates proof-of-performance, and approves a settlement. Settlement posts a credit memo to the customer, debits the accrual account, and clears the liability. ## Integration with sales Pricing on sales orders can reflect trade-allowance-derived discounts at posting (immediate visibility) or accrue separately for later settlement. Both patterns are supported. ## Reporting Standard reports show: - Funds: budgeted vs accrued vs settled vs available. - Customer scorecards: trade-allowance earnings, ROI of promotional spend. - Accrued liability by customer for finance reconciliation. - Aged claims awaiting settlement. ## Limits The standard module covers most distributor and CPG patterns. For deeply retailer-specific allowances (chargebacks, deductions, complex deal structures across many channels), customers often layer a specialist trade-promotion management (TPM) tool. ## Operational reality The biggest trap is not adopting accruals systematically — running trade allowances as ad-hoc credit memos at quarter-end. Accrue at the transaction, and the management view is real-time. --- # Transportation management in Dynamics 365 SCM How the Transportation Management module in F&O handles rates, routing, loads, freight reconciliation, and where it stops being enough for serious shippers. Source: https://www.solvingdynamics365.com/guides/transportation-management-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 The **Transportation Management (TMS)** module in Dynamics 365 SCM extends order management into the freight world — rating shipments, building loads, planning routes, generating shipping documents, and reconciling freight invoices. It's a meaningful capability for mid-market shippers, with clear ceilings beyond which dedicated TMS platforms (BluJay, MercuryGate, Manhattan, Oracle TMS) start to win. **Core entities.** - **Carriers** — the transportation providers. Each carrier has services (LTL, FTL, parcel) and rate engines. - **Routes** — origin-destination definitions; can include intermediate stops. - **Loads** — the container holding shipped goods, with a carrier, a route, and load lines from one or more orders. - **Shipments** — the warehouse-side outbound (already in WMS); loads aggregate one or more shipments. - **Rate engines** — code that computes freight cost for a load. - **Rate routes / Rate masters** — rate cards per carrier per route. - **Freight bills** — what the carrier billed; reconciled against the system's rated cost. ## Rating Two types: - **Spot rates** — manual entry for ad-hoc shipments. - **Contract rates** — uploaded rate cards (per weight, per mile, per pallet, per container). Rate engine extensibility means partner ISVs add specific carrier rate APIs (FedEx, UPS, DHL) for real-time quotes. Without an API, you upload tariff sheets and the engine looks up rates. ## Load building The **Load Planning Workbench** lets a planner consolidate open shipments into loads: - Filter by ship-from, ship-to, carrier, equipment type. - Assign shipments to loads based on weight, volume, route compatibility. - Calculate utilisation (% of vehicle capacity). - Multi-stop routing (truck visits two customers on one trip). For high-volume operations, load building is the planner's daily task; for low-volume, it's automated by rules. ## Routing Routes can be: - **Direct** — origin to destination, one carrier. - **Multi-leg** — pickup, hub consolidation, line-haul, last-mile delivery. - **Pool point** — collected at a pool point and forwarded. Multi-leg routing supports international shipments crossing border with brokerage steps. ## Shipping documents TMS generates: - **Bill of lading (BOL)** — the carrier's contract. - **Packing list** — what's in the shipment. - **Commercial invoice** — for international. - **Carrier-specific labels** — UPS, FedEx, DHL labels via integration. - **Custom documents** — country-specific export paperwork. For parcel carriers, the workflow ends with a label printed at the pack station; for LTL/FTL, paperwork rides with the driver. ## Freight reconciliation Carrier invoices arrive after the shipment. The reconciliation workflow: 1. Freight invoice imported (EDI, file, manual entry). 2. System matches invoice line to load and rated cost. 3. Variances flagged (rate difference, weight reweigh, accessorials). 4. Approved invoices post to AP as cost; variances post to a freight variance account or get disputed. Done right, freight reconciliation recovers material savings; done poorly, freight overcharges sneak through. ## Hazardous goods Items flagged as hazmat carry **hazmat group** codes. TMS enforces: - Carrier eligibility (not all carriers handle hazmat). - Documentation generation (hazmat declarations). - Mode restrictions (some hazmat can't fly). ## Container management For ocean and rail freight, **container** tracking integrates: - Container booking against carriers. - Stowage planning. - Customs documentation per container. ## Integration with WMS Once a load is planned, the warehouse pick logic respects load assignment — pickers pick to load destination, pack to load. The handover is bidirectional: WMS reports actual ship weight back, which can trigger reweigh adjustments in TMS. **Where TMS in F&O stops being enough.** - **Complex multi-modal optimisation** — sophisticated TMS platforms run mathematical optimisation across thousands of shipments daily; F&O's load building is rule-based. - **Spot market integration** — real-time spot quotes across freight marketplaces; F&O doesn't natively integrate. - **Visibility services** — Project44, FourKites integration for in-transit tracking; F&O integrates via partner connectors. - **Yard management** — F&O has basic yard features; deep yard ops typically use a dedicated YMS. **Common pitfalls.** - **Rate cards out of date.** Carriers renegotiate; rate cards need to follow. A monthly rate refresh cadence avoids surprise variances. - **Accessorials not modelled.** Detention, fuel surcharges, residential surcharges accumulate; if not in the rate engine, they appear as variances. - **Load planning skipped.** Planners ignore load building, just dispatch each shipment individually; missed consolidation savings. - **No freight invoice reconciliation.** Pay-on-receipt; carriers overbill systematically when they sense no scrutiny. - **Carrier API integration cost underestimated.** Integration with FedEx, UPS, DHL is ongoing work as APIs change. ## Decision F&O TMS is well-suited to mid-market shippers with consistent lanes and moderate carrier counts. Beyond that, a dedicated TMS connected to F&O via integration delivers more capability than trying to push F&O TMS past its design envelope. --- # Vendor collaboration in Dynamics 365 SCM How the Vendor Collaboration portal in F&O lets suppliers interact directly with the buyer's system — orders, ASNs, invoices, and the operational benefits. Source: https://www.solvingdynamics365.com/guides/vendor-collaboration-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 For mid-to-large operations dealing with many suppliers, the cost of email-and-PDF-driven procurement is real: typos in order acknowledgments, missing shipping notices, AP departments chasing invoices, manual three-way matching. **Vendor Collaboration** in Dynamics 365 SCM gives suppliers structured, secure access to relevant parts of the buyer's system — they see their POs, acknowledge them, confirm shipments, submit invoices, and update their own contact data, all without email. ## The architecture Vendor Collaboration runs as a **scoped Power Pages portal** sitting in front of F&O's vendor data. Suppliers sign in with their own identities (Microsoft accounts, Entra B2B, or guest accounts depending on configuration), and the portal exposes specific entities scoped to the supplier's own data only. No supplier can see any data belonging to another supplier. **What suppliers do in the portal.** - **View open purchase orders.** Every PO sent to the supplier appears with full line detail, pricing, quantity, delivery date. - **Acknowledge purchase orders.** The supplier confirms (accepts, partially accepts with proposed changes, or rejects) each PO. Acknowledgments post back as workflow notifications to the buyer's purchasing team. - **Submit advance shipping notices (ASNs).** Before goods ship, the supplier creates an ASN with shipment date, tracking number, line-level quantities. The ASN arrives in F&O as expected receipt data. - **Submit invoices.** The supplier creates an invoice referencing the PO and shipment, with line-level detail. The invoice queues in F&O's incoming-document pipeline for approval and posting. - **Update vendor master data.** Address, contact, bank account changes are submitted by the supplier; the buyer's vendor master administrator approves or rejects. - **View payment status.** The supplier sees which of their invoices are approved, paid, on hold, with promised payment dates. - **View consumption data** — for vendor-managed inventory (VMI) scenarios, the supplier sees the buyer's inventory levels and consumption to plan replenishment. ## Onboarding suppliers Each supplier needs to be invited to the portal, granted appropriate roles, and assigned the relevant data scope. The onboarding flow can be self-service (the supplier requests access via a registration form, the buyer approves) or admin-driven (the buyer invites individually). Vendor users authenticate against their own organisation's identity provider through Entra B2B, so the supplier's IT controls their access lifecycle. ## Permission scoping A supplier user's roles control what they can see and do: - **Read-only view** of orders and invoices. - **Active responder** for acknowledgments and ASNs. - **Self-service editor** for their own profile. Different users at the same supplier can have different roles — a customer-service rep handles acknowledgments; an AP-side counterpart handles invoicing. ## The buyer-side workflow Inside F&O: - Supplier acknowledgments appear in the purchasing buyer's workspace for review. - Submitted ASNs queue for receipt processing in the warehouse. - Submitted invoices flow into the vendor-invoice approval workflow. - Master-data change requests route to the vendor-master administrator. **Benefits.** - **Reduced AP friction** — invoices arrive as structured data, not PDFs requiring data entry. - **Improved on-time receiving** — ASNs tell the warehouse exactly what's arriving. - **Faster cycle time** — supplier responses are minutes, not days of email back-and-forth. - **Better master data** — suppliers maintain their own contact and banking data. - **Audit trail** — every interaction logged. **Limits.** - **Supplier adoption** — small suppliers may resist portal use; need a fallback for paper / email. - **Setup overhead per supplier** — onboarding each supplier is real work; only worth it for suppliers with meaningful volume. - **EDI overlap** — large suppliers may already use EDI; the portal duplicates effort. ## Operational reality Vendor Collaboration pays off when most procurement volume flows through portal-enabled suppliers. Pilot with the top 20% of suppliers (by spend or volume) first; expand from there. --- # Warehouse mobile workflows in Dynamics 365 Supply Chain How handheld warehouse workflows work in Dynamics 365 SCM — configurable mobile workflows, scanning, license plates, and where they fit operationally. Source: https://www.solvingdynamics365.com/guides/warehouse-mobile-workflows-in-f-and-o Section: Finance & SCM / Supply chain & inventory Published: 2026-05-01 The advanced **Warehouse Management** module in Dynamics 365 Supply Chain Management is one of the standout features that justifies stepping up from Business Central. At its heart is a **configurable mobile workflow engine** that drives handheld scanner devices on the warehouse floor — purpose-built for performance, glove-friendly use, and customisable without code. ## The model A **mobile workflow** is a sequence of steps a warehouse worker performs through their handheld device — scan a license plate, scan an item, confirm a quantity, scan a destination location, complete the move. Each step is defined in the workflow designer with prompts, validation, and conditional branching. Workflows live in F&O's setup; they're solution-package-portable like other configuration. ## Pre-built workflow types Microsoft ships configurations for the standard warehouse operations: - **Receipt** — inbound from purchase orders, transfer orders, return shipments. - **Put-away** — directed put-away to bins. - **Pick** — pick for outbound shipments, transfers, production consumption. - **Pack** — packing into outbound containers. - **Load** — loading onto outbound shipments. - **Counting** — cycle counting and full physical inventory. - **Movement** — moving stock between bins. - **Production** — material picking for production orders, finished-goods reporting. - **Quality** — quality inspection sampling and disposition. Each pre-built workflow can be cloned and customised — change the prompts, skip optional steps, add validation rules, branch on conditions. ## License plates A **license plate (LP)** is a label representing a logical unit of inventory — a pallet, a tote, a carton. License plates are the unit of movement: scan one license plate to move many items at once. License plates can be nested (a pallet LP contains many carton LPs each containing many items). Operations on the LP propagate to its contents. ## The handheld experience The mobile interface is deliberately minimal — large buttons, short prompts, scannable barcodes. Workers operate at speed without paging through menus. Each step's UI is generated from the workflow definition, with text and barcode-input emphasis. ## Hardware F&O's mobile experience runs on Windows-based industrial PDAs, Android devices via the **Warehouse Management mobile app** (the modern, recommended option), iOS devices, and forklift-mounted vehicle terminals. Bluetooth and Bluetooth+WiFi scanners pair with the device. Voice-pick devices integrate through partner add-ons. ## Wave processing Outbound order flow runs through **waves**: groups of orders released together for picking. Wave templates define the bundling logic (orders by route, by carrier, by priority). When a wave releases, the system computes pick plans, generates LP shipments, and queues pick work for handhelds. ## Slotting and replenishment Bin replenishment (moving stock from bulk to pick bins) is automated based on min/max thresholds, demand profiles, or scheduled jobs. Slotting (the assignment of items to optimal pick bin locations) can run on an ABC-velocity basis or through advanced WMS optimisation modules. ## Why this matters A well-configured advanced WMS in F&O can run a complex distribution warehouse with hundreds of operators, multiple shifts, and thousands of orders per day at the kind of throughput that lower-tier WMS systems struggle with. The trade-off is real: implementation is substantial, and the workflow design demands warehouse-domain expertise. ## Beyond the standard Customers with very specific WMS needs (mezzanines with pick-to-light, dynamic slotting based on real-time analytics, robotic AS/RS integration) extend through partner ISVs or via the open APIs. --- # What is Dynamics 365 Finance? Microsoft's enterprise finance app — multi-entity general ledger, AP/AR, fixed assets, budgeting, and consolidations at scale. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-finance Section: Finance & SCM / Overview & platform Published: 2026-05-01 Updated: 2026-09-05 ### Key facts - Dynamics 365 Finance and Supply Chain Management share one application core, one database, and one object model — effectively one product licensed as two. - Supports up to ten financial dimensions on a shared chart of accounts, set-based rather than segment-based. - Costs roughly three times more per user than Business Central and is typically implemented by global system integrators over six months to two years (as of 2026-08-27). - IFRS 15 / ASC 606 revenue recognition is covered by a dedicated module supporting bundles, allocations, and residual-method treatment. 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](https://www.solvingdynamics365.com/guides/global-address-book-in-f-and-o)**, with intercompany accounting wired in so that transactions between entities balance automatically. [Organization hierarchies](https://www.solvingdynamics365.com/guides/organization-hierarchies-in-f-and-o) model the reporting and approval structure across those entities, and the whole thing sits on [a role-based security model](https://www.solvingdynamics365.com/guides/dynamics-365-finance-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](https://www.solvingdynamics365.com/guides/number-sequences-in-finance-and-operations), and any entity trading in more than one currency layers in [parallel currencies](https://www.solvingdynamics365.com/guides/parallel-currencies-in-finance-and-operations) 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](https://www.solvingdynamics365.com/guides/the-cost-accounting-module-in-f-and-o)** 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](https://www.solvingdynamics365.com/guides/cash-management-module-in-f-and-o) and [cash flow forecasting](https://www.solvingdynamics365.com/guides/cash-flow-forecasts-in-f-and-o) for the liquidity side — and **AI-assisted matching** for payments and invoices, the same OCR-driven pipeline covered in [AP automation and OCR](https://www.solvingdynamics365.com/guides/ap-automation-and-ocr-in-f-and-o). 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](https://www.solvingdynamics365.com/guides/1099-reporting-in-f-and-o), and payments in jurisdictions that tax at source need [withholding tax](https://www.solvingdynamics365.com/guides/withholding-tax-in-f-and-o) 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](https://www.solvingdynamics365.com/guides/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](https://www.solvingdynamics365.com/guides/dynamics-365-finance-subscription-billing) for recurring-contract billing itself. Lease accounting under the related IFRS 16 / ASC 842 standards is covered separately in [IFRS 16 lease accounting](https://www.solvingdynamics365.com/guides/ifrs-16-lease-accounting-in-f-and-o). ## Budgeting, planning, and consolidations **Budget control** with optional commitment accounting stops purchase orders and expense reports that would overrun a budget bucket. **[Budget planning](https://www.solvingdynamics365.com/guides/budget-planning-in-f-and-o)** workflows let distributed contributors build a consolidated plan through Excel templates and route-based approvals — the same **[workflow engine](https://www.solvingdynamics365.com/guides/dynamics-365-finance-workflow)** 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](https://www.solvingdynamics365.com/guides/sales-tax-setup-in-f-and-o) 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](https://www.solvingdynamics365.com/guides/electronic-reporting-in-f-and-o)** 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](https://www.solvingdynamics365.com/guides/choosing-a-dynamics-365-partner) shapes the project as much as the product does. ## Where to go next Go deeper with [financial dimensions in Dynamics 365 Finance](https://www.solvingdynamics365.com/guides/financial-dimensions-in-dynamics-365-finance), [environments and LCS](https://www.solvingdynamics365.com/guides/dynamics-365-finance-environments-and-lcs), and the update discipline in [One Version and updates](https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates). [Year-end close in F&O](https://www.solvingdynamics365.com/guides/year-end-close-in-f-and-o) shows the periodic routines in practice. If you are deciding between tiers, [Business Central vs Finance and Operations](https://www.solvingdynamics365.com/guides/business-central-vs-finance-and-operations) draws the line, and the [Finance and Operations pricing page](https://www.solvingdynamics365.com/pricing/finance-and-operations) has current list prices. ### Frequently asked questions **What is the difference between Dynamics 365 Finance and Business Central?** Finance is the enterprise-tier ledger descended from Dynamics AX, built for groups with many legal entities, currencies, and statutory regimes; Business Central is the SMB ERP. Finance costs roughly three times more per user, is implemented by global system integrators over six months to two years, and pays off when you need a shared chart of accounts, posting layers, native consolidations, and dozens of localisations in one tenant. **Is Dynamics 365 Finance the same product as Finance and Operations?** Finance is one half of what Microsoft calls the Finance and Operations apps. Finance and Supply Chain Management share one application core, one database, and one object model — effectively one product licensed as two — so a Finance-only deployment can add Supply Chain later without integration work. **How many financial dimensions does Dynamics 365 Finance support?** Up to ten financial dimensions on a shared chart of accounts. They are set-based rather than segment-based, so a report can slice on any subset independently without the chart of accounts having to carry the analytical structure. **Does Dynamics 365 Finance handle IFRS 15 and ASC 606 revenue recognition?** Yes. The dedicated Revenue Recognition module covers bundles, allocations, contract management, and residual-method treatment. It replaced the older revenue recognition feature in Sales and Marketing and is the recommended path for subscription and services businesses. **Who implements Dynamics 365 Finance and how long does it take?** Almost always a global system integrator or a large regional partner. Six months for a subsidiary rollout is the fast end; a global template takes two years or more, and consulting effort dominates total cost in the first two years. **When is Dynamics 365 Finance the wrong fit?** Below roughly a hundred million in revenue with a handful of legal entities, Business Central's finance module covers the same ground — dimensions, posting groups, consolidations — at a fraction of the licence and implementation cost. Above the enterprise tier, at the largest, most acquisitive multinationals running dozens of currencies and statutory regimes with a mature corporate-performance-management estate already in place, Finance's built-in budgeting and consolidations are a starting point, not a CPM replacement — expect to keep or add a dedicated tool like Anaplan, OneStream, or Board. --- # What is Dynamics 365 Supply Chain Management? Microsoft's enterprise supply chain app — manufacturing, warehouse, transportation, planning, and asset management at scale. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-supply-chain Section: Finance & SCM / Overview & platform Published: 2026-05-01 Updated: 2026-09-05 ### Key facts - Covers procurement, inventory, full warehouse management (handheld scanning), discrete/process/lean manufacturing, master planning, transportation, and asset management on the same core as Dynamics 365 Finance. - Planning Optimization is the in-memory master planning engine that replaced the older MRP engine, running net-change or regenerative plans in minutes across hundreds of sites. - Deliberately stops short of being a manufacturing execution system (MES) — machine-level execution integrates through Microsoft's MES hooks or partner products (as of 2026-08-27). - The recommended fit threshold versus Business Central's light manufacturing is roughly a few hundred million in revenue or genuine multi-site/process-manufacturing complexity. Dynamics 365 Supply Chain Management (SCM) is Microsoft's enterprise-grade application for procurement, manufacturing, inventory, warehousing, transportation, and master planning. Like Dynamics 365 Finance, it descends from Dynamics AX, and is built for organisations whose operational complexity has outgrown Business Central — multi-site manufacturers, large distributors, retailers, and process industries. ## Where it fits SCM is the operations half of what Microsoft calls the **Finance and Operations apps** (F&O). Finance and SCM share a single application core, a single database, and a single object model — they are effectively one product sold as two. A deployment that runs both gets a unified back office with no integration between finance and operations; a deployment that runs only Finance is skipping the operational modules but sitting on the same platform, ready to add them later. The target customer is a manufacturer, distributor, or asset-heavy operator with revenues from a few hundred million upwards. Below that scale, Business Central is usually the right fit, and its light-manufacturing capabilities cover simpler assembly workflows. Above it — global groups running across dozens of legal entities with heavy shop-floor operations — SCM competes directly with SAP S/4HANA and Oracle NetSuite / Fusion. ## Inventory and warehouse Item master with sophisticated **product dimensions** (size, colour, style, configuration) and **[tracking dimensions](https://www.solvingdynamics365.com/guides/inventory-dimensions-in-f-and-o)** (batch, serial, owner), multi-site warehousing, and full **Warehouse Management (WMS)** with handheld scanning, wave and load management, configurable **mobile device menus**, license plate tracking, cluster picking, and slotting. Directed put-away and picking are the norm, not the exception. [Inventory classification](https://www.solvingdynamics365.com/guides/inventory-classification-in-f-and-o) and periodic [inventory closing](https://www.solvingdynamics365.com/guides/cost-management-and-inventory-closing-in-f-and-o) are what keep that inventory model reconciled to the GL. The WMS is deep enough that it replaces many standalone WMS products, and it can be **advanced-warehouse-enabled** on some warehouses while others operate in the simpler basic warehousing mode — useful for phased rollouts. [Consignment inventory](https://www.solvingdynamics365.com/guides/consignment-inventory-in-f-and-o), vendor-owned stock, and split-ownership scenarios are all supported. ## Procurement Vendor catalogues, sourcing, purchase requisitions with configurable approval workflows, RFQs with sealed-bid evaluation, purchase agreements (blanket orders), a **vendor collaboration portal** for suppliers who don't have EDI, and three-way matching between purchase order, receipt, and invoice. Freight, duty, and insurance charges on those purchase orders allocate into inventory value through the [Landed Cost module](https://www.solvingdynamics365.com/guides/landed-cost-module-in-f-and-o). For process-heavy industries, category management structures the spend hierarchy, and integration to **[Microsoft Cloud for Sustainability](https://www.solvingdynamics365.com/guides/microsoft-cloud-for-sustainability)** — and its [Sustainability Manager](https://www.solvingdynamics365.com/guides/sustainability-manager-for-dynamics-365) component specifically — and to third-party spend-analytics tools brings emissions and category insight into the buying process. ## Manufacturing SCM's manufacturing coverage is broad. **Discrete** manufacturing uses production BOMs and routings; **process** manufacturing uses formulas and co/by-products with [catch weight](https://www.solvingdynamics365.com/guides/catch-weight-items-in-f-and-o); **lean** manufacturing supports kanban and takt-based flow. All three modes can coexist on the same site. Beyond the modes, the shop-floor toolkit is comprehensive: work centres and resources with capabilities and calendars, **finite scheduling**, [subcontracting](https://www.solvingdynamics365.com/guides/dynamics-365-for-manufacturing-subcontracting-in-f-and-o), [engineering change management](https://www.solvingdynamics365.com/guides/bom-versioning-and-engineering-change-in-f-and-o), batch attributes (viscosity, potency, purity) for regulated industries, and shop floor control with clock-in and job registration. **Product Configuration Model** (PCM) supports engineer-to-order and configure-to-order flows. Process manufacturers producing more than one output from a single run rely on [co-products and by-products](https://www.solvingdynamics365.com/guides/co-products-and-by-products-in-f-and-o) allocation on top of the formula. Manufacturing execution below that layer typically integrates through the **Manufacturing Execution System (MES) integration** hooks or through partner products; SCM is deliberately not an MES. ## Master planning **Planning Optimization** is a high-performance, in-memory service that replaced the older MRP engine in the last few years. It runs net-change or full regenerative plans in minutes instead of hours, scales across hundreds of sites, and separates planning from the transactional database so long plans don't lock the system. On top of Planning Optimization sit **demand forecasting** (statistical baseline forecasts) and the more recent **demand planning** module (collaborative planning workflows), which increasingly incorporates [machine learning forecasting](https://www.solvingdynamics365.com/guides/machine-learning-forecasting-for-d365-supply-chain) rather than pure statistical models. Together they close the loop from statistical forecast to consensus plan to net requirement to purchase or production order. ## Transportation and asset management [Transportation management](https://www.solvingdynamics365.com/guides/transportation-management-in-f-and-o) covers inbound and outbound transportation with rate shopping across carriers, route planning, load building, freight reconciliation, and shipping-carrier integration (parcel and LTL). Not a full TMS replacement for the largest 3PL operators, but adequate for most in-house transportation needs. **[Asset Management](https://www.solvingdynamics365.com/guides/asset-management-in-dynamics-365-scm)** covers work orders, preventive maintenance, condition-based monitoring, fault management, and IoT signal integration for industrial equipment — increasingly important for asset-heavy operators such as [utilities](https://www.solvingdynamics365.com/guides/dynamics-365-for-utilities), [mining](https://www.solvingdynamics365.com/guides/dynamics-365-for-mining), and [manufacturing](https://www.solvingdynamics365.com/guides/dynamics-365-for-manufacturing) plants that want the maintenance system on the same platform as inventory and procurement, and it shows up again for asset-heavy [telecommunications](https://www.solvingdynamics365.com/guides/dynamics-365-for-telecommunications) network operators and [energy](https://www.solvingdynamics365.com/guides/dynamics-365-for-energy) producers running the same equipment-maintenance discipline. ## Adjacent products Two products sit around SCM and are commonly deployed with it. **Intelligent Order Management** (sold separately) orchestrates orders across sales channels and fulfilment locations — useful for omnichannel retailers where the "where does this order ship from" decision is non-trivial. **Dynamics 365 Commerce** is the retail store solution (POS, e-commerce, clienteling); it uses SCM as its inventory and pricing back end. For the CRM side of the business, SCM shares Dataverse via **Dual-write**, so a Sales opportunity in the Sales app or a case in Customer Service can flow through to a sales order or a return in SCM without custom integration. ## Licensing and implementation SCM is licensed per user, typically alongside Finance under the F&O bundle. **Full users**, **Activity users**, and **Team Members** provide different price points depending on access needs. Device licenses cover shop-floor terminals and warehouse handhelds. Implementations are large — six months at the very fast end, more commonly a year and up — and are almost always led by a global system integrator. The functional footprint is wide (finance, procurement, warehouse, manufacturing, transportation) and every area has depth, so consulting effort dominates the total cost of ownership in the first two years. ## When Supply Chain Management is the wrong fit Below a few hundred million in revenue with simple assembly or light manufacturing, Business Central's Premium tier and its production BOMs, routings, and capacity planning cover the workload at a fraction of the licence and implementation cost — SCM's finite scheduling, advanced warehousing, and multi-site planning are overkill for a single-site operation. Above the enterprise tier, at the very largest, most process-heavy multinationals with deep formula management and regulatory batch records across dozens of countries, SAP S/4HANA remains the incumbent default that most large system integrators are staffed to deliver at scale — SCM is the credible, faster-moving challenger, not yet the safe default for that segment. And organisations expecting a manufacturing execution system out of the box will be disappointed: SCM's shop-floor tools stop at job registration and finite scheduling, and true machine-level execution needs an MES integration or a partner product on top. ## First-time buyer checklist - **Scale check.** Confirm revenue, site count, and legal-entity count actually sit in SCM's target band — a single-site operation with light assembly is usually cheaper and faster on Business Central. - **Manufacturing mode.** Decide whether the operation is discrete, process, lean, or a mix — all three can coexist on one site, but the fit-gap workshop should map your actual production flow against them before configuration starts. - **Warehouse depth.** Decide which sites need advanced-warehouse-enabled WMS (directed put-away, wave/load management, handheld scanning) versus simpler basic warehousing — mixing both across sites is supported and often the right phased approach. - **Planning cadence.** Model whether Planning Optimization's net-change or full regenerative runs fit your replenishment rhythm, and whether demand forecasting or the newer demand planning module is the right layer on top. - **MES boundary.** If shop-floor execution needs machine-level detail, scope the MES integration or a partner product alongside SCM rather than expecting SCM alone to cover it. - **Dual-write scope.** If Sales, Customer Service, or Field Service are in play, decide which entities sync through dual-write before go-live — retrofitting the integration later is more disruptive than scoping it up front. - **System integrator.** SCM implementations are large and consulting-effort-dominated; [choosing the right partner](https://www.solvingdynamics365.com/guides/choosing-a-dynamics-365-partner) matters more here than almost anywhere else in the portfolio. ## Where to go next The planning engine is covered in [master planning runs](https://www.solvingdynamics365.com/guides/master-planning-runs-in-f-and-o) and [Planning Optimization](https://www.solvingdynamics365.com/guides/dynamics-365-planning-optimization); the warehouse in [warehouse mobile workflows](https://www.solvingdynamics365.com/guides/warehouse-mobile-workflows-in-f-and-o); the three manufacturing modes in [discrete vs process vs lean](https://www.solvingdynamics365.com/guides/discrete-vs-process-vs-lean-manufacturing-in-f-and-o). The bridge to the CRM apps is [dual-write](https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-integration). Current list prices are on the [Finance and Operations pricing page](https://www.solvingdynamics365.com/pricing/finance-and-operations). ### Frequently asked questions **What does Dynamics 365 Supply Chain Management cover?** Procurement, inventory, full warehouse management with handheld scanning, discrete, process, and lean manufacturing, master planning through Planning Optimization, transportation, and asset management — all on the same application core as Dynamics 365 Finance. **When should I choose Supply Chain Management over Business Central?** When operational complexity has outgrown Business Central: multi-site manufacturing, directed put-away and picking, process manufacturing with catch-weight, finite scheduling, or planning across hundreds of sites. Below a few hundred million in revenue, Business Central and its light manufacturing usually fit better. **Is Dynamics 365 Supply Chain Management an MES?** No. It covers shop-floor control, job registration, and finite scheduling but deliberately stops short of a manufacturing execution system. Machine-level execution integrates through Microsoft's MES integration hooks or partner products. **What is Planning Optimization?** The in-memory master planning service that replaced the older MRP engine. It runs net-change or regenerative plans in minutes rather than hours, scales across hundreds of sites, and runs outside the transactional database so long plans do not lock the system. **How does Supply Chain Management connect to the CRM apps?** Through dual-write, which syncs selected Supply Chain and Finance entities to Dataverse in near real time. A Sales opportunity or a Customer Service case can flow to a sales order or a return without custom integration. **When is Dynamics 365 Supply Chain Management the wrong fit?** Below a few hundred million in revenue with simple assembly or light manufacturing, Business Central's Premium tier covers the workload at a fraction of the cost — SCM's finite scheduling and multi-site planning are overkill for a single-site operation. At the very largest, most process-heavy multinationals with deep regulatory batch records across dozens of countries, SAP S/4HANA remains the safer incumbent default for now. And SCM is not a manufacturing execution system — shop-floor tools stop at job registration and finite scheduling. --- # Withholding tax in Dynamics 365 Finance How F&O handles withholding tax — vendor and customer-side configurations, country variations, and the integration with payments and reporting. Source: https://www.solvingdynamics365.com/guides/withholding-tax-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 **Withholding tax** is the practice of deducting tax from a payment at source and remitting it directly to the tax authority on behalf of the recipient — common for cross-border payments, professional services, dividends, royalties, and certain domestic transactions. Dynamics 365 Finance supports withholding tax in detail because the requirements vary substantially by country and transaction type. ## The concept When Company A pays a foreign service provider (or a domestic supplier in jurisdictions that require it), instead of paying the full invoice amount and the provider declaring tax in their own jurisdiction, Company A *withholds* a tax amount and remits it directly to its own tax authority. The provider receives the net amount; the tax authority gets the withheld portion; documentation flows so the provider can claim the withheld amount as tax paid in their own jurisdiction. **Use cases.** - **Cross-border services** — payments to foreign consultants, technology licences, royalties. - **Domestic professional services** — many countries (India, Brazil, Argentina, Mexico, Philippines, Indonesia, others) require withholding on domestic invoices to professionals or specific industries. - **Dividends and interest** — typically withholding applies to outbound payments to foreign shareholders / lenders. - **Subcontractor payments** — UK's CIS (Construction Industry Scheme) withholds tax from subcontractors. **Setup in F&O.** - **Withholding tax codes** — define the rate, calculation, and tax-authority destination for each type of withholding. - **Withholding tax groups** — combinations of codes for cascaded or layered withholding (some countries layer multiple withholdings on the same transaction). - **Item / service classification** — which goods or services are withholding-eligible. - **Vendor configuration** — flag vendors as subject to withholding, with the applicable group. - **Customer configuration** — for customer-side withholding (where the *customer* is required to withhold from the seller's invoice). - **Country-specific localisations** — the country localisation typically pre-configures the standard withholding regimes. **The transaction flow.** 1. **Invoice received** — the full invoice amount is recorded as vendor liability. 2. **Payment proposed** — the payment routine identifies the withholding requirement, calculates the withheld amount, splits the payment: - Vendor receives invoice amount minus withholding. - Withholding amount books to a tax-payable account. 3. **Payment posted** — both legs post: payment to vendor, withholding liability to tax authority. 4. **Periodic remittance** — accumulated withholding is paid to the tax authority on the schedule the regulator requires (monthly, quarterly). 5. **Withholding certificate** — the vendor receives a certificate documenting the withheld amount for their tax claim. **Country-specific complications.** - **India TDS** (Tax Deducted at Source) — multiple withholding categories with thresholds, exemptions, certificates (Form 16A), and quarterly returns (Form 26Q, 27Q). - **Brazil IRRF, PIS, COFINS, INSS, ISS** — multiple cascaded withholdings on the same invoice with different rates, bases, and recipients. - **UK CIS** — subcontractor classification (Gross, Net 20%, Net 30% with no verification) and monthly returns. - **Argentina** — multiple federal and provincial withholdings; complex. - **US 1099 reporting** — not withholding per se, but annual reporting of payments to certain vendors; similar configuration model. The country-specific complications are why country localisations matter — getting the engine right requires deep regulatory knowledge. **Documentation.** - **Withholding certificates** — issued to vendors documenting the amount withheld. Templates per country. - **Periodic returns** — generated through Electronic Reporting (Globalization Studio) per country format. - **Annual summaries** — for tax authorities and for vendors' year-end tax claims. **Common pitfalls.** - **Vendor not flagged for withholding** — invoice paid in full, withholding missed, penalty risk. - **Wrong withholding rate applied** — under-withholding causes liability; over-withholding causes vendor disputes. - **Threshold rules not respected** — some withholdings only apply above thresholds; below, no withholding required. - **Exemption certificates not honoured** — vendors with exemption certificates shouldn't have withholding applied. - **Certificate generation skipped** — vendors require certificates for their own tax claims. ## Operational reality Withholding tax is one of the most country-specific areas of F&O. Engage local tax expertise during setup; partner with a localisation specialist for the country; review setup annually as regulations change. --- # Workflow in Dynamics 365 Finance The workflow engine in Dynamics 365 Finance and SCM — designers, conditions, assignment, escalations, and Power Automate alternatives. Source: https://www.solvingdynamics365.com/guides/dynamics-365-finance-workflow Section: Finance & SCM / Finance Published: 2026-05-01 The Finance and Operations workflow engine is the routing and approval framework for almost every transactional document — purchase requisitions, purchase orders, vendor invoices, journals, project quotations, expense reports, time sheets. Every Finance/SCM implementation configures dozens of workflows; knowing the engine's shape saves a lot of rebuilds. ## Workflow types Each business document has a *workflow type* — a definition Microsoft ships per area (Vendor Invoice Workflow, Purchase Requisition Workflow, etc.). A workflow type defines which tasks, approvals, and conditional decisions are valid for that document. Customers create one or many workflow *instances* of each type, with different conditions to route to different approver chains. ## Designer The graphical workflow designer runs inside Finance/SCM, drag-and-drop, with elements: - **Manual decisions** — branch based on a condition (e.g. amount > 50,000). - **Approvals** — one or more approval steps, each with a defined approver (a named user, a hierarchy lookup, a workflow user, a position-based lookup). - **Tasks** — actions assigned to a user that aren't approvals (e.g. "verify supporting documents"). - **Automated tasks** — server-side actions (e.g. "apply default dimensions") that run without human interaction. - **Parallel branches** — multiple paths running concurrently with a join. ## Approver resolution Approvers can be resolved by: - **Hierarchical**: walk up the position hierarchy until an approver with sufficient authority is found. - **Named approver**: a specific user. - **Workflow user**: a user selected from a configured list. - **Limits**: signing limits per position drive how far up the hierarchy a document escalates. ## Conditions Workflow steps can be gated by **conditions** expressed in a simple query against document fields and dimensions. Conditions are why a 5,000-EUR invoice routes one way and a 500,000-EUR invoice routes another. ## Escalation Each step has an escalation policy — if the approver doesn't act in N days, the step reassigns or notifies. This is the saving grace of workflows that get stuck on leave. ## Delegation Users delegate their workflow inbox to a substitute during absences. ## Power Automate alternatives For workflows that need to reach outside Finance/SCM, customers increasingly use **Power Automate** approvals flows triggered by Dataverse changes (via virtual entities or Dual-write). The pattern: lightweight transactional approvals stay in F&O; cross-system or external-stakeholder approvals move to Power Automate. ## Operational reality Heavy workflow proliferation slows performance and clouds audit. Aim for ten well-designed workflows, not fifty quick ones. --- # X++ — the language behind Finance and Operations What X++ is, where it came from, and how it's used in F&O — language features, the application object tree. Source: https://www.solvingdynamics365.com/guides/f-and-o-x-plus-plus-language Section: Finance & SCM / AL & X++ development Published: 2026-05-01 Dynamics 365 Finance and Operations runs on **X++** — a proprietary object-oriented language that's been the foundation of the AX / F&O product family since the 1990s. Modern X++ feels like a hybrid of Java, C#, and SQL; for developers extending F&O, learning X++ is the prerequisite for serious work. ## Origin Born in the 1990s with Axapta (later acquired by Microsoft, becoming Dynamics AX, then Dynamics 365 F&O). Inspired by Object Pascal and Java; designed for business applications with native data access. ## Modern X++ As of F&O wave 2 2026: - **Compiled to IL** — runs on .NET CIL after compilation. - **Visual Studio development** — primary IDE; AOT (Application Object Tree) navigated visually. - **Modern syntax** — closures, attributes, generics (limited). - **Native SQL** — `select * from custTable where ...` works inline. The language has evolved significantly; modern X++ is more Java/C#-like than its Pascal heritage. **Core constructs.** - **Classes** with inheritance. - **Tables** as first-class objects (extending DataObject). - **Views, queries, maps.** - **[Forms](https://www.solvingdynamics365.com/guides/f-and-o-form-extensions)** with event-driven controllers. - **Reports** (mostly legacy; SSRS for newer). - **Workflows.** - **Services.** The Application Object Tree (AOT) is the namespace; all artefacts live in it organised by type. **Native SQL.** ```x++ CustTable custTable; select firstonly custTable where custTable.AccountNum == '4000'; ``` The `select` statement is integrated with the language; the compiler generates SQL. ## Table buffers A table variable represents a row buffer: ```x++ CustTable custTable; custTable.AccountNum = 'NEW001'; custTable.Name = 'New Customer'; custTable.insert(); ``` `custTable` is a buffer; methods like `.insert()`, `.update()`, `.delete()` operate on the buffer's data. **Extension model.** - **[Chain of Command (CoC)](https://www.solvingdynamics365.com/guides/chain-of-command-extension-model-in-f-and-o)** — extension method wrappers around base methods. - **Event handlers** — subscribe to pre/post events on base methods. - **Table extensions** — add fields, methods, events to existing tables. - **[Form extensions](https://www.solvingdynamics365.com/guides/f-and-o-form-extensions)** — add controls to existing forms. No direct base code modification; extensions only. This enables Microsoft to update base code without breaking customisations. A new or changed table or field still has to synchronize into the underlying SQL database before it's usable — when that step fails, [database synchronization errors](https://www.solvingdynamics365.com/guides/finance-and-operations-database-synchronization-errors) is the reference for reading the sync log. **Visual Studio integration.** - Visual Studio with F&O developer tools installed. - Browse AOT, edit X++, compile, deploy. - Debugger built in. - Source control via Azure DevOps git. The development experience has improved dramatically vs the old MorphX environment. ## Classes vs tables Two distinct concepts: - **Class** — code logic, business rules. - **Table** — data storage. A class operates on table buffers; a table can have methods too but typically lightweight. ## The macro system X++ has a C-like preprocessor: ```x++ #define.MaxLength 100 ``` Used heavily in older code; less in modern. Macros pollute namespaces and are deprecated for most uses. ## Currency and value handling Built-in types for financial data: - **Real** — decimal numbers. - **Currency** — currency-aware decimals. - **Amount** — financial amounts with currency. Plus rounding helpers, conversion functions; financial math is first-class. **Common patterns.** **Iterate records:** ```x++ while select custTable where custTable.CustGroup == 'PREMIUM' { info(strFmt("Customer: %1", custTable.Name)); } ``` **Insert with transaction:** ```x++ ttsbegin; CustTable.insert(); ttscommit; ``` **Method call with exception:** ```x++ try { someMethod(); } catch { error("Something failed"); } ``` **Performance considerations.** - **Set-based vs record-based operations** — set-based much faster. - **Index utilisation** — define indexes for common queries. - **Cache hints** — `forupdate`, `notexistsjoin` for performance. - **Batch processing** — for long operations. **Modern X++ features.** - **Closures** (anonymous methods). - **Attributes** for metadata. - **Reflection** via SysDictType, SysDictClass. ## Comparison with C# X++ is similar to C# in many ways but: - Less generic (limited generics). - Native SQL integration. - Domain-specific for ERP. - Smaller community. C# developers picking up X++ usually feel productive within weeks. **Extension considerations.** - **Sandboxed dev environments** — Tier 1 VMs. - **Build server** — compiles and packages. - **Deployment via LCS or Azure DevOps** — to upper environments. The deployment story is more complex than BC's AL; F&O development is heavier infrastructure. **Common pitfalls.** - **Modifying base code.** Cardinal sin; updates break. - **Heavy in-loop DB calls** — performance dies. - **No transaction control.** Inconsistent state on errors. - **Skipping CoC pattern** — using events when CoC is cleaner. - **Macro overuse** — modern code prefers methods and constants. ## Strategic positioning X++ is here to stay — F&O is built on it; replacing it would mean a rewrite of millions of lines of base application code. Microsoft continues to invest: modernisation each wave, better tooling, Copilot-assisted X++ development emerging. Developers committing to F&O development should treat X++ as a long-term investment; the language isn't going anywhere. Mastery requires the language plus the AOT plus the patterns; investment time is meaningful but the resulting capability is in demand. --- # Year-end close in Dynamics 365 Finance How year-end close works in F&O — fiscal year closure, opening transactions, depreciation reset, ledger settlements, and the year-end ritual. Source: https://www.solvingdynamics365.com/guides/year-end-close-in-f-and-o Section: Finance & SCM / Finance Published: 2026-05-01 ### Key facts - Year-end close generates opening transactions on the first day of the new fiscal year that carry forward the prior year's closing balances into fresh postings. - The Year-end close routine closes P&L accounts to a retained-earnings account, rolls forward balance-sheet accounts at their closing values, and updates the fiscal year status to Closed. - Most organisations use the detailed close method, which closes P&L accounts to retained earnings line by line to preserve the audit trail, over the summary close, which posts a single aggregated entry. - Depreciation books roll the current year's depreciation into accumulated depreciation, and asset transactions before the closure date are locked while new-year transactions open. - Year-end is fundamentally a monthly close at scale — disciplined monthly closes mean the December cycle is month-end plus the closing routine, not a separate panic. Year-end close in Dynamics 365 Finance is the culmination of the financial cycle — the formal closing of one fiscal year, the rolling of profit-and-loss balances into retained earnings, and the opening of the new year. Done well, it's a structured ritual with predictable steps; done badly, it's a frantic month of corrections that delays everyone. ## Pre-close preparation Before any year-end-specific steps, the year's final period must be fully closed: - All accruals posted. - All depreciation calculated and posted (final period plus catch-up). - All FX revaluations run with year-end rates. - All inventory closing completed (with year-end as the closing date). - All project recognitions and WIP postings finalised. - All AP / AR sub-ledgers reconciled to GL. - All bank accounts reconciled. - All intercompany reconciliations completed. These are part of normal monthly close; year-end just demands they all happen for the final period without gaps. ## Opening transactions A **closing transaction** posts on the last day of the fiscal year to capture the closing balances. Year-end specifically generates **opening transactions** on the first day of the new year — same balances but in the new year's books, ready to receive new postings. F&O's **Year-end close** routine performs: - **Closing of P&L accounts** — revenue and expense accounts close to zero by posting their balance to a **retained earnings** account (or multiple, per the chart-of-accounts configuration). - **Opening of balance-sheet accounts** — asset, liability, and equity accounts roll forward at their closing values as opening values. - **Closing transactions on dimensions** — if dimensions are tracked at year-end, closing transactions can carry them forward. - **Fiscal year status update** — the closing year moves to *Closed* status; the new year is opened for posting. **Closing methods.** - **Detailed close** — closes all P&L accounts to retained earnings line by line, preserving the audit trail. - **Summary close** — aggregates P&L into a single retained-earnings posting. - **Reverse close** — for reopening a year if needed (rare; should require strong governance). Most organisations use **Detailed close** for audit traceability. ## Fixed asset year-end Fixed assets have their own year-end handling: - **Depreciation books** roll forward — the current year's depreciation accumulates into the asset's accumulated depreciation; the new year's depreciation starts fresh. - **Asset transactions** before year-end-closure date are locked; transactions after open in the new year. - **Depreciation forecasts** for the new year can be generated for budgeting purposes. ## Project year-end Projects don't have separate year-end ceremony, but year-end is when: - Multi-year project budgets roll forward. - WIP balances at year-end reflect the project's true financial state for statutory purposes. - Outstanding project commitments carry into the new year. ## Inventory year-end Inventory closing for the final fiscal period locks inventory transactions as of year-end. **Physical inventory counts** that happen near year-end produce the audit-ready inventory valuation. Some organisations do mid-year cycle counts to spread the workload. ## Intercompany at year-end Multi-entity tenants reconcile intercompany balances rigorously at year-end. Each pair of entities must agree on: - Open intercompany invoices and payments. - IC sales and IC purchases. - IC asset transfers. - IC ledger settlements. The reconciliation typically takes weeks before year-end and surfaces discrepancies that require correction journals before close. ## Statutory and audit Year-end produces: - **Financial statements** — balance sheet, P&L, cash flow, equity statement. - **Notes and disclosures** — for statutory reporting. - **Audit packages** — for external auditors. - **Tax provision** — year-end tax accruals and corporate tax calculations. - **Country-specific year-end filings** — VAT annual returns, corporate income tax, etc. For multi-entity groups, **consolidation** at year-end produces group financial statements with eliminations and currency translation. ## Period and year permissions After closure, posting in the closed year is restricted to specific user roles. Re-opening a closed year is possible but should require governance approval and trigger audit-trail events. **Common pitfalls.** - **Trying to close before reconciliations complete** — produces wrong opening balances; expensive to fix. - **Forgetting subsidiary year-end alignment** — different fiscal years across entities create consolidation complexity. - **Insufficient retained-earnings configuration** — wrong account picks, single retained-earnings for multi-dimension structures that need separate ones. ## Operational reality Year-end is mostly a monthly close at scale. Disciplined monthly close means year-end isn't a special panic — it's just December's month-end plus the closing routine. Build the discipline year-round. ## Where to go next The routines that recur every period are in [periodic processes in F&O](https://www.solvingdynamics365.com/guides/periodic-processes-in-f-and-o); the calendar they run against is [fiscal calendar setup](https://www.solvingdynamics365.com/guides/fiscal-calendar-setup-in-f-and-o). Sub-ledger year-ends are covered in [fixed assets in F&O](https://www.solvingdynamics365.com/guides/fixed-assets-in-f-and-o) and [consolidations in F&O](https://www.solvingdynamics365.com/guides/consolidations-in-f-and-o), and the reporting pack in [finance reporting tools](https://www.solvingdynamics365.com/guides/dynamics-365-finance-reporting-tools).