Check a paycheck

Use History and audit revisions

Add late paychecks, correct confirmed paycheck facts, and return to earlier audit evidence.

Find the right period

Open History. Closed work periods are grouped by month and show their dates and expected wages when a safe calculation exists. A period with no paystub is marked Awaiting paycheck. A period that was closed before its calculation could be priced is marked Calculation needs review and keeps the warning that explains why; it is not a zero or an estimate.

Select the work dates covered by the paycheck, not simply the most recent item. History uses the period’s saved timezone context, rather than your phone’s current location.

Add a paycheck that arrived later

Select the pending period and choose Add this paycheck. Import or enter its paystub and complete field review. You can do this while the next work period remains open for new shifts.

The closed period’s work and rules stay frozen. A late audit or later rule correction does not recalculate old work using the latest profile rate unless you explicitly review and confirm it.

In the v2 development build, an explicit new paycheck review uses current calculation precision with the closed period’s saved rules and clock facts. The original estimate and earlier audit revisions remain intact. The period’s Saved expected amount follows its current recorded paycheck comparison; open an earlier revision to inspect the earlier answer.

Correct paycheck facts

Open the period and choose Correct paycheck facts, or open its live audit and choose Review or correct paycheck facts. To keep the same source, choose Correct existing facts, keep original where offered.

Correct the erroneous field, reconfirm it, and review the comparison basis and scope before saving. A correction appends an audit revision rather than silently replacing all prior evidence.

This is a paycheck-fact correction, not arbitrary editing of frozen work. If already closed work itself is wrong, preserve a backup and contact support before deleting or rebuilding history.

Read an earlier revision

Under Saved paycheck checks, select the timestamped audit you need. Its saved work, rules, calculation, and confirmed facts explain what was assessed at that time. A later correction does not make that earlier record the current answer.

Use Track this paycheck question from the intended audit revision to record a follow-up about that exact paycheck. Notes for a different revision are labelled, and a report for an older revision includes only that revision’s follow-ups when you opt in.

When sharing a report, make sure you have opened the intended current or historical revision. Keep the period and revision context with any explanation you send.

Original files can be shared by several revisions. Removing a shared original removes access for all of them, even though the confirmed figures and calculation records remain.

Earlier weekly comparisons in the v2 candidate

An Earlier recorded comparison note identifies a saved result that did not record verified workweek-to-paycheck mapping. Its original verdict and amounts remain unchanged. An explicit new review uses current safeguards and appends a revision; it does not reclassify the old record. Historical PDF copies disclose this scope beside the Recorded verdict. Native interaction/report acceptance of this candidate is pending.

Delete only with a backup plan

Delete work period and its checks → Delete period removes that period’s local work and confirmed facts. Originals that are not shared elsewhere are deleted or queued for cleanup. This is not the same as closing a period, and the guide does not assume a historical recycle bin exists.

Export a complete backup first when those records may be needed later. Local deletion does not delete copies already exported to Files, iCloud Drive, email, or another destination. It also does not cancel a subscription.

Next: Back up and restore safely .

In the v2 development workflow, benefits checks are independent fund/period records. Deleting a wage work period does not delete those separate benefits checks.

Premium-only precision in the v2 candidate

Development preview: final App Store release and physical-device acceptance remain pending. An older Base + premium only check may have reconstructed base pay from rounded decimal hours. At a half-cent this can change a line by one cent even when gross is correct. New checks use exact base-time evidence. An older active monetary-line check requires an explicit new review; its original values remain in the earlier revision. Earlier recorded comparison and a premium-only scope note identify preserved historical results, including their Recorded verdict in reports. Missing exact evidence keeps a new line comparison in review until recalculated from original work and rules. This does not verify missing weekly or agreement coverage.

Still unsure? Keep your original records and get help before changing facts to make a total match.