Business Process Consultant, Belgium

One process, several languages and regions

A Belgian process map often has to show something maps elsewhere rarely draw: language. A customer order taken in French in Brussels, prepared in Dutch in a Flemish warehouse and invoiced from a central team may be described three different ways by three teams. When I map such a flow, each step records not only who acts but in which language the document or message is produced and received.

That makes certain problems visible. Product descriptions maintained separately in each language drift apart. A credit note issued in Dutch is queried by a French-speaking customer. Work instructions exist in one language only, so half the team follows an older version passed on by word of mouth. Approvals stall because the approver cannot quickly read the request.

The future design does not try to make everyone work in one language. It decides which data has one owner and is translated from there, which documents exist in which languages and which version prevails if they differ. The maps themselves are drawn in English with the French, Dutch and German terms your staff use, and local-language versions of instructions are produced by your bilingual colleagues or a local partner. Customer-facing aspects of the same question are on my CRM consultant page for Belgium.

Order to cash with Peppol and structured references

Belgium has been moving business invoicing toward structured electronic invoices exchanged over Peppol, and that changes the order to cash process before it changes any system. Your accountant or tax advisor confirms which obligations apply to you and from when; the process questions are the same either way.

Before an invoice leaves, someone must be sure the customer's enterprise number and Peppol identifier are correct, the order reference the customer requires is present and the VAT treatment is right. After it leaves, someone must watch for rejections and act on them. I map who does each of these today, often nobody explicitly, and design the future steps with owners.

Collections have their own Belgian detail. Many invoices carry a structured payment reference so the payment can be linked to the right invoice. The process should define who generates it, what happens when a customer pays without it or combines several invoices, and when a reminder goes out and in which language. Where you collect by SEPA direct debit, the mandate, the advance notice to the customer and returned collections each need an owner.

These steps later shape configuration and automation. The link to an access point is integration work, described on my integration page for Belgium.

Hire to pay with a social secretariat

Most Belgian employers use a social secretariat to calculate payroll and handle many of the related declarations. That keeps payroll expertise outside the company, but the process that feeds it remains inside. Starters, leavers, contract changes, absences, overtime, meal vouchers and expense claims all have to reach the secretariat complete and on time, and a journal has to come back and be posted correctly.

I map hire to pay as a process with cut-off points. Who tells the secretariat about a new starter, and with what information? Who approves overtime and absences, and by when? How are corrections handled once a payroll is closed? Who checks the journal against the payroll summary before it is posted, and how are costs allocated to departments or projects?

The common failure points are predictable from the map: late information from managers, approvals by email that nobody can find later and journal postings corrected after the fact. The future process assigns each input to a role, sets a cut-off and defines the review of the journal with your accounting firm. Labor law and payroll rules stay with your social secretariat and advisors; I concentrate on making the internal flow dependable. Personal data in this flow is handled as your privacy contact decides under GDPR.

Projects, grants and member-funded organizations

Belgium, and Brussels in particular, has many associations, federations, consultancies and project-funded organizations whose core process is project delivery rather than stock. Their flow runs from a proposal or grant agreement through planning, time recording, purchasing, cost allocation and reporting to the funder or client, then invoicing or claiming.

I map this path with the people who run projects and those who report on them. The map shows where the budget in the proposal becomes the budget the project is tracked against, how staff time reaches the right project, who approves costs as eligible under the agreement and how a funder's reporting format is fed. Where an organization has both grant funding and member fees, the two flows are mapped separately because their rules differ.

Approval limits matter here as much as in a trading company. The design records who may commit project budget, who approves travel and external costs, and when a second signature is needed. Funding rules themselves are interpreted by your finance lead and the funder; the process makes sure the evidence exists when it is asked for. Industry context for service organizations is on my professional services page.

Approval limits, ownership and the software decision

An agreed process needs owners and a clear approval design to stay agreed. For every flow I name an owner who approves changes, and I document an approval matrix covering purchases, credit notes, write-offs, payment releases and edits to supplier bank details. Each limit is a band whose value management sets. Where a small team cannot separate duties fully, a compensating review is written in rather than assumed away.

Documentation is kept short: a map per process, role instructions and the matrix, each in the languages agreed in the document plan, with one version marked as the reference. The owner maintains them and checks any system change against them.

Then comes software. Sometimes the existing accounting package can support the agreed process with better configuration. Sometimes a few repetitive steps call for automation, which my business automation page for Belgium describes. Sometimes the maps justify a new system, and they become the starting point for business analysis in Belgium and selection. In each case the platform follows the process. For the general method, see business process consulting; the Belgium hub sets out what else I do for Belgian organizations. Workshops are online; an on-site session is possible by arrangement.