AFAS Profit integration • Automatic employee identity verification

Connect AFAS Profit to ID Scan.

Verify existing employees in bulk and automatically process new employees from AFAS Profit. You decide which AFAS connector and fields ID Scan uses. After verification, only the fields you explicitly map are written back and the digitally sealed ID Scan verification report can be stored in the employee dossier.

Open ID Scan portalSetup instructions

Set up the AFAS integration

The AFAS integration is configured from the ID Scan portal and uses an AFAS AppConnector token. The connector definitions remain under your control in AFAS Profit.

ID Scan Portal → Settings → API's and integrations → Integrations → AFAS → Manage

1

Create or select an AFAS AppConnector

In AFAS Profit, make the required GetConnector and UpdateConnector available to an AppConnector and generate a token for the connection.

2

Choose the AFAS environment

Select Test, Accept or Production and enter the AFAS environment number and token. ID Scan keeps synchronized data separated by environment.

3

Select the employee GetConnector

ID Scan reads the connector metadata available to the token. Select the GetConnector that exposes the employees and the fields needed to identify and contact them.

4

Map employee and result fields

Map the AFAS employee identifier, name, email and telephone fields. If verified data should be returned to AFAS, select an UpdateConnector and explicitly map each ID Scan result field that may be updated.

5

Configure the dossier report

Optionally configure the AFAS dossier item type for the verification report. After a successful verification, ID Scan can create a dossier item for the employee and attach the sealed PDF report.

6

Select a verification template

Choose the ID Scan template that determines which identity fields and checks are requested. Save the connection, then use manual employee selection or enable automatic onboarding for newly detected employees.

Your AFAS connectors, your field mapping

AFAS GetConnectors can be configured specifically for each organization. ID Scan therefore does not assume fixed employee field names. The portal reads the available metadata and lets you map the fields used by the integration.

Employee dataChoose the GetConnector and map the employee ID, given name, surname, email address and telephone number used for selection and invitations.
Verified dataWriting data back is explicit. Only ID Scan fields that you map to an AFAS UpdateConnector field are sent to AFAS; unmapped employee data is left unchanged.
Verification reportThe digitally sealed PDF report can be added as a dossier item attachment for the verified employee, using the configured AFAS dossier item type.

Manual selection or automatic onboarding

Use AFAS in the way that fits your onboarding process. Select existing employees yourself for a bulk verification, or enable automatic onboarding so newly detected employees enter the ID Scan verification flow without manual selection.

Select employees manuallyRetrieve employees through the configured GetConnector, search or filter the list and add the employees you want to verify to the ID Scan queue. This is useful for an existing workforce, a specific department or a one-time verification campaign.
Automatically verify new employeesEnable automatic onboarding and ID Scan periodically checks the configured GetConnector. Employees that appear after the initial baseline are automatically added to the verification flow and receive an invitation when the required contact information is available.
Safe first synchronizationWhen automatic onboarding is enabled, ID Scan first records the employees that already exist in AFAS as the baseline. They are not automatically invited. From then on, only newly detected employees are processed automatically.

1. Detect or select

Employees are either selected manually or detected automatically through the configured AFAS GetConnector.

2. Verify identity

ID Scan creates the verification request using the selected template and sends the invitation through the available configured contact channel.

3. Return the result

After successful verification, only configured result mappings can update AFAS and the digitally sealed PDF report can be added to the employee dossier.

Test safely before going live

Configure the integration against an AFAS Test or Accept environment first and switch to Production when the connector definitions and mappings have been validated. When connection-identifying environment settings change, ID Scan clears locally synchronized AFAS state so records from different environments are not mixed. Reusable connector and field configuration is preserved where possible and validated against the new environment.

Controlled data exchange

The AFAS integration follows the same data-minimization approach as ID Scan itself. The employee connector determines what AFAS exposes, the verification template determines what ID Scan verifies, and the write-back mapping determines which verified values may be returned.

AFAS remains the sourceEmployee records are read through the GetConnector selected by your organization.
No implicit overwriteID Scan does not decide which AFAS employee fields should be replaced. Write-back occurs only for mappings you configure.
Sealed evidenceThe verification report provides a digitally sealed record of the identity verification and can be stored with the employee dossier.

Credits and billing

AFAS verifications use the available ID Scan credits on your account. If there are insufficient credits, new verifications are not started until credits are available again.

Would you like to process verifications on a postpaid basis? Please contact us at info@id-scan.nl.

Support and troubleshooting

A connector is not available

Check in AFAS Profit that the GetConnector or UpdateConnector has been added to the AppConnector used by the token. ID Scan can only use connectors exposed to that AppConnector.

An employee field is missing

Add the required field to the AFAS GetConnector and refresh its metadata in ID Scan. Because GetConnectors are organization-specific, ID Scan only offers fields exposed by your connector.

The PDF is not added to the dossier

Check that the AppConnector permits the required dossier UpdateConnector and that the configured dossier item type can be used for the employee. Also verify the employee identifier mapping.

Need help?Contact ID Scan support at info@id-scan.nl.