HR and Payroll Software Built for Qatar Labour Law

End-of-service gratuity, calculated and provisioned

Qatar Labour Law entitles an employee completing one year of continuous service to end-of-service gratuity of at least three weeks' basic wage per year of service, paid on the final basic salary, pro rata beyond whole years. We hold that entitlement as a slab table rather than a hardcoded formula, so contracts more generous than the statutory minimum — four weeks after five years, a full month after ten — are applied as written. Unpaid leave is deducted from effective service, so the figure matches what finance would compute by hand.

The part spreadsheets never do is provision booking. A monthly provision entry calculates each employee's incremental gratuity liability, totals the increase and decrease across the workforce, and posts the journal entry — so the balance sheet carries the real number continuously instead of absorbing a shock when three managers resign in the same quarter. Opening balances load for existing staff, so the provision is correct from go-live rather than only for new hires.

When someone leaves, EOS encashment settles the accrued figure against what was provisioned, and the difference posts automatically. No reconciliation by hand between what was accrued and what was paid.

Air ticket entitlement, allocation, booking and encashment

Air ticket allowance causes more disputes than almost anything else in Gulf HR, because the entitlement is a rule and the record is usually a memory. The system holds the rule explicitly: minimum service years, nationality or destination, frequency, and ticket value or class. Each employee accrues against it.

• Air ticket allocation. Entitlement accrues per the eligibility rule, visible per employee with the balance to date.
• Booking by the company. When management books the ticket directly, it settles against that employee's entitlement — so the same year cannot be both flown and encashed.
• Air ticket encashment. Where cash is taken instead, the amount is calculated from the entitlement rule and settled against the same balance.
• Provision booking. Like gratuity, ticket entitlement is a liability that accrues whether or not anyone flies. It can be provisioned monthly so the obligation sits on the balance sheet rather than appearing as an unbudgeted travel spike each summer.
• Settlement at exit. Outstanding entitlement flows into full and final settlement rather than being argued at the door.

Liability management across gratuity and tickets

Gratuity and air ticket entitlement are the two largest employee liabilities most Qatar businesses carry, and the two most often absent from management reporting. Provisioning both gives a running figure for what the company owes its workforce today — by division, by department, or consolidated — with each movement traceable to the employees who caused it. For an auditor, that is the difference between a defensible accrual and an estimate.

Annual leave: 21 days, 42 days, and automatic allocation

Qatar Labour Law sets a minimum of three weeks' paid annual leave for one to five years of service, rising to four weeks beyond five. In practice many employers run a biennial cycle: 21 days allocated each year, taken as 42 days every second year when the employee travels home. Both are held as leave slabs and allocated automatically on each service anniversary, so HR does not reissue allocations by hand and balances cannot quietly drift from the contract.

• Automatic allocation by service slab on the anniversary date, not a manual January exercise.
• Carry-forward under your own rule, with caps and expiry where you apply them.
• Paid annual leave encashment calculated from the balance and the applicable wage.
• Leave applications routed for approval, with the balance checked at submission rather than discovered afterwards.
• Opening balances and adjustments for migrating staff mid-cycle, with an audit trail on every correction.

Attendance, biometric integration and regularisation

Punch data from biometric and face-recognition terminals imports into attendance and is matched against each employee's assigned shift to produce worked hours, late marks, early exits and absence. Multi-site employers map each device to its location. Where a device misses a punch, a regularisation request routes to the supervisor for approval instead of someone editing the record silently — the correction is captured, and the audit trail survives a labour inspection.

Late excuses and overtime requests follow the same approval pattern, so what reaches payroll is reviewed data rather than a spreadsheet assembled the night before cut-off.

Shifts, week-offs and multiple holiday lists

• Shift assignment per employee or per department, read by the attendance engine as of each date — so a mid-month shift change does not corrupt the days before it.
• Fixed week-offs as a per-employee pattern: Friday for one group, Saturday for another.
• Week-off scheduler that generates the pattern forward, so rosters exist before the week starts.
• Switching week-offs for a single week without breaking the pattern that follows it.
• Multiple holiday lists in parallel, assigned per employee or department — office staff on one calendar, a plant that runs through public holidays on another, overseas sites on their own.

Full and final settlement

A leaver's settlement assembles gratuity, unused leave encashment, outstanding air ticket entitlement, pending expense and petty cash claims, notice pay or deduction, loan and advance recovery, and company assets still held — into one statement with a net payable figure and the accounting entries behind it. Finance stops rebuilding it from four spreadsheets while someone waits at the counter for their exit paperwork.

Employee asset management

Laptops, phones, vehicles, tools and safety equipment issued to staff are tracked against the employee holding them, with issue and return recorded. The payoff is at exit: the settlement knows what has not come back, so recovery is handled before the final payment rather than written off after it. For audit, every asset has a custodian and a history rather than a note in someone's inbox.

Manpower planning and replacements

Where a role must stay covered while its holder is on annual leave, the replacement is recorded against the period, so the roster shows the gap before it arrives rather than on the morning it does. Combined with the leave calendar and the biennial 42-day cycle, travel season becomes something you plan for in advance instead of absorbing.

Document renewal: QID, passport and visa

Renewable documents are held per employee with expiry dates and notification lead times. The value is not the record — it is the warning. A Qatar ID that lapses because nobody opened the tracking sheet means a fine and an employee who cannot work, and it is entirely avoidable.

WPS payroll your bank accepts

Qatar's Wage Protection System requires salaries to be reported in the Salary Information File layout your bank expects. The file is generated from the same payroll run that produced the payslips, so the figures reconcile by construction rather than by checking. Bank layouts differ in field order and padding, so we configure against your bank and test a real submission before go-live — not after a rejection on salary day.

Salary structures handle basic, housing, transport and the other allowance patterns Qatar contracts use, with deductions, loans and advances recovered on schedule.

Why this runs on Frappe HR

The foundation is Frappe HR, the open-source HR and payroll module built on the same platform as ERPNext. HR, payroll and accounting share one database, so a payroll run posts to the ledger with no interface to build or maintain, and gratuity provisioning posts journal entries directly. It is open source under GPLv3 — no per-user licence at any headcount, which is the opposite of how most HR products price as you grow.

What Frappe HR does not ship for this region — gratuity slabs, air ticket entitlement and provisioning, week-off pattern generation, biennial leave cycles — is built on top. Those are the parts we have already delivered across 15+ HR and payroll rollouts, so they arrive configured rather than discovered mid-project.

How an implementation runs

• Policy capture. Your gratuity slabs, ticket eligibility, leave cycle and week-off patterns written down as rules — usually the first time they exist in one place.
• Configuration. Salary structures, leave types, shifts, holiday lists, approval routing and device mapping.
• Opening balances. Leave balances, gratuity accrual and ticket entitlement loaded for existing staff, so day one is correct for everyone.
• Parallel run. One payroll cycle run alongside your current process and reconciled line by line before anyone depends on it.
• Go-live and hypercare. We stay through the first full month-end and the first WPS submission.