Integration methodAPI (API31 + subscription key)DirectionSend + ReceiveMinimum subscriptionProfessionalContract requiredYes (via sales)Connect 4PS Business Central with eConnect in 2026 via an API connection. This requires a contract with API rights and a subscription key received from eConnect sales.
Before you start
- An active eConnect account with at least a Professional subscription
- A contract with eConnect for API rights, including subscription key
- An activated organisation on the eConnect platform
- Administrator access to your 4PS Business Central environment
Setting up the connection
Step 1: Create connection keys
Create connection keys in the eConnect platform. Follow the steps in Create connection keys.
Step 2: Configure in 4PS Business Central
- Go to the eConnect document exchange settings in 4PS Business Central.
- Select API31 as the Connection type.
- Enter the following details:
- The connection keys (App Key and Secret)
- The eConnect Company ID (found under Organisations on the platform, starts with "XC...")
- The subscription key received from sales
- Click Test connection to verify everything is configured correctly.
If the test fails
Check that the "Generic web service namespaces" are correctly filled in:
- Prefix:
soapenv - Namespace:
http://schemas.xmlsoap.org/soap/envelope/
Step 3: Configure the customer card for sending
To send sales invoices, an identifier (CoC number, GLN or VAT number) is mandatory on the customer card.
- Open the customer card in 4PS Business Central.
- Set up the e-invoicing data in the Sales section.
Connection via the PSB (new integration path)
In addition to the API31 connection described above, a newer integration path is available via the eConnect PSB (Peppol Service Broker). This path uses the eConnect extension in Business Central and Microsoft Entra ID for authentication. The legacy path (API31 + subscription key) remains fully supported.
Preparation
Before you start, you need the following:
- The username of the person setting up the connection
- Organisation names and CoC number (or other company number)
- Someone with global admin or super admin rights must be available
- Check in advance whether the eConnect extension may be installed (some organisations only allow this outside business hours)
It helps to have the customer go through the settings in advance until the screen showing no partyIds are linked. Sometimes an Entra ID admin needs to grant permission to log in to eConnect first, which can also be arranged in advance.
Step 1: Install the extension
- Open Business Central and search for Extension Management using the search bar.
- Search for "eConnect" and install the extension via the three dots.
Step 2: Configure the extension
- Click the eConnect Peppol link and tick HttpClient requests.
- Under PSB Environment choose the correct environment (acceptance for testing, production for live use).
- Click Connect to the eConnect PSB.
- Log in with your Microsoft Entra ID account. This account must have sufficient rights for the BC API.
- On the first login, a screen appears showing that partyIds are not yet linked. At that point, contact TechSupport, who will link the partyIds. Then log in again (preferably in an incognito session).
- Select the organisation name and verify the settings. Sending via Peppol must be ticked.
Step 3: Configure the sending profile
After setting up the extension, you need to configure the sending profile. This determines how invoices are processed after posting.
DefaultYes / NoThe default profile is used when no sending profile is set on the customer card. Usually do not set this as default, as it causes problems for customers without Peppol support.Processing ModeManual / AutomaticWith Automatic, the invoice is offered and validated before posting when booking (errors are still correctable). With Manual, the invoice cannot be changed after posting and you need a credit note for errors.XMLPorts(optional)Custom mapping of BC fields to e-invoice XML. The eConnect mapping is set by default.Step 4: Configure the customer card
On the customer card, set up e-invoicing per customer:
- Set the sending profile to eConnect. In 4PS, this is sometimes a hidden field; find it via "personalise".
- Set "electronic invoicing" to Document sending profile (not "eVerbinding", which belongs to the old connection).
- Enter the Endpoint ID in full including the schemeID, for example
0106:12345678. - If a different ID must appear on the invoice (such as a GLN or VAT number): enter an identifier in Legal ID with a schemeID that does not start with a 9.
- Make sure the "your reference" or "external document number" fields are filled in. These are used as BuyerReference or order number.
Incoming via Autopilot
The connection for incoming invoices is set up via the Autopilot in the eConnect platform. You need a platform user with access to all organisations and a user with admin rights in Business Central. See Autopilot: automatically import invoices for the steps.
Frequently asked questions
What is the difference between the API31 connection and the PSB connection?The API31 connection uses connection keys and a subscription key, and is the original integration path. The PSB connection is newer, uses the eConnect extension in Business Central and Microsoft Entra ID for authentication. Both paths are fully supported.
How do I receive purchase invoices in 4PS Business Central?Incoming invoices are connected via the Autopilot in the eConnect platform. You need a platform user with access to all organisations and a user with admin rights in Business Central. The Autopilot automatically forwards invoices to your administration.
What if the connection test in 4PS Business Central fails?Check that the generic web service namespaces are correctly filled in (prefix: soapenv, namespace: http://schemas.xmlsoap.org/soap/envelope/). Also verify that the connection keys, Company ID and subscription key are entered correctly.
Need help with the connection? Contact support.
Connect your administration