Connecting an LMS to HR Systems in Saudi Arabia

The integration went live on a Thursday. By Sunday, HR in Riyadh had three complaints. An accountant who had moved to the procurement department in Jeddah had not been assigned the procurement policy course, his former manager was still receiving his reminders, and the monthly report credited his completed courses to a department he no longer belonged to. The connection between the HR system and the LMS software was working exactly as built. The problem was what it had been built to send.

Most HR integration problems in Saudi organizations are not technical failures. They come from a field map nobody wrote down: which fields leave the HR system, what each one means in the LMS software, which system has the final word, and what should happen when an employee moves.

This article walks HR, IT, and procurement teams through those decisions when connecting LMS software to HR systems: building the field map, confirming the reference source for each field, and handling employees who move between departments. It assumes your organization has already decided where employee data is mastered; if not, start with our guide to choosing an authoritative source for employee data.

Start with What the LMS Software Will Do with Each Field

Before listing fields, list purposes. An HR system can hold hundreds of attributes per employee, and most of them have no role in a learning management system. In the LMS software, an employee field usually earns its place for one of three reasons:

• Identity: matching the person between the HR system and the LMS software and signing them in, such as the employee number and work email.

• Placement: deciding which courses apply and how reports are grouped, such as department, job title, grade, location, and line manager.

• Visibility: deciding who can see whose records, such as the manager field and the organizational unit used for report access.

A field that serves none of these purposes should stay in the HR system and out of the LMS software. In the Kingdom, this is also a legal question. Article 19 of the Implementing Regulation of the Personal Data Protection Law published by SDAIA requires controllers to collect only the minimum personal data necessary for the purpose of processing, and to retain only the minimum. In practice, ask your data protection lead to confirm the final list, and expect fields such as the national ID or Iqama number, salary, home address, and family details to be removed unless a specific training purpose justifies them.

Building the Field Map for Your LMS Software

A field map is a simple table with one row per field. It turns an integration from a set of assumptions into a document that HR, IT, the training team, and the LMS software provider can all check. Useful columns include:

• The field name in the HR system and in the LMS software, exactly as each system spells it.

• Purpose: identity, placement, or visibility.

• Reference source: the system whose value wins if the two disagree.

• Format and allowed values, for example, a six-digit code or a fixed list of grades.

• Transformation, if the value must change on the way, such as combining name parts.

• Update timing: on change, daily, or on the effective date.

• Owner: the person who answers for errors in that field.

If your team needs a shared vocabulary, open standards can help. The IETF’s SCIM core schema (RFC 7643) defines a common user schema with an enterprise extension that includes attributes such as employeeNumber, costCenter, organization, division, department, and manager, where the manager value points to the identifier of the user’s manager. You do not need to use SCIM to borrow its naming, and you should not assume any LMS software supports it until the provider demonstrates it.

The Fields That Need Extra Care in Saudi Organizations

Identifiers

Match people in the LMS software on the employee number, never on names. Keep it as text so leading zeros survive, and confirm that it does not change when an employee moves, is promoted, or is rehired. Avoid the national ID or Iqama number as the matching key; it is more sensitive than training needs.

Names in Arabic and English

Many Saudi HR systems hold each name in both Arabic and English, sometimes in four parts. Decide which form the LMS software shows the learner, which appears in manager reports, and which is printed on certificates, and map each to its own field rather than letting one overwrite the other.

Dates and Calendars

Map every date with its format. If any date in your HR system, such as a hire date or contract end date, is held in the Hijri calendar while others are Gregorian, choose one calendar for the LMS software and record the conversion rule in the map. A due date calculated from a misread hire date is wrong for every rule that uses it.

Organizational Units

Send department codes as well as names. Names get translated, shortened, and renamed; codes are what assignment rules and reports in the LMS software should rely on. Record the code structure in the map so that a reorganization can be handled as one mapping change rather than hundreds of edits.

Confirming the Reference Source Field by Field

The reference source column is where the map usually exposes disagreements. During mapping, take a sample of 20 employees and compare the same fields in the HR system, the IT directory, and any spreadsheet the training team keeps. Wherever the values differ, record which source wins and who corrects the others.

Then mark the fields that belong to the LMS software and must never be overwritten by the sync: completion dates, scores, certificates, external training records entered by the training team, and approved exemptions. A sync that resets these whenever HR sends a full file will erase history without warning. Ask the provider to show, with your test data, what happens to an LMS-owned field when an HR record changes.

Handling Employees Who Move Between Departments

A department transfer tests a field map harder than any other change, because several fields change at once: department code, line manager, often location and cost center, and sometimes job title. Agree on how the LMS software should treat each part:

• Effective date. Transfers often take effect at the start of a month or after a handover period. Send the effective date with the change, and decide whether the LMS software applies future-dated transfers on the day or when they arrive.

• Manager handover. From the effective date, the LMS software should stop showing the employee’s open items to the previous manager and start showing them to the new one. Check whether pending approvals and overdue reminders move with the employee.

• Reporting history. Decide whether the LMS software reports completions under the employee’s current department or the department they belonged to when they completed the course. HR usually needs both views, so the department at the time of completion must be kept somewhere.

• Previous values. Carry the previous department code with the change, so that the rules deciding which courses stop and which continue have what they need.

The rules themselves, which assignments to add, which to stop and how to keep learning history intact, are a design topic of their own, covered in our guide to managing role changes in an Arabic LMS.

Finally, separate individual transfers from reorganizations. When two departments merge, or codes are renumbered, hundreds of employees appear to move on the same day. Handle this as a single code mapping in the LMS software, agreed in advance, rather than as hundreds of transfers that would each trigger reminders and reassignments.

A Hypothetical Example: A Food Producer Maps One Transfer

The following example is hypothetical and is included only to show how a field map works in practice.

A food producer with a head office in Riyadh, a plant in Dammam, and a distribution center in Jeddah is connecting its HR system to new LMS software. Its first field map has 34 fields. After the purpose test, the team keeps 14 and removes the rest, including national ID, home address, and bank details, once its data protection lead confirms they serve no training purpose.

The team then walks one transfer through the map: a quality inspector in Dammam moving to the production planning department in Riyadh from the first of next month. The test shows that department names in the HR system are in English while the LMS software groups reports by Arabic names, so the team switches its assignment rules to department codes. It also finds that the nightly full file would have reset the inspector’s completed food safety course, because completion dates had been mapped as an HR field by mistake.

Both issues are corrected in the map, not in the LMS software screens. The final document, 14 rows long, is signed by HR, IT, and the training manager and attached to the provider’s statement of work.

Summary

Connecting LMS software to an HR system in Saudi Arabia succeeds or fails on a document many projects skip: the field map. Decide what each field is for, keep only what training needs, record the reference source and format for every row, and protect the learning records that belong to the LMS software.

Then test the hardest case before go-live: an employee moving between departments, with a new manager, a new code, and a future effective date. If the map handles that, your LMS software will handle most of what follows. For the platform selection itself, see our guide to running a practical demo test of an Arabic LMS in Saudi Arabia.

Click here. If you are preparing a field map to connect LMS software to your HR system, you can discuss your requirements with the SkillUp MENA team.