Payroll Module
Running Payroll
How to set up employees, run a pay cycle, post it to your books, and actually pay people — including from more than one bank account, and how to enter a payment you already made.
Start here
1Before you start
Payroll doesn’t keep its own employee list. Every pay run is built by pulling your current roster straight from HR — so before you can run payroll, HR needs to be enabled and have at least one employee in it.
If HR isn’t enabled, “Create Payroll Run” will still work, but it brings in zero employees — there’s nothing else for it to pull from. Enable HR first (Settings → Modules, or ask whoever manages that).
Once HR is on, the rest of this guide follows the order you’d actually do it in: add people, tell the system what they’re paid, then run a pay cycle.
Set up people
2Add an employee
In HR → Employees, click Add Employee. The form is one page — no separate wizard steps. Most fields are optional; fill in what you have and come back later for the rest.
| Field | What it’s for |
|---|---|
| Employee Code | Your own reference ID, e.g. EMP-0002. Optional. |
| Linked User | Ties this record to a user login, if the employee has app access. |
| First / Last / Display Name | Display Name is what shows up everywhere else in the app. |
| Email, Phone | Contact details. |
| Department, Job Title | Used for filtering and the org chart. |
| Employment Type | Full Time, Part Time, Contract, or Intern — informational. |
| Status | Active, On Leave, Inactive, or Terminated — this one drives payroll inclusion. |
| Role Profile / Module Access | Controls what this person can see if they log in — not related to pay. |
| Reports To | Feeds the org chart. Leave as “No manager” for top-level people. |
| Start Date, Notes | Reference only. |
Click Save Employee. Nothing here is validated as required by the form itself, but a person needs at least a name to be worth adding.
Adding people one at a time slow going? Use Import in the Employee Directory toolbar — it opens the same bulk-import wizard used across the app (upload a file, map columns, review, commit). Duplicate on any employee card is the quick option for cloning someone with a similar setup (department, role, pay) minus their personal details.
3Set what they’re paid
There’s no separate “salary” screen — compensation is four fields built into the same employee form, right below Status.
| Field | Notes |
|---|---|
| Compensation Amount | The figure for one pay period at the frequency you choose next. |
| Frequency | Hourly, Weekly, Biweekly, Semimonthly, Monthly, or Annual. |
| Effective Date | When this amount starts applying. Defaults to today. |
| Compensation Note | Optional — e.g. “Annual review raise.” |
Save, and this becomes the employee’s on-file pay rate — Payroll reads it automatically as the Base Salary line the next time you create a run.
Giving someone a raise
Open the employee, change Compensation Amount to the new figure, set Effective Date to when it starts, and save. This doesn’t overwrite the old rate — it appends a new entry to their Compensation History, which appears as a read-only table right below the fields once there’s more than one entry.
Because payroll always resolves pay as of the run’s own scheduled date, re-running a past pay period still uses whatever rate was actually in effect back then — not today’s rate.
Compensation here only sets Base Salary. There’s still no automatic overtime-from-hours calculation — for that, add an Overtime earning line by hand on the payslip (see Enter pay figures). Tax, on the other hand, is automatic once you set it up — see the next section.
4Set up tax
Payroll → Tax Setup is where you define the taxes and contributions payroll works out for you — income tax (PAYE), pension/social security (SSNIT), or anything else your country requires. Once set up, every run works them out automatically.
In Ghana: SSNIT and PAYE are ready-made
- SSNIT — go to Settings → SSNIT, tick Apply SSNIT deductions to Payroll and Save. The current rates fill in: 5.5% from the employee, 13% from you. Payslips show the employee’s share as one SSNIT (5.5%) line, and yours as Employer SSNIT (13%), which never comes out of their pay.
- PAYE — switching SSNIT on also adds PAYE with the GRA monthly bands for residents, if you don’t already have an income tax set up. You can also click Use GRA PAYE bands (or Reset to GRA bands) at the top of Tax Setup at any time.
| Monthly chargeable income (GHS) | Rate |
|---|---|
| First 490 | 0% |
| Next 110 (up to 600) | 5% |
| Next 130 (up to 730) | 10% |
| Next 3,166.67 (up to 3,896.67) | 17.5% |
| Next 16,000 (up to 19,896.67) | 25% |
| Next 30,520 (up to 50,416.67) | 30% |
| Above 50,416.67 | 35% |
These are the GRA bands in force since January 2024. If GRA changes them, edit the bands in Tax Setup and click Save — every new run (and every Simulate) uses the new figures.
In Ghana, PAYE is charged on pay after the employee’s 5.5% SSNIT. Example: on GHS 2,000, SSNIT is GHS 110, so PAYE is worked out on GHS 1,890 = GHS 221.50, and take-home pay is GHS 1,668.50. The payslip shows “on taxable pay of GHS 1,890.00” under PAYE so you can see it.
Adding your own tax or contribution
Click + Add Tax Component for each one:
| Field | Notes |
|---|---|
| Label | Whatever you call it — e.g. “PAYE”. |
| Income tax / Pension or social security | Pension and social-security contributions are worked out first, on gross pay. Income taxes are worked out after them. |
| Deduct employee pension/SSNIT before tax | Income taxes only. When ticked, the tax is worked out on gross pay minus the employee’s own pension/social-security contributions. On by default for Ghana companies, off elsewhere. |
| Employee-funded / Employer-funded | Employee-funded reduces net pay. Employer-funded is a separate company cost — it never touches the employee’s pay, but still posts as a real expense when you post the run. |
| Flat % / Progressive (bands) | Flat % applies one rate to the whole amount. Progressive taxes each slice of pay at its own band’s rate — add bands with an upper limit and a rate each; leave the last band’s limit blank for “and above.” You can type amounts with commas, e.g. 3,896.67. |
| Active | Untick to keep a component defined but stop applying it, without deleting your setup. |
Click Save Tax Setup. Every run you create, and every time you click Simulate on a run, works out tax fresh from each person’s current pay and your current Tax Setup.
On an individual payslip, Statutory deductions & tax shows the itemized lines and a Recalculate Tax button. Withheld from pay (SSNIT + tax) stays an editable number underneath for a one-off correction. The totals at the bottom separate Statutory deductions (SSNIT) from Income tax (PAYE).
5Status & who gets paid
An employee’s Status field decides whether a new pay run includes them by default:
| HR Status | New run includes them as |
|---|---|
| Active | Included |
| On Leave | On Hold |
| Inactive / Terminated | Not added to the run |
This is just the starting point — you can override any individual employee’s inclusion directly on their payslip once a run exists. Note this status is set by hand on the employee record; it isn’t touched automatically by the Attendance & Leave module, even if someone has an approved leave request in there.
Run payroll
6Create a pay run
In Payroll → Runs, click + New Payroll Run.
- Period — the month this run covers.
- Run Name — optional; defaults to “Payroll Run — [period]”.
- Scheduled Date — the pay date. This is also the date used to resolve each employee’s compensation, so set it to the real pay date, not just “today.”
Click Create Run. Every active/on-leave employee in HR is pulled in immediately, with Base Salary pre-filled from their compensation on file, and any recurring deductions copied forward from their last payslip.
- People with no salary in HR — usually you, the owner, who is added to HR automatically — are simply left out, with a short note saying so.
- Someone whose salary starts later than this period (their Effective Date is after the 1st) is added On Hold with no pay, and you’re told to check their Effective Date in HR.
Then open the run and click Simulate to work out everyone’s pay. The run’s Summary shows gross pay, Statutory deductions (SSNIT), Income tax (PAYE), net pay, and the employer contributions you pay on top.
7Enter pay figures
Open the run and go to its Employees tab, or the Payslips tab for every run at once. Click into a person’s payslip to edit:
- Earnings — Base Salary plus any others (Overtime, Allowances) as plain label + amount lines.
- Deductions — Health Insurance, Pension, or anything custom, same label + amount shape.
- Statutory deductions & tax — worked out automatically from Tax Setup, or click Recalculate Tax to refresh it against this payslip’s current gross. Withheld from pay (SSNIT + tax) stays a plain number you can still override by hand.
- Inclusion Status — Included / On Hold / Excluded, overriding the run’s default for this one person.
Net pay recalculates as Gross − SSNIT − Income tax − Other deductions, floored at zero. The Components and Deductions tabs manage the reusable label list the Earnings/Deductions dropdowns pull from.
8Print or email a payslip
There’s no employee self-service portal — an employee never logs in and pulls their own payslip. If someone needs a copy, an admin hands it to them from right here, at the bottom of that same payslip you were just editing.
On any open payslip, two buttons sit next to Save Payslip:
- Print Payslip — opens a clean, branded one-page version (your company logo and accent color, itemized Earnings/Deductions/Tax, Net Pay) in a new tab and triggers your browser’s print dialog immediately. Save it as PDF from there if you want a file instead of paper.
- Email Payslip — sends that same branded payslip straight to the employee, using the email address on file for them in HR. If they don’t have one on file, this fails with a message telling you so — add their email in HR → Employees first, then try again.
Every successful email is recorded in System Logs (event payslip_emailed), so you have a record of who was sent what and when.
9Approve & post
Once figures look right, click Simulate — this locks in the run as ready for review (status → Calculated) without touching your books yet.
Then click Approve & Post. If your company uses double-entry accounting, this writes a real GL journal:
Example — a run with $4,000 gross, $150 health insurance, $200 PAYE
Every active deduction and tax component gets its own labeled liability line — a real “PAYE Payable” account, not one lump “tax” bucket — so each one can be tracked and settled separately in Payroll Liabilities. An employer-funded contribution (e.g. Employer SSNIT 13%) posts as an extra, balanced expense-and-liability pair on top of this — a real added company cost, separate from what’s withheld from the employee.
SSNIT shows as one line on the payslip but posts to the two places it is really paid: SSNIT Tier 1 Payable (your 13% plus the employee’s 0.5% — 13.5% remitted to SSNIT) and SSNIT Tier 2 Payable (the employee’s 5%, remitted to their Tier 2 trustee). For GHS 2,000 gross: Salaries & Wages Dr 2,000; Payroll Liabilities Cr 1,668.50; SSNIT Tier 1 Payable Cr 10 + 260; SSNIT Tier 2 Payable Cr 100; PAYE Payable Cr 221.50; Employer SSNIT expense Dr 260.
Nothing has left your bank account yet — this step only records that you owe your employees and whichever tax/insurance authority the deductions go to. Simple-mode companies skip the journal and the run just moves straight to Posted.
The run stays at Approved rather than reverting — fix whatever’s wrong (like a disabled Accounts module) and click Retry Post. It’s safe to retry; nothing gets posted twice.
10Disburse net pay
This is the step that actually moves money — a real bank transaction, not just a bookkeeping entry.
From the posted run, click Disburse — it opens the run’s Posting tab and scrolls straight to Disburse Remaining Balance. You’ll set:
- Pay Date — defaults to today. Change this if you’re recording a payment that already happened (see below).
- Bank account per employee — everyone defaults to whatever you pick in “Pay everyone from,” but each person can be assigned their own account.
Click Disburse. Everyone sharing the same account is grouped into one outflow transaction for that account — matching what a real batch transfer looks like on your bank statement — each with its own GL entry (debits Payroll Liabilities, credits Cash).
This pays out take-home pay — not the withheld tax and deductions sitting in Payroll Liabilities. Those get remitted separately, whenever you actually send them.
11Settle withheld amounts
Go to Payroll → Posting → Payroll Liabilities. Every account you’re holding money in from withholding — net pay not yet disbursed, each deduction, payroll tax — is listed with its current balance. Click Pay on any of them, pick the bank account and amount, and confirm. This is how the health insurance premium, pension contribution, or tax withholding actually leaves your account and gets marked settled.
Common tasks
Entering a payment you already made
Already paid someone outside the system and need your books to reflect it accurately? Run the same flow — the difference is just in the dates and figures you enter.
-
Create the run with the real pay date
Set Scheduled Date to the day you actually paid, not today.
-
Enter what actually went out
On each payslip, enter the real earnings, deductions, and tax so Net Pay matches the real amount. Exclude anyone you didn’t pay this round.
-
Approve & Post
Same as any run — this records the obligation.
-
Disburse with the real date
Set Pay Date on the Disburse form to when the money actually left your account. The bank transaction and its GL entry are both dated to this, not to today.
Paying from different accounts
If different people get paid from different accounts, assign each one individually on the Disburse form instead of relying on the “Pay everyone from” default. Everyone sharing an account is still batched into one transaction for that account — so three people paid from the same account produce one transaction, and a fourth paid from a different account produces a second, separate one, each with its own correctly balanced GL entry.
Common tasks
Salary paid out weekly
Some people have a monthly salary on paper that’s actually handed over in smaller weekly instalments — say, a $1,600/month salary paid as $400 each week. There are two ways to set this up, and which one you want depends on whether tax is involved.
Option A — four weekly runs
Set the employee’s Compensation Amount to $400 with Frequency set to Weekly (not $1,600/Monthly) — Payroll pulls whatever figure is on file verbatim as Base Salary into a run, so the on-file amount has to already be the per-run figure. Then create a separate run for each week.
-
Create one run per week
Give each its own Scheduled Date and a name that tells them apart — “Week 1,” “Week 2,” and so on. The Period field can be shared across all of them (e.g. all set to the same month); there’s nothing stopping multiple runs from sharing one period.
-
Confirm the $400 pulled in automatically
Each run’s Base Salary line comes in at $400 on its own, since that’s what’s on file. Add anything else that applies to that week and Approve & Post as normal.
-
Disburse each run separately
Each run produces its own net pay transaction, dated to that week — see Disburse net pay.
If this employee has any active tax component (see Set up tax), it gets calculated fresh on whatever that single run’s gross pay is — $400, not the real $1,600 monthly total. With a flat percentage rate this comes out the same either way, but with a progressive/bracketed rate, taxing four separate $400 runs can land in a different bracket than taxing one $1,600 run — usually under-withholding versus what the true monthly figure owes. If tax is active for this employee, Option B keeps the withholding accurate.
Option B — one monthly run, paid out in instalments
Keep the employee’s compensation as the real figure — $1,600, Monthly — and run payroll normally, once a month. Instead of disbursing the full net pay in one shot, settle it in $400 pieces as the money actually goes out.
-
Run the month as usual
Create, enter figures for, and Approve & Post one run for the full month. Tax and deductions are calculated correctly on the real $1,600 gross.
-
Skip the one-shot Disburse button
Go to Payroll → Posting → Payroll Liabilities instead — the same place you’d settle withheld tax or deductions (see Settle withheld amounts). The employee’s net pay balance sits there too, waiting to be paid down.
-
Pay it down $400 at a time
Click Pay, enter $400, the date, and the bank account, and confirm — once a week. Each payment posts its own dated bank transaction and GL entry, and the remaining balance drops by exactly what you paid. After four payments, the full $1,600 is settled.
Option B is the better default whenever tax or deductions apply — it computes them once, correctly, against the real monthly figure, and only the disbursement is spread out.
Reference
Run statuses
A run can only move forward. Draft and Calculated runs can be deleted; once Approved or later, a run is a permanent record — reverse individual mistakes rather than deleting.
What this module doesn’t do
Tax is automatic once Tax Setup is configured — but deductions (health insurance, pension) and overtime still don’t calculate themselves. Deductions are typed in once and copy forward automatically; overtime needs a new Earnings line added by hand each time it applies.
Clocking in/out and leave requests live entirely separately. An approved leave request doesn’t automatically deduct pay or mark someone On Hold — you do that by hand on the employee’s Status field.
The Pending / Paid / Failed field on a payslip is a record-keeping label. Only Disburse actually moves money — editing this field directly does nothing to your bank balance.