There is one moment when almost every finance team thinks seriously about automation, and it isn't during a strategy session. It's the day the AP clerk hands in their notice. Suddenly a choice is on the table that was unthinkable three months ago: do we post the vacancy, or do we make sure this work no longer needs one?
The short answer: do the math first, look at candidates second. In today's market a hire takes months, costs thousands in recruitment and delivers a colleague who needs months more to learn your vendor base. Automating the repetitive part runs within weeks and doesn't leave for another employer. The honest trade-off sits in what kind of work is actually walking out the door.
What 24,078 vacancies show
We analyzed 24,078 Dutch finance vacancies, line by line. Three patterns together tell you when this role comes into existence, and what keeps it alive.
The dedicated AP role only emerges above fifty employees. Below that line, almost no company has a separate AP clerk: the work sits folded into the generalist vacancy called "financieel medewerker" or "administratief medewerker", usually with receivables attached. From fifty employees the split begins, and the share of specialized AP vacancies then roughly doubles with every size class: from 2 percent at companies up to fifty employees to 11 percent above five hundred. The vacancy you are considering is a scale phenomenon: it appeared when volume justified one person, and it disappears again once the work no longer hangs on a person.
A scan tool barely changes the vacancy text. We compared AP vacancies at companies that already name scanning software (Blue10, Basecone and comparable) with AP vacancies without one. The requested set of tasks is nearly identical: matching, investigating differences, the close, the mailbox. It's all still there, tool or no tool. The software took over the retyping; the job remained.
The system switch coincides with the same growth moment. Up to fifty employees, Exact dominates with a third of ERP mentions; between two hundred and five hundred, Microsoft Dynamics takes the lead, and above five hundred SAP is dominant. Exactly in the phase where the AP role emerges, the system it has to run on changes too. Two transitions that reinforce each other, and both are moments when companies redesign their process anyway.
Source: Claridy analysis of 24,078 Dutch finance vacancies, 2026.
The decision framework
Ask three questions before the vacancy goes out.
1. Which part of the week was repetitive? Walk through your departing colleague's last month. Booking, matching, coding, chasing approvers, answering supplier status questions: that part is automatable. Judgment calls, escalations, talking to the auditor: that part isn't, and you wouldn't want it to be.
2. What does the next person really cost? Salary plus employer costs for an experienced AP clerk quickly reaches €45,000 to €60,000 a year. Add recruitment fees, ramp-up time and the risk of doing this again in two years. Compare that with the cost of automating the same work, over three years, for both options.
3. What happens on the next sick day? This is the question most often skipped. A team where one person knows the AP process doesn't have a process, it has a person. The vacancy on the table today is the chance to fix that structurally instead of forwarding it to the next resignation date.
When hiring is the right answer
Automation isn't always the outcome. If you process a few dozen invoices a month, there is too little repetitive work to automate and a part-timer or your accountant is the sensible route. If the role is mostly judgment and working with procurement, then what's leaving isn't manual work but an expert, and you simply replace them.
The tipping point is where volume starts dictating the human's day: hundreds of invoices a month, multiple entities, a mailbox that needs daily attention. From there on, every new hire inherits the same manual work, and in two years you're back at the same choice.
What the automation route looks like
With Claridy it runs like this: the workflows connect to your existing ERP (Exact, NetSuite or Microsoft Dynamics) and your AP mailbox, read-only at first. For the first weeks everything runs supervised: every booking is proposed, your team approves. You see week by week where the system agrees with your team. Then it takes over the flow and your team only sees what deviates. No migration, no new package to learn, and the process knowledge now lives in rules you can read instead of in someone's head.
The vacancy can still go out, but for a different role: someone who uses the numbers instead of retyping them.