In this article
Define the factual question and the current workflow stage before selecting a correction action in Hours+.
Do not start with the button
An accountant notices a possible discrepancy and asks which action to take. The answer depends on what is wrong, whose confirmation is needed and how far the item has travelled. “Edit,” “reject” and “recall” describe different workflow actions; none is a generic undo for all payroll events.
The Hours+ payroll-accountant guide describes editing days and times with a history trail, rejecting a timecard with a reason, and recalling a previously submitted card in the described workflow. It also says a card created for an employee needs that employee’s sign-off before submission for approval. These descriptions must be read with current role access and processing status; they are not a universal permission to change a finalized result.
Write the question in neutral language
Begin with the exact field or day and the evidence that prompted review. “Tuesday’s entry differs from the approved work note” is more useful than “Tuesday is wrong.” The first sentence identifies a comparison; the second presumes a conclusion. Ask the authorized fact owner to establish which source should govern.
Separate clerical correction from a disputed entitlement or classification. A production accountant may be able to update a field but still need direction about what that field should contain. The software’s ability to accept a value does not resolve a contractual or legal question.
Fictional rejection note, rewritten
Unhelpful: “Fix this and resubmit.”
More useful: “Please review the meal entry for the stated workday against your actual work record. The submitted interval and the department note differ. Confirm the correct entry through the approved production process.”
The revised note names the issue without dictating unsupported facts. It avoids spreading other employees’ details and does not ask the recipient to approve something they do not understand.
After the correction
Check the resulting record and its current review stage. A saved change is not the same as a completed approval. If an action returns the card to an earlier stage, identify who now needs to review it. If the intended action is unavailable or the record is already downstream, ask the responsible coordinator for the supported correction process rather than creating a replacement card.
Preserve the reason for the change in the appropriate system. An email thread can explain context, but it should not be the only place where the operational team can discover that a source value changed. Use the production’s approved documentation practice and avoid exporting sensitive history merely to create a local archive.
Do not promise a payment outcome
A correction can affect later review or processing, but this publication cannot determine a payroll date or whether a payment needs adjustment. If a worker asks about money already issued, route the inquiry through the production’s official payroll channel with the minimum relevant context. Do not treat a timecard action as confirmation of a bank event.
Read the first-pass method to classify the issue, then the handoff guide to keep the next owner informed. Clear wording reduces repeat corrections because the recipient knows the actual question.
Sources and scope
Public documentation checked October 25, 2026. Product facts are attributed below; the review methods and fictional examples are original editorial analysis, not an official procedure, payroll calculation or private-account test. Permissions and interfaces can differ. Follow current instructions in your authorized production environment.