Workplace pension setup stalls in QuickBooks Advanced Payroll
UK payroll teams report stuck pension submissions and unclear alert statuses when connecting QuickBooks Advanced Payroll to workplace pension providers.
UK payroll teams using QuickBooks Online Advanced Payroll are running into a familiar tangle when they set up workplace pensions. The accepted community answer points to PensionSync as the main route, but it also surfaces a fixed list of supported providers and a dashboard that can look busy if you do not know which column to read first. What looks like a submission failure is often a scheme waiting for authorisation or an action flag sitting inside the payroll data.
The symptoms users describe
The reports cluster around a few common signs. A pension scheme may show as connected even though no submission data has left. A required action may sit unnoticed until a payroll deadline is close. Newly eligible employees do not appear in the expected batch, or changes to qualifying earnings do not sync back into QuickBooks. Users also describe selecting a scheme and only later realising that the choice cannot be swapped for another provider.
These are usually workflow and status problems rather than a complete outage. The thread makes clear that the issue is often visible only inside the PensionSync dashboard, not in the main payroll run, which is why teams can miss it until a provider rejects a submission.
Affected product and provider scope
The guidance applies to QuickBooks Online Advanced Payroll and Bureau Payroll in the UK. PensionSync is the digital connection that automates pension reporting, but it does not work with every provider. The supported list is limited to NEST, Aviva Company Pension, Smart Pension, People’s Pension, and NOW Pension.
One hard constraint stands out. Once a pension scheme is selected, you cannot switch to another. That means the initial provider choice matters, and a wrong selection can leave a team waiting for data that will never arrive through the chosen connection. If a provider is not on the supported list, the manual scheme setup route still exists, but it will not deliver the same automatic submissions, opt-out imports, or enrolment updates.
Reading the Schemes tab
Most of the stuck work becomes clearer in the Schemes tab. This view lists all pension schemes in one place, and each column answers a specific question. The provider name and employer name identify the scheme. The employer ID is the reference assigned by the pension provider. Scheme status shows whether the provider has authorised data to be sent and received through PensionSync.
The remaining columns track the submission itself. Submission type tells you whether enrolment or contribution data has been sent. Submission date shows when the last attempt was made. Submission status confirms whether the provider accepted the data. Required actions is the column that matters most when something is waiting, because it flags authorisation gaps, errors to resolve, or other outstanding work.
Sorting the Required Actions column brings every scheme with open work to the top of the list. That single step is often enough to show why a pension submission has not moved.
What the activity alerts mean
The Activities tab gives a closer view of each scheme. Four colour-coded alerts appear there, and they map to the likely workflow problem. A green alert means a submission was accepted or a new scheme was added successfully. An amber alert usually means an action may be required, often a payroll update to clear an error. A blue alert is informational. A red alert is a genuine error that needs attention before data can move.
A common pattern in the thread is that users see an amber alert, assume the submission failed, and then search for a provider-side problem. In many cases the fix is inside QuickBooks itself, because the payroll data needs to be corrected before PensionSync can complete the submission.
What actually clears the backlog
The accepted answer resolves the confusion by turning the dashboard into a short checklist. First, open the Schemes tab and sort by Required Actions. That exposes the schemes that are blocked. Second, authorise any scheme that is waiting for provider authorisation. Third, treat every amber alert as a prompt to review and update the payroll data behind the submission.
Changes to scheme details, including qualifying earnings, must be made directly with the pension provider before they sync into QuickBooks. If you use NEST, the provider can collect contributions automatically and update employee details such as opt-outs, ceased memberships, and contribution changes within payroll. For other supported providers, PensionSync imports the details after the provider side is correct.
The practical outcome is that most stalled workplace pension work clears once the Required Actions column is sorted, authorisation is completed, and any amber payroll errors are resolved. The dashboard is not simply a status page. It is the place where the block is named, and the accepted guidance in this thread says to read it before chasing the provider.