Skip to main content

Payroll

Payroll is where your workspace turns each employee's salary into a monthly pay run: it calculates gross pay, applies attendance-based proration, deducts tax and other statutory amounts, produces salary slips, and records how each person was paid.

All screens below live under Payroll in the admin sidebar (/admin/payroll/...). The exact deductions and tax math follow your workspace's country pack — for example, a US workspace withholds federal income tax from the year's brackets, while workspaces set to a Gulf country such as the UAE have no income tax. You never pick these formulas by hand; they come from the country set on your company profile.

note

Menu items and buttons only appear if your role has the matching payroll permission (view, process, approve, lock, manage, configure). If a page is missing, ask an admin to grant the permission.

The big picture​

A typical month runs in this order:

  1. Set up components and structures (one-time, then occasional edits).
  2. Assign a salary to each employee.
  3. Add any increments, bonuses or adjustments for the month.
  4. Process the payroll run for the month.
  5. Review → Approve → Lock the run — approval runs automatic pre-flight checks and is refused while any blocking problem remains.
  6. Mark as paid (disburse) and optionally generate the bank file.
  7. Send salary slips; employees acknowledge them in their portal.

1. Salary components​

Screen: /admin/payroll/components

A component is a single line that can appear on a pay slip — Basic, Housing Allowance, Provident Fund, Income Tax, Social Security, and so on. Click Add Component and fill in:

FieldWhat it does
Name / CodeLabel shown on slips; the short code (e.g. BASIC, TAX) is how the payroll engine recognises statutory lines
TypeEarning, Deduction, or Employer contribution
CalculationFixed, % of Basic, % of Gross, Computed by payroll (lines the engine works out from your country's rules by code: income tax, social-security contributions), or Computed by formula or tiers (a rule you write, evaluated every month; see below)
TaxableWhether the amount is included in taxable income, with an optional exempt portion (a share of basic or a flat cap)
MandatoryShown as mandatory on the structures that include the component
tip

The component with the code TAX is special: income tax is only deducted from an employee whose salary structure includes a TAX component. A structure built without it is treated as fully tax-exempt.

Computed components​

A component with Computed by formula or tiers is priced every month by a rule you write, for every employee on a structure that carries it: an attendance allowance that pays when the month was fully present, a commission on the month's sales reports, a performance bonus from merit points, an allowance that grows with years of service.

By formula takes an expression such as if(presentDays >= 22, round(basic * 0.1), 0) or min(salesMetric("new_sales") * 0.02, 25000). It can read basic, gross, the month's day counts (calendarDays, workingDays, payableDays, presentDays, absentDays, lateCount, overtimeHours and the rest), meritPoints from the performance ledger, yearsOfService, another line of the structure with component("CODE") (only a line above it in the structure), a weekly sales-report metric summed over the month with salesMetric("key"), and a few country-pack figures with pack("name"). It has min, max, round, floor, ceil, abs, if and the usual comparisons; What a formula may use on the form lists everything, with the rules the syntax does not show.

Saving checks the formula the way a run will read it, and refuses with the position:

  • a formula the engine cannot read;
  • component("CODE") naming a component the workspace does not have, or the line itself;
  • on a structure, a component("CODE") that is not on that structure or sits below the line that reads it, and a line set to Computed with nothing to compute.

Three rules hold when the run evaluates it:

  • Dividing by zero gives zero, not an error, so salesMetric("new_sales") / presentDays pays nothing in a month with no days present.
  • A result that is not a number, or is larger than a pay amount can be, fails that employee's entry and names the line. The employee is listed under the people the run skipped, with the reason; nobody is paid a silent zero, and the rest of the run is saved.
  • A number you type is an amount per run. basic and gross are the pay of the run being processed, and so are the day counts. On a pay group's run they are the period's (Pay schedules), so 500 pays 500 in every period, not 500 a month.

By tier table needs no formula: pick what to band on (merit points, a sales metric, a line), set the bands (up to 50 pays nothing, up to 80 pays 5%, above pays 10%) and whether a band pays an amount, a share of basic or a rate per unit.

Preview on the form prices the draft against any employee and month exactly as processing would, and shows every figure it read. Because it shows that person's salary lines, it needs the permission to view salaries (payroll.salary_view_all) as well as the one to configure payroll. A salary structure can also set its own formula on a row, overriding the component's for that structure.

The result is never negative and is rounded like every other line. A computed line is taxed and counted toward the statutory bases by its own flags, like any component, and on the amount actually paid: a commission paid in full to someone who joined mid-month is taxed in full, not at the share of the month they were present. Income tax and social security stay on Computed by payroll: those come from your country's rules, not from a formula.

2. Salary structures​

Screen: /admin/payroll/structures

A structure is a reusable template that bundles several components together (for example "Standard Employee"). Click Add Structure, give it a name, then add components one by one. For each row you set the calculation type and a value (or a formula) and whether it is mandatory. Click a structure to see its full component breakdown.

3. Assign salaries to employees​

Screen: /admin/payroll/salaries

Click Assign Salary and choose the employee, the structure, the pay basis, the gross salary (or the rate), and the effective-from date. This becomes the basis for every future pay run. When the workspace has pay schedules on (Pay schedules), a Pay schedule field names the pay group the salary is paid on; left on the default, the person is paid by the monthly run.

Pay basis decides how pay is earned:

  • Monthly salary — the gross is spread over the calendar days of the month and prorated by presence (absences, unpaid leave and lateness appear as deductions).
  • Daily wage — enter a rate per day. Payroll pays the rate for the working days actually worked: a half day pays half, approved paid leave pays a day, a weekly off or a holiday pays nothing unless it was worked, and then overtime prices it. There is no absence deduction, because nothing was contracted for the days not worked.
  • Hourly wage — enter a rate per hour and, if the shift's length is not right for this person, the hours in a standard day. Payroll pays the rate for the regular hours attendance recorded, leave days at the standard hours, and prices overtime separately. On a structure with no Overtime line there is nothing to price it, so every hour worked is paid at the plain rate instead (see Overtime pay).

For a daily or hourly wage the monthly equivalent shown in lists and reports is worked out from the rate and the workspace's working days a week (Attendance Settings); payroll never pays that figure, only the days or hours worked. Increments on such a record move the rate in step with the monthly equivalent. Nothing changes for existing employees: every salary on file is a monthly salary.

To give someone a different template later, use Change Structure on their row — it creates a new assignment from the effective date you pick, so history is preserved.

A new assignment replaces everything from its effective date on. An assignment that started earlier ends the day before the new one. One that starts on or after the new date no longer applies: it is removed, or, if a payroll run was already built on it, kept with that run and marked as replaced. So to correct a structure or salary recorded from the wrong date, assign again from the right date.

Saving also updates any payroll still open (a draft or in review) for that month or a later one that the employee is in: their pay there is worked out again on the new salary, as a reprocess of just them would, and no email is sent. The form says which runs before you save, and the page says afterwards whether each was updated. Approved, locked and paid runs are never changed. Updating a run needs the permission to process payroll; without it, the run keeps the old salary until someone who has it reprocesses the employee there (see Fixing a run before approval).

Salary history​

Assign Salary and Change Structure list every salary record on file for the employee: structure, gross, dates, the payroll runs built on it, and whether it is In force, Scheduled, Ended or Replaced. As you pick the effective date, the records the save would replace or end are marked, and a note above the save button says how many it replaces.

To undo a mistake, delete a record with the bin icon. If the record before it ran right up to it, that one applies in its place, so deleting the latest record reopens the previous one. A record that a payroll still open was built on (marked still open next to the run) can be deleted too: the employee's pay in that run is worked out again on the record that takes over. If that run cannot be updated (it was approved meanwhile, say), nothing is deleted and the panel says why. A lock icon instead of the bin means the record stays, for one of these reasons (hover for which):

  • an approved, locked or paid payroll was built on it — assign the correct salary from the right date instead;
  • a payroll still open was built on it, and deleting it would update that run, which needs the permission to process payroll;
  • an increment or decrement created it — correct it with another increment, or assign the correct salary;
  • it is the employee's only salary record;
  • it is the salary in force today and no earlier record would take its place, or a payroll still open was built on it and no other record would cover that month.

Dates and amounts are never edited in place: a record that payroll, tax and slips may point back to is replaced, not rewritten.

4. Increments, bonuses and adjustments​

These optional items feed into the pay run for their month.

  • Increments — /admin/payroll/increments A permanent salary change going forward (types: annual, promotion, performance, adjustment). Enter the employee, the new salary and the effective date. To lower a salary, use Process Decrement on the same page. Enter the reduced salary and a reason. If the email trigger and letter template are active, the employee gets a salary revision email and a decrement letter instead of the increment ones. The change shows in red in the list. A salary record dated on or after the effective date, such as a scheduled raise, is replaced, and the form warns before you save. Like a new assignment, an increment or decrement also updates any payroll still open for its month or a later one that the employee is in: the form says which runs before you save, and the page says afterwards whether each was updated. The same permission rule applies (see Assign salaries to employees).
  • Bonuses — /admin/payroll/bonuses A one-time payment for a chosen month (performance, festival, annual, signing, spot, or custom). A bonus is recorded as approved and the employee is emailed; it becomes paid when its month's run is locked, and can be edited or cancelled until then. In US, UK and Canadian workspaces a bonus is taxed as pay: the month's payroll takes income tax and contributions (FICA, National Insurance, CPP and EI) from it, as it does from salary. Elsewhere a bonus is paid on top of net pay, with no income tax or social security taken from it; to tax a payment as pay there, enter it as an adjustment with Tax applicable on. The Bonuses page says which applies to your workspace.
  • Adjustments — /admin/payroll/adjustments A low-ceremony one-off addition or deduction for a month. An addition with Tax applicable on is taxed as pay, for income tax and for contributions such as US FICA; leave it off for a reimbursement. Use it for corrections and edge cases.

Recorded bonuses

Bonuses and adjustments attached to a run are settled (marked paid) automatically when the run is locked, after which they can no longer be edited. Nothing can be added to a month whose run is locked or paid; use the next month. One added while the run is approved is paid only if the run is sent back to review and reprocessed, and locking is refused until it is. An approved expense claim becomes an addition in the current month, or the next month whose payroll is still open.

Payroll adjustments queued for the next run

Recurring deductions and garnishments​

A court order, union dues, an insurance premium or a savings plan is neither a loan (nothing was advanced) nor a one-off adjustment (it recurs until it ends). Recurring Deductions (/admin/payroll/recurring-deductions, under Payroll) records each one once and payroll withholds it every month.

Each deduction has an employee, a kind (garnishment / court order, union dues, insurance premium, savings plan, other), a name as it prints on the slip, an optional reference (the order, policy or membership number), and either a fixed monthly amount or a share of net pay. It runs from a start month until an end month, a cap on the total withheld, or a cancellation, whichever comes first. A priority decides the order when pay is short: a court order (10 by default) before union dues (100).

The engine takes recurring deductions after income tax, the country pack's contributions, loan instalments, the attendance docks and the month's adjustments, from what is left, in priority order. It never takes pay below the protected share of that figure: the country pack's statutory percentage where there is one (the United Kingdom, the United States, New Zealand, India and Singapore), the order's own figure, or no floor at all. A deduction that cannot be taken in full this month takes what it can; the rest is not carried forward, because an order names a monthly figure, not a debt. The share-of-net figure is worked out on pay before any recurring deduction, so the order of two deductions does not change their size.

A deduction is claimed when the run is processed and settled when the run is locked or paid, the way a loan instalment is: only then does Paid to date move, and a deduction whose cap is reached completes itself. Reprocessing a run before it locks releases and re-takes the month. Pause skips months without ending the deduction; Cancel stops it from the next run and keeps what earlier runs withheld.

The cap counts what is claimed as well as what is settled. With a cap of 1,000, 800 paid to date and 200 a month, a March run still in review has claimed the last 200: an April run processed before March is locked takes nothing more, where it used to take another 200. Locking never moves Paid to date past the cap either.

The slip prints one line per deduction, under its name and reference. The run page's breakdown and the payroll CSV carry the month's total. The Monthly register tab lists every deduction in force in a month with what the run withheld, paid to date and what remains of the cap, with a CSV for finance, headed and worded in the language you work in. In the accounting journal, recurring deductions fall under the existing deductions line.

Reading needs View All Salaries; recording, editing, pausing and cancelling need Manage Payroll. Employees see their own on the portal slip.

5. Process a monthly payroll run​

Screen: /admin/payroll/process

Monthly payroll runs and their status

Pick the month and year (the picker defaults to the previous month, since a month's payroll is normally run after it closes) and click Process Payroll. The system calculates every eligible employee and shows totals for employees, gross, deductions and net. Anyone it skipped is listed under the totals with their employee code and the reason; they are not in the run, so fix each reason and process the month again. The Checks before approval panel on the same page lists, for the selected month, everything that would stop approval before you process it.

Processing a month again rebuilds the run for the people payroll pays now. Someone the run no longer pays (they have left or been deactivated since, have no salary for the month, or are skipped) drops out of it, and so do their bonuses, adjustments and loan installment for the month: these stay unpaid, and locking or paying the run does not mark them paid.

If your workspace has enabled it in settings, a Skip attendance deductions checkbox appears — ticking it pays everyone in full for that run, ignoring absences, late days and unpaid leave.

Pay schedules​

By default every workspace pays monthly: one run per calendar month. A team paid weekly, every two weeks or twice a month is put on a pay group with that frequency, and its runs cover one period of the group's calendar each.

  1. On Payroll › Settings, tick Pay schedules and save. A Pay groups table appears below it: Add pay group with a name, the frequency, the first period start (a date a period begins on; weekly and fortnightly periods are counted from it, forwards and backwards) and how many days after a period's end the group is paid.
  2. On Employee Salaries, assign (or change) a salary with the Pay schedule set to the group. The record takes effect from its date, so a person moved mid-month is paid by the monthly run up to then and by the group from then on. Date the move on the first day of one of the group's periods (see Who each run pays below).
  3. On Process Payroll, choose the group under Pay schedule; the month picker is replaced by a Pay period list showing each period and whether it has a run. The dry run, the processing and the banners name the period. The run appears in Payroll History as its dates and the group's name, and the payslip names the period the same way.

What a period pays:

  • a monthly salary pays its share of the month (half for the 1st–15th, 12/26 for a fortnight) over the period's own days, so a day's absence on a half-month run is one fifteenth; fixed allowances take the same share; a daily or hourly wage pays the days and hours worked in the period;
  • income tax and the statutory contributions are worked out for the period as a share of a year of such periods (a fortnight is one of 26). A component's tax-exempt flat cap is a monthly figure, and a period exempts its share of it (a twelfth of the year's cap becomes a twenty-sixth on a fortnight), so the year's exemption is the same on any schedule;
  • a computed line's salesMetric and meritPoints read the period's own dates, so each weekly sales report and each merit point is counted by exactly one period, and a commission comes to the same total over the year on any schedule;
  • a bonus or adjustment can be dated to a period on its form; one left on a month is paid by the period that closes that month, with the month's loan instalment and standing deductions;
  • a pause for a month skips every period that ends in it.

Which period closes a month. Every calendar month has exactly one period of the group that closes it: the group's last period whose end date falls in that month. For a twice-a-month group that is the 16th to the month's end. For a weekly or fortnightly group it is the week (or fortnight) after which the next one ends in a later month, wherever in the month that leaves it: a fortnight ending on the 20th closes its month, because the next one ends in the following month. Every other period (the 1st–15th, the earlier weeks of a month) takes no month-keyed input. So a loan instalment and a standing deduction are taken once a month on every schedule, never skipped for months and then taken together.

Who each run pays. With pay schedules on, the default monthly run pays the people whose salary names no pay group, and a group's run pays the people whose salary names that group. Nobody is in both for the same days:

  • the salary record in force on a day decides which schedule that day belongs to (the newest start wins, as everywhere in payroll);
  • someone moved onto a group mid-month is paid by the monthly run for the days before the move and by the group's periods from the move on. In each run the days that belong to the other schedule earn nothing, the way the days before a joining date do;
  • a month's instalment, standing deductions and undated bonuses and adjustments are collected once, by whichever of the person's runs takes the month's inputs first. A group's first closing period does not collect again what the monthly run already took for that month;
  • a person whose pay schedule changes twice inside one run's dates is left out of that run and listed as skipped with the reason: date the salary records so that the schedule changes once in the period, then process again;
  • a person has one tax record per period start, and it is never overwritten. Two runs that start on the same day (June's monthly run and a twice-a-month group's 1st–15th of June) cannot both pay one person: the second to be processed leaves them out, listed as skipped with the run that holds the record. So date a change of schedule on the first day of a pay period: moved on the 1st the group pays the whole month, moved on the 16th the monthly run pays the first half and the group the second, and neither is refused. Moved on the 10th, whichever of the monthly run and the group's 1st–15th is processed second refuses them, and those days stay unpaid until the move is re-dated. If the run holding the record should no longer pay them at all, reprocess them there first and it lets them go.

Switch Pay schedules off again and the monthly run pays everyone as it did before, including people whose salary still names a group, so nobody silently goes unpaid.

The processing email and the payslip's file name carry a period's dates, so the two halves of a month are not both titled with the month. Pausing or resuming someone's pay is refused once the month's default run is approved, or once a group's period that paid them is; a locked period of a group they are not on does not stand in the way. Resuming puts them back into every open run of the month that pays them.

A group's frequency and first period cannot change once it has a run; deactivate it and create another instead. Processing a group's period needs payroll.process, as a month does; creating and editing groups needs payroll.configure.

Dry run​

Click Dry run instead of Process Payroll to calculate the month without saving anything. No run is created or changed and no one is emailed, so you can run it as often as you like. It shows the same totals, then one row per employee: the salary structure they would be paid on, gross, deductions and net. Click a row to see its components. Anyone who would be skipped is listed with the reason.

If the month already has a run, each person is compared with it. Net change shows the difference, a changed structure is shown under the new one, and Only show changes narrows the list to the people a reprocess would change. When the figures are right, click Process Payroll to save them.

A month whose run is locked or disbursed cannot be dry-run. An approved run can, so you can see what a reprocess would change before you send it back to review.

The processing email​

By default, processing emails each employee a Salary processed summary of their figures. Untick Email employees when processed to process the month without sending a single email, for example when you process it again after a correction. You can still send slips later with Email All on the Salary Slips page. Reprocessing selected employees from the run page never sends this email.

Pausing someone's pay for a month​

When someone's employment is paused for a month (an unpaid sabbatical, an agreed break), pause their pay instead of changing their status. On Process Payroll, the Pay paused for panel lists everyone paused for the selected month. Click Pause someone's pay, pick the person, the last month of the pause (or This month only) and a reason. You can also pause someone from their row in a dry run, or from their row in a run still in review.

For each paused month:

  • the run leaves the person out and lists them as skipped, with your reason. Processing, the dry run and reprocessing all do this, and the checks before approval list them as a note instead of flagging their attendance or salary;
  • if the month's run is still in draft or review, they are taken out of it at once: their entry, its tax record and PF ledger rows go, and the run's totals are recalculated;
  • their status stays Active. Leave accrual, length of service and gratuity carry on as usual;
  • a loan instalment due that month is not deducted; it waits for the next run;
  • an approved bonus or adjustment for that month is not paid. It stays approved and unpaid, and the checks before approval warn about it, so move it to a month the person is paid, or cancel it.

A month whose run is approved, locked or disbursed cannot be paused or resumed: its figures are settled. Send an approved run back to review first. A month in which the person's salary is on hold in the run cannot be paused either: release the hold first (see Holding a salary). One request pauses at most 12 months.

To pay the person after all, click the × next to their name in the panel and confirm. If the month's run is still open, they are added back to it at once (just they are reprocessed); otherwise the next processing includes them.

A loan instalment that waited through a paused month is deducted together with the next month's. The checks before approval warn when anyone will repay more than one instalment in a month, so you can check the amounts first.

Presence-based proration (the "sandwich" rest-day rule)​

Payroll prorates pay on a calendar-day basis: each employee earns payable days out of the month's total days, and pay is scaled by that ratio.

  • Working days are paid according to attendance (present days count, absent days do not, half-days count as half).
  • Rest days (weekly offs and holidays) are paid only when they sit between two earned days. An absence directly next to a weekend or holiday forfeits that rest day — this is the "sandwich" rule.
  • Mid-month joiners and leavers are prorated for the days they were actually employed.
  • Unpaid leave docks only its days in the month being paid. A leave that runs from one month into the next is split between the two payrolls, not charged in full to both.
  • Leave at reduced pay — a paid leave type whose Pay is under 100% — is paid at that share of each day, and the rest is part of the unpaid-leave deduction. See Leave at reduced pay.
  • Leave by the hour that is unpaid, or paid at a reduced share, docks its share of the day whatever the day's attendance says: four unpaid hours of an eight-hour day cost half a day's pay even though the day is marked present. A day never loses more than one day's pay in total, counting any absence dock. On a daily wage the day pays the rate less that share; on an hourly wage the hours off are simply not among the hours worked, and a leave type that pays a share has that share of them paid.

Rest-day swaps (a worked weekend traded for a different day off) are honoured in the same calculation. If Skip attendance deductions was used, everyone counts as fully present and no proration is applied.

Overtime pay​

Attendance decides how many overtime hours a month has: the time beyond the shift, above the minimum, and, where Require OT Approval is on, only the hours an approved request covers. Payroll decides what they are worth, in tiers:

TierHours it covers
Daily overtimethe overtime minutes of a working day
Weekly overtimehours beyond the country's weekly threshold (US 40, Pakistan 48, France 35) not already paid above
Rest-day workevery hour worked on a weekly-off day
Holiday workevery hour worked on a company holiday

Each tier is paid at the hourly rate times the country's statutory multiplier, or the workspace's Overtime Rate Multiplier where the law sets none. The hourly rate is the earnings flagged contributes to overtime (Basic, by default) over the month's standard hours for a monthly salary, the day rate over the standard hours for a daily wage, and the rate itself for an hourly wage.

Overtime is paid only when the employee's salary structure carries the Overtime component that came with the workspace (Salary Structures → add the component), as one earning line on the slip with the tiers listed in the entry's breakdown. A structure without it shows the hours and pays no premium, exactly as before, so no payroll changes until you add the line.

  • An Overtime earning of your own. If you created an earning coded OVERTIME yourself and gave it an amount, it is not that line: it is paid as the amount it carries, like any other earning, and no tiers are priced through it.
  • An hourly wage without the line. An hourly worker is paid for the hours worked, so on a structure with no Overtime line the hours beyond the standard day and the hours of a worked rest day are paid at the plain hourly rate, with no premium. The checks before approval list those people as a warning, in case the premium was meant.
  • Hours banked as time off. Where approved overtime becomes Compensatory Off (Banked overtime), the hours of a request that was banked are not priced, and the hours of one approved to be paid are. Payroll reads what each request became, not the setting on the day the run is processed, so the setting can change mid-month without an hour being lost or paid twice.

Income tax and statutory amounts​

Tax and other statutory figures come from your country pack:

  • Income tax — progressive slabs, a flat percentage, or none (for example, the Gulf states), depending on your country. Tax is applied only if the structure carries a TAX component (see the tip above). Where the statute taxes pay net of the employee's statutory contributions (the Philippines), those lines are taken off before the tax table is applied. German and French workspaces are asked to enter their own bracket table before approval — see the pre-flight table below.
  • Income tax is charged on the pay earned that month, not the contracted salary. Days docked for absence, unpaid leave, or late arrivals and early leaves are not taxed: each earning line counts only for the days that were paid, and its exempt portion (a share of Basic or a flat cap) is left out as usual. The payslip still shows every earning in full, with the docked days as their own deduction lines.
  • Provident Fund, Gratuity, and social-security contributions are computed using the country's rules: provident fund as a share of Basic, gratuity by the country's end-of-service rule, and social security on the pay earned that month.
  • Contributions charged on pay, such as US FICA, UK National Insurance, or Canada's CPP and EI, are worked out on the pay earned that month. Days docked for absence, unpaid leave, or late arrivals and early leaves are left out, as they are for income tax. An adjustment with Tax applicable on counts as pay for them too, and so does a bonus in US, UK and Canadian workspaces.
  • Contributions your country charges on Basic, such as India's EPF, the Philippines' PhilHealth and Pag-IBIG, and the basic part of Saudi GOSI, are worked out on the Basic earned that month, with the same days left out. GOSI adds the housing allowance in full. A provident fund you set up on a salary structure is not affected by late arrivals or early leaves: it stays a share of Basic after absence and unpaid leave only.
  • A bonus or taxable adjustment is taxed in the month it is paid, as if that month's pay ran all year. For US federal withholding this is the IRS aggregate method. It can withhold more on a bonus than the year's tax return ends up charging on it; the difference is settled after the tax year. Contributions with an annual wage cap, such as US Social Security, are capped a twelfth at a time, so a very large bonus month can take less of them than is due.

If your country levies no income tax through payroll (for example the UAE or Saudi Arabia — or Singapore, where employers never withhold and IRAS assesses each employee directly), the tax screens are not just inert — they are removed. The whole Tax section vanishes from the admin sidebar (Tax Slabs, Tax Certificates, Adjustments, Templates), Tax Reports disappears from Reports, and employees do not see Tax Certificates in their portal. An old bookmark opens a Not applicable in <your country> page instead of an error, and the underlying API answers 404.

note

Nothing is wrong and there is nothing to configure — this is driven by the country on your company profile, not by permissions or your plan, and no admin can turn it on.

Tax slabs and the new fiscal year​

Your fiscal year now advances automatically each year — the platform opens the next year the day after the current one ends (see Company Setup → Fiscal Years). But in a progressive-tax country the slab table follows each year's Finance Act, so the new year does not automatically come with brackets.

warning

Seeded brackets cover the years your country pack ships with. Before processing the first run of a new fiscal year, open Tax → Tax Slabs (/admin/tax/slabs), pick the new year and confirm brackets exist. A fiscal year with no slabs computes zero income tax for everyone — the platform logs an error when this happens, but the run itself will not invent a number. If slabs are missing, contact support or enter the year's brackets on that page.

Fixing a run before approval​

While a run is still in draft, processing or review, you can open it (/admin/payroll/runs/{id}) and Reprocess one or more selected employees without disturbing the rest. Once approved, locked or disbursed, entries are protected from reprocessing.

When a bonus or adjustment for the month is added, edited or cancelled after the run was processed, the run page says This run is out of date. and counts what changed, for example "1 new adjustment". Reprocess to include it. The banner counts only the people a reprocess would pay: active employees who joined by the end of the month and have a salary for it. An item for anyone else does not raise it. A leaver's final settlement, for one, is paid outside payroll (see Paying the settlement).

6. Review, approve, lock and disburse​

Open a run from the history list (/admin/payroll/history) or straight after processing. A run moves through these statuses:

StatusMeaning
ReviewFreshly processed; still editable
ApprovedSigned off; ready to lock or pay
LockedFrozen — no further changes
DisbursedPayments recorded as made

Buttons appear according to the current status:

  • Approve a run in review. You can Send back to review an approved run to edit it again. Approval is subject to the pre-flight checks below — if a blocking issue exists you will see an error explaining each problem, and the run stays in review.
  • Lock an approved run to freeze it.
  • Mark as Paid opens the disburse dialog — enter the payment date, payment method (bank transfer, cheque, cash or wallet), an optional bank account and reference, and whether to email employees. This marks paid every entry that is not paid yet and not on hold, and moves the run to Disbursed. The button shows only while such an entry exists, including on a Disbursed run once a held salary has been released.
  • Finalize Run is used when each entry was already marked paid individually (e.g. imported history): it moves the run to Disbursed without overwriting per-entry payment details. It shows once every entry is paid or on hold.
  • You can also mark or un-mark individual entries as paid from the run detail.
  • Paying by cheque? Print the cheques from Cheques → Print Cheques and mark each one issued when you hand it over — that marks the entry paid. While an entry has a cheque in play, its payment is changed only through the cheque. See Cheques.

Print produces a clean payroll register, and Export downloads every column for all employees as a CSV.

Pre-flight checks — why an approval can be refused​

The most damaging payroll mistakes look completely normal on a payslip. An employee with no shift is never marked present, so payroll reads the whole month as absence and deducts nearly the entire salary — and the slip still looks ordinary. Before a run can be approved, the system checks the month and refuses approval while any blocking problem remains. Warnings are surfaced but never stop payday.

The Checks before approval panel shows these findings on the Process page for the selected month and, collapsed, on a run still in review. When you click Approve with problems present, approval fails and the panel opens listing each problem. Every finding explains what is wrong, why it matters in money terms, and what to fix — the person running payroll is often not the person who configured the workspace.

Findings about specific people name them in the error itself — "2 employee(s) have no attendance at all this month: Ada Lovelace, Grace Hopper" — so you can go straight to the right profiles. Only current employees are considered: anyone who has left (separated, terminated, resigned or retired) is ignored by every check, because the run will not pay them.

Blockers — approval is refused until these are fixed:

What stops approvalHow to fix
This workspace has no default shiftCreate a shift under Attendance → Shifts (/admin/attendance/shifts) and mark it as the default. Without one, new employees get no working pattern.
Employee(s) have no shift assignedNo shift means no attendance is ever recorded, so payroll treats every day as absence and deducts almost the whole salary. Assign a shift on each employee's profile.
Employee(s) have no attendance at all this monthNot a single day is recorded, so the month is treated as unworked. Mark the days on Mark Attendance (/admin/attendance/mark), or switch their shift to auto-present if they are not expected to clock in.
No fiscal year is marked currentSet it under Company → Fiscal Years (/admin/company/fiscal-years).
No income tax slabs configured for the current fiscal yearOnly raised where your country levies income tax. Without slabs, income tax computes as zero for everyone — silent under-withholding. Add them at Tax → Tax Slabs (/admin/tax/slabs).
Income-tax brackets for your country are yours to enterRaised instead of the row above for Germany and France, whose income tax no bracket table can express (German tax classes; the French per-employee withholding rate). Enter your own approximation at Tax → Tax Slabs — or, if you run tax entirely outside the product, a single 0% row for the year, and post each employee's tax as a payroll adjustment deduction.
A statutory deduction has no salary component to post throughYour country pack computes a contribution (UK National Insurance, US FICA, Canada CPP/EI, Saudi GOSI, India EPF, Australian Medicare levy, German RV/KV/PV/AV, French vieillesse/AGIRC-ARRCO/CSG, NZ ACC levy, Singapore CPF, Philippine SSS/PhilHealth/Pag-IBIG) but no active deduction component with its code exists, so nothing would be deducted and take-home would come out too high with no line explaining why. Create the component under Payroll → Salary Components and link it to the structures it applies to.
The employer's share of a matched contribution has no component to record itUS FICA is matched by the employer: the same 6.2% Social Security and 1.45% Medicare on the same wages. Payroll adds it as an employer contribution through the FICA_ER component, which US workspaces get automatically. If it has been deleted or deactivated, pay still comes out right, but the employer's share is missing from the payslip, the employer cost and the payroll reports. Create an active employer-contribution component with code FICA_ER under Payroll → Salary Components; it does not need to be on any salary structure.
Employee(s) have no nationality recorded, and a contribution is levied on nationals onlySaudi GOSI comes out of Saudi nationals' pay and Singapore CPF out of Singapore citizens' pay; a foreign employee contributes nothing. With nationality blank, neither deducting nor skipping can be justified, so payroll deducts nothing for those employees and refuses approval. Set Nationality on each employee's profile, then reprocess.

Warnings — shown with the findings but never block approval:

  • Employees still pending activation will not be paid by this run — activate them first if they should be paid (see the Employees guide).
  • More than one shift is flagged as the default.
  • Employees with no active salary structure are skipped by the run entirely — not paid zero, but absent from the totals, which is easy to miss when reviewing.
  • One or more employees lose over 60% of gross to deductions. The message notes when the bulk is an absence deduction, which usually means missing attendance rather than genuine absence.
  • Employees whose pay is paused for the month have an approved bonus or adjustment for it. It is not paid while their pay is paused: move it to a month they are paid, or cancel it.
  • Employees will repay more than one loan instalment this month, because an earlier instalment was not deducted (for example in a month whose pay was paused). Check the amounts on the Loans page.
  • Hourly employees are on a salary structure with no Overtime line. Their hours beyond the standard day and on rest days are paid at the plain hourly rate, with no overtime premium. Add the Overtime component to the structure if the country's rates were meant; nothing to do if the plain rate is intended. A workspace that banks its overtime as time off is told only of the people with overtime this month that was approved to be paid (Overtime pay).
  • In a UAE workspace with a WPS salary file (SIF) format on any account: "No MOHRE establishment ID for the WPS salary file"; "N employee(s) have no MOHRE person ID"; and "N employee(s) cannot be paid through the WPS salary file" (no bank account, a bank without a routing code, or no IBAN or salary card number). The last two name the people. The file would leave them out, so fix them before payday.

With pay schedules on, a month can have several runs (its default run and each group's periods ending in it). The deduction and loan checks read all of them.

Anyone whose pay is paused for the month is listed as a note, not a warning: the run leaves them out on purpose.

A large deduction can be genuine — a mid-month joiner, unpaid leave, a loan recovery — so warnings never block; blocking them would train people to route around the check.

Who is checked. Employees pending activation are excluded from the per-employee checks — payroll never pays them, and they get their own warning instead. The attendance check only covers people this run will actually pay: joined by the end of the month, holding an active salary structure, not paused for the month, and not on a Punch Not Required (attendance-exempt) shift — exempt staff never produce attendance rows by design, so they are not flagged. Per-person findings name up to 8 employees, then collapse to a count.

The same checks are available any time via the API (GET payroll/preflight?month&year) so problems can be caught while the month is being set up.

Holding a salary​

When a salary is earned but must not be paid yet (pending clearance, a dispute, an employee who has stopped coming), hold it rather than removing it. On the run page, the hand icon on an unpaid row asks for a reason and puts that salary On hold. The run must be in review or later.

A held salary keeps its figures: its slip, the run's totals, and the bonuses and loan instalment it settles at lock all stay as they are. Only the payment waits:

  • the bank file leaves it out and lists it as skipped, with the reason;
  • Mark as Paid on the run pays everyone else and leaves it unpaid, with no receipt request, and the result says how many salaries are on hold. A run whose every unpaid salary is held cannot be marked paid;
  • marking the entry paid on its own, and cheques, are refused;
  • Finalize Run is not blocked by it: a run whose only unpaid salaries are on hold can be finalized, and the confirmation says how many stay unpaid;
  • the employee's portal shows "Salary on hold" and asks them to contact HR. Your reason is not shown to them.

To pay it, click the unlock icon on the row to release the hold (you are asked to confirm). If the run has not been paid yet, Mark as Paid on the run then pays it with everyone else. If the run is already Disbursed, Mark as Paid shows on it again and pays only the salaries still unpaid (or mark the entry paid from its row); for the transfer, download the bank file with Only entries not paid yet ticked, which holds just the unpaid salaries and no fund rows. Everyone already paid keeps their payment, receipt and date, and the run's disbursement date and fund remittance stay as they were.

A held salary is kept through processing the month again. If the person would drop out of the run (their salary ended, say), processing is refused until you release the hold, so a hold is never lost silently.

7. The bank payment file​

When a run is locked or disbursed, use Download Bank File on the run detail page to generate the salary file for bulk upload, in the payment-file format designed for the paying account (Company › Bank Accounts › Payment file). You choose the company bank account to pay from and the value date. If that account's format uses a branch city code, the dialog asks for it and remembers it for that account. A preview lists who will be paid and who is skipped (and why) before you download. A salary on hold is skipped. On a Disbursed run, tick Only entries not paid yet for a file of just the salaries still unpaid, such as one released from hold; it has no fund rows, because the funds were paid with the run. See also /docs/payroll/bank-payment-file.

If you have set up a contribution fund that is paid into your own fund account, the file also carries one extra row per fund: the run's total for that fund (for a provident fund, the employee and employer shares together) paid into the fund's own bank account. The preview shows these under Fund transfers in this file, with the amount per component. Choose a salary account to pay from — a fund account is never offered as the paying account.

With pay schedules on, the file of a pay group's period holds that period's salaries, but it is still named by the run's month: the account's file-name pattern has the year and the month only. Two periods of one month therefore download under the same name; rename one before uploading if your bank refuses a repeated file name.

The WPS salary file (SIF)​

In the United Arab Emirates, the Wage Protection System requires salaries to be paid through a Salary Information File (SIF) that the employer uploads to its bank or exchange house. Operentra makes that file from a locked or disbursed run. It does not connect to WPS or to any bank: you download the file and upload it yourself.

The format and the two ID fields below are offered only in workspaces whose company country is the United Arab Emirates. A field that already holds a value is shown in any workspace.

Set it up once:

  1. Company Setup → Company Profile → MOHRE establishment ID: the 13-digit number on your establishment card. Spaces and dashes are removed when you save.

    Company Profile, Basic information section, with the MOHRE establishment ID field and its hint

  2. Each employee: Edit → MOHRE person ID (Personal Information): the 14-digit person ID on the labour card. Spaces and dashes are removed; clearing the field removes it. It is shown on the employee's profile. Where a Labour Card document already had a well-formed person ID typed into it, it was copied into this field for you.

  3. Each employee's bank account: the bank or exchange house picked from the list (the list carries each one's 9-digit routing code), and the IBAN, or, for an exchange house salary card, the card or account number (23 characters at most).

  4. Company Setup → Bank Accounts → Design on the paying account. Under Formats your country requires, select Start from this format on "WPS salary file (SIF)", then Save format. The paying account's bank must be one picked from the list, because its routing code goes into the file.

    The Formats your country requires card in the payment-file designer, offering the WPS salary file (SIF) with Start from this format

The designer then shows Follows: WPS salary file (SIF). The templates stay visible and editable, and the format's rules apply when the file is made. Use my own design instead turns the rules off. Change the file name pattern only if your bank names its files differently. A company can keep its ordinary transfer file on one account and the SIF on another.

The payment-file designer on a payroll account following the WPS salary file (SIF): the green Follows banner, the EDR row and SCR trailer templates, and the live preview

What the file holds. One EDR line per employee, then one SCR line last:

LineFields, in order
EDREDR, person ID, the routing code of the employee's bank or exchange house, the IBAN or salary card number, pay start (YYYY-MM-DD), pay end, days in the period, fixed income, variable income, days of unpaid leave
SCRSCR, establishment ID, the paying bank's routing code, file date (YYYY-MM-DD), file time (HHMM), salary month (MMYYYY), number of EDR lines, total, AED, the company name in plain letters and digits, at most 35 (the establishment ID when the name has none, such as a name written in Arabic)

For example, an EDR line for September 2026 reads EDR,00915012345663,802420101,AE160240043520123456701,2026-09-01,2026-09-30,30,5000.00,330.00,0.

  • Pay period: the run's calendar month; from the joining day for someone who joined in the month; to the last working day for someone whose separation has one in the month. Days are counted with both ends included.
  • Fixed and variable income: variable is the run's overtime, bonuses and one-off additions; fixed is the rest of the net. They always add up to the net the person is paid, and neither is negative: if deductions take the net below the variable pay, all of it is reported as variable and fixed is 0. The SCR total is the run's net for the people in the file.
  • Days of unpaid leave: the run's unpaid leave days in whole days; a half day counts as one.
  • Every line is routed by the routing code of the person's own bank or exchange house.
  • Amounts have two decimals, lines end in Windows line endings, and nothing follows the SCR line.
  • The file is named by your establishment ID and the moment it was made, in the company's time zone (YYMMDDHHMMSS), with the extension .SIF, for example 1000004829307261005093015.SIF. The SCR carries the same date and time. It downloads as plain text.
  • The EVP line is optional. Some agents ask for it; tick Itemise variable income on an EVP line on the format to add one after each EDR: EVP, person ID, routing code, then housing, transport, medical, annual air ticket, overtime, all other allowances and additions, and leave encashment. With it on, variable income is everything but basic pay, and the seven amounts add up to it exactly. Each salary component is placed by its name or code (housing, transport, medical, ticket, overtime, leave encashment); anything else counts as other. When deductions take the net below the allowances, other pay is reduced first, then the rest in reverse order.

Making the file. On a locked or disbursed run, select Download Bank File and choose the account that has the SIF. In place of the value date, the dialog shows a note: a SIF carries no payment date, and you upload it to your bank or exchange house's WPS service. It shows how many people will be paid and the total, everyone left out with the reason, and any warnings. Download SIF (n) saves the file. Only entries not paid yet works as for any bank file.

The Download bank payment file dialog on a SIF account: the SIF note, 43 employees to be paid, 2 skipped with No MOHRE person ID on their employee record, a provident fund warning, and Download SIF (43)

No file is made, and an error says why, when:

  • the company has no valid MOHRE establishment ID;
  • the paying account's bank has no routing code;
  • the workspace does not pay in AED.

A person is left out, with the reason, when:

  • they have no valid person ID ("No MOHRE person ID on their employee record");
  • they have no bank account;
  • their account has no IBAN or salary card number ("No IBAN or salary card number on their bank account");
  • no bank was picked on their account;
  • their bank has no routing code ("Their bank (name) has no routing code");
  • they were not employed on any day of the month;
  • or for the reasons every bank file has: paid by cheque, salary on hold, paid by another method, or a net that is not above zero.

A final salary paid late. Every line in a SIF must be for the file's salary month. When a run pays someone whose last working day was in an earlier month (their final pay came a month late), their line is for that earlier month: from its first day, or their joining day, to their last working day. They are left out of this month's file with the reason "Paid in this run for 11/2026: in that month's own file", and the dialog offers a button per such month, 11/2026 file (1), that downloads a SIF for that month holding only them.

Refund requests (FDR/FCR). When the agent has paid a line that should not have been paid (the person left, the account was wrong, the amount was miscalculated), it returns the money on a salary refund request. In the Download Bank File dialog of a SIF account, select Request a refund for a SIF…:

  1. Choose the original SIF. Every SIF downloaded from the run is kept with its lines, so the request quotes them exactly as they were sent.
  2. Enter the name of the acknowledgement (ACK) file the agent returned for it.
  3. Choose the company account the refund is credited to. Its bank must have a routing code.
  4. Tick each person to refund, choose the reason (the agents' sixteen codes, such as 010 Employee terminated), and enter an amount, or leave it empty for the whole line. An amount above what the line paid is refused.

Download refund file saves one FDR line per person and the FCR control line last:

LineFields, in order
FDRFDR, original SIF file name, ACK file name, the person's routing code, person ID, refund amount, reason code, the account as it was in the SIF, a blank, EWPMS
FCRFCR, establishment ID, company name (as in the SCR), the credit account's bank routing code, the credit account zero-padded to 23, total refund, number of FDR lines, two blanks, EWPMS

The file is named REFUND-<establishment ID>-<YYMMDDHHMMSS>.txt; rename it if your agent asks for another name. Like the SIF, it is uploaded by you, never sent.

A contribution fund paid through a payment file is not in a SIF, which carries employees only. The dialog warns "(fund) is paid through a payment file, but a WPS salary file carries employees only. Pay it separately."

The pre-flight checks warn about a missing establishment ID, missing person IDs and people the file cannot pay before you approve the run; see Pre-flight checks. Designing the format needs the company settings permission (company.settings); making the file needs payroll.manage.

The journal CSV​

A locked or disbursed run also offers Journal CSV: the same balanced journal a connected ledger (QuickBooks Online, Xero) would receive, as a file, for a workspace with no ledger connected or an accountant who wants to post it by hand. One row per line — wages, employer contributions, reimbursements, tax, contributions, loans, deductions, net pay and rounding — with the debit or credit, the currency and a memo, and a total row that balances. Expense reimbursements paid through the run are in the reimbursements line; company-card items are not, since nothing is paid for them through payroll. The column headings, the total row and the memo are in the language you work in, and a pay group's journal is named and noted by its period's dates.

8. Salary slips​

Screen: /admin/payroll/slips

Generated salary slips for a run

Each processed entry produces a salary slip. From this page you can:

  • View a slip, download its PDF, or email it to one employee. The email follows the acknowledgment flow: the slip must be marked paid first; the employee then gets the acknowledgment request, or the signed slip PDF once they have acknowledged.
  • Select several and Download ZIP or Email All at once. Email All sends each employee the Payroll Processed email with their slip PDF attached. The email shows the pay period, working days, present days, gross salary, total deductions, any tax deducted and the net salary. When it finishes, it shows how many emails were sent, skipped and failed, with the reason for each one not sent, such as no email on file, the email switched off in Settings › Email Templates, the monthly email limit reached, or the mail server refusing it. A slip counts as emailed only when its email went out.

Besides the salary components, a slip lists the bonus, adjustments, loan repayment and late, absence and unpaid-leave deductions as their own lines when they apply. These lines print in the slip's language; a salary component prints the name you gave it.

The attendance strip at the top of the slip shows working days, present, absent, leaves and late arrivals. It also shows Half Days, Unpaid Leave and Early Leave when the month has any, so every attendance deduction on the slip has its count beside it: half days are part of the absence deduction, unpaid leave has its own line, and early leaves count with late arrivals towards the late deduction.

Slip layout is controlled by your slip template (/admin/payroll/slip-templates).

Acknowledgment flow​

When you disburse a run with emails enabled, each employee gets an acknowledgment-request email (no PDF) linking to their portal at /portal/salary. After the employee confirms receipt there, the system emails the signed slip PDF with an e-signature stamp and records the acknowledgment (with timestamp and IP) for your records.

A slip that is still unacknowledged gets up to two reminder emails: the first at least two days after the request, the second at least three days after that. Reminders go out shortly after 09:00 in your workspace's time zone.

Provident Fund ledger​

Screen: /admin/payroll/pf-ledger

If your components contribute to Provident Fund, this page shows each employee's running PF balance. Click an employee to open their full ledger of contributions and movements at /admin/payroll/pf-ledger/{employeeId}.

This ledger tracks what each member is owed. The money itself — the fund's bank account — is tracked under Contribution funds.

The profit the fund earns belongs to its members. For a provident fund kept in its own account, share it out from the fund page with Share profit with members (see Sharing profit with members), which posts each member's Fund profit here. Credit fund profit on an employee's ledger is for a one-off correction.

Contribution funds​

Screen: /admin/payroll/funds

Use a contribution fund for money collected through payroll that the company does not simply keep in its salary account: most often an employees' provident fund, but equally a pension fund, a gratuity fund, or a statutory scheme.

Setting up a fund starts with one question: how is this fund paid each month?

AnswerWhat happens
Into our own fund accountThe employee and employer shares go into the fund's own bank account, for example a PF trust account. Every payroll's bank file gets one row moving the fund's total from the salary account into that account, and disbursing the run records it on the fund.
To a government bodyPaid to an authority by challan or online portal (for example GOSI, CPF, EPF or EOBI). Nothing is added to the bank file; you record each payment with its reference.
To an outside providerPaid to a pension provider or insurer that runs the scheme. Nothing is added to the bank file; you record each payment with its reference.
Kept on our booksNo money is paid out each month. The company owes each employee's balance and pays it with their final settlement. The fund has no remittances, ledger or bank balance; for a provident fund it shows the total owed to members.

The rest of the setup:

SettingWhat it does
Salary components collectedThe components whose run total goes into the fund. For a provident fund this is usually PF_EE (employee share) and PF_ER (employer share). A component must be in at least one salary structure, otherwise payroll never produces it and the fund is refused.
Fund bank accountRequired when the fund is paid into your own fund account; optional (for reference) for a government body or provider. Add it under Company Setup → Bank Accounts with purpose Fund account.
Starts fromRuns for months before this are never remitted to the fund (for example, history imported from CSV).
Opening balanceOptional, and not offered for a fund kept on your books. What the fund already holds, so the balance starts from the right figure.
Tax withheld on bank profit (%)Optional. The rate the bank deducts from the profit it credits (for example 20). It pre-fills the tax when you record bank profit.

Who is in the fund is decided by salary structures, as with any component: only employees whose structure includes the fund's components contribute.

A provident fund outside Pakistan

PF_EE and PF_ER are seeded only in Pakistani workspaces. To run a provident fund anywhere else, first create both under Salary Components: PF_EE as a deduction and PF_ER as an employer contribution, each a percentage of basic. Then add them to the salary structure. Use exactly these codes: payroll fills each member's PF ledger only from components coded PF_EE and PF_ER.

Set "Starts from" to the first month you want in the fund

The form suggests the first day of the current month. If a run for an earlier month is still to be paid — say you set the fund up in October for a September run that is locked but not yet disbursed — set Starts from to that earlier month, or the run will not include the fund's transfer.

How the balance is kept​

Every fund except one kept on your books has its own ledger. The book balance is every credit minus every debit:

EntryWritten byEffect
Payroll remittanceAutomatically when a run is disbursed by bank transfer and the fund's row was in the bank file (own fund account), or Record remittance (government body, provider, or any run paid another way)Adds the run's total for the fund's components — for a bank-file row, the whole-unit amount the file moved
Leaver payoutAutomatically on final settlement, when the PF is withdrawn or transferredTakes the leaver's PF balance out of the fund
Opening balance, Bank profit, Loan repaymentAdd entryAdds
Tax withheld on profitAdd entry — with Bank profit, or on its own against a profit entryTakes away
Bank charge, Loan to memberAdd entryTakes away
AdjustmentAdd entry — you choose the directionEither

Disbursing the same run again never books it twice.

HRM cannot read your bank, so the book balance is only as complete as these records. Use Record statement balance to enter the closing balance from the fund account's statement: it does not change the book balance, but any difference on that date is shown on the fund and on the funds list, so you can find it.

For a provident fund, the fund page also compares the fund's book balance with the total that the Provident Fund ledger says is owed to members. A difference usually means a month has not been remitted yet, the fund's profit has not yet been shared out to members, or the fund held money before member balances were set up.

Bank profit and its tax. When you add Bank profit, enter the profit before tax; the Tax withheld field fills in at the fund's rate (change it to match the statement — banks round). Saving records two lines, so the book follows the statement line by line: the profit, and the tax as Tax withheld on profit.

Whose money is it. Opening balances, adjustments and member loans can name the member the money belongs to — for example a balance transferred in for one employee, or a top-up of one employee's shortfall. Leave it blank for company money (a correction, a repaid bank fee). Payroll remittances already know their employees.

Sharing profit with members​

The fund's profit after tax belongs to its members. When bank profit is recorded, the fund page shows how much is not yet shared and a Share profit with members button. It opens a preview before anything is posted:

  • Each bank profit credit counts as earned over the month before it was credited.
  • Its amount after tax is split by each member's daily balance in the fund that month: payroll deposits from the date they arrived, plus entries marked for a member. Company money does not earn a share.
  • Each member's share is rounded to 2 decimals; any remainder goes to the largest share, so the shares always add up to the profit.

Confirming posts one Fund profit entry on each member's PF ledger and marks the profit (and its tax) as shared — shared lines can't be deleted. If something was wrong, Undo on the share removes the members' entries and the profit can be shared again.

Runs not yet remitted​

The fund page lists runs that owe the fund something but are not yet on its ledger.

  • Own fund account: a run is booked automatically when you disburse it by bank transfer. It only appears here if it was disbursed but not booked — because it was paid another way (cash, cheque, or entries marked paid one by one), or because the fund's row was skipped in the bank file (for example, its account had no IBAN). Once the money has gone, use Record remittance with the transfer reference.
  • Government body or provider: every locked or disbursed run appears here until you record its payment with the challan or transfer reference.

Importing historical salary​

Screen: /admin/payroll/salary-history-import

To backfill past pay records for an employee (for example when migrating onto Operentra), download the CSV template, pick the employee, upload the filled file, preview the parsed rows and warnings, then import to commit them. Each import is tracked as a batch you can revert in one click if something looks wrong. A setting controls whether the Provident Fund column is treated as a real ongoing balance or a legacy cash refund.

Payroll settings​

Screen: /admin/payroll/settings

Workspace-wide options that affect every run:

  • Rounding method — round, floor or ceil.
  • Rounding precision — number of decimal places. An expense claim reimbursed through payroll is not rounded: it is added to total earnings and net pay to the cent.
  • Pay day — the day of the month salaries are due.
  • Allow skip attendance deductions — whether the "pay in full" option shows on the Process Payroll screen.
  • Pay schedules — lets you create pay groups and run their periods beside the monthly run; the pay groups table sits under it (see Pay schedules).