What is SLinkHub?

SLinkHub is a Microsoft Dynamics 365 Business Central extension that connects Business Central to SLinkHub for sending and receiving electronic invoices over the Peppol network. It plugs into Microsoft's built-in E-Document framework, so documents flow through the standard Business Central experience — no separate portal is required for day-to-day invoicing.

SLinkHub is published on Microsoft AppSource by INFIVEX and runs on Business Central online (Cloud).

One app, a profile per country

SLinkHub is a single app for every country. The country-specific part — which identifier a company is addressed by on Peppol, and which local rules apply — is a row on the SLink Country Profiles page. Profiles for Belgium, France, the Netherlands, Germany, Spain, Greece, the United Kingdom and Singapore ship with the app; every other country uses a general profile that you can adjust. Your company's country picks the profile, so there is nothing extra to install.

Requirements

Dependencies

SLinkHub relies on two Microsoft apps. On AppSource they are resolved and installed automatically:

E-Document Core — version 28.0.0.0 or later (Microsoft)
Business Foundation — version 28.0.0.0 or later (Microsoft)

Installation

1. Open the marketplace

In Business Central, search for Microsoft AppSource Apps (or open Extension Management and choose Manage → Microsoft AppSource Gallery).

2. Install SLinkHub

Search for SLinkHub and choose Install. Business Central installs the required Microsoft apps first.

3. Verify

Open Extension Management and confirm SLinkHub by INFIVEX shows as Installed.

4. Assign permissions

Assign the permission set INFIVEX.SLink to the users who work with SLinkHub.

Configuration — getting started

1. Enter the connection

Open the SLink Setup page, enter the API key from your SLinkHub account and use Test Connection to check it.

2. Check the country profile

Open SLink Country Profiles and check the profile for your company's country, including which field holds the company identifier.

3. Configure the E-Document Service

Create an E-Document Service with document format SLink and service integration SLink, and select the document types to send.

4. Set the sending profile

Use the service in a Document Sending Profile, assign it to the customers you invoice electronically, and post a test invoice. Its status appears in the E-Document log.

Country specifics

Belgium

Companies are addressed by their Enterprise Number under Peppol scheme 0208. Where Business Central has no Enterprise Number field, it is derived from the Belgian VAT number.

France

Companies are addressed by their SIREN under scheme 0225, taken from the SIREN field or derived from the VAT number. The French e-invoicing regime is included: the BT-23 cadre de facturation on customers and documents, the lifecycle statuses of each invoice, and payment reporting. Check your SIREN/SIRET and the French settings on the SLink Setup page before going live.

Netherlands, Germany, Spain, Greece and the United Kingdom

Companies are addressed by their VAT registration number: scheme 9944 (NL), 9930 (DE), 9920 (ES), 9933 (GR) and 9932 (GB). Public-sector routing codes, such as the German Leitweg-ID or the Spanish DIR3 codes, are kept per customer as routing codes.

Singapore

Companies are addressed by their UEN under scheme 0195, kept in the Registration No. field. The UEN is validated before it is used.

Other countries

Other countries use the general profile. Ask us which Peppol scheme applies and adjust the profile on the SLink Country Profiles page.

VAT number check (VIES)

With Enable VIES Validation switched on in SLink Setup, customer, vendor and contact cards get a VIES Search (SLink) action. It looks up the card's VAT number in the European Commission's VIES service, warns when another customer, vendor or contact already holds the same number, and on Apply to Record fills in the registered name, address and VAT number. The action is not shown for companies in Asia, or when Finly is installed, since Finly brings its own VIES search.

Troubleshooting

An invoice is stuck or fails to send

Open the E-Document entry and review the error and status log, and the SLink Integration Log. The most common causes are a missing or invalid Peppol identifier on the customer, or an API key that has not been entered on the SLink Setup page.

The app will not install

Confirm your Business Central environment is version 28 or later and that the Microsoft E-Document Core and Business Foundation apps are available. On AppSource these install automatically.

Peppol identifiers are rejected

Verify that the company and the customer or vendor have a valid identifier for the country's scheme (see Country specifics above), and that the country profile reads it from the field where you keep it.

Developer & API Documentation

SLinkHub also exposes a REST API for integrating with your own systems. The interactive reference is available online:

API Reference: api-dev.slinkhub.net/scalar/v1
OpenAPI Spec: api-dev.slinkhub.net/openapi/v1.json
Authentication: X-Api-Key header

Contact Support

For questions not covered here:

Please include your company name, the SLinkHub version (shown in Extension Management, for example 2.7.0.10), your Business Central environment, and a description of the issue. Screenshots of the E-Document log are helpful.