Reports Overview
What's on the Reports page, and how live reporting works in Greenroom
Everything on the Reports page is built the moment you ask for it, straight from your payroll data — as the page itself puts it, "nothing here is a stale file." There's no batch job to wait on and no library of previously-generated reports to dig through. Pick a report, tell it which run, date range, or year you care about, and it renders right there on the page.
The five reports
All five live on one page — Reports in the main navigation — as a row of cards. Four of them work the same way: fill in a card's picker and click Generate, and the result appears below, replacing whatever was showing before — you can only look at one of those four at a time. The fifth, the QuickBooks package, is different: its card takes you to its own page instead of generating inline, since it has its own multi-step setup and history to show.
| Report | You pick | What it shows |
|---|---|---|
| Payroll register | A run | Every payee on that run — gross, deductions, taxes, net, payment method, and check number |
| Union remittance | A run, optionally one union | Fund-by-fund totals for that run, split into what's covered by the union's own settlement process and what still needs a check |
| QuickBooks package (QBD) | A run, on its own page | A versioned QuickBooks Desktop workbook for that run — recognition journal entry, cash settlement batch, and reconciliation — plus a PDF |
| Consolidated register | A date range | A company-wide rollup across every paid run in that range — per payee, by union fund, by cost, by representative |
| 1099 filing preview | A calendar year | Which recipients are on track for a 1099, who needs more information, and who falls under the threshold |
A run voided at the payroll provider
If Check voids a run, its tax calculation, filing, and cash requirement are all reversed — so any report asserting it settled would be false.
Greenroom refuses to export such a run rather than hiding it. The run stays in the picker, labelled "— VOIDED at payroll provider", and generating it returns a message naming the run and pointing at its detail page for the void details. The QuickBooks package page gives the same answer in a card under its own run picker — it used to render nothing at all below the picker for a voided run, which read as a blank page rather than a refusal.
That's deliberate: a run that silently vanished from the list would be indistinguishable from one that never happened, and anyone reconciling against a bank statement would be hunting a discrepancy with nothing on screen to explain it. Never silent in either direction.
A void is keyed on what the provider reported, not on the run's status. A run's status is yours to set and never flips itself on a void, so a voided run keeps reading Paid — which is exactly why the void has to be shown separately.
One more report lives on its own page rather than as a card here: the Physical-check register (/reports/checks), which lists every printed cheque handed to the printer for a run and its current lifecycle status. It's linked from a run's submit confirmation, and only exists where cheque printing is switched on.
There's no standalone payee report — a payee's numbers show up as rows inside the reports above. See Payee Reports for exactly where to look.
Why a run might not show up
The Payroll register, Union remittance, and QuickBooks package run pickers only list runs that have moved past your team's internal review — status Approved, Processing, Paying out, or Paid. A run still sitting in Draft or In review won't appear yet; finish getting it approved first.
The Consolidated register and 1099 filing preview go a step further and only draw from runs that have actually reached Paid — a run that's approved or still processing isn't in the books yet as far as those two reports are concerned. If a run is in the in-between "Paying out" state — submitted but not yet confirmed paid by Check — a collapsible More details — Paying out panel appears above either of those two reports listing that in-flight money by run, purely for visibility; it's explicitly excluded from the paid totals in the report itself until Check confirms the run as paid, and the panel doesn't appear at all when nothing is currently in that state.
If any picker comes up empty, the card tells you why instead of showing a form — usually "No approved runs yet" or "No paid runs yet."
Getting your data out
The four reports that generate inline on this page each have a Download CSV button in their top-right corner — that's the only export format for those four, and nothing gets saved to a report library for later. If you need the same report again, regenerate it.
Two exceptions live outside that inline CSV pattern. The QuickBooks package produces a full Excel workbook plus a PDF from its own page, not a CSV from this one — see QuickBooks Package (QBD). And a proper printable PDF for union reports exists too, but it's generated from inside a payroll run's own Union Reports step, not from this Reports page — see Union Reports for how the two relate.
Read-only, no drill-down
On the four inline reports, tables don't expand and their rows aren't links — you can't click a payee or a run from a report to jump to their record. If you need to open a specific run, use Payroll History; if you need a specific payee, use the Payees list. The QuickBooks package works differently: its own page keeps a history of every package generated for a run, and those rows carry real actions (download, mark posted, void) — see QuickBooks Package (QBD).
Next steps
See Payroll Reports for the payroll register, QuickBooks Package (QBD) for the accounting export, Union Reports for fund remittance, Company Reports for the consolidated register and 1099 preview, or Payee Reports for where an individual payee's numbers actually live.