Pay runs calculated on the CRA’s own formulas, paystubs your clients’ staff can read, T4s and ROEs when they are due, and a remittance calendar that covers every employer at once. The journal entry lands in the books you already keep.
Ontario, Alberta & British Columbia · T4s and ROEs · PD7A remittances · Posts to the books
Payroll is organised by employer, not by client type. Your own staff and every client you run payroll for sit in the same list and behave the same way, because there is one code path underneath rather than a bureau mode bolted onto a single-company product.
Employees, attendance, schedules, time off, pay runs, T4s and ROEs are all scoped to the employer you opened. The employer stays in the address, so a link you send a colleague opens exactly what you were looking at.
Every due date across every employer you run sits on one firm-wide calendar, because the thing that gets a firm penalised is the deadline nobody was looking at.
A raise is a new record with a date on it, not an overwrite. Re-run June in November and June’s rate is what gets used, which is what makes a correction defensible months later.
The engine implements the CRA’s T4127 payroll deduction formulas: federal and provincial tax, CPP and the second CPP contribution, EI with its annual maximums, the basic personal amount and its phase-out, TD1 claims, and the Ontario health premium and surtax. Maximums are committed when a run is approved rather than when it is calculated, so an employee who reaches the CPP or EI ceiling mid-year stops contributing at the right cheque.
Pay run · Biweekly · Approved
Figures are illustrative.
Everything a payroll year produces, generated from the runs you already approved rather than re-keyed at the deadline.
A PDF per employee per run, emailed out in a batch once the run is approved. A draft run cannot be emailed by mistake.
Built from year-to-date figures, reconciled against the runs before you issue, then produced as slip PDFs emailed to employees and a CRA XML file for filing. Amended slips are supported, and the slips warn you when they fall behind the approved runs.
Insurable hours and earnings pulled from the pay history into a worksheet with every box filled for ROE Web, with re-hire handling, a list of ROEs still owed, and a guard against issuing the same ROE twice.
Due dates worked out from the employer’s remitter type, including the weekly buckets a threshold-two remitter has to hit, with a PD7A figure sheet to remit against. The remittance amount also lands on the client’s Payroll filing card in Workflow.
A payroll register, year-to-date totals, a deductions report and cost per person, each exportable to CSV, plus an employee list export with the SIN masked.
A T4 or ROE is held until the employee’s SIN and address are on file, a draft run cannot be emailed, and paystubs and T4s go out only from approved runs.
Time clock
Punches are recorded in your firm’s timezone, not the server’s.
A shared kiosk takes a PIN and records punches as real instants. Schedules and reusable schedule templates say what was meant to happen, time-off requests say what changed, and a punch left open overnight is closed automatically to the scheduled end time rather than running to midnight.
Switch posting on for an employer and approving a run posts to their books through your chart of accounts: wages to the expense head, source deductions, the employer share, EHT and WSIB to their payables, and net pay to a clearing account. The heads are resolved by role rather than by name, so a firm that renames an account does not break the posting. Posting is a per-employer setting, so you decide whose books receive the entry.
See how the books fit togetherPayroll is an add on. Your firm turns it on, it appears for the staff you give access to, and we would rather sit with you through the first run than have you switch it on cold.
Built for Ontario, Alberta and British Columbia employers, on the CRA’s T4127 formulas and each province’s tax figures.
Yes. Payroll is employer-scoped. Your own firm is one employer and every client you run payroll for is another, all in the same place with one code path behind them. You pick an employer and work inside it, and the CRA remittance calendar stays firm-wide across every employer so nothing is missed.
Ontario, Alberta and British Columbia. The module carries the CRA T4127 payroll deduction formulas and the provincial tax figures for those three, and it checks each employee's province before a run is approved. The tax tables themselves live in Settings, with January and July releases, a verified-against-CRA badge, and a line-by-line calculation trace for every employee on every run.
Everything you need to pay and file through your normal channels: the net pay per employee, a PDF paystub per employee per run, the PD7A figures and a worksheet to remit against, T4 slips as PDFs plus the CRA XML file for filing, and a record of employment worksheet with every box filled for ROE Web. Four payroll reports (register, year-to-date, deductions and cost per person) export to CSV.
Paystubs and T4 slips are emailed to them as PDFs once the run is approved, so there are no accounts to manage or passwords to reset. On the time clock, employees punch with a PIN on a shared kiosk, and staff who already have a CRM login punch without one.
Yes, for any employer you switch posting on for. An approved pay run then posts a journal entry into that client’s bookkeeping engagement, resolving wages, source deductions, the employer share, EHT and WSIB, and the net pay clearing account through your chart of accounts. Posting is a per-employer setting, so you decide whose books receive the entry.
Yes. Employer Health Tax and WSIB premiums are calculated as a percentage of gross for the employers you set them on, posted to the books with the run, and carried onto the remittance calendar alongside the CRA source deductions.
Employees punch in and out against a PIN, punches are recorded as server-side instants in your firm’s timezone, and anything left open is closed automatically overnight to the scheduled end time. Schedules, schedule templates and time-off requests sit alongside it, and approved hours flow into the pay run.
See a pay run calculated, a paystub emailed, a remittance dated and the journal entry land in the client’s books. Talk to us and we will take you through it end to end.