Skip to content

Export reports and payroll files

Every report on the platform exports as CSV, and several also offer Excel. Payroll Export builds the file your payroll software imports — a Sage 50 timesheet, a BrightPay hourly-payments file or a plain hours file — from approved arbitration records, or draft timesheets sent to Xero. PDF is the exception: the three pay reports print to PDF through your browser, and only form submissions are rendered as true PDFs.

What do I need before I start?

The role that owns the report. Exports carry the same data as the screen, so they carry the same restriction. The shift and payroll reports, and Payroll Export, need reports.view.payroll_summary — Admin and Manager. The Audit Trail export follows the Audit Trail. Agency Reports adds Agency Admin and Agency Coordinator, scoped to their own agency, and excludes Control.

Rows on screen. Most export buttons are disabled while the report is empty, and the ones that are not will tell you to generate a report first. Nothing exports a query you have not run.

A generated report, on Agency Reports specifically. Its Export button checks that a report exists before it does anything and shows Please generate a report first before exporting. if not.

How do I export a report?

  1. Open the report and set its date range and filters.
  2. On the pages that need it — Pay Summary, Pay Detail, Payroll & Charge, Absences, Agency Reports — press Generate (or set the filters, on Agency Reports) so the table is populated.
  3. Press the export control in the header. Depending on the report that is Export, Export CSV, or a CSV / Excel / Print trio.
  4. The file downloads immediately. Nothing is emailed, queued or stored — the export exists only in your downloads folder.

Which report gives me what?

Report CSV Excel PDF
Reports (shift and payroll) Yes, built in the browser No No
Payroll Export Yes — a Sage 50 timesheet, a BrightPay file or a generic hours file No No
Payroll Arbitration Yes No No
Pay Summary Yes Yes, as .xls Print only
Pay Detail Yes Yes, as .xls Print only
Payroll & Charge Yes Yes, as .xls Print only
Absences Yes No No
Check-call compliance Yes No No
Agency Reports Yes, built on the server Supported by the endpoint, not offered by the button No
SIA Compliance Yes Yes, a true .xlsx No
Right to Work Report Yes, built on the server No No
Audit Trail Yes No No
Form submissions Yes Yes, a true .xlsx Yes, a true PDF

So where does a PDF actually come from?

Two places, and only one of them is a real PDF file the platform produces.

The Employee Pay Summary after Generate, subtitled Pay breakdown grouped by employee from arbitrated shift data. Its header carries Hide Employees and then the three export controls side by side — CSV, Excel and Print — and none of them is greyed out, because the report has rows. In one row, a date-range box reading 7 Sep – 13 Sep 2026, All Sites and Generate sit beside a summary of 8, 31 shifts, 368.0h, £4926.40, and quick ranges from This Week to This Year. The table groups shifts under each employee, one line per shift with location, payroll group, PIN, date, start, end, hours, rate and pay, and closes each group with a shaded subtotal such as PRIYA RAGHUNATHAN TOTAL (4) · 48.00 · £633.60. A dark bar at the foot reads GRAND TOTAL · 8 EMPLOYEES · 31 SHIFTS · 368.00 · £4926.40. A checkbox list of the eight employees runs down the right.

Print, on the three pay reports. The button calls your browser's print dialogue against a page that carries a print stylesheet: the navigation, the header, every button and the employee sidebar are hidden, and table headers are given a grey fill that survives printing. From that dialogue you choose your printer, or Save as PDF. The layout and the page breaks are your browser's, not the platform's.

A form submission. Print or PDF, on a submission, opens a server-rendered PDF in a new tab, with the organisation's branding and a consistent layout. Choose PDF — Photos are reduced so the file is small enough to email — or Full quality PDF — Largest file. Best for printing and evidence. From the submissions list you can also select rows and choose PDF (zip) or Full quality PDF (zip), which renders each one and returns them zipped.

There is no PDF of the shift report, the payroll report, the pay reports, the absence report, the agency report or the audit trail. If somebody has asked for one of those "as a PDF", the honest route is Print and Save as PDF for the three that have a print layout, and CSV or Excel for the rest.

What is in each file?

Reports (shift and payroll). A flat CSV of the Shifts tab, one row per shift, named shift-report-<from>-to-<to>.csv, with the header Worker, Worker Type, Employee # / Agency, Site, Date, Start, End, Status, Scheduled Hrs, Actual Hrs, Start Variance (min), End Variance (min), Rate, Pay. Worker Type says whether the row is an employee or an agency officer, because an officer's Rate is a charge rate rather than a pay rate. It always exports the Shifts data even if you are looking at the Payroll tab, and it follows the Search box — you get the rows on screen.

The pay reports. The CSV opens with the report name, the date range and a generated-at timestamp, then the columns, then a subtotal row per employee and a grand total at the end, each under the Duration (hrs) and Pay (£) columns. The Excel button produces a styled HTML table saved with an .xls extension. Excel and most spreadsheet tools open it happily; anything expecting a genuine .xlsx workbook will not.

Agency Reports. This one is built on the server and is a formatted document rather than a table: banner headings for export information, an executive summary of key metrics, status analysis, agency performance, site utilisation and officer rankings, then a footer. The endpoint can also emit a genuine multi-sheet .xlsx workbook with the same content, but the screen only wires up the CSV button, and the endpoint refuses any other format with Only CSV and Excel formats are supported.

SIA Compliance. Export offers Excel (.xlsx) and CSV, both named sia-compliance-report- plus today's date. The CSV is written with a byte-order mark and with licence numbers forced to text so a spreadsheet cannot reformat them into something else.

Right to Work Report. One row per officer, built on the server, and recorded in the audit trail — see Check agency officers' right to work.

Payroll Arbitration. One row per shift for the range on screen, arbitration-<from>-to-<to>.csv, with expected, actual and arbitrated times, rates, totals, variance and notes — see Arbitrate shifts for payroll.

Audit Trail. Covered in full on Audit trail — twelve columns including the actor's IP address, capped at 10,000 rows.

Form submissions. CSV and Excel flatten the answers into columns and cap at 5000 submissions; when a file is cut short, the page says Export limited to the first … submissions. The PDF export renders each submission individually and is capped at 25, because each one fetches its attached media. Form Reports exports the same way and says Narrow the date range for the rest.

How do I export hours for payroll?

Payroll Export builds the file your payroll software imports, from the hours on Payroll Arbitration. It sits under Reports → Reports → Payroll Export and needs the same reports.view.payroll_summary permission as the pay reports.

  1. Arbitrate the period first, and clear any shift you do not want paid. The export reads arbitration records that are included in payroll and not dropped — whatever their status, so it can run before anything is marked paid. Shifts already marked paid are left out, so a second export does not repeat them; tick Include shifts already marked paid (to send a corrected file again) to bring them back.
  2. Open Payroll Export and set the Period. The range can be up to 366 days.
  3. Choose the Format:
    • Sage 50 Payroll timesheet — for File → Data Import → Import Sage Payroll Data → Timesheet Payments in Sage 50 Payroll. Saved as sage50-timesheet_<from>_<to>.csv.
    • BrightPay hourly payments — for Payroll → Import → Import Hourly Payments from CSV File, then Match Header Row. Each pay element is listed at the rate it was paid, so BrightPay pays what was approved here. Saved as brightpay-hourly_<from>_<to>.csv.
    • Generic hours by shift — a plain hours file for any other payroll. Saved as payroll-hours_<from>_<to>.csv.
    • Send to Xero (draft timesheets) — no file. Preview for Xero lists each employee's hours, with a Xero employee to match them to. Not matched employees are not sent. Sending asks first — You approve them in Xero. — and each employee then shows Sent as draft, Failed or Skipped. Earnings rates are set in Settings → Integrations, which is Professional.
  4. Press Preview (not for Xero). A table shows one row per employee — the payroll reference, Name, Shifts, hours under Basic, Overtime and BankHoliday, and Pay — with the totals above it, and any warnings.
  5. Check the warnings, then press Download.

Payroll Export, subtitled Approved hours by pay element, as the file your payroll imports. Preview, check the warnings, then download. Period reads 7 Sep – 13 Sep 2026 and Format is Sage 50 Payroll timesheet, beside Preview and Download buttons, with an unticked Include shifts already marked paid (to send a corrected file again) beneath. A note explains the Sage import menu path, that rows are keyed on the employee's payroll number, falling back to their employee number when that is blank, that the columns are your pay-element names, and that rates come from the employee record in Sage, not from this file. A yellow Check before you import box reads 1 shift is in this period already marked paid and left out. Include paid shifts only to send them again. The preview reads 8 employees · 30 shifts · 356.00 hours · £4768.00 above a table with columns Payroll No., Name, Shifts, Basic, Overtime, BankHoliday and Pay: PGG-P0101 Priya Raghunathan, 3 shifts, 36.00 basic hours, £475.20, down to PGG-P0108 Siobhan Mullan, 5 shifts, 60.00, £786.00. Every Overtime and BankHoliday cell is a dash.

In the Sage 50 file, each row is keyed on the employee's Payroll Number from their Payroll tab, falling back to their employee number where that is blank, so set payroll numbers to match Sage before your first export. The hours land under the pay-element names Basic, Overtime and BankHoliday; if your Sage elements are named differently, map them in Sage's import wizard. Rates are not in the Sage file — Sage applies its own. The BrightPay file uses the same reference as the employee's works number, and does carry the rate: each pay element appears at the rate it was paid, up to five per employee, and a warning names any more, to add by hand.

Agency officers are never in the file: their agency pays them. Downloading writes a record to the audit trail, and if that record cannot be written the file is not produced. Previewing records nothing.

The warnings to look for:

  • Identifier … is shared by … — their hours would merge into one row. Two employees have the same payroll number. Fix one before downloading.
  • Pay element "…" exported as "…" (Sage allows letters and digits only). A pay-element name was cleaned up for Sage.

No approved hours in this period. means nothing in the range has been arbitrated, or everything was dropped or left out of payroll.

If it goes wrong

What you see What it means
The export button is greyed out The report has no rows. Widen the date range or clear a filter.
Please generate a report first before exporting. Agency Reports only. Set the filters so the report runs, then export.
No data to export Same cause on the pay reports — the report ran but returned nothing.
Excel warns the file is not really .xls Expected on the three pay reports — the file is an HTML table with an .xls extension. Open it anyway, or take the CSV.
The PDF zip is refused for a large selection The PDF export is capped at 25 submissions per go. Narrow the selection.
The audit export stops at 10,000 rows It is capped there, with no warning in the file. Narrow the date range.
Export limited to the first … submissions. The form exports cap at 5000. Narrow the date range.

Last updated 2026-11-17