The Employee File and Contract: One Source of Truth

The employee file is the record every HR process should read from: attendance, leave, payroll and end of service. When the wage in the contract differs from the wage in the employee list, or the start date in one file differs from the one in payroll, every later process is built on a wrong number. In part one we mapped where HR time goes; this second part lays the foundation: what the employee file holds, what the Labor Law requires in the contract, who may see salaries, and an exercise to check 5 employee files in one day.

What the employee master record is

The employee master record (master data) is one record per employee, where each piece of information is written once, and every other process reads from it instead of keeping its own copy. At a minimum it holds:

• Identity: name, nationality, national ID or iqama number and its expiry, address and contact details.
• Job: title, department, line manager, place of work and the actual start date.
• Pay: basic wage, every allowance by name and amount, and the bank account the salary goes to.
• Contract: fixed-term or indefinite, start and end dates, probation if any, and every renewal with its date.
• Documents: the contract copy, ID, qualification and medical insurance, each with a tracked expiry date.

The simple rule: if payroll needs the wage, it reads it from the record. If the end-of-service award needs the start date, it reads it from the record. Nobody copies and nobody retypes.

What the Labor Law requires in the contract

The Labor Relations page of the Ministry of Human Resources and Social Development publishes the current amended text, and it defines the fields your file should never be missing:

• Article 51: the contract is written in two copies, one for each party, and documented under the applicable rules. It is valid even if not written, in which case the worker alone may prove it by any means, and either party may ask for it in writing at any time.
• Article 52: the Ministry sets a standard template for each contract type, essentially including the employer's name and place of business, the worker's name, nationality, identity details and address, the agreed wage including benefits and allowances, the type and place of work, the start date, and the term if it is fixed-term.
• Article 53: any probation period is stated explicitly in the contract with a set duration, and may not exceed 180 days in total.
• Article 54: a worker may not be placed on probation more than once with the same employer, unless agreed in writing for a different profession or type of work, or after 6 months have passed since the previous employment with that employer ended.

Notice that Article 52 is almost a ready-made field list. If the master record carries those same fields, issuing and reviewing a contract becomes a read, not a retype. Always confirm entitlements for your case with the Ministry or a labor lawyer; this series explains the mechanism, it does not give legal advice.

Fixed-term contracts: dates you cannot afford to forget

The most dangerous thing to lose in a spreadsheet is a renewal date. Under Article 55, a fixed-term contract ends when its term expires; if both parties keep performing it, it is deemed renewed for an indefinite term, subject to Article 37 on non-Saudis. If it is renewed 3 consecutive times, or the original term plus renewals reaches 4 years, whichever is less, and the parties continue, it becomes an indefinite-term contract. Article 56 adds that a renewal period counts as an extension of the original term for rights tied to length of service.

In practice, the employee file must keep every renewal as its own dated line, not overwrite the old end date with the new one. A good system counts renewals, adds up the total term automatically, and warns well before a contract ends, so a manager makes the decision instead of the calendar making it for them.

Documenting contracts on the government platform complements this; it does not replace it: contracts are documented on Qiwa, and wages flow through the Wage Protection System. We will not re-explain the integration here; it is covered in integrating your systems with Saudi government platforms. What matters in this part is that what is documented on the platform must match your internal file, or you end up with two sources of truth.

Who may see the salary

Employee data is personal data, and wage, bank account and ID number are among the most sensitive fields. Moving this data from a shared folder into a system is a chance to set permissions properly instead of copying the mess:

• The employee sees only their own file.
• The line manager sees their team's job data, and sees salaries only if the business explicitly decides so.
• HR and payroll see wages and bank accounts, and every change is logged with who made it and when.
• Senior management sees aggregated reports without opening each file.

This is consistent with the Personal Data Protection Law issued by the Saudi Data and AI Authority, whose practical duties we cover in our PDPL guide for businesses. The address on file is not a detail either: Article 72 says a penalty notice goes by registered mail to the address in the worker's file if they refuse it or are absent, and Article 73 requires fines to be recorded in a dedicated register with the worker's name, wage, the amount, the reason and the date.

The Origami view

We are a technology company that builds custom systems and integrations, and the first thing we build in any HR project is the employee master record and its change log, before attendance or payroll screens. Everything that comes after reads from it, so any flaw in it multiplies in every process.

We prefer to migrate current data after cleaning it and matching it against the documented contracts, rather than copying spreadsheets as they are. That way the team starts with a record it trusts from day one, which is how we design our services around how a business actually works.

Exercise: check 5 employee files today

• Pick 5 employees from different departments, including one on a fixed-term contract renewed at least once.
• Gather 3 copies for each: the signed contract, their row in the employee list, and their row in the last payroll.
• Compare 4 fields: basic wage, allowances, start date and contract end date.
• Count renewals for each fixed-term contract and add up the term, then ask: do we know whether it has become indefinite?
• Ask who can open the payroll file today, and write down the names.

Every mismatch you find is the first item in your digitization plan, and every unexpected name on the list of people who can see salaries is the second.

Conclusion and next part

The employee file is not an archive; it is the source every process reads from. When the wage, the start date and every renewal are written once in one place, and it is clear who sees what, everything after gets easier. In the next part we move to attendance and shifts: how paper sheets become a record the employee, the manager and payroll all trust.

Sources

• Ministry of Human Resources and Social Development: Labor Relations — amended text of Articles 51, 52, 53, 54, 55, 56, 72 and 73 of the Labor Law.
• Saudi Data and AI Authority: Personal Data Protection Law — the framework governing how employee data is stored and accessed.