Starting point
Personnel cards were kept in Oracle, while HR and time-and-attendance processes ran in Idenfit. New hires, role changes and leavers had to be entered in Idenfit separately. The goal was to treat Oracle as the single source and feed Idenfit from it.
What is transferred
The service reads the personnel list from an Oracle integration endpoint and writes nothing back to Oracle. It transfers the personnel card: name, contact details, start and end dates, employment and collar type. Company, branch, unit, title, job, team and termination reason are linked to the record as well. Leave and attendance records are outside the scope of this integration.
Matching and updates
Each record is matched by staff number against a local control table. Staff not in the table are created in Idenfit. When the summary value of a known record changes, the record is updated in Idenfit section by section: profile, contact, personal data, employment, family, education, bank and insurance. Definitions such as branch, unit and title are created in Idenfit first if they are missing; empty values fall back to agreed defaults.
Leavers
Staff who no longer appear in the source list are deactivated in Idenfit with the default termination reason. A person whose employment has ended in Oracle therefore does not remain active in Idenfit.
Operation
The service runs on the customer's server as a Windows service that starts automatically and runs at configurable intervals. Created, updated and failed records are reported by regular email, including the section where an error occurred; daily logs are kept as well. Owners are alerted if the source returns an empty response or the service stops. For staff added to Idenfit by hand, a matching row is entered in the control table first; otherwise the service tries to create the person again. Configuration changes take effect after a service restart.