E-Invoice Platform Setup Reference
This article covers the E-Invoice Platform Setup page: the fields that need a decision, and the actions on it. Choose a field to read a short description of the field or link to more information — the tables below cover only the settings where the choice has consequences.
Connection
| Field | Description | What to choose |
|---|---|---|
| Base URL | The platform API base URL. | Leave the default unless told otherwise. A trailing slash is added automatically. |
| API Key Id | The Basic API key id, the part before the colon. | The key belongs to your team and reaches every company in it. |
| API Secret | Masked when stored. | Type a new secret to replace it; leave the placeholder to keep the current one. |
| Connection Status | Result of the last Test Connection. | Read-only. |
The secret lives outside the database tables and is never returned by any page or API, so it cannot be read back — only replaced or cleared.
Incoming documents
| Field | Description | What to choose |
|---|---|---|
| Inbound Look-Back (Days) | How far back to read the inbox. | 0 uses the default of 30 days. Widen it before a long pause, not after. |
| Track Which Documents Are Read | Uses the platform's read marker so the same entries are not read every run. | On once the inbox is busy. It writes to the platform, where other tools see the marker. |
| Recognize Suppliers on Incoming Documents | Matches an incoming document to a vendor by Peppol endpoint, VAT number or Belgian enterprise number. | On. Without a matched vendor there is no automatic G/L coding at all. |
| Approval for Incoming Documents | What happens to the purchase document an e-document creates. | Send for Approval if approval is a control you rely on; otherwise Leave As Is. |
Two of these are worth restating outside the table. The look-back window is a real cut-off: if receiving is off for longer than the window, older documents are not offered again. And turning on read tracking writes to the platform, so it is not a Business Central-only setting.
Outgoing documents and automatic sending
| Field | Description | What to choose |
|---|---|---|
| Attach PDF to Outgoing Documents | Sends a PDF rendering alongside the structured data. | On if you want receivers to see your layout. Rendering never blocks a send. |
| Auto-Send Enabled | A sweep sends posted documents that have not gone out. | On to stop relying on people pressing Send. |
| Auto-Send From Date | Earliest posting date the sweep considers. | Required. Without it the sweep refuses to run rather than send years of history. |
Reverse charge
| Field | Description | What to choose |
|---|---|---|
| Reverse Charge Reason Code | Sent as BT-121 on documents with a reverse-charge line. | A code from the VATEX list. VATEX-EU-AE covers reverse charge including medecontractant. |
| Reverse Charge Reason | Sent as BT-120 — the legal mention your customer reads. | Wording that matches the ground you actually apply. Construction work under medecontractant needs different wording from an intra-Community service. |
Neither may be empty on a document carrying a reverse-charge line, which is why both ship with a value.
Supplier bank details
| Field | Description | What to choose |
|---|---|---|
| Approved IBAN Action | What approving a supplier bank account does. | Record Only changes nothing on the vendor. Create Bank Account adds it without nominating it. Create and Set Preferred also makes it the account payment suggestions use. |
| Vendor Bank Account Code | Code given to accounts created from an approved e-invoice. | A numeric suffix is added if the code is already taken for that vendor. |
Create and Set Preferred is the setting invoice fraud is aiming for. Choose it only where you trust the approval step completely.
Self-billing
| Field | Description | What to choose |
|---|---|---|
| Self-Billed Document No. | Which number identifies a self-billed document (BT-1). | Own Posted No. is the safe default. Vendor Invoice No. is equally safe for a vendor with a self-billing agreement, because the number then comes from a dedicated number series. |
For a vendor without an agreement, Vendor Invoice No. is a typed value that Business Central does not check for uniqueness.
Official data lookup
Look Up Official Data (VIES) lets customer and vendor cards query the EU VAT register for the official name and address of Belgian parties. It contacts ec.europa.eu, a host outside the e-invoice platform, so it is off until you switch it on.
Indicators
These fields are counts, not settings: Secret Configured, Bank Accounts Awaiting Approval, Applied To Services, Documents Without a Supplier, Documents That Will Not Import, and the This Company group showing which platform company this one sends as and whether its mapping is OK.
Actions
| Action | What it does |
|---|---|
| Test Connection | Lists how many companies your API key can reach |
| Clear Secret | Removes the stored secret; every company stops sending until a new one is entered |
| Reset Base URL to Default | Puts the platform's standard endpoint back |
| Send Pending Documents Now | Runs the automatic sweep once, immediately |
| Fill Peppol Endpoints | Looks up and fills endpoints for Belgian customers and vendors |
| Add Missing Units | Creates a Unit of Measure for every unresolved unit code seen on incoming documents |
| Apply Supplier Recognition to Services | Selects this app's supplier recognition on the e-document services it receives on |
| Platform Documents | Shows what the platform holds, incoming and outgoing |
| Uninstall Impact | Shows what the app would leave behind, changing nothing |
| Prepare for Uninstall | Lists and removes what the app wrote into standard tables |
| Companies, Vendor Bank Approvals, Incoming Supplier Recognition | Open E-Invoice Platform Companies, Vendor Bank Approvals and Incoming Supplier Recognition |
Add Missing Units creates master data, using the code itself as both Code and International Standard Code — review the result afterwards.