Bureau Payroll Activity Feed: Statuses, Filters and Fixes
How the QuickBooks Online Bureau Payroll activity feed surfaces failed pay runs across clients, and the steps that clear each warning.
Practices that handle payroll for multiple clients in QuickBooks Online Bureau Payroll keep hitting the same wall. A submission fails or a journal refuses to export, and nobody notices until a client asks about it. The accepted answer to a recent community question points to a single screen as the remedy: the activity feed. We reviewed that answer, and the guidance Intuit attached to it, to set out what the screen covers and where the fixes live.
One screen for every client pay run
The feed gathers pay run activity for every client a bureau manages into a single list. It is more than a history view. Each entry carries a status, an icon and an action, so the screen doubles as a triage queue. Failures stop hiding inside individual client files, which is the core complaint the thread responds to.
Filters shrink the list before you scan it
Five filters control what appears. Brand narrows the view to one part of a practice. Business name or ID pulls a single client’s activity. Activity type separates journals, notifications, pay runs, report packs, pensions and the EPS and FPS returns sent to HMRC. Payroll manager isolates one person’s workload. Date switches the month in focus.
Our advice is to filter before you scan. Set the month first, then the activity type. A list of every pay run for every client is noise; a list of this month’s FPS items is a checklist. Teams that split clients between managers can filter by manager and clear a personal queue.
Statuses sort the work into five groups
Every activity lands in one of five groups. Errors holds items that need action because something failed. Overdue lists pay runs past their due date. In progress covers pay runs created but not yet finalised. Upcoming shows what is coming, which helps with preparation. Complete holds finished activity and finalised runs.
Each group shows the same columns: the activity, a status icon, the business, the payroll manager, a date and an action. Colour carries most of the meaning. Green marks something done, orange marks something scheduled, red marks an error. The icons cover events such as journal exports, payslip publication, HMRC submissions, pension submissions, automated pay runs, approvals, declines and warnings.
Two details in those columns trip people up. The payroll manager shown is the person responsible for the client, not a record of who can open the file. The date is sometimes a due date and sometimes a date paid; hover over the information icon beside it to confirm which.
Where do failures actually collect?
The Errors group concentrates most of the pain. Per the accepted guidance, failures here involve report packs, journal exports, payslip notifications, EPS, FPS and pension files. That list covers nearly every step after a pay run is approved, so a red icon can mean several things. Selecting a group expands its rows, and each row carries its own action.
There is a practical order to work in. Clear Errors first, because failed submissions carry deadlines and the Overdue group grows while errors wait. Move to Overdue next, then review In progress before finalising anything.
The action column is where the fix starts
The feed repairs nothing by itself. What it does is put the fix one click away. The action column changes with the activity, so the path from a failure to a resolution stays on one screen. That is the substance of the accepted answer: open the feed, expand the group, read the row, take the action offered.
Downloading the feed for the record
You can export the list as well. The download earns its keep at month end. Save a copy before a review or a client meeting and you hold a record of what ran, what failed and when it cleared. It also gives you a baseline to compare against once the busy period passes.
A routine that keeps the queue short
When the queue keeps overflowing, cadence is usually the problem rather than the screen. One workable routine: open the feed each morning, filter to the current month, clear every red row, then clear Overdue. Review In progress before you finalise anything. Skim Upcoming weekly to plan around peak dates. Short, frequent visits beat a weekly deep scan, because errors left alone age into overdue items.
The feed has limits worth knowing
The screen reports status; it does not explain root causes. It will tell you an FPS failed, not why it failed. Treat it as a dashboard rather than an audit trail. The repair still happens in the pay run, the submission or the export, wherever the red icon first appeared.