AFAS | Translation Test

AFAS Software is a leading provider of ERP and HRM software, widely used to manage organizational processes and employee data. You can read more here: https://www.afas.com/

The Identum eADM for AFAS is a turnkey solution designed to automate the lifecycle management of digital identities. By connecting AFAS directly to Identum eADM, the system imports employee data, position data, and organizational hierarchy information. This ensures that user accounts in Active Directory, Azure AD, and other target systems are automatically created, updated, and disabled based on the authoritative HR data in AFAS.

This document provides technical instructions for integrating the AFAS Human Resource Management (HRM) system with Identum's eADM . It covers the initial setup, data import, and configuration for writing data back to AFAS

Prerequisites

Contact your AFAS support representative to request the API credentials for your AFAS instance. You must request the following:

Import User Data URL: The endpoint for importing user data.
Import Hierarchy Data URL: The endpoint for importing hierarchy data.
Writeback Data URL: The endpoint for writing user data back to the system.
SecretKey: A unique key for authentication.

Please forward this to your Identum partner so they can begin the setup process for importing user and hierarchy data from AFAS.

User Data Writeback

eADM be configured to synchronize user email addresses with AFAS. This is typically used to update AFAS with the email addresses of new employees once Identum eADM generated them in AD, Entra ID, or Google Workspace.

Appendix: Dutch Naming Conventions

The AFAS integration provides several attributes to correctly handle Dutch names, particularly prefixes and partner names. The following attributes are imported from AFAS and mapped to custom attributes in Identum eADM.

eADM Attribute	Description	AFAS Codes
extensionAttribute1	Marital Status: The user's marital status.	`$GH` (Married); `$GP` (Registered partnership); `$GS` (Divorced); `$0G` (Unmarried); `$TR` (Other); `$WE` (Widow/widower).
extensionAttribute2	Partner's Last Name: The last name of the user's partner.	N/A
extensionAttribute3	Name Use: Code that specifies which last name to display.	`$0` (Birth name); `$1` (Partner's birth name + Birth name); `$2` (Partner's birth name); `$3` (Birth name + Partner's birth name).
extensionAttribute4	Prefix (Birth Name): The user's surname prefix (e.g., "van der").	N/A
extensionAttribute5	Prefix (Partner's Last Name): The partner's last name prefix.	N/A
Last name	Last Name (at Birth): The user's last name at birth.	N/A

Typical Display Name Rules

The DisplayName should always be generated with any prefix included.
The prefix should not affect alphabetical sorting.
If Name Use is 1 or 3, the name parts should be separated by a hyphen.

To ensure sustainable management, we recommend using birth names for usernames and email addresses (UPN). This approach simplifies administration and maintains technical stability in the event of name changes.

Note: In the Netherlands, it is common to have a "nickname" (roepnaam). The system typically uses the official given name.

4. AI Summary

This document outlines the technical configuration for the turnkey integration between Identum eADM AFAS HRM. It guides administrators through obtaining API credentials, setting up data imports for HR and organizational hierarchy data, and configuring email writeback functionality. The guide also details specific attribute mappings and rules for handling Dutch naming conventions to ensure accurate identity synchronization across systems.