Digital Transformation, Belgium

Start with processes, data and people across language communities

In Belgium the same process may be run by a team in Antwerp working in Dutch, colleagues in Liège or Namur working in French and a Brussels office that defaults to English. Each group often developed its own habits, templates and spreadsheets. Before deciding on any system, the organization needs one agreed version of how work should flow, written down in a way all groups recognize.

I run the first phase as remote workshops with representatives from each department and region. We follow real transactions: a customer order or project from quote to invoice and payment, a supplier invoice from receipt over Peppol or email to approval and posting, and the monthly path from payroll journals to management figures. Differences between regions are recorded, and the business decides which are justified and which are simply history.

Data gets the same attention. Customers with separate records per language, products described differently in each catalog and cost centers that do not match between payroll and accounting all weaken later automation and reporting. I document who should own each type of record and how translations of names and descriptions are maintained.

The result is a set of process maps, a systems map, a data ownership table and a ranked list of problems. Where the process layer needs more work, my business process consulting in Belgium continues from there.

Using the Peppol change as a starting point, not the whole plan

For many Belgian companies the move to structured invoicing over Peppol was the first transformation project they could not postpone. Often it was solved quickly: an access point bolted onto the accounting package, incoming invoices still approved by email and outgoing ones generated from a separate tool. That met the immediate need but left the surrounding process unchanged.

A roadmap treats that work as a foundation to build on. A typical Belgian sequence, reshaped by whatever the diagnosis uncovers:

• Invoicing flow: incoming Peppol invoices matched to orders and receipts and routed for approval inside the system; outgoing invoices produced from the order or project, not retyped.
• Core system: an ERP or stronger accounting setup if the current package cannot carry projects, stock or several entities, chosen with structured invoicing and bank file handling as requirements.
• CRM and projects: quotes, member or client records and project budgets connected to invoicing.
• Automation and reporting: reminders, approvals and management figures built once the steps beneath them are stable.
• Lead engine: websites in each language feeding the same CRM, so inquiries from every region are visible together.

Each initiative carries an owner, dependencies and cost drivers such as subscriptions, partner effort, interfaces, data cleansing and translation of templates. Which invoicing and reporting obligations apply to you, and from when, remains a question for your accountant. If the core platform decision comes first, my ERP selection work in Belgium handles the comparison.

Outside drivers: regulation, digital government and talent

Beyond invoicing, several outside factors shape a Belgian roadmap. I treat each as an input to prioritize, with the legal detail left to your advisors.

Further digital reporting. The EU direction points toward more transaction-level reporting to tax authorities, and Belgium has signaled its own steps that way. A system that already exchanges structured invoices and keeps clean VAT data is better placed for whatever follows; your accountant confirms what applies and when.

Digital government. Companies deal with authorities through online portals, signing in with the electronic identity card or apps such as itsme. Filings assembled by hand at each deadline are a sign that ledger data is not yet reliable enough.

Regional support. Flanders, Wallonia and Brussels each have agencies that have offered advice or funding for digital projects in smaller firms. Schemes and conditions change, so check them directly; a documented baseline and roadmap usually help any application.

Talent. Finance and operations profiles, especially bilingual ones, can be hard to recruit. Automating routine handling protects scarce staff and is better presented as relief than as replacement.

These drivers rarely point to one platform. They argue for clean ledger data, structured documents and less manual handling early in the sequence.

Governance, staff consultation and adoption in several languages

A roadmap that spans regions needs clear decision rights. I propose a small steering group with a business owner for each initiative, a decision log kept in English and a clear procedure for changing scope. For a family firm this may be the owner and the finance lead; in the Belgian office of a group it includes whoever represents the parent.

Staff consultation deserves early attention. Where a works council or union delegation exists, new technology that changes work organization or records employee activity may need to be discussed with it. I do not advise on Belgian labor law. I prepare a plain description of what each planned system records about users, which reports could show individual performance and how permissions limit access, so management and its advisors can plan that dialogue.

Adoption then runs per phase:

• Change notes for each team, prepared in English and adapted into Dutch or French by your native speakers.
• Key users from each region who join design sessions and acceptance testing.
• Training on real tasks, delivered in the language each group works in by your key users or a local partner.
• A usage check after go-live to see whether old spreadsheets have quietly returned.

Payroll stays with the social secretariat throughout; the roadmap only defines how its journals and cost data flow into accounting and reporting.

Independent oversight, and a sober view of AI

Belgian implementation partners and software vendors carry the configuration, integrations and support. My job is to keep the client's perspective in the room across all of them. That means owning the roadmap document, turning each phase into requirements, setting comparable criteria for every option, reading statements of work closely and confirming at the end of each phase that the funded problem is actually gone. My fees come only from the client.

On AI, I aim to be useful rather than fashionable. Reading incoming documents, proposing payment matches, drafting replies in several languages and searching internal knowledge can all save effort, but only on top of agreed processes and clean data. These ideas enter the roadmap after the foundations, each with written rules on the data it may touch, the person who checks its output and the way mistakes get corrected. GDPR questions go to your privacy advisor. Proposals that put a confident savings number on AI deserve questions before approval.

You can engage me for a diagnosis and roadmap, or keep me on as fractional lead during delivery by your partners. Delivery is remote, with visits by arrangement. Related pages include digital transformation consulting, the Belgian ERP consulting page and SEO consulting in Belgium for the multilingual search side. The Belgium overview lists everything else.