Connect D365 BC via the Autopilot and AppSource extension for automatic invoice processing.
Connect Dynamics 365 Business Central (D365 BC) 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 Posted Sales Invoices > Invoice > Activity Log.
When a purchase invoice arrives in Business Central via eConnect, the vendor is automatically looked up using the identifiers in the invoice. The lookup order is:
VAT_Registration_NoRegistration_NumberNoThe extension first searches by VAT number. If no match is found, it tries the Chamber of Commerce number, then the IBAN. If none of the identifiers yield a match, the invoice is not posted.
Note: If the vendor does not exist in Business Central, it will not be created automatically. The invoice will fail with an error message. Create the vendor manually in Business Central first.
When a vendor is found, the extension also checks whether the bank accounts provided (including any G-accounts) are registered with that vendor's linked bank accounts.
When setting up the BC extension, you are redirected to the Autopilot Connect web page, where logging in with a Microsoft Entra ID account is required. This account is also used to call the BC environment via the API, and therefore needs sufficient rights and a BC licence.
After logging in, a user is automatically created in the eConnect identity server with login type "Business Central Azure Active Directory". TechSupport then manually assigns the tenantId and partyIds. Multiple partyIds can be linked to a 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 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 from an App Registration. This is particularly suitable for posting purchase invoices. There is currently no UI for this flow; TechSupport sets this up via the API.
The steps are as follows:
baseUrl via the Management API (Update Attributes). If necessary, 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 in the invoice (VAT number, Chamber of Commerce number or IBAN). Check that the vendor is correctly set up and that the VAT number, Chamber of Commerce number or IBAN matches the details in 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 registered as a bank account with the relevant vendor. This occurs with organisations using the Idyn extension for G-accounts. Register the G-account number as a bank account with 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 installing the eConnect extension, this transaction type is normally created automatically. For older versions, you need to 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 correctly configured. 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 "Page is currently unavailable""} A BC licence is likely missing for the user trying to make the connection. Refer the customer to their BC partner (e.g. Databalk) to check the licence assignment. ::
This error comes from Microsoft Business Central, not from eConnect. The document has usually already been processed. Check in Business Central whether the invoice has been posted. If the problem persists, contact your BC partner to increase the API limits.
The integration has become corrupted, usually due to a previous installation or uninstallation of the eConnect app. Contact eConnect support to remove the old connection and create a new one.
The connection configuration has the action set to "booking" instead of "autobooking". Contact eConnect support to correct this via the Management API.
Want to know more about the Autopilot? Read how the Autopilot works.
Start the integration
You need a Basic subscription with eConnect. You also need the eConnect app (free) from the BC AppSource. The integration works via the Autopilot.
Yes, you can connect multiple Business Central environments. For each environment, you create a separate Autopilot connection in the eConnect platform. Use unique credentials for each environment.
eConnect tries to match the vendor in Business Central via a fixed lookup order: first the VAT number, then the Chamber of Commerce number, and finally the IBAN. If none of these identifiers yields a match, the invoice is not automatically posted but fails with an error message. You can then create the vendor manually in Business Central, after which the document can be resubmitted.