What to Check Before Payroll Cutoff When Exporting Employee Hours

How do restaurants calculate payroll?

Before you export employee hours to payroll, separate the report you can reproduce from the facts that still need approval. One exception ledger should explain what changed, who reviewed it, which version was sent and what remains on hold.

A restaurant’s payroll process approves time and other inputs, applies the relevant treatment and deductions, then issues pay in its payroll system. Maxuod Shift supports the earlier schedule, estimate and handoff work. The stored shift record and locked report do not, by themselves, prove attendance or final legal entitlement.

Start by agreeing on the receiver’s cutoff and correction route. A late change needs a named owner and a version reference, not a second file quietly labelled final. The example below follows one record through that decision so the next reviewer can see what was accepted and what still needs an answer.

The seven checks before export

Give the ledger seven identifiers: the source week and location; employee/payroll mapping; original entry; evidence reference; proposed change; reviewer and review time; and disposition/version. These are suggested fields for the restaurant’s controlled record, not seven additional columns promised by the app.

Use explicit statuses such as awaiting evidence, approved for this handoff, and correction pending. An empty status does not mean approved. Keep private employment explanations in their restricted record; the ledger needs only the reference and the operating consequence needed by the payroll reviewer.

Start with changed or disputed records, but reconcile the whole employee list and totals before release. Exception-first ordering helps route work; it is not evidence that a sample catches most payroll mistakes.

Follow one exception ledger through the cutoff

One fictional ledger follows Sam’s close. The source shift is 09:00–13:00, with no unpaid interval in this illustration. The report’s baseline estimate is $80 at an entered $20 rate. A separate $25 adjustment has already been confirmed and recorded before the week is locked. These are illustrative report inputs, not a customer result or a pay entitlement.

The last row does not authorize 20 extra minutes, zero extra minutes or a particular payment. It identifies a question. Preserve the first record, check the new evidence and let the payroll owner decide the corrected handoff. A locked total cannot settle a conflicting attendance record.

What changes on payroll cutoff day

Locking changes the report’s source, not the truth of every input. Current archives freeze baseline hours, wages and pay alongside confirmed adjustment records. Later changes to a live shift or employee wage do not recalculate that frozen baseline. The archive’s internal consistency still does not establish that the manager’s time review was complete.

In Sam’s example, $80 remains baseline Gross Pay. The separate adjustment is $25 and Total with adjustments is $105. Do not add $25 to Gross Pay and then add it again during import. Preserve the receiving system’s mapping so the payroll reviewer can see which amount was used and why.

Approval to send a record is narrower than final payroll approval. Identify which items the reviewer accepted and which remain unresolved. A cutoff deadline does not make missing evidence disappear or permit silence to be treated as consent.

One exception ledger is more useful than a perfect-looking CSV

If Sam’s week is an older archive without a complete frozen adjustment set, surviving confirmed records created at or before its lock may be reconciled against the preserved baseline. Keep the report’s historical-source review warning visible. It means the surviving set is not proven to be the complete historical set, even when it produces a plausible total.

A missing lock timestamp, unavailable records or an empty surviving set can leave the adjustment evidence unavailable. Unknown is not zero. Existing stored adjustment amounts must not be added twice, and an adjustment created after the lock is not evidence for the legacy pre-lock reconciliation.

Keep the ledger’s review state open until the responsible person resolves that gap. The free weekly payroll handoff checklist can carry the evidence reference, owner and unresolved question beside the file. It does not supply missing approval evidence.

Build a simple payroll evidence pack

File the original source week, reviewed time evidence, approved adjustment references, exact exported file and ledger version together. Add the sent time and recipient. If the receiver needs a mapped import copy, keep its mapping and preview acknowledgement without deleting the original report.

For a post-export correction, reference the first file, identify the changed employee/item, preserve the evidence and record who approved the replacement or adjustment. Tell the receiver which version supersedes which and which items remain held. Do not maintain two silently different files with the same final label.

For column-level decisions, use the restaurant payroll CSV template guide. Its actual export fields and illustrative provider mapping answer a different question from this cutoff ledger.

Prepare the handoff without pretending to run payroll

Maxuod Shift is useful before payroll because it keeps the weekly schedule, employee hour totals, overtime visibility, and CSV export in one workflow. The goal is to reduce the mess that happens when a manager builds the schedule in one spreadsheet, tracks changes in a group chat, and then rebuilds hours in a second file for payroll.

It is not a payroll provider. It does not move money, calculate statutory deductions, remit tax, issue T4s, decide employee classification, or guarantee compliance. Use it as the scheduling and hours review layer before your payroll provider or accountant does the payroll work.

A Free account covers 12 active employees at 1 location. Its manager can review the week and export CSV/XLSX without upgrading. Keep the sent file and correction ledger in the business’s own controlled archive: the account keeps 8 weeks of history, not an indefinite payroll evidence pack. A plan upgrade does not resolve an unapproved time entry.

For a quick test, build one real week in the free scheduler, check the totals in the employee hours calculator, review overtime exposure in the overtime calculator, attach the result to the weekly payroll handoff checklist, and compare plans on pricing only if you need capacity or history beyond the Free limits.

Recordkeeping notes for Canadian teams

The CRA keeping-records hub and IC05-1 electronic recordkeeping guidance were reviewed October 11, 2026 for this bounded record-access discussion. The business remains responsible for readable records when a third party handles them. Check applicable retention requirements and exceptions separately; these sources are not provincial employment-retention authority.

The older Canada Labour Program employer-compliance reference retains its July 20, 2026 source history and was not rechecked here. Federally regulated workplaces and provincially regulated restaurants require their own appropriate sources. This is operational guidance, not legal, tax, payroll or accounting advice.

Do not call the file ready when the receiver cannot trace an amount, identify the current version or distinguish approved items from held review questions. 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. A downloaded report is not an attestation.