Go-Live Checklist

This is the list to work through, top to bottom, until Recommand E-Invoicing is operational. Operational means three things you can see: Test Connection answers OK, one posted sales invoice has left and Check Delivery finds it on the platform, and one supplier document has arrived through the E-Document framework. Everything after that is tuning.

Each step says who normally does it, whether it is required, where it happens, and how you know it is done. Work through the required steps in order — most of them refuse to work until the previous one is complete, and the message they give then points back here.

Phase 0 — Before you install

• ✔ Business Central 2026 release wave 1 (version 28) or later, with Microsoft's E-Document Core app (it ships with Business Central). Who: Customer admin. Done when: Help & Support shows version 28 or higher. What Business Central Must Have in Place.
• ✔ A Recommand account for your team, your company added under Companies and verified against its enterprise number, and an API key id and API secret for the team. Who: Recommand. Where: app.recommand.eu — the Recommand documentation describes the sign-up. Done when: the company shows as Verified and you hold both halves of the key.
• ✔ Your tenant lets this extension reach three hosts: app.recommand.eu (the platform), directory.peppol.eu (the public Peppol Directory) and, only if you switch on the official-data lookup, ec.europa.eu. Who: Customer admin (IT). Done when: nobody has restricted outbound calls per extension, or those hosts are on the allow-list.

Phase 1 — Install and allow

• ✔ Install the app from AppSource. AppSource installs the dependency External Storage - Document Attachments (Microsoft) with it. Who: Customer admin. Where: Extension Management → AppSource Gallery. Done when: Recommand E-Invoicing shows Is Installed.
• ✔ Assign the permission sets. Recommand E-Invoicing Admin for whoever sets up the connection, Recommand E-Invoicing User for everyone who sends or receives. Neither needs SUPER. Who: Customer admin. Where: Users. Done when: every user who will touch the app has one of the two. Permission Sets.
• ✔ Allow outbound calls for the extension. A newly installed extension has this off, and reinstalling switches it off again. Until it is on, every call to Recommand fails with no status code and no message. Who: Customer admin. Where: Extension Management → select Recommand E-Invoicing → Manage → View → switch on Allow HttpClient Requests. Done when: the toggle is on, and the support package (Phase 6) no longer warns about it. Set Up the Platform Connection.

Phase 2 — Connect and map

• ✔ Enter the credentials and test the connection. Fill in API Key Id and API Secret, then choose Test Connection. Who: Customer admin. Where: Recommand E-Invoicing Setup. Done when: Connection Status reads OK and the message says how many companies the key can reach. Set Up the Platform Connection.
• ✔ Map each Business Central company to its Recommand company. Choose Refresh from Recommand, assign the Recommand company this company sends as, then Validate All. Nothing can be sent until the mapping is validated — this is what stops an invoice from leaving under the wrong legal entity. Who: Customer admin. Where: Recommand E-Invoicing Companies. Done when: Mapping Status is OK and Enabled is on; on the setup page, Sends as shows the Recommand company. Map Your Companies to the Platform.
• ✔ Check Company Information. The company needs a VAT Registration No. or, for a Belgian company, an Enterprise No., plus its Country/Region Code. Add the company IBAN on a bank account or in Company Information so outgoing invoices carry payment details. Who: Customer admin. Where: Company Information. Done when: Validate All no longer says the identity cannot be checked, and a draft sales invoice's Peppol FactBox does not warn about a missing IBAN. What Business Central Must Have in Place.

Phase 3 — Posting setup and trading partners

• ✔ Review the VAT posting setup. On every VAT Posting Setup row that Business Central posts with Reverse Charge VAT, the Tax Category must be blank, AE (domestic reverse charge) or K (intra-Community supply) — never S. Blank is safe: the app derives the category from the line. Category O cannot be sent at all. Point the rows that resolve to category E at a VAT Clause that carries the legal ground. Who: Partner. Where: VAT Posting Setup. Done when: the Peppol FactBox on a draft invoice for each posting group shows All local checks passed. Recommand E-Invoicing Setup Reference.
• ◐ Give every unit of measure its International Standard Code. STUKS, UUR and DOOS are not Peppol codes; EA, HUR and BX are. A unit without one is sent as C62 ("one"), which some receivers cannot read back. Who: Partner. Where: Units of Measure. Done when: the Peppol FactBox no longer lists units without a code.
• ✔ Set Peppol endpoints on customers and vendors. Run Fill Peppol Endpoints from the customer list and the vendor list; it derives the endpoint from the Belgian enterprise number and only writes endpoints that are actually published. Enter the rest by hand on the card, and use Verify Recipient where in doubt. Who: Any user. Where: Customers and Vendors. Done when: the results page shows the parties as Filled, and each card you will send to shows a Peppol Endpoint. Fill Peppol Endpoints in Bulk, Set Peppol Endpoints on Customers and Vendors.

Phase 4 — First invoice

• ✔ Send one posted sales invoice. Open it and choose Send via Recommand. Who: Any user. Where: Posted Sales Invoices. Done when: the message says Sent with a message id, and the E-Invoice Status FactBox reads Sent. Send Posted Sales Invoices and Credit Memos.
• ✔ Confirm it arrived. On the log entry, choose Check Delivery. A delivery signal can take a while and not every receiver sends one; no signal yet is not a failure. Who: Any user. Where: Recommand E-Invoicing Log. Done when: the entry has a platform document id and Check Delivery answers. Check Whether a Document Arrived.

Phase 5 — Receiving

• ✔ Create the E-Document Service. Document Format Recommand E-Invoicing (Peppol), Service Integration Recommand E-Invoicing, and Validate Receiving Company switched off — a Belgian company can never satisfy that check, because it accepts only a GLN or the W1 VAT field, which Belgium does not use. Accept the one-time third-party consent dialog that Business Central shows when you pick a non-Microsoft integration. Who: Customer admin. Where: E-Document Services. Done when: the service exists and the setup page's Applied To Services no longer says no service receives through this app. Set Up Receiving of Supplier Documents.
• ✔ Let Recommand receive for you. Your company must be registered with Recommand as the receiving access point. Who: Recommand. Done when: Recommand E-Invoicing Companies shows Is SMP Recipient for the company; without it the inbox stays empty forever and the app stops rather than returning nothing.
• ✔ Add the units of measure your suppliers send. Business Central stops an incoming document before it even looks for the vendor when a unit code is unknown, and C62 is the most common one in the wild. Add Missing Units on the setup page creates them. Who: Customer admin. Where: Recommand E-Invoicing Setup → Add Missing Units. Done when: the action reports nothing left to add.
• ✔ Apply supplier recognition to the service if your E-Documents Setup uses Import Process Version 2.0. Business Central cannot recognise a Belgian supplier on its own; this is what makes the app's matching run. Who: Customer admin. Where: Recommand E-Invoicing Setup → Apply Supplier Recognition to Services. Done when: Applied To Services reads Applied to 1 service(s). Recognize Suppliers on Incoming Documents.
• ◐ Schedule the import. Switch on Automatic Import on the service with a sensible interval, or accept that documents are only fetched when someone chooses Scan Inbox Now. Who: Customer admin. Where: the E-Document Service card. Done when: E-Invoice Inbound Runs shows a run triggered by the job queue with Documents Offered greater than zero.
• ◐ Decide what happens to supplier bank details. Choose the Approved IBAN Action on the setup page, and make sure whoever approves has the standard purchase permissions — the app deliberately does not widen them. Who: Customer admin. Where: Recommand E-Invoicing Setup and Vendor Bank Approvals. Done when: the first proposed account has been approved or rejected. Approve Supplier Bank Details.
• ○ Route incoming invoices through approval. Only if you set Approval for Incoming Documents to Send for Approval, and only with an approval workflow for purchase documents enabled. Who: Partner. Where: Workflows. Done when: the Incoming Supplier Recognition list shows no reason in the routing column. Set Up an Approval Workflow for Purchase Documents.

Phase 6 — Keep it running

• ◐ Schedule the nightly check. It repeats Test Connection every night so the Setup Issues tile and the FactBoxes show a current status. Who: Customer admin. Where: Recommand E-Invoicing Setup → Schedule Nightly Check. Done when: the job queue entry is Ready and Setup Issues reads 0.
• ○ Send automatically. Switch on Auto-Send Enabled, set Auto-Send From Date (required — without it the first run would send every posted document in the company), and create a job queue entry for codeunit 73632653. Who: Customer admin. Where: Recommand E-Invoicing Setup and Job Queue Entries. Done when: the support package no longer warns that auto-send has no job queue entry. Send Documents Automatically.
• ◐ Set retention periods. The app registers four of its tables with retention policies but leaves the period to you; the log and the bank approvals are audit trails, so respect the legal retention of invoices — seven years in Belgium. Who: Customer admin. Where: Retention Policies.
• ○ Self-billing, if you issue invoices in a supplier's name. First fill Posted Self-Billing Invoice Nos. in Purchases & Payables Setup — the moment any vendor has a self-billing agreement, posting a purchase invoice for that vendor fails without it. Then switch on Self-Billing Agreement on each vendor card, and choose Self-Billed Document No. on the setup page. Who: Partner. Where: Purchases & Payables Setup, Vendors. Done when: the Peppol FactBox on a posted purchase invoice reads Agreed. Issue Self-Billed Invoices in a Supplier's Name.
• ○ Attach a PDF to outgoing invoices, and optionally keep supplier documents outside the database. The PDF comes from Report Selections; external storage takes three setup pages and a storage account secret you own. Who: Customer admin. Where: Report Selection - Sales; Recommand E-Invoicing Setup → Attach PDF to Outgoing Documents. Done when: a sent invoice shows Attachments (1). Where Supplier Documents Are Stored.
• ◐ Choose your tiles. Every user picks which e-invoicing tiles appear on their role center; nothing is shown until they do. Who: Any user. Where: My E-Invoicing Tiles. Show the E-Invoicing Tiles on Your Role Center.

Final check

• ✔ Download a support package and read its warnings. The package lists exactly the conditions this checklist covers — outbound calls off, no secret, connection never tested, no company mapping, no nightly check, no e-document service, auto-send without a job — as one line each. Who: Customer admin. Where: Recommand E-Invoicing Setup → Download Support Package. Done when: the warnings section is empty. If a warning stays that you cannot place, choose Send to Support instead, or use the support chat — it reads the same package. Get Help.

Related information

• What Business Central Must Have in Place
• Set Up the Platform Connection
• Recommand E-Invoicing Setup Reference
• Troubleshoot the Connection and Setup