A native Microsoft Dynamics 365
Business Central integration.
Bidirectional sync, with four-eyes on the workflows that move money. One of several ways Elevate Approvals connects to your systems of record.
Read existing data. Write approved records. Gate the sensitive ones.
Read existing master data
Lookup tables sync from Business Central into Elevate Approvals. Payment terms, currencies, countries, posting groups, and reference data appear in the form so requestors and counterparties pick the values that already exist in your tenant.
Write approved records back
When a request reaches final approval, Business Central picks it up via a scheduled job queue and creates the record. If creation fails, the system logs the error and lets you retry after correcting the data.
Gate the workflows that move money
Four-eyes on the workflows that change a vendor bank account, a customer credit limit, or payment terms; the requester cannot approve their own request. The new value never reaches the production record until an independent approver signs off.
Three layers. One controlled path into Business Central.
The Web Portal hosts the request and approval experience. The Approval Engine runs the workflow. The Business Central Connector reads master data and writes back the approved record. Microsoft Entra ID secures every layer.
Web Portal
The interface where requestors raise approvals, approvers act on them, and admins configure forms and workflows. Suppliers and customers use a separate, scoped form view, no portal access required.
Approval Engine
The workflow runtime. Single, group, quorum, conditional, and four-eyes patterns. Out-of-office delegation. Authentication via Microsoft Entra ID. Database-per-tenant isolation.
Business Central Connector
A native extension installed in your Business Central environment. Handles the lookup sync and the write-back, surfaces errors, and gives BC a controlled path back to the approval record.
Elevate Approvals to Business Central architecture: Web Portal, Approval Engine, BC Connector
Field changes are covered. Record creation is not.
Standard Business Central approvals cover field changes after a record exists. They do not cover record creation, and they do not bring the counterparty into the process. Elevate Approvals handles those two cases: a counterparty-facing form for the supplier or customer to complete, and four-eyes (no self-approval) on the workflows that move money once records are live. The two patterns coexist; Elevate Approvals fills the gap before the record exists and on the sensitive workflows after it does.
Catch the change before the consequence.
Approve a new vendor before it lands
The supplier completes onboarding through a secure link. Internal approvers review the record, with four-eyes on the bank account from the first submission. The vendor is created in Business Central only after every gate clears.
Gate a vendor bank account change
A change to an existing vendor bank account is held in Elevate Approvals. Both the original and proposed values are visible to a second approver. The new bank account never reaches Business Central until two authorised users have signed off and the audit trail is recorded.
Gate a customer credit limit change
Increases above your nominated threshold route through a credit-check step and a four-eyes approval. The change writes back to Business Central with the approver, the timestamp, and the reasoning attached.
Layer Elevate Approvals into your Business Central engagements.
Implementation partners can offer Elevate Approvals as a master data approval layer on top of an existing Business Central rollout. Open APIs, partner-led implementations, and no channel conflict. Elevate Approvals sells the platform; partners deliver the engagement.
Three steps from install to live workflow.
Install the Business Central extension in your tenant. Authentication is wired through Microsoft Entra ID, reusing your existing identity setup.
Pick the records you want to gate (vendors, customers, items, journals, custom entities) and map their fields, including the sensitive ones that trigger four-eyes.
Use the visual workflow builder to design the routing your scenario needs. Single-approver and four-eyes ship on every plan; the Advanced Workflows add-on unlocks group, quorum, conditional, and field-routed steps. Publish, test with a sample request, then go live.
Questions we hear about Business Central.
Six answers covering scope, timing, and how Elevate Approvals fits alongside the standard Business Central approval features you already have.
Do I need Microsoft Dynamics 365 Business Central to use Elevate Approvals?
No. Elevate Approvals is a master data approval platform that connects to any ERP, HRIS, or CRM through REST APIs and webhooks. Microsoft Dynamics 365 Business Central is one of several systems you can connect to, and the only one with a native bidirectional integration today.
Can I add Business Central later?
Yes. You can start with REST and webhooks against a different system of record and add the Business Central native integration later, without rebuilding your workflows. The forms, approval logic, and audit trail carry over.
How is this different from standard Business Central approvals?
Standard Business Central approvals cover field changes after a record exists. Elevate Approvals covers the gap before the record exists, including counterparty-facing onboarding forms, and applies four-eyes (the requester cannot approve their own request) on the workflows that change vendor bank accounts, customer credit limits, and payment terms once records are live. The two patterns coexist; Elevate Approvals handles record creation and sensitive-workflow gating, native approvals handle the rest.
Is the integration bidirectional?
Yes. Elevate Approvals reads existing master data from Business Central so requestors and counterparties pick the values you already use, and writes the approved record back when every gate clears. Failed creations are logged and retryable.
Is Elevate Approvals listed on Microsoft AppSource?
Not at launch. AppSource publication is a path we may take in future, but the integration does not require it. The connector installs as a Business Central extension directly, with authentication via Microsoft Entra ID.
Who typically implements the Business Central integration?
Most Business Central implementations are partner-led. If you already work with a Business Central implementation partner, they can layer Elevate Approvals into the engagement. If you do not, we will introduce you to one. Either way, contact us to start the conversation.