THAR
Knowledge Center/Integrations/AFAS

AFAS Integration Guide

Learn how to connect employee and organisational data between AFAS and THAR.

Last updated: Aug 15, 2026Reading time: 6 mins

Overview

AFAS is a widely used HR and payroll platform in the Netherlands. The THAR–AFAS integration allows organisations to automatically synchronise employee records, departments, and organisational structures between the two systems.

This guide covers how to set up, map key fields, configure synchronization frequencies, and troubleshoot common configuration issues to ensure seamless daily operations.

What this integration does

  • • Automated Employee Import: Pulls active personnel records directly from AFAS into THAR database.
  • • Organizational Alignment: Replicates department and structural teams to ensure training pathways map accurately.
  • • Lifecycle Syncing: Detects newly added profiles, leavers, and position upgrades dynamically.
  • • Error Prevention: Standardises data inputs, preventing misspelled entries or missing certification fields.
  • • Flexible Triggers: Runs automatically on schedule or instantly with a "sync now" admin manual trigger.

Requirements

Before commencing the setup, ensure that all network connections and authentication variables are provisioned as listed below.

Prerequisites Checklist

  • • An active AFAS environment with App Connector / API access enabled
  • • A THAR administrator account with integration permissions
  • • Your AFAS Token XML containing your generated API token
  • • Network connectivity between your AFAS environment and THAR's API endpoints

Setup instructions

1

Generate an API token in AFAS

Log in to your AFAS Profit environment with administrative privileges. Navigate to General > Profit Management > Generate Token. Ensure appropriate permissions are ticked for user profiles. Copy the generated XML token — you will need it in step 3.

2

Open the THAR Integration Settings

Access your THAR portal as an Administrator. From the sidebar menu, navigate to Settings > Integrations > AFAS. Select 'Configure integration'.

3

Enter your AFAS credentials

Paste your AFAS API token in the token input area. Enter your verified AFAS Environment URL. Click 'Test connection' to run a system heartbeat check.

4

Configure data mapping

Map relevant employee details. Inspect the recommended default mapping table and adjust optional fields like contract types, function designations, and telephone metadata.

5

Set synchronisation schedule

Define your operational update frequency: choose hourly, four-hour blocks, once-daily syncs, or manual sync-on-demand only.

6

Activate the integration

Validate all inputs, confirm your checklist, and click 'Activate Integration'. An initial structural database sync executes instantly upon confirmation.

Configuration

Field Mapping Values

AFAS Field

THAR Field

Status

Medewerker naam

Employee name

Active

E-mailadres

Email

Active

Afdeling

Department

Active

Functie

Role / Function

Active

Startdatum

Start date

Active

Contracttype

Contract type

Optional

Sync Frequency Recommendations

Frequency Option

Recommended Use Case

Every hour

Highly fluid organizations experiencing multiple active contractor shifts hourly.

Every 4 hours

Standard setup. Catches morning/afternoon roster shifts with minimal API overhead.

Daily

Stable corporate structures with low weekly employee onboarding volumes.

Troubleshooting

Issue 01

Problem: 'Connection failed' error when testing connection.

Solution: Double check your endpoint syntax and ensure your AFAS App Connector token has not been revoked. Confirm that external network firewalls allow inbound traffic from THAR production IPs.

Issue 02

Problem: Employee details not synchronising into THAR database.

Solution: Ensure the medewerker's active contract box in AFAS matches the filter profile criteria. Deactivated, draft, or pending contracts are excluded from daily sync scopes by default.

Issue 03

Problem: Department structural designations mismatches.

Solution: Department code configurations must match exactly. If structural alignment differs, establish manual translation pathways within THAR's Advanced Fields Editor.

Need help setting up this integration?

Can't find the answers or having configuration issues? Get in touch with the THAR team. Our specialists are ready to assist you.

Contact support