Does Procurement VMS integrate with Dynamics 365 Business Central?
Procurement VMS lists Dynamics 365 Business Central among its supported integrations. A Business Central procurement integration connects through the Business Central API v2.0, authenticates with Microsoft Entra ID and OAuth 2.0 1, and keeps vendors, purchase orders and purchase invoices aligned between the two systems.
In Business Central, a purchase order that is raised outside the system and keyed in afterward leaves the approval somewhere else: a mailbox, a Teams thread or a spreadsheet. The person posting the invoice rarely sees who agreed to the spend.
In a connected setup, the request is approved first and Business Central receives the approved order. Receipts and purchase invoices then match against it inside Business Central, where finance already works.
What syncs between Dynamics 365 Business Central and Procurement VMS?
Procurement VMS and Business Central each own different records. The table shows the data most Business Central procurement integrations touch and the usual direction. The final mapping depends on your companies and dimensions.
| Data | Dynamics 365 Business Central record | Direction | When | Notes |
|---|---|---|---|---|
| Vendorsconfirm | vendors | Dynamics 365 Business Central → Procurement VMS | On change and on a schedule | Business Central stays the vendor of record. The API v2.0 exposes vendors as a standard entity 3. |
| Approved purchase ordersconfirm | purchaseOrders | Procurement VMS → Dynamics 365 Business Central | When the last approval clears | Created in the company the order belongs to. |
| Receiptsconfirm | purchaseReceipts | Dynamics 365 Business Central → Procurement VMS | When goods are received | Receipt data supports matching against the order and the invoice. |
| Purchase invoicesconfirm | purchaseInvoices | Two-way | When an invoice is entered or posted | Calls are scoped to a company, for example companies({companyId})/purchaseInvoices 3. |
| Dimensionsconfirm | dimensions, dimensionValues | Dynamics 365 Business Central → Procurement VMS | On a schedule | Drive coding and approval routing. |
How the Dynamics 365 Business Central connection works, step by step
Setup is split between a Microsoft Entra administrator, a Business Central administrator and the Procurement VMS team. Microsoft requires Entra authentication for production 1.
- Register an application in Microsoft EntraRegister an app in your Entra tenant for authenticating API calls to Business Central 2.Entra administrator
- Grant the Business Central API permissionsGrant the registered application the API.ReadWrite.All and Automation.ReadWrite.All permissions for Dynamics 365 Business Central 2.Entra administrator
- Register the application inside Business CentralOpen the Microsoft Entra applications page in Business Central and set the application up there. Without this step the calls will not be accepted 2.Business Central administrator
- Choose the environment and companyThe environment name is part of the endpoint, and calls are made against a company 13. Decide which environments and companies the sync covers.Business Central administrator
- Map dimensions and posting setupMatch dimensions and the purchasing setup that orders will use before the first order is sent.Finance
- Trace one order end to endFollow a single order through approval, receipt and invoice in a sandbox environment, then repeat in production.Everyone above
Who this fits
Business Central serves small and mid-sized companies, and the number of companies and environments is what changes the work.
SMB · fits
One company, one production environment and a small approver group. Start with vendors and approved purchase orders, then add receipts and invoices.
Mid-market · fits
Several companies and a sandbox that mirrors production. Plan the mapping per company, and plan the Entra registration once rather than once per company.
Enterprise
Large groups with complex finance usually run Dynamics 365 Finance. See that page if you are comparing.
Who does what
What to plan for in Dynamics 365 Business Central
These come straight from Microsoft's documentation. Check all of them before the first sync.
Production needs Entra, not access keys
Basic authentication with a web service access key exists for development, but Microsoft states that production must use Microsoft Entra ID and OAuth 2.0 1.
Two registrations, not one
Service-to-service access needs an Entra app registration with API permissions, and then the same application set up inside Business Central 2. Missing the second step is an easy way to get rejected calls.
Environment and company are part of every call
The endpoint includes the environment name, and calls run against a company 13. A sandbox and a production environment need separate setup and separate testing.
On-premises is configured differently
Business Central on-premises has to be configured for Entra authentication with OpenID Connect, and its valid audiences must include the Business Central API endpoint 2.
Decide where approval livesverify source
If Business Central's own purchase approval workflow is in use, pick one system as the authority. Otherwise every order is approved twice.
Security and access
Microsoft requires Entra-based authentication for production, which ties the integration to your existing identity controls.
- Production access uses Microsoft Entra ID and OAuth 2.0 12.
- The application is granted specific Business Central API permissions in Entra, and then registered again inside Business Central 2.
- Calls are scoped to an environment and a company, which limits what a single call can reach 13.
- Procurement VMS describes its own security posture as SOC 2 Type II aligned and CCPA compliant, with role-based access control 4. Ask for current security documentation during scoping.
Related integrations and guides
Other systems in the same category, and the workflow guides that explain the processes this connection touches.
Dynamics 365 Business Central integration FAQ
Yes. Dynamics 365 Business Central is in Procurement VMS's published list of supported integrations. What moves in each direction is scoped against your Dynamics 365 Business Central setup.
Typically vendors, approved purchase orders, receipts, purchase invoices and dimensions. Direction is set per record type. The table above shows the proposed split.
Scope sets the timeline: what moves, whether it moves one way or both, and how much mapping your Dynamics 365 Business Central setup needs. Procurement VMS states that the platform as a whole typically goes live in 4 to 8 weeks 4. The Dynamics 365 Business Central connection is scoped within that timeline.
Only for development. Microsoft states that production must use Microsoft Entra ID and OAuth 2.0 1.
The API v2.0 exposes standard entities such as vendors, purchase orders and purchase invoices, scoped to a company 3.
Sources and how this page was verified
Facts about Dynamics 365 Business Central on this page were checked against Microsoft's documentation on the date shown. Where only third-party integration documentation covers a behavior, the source is labelled third-party. Statements about Procurement VMS come from the company's published integration list; anything beyond that is confirmed with the product team before publishing.
- Microsoft Learn: Get started developing Connect apps for Dynamics 365 Business Centralvendor documentation
- Microsoft Learn: Automation APIs using service-to-service authenticationvendor documentation
- Microsoft Learn: Business Central API v2.0 referencevendor documentation
- Procurement VMS: platform overview and integration listProcurement VMS
Dynamics 365 Business Central is a trademark of Microsoft or its affiliates. Procurement VMS is not affiliated with, sponsored by or endorsed by Microsoft. Platform names are used only to describe compatibility.