Accounts in applications
Buddee to Simplicate integration: employees, supervisor and schedule from Buddee in Simplicate
With an integration between BuddeeHR and Simplicate, every new employee from Buddee appears automatically in Simplicate, with name, work email, job title, supervisor and work schedule. A new schedule or a different manager in Buddee carries over to Simplicate, and after the end date of the employment the employee is set to inactive in Simplicate.
What the integration does
Anyone who keeps personnel files, leave and absence in Buddee and projects, hours and invoices in Simplicate enters new colleagues twice. A manager who changes team keeps approving hours in Simplicate for their old team.
- HR creates the new employee in Buddee, with employment, job, manager and work schedule.
- KoppelHet creates the person with name and work email in Simplicate and the employee linked to it, with the manager from Buddee.
- The schedule from Buddee arrives in Simplicate, with hours and start and end times per day, for one week or alternating every other week.
- On a new job, manager or schedule in Buddee, KoppelHet updates the employee or schedule in Simplicate.
- After the end date of the employment KoppelHet sets the employee to inactive and reports it to the Simplicate administrator.
What to watch for with BuddeeHR and Simplicate
- Buddee stores the schedule as week 1 and week 2 with hours and start and end times per day, with a flag for whether it alternates. Simplicate has even and odd weeks with the same three values per day. At the start KoppelHet records which Buddee week matches the even weeks, so a free Wednesday every other week lands in the right week.
- Buddee records the manager per job period, and Simplicate uses the supervisor for approving hours. A new manager in Buddee carries over to Simplicate, so after a team change hours go to the new manager for approval.
- Buddee has its own projects, clients and time registration too. With Simplicate alongside, that makes two places for the same hours. The integration does not carry over projects or hours from Buddee; hours are written in Simplicate.
- Buddee has a composed surname according to name usage, with its own prefix. Simplicate has a separate prefix field for a person. KoppelHet fills it with the prefix of the name in use, so someone who uses their partner's name appears in Simplicate under that name.
- Simplicate does not let the API fill in an employee's job title or hourly rates. The job title from Buddee therefore goes into a custom field; cost and sales rates stay in Simplicate, where they are set per employee anyway.
- Buddee grants access through a normal user account with email and password, and returns per record what that account may do. KoppelHet uses its own account that only needs to read employees, jobs and schedules, so salaries and absence stay out of view.
This integration is also part of joiner, mover, leaver.
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 approved leave from Buddee also reach Simplicate?
That can be added later as an extension. Simplicate can receive leave through the API, so planning knows who is away. We start with employees, supervisor and schedule.
Does the new employee also get a Simplicate login?
The employee is ready, but the administrator creates a user with a licence in Simplicate; the API has no field for it. KoppelHet reports every new employee, so this happens in time.
Buddee already connects with Nmbrs and Loket. Is this still needed?
Those integrations go to payroll. Simplicate is not in Buddee's list of integrations; this integration fills that gap, alongside what Buddee itself sends to payroll.
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 at api.buddee.nl with a JWT token after Basic Auth on /auth/token. Resources employees (number, first_name, composed_last_name, composed_last_name_prefix, work_email, manager_id, archived_at), employments (start_date, end_date), positions (job_id, department_id, manager_id with start and end date) and work-schedules (week_1 and week_2 per day with hours, start_time and end_time, is_biweekly). Pagination per 200.
- Simplicate is written through API v2 (Authentication-Key and Authentication-Secret) on crm/person, hrm/employee (person_id, supervisor, status, custom_fields) and hrm/timetable (even_week, odd_week with start_time, end_time and hours per day, start_date, end_date). Employees cannot be deleted through the API; Simplicate limits to at least 60 requests per minute.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BuddeeHR | Field in Simplicate | Notes |
|---|---|---|
employees.number | Eigen veld personeelsnummer | Fixed key to find the employee again |
first_name | person.first_name | |
composed_last_name_prefix | person.family_name_prefix | According to the name usage in Buddee |
composed_last_name | person.family_name | |
work_email | person.email | |
positions.job_id | employee.custom_fields (functie) | |
positions.manager_id | employee.supervisor | Only if the manager is already in Simplicate |
work-schedules week_1 en week_2 | timetable.odd_week en even_week | Hours, start and end time per day |
work-schedules start_date en end_date | timetable.start_date en end_date | |
employments.end_date | employee.status | Inactive after the end date |
Related
BuddeeHR → Active Directory
BuddeeHR to Active Directory integration: domain account from employment and position in Buddee
BuddeeHR → AllSolutions
Buddee to AllSolutions integration: employees, positions and schedules from BuddeeHR in AllSolutions
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