PeoplePay runsCompliance
Leavers are never missed on the FPS
If you recorded a leaving date after that employee’s final pay run had already gone to HMRC, the cessation had no way of reaching them. HMRC carried on treating the employment as live and kept issuing tax codes against your PAYE scheme. That is now fixed, and it corrects itself without you doing anything.What’s new- An employee stays on your pay run list until their leaving date has actually been reported to HMRC, rather than dropping off the moment you record it.
- A leaving date recorded too late for its own pay run is picked up on the next one, as a zero-value payslip carrying only the cessation.
- A new Leaver on this pay run alert on the alerts step shows who is being reported as leaving, with the leaving date. Employees who left before the pay period started are raised as a warning, so a late cessation is easy to spot.
- Cancelling a leaving date is now blocked once it has reached a finalised payslip, so your records and HMRC’s cannot drift apart.
APIReports
Reports API (Beta)
Your payroll data is now queryable over the API. Instead of downloading fixed reports, you describe the report you want as a single JSON definition — which dataset, which columns, how to filter, group, and aggregate — and run it whenever and however you need: on demand, as a large export, or on a recurring schedule. It’s in beta, so build against it and tell us what’s missing.What’s new- Query datasets across the whole platform — payslips, payslip lines, payroll runs, statutory payments, court orders, holiday, payments, pensions, journals, invoices, and clients — with a field catalog that tells you exactly what each dataset can filter, group, and aggregate.
- Run reports synchronously and get the rows straight back, or queue CSV/JSONL exports of up to 5,000,000 rows behind a download link.
- Save a report definition once and reuse it everywhere — re-run it by ID, export it, or put it on a cron schedule delivered by signed webhook or email.
- Relative-period filters (
@currentWeek,@currentMonth,@currentTaxYear) that resolve at run time, so a scheduled “this month” report never needs editing. - A full run history that doubles as an audit trail, including access to sensitive fields.
/v1/report and appears as the Reports group (badged Beta) in the API reference. Start with the Reports API overview — it walks through datasets, the report definition document, exports, and scheduling. Feedback to hello@flowpayroll.ai.Pay runsSettings
Payroll journals
Your finance team no longer needs to build payroll journals by hand. Flow now generates a balanced double-entry journal from every pay run automatically — mapped to your chart of accounts, split by department or cost centre, and ready to export to Xero or any other accounting system.What’s new- A journal is generated in the background as soon as payslips are calculated, and it locks together with the pay run — there is no separate finalise step.
- Journal templates in Settings → Journals define your nominal code mappings, control accounts, and cost splits by department, cost centre, NI category, or any tag group.
- Import existing mappings from Sage, Xero, Staffology, IRIS, and other systems, and move templates between companies — particularly useful for bureaux managing multiple entities.
- Every journal is balance-checked before it locks, and exports as Xero Manual Journal CSV, generic CSV, or PDF.