
Employee Payroll Register Excel: Master Data Plus Every Pay Run
Set up an employee payroll register excel file: Employee Info fields, Canadian register rows, CPP/EI flags, and links to remittance and T4 workflows.
This setup guide extends the Canadian payroll register template excel pillar. An employee payroll register excel file fails in two opposite ways: a register with no master data (you retype province and claim codes every period), or an employee list with no period ledger (you cannot prove what you paid). Canadian payroll needs both sheets working together.
Key takeaway: Keep Employee Info as the source of truth for identity and CRA-relevant flags; keep the Payroll Register as the append-only history of each pay run. Link them with a stable EmployeeID.
Employee Info fields that prevent bad pay runs
Employee Info essentials
| Field | Why it matters |
|---|---|
| EmployeeID | Joins Info ↔ Register |
| Legal name / SIN storage policy | T4 identity — store SIN securely; minimize exposure in shared files |
| Province of employment | Affects provincial tax |
| Pay type / frequency | Salary vs hourly; weekly/biweekly/semi-monthly/monthly |
| TD1 federal / provincial context | Claim codes drive tax withholding |
| CPP exempt? / EI exempt? | Prevents incorrect deductions |
| Hire / termination dates | Proration and final pay |
| Default payment method | EFT vs cheque |
| Notes | Special arrangements |
Avalon’s Start Here + employee tabs pattern is a Canadian example of putting these inputs where calculators can see them before amounts hit a register.
How the register consumes Employee Info
Run payroll with both sheets
- Update Employee Info when TD1, province, or exemption status changes — date the change in Notes.
- Create register rows for the pay period using EmployeeID (Data Validation list).
- Pull display name / province via XLOOKUP if helpful.
- Enter earnings; calculate CPP/EI/tax via CRA PDOC or T4032.
- Fill employee and employer deduction columns; confirm net pay.
- Save an archived copy of the finalized run.
Warning: Sharing an Employee Info sheet that contains SINs in an open OneDrive folder is a privacy incident waiting to happen. Restrict access; mask SIN where possible; follow your privacy obligations.
Hygiene rules that save February
- Never reuse EmployeeIDs.
- Do not delete terminated employees mid-year — mark status Inactive so YTD remains.
- Keep contractors off the employment register.
- Align naming with how you will print T4s (CRA T4).
- Revisit exemption flags annually.
Where this sits in the cluster
- Template shopping: payroll register template excel
- Columns: payroll register format in excel
- CPP/EI: canadian payroll cpp ei excel
- T4: t4 payroll register excel
- Product: Canadian payroll register template excel
Field notes from Canadian payroll register cycles
After every pay run, lock a dated copy of the register totals before you change rates or claim codes. Mid-year TD1 updates and CPP/EI exemption flags are common — if you overwrite the live row without an archive, February T4 reconciling becomes guesswork.
Keep employer CPP and EI in their own columns. Remittance math and general-ledger wage expense need those amounts; stuffing them into a single “taxes” cell forces you to re-split later. When finance asks “what did we remit last month?”, you should filter the register by pay dates in that remittance period and sum — not rebuild from memory.
Keep pensionable and insurable earnings honest
Gross pay is not always the same as CPP pensionable earnings or EI insurable earnings. Record both when your pay codes include non-pensionable or non-insurable amounts. The CRA Payroll Deductions Online Calculator and T4032 tables expect the right bases — your register should too.
If you only store net pay, you cannot explain a CRA notice or a T4 mismatch. Earnings bases are part of the audit story, not optional metadata.
When to reopen the Start Here sheet
Reopen onboarding notes when you add a province of employment, change pay frequency (weekly vs biweekly vs semi-monthly), or hire someone with CPP or EI exemption status. Those three inputs change almost every deduction line. A five-minute Start Here review beats a month of wrong remittances.
Also reopen Start Here after CRA annual rate updates take effect, and after anyone on the team “helps” by typing over a gray formula cell. Document which cells are inputs in one place so the next person does not invent a second process.
Remittance and bank proof habits
After you pay employees, keep the register row IDs (or pay date + employee ID) in your bank memo or payment export when possible. Matching bank outflows to register net pay is how you catch a duplicate EFT or a missed cheque before month close.
Build a simple remittance checklist: filter register → sum employee deductions + employer CPP/EI → compare to the amount you will send CRA → file the confirmation PDF beside that month’s register archive. This habit is boring — and it is what makes T4 season short.
What this workbook is not
A Canadian payroll register is not a personal expense tracker, not a US Form W-2 worksheet, and not a full HRIS. It will not replace advice from a CPA or payroll professional when you have multi-province complexity, union dues, or unusual taxable benefits. Use the register to keep Canadian pay-run facts tidy; escalate edge cases instead of hiding them in a Notes cell nobody reads.
Field notes from Canadian payroll register cycles
After every pay run, lock a dated copy of the register totals before you change rates or claim codes. Mid-year TD1 updates and CPP/EI exemption flags are common — if you overwrite the live row without an archive, February T4 reconciling becomes guesswork.
Keep employer CPP and EI in their own columns. Remittance math and general-ledger wage expense need those amounts; stuffing them into a single “taxes” cell forces you to re-split later. When finance asks “what did we remit last month?”, you should filter the register by pay dates in that remittance period and sum — not rebuild from memory.
FAQ
What is the difference between Employee Info and the payroll register?
Employee Info holds relatively stable master data (province, pay type, claim context, exemptions). The register holds period transactions. Separating them prevents retyping identity data every pay run.
Which employee fields matter for Canadian payroll?
Legal name, employee ID, province of employment, pay frequency/type, TD1 claim context, CPP/EI exemption flags, and start/termination dates are the usual minimum.
How many employees can Excel handle?
Small teams often manage comfortably. As headcount, provinces, and benefits complexity grow, dedicated Canadian payroll software becomes more appropriate.
Should contractors live on the same register?
Generally no — employment payroll and contractor payments follow different tax rules. Keep clear separation to avoid T4/T4A confusion.
Is there a template with both sheets?
Yes. PlanoNest’s Canadian payroll register template is built around Employee Info and Payroll Register sheets — one-time purchase; see the product page for pricing.
Related reading in this cluster
Stay inside one Canadian payroll register workflow: start from the pillar guide, evaluate sheets with payroll register template excel, set columns via payroll register format in excel, run deductions with canadian payroll cpp ei excel, balance year-end using t4 payroll register excel, and connect master data in employee payroll register excel.

