AFAS Profit logoCornerstone OnDemand logo

Training and certificates

AFAS to Cornerstone integration: employees and organisational units from AFAS, completed training back

With an integration between AFAS Profit and Cornerstone OnDemand, employees from AFAS appear in Cornerstone automatically, with manager and with employer, unit, cost centre and job as organisational units. Completed mandatory training comes back to AFAS as a course on the employee, with the period in which the certificate is valid.

What the integration does

Organisations that run HR in AFAS Profit and organise mandatory training in Cornerstone often load employees with a file someone exports from AFAS periodically. After a reorganisation Cornerstone assigns training on the old structure, and earned certificates are not in the AFAS file.

  1. HR processes the new employee or the change in AFAS, as today.
  2. KoppelHet reads the changes and puts new units, cost centres, jobs and employees together in one job for Cornerstone.
  3. Cornerstone processes the job and assigns training based on the organisational units.
  4. KoppelHet fetches the result per record and reports rejected employees to HR.
  5. Completed mandatory training arrives as a course on the employee in AFAS; after the termination date the user becomes inactive.
AFAS Profit → KoppelHet → Cornerstone OnDemandSOURCEAFAS ProfitTARGETCornerstone OnDemandKoppelHetmapping · logging · monitoringAFAS Profit → KoppelHet → Cornerstone OnDemandSOURCEAFAS ProfitTARGETCornerstone OnDemandKoppelHetmapping · logging · monitoring
Out: User with name, work email and manager · Organisational units: employer, unit, cost centre and job · Status active or inactive
Back: Completed training with date and validity

What to watch for with AFAS Profit and Cornerstone OnDemand

  • AFAS has employer, organisational unit, cost centre and job as separate structures, and Cornerstone has its own kind of organisational unit for each. Every AFAS structure thus gets a fixed place, and a training coordinator can for example assign a training only to one job within one employer.
  • Cornerstone places an employee without a valid manager under the integration's own user. In AFAS not every employee has a manager filled in. KoppelHet then takes the manager of the parent unit, so training requests do not get stuck with a technical account.
  • With the default setting Cornerstone skips empty fields of existing employees. If HR removes a cost centre in AFAS, for example, the old one stays in Cornerstone. KoppelHet therefore sends a removed value explicitly, so Cornerstone does not assign on outdated data.
  • Cornerstone accepts only five running imports per type at a time, and the integration shares that capacity with manual imports through Edge Import. KoppelHet therefore bundles all AFAS changes of a round into one job, so there is room left for the administrator.
  • AFAS delivers dates as year-month-day. Cornerstone reads dates according to the culture given per job and otherwise swaps day and month. KoppelHet sets the job to the British notation with the year first, so 3 April does not arrive as 4 March.
  • Fields Cornerstone marks as secure or as sensitive personal data are not loaded by the Bulk API. That fits what KoppelHet reads from AFAS - only name, work address, structure and contract dates; citizen service number, date of birth and salary stay in AFAS.
  • As soon as the integration loads employees, the old data load wizard for HR data in Cornerstone must be switched off permanently. The periodic export file from AFAS therefore stops on the go-live day.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does all training go back to AFAS?

No, only the training HR designates as mandatory and that exists as a course in AFAS. The rest stays in the transcript in Cornerstone.

Can we keep using Edge Import?

Yes, for other data. Edge Import and the integration do share the same import capacity, and employees and organisational units then only come from the integration.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • AFAS is read with a dedicated GetConnector on employees, employments, organisational units, cost centres and jobs, filtered on change date, through an app connector. Training goes back through the HrEmpCourse UpdateConnector (certificate earned, valid from, valid until).
  • Cornerstone is written through the Bulk API (OAuth 2.0, asynchronous) - one job with imports for Legal Entity, Division, Cost Center, Position and Employee, datetime_culture en-GB, results per import through report, warnings and errors (kept for 30 days). Capacity 50 jobs and 5 imports per type per environment, shared with Edge Import.
  • Training results are read through the Reporting API (OData, read-only, on the Real-time Data Warehouse).

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in AFAS ProfitField in Cornerstone OnDemandNotes
MedewerkerUser IDFixed key in Cornerstone
Roepnaam, Voorvoegsel + AchternaamVoornaam en achternaam
E-mail werkE-mail
LeidinggevendeManager (User ID)Empty? Then the manager of the parent unit
WerkgeverLegal Entity-OU
Organisatorische eenheidDivision-OUWith the parent unit as parent
KostenplaatsCost Center-OU
FunctiePosition-OU
Datum in dienst / Datum uit dienstStatus actief of inactief
Behaalde trainingCursussen per medewerker (HrEmpCourse)

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.