HR and Payroll System in 90 Days: A Rollout Plan

Rolling out an HR and payroll system in 90 days is realistic if you split the work into 3 blocks of 30 days in the right order: first clean the employee master data and contracts, then put attendance and requests on one approval path, then run two payroll closes in parallel before switching over. This seventh and final part of Digitizing HR gathers the exercises from the six earlier parts into one plan, and states which decisions belong to the owner and which belong to the HR team. If you have not chosen a system yet, start with our guide to choosing an HR and payroll system, then come back to this plan, because it works with whichever system you pick.

Before day one: three decisions for the owner

The plan does not start with technology but with decisions only the owner or general manager can make. If they are postponed, the plan stalls halfway:

• Who owns the project: one named person from HR or administration, with dedicated time each week and the authority to request data from any department.
• What stops: the day the system becomes the only source; after it, no leave request is accepted on WhatsApp and no salary is changed in a side file.
• Who sees salaries: the list of names allowed to see wages and settlements, because employee data is personal data governed by the Personal Data Protection Law.

Everything else is an operational decision for the HR team: field formats, shift names, the order files move in, and request forms.

Days 1 to 30: the employee file and contract first

Everything after this reads from the file, so it comes first. Repeat the exercise from part one, then the part two exercise on every employee, not just 5:

• Week one: the task map from part one, plus a list of every file, sheet or group that holds employee data today.
• Weeks two and three: match 4 fields for each employee across the contract, the employee list and the last payroll: basic wage, allowances, start date and contract end date. Under Article 52 on the Ministry of Human Resources Labor Relations page, the contract template includes the agreed wage with its benefits and allowances, the start date and the term if the contract is fixed-term, so these fields are the skeleton of the file itself.
• Week four: move the cleaned data into the system and lock the old files as read-only. Article 53 states that the probation period may not exceed 180 days in total, so record its end date for every new hire so the system warns you in time.

The cleaning method itself is in our article on cleaning data before the move from the Excel-to-system series: nothing travels as-is, and every conflict is settled before the move, not after.

Days 31 to 60: attendance and requests on one path

Once the file is trusted, daily activity is attached to it:

• Attendance: define shifts as in part three, bring every check-in method into one record, and raise exceptions to the manager instead of deducting silently. Repeat the exercise comparing the attendance sheet with deductions for 3 employees at month end.
• Requests: the approval matrix from part four for your 5 most frequent requests, with a delegate and an escalation deadline, and leave balances that update themselves.
• The day WhatsApp stops: announced in advance; after it, any request that arrives by message is redirected to the system politely, not refused.

Here the owner decides one thing: who approves exceptions a department manager cannot, such as overtime above a set limit or salary advances.

Days 61 to 90: two parallel payrolls before the switch

Payroll moves last because it depends on everything before it, and because an error there lands straight in an employee's account:

• First parallel month: payroll is prepared the old way and in the system, and net pay is compared employee by employee. Every difference is explained: is it the file, attendance or a calculation rule.
• Second parallel month: repeated with the close checklist from part five, with an owner and a date for each step, until no difference is left unexplained.
• The switch: after two matching payrolls, the owner approves making the system the only source, and the old file is kept as a read-only archive.
• End of service: the part six checklist is added, because Article 88 requires entitlements to be settled within one week, or two weeks if the worker ended the contract, a deadline a manual calculation struggles to meet. Award details are in part six and the End-of-Service Award Regulations page.

The month after the switch needs close follow-up, as we explained in the first thirty days after the move.

The Origami view

We are a technology company that builds custom systems, apps and integrations, and when we work on HR we follow this same order: the file first, then daily activity, then payroll after two matching runs. A system built on top of mismatched data only moves the problem to a nicer screen.

We start from the exercises of the six parts themselves rather than a ready-made feature list, because they show what your business actually needs, then we build what is missing and connect it to the government platforms. That is how we build our services around how a business works, while legal questions are settled by the text of the law or a labor lawyer.

Conclusion: the end of the series

Digitizing HR is not buying software, it is an order of work: one correct employee file, then attendance and requests on one path, then payroll that proves itself through two parallel runs, then an end of service that comes out of existing data. This part completes the series, and you can return to any part in the knowledge hub when you reach its stage in the plan.

Sources

• Ministry of Human Resources and Social Development: Labor Relations — current text of Articles 51, 52, 53 and 88.
• Ministry of Human Resources and Social Development: End-of-Service Award Regulations — calculation rules.
• Saudi Data and AI Authority: Personal Data Protection Law — the framework for keeping employee data.

This article explains the mechanism and is not legal advice; confirm your case with the Ministry or a labor lawyer.