Connecting Bullhorn to AFAS
For Bullhorn and AFAS there is one established standard route: the Solid Online Connector, built on the partnership between the two systems — price on request (Solid Online, 2026) and geared above all to high-volume staffing. For SMB agencies that want to start with placement-to-payroll, timesheets or debtor sync, a custom integration on both APIs is often a better fit: an indicative €1,500 to €15,000 one-off.
- Fixed monthly fee
- Fixed project price up front
- Microsoft and Google
- Response to your request within one business day
What does an integration between Bullhorn and AFAS deliver?
An integration between Bullhorn and AFAS lets the process run through at the point where it breaks in practice: at the placement. The recruitment process in Bullhorn ends the moment a candidate is placed — from there it continues in AFAS with employment, payroll and invoicing, and that exact handover still happens by retyping at many agencies. Connected, a placement automatically becomes an employee with a contract in AFAS, timesheets flow through to payable hours, and the back office sees the debtor and invoice status back at the placement. You can see what such a flow looks like in the Flow Lab; what integrating costs in general is covered in What does an API integration cost?
The market is thinner here than for common CRM–accounting combinations: the official partner pages give little detail and the established platform targets high-volume staffing. For SMB recruitment and secondment agencies the alternative is all but invisible — which is why we set out the routes below.
Four routes, from platform to custom build.
| Option | Type | Indicative cost | Suitable for |
|---|---|---|---|
| Solid Online Connector | Off-the-shelf connector | Price on request (Solid Online, 2026) | Staffing and secondment firms running the full chain — placement, contracts, hours, payroll, invoicing — at volume |
| Databrydge | Integration platform | Price on request (Databrydge, 2026) | Organisations that already connect AFAS more broadly through a single integration platform |
| Make / Zapier / Power Automate | iPaaS workflow | Licences from $9 per month (Make, 2026), plus considerable build time | Small, single flows with your own technical management — Bullhorn and AFAS have no ready-made modules, so everything runs through HTTP connectors |
| Custom build on the API | Custom | Indicative €1,500–€15,000 one-off (see What does an API integration cost?) | SMB agencies that want to connect per flow — placement-to-payroll first, hours and debtors after |
What does sync — and what doesn't?
The core: the placement-to-payroll flow can be built on any paid route; the difference lies in hours, corrections and custom fields. Hours processing requires a separate module on the standard platform, whereas a custom build sets the hours flow up precisely around your collective labour agreement terms and correction process.
| Data | Off-the-shelf connector | Custom integration |
|---|---|---|
| Candidate → employee in AFAS | Yes | Yes |
| Placement → contract and payroll | Yes | Yes |
| Timesheets → payable hours | Limited — with Solid Online via the separate Uren Transformer module | Yes |
| Debtor and invoice status back in Bullhorn | Limited — depending on the chosen scope and setup | Yes |
| Custom fields and agency-specific logic | Limited — within the platform's template | Yes |
| History from before the start date | No | Optional |
Three questions that settle the choice.
Do you run at volume, with collective labour agreement payroll and hundreds of flex workers?
Yes → an established platform such as the Solid Online Connector is built for exactly that. No → a custom build per flow is usually faster and cheaper for an SMB agency.
Is your master data in AFAS — agreements, wage components, debtors — in order?
Yes → you can connect straight away. No → configure AFAS first; every integration multiplies what's in there, including the errors.
Do you want to start small, with a single flow such as placement-to-payroll?
Yes → a custom build can be built per flow and extended later with hours and debtor sync. No, it all has to go live at once → then a platform implementation fits better.
Rule of thumb: volume and full chain → platform; a focused start extended per flow → a custom build on the APIs.
Four pitfalls with a Bullhorn–AFAS integration.
Connecting on dirty master data
Missing wage components or duplicate debtors in AFAS come back in every placement once you connect. Clean up the master data first and agree who is allowed to create new values — then it stays clean.
Not agreeing a leading system
If an address can be changed in both Bullhorn and AFAS, the wrong version wins at the next sync. Record per field which system is leading and have the integration enforce that direction.
Forgetting hours corrections
Hours are never final in one go: corrections, back-billing and revised rates follow. An hours flow that only handles the first submission stalls within a month — design the correction route in from day one.
Silent failure just before payroll
An integration that fails silently on a Thursday evening means a missed payroll run on Monday. Monitoring with an alert on every failed transfer is not a luxury here but a precondition.
More combinations are in the integrations overview — for example HubSpot ↔ Exact Online or Pipedrive ↔ Moneybird for the sales side of your agency.
What agencies ask us up front.
What does an integration between Bullhorn and AFAS cost?
The Solid Online Connector — the established standard route — has no public price list; pricing is on request (2026). A custom integration on the Bullhorn and AFAS APIs costs an indicative €1,500 to €15,000 one-off; a first flow, such as placement-to-payroll, usually sits at the lower end of that range.
How long does it take to connect Bullhorn to AFAS?
For a custom integration, allow three to eight weeks, depending on the number of flows and the state of your master data in AFAS. A standard platform implementation is scheduled with you by the vendor and depends on the scope. The lead time rarely lies in the programming and almost always in working out collective labour agreement rules, wage components and test payroll runs.
What if the off-the-shelf connector doesn't fit or stops working?
Your data stays in Bullhorn and AFAS regardless; a connector only moves data. If the standard template doesn't fit your process, a custom build per flow is a real alternative — and the other way around, you can still migrate to a platform later. What matters most is that the field mapping is documented, so a switch doesn't turn into archaeology.
Who manages and monitors the integration?
With a standard platform, the vendor handles the technical management; the functional setup in AFAS stays with you or your AFAS consultant. With a custom build, you agree management and monitoring with the developer — we set up alerts on every flow by default, so a missed placement or a stalled hours stream is immediately visible and not only at the payroll deadline.
Do we need to switch ATS or ERP?
No. Bullhorn and AFAS are both common systems with a mature API; the combination is widespread in the Dutch flex sector and connects well. If you are about to switch anyway, or to reconfigure AFAS, that is the ideal moment to design the integration in at the same time.
Ready to let placements flow through on their own?
Book an intro call — or start with the free Operations Scan and see where the hours leak away at your agency.