Best Practice: Payroll Setup — Aligning MSP Pulse with Your Payroll Package
Start with your payroll package, not MSP Pulse
Your payroll provider (Sage, QuickBooks Payroll, BrightPay, Thesaurus, Xero Payroll, or whichever you already run) already decides your frequency, pay date and cutoff. MSP Pulse doesn't calculate tax, PRSI or net pay; it produces the hours, overtime, mileage and expenses that feed into that software.
So the first step isn't a setting in MSP Pulse at all. It's going into your existing payroll package and writing down exactly what it's already configured to do:
- How often you pay (weekly, fortnightly, monthly)
- The actual pay day
- The submission deadline your provider expects timesheets and expenses by
- What happens when pay day falls on a weekend or bank holiday
These four answers become the configuration you enter into MSP Pulse. Its job is to mirror your payroll package's calendar precisely, not to set its own.
The different ways payroll periods work
Frequency is the easy part: weekly, fortnightly, four-weekly and monthly all mean exactly what they say. The part that trips people up is this rule: the pay date decides the tax period, not the days actually worked. A payment made on 7 January is taxed entirely in the new tax year, even if most of the hours it covers were worked in December.
Monthly schedules split into two genuinely different models, and both are legitimate:
| Model A: offset period | Model B: calendar month + cutoff | |
|---|---|---|
| Period dates | Shifted, e.g. 21st – 20th | Full calendar month, e.g. 1st – 31st |
| Cutoff | Same as period end | Earlier than period end, e.g. the 20th |
| Late hours (21st–31st) | Can't happen: they already belong to the next period | Roll into next month's pay run |
| Best for | Teams that want the payslip to always cover a clean rolling window | Teams that want payslips to read as "January pay", "February pay" |
Neither is more correct than the other. They are two ways of giving payroll enough processing time before pay day. What matters is picking one and configuring MSP Pulse to match it exactly.
Handling the edges
Week 53. A weekly schedule pays on the same weekday every week, and a year isn't a whole number of weeks, so whichever weekday 1 January falls on gets one extra pay date that year: 53 instead of 52. Most payroll packages tax that payment on a non-cumulative, single-week basis rather than folding it into the normal running total. It comes round for any given weekday every few years and is expected, not an error. MSP Pulse generates a weekly calendar as every pay weekday in the year, so you will see 52 or 53 pay runs.
The weekend/bank-holiday pay-day rule. When pay day lands on a weekend or holiday, you choose: pay on the previous working day, or the next one. This sounds like a small choice, but it has a real tax consequence. If 1 January is a pay day and you choose "previous working day", that payment is pulled back to 31 December, into the previous tax year with its old credits and rates. Choosing "next working day" avoids this. Know which one your payroll package uses before copying the setting into MSP Pulse.
MSP Pulse warns you when a pay run would be moved outside its own pay year, and offers a one-click switch to the next working day. The cutoff is different: it always moves to the previous working day, because moving a deadline later would leave you less time, not more.
National holidays, and what they actually affect
National holidays are one list per tenant for the year, shared by every schedule. Enter them manually or draft them with Set up with AI, which only proposes the holiday dates and creates the pay calendars. It never touches anyone's hours, pay or wages, and you review the holidays before they are saved. Holidays feed three separate things:
- Pay day itself. A holiday is one of the days checked when working out whether a pay day needs to move. A pay day landing on a holiday follows the "previous or next working day" setting above.
- Billing rate. If you have set up office-hours billing, a holiday is treated as a non-working day, so labour logged on it bills at the after-hours rate.
- The scheduling calendar. Holidays shade as non-working days, so they look different from normal rostered time when you plan work.
Because working days and holidays together decide where a cutoff or pay day lands when it is moved off a weekend, keep your holiday list current. A missing holiday doesn't just mis-shade the calendar; it can leave a cutoff or pay date on the wrong day.
Mapping your payroll package onto MSP Pulse
Once you know what your provider is already set to, enter the matching values on the Payroll tab (Settings → Finance → Payroll):
| Your payroll package shows | Enter it in MSP Pulse as |
|---|---|
| Pay frequency | Frequency |
| First pay date (weekly, fortnightly, four-weekly) | First pay date. The pay weekday is taken from it |
| First period's start date (monthly) | Start date |
| The day of the month wages are paid (monthly) | Pay run day |
| The deadline for submitting hours and expenses | Expenses / overtime cutoff |
| What happens if pay day is a weekend or holiday | "If the pay day is a weekend or holiday" |
For a weekly schedule the first pay date is a floor: no pay run is generated before it. Each pay run covers the previous week.
You can run more than one schedule at once. A tenant with weekly-paid engineers and monthly-paid office staff sets up both, each with its own employees. Each year starts with no schedules listed, so you only set up the ones you use. If you change from weekly to monthly, add the new schedule, move your staff onto it and archive the old one. Archiving keeps the history and timesheets, and a schedule with submitted timesheets can't be deleted.
When you add a new year, MSP Pulse checks that its first period follows straight on from the previous year's last one, and shows that last period greyed out at the top of the list so you can see there is no gap.
How MSP Pulse protects a finalized pay run
When you finalize a pay period, MSP Pulse locks in which approved expenses, mileage, paid overtime, time off in lieu and on-call shifts are included. That pack won't silently change afterwards, even if someone later edits or backdates a record that falls inside the same dates. It is the same principle MSP Pulse applies to invoices: once sent, the numbers are frozen.
Anything dated after your cutoff, even if it sits inside the current calendar period, simply isn't ready yet. It isn't lost: it is picked up when you finalize the following period, so you don't need to track or re-enter anything that arrives late.
Two things to know. Finalizing cannot be undone, so check the pack first (the Timesheet link shows a live preview before you finalize). And finalizing locks the claims and overtime lines, not the underlying schedule: working hours and booked leave still follow later edits to someone's schedule or leave.
Setup checklist
- ☐ Log into your payroll package and note its frequency, pay day, submission deadline and weekend/holiday rule
- ☐ If you pay monthly, decide which model applies: offset (Model A) or calendar month + cutoff (Model B)
- ☐ Create a matching schedule in MSP Pulse (Settings → Finance → Payroll) with the same first pay date or start date, pay run day and cutoff
- ☐ Set the weekend/holiday rule to match your payroll package exactly, not whichever option sounds safer
- ☐ Add a second schedule if you pay different staff groups on different frequencies
- ☐ Assign each employee to the correct schedule
- ☐ Add your national holidays for the year (or use "Set up with AI" to draft them) before you create the pay calendar
- ☐ Run one test period end to end before relying on it for a real pay run
- ☐ Finalize the period and check the pack matches what you expected before sending it to your payroll runner
Common pitfalls
- Cutoff doesn't match your provider's deadline. If MSP Pulse's cutoff is later than what your payroll package accepts, you'll finalize a pack with hours your provider won't have time to process before pay day.
- Picking the weekend/holiday rule without checking. "Previous working day" feels natural, but on a 1 January pay day it quietly shifts that payment into the previous tax year. Match what your provider already does; don't guess.
- Assuming the new year resets anything. It doesn't. Pay periods run straight through 31 December into January with no gap or restart. Only the tax-year label on the pay date changes.
- Treating a schedule change as free. Switching an employee's frequency or cutoff mid-cycle can mean a day gets missed or counted twice. Change it between periods, not during one.
- Changing settings and forgetting to regenerate. A change to a schedule applies to pay calendars created from then on. Press Regenerate on a year that already exists to apply it, then check the dates it reports.
- Not testing before the first real run. Run one full period (log entries, finalize, check the pack) before trusting it with a pay day that actually matters.