AFAS integrations without a human glue layer.
AFAS holds your employees, your administration or both. Around it sit the systems that feed it: contracts, signatures, webshops, tills. Usually a person copies data between them. I connect them through the AFAS API so that person can do something else.
What I connect AFAS to.
Employee onboarding
From signed contract to employee in AFAS, with the right documents in SharePoint and the signature flow in Acrobat Sign, without anyone retyping.
Journal entries
Daily sales from a webshop or till into AFAS as journal entries, with your own ledger mapping per product group or payment method.
Employee data to other tools
New starters, leavers and changes pushed to the tools that need them: access, planning, mailing lists.
Reports and dashboards
Data out of AFAS through GetConnectors into a dashboard, so management doesn't wait for a monthly export.
Order and customer sync
Customers and orders kept in sync between AFAS and your webshop or CRM.
These are the most common starting points. Every integration is built around how you work.
What I've built so far.
Built forMatchingPool
How a project runs.
A conversation first
We go through how the work runs today and what the integration has to do. Every company does this differently, so I don't start from a template.
A fixed, one-time price
You get one price for the build. No monthly licence for something that only needs looking at when a system changes.
I build it and keep it running
I build it, host it if you want me to, and keep an eye on it. The code is yours, so you're never locked in.
How your data stays safe.
Only what's neededThe integration only gets access to the data it needs for the job, and read-only access where that's enough.
Keys stay out of sightAPI keys and tokens live in an encrypted server environment, never in a spreadsheet or a shared document.
Hosted in the EUI run integrations on servers in the EU unless you prefer your own environment.
Not used to train AIWhere AI is involved, I use the business APIs of OpenAI or Anthropic. Your data is not used to train their models.
What people ask about AFAS.
How do you connect to AFAS?
Through AFAS App Connectors. You create a connector with the GetConnectors and UpdateConnectors the integration needs, and I build against those. I always start on your test environment.
Do I need an AFAS partner for this?
No. AFAS lets you give access to any developer through an App Connector. You stay in control of what that connector can read and write.
Can this work with AFAS and SharePoint together?
Yes. I've built onboarding flows that run across AFAS, SharePoint and Acrobat Sign in one go.
Do I pay a monthly fee?
No subscription to me. You pay once for the build. If a system changes its API later, or you want something extra, I'll quote that separately. Hosting is usually a few euros a month, at cost.
Who owns the integration?
You do. The code is yours, and so are the accounts it runs on if you want that. You can hand it to another developer at any time.
What if something breaks?
I add monitoring to every integration, so I usually see a failed run before you do. When something does stop, I fix it quickly.
Often connected together.
Want AFAS connected to your other systems?
Tell me what runs where today and what should happen automatically. I'll tell you what's possible, how I'd build it and what it costs.






