HR to ERP
Buddee to AllSolutions integration: employees, positions and schedules from BuddeeHR in AllSolutions
With an integration between BuddeeHR and AllSolutions, employees from Buddee appear automatically in AllSolutions, with department, job, manager, cost centre and work schedule, on the effective date HR records in Buddee. Projects and hours stay in AllSolutions, so there is one project administration and Buddee remains the source for who works there and for how many hours.
What the integration does
Organisations that use BuddeeHR for personnel files, leave and payroll preparation and AllSolutions for projects, planning and finance enter new employees separately in both systems. A changed schedule only reaches the planning if the planner happens to hear about it, and projects in Buddee drift out of step with AllSolutions.
- HR enters the new employee in Buddee, with employment, position line and schedule.
- KoppelHet fetches the changed employees, with their current position line and schedule.
- In AllSolutions the employee is created or updated with department, job, manager, cost centre and hours per week.
- A position line or schedule with a future date only goes to AllSolutions on that date.
- After the employment ends the employee gets an end date in AllSolutions; hours and projects remain.
What to watch for with BuddeeHR and AllSolutions
- Buddee keeps job, department, manager and cost centre as lines with a start and end date. AllSolutions always gets the line valid today; a transfer as of the first of next month changes the employee in AllSolutions only on that day.
- A schedule in Buddee can alternate weekly, with its own hours pattern for week one and week two. AllSolutions works with hours per week; KoppelHet then passes on the average of both weeks and flags the schedule to the planner.
- Buddee has its own projects, clients and time registration. Next to AllSolutions that gives two project lists. The integration only sends employees and organisation; hours are booked in AllSolutions, and Buddee projects are not passed on.
- Both Buddee and AllSolutions let an integration sign in with a normal user account. We ask for a separate integration account in each, with only the rights needed and a password of at least sixteen characters, so the integration does not stop when a colleague leaves.
- Buddee holds a name-use choice per employee, such as own name or partner's name, with a separate prefix. KoppelHet takes the composed name as Buddee shows it, so project reports in AllSolutions show the same name as the personnel file.
- An archived employee in Buddee is not always out of service. KoppelHet looks at the end date of the employment, not the archive, before an end date is set in AllSolutions.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Can projects from AllSolutions go to Buddee?
That can be added later as an extension, if you want to book hours in Buddee after all. For the start we keep hours in AllSolutions and only send employees.
Do leave and absence go to planning in AllSolutions?
That can be added later as an extension. Buddee then remains the place for the absence file; AllSolutions only learns that someone is away, without a reason.
We run payroll through Buddee in Nmbrs. Does that change?
No. This integration only reads from Buddee and does not touch payroll processing.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Buddee is read through the REST API on api.buddee.nl (employees with include for the active or future employment, employments, positions with start_date and end_date, work-schedules with week_1 and week_2, is_biweekly and hours_per_week). Sign-in with email address and password through Basic Auth on /auth/token; then a JWT access token, renewed with the refresh token.
- AllSolutions through the REST API - POST /api/v1/Login with SHA1 signature, employees with POST or PUT on the browser label the customer sets (PUT with only changed fields), one record per call. Free up to 20,000 calls per month.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BuddeeHR | Field in AllSolutions | Notes |
|---|---|---|
number | Personeelsnummer | Fixed key |
first_name, last_name_prefix, last_name | Naam | Following the name-use choice in Buddee (composed_last_name) |
work_email | E-mailadres | |
positions: department_id, job_id, location_id | Afdeling, functie en vestiging | Through lookup tables; the line valid on the date |
positions: manager_id | Leidinggevende | As the manager's employee number |
positions: cost_center_id | Kostenplaats | |
work-schedules: hours_per_week | Uren per week | For a two-week schedule the average of both weeks |
employments: start_date en end_date | Datum in dienst en datum uit dienst |
Related
BuddeeHR → Active Directory
BuddeeHR to Active Directory integration: domain account from employment and position in Buddee
ASBuddeeHR → Arbodienst (SIVI)
BuddeeHR to occupational health service via SIVI: verified sickness registrations from Buddee to the health service
BuddeeHR → Microsoft Entra ID
BuddeeHR to Entra ID integration: Microsoft 365 account from the employment in Buddee
BuddeeHR → Exact Online
BuddeeHR to Exact Online integration: cost centres, cost units and employees from Buddee consistent in Exact