Data Panda brings your Dynamics 365 Finance and Supply Chain Management data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Dynamics 365 Finance and Operations is Microsoft's enterprise-tier ERP, the lineage that started as Axapta in 1998 at Danish vendor Damgaard Data, became Microsoft Dynamics AX in 2006, and was rebuilt as Dynamics 365 for Operations in 2016. In 2020 Microsoft split the product into two apps sold separately: Dynamics 365 Finance for the general ledger, receivables, payables, budgeting and close, and Dynamics 365 Supply Chain Management for product, inventory, warehouse, planning and shopfloor. Most people in the ecosystem still say F&O or AX.
This is the tier above Business Central. Groups end up on F&O when they run many legal entities in many countries, need deep multi-currency and global tax localisation, and have manufacturing or distribution at a scale where WMS and production control matter. The data surface is wide: General Ledger and MainAccounts, CustomersV3, VendorsV2, SalesOrderHeadersV2, PurchaseOrderHeadersV2, ReleasedProductsV2, WarehouseIdentifiers and SalesInvoiceHeaders, plus the transactional tables behind them. In a warehouse, F&O becomes the group spine that the CRM, the PIM and the ecom channels line up against without a nightly export job nobody trusts.
One consolidated view across every F&O legal entity, currency and book, not fourteen Power BI workspaces that disagree.
Keep F&O in sync with the CRM, the PIM and the ecom channels without another middleware layer.
Use F&O history for forecasting and anomaly detection that runs on the warehouse, not on the production environment.
Internal tools on F&O data for people who should not pay for an F&O user licence.
A list of concrete reports, automations and AI features we have built on MS Dynamics 365 Finance and Operations (AX) data. Pick the one that matches your situation.
Are our F&O legal entities closing on the same numbers?
Every entity's trial balance, intercompany position and FX translation on one view, reconciled against the group consolidation. Flags the entity whose result is carrying a trend that disappears into the group number before the audit spots it.
Where is the item master drifting between F&O and the shopfloor?
ReleasedProductsV2 attributes, warehouse master data, BOMs and routing versions compared across entities, PIM and ecom channels. Surfaces the SKUs where cost, UOM or handling differs by entity, so the picking errors and the consolidated COGS stop looking like a mystery.
How does a CRM opportunity become posted revenue in F&O?
Salesforce or Dynamics opportunity tracked to an F&O sales order in the right legal entity, shipment, invoice and cleared payment. Elapsed days at each hop reveal where the commercial-to-operational handoff stalls, per rep, product and subsidiary.
Group P&L, intercompany elimination and working capital across every F&O legal entity, without the Excel merge on the fifth. Close stops waiting on the subsidiary controller whose localisation takes the longest to post.
Pipeline-to-order-to-invoice timing per rep, product and entity, tied back to the CRM. Forecast accuracy is checked against F&O posted revenue, not against CRM stage optimism.
Warehouse throughput, shopfloor output, supplier reliability and inventory turns across every entity and warehouse. Planning decisions run on the group view, not on one controller's saved view in F&O.
Closed-won Salesforce opportunities drop into F&O as sales orders in the right legal entity, with customer, item and pricing mapped to CustomersV3 and ReleasedProductsV2. Invoice status, shipment and cash collection flow back to the opportunity, so enterprise sales and group finance read the same cycle.
Dynamics 365 Sales opportunities, accounts and contacts line up with F&O customers, orders and invoices across legal entities. The Microsoft stack runs as one record instead of two tenants where CRM-side names and F&O-side customer IDs slowly drift apart.
Akeneo PIM attributes, variants and enrichment state flow into F&O as ReleasedProductsV2 records with the right units, categories and localisation. Item-master drift between the PIM, F&O and the ecom channels gets caught before it shows up in picking errors or distorted COGS.
Shopify orders land in F&O as sales orders in the legal entity that owns the brand or the region, with items, tax treatment and warehouse assignment in the right place. Refunds post as credit notes. Multi-brand groups stop treating DTC revenue as one number outside the group ledger.
You keep the reporting tool you already have. We connect it to the warehouse where your MS Dynamics 365 Finance and Operations (AX) data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
The primary path is the Data Entities layer, either through the OData endpoint for synchronous reads on entities like CustomersV3, SalesOrderHeadersV2 and ReleasedProductsV2, or through the data-management pipeline for higher-volume async extraction. For groups that already have Export to Data Lake or Synapse Link for Dataverse configured, we consume that feed directly so the extraction cost is not paid twice.
Yes. Since Microsoft split F&O into Dynamics 365 Finance and Dynamics 365 Supply Chain Management as separately licensed apps in 2020, most customers run both on a shared environment. We pull finance entities like MainAccounts and general-ledger postings alongside supply-chain entities like ReleasedProductsV2 and WarehouseIdentifiers so the warehouse has the group ledger and the physical flow in one place.
Every legal entity (DataAreaId), financial dimension and account structure comes across as a first-class column. Reporting can stay per entity for local controllers, roll up to regional or business-line level, or consolidate to group with FX translated at the rates F&O itself used.
We review your MS Dynamics 365 Finance and Operations (AX) setup and the systems around it. Together we pick the first thing worth building.