Overview
HR systems rarely fail at features. They fail at the record. The same employee exists in the attendance sheet, the payroll workbook, the leave register and the folder the PRO keeps — and by March those four sources disagree about when he joined, what he earns and how many days he has left. Every argument after that is really an argument about which copy is right.
Nama HR is built the other way round: one employee, one record, and every event in the person’s working life written against it. Attendance, leave, loans, penalties, appraisal scores, training, health insurance and government documents are not separate registers that have to be reconciled. They are transactions on a file.
Two layers to an employee
The personal and job side of the file — name, contact details, passport and residency, department, job position, bank account — sits on the employee record itself. Everything the salary engine needs sits on a companion record beside it: which calendar the person is paid against, which salary structure applies to them if they have no terms of their own, the contract period, and their own dated salary component lines.
That last part is what makes a raise or a temporary allowance safe. A component line carries a from-date and a to-date, so a change is scheduled rather than typed over the top of history: last year’s salary is still there, still explains last year’s payslips. Allowances such as housing and transport are switched on per employee rather than inherited silently from a structure, which is exactly the sort of assumption that produces a payroll everybody distrusts.
The pattern every HR screen follows
Almost everything that happens to an employee is recorded through the same three layers, and once you have seen it once you can read any screen in the module.
- A request is an application. It carries the real fields — employee, dates, amounts — plus an approval state: initial, accepted, rejected, processed. A request has no financial effect at all. It is the paperwork for a decision.
- A document is the executed transaction. Saving it is what consumes the leave balance, disburses the loan, or puts the new hire on the payroll. It can be generated straight from an accepted request, and the picker only ever offers accepted ones.
- An aggregated document does the same thing for three hundred people in one pass, for the days when HR is a batch operation rather than a conversation.
The moment a document is created from a request, the request flips to processed — so the same approval can never be spent twice. And because the request layer is optional, an organisation that does not want an approval step for, say, short leave permissions simply enters the document directly.
The calendar underneath payroll
Payroll runs against its own year and its own periods, deliberately separate from the accounting fiscal year, because a pay cycle rarely matches a financial one. Periods are opened and closed, which is what stops a corrected document from quietly reopening a month that has already been paid. A company can also run more than one pay stream — main salary and commissions, for example — with each employee’s component lines tagged to the stream they belong to.
Health insurance, kept as a record rather than a spreadsheet
In the Gulf, private cover is a legal obligation rather than a benefit, and the liability lands on the employer when a policy lapses or a dependant was never added. Nama tracks the insurer’s offer, the enrolment of employees and their families onto a policy, claims made against it, mid-year upgrades to a richer tier, and clean removal when someone leaves — against the same employee file the rest of HR uses.
Where the deadlines live
Passports expire. Residency permits expire. Work licences expire. Those dates sit on the employee record, and the transactions that renew them — with their government fees — are a separate area of the module written for the person who does that job full time.
The employee record, the request-and-document pattern, the payroll calendar and the health-insurance flow are documented in full in the HR documentation, starting with requests, documents and aggregated documents.
