Automation Consultant, Netherlands

Routine work in a Dutch back office that rules can carry

Automation work starts with a scan of where time actually goes. Over a few online sessions with finance, customer service and operations staff I list the tasks they repeat and note, for each, how often it happens, whether the rule behind it could be written down and what happens when it goes wrong. Screens and exports are shared live, so the list reflects real work rather than a job description.

In Dutch companies the scan tends to surface tasks like these:

• Purchase invoices downloaded from portals or mailboxes and keyed into the ledger.
• Approvals chased in chat because nobody can see where an invoice is waiting.
• Bank lines and failed direct debits matched or followed up by hand.
• Customers asking for shipment status that the logistics provider already confirmed.
• Weekly stock and margin overviews rebuilt in a spreadsheet.

The scan also shows what should not be automated yet. If the approval rules differ depending on who you ask, the problem is the process, and it goes to process consulting in the Netherlands first. Rare tasks often need a checklist rather than a workflow. The remaining candidates form a ranked backlog with a short reason for each, so management can approve the order of work.

Purchase invoices: Peppol, PDFs and the approval route

Purchase invoices are the usual first workflow because they combine volume, rules and risk. In the Netherlands they arrive through several channels: structured invoices over Peppol from suppliers that already use it, PDFs by email from most others and the occasional paper invoice. The workflow brings all three into one intake.

Structured invoices arrive as data and can be checked immediately. PDFs pass through capture, where AI-assisted extraction can read suppliers, amounts and BTW lines from varying layouts, and a person confirms each extracted value against the original. Then every invoice follows the same path: matching against the purchase order and goods receipt where they exist, a suggested cost code, and routing to the approver by amount and cost center, with a deputy when someone is away and a second approver above the agreed band.

The original invoice stays attached to the posting, and the approval history is kept with it. How long records must be retained, and in what form, is something your accountant confirms. Whether the Peppol connection runs through your ERP or an access point provider is an integration question; the automation starts once the invoice is inside. The general approach is on my procurement automation page.

Bank matching, failed collections and customer updates

Dutch bank statements arrive as structured files, and most incoming payments find their open item through the reference, the amount and the customer. Matching rules clear the obvious cases and leave a short list for a person: combined payments, partial payments and transfers with a reference the customer typed themselves. Payouts from payment providers are broken down into gross receipts, commissions and refunds before they hit the ledger.

Failed and reversed direct debits get their own workflow. The automation reopens the item, notes the reason the bank returned, informs the account owner and applies the follow-up your credit control has agreed, for example a second collection attempt or a request to pay by transfer. It does not make the judgment call on a long-standing customer; it makes sure someone does.

Customer messages follow the same logic. Shipment notices go out when the logistics provider confirms dispatch, not when someone remembers. Invoice copies and reminders follow staged rules, and accounts with an open dispute are held back automatically. Texts in Dutch, English or German come from templates your team approves. The result should be fewer customers calling to ask where an order is, and a credit controller working from exceptions instead of the full ledger.

The ondernemingsraad, GDPR and records you must keep

Automation changes how work is recorded. An approval workflow logs who decided what and how quickly, and a dashboard of invoices processed per person can look a lot like performance monitoring. Where a company has an ondernemingsraad, such features may fall within its remit; whether they do is for management to settle with HR and legal counsel. I document what each workflow logs and which reports it allows, and which of those logs could be switched off without hurting the process.

GDPR applies to the personal data that passes through workflows: supplier contacts, customer email addresses, employee names on expense claims. Each workflow description lists that data, which tools handle it and in which location, plus anything an AI service would receive. Your privacy officer decides whether that is acceptable. Some Dutch companies prefer to keep automation tooling on infrastructure they control, and n8n can be self-hosted for that reason.

Record-keeping is the third point. Automated steps must not lose originals, overwrite histories or delete anything that the tax retention rules, as your accountant explains them, require you to hold. I design workflows to add records, not remove them, and each one keeps a run log that shows what happened to a document and when.

What stays manual, who builds and how it is maintained

Some decisions should stay with people even where automation is possible: releasing payment batches, approving changes to supplier bank details, deciding on credit for a large customer and assessing unusual BTW treatment. Automation prepares the information for those decisions; a person takes them. Processes still being redesigned should also wait, because automating a moving target creates rework.

On the build, I work as my global automation service describes: native workflows in Zoho, Odoo or ERPNext, low-code flows, and occasionally a small app in Zoho Creator when a process needs its own screens. When a flow needs real code or a change inside software your partner looks after, the partner develops it from my written brief, and I run the acceptance tests. Connecting systems to each other, such as the logistics provider's messages, is integration work and is scoped separately.

Every workflow gets a named owner, alerts on failure, a list of items awaiting review and a runbook. We describe success in plain terms at the start, for example fewer invoices without an owner or a month-end without a stock spreadsheet, and review those signs together after the first periods. The work is remote; the Netherlands overview lists related services.