Connect D365 BC via the Autopilot and AppSource extension for automatic invoice processing.
You connect Dynamics 365 Business Central (D365 BC) in 2026 with eConnect via the Autopilot and the official AppSource extension "eConnect Peppol e-invoicing & OCR+". Invoices are automatically sent and received, including posting suggestions for purchase invoices.
If you want to automatically post purchase invoices, configure the Autopilot from the eConnect platform:
There are two options for sending sales invoices:
Purchase invoices received via eConnect are automatically placed in your Business Central administration via the Digital Mailbox or the Autopilot.
Tip: The Activity Log of an invoice provides detailed information about communication with the PSB. Go to Geboekte verkoopfacturen > Factureren > Activity Log.
When a purchase invoice arrives via eConnect in Business Central, the vendor is looked up automatically using the identifiers on the invoice. The search order is:
VAT_Registration_NoRegistration_NumberNoThe extension searches by VAT number first. If no match is found, it tries the Chamber of Commerce number, then the IBAN. If none of the identifiers match, the invoice is not posted.
Note: If the vendor does not exist in Business Central, it is not created automatically. The invoice then fails with an error message. Create the vendor manually in Business Central first.
For a matched vendor, the extension also checks whether the bank accounts supplied on the invoice (including any G-accounts) exist among the bank accounts linked to that vendor.
When setting up the BC extension, you are redirected to the Autopilot Connect web page, where signing in with a Microsoft Entra ID account is required. This account is also used to call the BC environment via the API, and must therefore have sufficient rights and a BC license.
After signing in, a user is automatically created in the eConnect identity server with login type "Business Central Azure Active Directory". TechSupport then needs to manually assign the tenantId and partyIds. Multiple partyIds can be linked to a single user. The customer then chooses during setup which partyId is linked to which BC environment.
It is possible to connect multiple Business Central environments, but there are some important rules. Each environment needs a unique partyId. If multiple environments need to send invoices on behalf of the same Chamber of Commerce number, each connection must be made with a different Entra ID account. Each "Business Central Azure Active Directory" user in the identity server must then also have a different tenantId.
There are two pitfalls to watch out for:
As an alternative to Entra ID authentication, you can also authenticate via Client Credentials of an App Registration. This is particularly suitable for posting purchase invoices. There is currently no UI for this flow; TechSupport configures it via the API.
The steps are as follows:
baseUrl via the Management API (Update Attributes). Additional additionalQueryParameters may also need to be set.referenceKey parameter is a Base64-encoded string with the format businesscentral_{contextId}_{tenantId}_{connectionId}.Contact support if you want to use this authentication method.
::e-accordion-item{value="item-1" header=""API400 Could not retrieve vendor ids""} The vendor was not found in Business Central based on the identifiers on the invoice (VAT number, Chamber of Commerce number or IBAN). Check that the vendor is set up correctly and that the VAT number, Chamber of Commerce number or IBAN match the details on the invoice. ::
::e-accordion-item{value="item-2" header=""BCNotFound: Internal_InvalidTableRelation ... G-Account Code""} The invoice contains a G-account number that is not recorded as a bank account for that vendor. This occurs with organisations that use the Idyn extension for G-accounts. Record the G-account number as a bank account for the vendor in Business Central. ::
::e-accordion-item{value="item-3" header=""BCBadRequest: ... Transaction Type ... ECONNECT""} The value "ECONNECT" does not exist in the Transaction Type table. When you install the eConnect extension, this transaction type is normally created automatically. For older versions you must add it manually: search for Transaction Types in Business Central and add the code "ECONNECT". ::
::e-accordion-item{value="item-4" header=""BCBadRequest: ... VAT Prod. Posting Group""} The VAT product posting group from the invoice does not exist in Business Central. Check that the VAT mapping is configured correctly. During setup, an Excel file (BusinessCentral VAT Mapping) is used to map VAT codes. Add the missing group to the VAT Product Posting Group table. ::
::e-accordion-item{value="item-5" header="Autopilot connection shows "Pagina werkt momenteel niet""} The user trying to establish the connection probably does not have a BC licence. Refer the customer to their BC partner (for example Databalk) to check licence assignment. ::
Want to learn more about the Autopilot? Read how the Autopilot works.
Start the integration
You need a Basic subscription with eConnect. Additionally, the eConnect app (free) is required from BC AppSource. The integration works via the Autopilot.
Yes, you can connect multiple Business Central environments. Per environment, you create a separate Autopilot connection in the eConnect platform. Use unique credentials for each environment.
eConnect tries to match the supplier in Business Central using a fixed search order: first the VAT number, then the Chamber of Commerce number, and finally the IBAN. If none of these identifiers produce a match, the invoice is not automatically booked but fails with an error message. You can then manually create the supplier in Business Central, after which the document can be resubmitted.