Connecting Business Central
Connect Business Central to Orbit so completed Orders can be submitted as invoice drafts.
Orbit MissionControl
View as MarkdownWas this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Connect Business Central to Orbit so completed Orders can be submitted as invoice drafts.
Was this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Connect Business Central to Orbit to submit invoice drafts for completed Orders. You can test the connection, choose a company and decide when automatic submission is active.
Open Accounting integrations
In Orbit MissionControl, open Settings → Accounting → Integrations.
Add the integration
Select Add integration.
Choose Business Central
Choose Microsoft Dynamics 365 Business Central.
Choose a login method
Under Login, choose Official Orbit Connector (Recommended) or Own App Registration. The Orbit connector uses an app managed by Orbit and does not require your own secret.
Enter your app details
For your own app registration, enter its Client ID and Client Secret. Enter the secret value, not its secret ID. Orbit stores the value securely and does not show it again. You can set Client secret expires on to receive an expiry warning.
Enter the directory details
Enter the Business Central Tenant ID in the displayed 8-4-4-4-12 format.
Enter the environment name
Enter Environment exactly as it appears in the Business Central admin centre.
Copy the Orbit connector ID
For the Orbit connector, select Copy beside Orbit Connector Client ID to copy the value when completing the setup in Microsoft Entra.
Create the integration
Select Create to add the integration card.
For the Orbit connector, select Grant Admin Consent. Microsoft opens so an Entra administrator can sign in and grant consent for the directory. When you return to Orbit, the connection is tested automatically. If consent is already recorded but the directory is not verified, select Verify Directory instead. The card shows Consent granted on and Directory verified on dates.
If sign-in is not verified, use the message to choose what to do:
| Message | What to do |
|---|---|
| The account is not an administrator. | Sign in as a Global Administrator, Privileged Role Administrator, Cloud Application Administrator or Application Administrator. |
| The sign-in expired or was already used. | Start the sign-in again. |
| The signed-in directory does not match the integration. | Sign in to the directory configured by the Tenant ID, or correct the Tenant ID. |
| The sign-in was cancelled. | Start the sign-in again and complete it. |
| The sign-in could not be verified. | Start again. If the error continues, contact Orbit support. |
If consent is declined, ask an Entra administrator to grant it.
Remove Binding stops Orbit from calling Business Central for that directory until an administrator verifies it again.
Select Test Connection. A successful test shows Connection Successful and the number of companies found in the environment. You need to choose a company even when the test finds only one.
Choose a company
Select Select Company and choose the company to use.
Use the selected company
Select Use Company.
If the test fails, use the message on the card to choose what to check:
| Connection message | What to check |
|---|---|
| Check the Client ID and Tenant ID. | Confirm both IDs match the app registration and directory. |
| The connector still needs administrator consent, or the directory is not verified. | Ask an Entra administrator to complete the consent and sign-in steps above. |
| The app is not configured in Business Central. | Add or activate it under Microsoft Entra applications in Business Central. |
| Companies could not be loaded. | Check the environment name and test again. |
| No company was found in this environment. | Enter the environment name as shown in the Business Central admin centre. |
| Required permission sets are missing. | Assign the required permission sets in Business Central, then test again. |
| The client secret is incorrect or expired. | Enter the secret value, not its ID. For an expired secret, create a new one and replace it in Orbit. |
| The connection could not be verified. | Check the settings and test again. |
Orbit tests the connection every hour while the integration is active. The hourly test is paused while it is inactive. If an own app's secret is approaching its expiry date, the card shows a warning; select Enter New Secret to replace it.
Select Activate after the connection test succeeds and you have chosen a company. Only one accounting integration can be active at a time, so deactivate another integration first if Orbit asks you to.
Select Deactivate to stop automatic submission. Deactivation does not unlock properties managed by Business Central. To remove the integration, deactivate it first, then select Delete. Deleting releases the managed properties and keeps their values. It does not delete anything in Business Central.
When the integration is active, Customer Number on shippers and Vendor Number on carriers show Managed by Business Central and cannot be edited in Orbit. If a property shows Managed property missing, select Create Again. Activation also adds IBAN, BIC and Bank Name to carriers as editable properties.
On the active integration card, choose Send automatically when an order is completed to submit invoice drafts automatically when an Order is completed. You can select operator users under Report failures to. If none of the selected users can receive the notice, active operator administrators receive it instead.
Categories without an accounting mapping are listed on the card because their line items cannot be sent. Select Open Accounting Categories to review the mappings. For submission details and the Submissions page, see Orders. To configure category mappings, see Accounting categories.
Orbit first uses a customer or vendor number already linked to the shipper or carrier. When it needs to find a record, it matches by VAT ID: one match is linked, no match creates a record, and multiple matches stop submission so you can link the correct record manually. A name alone does not identify a record. See Accounting partner records for linking or creating records in Orbit MissionControl.
No. Deactivate the active integration before activating another one.
They remain locked while the integration exists. Deactivate the integration and delete it to release them; their values are kept.
No. Deleting the integration in Orbit does not delete anything in Business Central.