Back-office automation
We build back-office automation for finance, HR and operations workflows, so approvals move, accounts reconcile and reports appear without anyone chasing them. Your people step in for exceptions and sign-offs, and every action is logged for audit.
What it is and when it fits
Back-office automation connects the systems your teams already use, such as the ERP, accounting package, HR platform, shared inbox and spreadsheets, and moves work between them according to your rules. We build in n8n when your team should be able to see and adjust the flow, and write custom workers in Python or TypeScript when volume, logic or reliability calls for code. AI steps handle the unstructured parts, like reading an email or classifying a request.
It pays off for processes that are frequent, rule-based at their core and currently held together by manual handovers. Month-end reconciliation, purchase approvals, employee onboarding and recurring management reports are typical candidates. A process that changes every month, or that only a single expert understands, needs to be written down and stabilised first, and we help with that before automating anything.
What we build
Approval workflows
Purchase requests, expenses and contract sign-offs routed to the right approver by amount, department or supplier, with reminders and escalation.
Bank and ledger reconciliation
Transactions matched against invoices and ledger entries automatically, leaving only genuine mismatches for your finance team.
Employee onboarding and offboarding
Accounts, equipment requests, contracts and access rights created or revoked across systems from a single HR trigger.
Scheduled management reporting
Figures pulled from finance, sales and operations systems into a consistent weekly or monthly report, delivered to the right inboxes.
Shared inbox triage
Incoming requests read, categorised and routed to the right queue or workflow, with a drafted reply where the answer is standard.
How it works
- 01
Map the process
We sit with the people doing the work, document each step and exception, and pick the workflows with the clearest return.
- 02
Choose the build approach
We decide per workflow between n8n and custom workers, based on volume, complexity and who will maintain it.
- 03
Run alongside the team
The automation runs next to the manual process at first, so results can be compared and edge cases handled before full handover.
- 04
Hand over and monitor
Your team gets documentation, alerts for failures and a clear owner for each workflow, with ongoing support if you want it.
Related work
- Reference build
AI invoice approval agent that cites the policy clause behind every decision
100%of automatic decisions cite a policy clause- AI agents
- Human in the loop
- RAG
- Logistics
How AI agents saved a freight forwarder €400k a year on shipment exceptions
€400ksaved a year- AI agents
- LangGraph
- Workflow automation
Built with
All technologiesFurther reading
How to automate your business processes
How to automate business processes one at a time: pick a repetitive process, measure it, decide between rules and AI for each step, and run it alongside your team before it takes over.
10 min read
Human-in-the-loop AI agents: design patterns for real operations
How we keep a human in the loop when AI agents run on live systems: approval checkpoints, confidence thresholds, tool permissions, audit trails and fallbacks.
5 min read
Common questions
n8n suits workflows your operations team wants to see and tweak, and it can be self-hosted to keep data in your environment. Custom workers suit high volumes, complex logic or strict reliability needs. Many setups use both, and we explain the trade-off for each workflow.
Every workflow has retries, error alerts and a clear place where failed items wait for a person. Nothing disappears silently. We also log each run so you can trace what happened to a specific invoice or request.
Most ERP, accounting, HR and productivity tools with an API, including SAP, Odoo, Exact, AFAS and Microsoft 365. Where a system has no API, we look at exports, database access or email-based routes and tell you how reliable each option is.
You do, once invoices are paid. Workflows and code live in your accounts and repositories, with documentation, so another team can maintain them if you choose.