Most Qatar employers we meet are running payroll twice. Once in whatever HR system holds the employee records, and once again in a spreadsheet that actually produces the bank file — because the HR system was never set up to generate a WPS salary file, or was bought before WPS mattered. Every month, someone rebuilds that spreadsheet, checks it by eye, and hopes the bank accepts it.
That spreadsheet is the problem worth solving. Not because it is inelegant, but because it is the single point where an error becomes a late salary payment and a compliance issue.
WPS-compliant payroll, generated by the system
Qatar's Wage Protection System requires salaries to reach employees through the banking channel on a fixed schedule, with a salary information file submitted to your bank in a prescribed layout. That file needs the employer and payer identifiers at the top, then a row per employee carrying the QID, visa ID, bank short name, account number or IBAN, salary frequency, number of working days, and the breakdown of basic pay, allowances and deductions.
We configure ERPNext payroll so that file comes out of the system already correct. Your HR team runs the payroll for the period, reviews it, and exports. There is no parallel spreadsheet and no manual re-keying of IBANs — which is where transposition errors come from, and a transposed IBAN is a salary that does not arrive.
The screenshot on our homepage platform section shows the WPS report laid out with exactly these fields, taken from a live installation with employee identifiers removed.
What Frappe HR covers
Frappe HR is a complete open-source HR system that installs onto the same Frappe instance as ERPNext and shares its database. That shared database is the point: attendance feeds payroll, payroll posts to the ledger, and an employee exists once rather than once in HR and again in finance.
- Employee lifecycle — onboarding, confirmation, transfers, promotions and exit as tracked stages with their own checklists, rather than an email trail nobody can find in a year's time.
- Leave and attendance — leave types, balances, applications and approvals with the Qatar holiday calendar built in. Attendance arrives from biometric devices, access control or mobile check-in with geolocation for site-based staff.
- Shift management — rosters, shift assignment and shift change requests, for operations that do not run nine to five.
- Expense claims and advances — staff claim with a photographed receipt from their phone; outstanding advances allocate automatically against the claim instead of being reconciled by hand.
- Hiring — staffing plans, job openings, a public job portal and applicant tracking through to offer letter.
- Performance — appraisal cycles, goals and feedback recorded against the employee record and visible only to the right approvers.
- Payroll and WPS — salary structures, payroll runs, bilingual payslips emailed automatically, and the WPS salary file for your bank.
- Mobile app — check-in, leave, claims, advances and payslips from a phone, with workflow-aware approvals for managers who are rarely at a desk.
End-of-service gratuity, visible before it is due
Gratuity in Qatar is a real liability that accrues quietly and is usually calculated at the worst possible moment — when someone is leaving and everyone is in a hurry. We configure the calculation rules against your policy: the service-period bands you apply, which salary components count towards the calculation, and how unpaid leave is treated. The accrued liability is then visible in reporting throughout the year, not discovered at exit.
Where this matters most in Qatar
Two kinds of employer get disproportionate value from this. Contracting firms managing large labour headcounts across multiple sites, where attendance capture is genuinely hard, shift patterns vary, and payroll volume makes manual handling untenable — see our contracting and MEP contracting pages for how this fits the wider project picture. And schools and training institutes, where faculty payroll runs alongside student fee collection; we pair Frappe HR with the education modules covering student records, admissions, programmes, timetables, assessment and fee management, which is covered on the education page.
No per-user licence, at any headcount
HR systems are usually priced per employee per month, which means the software bill grows every time you hire. Frappe HR is open source under the GNU GPLv3 licence — you pay for implementation, hosting and support, and never for the right to add another employee record. For a business that grew from 80 staff to 400 over a few years, that difference is not a rounding error.
How we implement it
HR and payroll usually go in as a phase of a wider ERPNext implementation, or as a standalone project of three to six weeks if your accounts are staying where they are for now. The sequence is the same either way: we map your existing salary structures and leave policy, configure them, load employee masters and opening leave balances, run a parallel payroll against the last period you have already paid, and compare the output line by line against what your bank actually received. Only when those match do we go live.
Frequently asked questions
-
What is WPS and what does the system actually have to produce?
Qatar's Wage Protection System requires employers to pay salaries through the banking channel on a fixed schedule, and to submit a salary information file to the bank in a prescribed layout. The file carries employer and payer identifiers, then a row per employee with QID, visa ID, bank details, salary frequency, working days and the salary components. We configure payroll so that file comes out of the system correctly formatted — your HR team runs payroll and exports it.
-
Is Frappe HR a separate product from ERPNext?
It is a separate open-source app that installs onto the same Frappe installation and shares the same database. Practically, that means attendance feeds payroll, payroll posts journal entries straight into your accounts, and employee records are not duplicated between an HR system and a finance system. You can run it alongside ERPNext or on its own.
-
Does it handle end-of-service gratuity?
Yes. Gratuity is configured against the rules you apply — service period bands, the salary components that count towards the calculation and the treatment of unpaid leave. The liability is visible before an employee leaves rather than being calculated manually on the way out.
-
Can attendance come from our biometric devices?
Yes. Frappe HR accepts check-in and check-out data from biometric readers and access-control systems, and it also supports mobile check-in with geolocation for staff who work on sites rather than in an office. Attendance then drives leave balances, overtime and payroll without anyone retyping a timesheet.
-
Can employees see their own payslips and apply for leave themselves?
Yes, through the employee portal and the mobile app. Staff apply for leave, claim expenses with a photographed receipt, view their salary slips and see their leave balances. Managers approve from the same place. That removes most of the paper traffic that HR departments spend their week on.
-
Do we need this if we only have 30 employees?
WPS compliance applies regardless of headcount, and building the salary file by hand in Excel every month is where errors come from. For a team of 30 the value is less about the HR features and more about the payroll file being produced correctly and the gratuity liability being visible. For 300 staff across sites, the attendance and shift handling matter as much as the payroll.
-
Does it support Arabic payslips?
Yes. Payslips, offer letters and HR documents can be produced as bilingual Arabic–English print formats, the same way we handle tax invoices and delivery notes on the finance side.
GET STARTED
Show us a payroll run
Tell us your headcount, how attendance is captured today and which bank you submit WPS files to — we will show you the same run inside ERPNext.