Read your expected-pay ledger

What the headline tells you

Today and Pay show expected wages calculated from recorded work and the configured rules. When applicable, expected per diem is separate. The period dates, actual worked hours, timezone, and rule context are part of the answer—not optional decoration.

Expected wages are not take-home pay, a guaranteed deposit, or proof of every contractual entitlement. The app does not calculate all taxes, deductions, benefits, or unsupported rules. An incomplete period is a to-date estimate, not a valid basis for declaring a full paycheck short.

Inspect the work behind the amount

Open Pay and review the ledger. Open a component to inspect the work facts, quantity, rate, multiplier, and rule/source information available for it. A callout guarantee is a separate entitlement from worked clock time.

Use the applied snapshot for the particular component, especially after a dated rule change. Rules used for this estimate provides agreement context, while component evidence explains that particular amount. A source reference you entered is not independent certification.

A worked example

The following numbers are synthetic. Assume the confirmed rules classify 40 hours as regular and six as double time, at a $58 base rate, with no allowances in this example:

The categories must come from the rules applied to actual work. Do not manually label all overtime as double time unless the configured agreement supports that result.

Calculation precision in the v2 development build

New estimates keep recorded time precise through money rounding. For a synthetic example, one minute at USD 58.50/hour is USD 0.975 before the stated half-up cent rounding, giving USD 0.98. Work-time summaries and rate explanations use hours, minutes or seconds so a short shift is not presented as a misleading rounded-hour equation. An ≈ marker indicates a presentation-rounded duration. Use the actual start/end times and unpaid breaks when checking the calculation; paystub-hour comparisons remain on their stated hours basis.

Earlier saved estimates and audit revisions retain their recorded values and calculation version. If updated precision changes an active check’s ledger, the app requires a new review instead of relabelling the old result as current. An explicit review of a closed period uses current precision and appends a new audit revision while keeping the original estimate and earlier checks. This is a calculation correction, not evidence that money has been recovered or that every pay obligation was checked.

The v2 candidate also requires a new review when weekly comparison safeguards or premium-only base precision change, even if the configured amount stays the same. This changes whether an active comparison can be relied on; it does not rewrite the earlier verdict or expected-pay record. For premium-only monetary lines, new checks keep exact base-time evidence; an older rounded-hours mapping can differ at a half-cent even with unchanged gross. See comparison safeguards . Native interaction and migration acceptance remains pending.

An unavailable result is not zero

A missing or unsafe calculation can show a problem requiring review instead of an amount. Examples include work outside agreement effective dates or an ambiguous guarantee across a rule change. Read the message and correct the underlying facts or rule coverage.

An empty work log is not a prediction that the employer owes nothing. Likewise, a saved draft is not a recorded shift until the work entry is successfully saved.

Before comparing a paycheck

Check every shift and unpaid break for the full period. Then confirm the paystub’s dates, current-period gross, and whether that gross includes per diem. Never subtract a net bank deposit from expected gross wages.

Next: Import the matching paycheck and understand gross and earnings layouts .