Dynamics 365 Finance & Supply Chain integration for SaaS companies
Your enterprise customers run Dynamics 365 Finance and Supply Chain Management. Unity connects your product to it through Microsoft's data entities, across every legal entity, under your brand, managed by our team.
- Customers
- Orders
- Invoices
- Payments
- Multiple legal entities
- Financial dimensions
- Cloud or on-premises
- Sandbox and production
Through data entities: Microsoft's business-level views of records such as customers, sales orders and invoices. Real-time flows read and write those entities through OData, a REST API. High-volume flows use Microsoft's Data management package API, which moves records in batches. Unity uses whichever pattern each flow needs, signs in through Microsoft Entra ID, and keeps the integration running through Microsoft's service updates under your brand.
Dynamics 365 records Unity maps for SaaS products
Each map uses Finance and Supply Chain Management's own data entities and rules, so records land in the right legal entity with the right dimensions.
| Dynamics 365 record | Typical direction | What it's used for |
|---|---|---|
| Customers and contacts | Both ways | The companies and people your app bills or serves, kept identical in each legal entity |
| Released products | From Dynamics 365 | Products, SKUs and prices your app quotes or sells against |
| Sales orders | To Dynamics 365 | Orders captured in your app, created in Dynamics 365 for fulfillment |
| Customer and free text invoices | Both ways | Invoices issued in either system, posted under the customer's rules |
| Customer payment journals | To Dynamics 365 | Payments collected in your app, applied against open customer invoices |
| Vendors and vendor invoices | Both ways | Suppliers and bills for AP, spend and procurement platforms |
| General journals and financial dimensions | To Dynamics 365 | Journal entries tagged with the dimensions finance reports on, such as department, cost center or project |
| Custom fields | Both ways | Fields your customer's partner added through extensions, reached through extended or custom data entities |
The right Microsoft API for each flow
Finance and Supply Chain customers run large volumes across many legal entities. Unity picks the integration pattern Microsoft recommends for each job.
OData for real time, batches for volume
Microsoft positions OData for real-time flows of a few thousand records an hour, and its batch Data management API for anything larger. Unity uses OData for day-to-day sync and the batch API for initial loads and high-volume flows.
Secure sign-in with Microsoft Entra ID
Unity connects as a Microsoft Entra application that your customer registers in Finance and Supply Chain Management and maps to a dedicated service user. The roles on that user decide exactly what the integration can see and change.
Every legal entity, explicitly
Dynamics 365 returns only the default company unless an integration asks for others. Unity targets each legal entity by name, so records never land in the wrong company.
Cloud and on-premises
On-premises deployments support only Microsoft's Data management package API. Unity supports both cloud and on-premises customers, using that API on-premises.
Dynamics 365 problems we've already solved
These are the issues that stall do-it-yourself Finance and Supply Chain integrations, and how Unity handles each one.
Records land in the default legal entity
An OData call without a company filter reads and writes only the service user's default company. Unity sets the legal entity on every call, so multi-company customers stay clean.
Busy environments return "Too Many Requests"
Dynamics 365 throttles integrations when the environment is under load and tells callers when to retry. Unity follows those retry signals, and your customer can raise the integration's priority in the throttling priority settings.
Postings fail on a dimension rule
Account structures decide which dimensions each account needs. Unity maps each customer's financial dimensions per legal entity and raises a case with Microsoft's own message when a combination is invalid.
Knowing what changed without constant polling
Dynamics 365 business events can notify integrations when key records change. Unity subscribes to them where they fit, so changes reach your app quickly without heavy polling.
Which SaaS products connect to Dynamics 365 Finance & Supply Chain?
Payments and accounts receivable
Pull open customer invoices into your platform, collect payment, and post the payments back through customer payment journals so invoices settle themselves.
Transportation management (TMS)
Send sales orders and shipments from Dynamics 365 to your TMS for load planning, then return carriers, tracking numbers and actual freight costs so invoices carry the real shipping charge.
AP automation and spend management
Sync vendors, push approved vendor invoices to Dynamics 365, and return payment status to your app.
Ecommerce, CPQ and order management
Read released products and prices from Dynamics 365, then create sales orders the moment a customer buys.
Field service and support
Keep customer and asset records aligned, and send billable work back to Dynamics 365 for invoicing.
Unity is a managed integration service for SaaS companies, built on the Intelligrate iPaaS. We build your Dynamics 365 integration, put your brand on it, monitor it, fix errors and handle Microsoft's updates. Integration updates can even flow into your own help desk. See how Unity works for SaaS.
Dynamics 365 Finance & Supply Chain integration questions
How does Unity connect to Dynamics 365 Finance and Supply Chain Management?
Through Microsoft's data entities. Real-time flows use OData, a REST API, and high-volume flows use the Data management package API, which moves records in batches. Both are standard Microsoft interfaces, so the integration stays supported through every service update.
How does Unity sign in to our customers' environment?
As a Microsoft Entra application. Your customer registers it under System administration in Finance and Supply Chain Management and maps it to a dedicated service user. That user's security roles control what the integration can access, and the customer can revoke it at any time.
Can one integration cover several legal entities?
Yes. Unity addresses each legal entity explicitly, so a customer with many companies is served by one integration, with each company's data kept separate.
Will the integration slow down our customers' Dynamics 365 environment?
No. Dynamics 365 throttles integrations when an environment is busy and tells them when to retry. Unity respects those signals and moves large volumes through Microsoft's batch API instead of thousands of individual calls.
Do you support on-premises Dynamics 365 Finance and Supply Chain?
Yes. On-premises deployments support Microsoft's Data management package API, and Unity uses it for those customers.
Can Unity map custom fields and financial dimensions?
Yes. Financial dimensions are mapped per legal entity, and custom fields added through extensions are reached through extended or custom data entities.
How long does a Dynamics 365 Finance and Supply Chain integration take?
A first integration typically goes live in ten to sixteen weeks. Each new customer after that is mostly configuration, since the maps are already built.
Your customers run other ERPs too
- All Unity integrations for SaaS
- SAP Business One
- All Microsoft Dynamics integrations
- Microsoft Dynamics 365 Business Central
- Microsoft Dynamics GP
- Epicor Prophet 21
- All Epicor integrations
- Epicor Kinetic
- Infor SyteLine / CloudSuite Industrial
- All Infor integrations
- Infor VISUAL
- Infor LN
- Infor M3
- Infor SX.e
- Infor XA
- NetSuite
- Acumatica