Skip to main content

How to integrate with AFAS Software

Easily send your newly hired candidates to AFAS Software without having to leave Homerun ATS.

Written by Valesca

When you hire a candidate in Homerun, you can send them to AFAS as a new hire in AFAS Onboarding. AFAS then asks the new hire for everything else, such as their address, BSN and bank details. Homerun never stores or sends those.

Only the new hire is sent. Vacancies don't sync, nothing is pushed automatically, and nothing comes back from AFAS into Homerun.

This page explains the following:

Before you start

Plan about 30 minutes with two people: an AFAS functional administrator (functioneel beheerder) and a Homerun admin. Make sure you have the following:

  • The AFAS administrator can open General > Management (Algemeen > Beheer) in AFAS Profit.

  • AFAS Onboarding (HR Onboarding) is part of your AFAS licence.

  • You know which environment you're connecting: production (O), test (T) or accept (A). Start in test if you have one.

  • You know your AFAS member number (deelnemernummer). It's shown top right in AFAS, for example O12345AA. In Homerun you only enter the digits: 12345.

  • The AFAS integration is turned on for your Homerun account. Don't see AFAS under Settings > Integrations? Contact Homerun support.

What Homerun sends to AFAS

Field

Where it comes from

First name, last name, initials

The candidate profile

Email address

The candidate profile (also used for the onboarding invite)

Date of birth

You enter it when you send

Onboarding profile

Chosen once, when you connect

Setting up AFAS Profit

Do these six steps in order, in the AFAS environment you'll connect. Menu names are in English, with the Dutch label in brackets.

Step 1: Create a Homerun user and user group

AFAS runs every Homerun request as one user. Create a user that stands for Homerun, not for a person. If the integration runs on a colleague's account, it stops working the day that account is blocked, and every new hire shows that colleague as its creator.

Create the Homerun user

  1. Go to General > Management > Authorisation tool (Algemeen > Beheer > Autorisatie tool) and open the Maintain users tab (Onderhoud gebruikers)

  2. Click New (Nieuw). A four-step wizard opens. Nobody logs in with this user, so fill in as little as possible.

  3. Name (Naam): enter Homerun as the Last name (Achternaam). Full name and search name fill in automatically. Leave the rest empty.

  4. General (Algemeen): keep the generated user code (for example 39700.1001493). Enter Homerun as the description and leave Blocked (Geblokkeerd) unticked.

  5. Access (Toegang): untick Profit Windows, InSite and OutSite. The connector doesn't need a login, and a user without access doesn't take a seat. Leave the Advanced and ASP options unticked.

  6. E-mail: leave E-mail and UPN empty. If AFAS won't let you finish without an email address, use a shared mailbox such as it@yourcompany.com, never a person's address.

  7. Click Finish (Voltooien)

Create the user group

  1. In the Authorisation tool, click New under user groups (Gebruikersgroep > Nieuw)

  2. Choose Create a completely new user group (Maak een geheel nieuwe gebruikersgroep), not a copy, and click Next (Volgende)

  3. Fill in the following:

    1. Group (Groep): a short code, for example HOMERUN

    2. Description (Omschrijving): Homerun koppeling

    3. Blocked (Geblokkeerd): leave unticked

    4. Fill based on (Vullen op basis van): change the default Function to Manual (Handmatig). With Function, AFAS fills the group with everyone in a job instead of the one user you choose.

  4. Skip the explanation step and click Finish (Voltooien)

  5. On the Maintain groups tab (Onderhoud groepen), select the new group

  6. In the right-hand pane, open Users in group (Gebruikers in groep) and click New (Nieuw)

  7. Tick only the Homerun user you just created and click Select (Selecteren)

Step 2: Give the user group access to employees

Before Homerun creates a new hire, it checks AFAS for an existing person with the same last name and date of birth. The user group needs access to employees for that check.

  1. In the Authorisation tool, select the HOMERUN group on the Maintain groups tab (Onderhoud groepen)

  2. Open the Maintain filters tab (Onderhoud filters) and expand HRM

  3. Set Employees (Medewerkers) to Full access (Volledige toegang)

  4. Check that Employers (Werkgevers) and Organisational units (Organisatorische eenheden) also show Full access. You can leave Applicants and Applications (Sollicitanten, Sollicitaties) as they are.

Note: A new group starts on By filters (Volgens filters). If the group can't see an employee, AFAS returns no results and the duplicate check sees nothing. Homerun detects this and won't send, so no duplicates are created, but nothing reaches AFAS until access is fixed.

Step 3: Create an App connector with OAuth

  1. Go to General > Management > App connector (Algemeen > Beheer > App connector) and click New (Nieuw)

  2. Set Authentication type (Authenticatietype) to OAuth (1). Not Classic token (2) or Hybride (3).

  3. Under User group (Gebruikersgroep), choose the HOMERUN group

  4. In the OAuth section that appears, set Type OAuth flow to Client credentials (2), not Code (1), and click Next (Volgende)

  5. Under User (Gebruiker), choose Use existing user (Gebruik bestaande gebruiker) and pick the Homerun user from step 1. Don't leave it on Maak nieuwe gebruiker op basis van App connector-naam: that creates a second user.

  6. Link the connectors in the wizard (see step 4 for what each one does):

    • GetConnectors (GetConnectoren, step 2 of 4): click New (Nieuw) and add Profit_Employees

    • UpdateConnectors (UpdateConnectoren, step 3 of 4): click New and add HrOnboarding with the description Onboarding

  7. Step 4 of 4 shows the OAuth client id and OAuth client secret. Copy both straight into your password manager with Copy (Kopiëren), then click Finish (Voltooien).

  8. Give the App connector a description, for example Homerun

Note: AFAS shows the client secret only once. Never put it in a screenshot, email or chat. The authentication type can't be changed after saving. Don't use the classic token (AfasToken): AFAS retires it on 31 August 2027.

Step 4: Link the connectors

The App connector needs exactly these connectors. If you linked them in the wizard in step 3, check them here. On an existing App connector, add them on the matching tab.

Tab

Connector

Used for

UpdateConnectors

HrOnboarding

Creating the new hire in Onboarding

GetConnectors

Profit_Employees

The duplicate check before sending

GetConnectors

Homerun_Profiles

Showing your onboarding profiles as a list in Homerun

Use Profit_Employees, not Profit_Employees_basic. Homerun checks the links when you connect and tells you which one is missing.

Import the Homerun profiles connector

Homerun_Profiles reads your onboarding profiles, so you can pick one from a list instead of typing its number.

  1. Download Homerun_Profiles.gcn

  2. Go to General > Output > Management > GetConnector (Algemeen > Uitvoer > Beheer > GetConnector), click Import, choose File and select the file

  3. On the App connector, add Homerun_Profiles under GetConnectors, next to Profit_Employees

Step 5: Unblock the App connector

  1. Untick Blocked (Geblokkeerd) on the App connector

  2. Make sure you have the client ID and client secret from step 3 in your password manager

  3. Optional: restrict the connector to IP addresses. Ask Homerun support for the current list first.

Lost the secret, or did it end up somewhere it shouldn't? Open the App connector, go to the OAuth section and click Renew (Vernieuwen) next to the client secret. The old secret stops working straight away, so enter the new one in Homerun.

Step 6: Create an onboarding profile

  1. Go to General > In & OutSite > Profile (Algemeen > In & OutSite > Profiel). Already have an onboarding profile? Use it and skip to step 4.

  2. Click New (Nieuw) and give the profile a name, such as Homerun onboarding (see the AFAS help article Profiel inrichten)

  3. Set Type to Onboarding (Onboarden) and Based on (Gebaseerd op) to your current hiring profile (indienstprofiel). On the next page, pick the workflow, assessment profile, matching and exit profile, then click Finish (Voltooien).

  4. Note the profile's number: the Sequence number (Volgnummer) column in the profile list. Filter Type profiel on Onboard to find it. You'll need it when you connect in Homerun.

Check the profile settings

The profile decides which fields AFAS requires. Homerun only sends name, email and date of birth. Everything else is filled in by the new hire or by HR during onboarding. Check these settings in particular:

  • Give every mandatory field a default value. AFAS requires these fields on every onboarding, and Homerun doesn't send them. A field without a default makes the send fail. HR can adjust the values per new hire in the onboarding workflow in AFAS. No vacancy is needed.

  • Portal access (Portaltoegang geven en/of deblokkeren) makes AFAS email the new hire an invite to the OutSite you pick, where they fill in their own details. That OutSite must be linked to a web location in your environment. Not using the portal yet? Untick it, and the onboarding stays with HR.

  • Birth registration (RsBi): if it's required, the country of birth (CoBi) must be optional or have a default.

  • BSN validation (SoSe) must accept an empty BSN, because the new hire enters it later.

Group

Fields that need a default

Contract

Cao, Arbeidsvoorwaarde, Type contract, Werkgever, Soort medewerker, Dienstbetrekking, Wachtdagen toepassen

Function (Functie)

Organisatorische eenheid, Functie, Kostendrager, Kostenplaats

Salary (Salaris)

Soort salaris, Salaris, Netto salaris, Periodetabel, Jaarloon BT

Tax (Fiscus)

Soort inkomstenverhouding, Aard arbeidsverhouding, Tabelkleur, Tabelcode, Loonheffingskorting, Zvw, Alleenstaande ouderenkorting, Premiekorting, Vakantiebonnen

The message De site is niet gekoppeld aan een weblocatie voor deze omgeving means the OutSite in your onboarding profile isn't linked to a web location. Link it in AFAS, or untick portal access in the profile (see step 6).

Still stuck?

Send Homerun support the full error message, including the AFAS log reference if there is one. AFAS support can look up that reference in your environment.

Related Articles
Did this answer your question?