Setting Someone's Pay
The Payroll Management tab — one person's standing rates, the four monthly figures derived from them, and the rule that saving replaces the whole set.
Employee → Payroll Management is where you set what one person is paid. Everything on this tab is a standing rate: it describes what the person earns from now on, and it is what the next pay run you build starts from.
The four figures
Across the top, four monthly totals. Every one is computed on the backend from the items beneath — the page never adds anything up itself.
| Figure | What it totals |
|---|---|
| Total pay | The monthly value of every salary, benefit and allowance item. |
| Deductions | The monthly value of every deduction. |
| Taxes | The monthly value of every tax item. |
| Net pay | What this person nets in a month at these rates. |
Net pay here is what the person nets in a typical month at their current rates. An actual payslip can differ — a run may carry a one-off bonus, fewer days worked, or an item added for that run only. The payslip is the truth about a period; this tab is the truth about the rate.
The items
Beneath the figures, one row per standing pay item:
| Column | Notes |
|---|---|
| Type | Salary, Benefit (non-cash), Allowance, Deduction, or Tax. |
| Name | The line as it appears on the payslip. |
| Amount | The rate, in your business currency. |
| Period | What the rate is per — Monthly, Weekly, Every two weeks, Daily, Hourly, Quarterly, Annually, One-time. |
| Count | How many of that period the amount covers. |
| Taxable | Whether the item is taxable. |
| Monthly | Amount × count, computed on the backend. This is the figure a pay run will use. |
The read view carries no inputs. Edit pay items turns the list into the editor; Save commits it.
See Pay items for what each type means and how amount, period and count combine.
Editing
Every existing item is already loaded into the editor. Nothing is hidden from you.
Adding a row asks for type, name, amount, period, count and taxable. Changing the period sets a sensible default count you can overwrite.
The complete list is sent, and the four figures recompute from what came back.
The editor always sends the complete list of items. An item you removed here is removed from the employee, and will not appear on the next pay run. This is exactly why every existing item is preloaded when you open it — so a straight re-save changes nothing, and you can never silently drop an item you did not look at.
Closing the editor with edits in it asks you to confirm first. Discarding returns the list to what the backend last returned.
What changing a rate does — and does not do
| Pay run | Effect of editing this tab |
|---|---|
| A run you have not built yet | Uses the new rates. This is the point of the tab. |
| A draft run that already exists | Unchanged. A draft carries its own copy of the items — change it in the run itself. |
| An approved run | Unchanged, and unchangeable. It has been posted and its payslips exist. |
Nothing in the product reaches back into a pay run to re-sync it with an employee record. Once a run exists it holds its own figures, and only an explicit edit by you on the run itself changes them. That is what makes a past period reproducible.
The other two places pay items live
| Where | Scope | When to use it |
|---|---|---|
| This tab | One person, going forward | A raise, a new allowance, a loan repayment starting. |
| The hire page | One person, at creation | Setting up a new joiner. Same editor, same replace-the-whole-set rule. |
| Import on the pay schedules list | Many people at once | A rate change that affects a whole department. |
| The pay run editor | One run only | A one-off bonus, or a correction that must not change the standing rate. |