By Deeyoung MaLinkedInWebsiteMay 31, 20269 min readTemplates & ToolsReviewed October 11, 2026
Restaurant Payroll CSV Template for Canada
A practical payroll CSV template for Canadian restaurants: columns to include, what to review before export, what Maxuod Shift can prepare, and what payroll still needs to verify.
A restaurant payroll CSV template should make the handoff understandable without pretending that a schedule export is already a payroll-provider import. Start with the seven base columns Maxuod Shift actually exports, identify any conditional columns, then keep the evidence and provider mapping beside the file.
The exported report reads stored shift intervals and employee settings. A row can be internally consistent while a missed punch, interrupted break or wrong wage setting remains unresolved. Review those source facts before treating the row as an approved payroll input. Neither a CSV download nor a locked archive attests that every hour was actually worked.
This guide distinguishes the product’s report from a fictional receiving-provider layout. It does not determine legal entitlements, statutory deductions, tip classification or final pay. The manager and payroll reviewer still own those decisions.
Payroll CSV columns to include
The English base fields appear in this order. Language and selected account currency can change their visible labels; a monetary label may include the currency. Employee carries the recorded employee name. The current formatter does not append the backend employee number, and there is no separate payroll-ID column. Check the recorded name rather than assuming it is an approved provider ID.
| Base column | What the report carries | What the reviewer still checks |
|---|---|---|
| Employee | Recorded employee name | Match the person to the receiving payroll record; resolve duplicate names |
| Regular Hours | Hours assigned to the regular bucket by the report settings | Source time, breaks and the employee’s applicable treatment |
| Overtime Hours | Hours assigned to the overtime bucket | Threshold, coverage, daily/weekly interaction and exceptions |
| Hourly Wage | Wage context used for the estimate | Correct person, rate and effective period |
| Regular Pay | Estimated regular amount | Inputs and receiving-system calculation |
| Overtime Pay | Estimated overtime amount | Applicable rate basis, multiplier and separate review items |
| Gross Pay | Baseline gross estimate | Not net pay or an automatic final-pay decision |
Confirmed adjustment data can add a provincial-estimate/adjustment column and Total with adjustments. The export requires an adjustment total in the report’s weekly summary before either column can appear. With that summary present, the columns appear if its total is nonzero, a confirmed adjustment record is retained, or an employee row has a nonzero adjustment. Retained records can therefore show the columns even when they net to zero; a row amount alone without the summary cannot. Locking alone does not add them. Gross Pay remains the baseline rather than being overwritten by the adjustment.
Some older finalized reports include Planned Hours and Variance (hrs). Current single-timeline reports do not gain those comparison columns merely because the manager locks a week. The current payroll export has no general Notes column; keep the explanation in a controlled exception record.
Sample restaurant payroll CSV layout
Illustrative provider layout, not a Maxuod Shift export or a supported integration: a fictional payroll provider asks for employee ID, pay code, units and an external reference. Its example row is PAY-014 / REG / 8.00 / CLOSE-3. The name-to-ID lookup and pay-code decision must come from the receiving workflow.
| Receiving field | Mapping decision | Acceptance check |
|---|---|---|
| Employee ID | Match the exported name through a separately approved mapping | Reviewer identifies the right employee, including duplicate names |
| Pay code and units | Map reviewed hour buckets to the provider’s required codes | Preview agrees with the approved source and its rounding rules |
| External reference or Notes | Add only if the provider specification supports it | Keep the exception reference separate from confidential case details |
The report also contains a title/week line, business context, a blank separator, totals and conditional notices. Its first row is therefore not necessarily an import header. Preserve the original report, prepare any required mapped copy separately, and ask the receiver to inspect its preview before using it for payroll.
What to review before sending the file
Compare the source week, employee mapping and report totals with the reviewed time record. A value such as 8.33 hours is formatted to two decimals; retain the underlying timestamps or minutes when the provider’s rounding convention matters. Do not repair a mismatch by adding an unexplained balancing amount.
For a locked week, use the frozen baseline and its retained confirmed adjustments rather than rebuilding old amounts from today’s employee settings. A modern archive preserves the adjustment records with the report. An older archive may show surviving confirmed records created no later than the lock, alongside a historical-source review warning: the complete adjustment set cannot be verified.
A missing or empty surviving legacy set is unknown, not verified zero. Keep that review warning with the handoff. If later evidence changes the week, preserve the first export and use a separately approved correction record or replacement version; do not quietly overwrite the file already sent.
How Maxuod Shift fits
Maxuod Shift sits before payroll. It helps the manager build the weekly schedule, review employee hour totals, see overtime risk, finalize the week, and export a cleaner CSV handoff. That is useful because many payroll problems start before payroll ever opens the file.
It does not run payroll, move money, calculate statutory deductions, remit tax, issue T4s, decide employee classification, or guarantee compliance. Payroll remains with your payroll provider, accountant, or internal payroll process.
The Free account supports 12 active employees, 1 location and 8 weeks of account history. Its core workflow includes CSV/XLSX exports, PDF/print and tips. Those exports are not a paid-only feature. Account history is not a substitute for the business’s required records archive.
For the workflow around this template, build the week in the free scheduler, review hours in the employee hours calculator, check overtime exposure in the overtime calculator, and use the payroll cutoff checklist before sending the export.
Canadian recordkeeping notes
The CRA keeping-records hub and IC05-1 electronic recordkeeping guidance were reviewed October 11, 2026 for record access and responsibility. Electronic records need to remain readable; using a third party does not remove the business’s responsibility. Retention requirements have exceptions. These tax-record references do not establish provincial employment-record retention rules.
Keep the original export, mapping, reviewed source record, correction references and receiver’s acknowledgement together. Check that the files can actually be reopened by the responsible person. Do not assume a payroll subscription or eight weeks of account history satisfies every retention obligation.
The Canada Labour Program employer-compliance reference belonged to the May 31, 2026 source set and was not rechecked for this refresh. Its federal scope must not be presented as the employment-record authority for every provincial restaurant. Ask the qualified recordkeeping owner which requirements apply.
Questions to answer before you export
Can I add Notes or rename the columns?
A provider-specific copy may require that work. It is not the product’s original seven-column report. Keep a mapping/version record and preserve the unchanged original so another reviewer can explain what was transformed.
What makes the handoff ready?
The receiver can identify each employee, explain the included amounts, locate any held review item and reproduce the approved mapping. If one of those checks fails, return that item for clarification rather than calling the file final. A pending mapping or correction review does not authorize erasing worked hours or postponing pay obligations. Hold the review item, not the employee’s pay; the payroll owner must address pay obligations separately.
Written as an operator checklist, not legal or payroll advice. Confirm local rules before changing pay, holiday, or tip policies.
Related guides
What to Check Before Payroll Cutoff When Exporting Employee Hours
A Canadian payroll-cutoff checklist for small teams: confirm dates, actual hours, overtime flags, holiday notes, corrections, and export records before the file leaves the schedule.
Excel vs Employee Scheduling Software for Small Businesses
When should you replace Excel for staff scheduling? Test availability, schedule changes, actual hours and payroll exports before moving your small team.
Square Shifts vs Maxuod Shift: Keep Staff Work in Your POS?
Already use Square? Compare its POS-connected staff workflow with an independent schedule-to-export tool, including owner counting and a CAD cost example.
Build the schedule before the week gets loud
Maxuod Shift keeps employee availability, overtime risk, payroll estimates, and tip distribution in the same place for small restaurant teams.