To prevent duplicate employee records when connecting skills data to an HR system, match each incoming profile to a stable, unique employee identifier from the authoritative HR source before creating or updating records. Set rules for rehires and worker-status changes, reconcile existing identities, and handle skill-name cleanup as a separate task: a consistent skills vocabulary does not prove that a profile belongs to the right person.
Separate employee identity matching from skills harmonization
There are two different problems to solve:
- Duplicate employee records: the same person appears more than once in an HR or identity system. Prevent this with an authoritative source, a stable identity key, explicit matching rules, and a review of existing records.
- Duplicate skill labels: different labels in an imported feed refer to the same skill in the destination library. Prevent this by mapping incoming labels to a governed skills taxonomy.
For example, ServiceNow documents mapping an imported label such as “Java 1.8” to the existing “Java” entry in its skills library. That avoids a second skill entry; it does not determine which employee should receive the skill. ServiceNow’s dynamic skill import documentation, updated March 12, 2026, describes this mapping workflow. Its applicability depends on the release and source system; the documented dynamic import currently uses Credly.
As an Amazon Associate I earn from qualifying purchases.
Choose the authoritative source and a durable employee ID
Decide which system owns workforce identity and employment status, and which system owns skills. For identity, select an identifier that is unique across the populations included in the integration and remains usable through the lifecycle events you support. GOV.UK describes an identifying attribute as “a unique attribute or combination of attributes that can be used to identify a person or organisation.” Its example uses an employee number to distinguish people who share a name. GOV.UK guidance on creating and sharing attributes explains the role of these identifiers.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesDo not use a display name as the primary matching key: two employees can have the same name, and names can change. Confirm how the chosen ID is represented in each system, whether it is unique across employees and contingent workers, and what happens to it when someone leaves and later returns.
#1 Best Overall
- Guide students toward a healthy lifestyle, both physically and financially
- This revised and expanded edition adds much more information on work ethic, nutrition, and exercise; updates the sections on sexually transmitted diseases and drugs; and includes completely new sections on preparing financially for the future
- Graphic organizers, self inventories, puzzles, real-life situations, and cloze activities provide creative opportunities for students to assess their own lifestyles and make good choices for the future
- Prepare students for adulthood
- Practical lessons to help handle real life events
Configure matching before provisioning records
Map the source employee ID to the destination’s unique employee attribute, then confirm that the pair uniquely identifies a person. Configure any matching precedence and fallback behavior deliberately. A failed or ambiguous match should go to review rather than silently creating another employee record.
In Microsoft’s Workday-to-Active Directory example, the default mapping uses Workday WorkerID against Active Directory employeeID. Microsoft’s planning guidance also describes assigning precedence when multiple matching attributes are used. In its API-driven provisioning FAQ, Microsoft documents a default externalId-to-employeeId pair for that flow and says the matching pair must uniquely identify users. These are Microsoft product examples, not universal field names; verify the mapping in the connector and tenant you are deploying. See Microsoft’s cloud HR provisioning plan and the API-driven provisioning FAQ.
Write down lifecycle rules before the first sync
A matching key is only reliable if the organization agrees how it behaves during employment changes. Microsoft’s cloud HR provisioning planning guidance calls out lifecycle questions that should be settled for the selected system and connector:
Recommended Free Tools
- Does a rehire retain the previous employee ID, or receive a new one?
- Are future-dated hires provisioned before their start date?
- If a person moves between employee and contingent-worker status, should the existing account remain associated with that person?
Document the expected create, update, and no-match outcomes for these cases. Without an agreed rule, a technically valid integration can still treat a returning or reclassified worker as a new person.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Reconcile existing records and collisions before enabling sync
Before production provisioning, compare the source and destination populations. Look for repeated employee IDs, mismatched identifiers, existing duplicate employee records, and username collisions. Microsoft’s deployment guidance recommends identifying the HR or other source of record and checking source-data quality as part of provisioning preparation. Microsoft’s Entra ID Governance deployment guide provides that broader source-quality context.
For SAP’s Workforce SCIM API, SAP states that the documented SCIM APIs do not support case-sensitive usernames and advises checking for duplicate usernames before enabling the case-insensitive username option. This guidance applies to that SAP configuration, not every HR integration. See SAP’s Workforce SCIM API overview.
Use a controlled implementation sequence
- Inventory ownership. Identify which system is authoritative for employee identity, employment status, and skills, and document the source fields used for each.
- Validate the identity key. Confirm the ID is unique across the integrated population, correctly represented in source and target, and governed for rehires and worker conversions.
- Set and verify the matching pair. Map the source employee ID to the destination’s unique employee attribute. Define precedence and ensure unmatched or ambiguous records cannot silently create a second person.
- Reconcile the current population. Resolve duplicate IDs, source-to-target mismatches, existing duplicates, and relevant username collisions before loading new data.
- Test lifecycle and exception cases. Use controlled records to test create, update, rehire, employee-to-contingent-worker conversion, and no-match outcomes. Review provisioning logs to verify that an existing employee is updated rather than recreated. Exact test mechanics depend on the HR system and connector.
- Normalize skills separately. Map incoming skill labels to the destination library, retain the employee identifier through the transformation, and send uncertain vocabulary matches for review.
- Monitor conflicts and unmatched profiles. Assign owners to correct source identifiers and taxonomy mappings. Set review rules appropriate to your data; the cited platform guidance does not establish a universal matching algorithm or threshold.
Check the platform-specific behavior you are deploying
Vendor examples are useful for understanding available controls, but they are not a universal schema or implementation requirement. Check the exact release, connector, and tenant configuration before adopting field mappings or workflow assumptions. Microsoft’s Workday and API-driven examples use different documented matching pairs; SAP’s username guidance concerns its Workforce SCIM API; and ServiceNow’s skill-import behavior depends on its release and source-system support.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
