Periodic — the simple default
Each pay period is taxed on its own: that period's pay against that period's slice of the tax-free threshold. Predictable and easy — best for steady salaries. The trade-off: if pay jumps around (a big commission month, a bonus), tax can spike in the high month, and unused threshold from a low month isn't automatically clawed back — the employee settles any difference on their own annual return.
Cumulative — smoother and self-correcting
Each pay period looks at the whole year so far: total pay to date against the threshold to date, works out the tax due for the year up to now, and deducts what's still owed after what was already taken. This smooths out bonuses and uneven pay and ties out cleanly at year end — but only if the year-to-date picture is correct.
Which should you choose?
| Pick… | When… |
|---|---|
| Periodic | Steady salaries; you want the simplest method to explain to staff. |
| Cumulative | Bonuses, commissions or irregular pay; you want year-end to tie out without staff having to file to settle. |
The mid-year trap (read this before switching)
The fix: before the first cumulative run, enter each employee's opening year-to-date figures (statutory income and PAYE already deducted this year). A brand-new hire — first job this tax year — needs nothing. In Brawta this is a field on the employee record, and switching methods is a setting you can change per person or company-wide.
Either method, worked out correctly.
Brawta does both periodic and cumulative PAYE, handles Week 53, and prompts for opening balances when you onboard mid-year — so the figures are right from the first payslip. Free to try.