In this article
Use a controlled comparison to tell a changed report population from a changed payroll value.
Start with the question, not the subtraction
Two exports can differ because of their dates, filters, included records, processing stages or values. Subtracting their totals is easy; explaining the difference requires a controlled comparison. A useful reconciliation names the question before selecting the reports.
The official Hours+ Reports collection lists distinct report types, including open batch, spot audit, pending timecard, Hot Cost and batch reports. Their names are not interchangeable evidence. Select the documented report that fits the question, and consult its current instructions rather than assuming every export contains the same population.
A comparison contract
| Fix this dimension | Record this fact |
|---|---|
| Scope | Project, department and period intended. |
| Population | Which categories or statuses are included. |
| Snapshot | When each report was generated. |
| Basis | Whether values are estimated, entered or processed. |
| Purpose | The specific difference being investigated. |
This contract is a working note, not an instruction to expose identifiers publicly. Keep detailed matching inside the approved accounting environment.
Fictional example: twelve rows versus thirteen
A fictional reviewer sees a higher total in a later export. Before examining every line, they notice one additional row. The extra row might explain part of the difference, but it does not establish that the remaining rows are unchanged. The reviewer separates additions, removals and changed comparable items.
That separation produces three different questions. Why was a record newly included? Why did another disappear? Which fields changed on records present in both snapshots? Asking those questions individually is more precise than circulating a single unexplained variance number.
Do not force a match
A reconciliation can end with an unresolved difference. That is preferable to editing an analysis copy until the totals agree. If a known timing or population difference explains the variance, label it. If it does not, preserve the comparison and route the remaining question to the responsible team.
Never change a source timecard solely to make a report total match a target. The underlying work facts, authorized review and applicable processing instructions govern source records. A spreadsheet is a diagnostic aid, not authority to alter them.
Make the result repeatable
Another authorized reviewer should be able to understand what was compared without reconstructing your memory. Record the report names, scope and generation times, the categories of differences, and the owner of any open question. A final summary should distinguish “matched,” “explained difference” and “unresolved” instead of collapsing all three into “checked.”
Read the estimate guide when one side of the comparison is Hot Cost. Read batch and invoice boundaries when grouping changed between snapshots. The comparison is reliable only when its limits are visible.
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.