Salary components
Define earnings, allowances, and deductions once as reusable components rather than re-typing them each month.
Payroll that runs on a structure, not a spreadsheet you rebuild every month.
Farexa Payroll is built from salary components and structures, produces payslips through an approved run, and posts the result to finance — so a month's pay is a repeatable process, not a monthly rescue operation.
Payroll goes wrong when every month starts from last month's spreadsheet. Farexa builds it from reusable parts instead: salary components — earnings, allowances, deductions — assembled into salary structures you assign to employees. When a run opens for a period, it applies each employee's structure, factors in overtime, and produces payslips, so the calculation is the same shape every month and the only things that change are the inputs.
A run is not a single button that pays everyone with no trail. It moves through a review-and-approval step before anything is final: gross, deductions, and net are computed per employee, the run records how many employees it covers and its totals, and it's approved before it closes. Because the whole thing is a record rather than a file, a payslip from four months ago is still there to open, and a run carries its own currency for teams that aren't paid in one.
Payroll doesn't stop at the payslip. The result posts to the ledger like any other financial event, so wage cost lands in the accounts without re-keying, and it draws on the same employee, attendance, and leave records the rest of HR keeps — which is why overtime and unpaid days don't need to be copied in by hand.
Key features
What the payroll engine gives you.
Salary structures
Assemble components into structures and assign them to employees, so pay is driven by a definition, not a spreadsheet row.
Period-based payroll runs
Open a run for a month, apply each employee's structure, and produce the period's payslips in one pass.
Gross, deduction, and net per employee
Each payslip computes gross, deductions, and net, and the run records its employee count and totals.
Overtime in the calculation
Overtime feeds the run rather than being added on the side, so the payslip reflects the hours actually worked.
A review and approval step
A run is checked and approved before it closes, so nobody is paid off an unreviewed calculation.
Payslips that stay on the record
Every payslip is a stored record you can reopen months later, not a file that has to be regenerated.
Posts to finance, in its own currency
The run's result posts to the ledger as wage cost, and each run carries its currency for teams paid in more than one.
How it works
From salary structure to posted wage cost.
01
Build components and structures. Set up earnings, allowances, and deductions as components, assemble them into salary structures, and assign structures to employees.
02
Open the run for the period. Start a payroll run for the month; it applies each employee's structure and pulls in overtime and leave from HR.
03
Review gross, deductions, and net. Check the computed payslips — gross, deductions, net, and the run's employee count and totals — before anything is final.
04
Approve and close. Approve the run so the figures are fixed and the payslips become the period's record.
05
Post to finance. The run's wage cost posts to the ledger, so payroll shows up in the accounts without re-keying.
Who it's for
Who runs payroll here.
- HR and payroll officers — A repeatable monthly run built from structures, with a review step before anyone is paid.
- Businesses with variable pay — Overtime and allowances handled inside the run rather than bolted on in a spreadsheet.
- Manpower and service companies — Payroll over the same worker and attendance records the deployment side already keeps.
- Finance teams — Wage cost that posts to the ledger, so payroll reconciles like any other financial event.
Works with
What it draws on and posts to.
- HR — Employees, departments, and leave that payroll runs against.
- Attendance — Attendance and overtime feed the run instead of being copied in.
- Accounting — The payroll result posts to the ledger as wage cost.
- Workforce — Deployment and assignment context for the people being paid.
- Analytics — Payroll totals and history export for management review.
FAQ
What payroll officers ask.
How does Farexa calculate pay?
From structure, not from last month's spreadsheet. You define salary components — earnings, allowances, deductions — assemble them into salary structures, and assign those to employees. A payroll run applies each employee's structure for the period, factors in overtime, and produces payslips with gross, deductions, and net.
Is there an approval step before payroll is final?
Yes. A run is reviewed and approved before it closes. Gross, deductions, and net are computed per employee and the run records its employee count and totals, so nobody is paid off an unreviewed calculation.
Does payroll use our attendance and leave data?
Yes. Payroll runs against the same employee, attendance, and leave records HR keeps, so overtime and unpaid days feed the run instead of being re-entered by hand.
Does the payroll result reach the accounts?
Yes. A completed run posts its wage cost to the ledger, so payroll shows up in finance without re-keying, and each run carries its own currency for teams paid in more than one.
Can I reopen an old payslip?
Yes. Every payslip is a stored record tied to its run and period, so a payslip from several months ago can be reopened rather than regenerated.
Turn payroll into a run you repeat, not rebuild.
Book a walkthrough with your own salary structures and see a run produce approved payslips that post straight to the ledger.