Business Automation Consultant, Belgium

Belgian back-office work that rules can take over

Each engagement opens with a list of what people actually repeat. In online sessions with finance, administration and customer or member services, we walk through a typical week and month, task by task, and note how often each occurs, whether a rule governs it, what an error leads to and who would spot an automated version that had stopped.

Belgian organizations tend to produce a recognizable list:

• Supplier invoices arriving through Peppol and by email, handled in two different ways.
• Incoming payments matched by hand when the structured reference is missing or wrong.
• Reminders written one by one because the customer's language has to be checked first.
• The payroll journal from the social secretariat checked line by line against a summary.
• Project or funder reports compiled from exports each quarter.

Some items drop off during the review. Tasks that come up rarely are often better served by a checklist. Tasks whose rules change depending on who describes them point to an unclear process, and those go to process consulting in Belgium before anyone automates them. The rest become a backlog with plain reasons, approved by management before work starts.

One approval flow for Peppol and paper invoices

Belgium's move toward structured e-invoicing over Peppol means a growing share of supplier invoices arrives as data. Others still come as PDFs or on paper. Running two separate routes doubles the effort and hides what is waiting, so the first workflow usually merges both into one queue.

Structured invoices are validated on arrival and compared with the purchase order and goods receipt where those exist. PDFs are read by a capture step that can use AI to pick out supplier, amounts and VAT lines, and a staff member confirms the values against the original before the invoice joins the queue. From there every invoice takes the same route: a suggested account and cost center, approval by amount and department, a stand-in during absences and a further sign-off once the amount crosses the set band.

Approvers often work in different languages, so the request shows the key fields in a fixed layout rather than relying on the invoice text. The original document and the approval history stay with the posting for as long as your accounting firm advises. Which Peppol obligations apply to you is for your advisor to confirm, and the access point link is integration work. More on the approach is on my approval workflows page.

Matching payments and reminding customers in their language

Belgian bank statements are delivered in a structured format, and many customer payments carry a structured reference that points to the invoice. Rules can clear those payments directly. What is left, such as payments without a reference, combined payments and partial amounts, is offered to a person together with the likeliest candidates, rather than left in a long unexplained list.

Returned direct debits follow a set route: the item reopens, the bank's reason is stored, the account owner hears about it and the agreed follow-up begins. Whether to keep collecting from a long-standing customer remains a human call; the workflow simply guarantees the call gets made.

Reminders are where language matters most. Each customer record holds a language, and reminders, statements and order updates are sent from templates in French, Dutch, German or English accordingly. Your team writes and approves every template, so tone and wording match how you deal with customers. Rules hold back reminders for disputed invoices, key accounts and customers with an open complaint, since a correct reminder sent at the wrong moment still causes harm. The aim is that credit control spends its time on the cases that need a conversation.

AI drafts, personal data and what to keep

AI helps in narrow, checkable steps: reading fields from invoices with varying layouts, sorting incoming emails by topic and language, or drafting a reply that a staff member checks and sends. Payment approval, credit decisions and unreviewed replies to customers or members stay off its list. Each AI step has a human checkpoint and a fallback for when the result is uncertain.

Personal data runs through many back-office workflows: customer contacts on reminders, member details, employee data in payroll checks. For each workflow I record which personal data it uses, the tools that touch it and where they run, and what any AI service receives and keeps. Acceptability under GDPR and your internal rules is judged by your privacy contact. Payroll checks compare totals and allocations rather than sending detailed pay data through extra tools.

Record-keeping is designed in from the start. Workflows add records and never delete originals, approval histories are retained and each workflow keeps a run log. Retention periods come from your accounting firm. Where a change in how work is recorded could affect staff, management and HR consider with their advisors whether employee representatives should be informed. My AI automation service explains the governance approach in general.

Limits, builders and long-term ownership

A few steps stay manual by design: releasing payments, approving changes to supplier bank details, accepting an unusual VAT treatment and anything a funder could later question. The automation gathers the information and a person signs off. Processes still under discussion wait until their rules are settled, because automating them early means rebuilding later.

The build follows my global approach. I set up flows with the native automation of each ERP and with low-code services, and occasionally a small Zoho Creator app where a process needs its own forms in several languages. Custom code, and changes inside software your partner supports, are developed by them from my written brief, and I test the results with your team before go-live. Linking systems to one another, such as the bank or the Peppol access point, is integration work rather than automation.

Every workflow has its own owner, failure alerts, a review list and written operating notes. Success is described in qualitative terms agreed at the start, for example fewer unexplained bank lines or reminders that no longer reach disputed accounts, and reviewed together after the first periods. Delivery is fully remote; the Belgium overview lists related work.