At a glance
- Every plan can backdate pay stubs up to 60 days with the self-serve tool.
- Further back than that, we build the history with you for a quote. Email support with how many months and employees.
- Once a newer pay run exists, the stubs before it lock.
How far back you can go
Payroll history has to be built one pay run at a time, in order, so that year-to-date totals, CPP, CPP2 and EI maximums, and TD1 changes stay correct. That's why PayCub doesn't generate a year of stubs in one batch.
- Up to 60 days back: included on every plan, using the self-serve tool.
- More than 60 days back: email us with how many months and how many employees. Pricing depends on both, and the further back you go, the larger the discount per month.
Why older stubs lock
Once a pay stub has later runs after it, it can't be edited. This is how payroll records have to work:
- Accuracy chains forward. Each run's year-to-date totals and CPP and EI amounts depend on every run before it. Changing an old stub would make every later stub wrong.
- Stubs are records. The employee may already be holding that stub for a loan application or a tax question. It has to keep matching what's on file.
- It protects you. A locked, in-order history is what you want to show if the CRA ever asks about an employee's pay.
Made a mistake on a recent run? Contact us. Depending on how recent it is and what changed, there are ways to correct it without breaking the record, but it has to go through support rather than a self-serve edit.