As published, B2B e-invoicing became mandatory in Belgium from 1 January 2026 for most domestic transactions between VAT-registered businesses established in Belgium. That is as published — confirm current rules with your tax or legal adviser. For a Brussels company, the practical consequence is a data problem before it is a sending problem: the invoice has to be built from clean, structured order and customer data.
LATYNEX Digital builds the workflows that prepare and route that data. This page covers that work for Brussels businesses. The general service is at Workflow Automation & Systems Integration, and the market overview is at LATYNEX Digital for businesses in Brussels.
Typical industries
- Professional and consulting services
- EU-facing associations and public-affairs firms
- Trade, wholesale and distribution
- Software and IT services
- Logistics and freight forwarding
- Construction and property services
Common lead-handling problems
- PDF invoices still emailed by habit, which as published no longer satisfies the requirement as the sole method
- CRM and ERP fields that do not map cleanly to structured invoice data
- Uncertainty about which invoices are in scope and which are not
- Rejected or incomplete documents with no queue and no owner
Direct answer
If your Brussels company must move invoicing from PDFs to structured data, LATYNEX maps the fields from your CRM, ERP or order system into the structure your invoicing provider expects, builds the workflow that gathers them, and adds a queue for records that are incomplete or rejected. Your existing invoicing provider or Peppol access point keeps transmitting the invoices.
Why the global workflow page is not enough for Belgium
The global Workflow Automation & Systems Integration page is general. The Belgian case has a defined shape. As published, structured invoices follow EN 16931 with Peppol BIS Billing 3.0 as the reference format, Peppol is the default channel, and there is no B2C mandate (as published — confirm current rules with your tax or legal adviser). That fixes what the output of the workflow must look like, so the work is field mapping and exception handling, not a generic integration.
What we build
The build stays on the data side of the invoicing boundary.
- A field map from your order, CRM or ERP records to the invoice fields your provider requires
- Validation before hand-off, so a missing VAT number or unit is caught early
- An exception queue with a named owner for incomplete or rejected documents
- Duplicate protection and a log of what was passed to the provider and when
- A written handover describing the mapping and how to change it
What stays with your provider
Transmission, network delivery and the legal status of the invoice stay with the invoicing provider or Peppol access point you already use. Whether it exposes an API or accepts files is checked in a technical review, and connections are scoped per project, through an API or webhook where the system supports it. Some ERPs will need custom scope, and we say so before quoting.
What we do not do
LATYNEX is not a Peppol access point or certified provider, does not submit invoices on your behalf, does not give VAT or legal advice, and does not deliver in Dutch or French. Which of your invoices are in scope is a question for your tax adviser.
How delivery actually works
LATYNEX Digital has no office in Brussels and does not claim one. We work with Brussels businesses remotely, over video calls and written updates, in English, with the same team and process as in every other market.
Questions
Do you have an office in Brussels?+
No. We work with businesses in Brussels remotely, over video calls and written updates, in English, and we do not imply a local presence.
Do you send our invoices over Peppol?+
No. LATYNEX is not a Peppol access point. We prepare and route the data; your existing invoicing provider or access point transmits the invoice.
Which of our invoices are in scope of the mandate?+
We do not give VAT or legal advice. As published, the mandate covers most domestic B2B transactions between VAT-registered Belgian businesses; confirm how it applies to you with your tax or legal adviser.
Can you connect any ERP?+
We do not claim prebuilt connectors. Integrations are scoped per project, through an API or webhook where the system supports it, after technical review; some systems need custom scope.
How are you invoiced, and in what currency?+
In EUR, by Latynex Trade OÜ, a company registered in Estonia (EU). Tax treatment for a client in Belgium is confirmed on the quote, and we do not give tax advice.
What happens next
- 01
We map the process and the tools
Where the work starts, what is done by hand, which systems are involved.
- 02
We pick the simplest reliable route
A platform, a workflow or a little custom code — whichever is simplest and safest for this outcome.
- 03
Scope and price in writing
One scope and one price for you to approve. Nothing starts before you agree.
- 04
We build it with failure handling
Retries, duplicate protection and a named person told when something breaks, in accounts you own.
- 05
Test, monitor, hand over
We check it against real cases, agree who watches it, and document how it works and what to do when it fails.
Who you would be working with
- Company · Who you would be working with
- LATYNEX Digital is a service line of Latynex Trade OÜ, a company registered in Estonia (EU). Contact: info@latynexdigital.com.
- How we work · Delivery
- Remote, in English, with the person who would run the project. No local office is implied in any market.
- How we work · Commercial terms
- One scope and one price, agreed in writing before work starts. Your accounts, code and domain stay yours; any access we use is granted by you and can be withdrawn.
There are no client case studies on this page, and none are implied. What LATYNEX has built and runs itself is on the portfolio, each system labelled by stage. Published prices are on the pricing page; anything not listed there is scoped and quoted after review.