Business Central automation
Runtara automates the work between Microsoft Dynamics 365 Business Central and the systems around it. Orders, invoices, and item records move in and out of Business Central through workflows that hold exceptions for a person before anything is written.
01 / Workflows
What you can automate.
Customer orders into Business Central
Customer orders that arrive by email, PDF, EDI or API become Business Central sales orders, with exceptions held for a person.
Invoice matching
Match supplier invoice lines against purchase orders and receipts in Business Central, hold variances for approval, and post the approved values.
Orders to the warehouse
Push orders from Business Central to a warehouse system such as Extensiv WMS, and carry shipment status back.
Item and product data
Compare item records in Business Central with your storefront, apply the rule for each field, and route ambiguous differences for review.
GPO reconciliation
Reconcile supplier reports and invoices against contracts, member rosters and expected revenue, with Business Central as the system of record.
02 / Connection
How the connection works.
Runtara connects to Business Central through a Microsoft Entra app registration with client credentials. You configure the tenant, client credentials, scope, authority host, and the Business Central API base URL once, as a reusable Microsoft Entra connection.
Each workflow step declares the connection it uses. The runtime checks every outbound call against that declaration and denies anything else, so a workflow built to read purchase orders cannot reach an undeclared system.
03 / Approval
Writes wait for a decision.
In the illustrative invoice run INV-0847, five lines match purchase order PO-4471 and goods receipt GR-8832. Line 04 carries a $1,240 variance and is held. Weeks later, a person approves it, and the workflow posts the approved invoice to Business Central.
The run waited at its last committed step the whole time, so nothing before the approval was repeated. One query against the instance database returns the extraction, the match, the approval, and the Business Central response.
On Runtara-managed Cloud, in a US or EU region, or on infrastructure you manage. Either way, model calls use your own provider account. See the security model.
04 / Availability
In every edition.
Business Central is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans
- Open-source engineAGPL-3.0, run and operate it yourself.Included
- CloudWe host and manage your instance.Included
- EnterpriseYour cloud or on-premises, supported by our team.Included
05 / Questions
Common questions.
Is Business Central included in my plan?
Yes. Business Central is a standard integration, included in Cloud, Enterprise and the open-source engine. The field mappings for your setup are scoped and quoted as part of implementing each process.
How does Runtara connect to Business Central?
Through a Microsoft Entra app registration using client credentials. You configure the tenant, client ID and secret, scope, authority host, and the Business Central API base URL. The same connection type works with Microsoft Graph and other Entra-protected APIs.
Can a person approve before anything is written to Business Central?
Yes. A workflow can hold a record for approval and write only after the person decides. The run keeps the source, the decision, who made it, and the Business Central response together.
What if an approval or a Business Central call takes a while?
Each completed step is committed, so a run waiting for a person, or retrying a call, resumes from where it stopped without repeating the matching or the approval.
Does Business Central need a custom extension?
Sometimes. Business Central's standard API is limited, so some processes need a custom Business Central extension. We scope that during implementation.
Which other ERPs do you work with?
Our team has integrated Odoo, QuickBooks, Infor CSD/SX.e, Epicor Prophet 21 and Epicor Eclipse. Other ERPs that expose an API, EDI or file exchange are scoped during implementation.
Bring your Business Central process.
Show us the records, the systems on either side, and the exceptions your team handles today. We will scope a first workflow.
All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.