An employee is a file, not a row
Each person carries their current contract, the history of amendments, their personnel documents and their place in the reporting structure. What changed and when is visible on the file, not inferred by comparing two documents with similar names.
The org chart is built from the same data — it is not a diagram maintained separately that falls out of date after the first reorganisation.
Timesheets and leave, in the same base as payroll
Time worked, leave requests and remaining entitlement live together. The difference from a spreadsheet is that the payroll run reads exactly this data: an absence recorded here appears in that month's pay without anyone entering it a second time.
Advances, expenses and travel
Salary advances are withheld automatically at calculation. Travel orders generate the statutory per-diem, and reimbursed expenses reach the ledger as documents rather than as notes on paper. Each has its own approval flow.
Day labourers, in their own register
Day labour has its own legal regime — permitted sectors, a day cap, a mandatory register. It is kept separately from employment contracts, with bulk import for days already worked.
Benefits
Meal tickets, subscriptions and other benefits are configured per employee and enter payroll with the correct tax treatment — meal tickets, for instance, are subject to health contributions but not to pension, and the difference shows up in net pay.
Worth knowing
HR and payroll are not two modules exchanging files. They are the same data seen from different angles: what you record in the personnel file lands in the payslip, and what the payslip computes lands in the filing.