QuickBooks Bureau Payroll supports many ledgers, one accounting link at a time
QuickBooks Bureau Payroll can post pay run journals to a range of ledgers, though only one accounting integration can be active at any time.
For UK payroll bureaus, one question keeps surfacing: how does QuickBooks Online Bureau Payroll hand its journals to a client whose books sit outside QuickBooks? We reviewed the accepted answer, maintained by Intuit. The connection exists, it reaches more ledgers than the product’s name suggests, and it carries a limit that is easy to miss.
A payroll that must talk to many books
Bureau Payroll is the UK offering for practices that process salaries for many clients under one roof. Each client keeps its own ledger. Often that ledger is not QuickBooks: Xero and FreeAgent are common choices, and some clients sit on larger platforms.
The symptom behind the question is familiar to any bureau. A pay run is finalised, payslips go out, and no journal ever reaches the client’s books. The cause is usually structural rather than a fault: nobody linked the two systems, or the link points at the wrong organisation. Payroll files to HMRC on its own schedule; the journal is how the ledger learns what payroll did. Without the link, the client’s accounts drift out of date every month.
One active connection of each type
The accepted answer opens with the rule that matters most. You can hold one accounting integration, one payments integration and one timesheet integration at the same time, but only one of each. A practice cannot keep two accounting links live for a single client company. Moving a client to a new ledger means retiring the old connection first.
The integrations screen makes the position easy to audit. Filters at the top narrow the list by type, and a counter shows how many integrations are enabled. When a new connection refuses to take, that screen is the first place to check.
Ledgers on the supported list
The list is longer than many users expect. Beside QuickBooks Online, the payroll links to Xero, FreshBooks, Zoho Books, FreeAgent, Microsoft Dynamics 365 Business Central, Oracle NetSuite and NetSuite OneWorld, Access Financials, and Quickfile.
Xero carries a caveat. The link needs at least the Standard Payroll tier on Xero’s side, and whoever authorises must hold admin access there. Nothing in the guidance covers packages outside the list, so anything else means journals go across by hand.
The connection runs through each client company
The settings live inside each client payroll company, not at practice level. Open the client, select the gear icon, choose Payroll settings, then Integrations. Pick the ledger from the dropdown, select Add, then Connect.
From there the payroll hands you to the provider’s own site. You select the organisation and approve data sharing with the payroll. Wording differs by provider, but the shape is identical: choose the books, grant the permission, and return to payroll. The QuickBooks Online link follows the same pattern, with the organisation chosen inside QuickBooks itself.
Journals, accounts, and the double finalise
The QuickBooks Online connection adds a step that is easy to skip. Before the first export, bring the chart of accounts across: in Payroll settings, open Chart of Accounts, select Import Accounts, and tick the accounts payroll should post to. Then map the payroll lines to those general ledger accounts. Skip this and the journal has nowhere to land.
Export happens at finalisation, with a quirk worth knowing. Open the pay run and select Finalise Pay Run. In the dialog, confirm that journal export is ticked; a pencil icon lets you switch it on if it is off. Choose to export immediately and confirm. Then, back on the pay run screen, finalise once more, and the journal moves across.
A manual export route for pay run journals is also documented. That matters when a run was finalised before anyone connected the systems, since the automatic handoff happens at finalisation.
The takeaway for bureau practices
The fix here is procedural, not technical. Authorise the link inside each client company. Map the accounts before the first finalised run. Respect the one-per-type limit when a client changes ledgers, and treat the integrations screen as the first diagnostic whenever journals fail to appear. The payroll speaks to more packages than its branding suggests; the work lies in getting each connection authorised and mapped.