Accurate, automated, compliant payroll

The salary element: what everything is built from

A payslip is not one figure but a set of elements, each with its own behaviour: is it an earning or a deduction? does it enter the insurance base? is it taxable? does it count toward the end-of-service gratuity?

An element in Nova HR is more than a number field — it can be a fixed value, a percentage of another element, or a formula that computes itself from the month's variables. That is what lets a salary structure express the company's real policy instead of simplifying it to fit the software.

The open month: why a past month's figures never move

The most dangerous thing in any payroll system is not a calculation error but a figure that changes quietly after it was paid. A report that recomputes from current data gives a past month numbers different from what was actually paid — and nobody notices, because nobody reruns an old report.

So everything touching money in Nova HR requires an open month: the payroll calculation, both steps of attendance processing, recording an expense, cashing out a leave balance, and a promotion. Once the month is closed, transactions in that period cannot be edited.

An error found after closing is handled as an adjustment in the following month, as a separate line carrying its reason — not by reopening a closed month. A visible adjustment is clearer to any reviewer than a retroactively edited figure.

From attendance to pay: two steps, not one

Punches alone are raw data. What turns them into lateness, absence and overtime is the attendance rule assigned to each employee, then the attendance processing that runs that rule over the data.

Processing is deliberately split into calculate then post. Calculation produces the figures and shows them for review — where the anomalies surface: someone with a week's absence and no leave request, or a department whose overtime is several times its usual. Posting is what links the result to payroll.

Each step has a rollback. Finding a misconfigured rule after a run does not mean editing hundreds of records by hand: roll back, fix the cause, run again.

Loans and advances: a balance and an instalment, not a recurring deduction

The difference between an advance and an expense is not the amount but the direction. An expense is the employee's money returned once by the company; an advance is the company's money returned by the employee in instalments.

An advance therefore needs what an expense does not: an outstanding balance, a monthly instalment, an end date, and a settlement on leaving. Any treatment that deducts monthly without tracking a balance creates an obligation nobody knows the end of — discovered a year later still being deducted.

Cost centres: where the wage cost actually lands

Payroll is the largest expense line in most companies and the least detailed in their reports. The question many systems cannot answer is simple: how much did this project cost us in wages, and how much did this branch?

A cost centre is a decision independent of the org structure rather than a copy of it: a project staffed from three departments is one cost centre, not three. Assuming they coincide is convenient at installation and costly at the first financial report needing detail the structure does not provide.

The bank file and the statutory reports

The last step in the cycle is the one employees see: the money arriving. A bank file is not an ordinary export — each bank has a format that rejects the file if a single column is off, and the rejection usually happens after hours on payday.

Generating the file in the approved format — including wage-protection files in Saudi Arabia — is therefore part of the system rather than a manual step in Excel. On the statutory side, insurance and tax reports are derived from the same data the salary was paid from, so what was paid and what was filed cannot diverge.