Identify the last accepted version
Record the original batch ID, export timestamp, period, affected record ID and recipient. Preserve the original file. Write the old and proposed values and why the change is requested. Before editing the source, determine whether the recipient has already imported or acted on it; the same correction can require different handling before and after acceptance.
Choose replacement or adjustment explicitly
In a fictional batch B-07, record W-020 changes from 45 to 60 minutes. A full replacement batch contains the corrected 60-minute entry and is labeled as superseding B-07. A delta adjustment is +15 minutes linked to W-020 and B-07. The recipient must support the chosen method. Sending a replacement and adding a +15 adjustment would produce 75 minutes if both were applied.
Preserve the correction trail
Keep who requested the change, the review decision, the version released and the recipient acknowledgement. If the product locks approved records, do not bypass that control or delete evidence. Use its documented correction route or an agreed external adjustment register. Product approval and export fields vary; a timestamp in one report is not proof of a complete change history.
Close the correction only after reconciliation
Compare the recipient’s final accepted total with the intended corrected total. Verify unaffected records remain unchanged. Mark the earlier batch as superseded in the handoff register, not by erasing it. If the recipient cannot identify which version it used, hold further replacements and reconstruct that state first. A quick resend can deepen the uncertainty rather than fix it.
Sources and boundaries
These pages were read on 2026-09-23. Primary documentation supports the dated product facts. Proposed checks and fictional examples are our editorial method.
- Clockify — detail — Vendor product page · clockify.me · checked 2026-09-23
- Clockify — approval — Vendor product page · clockify.me · checked 2026-09-23