Mapping General Ledger Accounts in QuickBooks Advanced Payroll

A short question keeps reappearing on the UK payroll boards: how do you map general ledger accounts in QuickBooks Online Advanced Payroll? The reply the community marked as the accepted answer comes from the vendor’s own payroll team. It reads less like a fix and more like a map of the machinery. We have condensed it here, because that map explains why a pay run can post somewhere nobody intended.

Where do you set the mappings?

Everything sits inside Payroll Settings, and the path is short:

1. Open the gear icon in QuickBooks Online.
2. Select Payroll Settings.
3. Open the General Ledger section.
4. Start with the default account mappings, then move to the category-level mappings beneath them.

One prerequisite shapes the whole exercise. The software can only map to accounts that already exist in your chart of accounts, so build the chart first and map second. Primary accounts are required, and the system uses them by default. Location-specific accounts exist purely as overrides, and they only apply to transactions that carry a location.

A four-level hierarchy decides every posting

The accepted reply describes a transaction hierarchy with four levels:

• Top level: default account mappings, the fallback for everything.
• Second level: mappings attached to pay categories, deduction categories, and expense categories.
• Third level: location-specific default mappings.
• Fourth level: location-specific mappings for pay, deduction, and expense categories.

Matching starts at the bottom and climbs. The most specific entry wins, so a location-level category mapping beats the location default, which beats the plain category mapping, which beats the top-level default. Nothing below the top is mandatory. Every level you leave empty simply hands the decision back to the level above it.

The default accounts, one by one

Before changing anything, it helps to know what each default slot controls. The reply lists them plainly:

• Payment account: commonly used as the payroll clearing account, it reconciles net pay against the money leaving the bank.
• Wages expense account: carries the gross wages for the pay run.
• Default payroll liability account: the catch-all for deductions with no dedicated liability account of their own.
• PAYE liability account: a clearing account for PAYE.
• Employer pension expense and liability accounts: track the employer side of pension costs and what is owed.
• Employee pension liability account: tracks what is owed on the employee side.
• National Insurance expense and liability accounts: track NI costs and the amounts due.
• Employee expenses account: records expenses processed inside a pay run. These do not count as wages.
• Employer liability expense and liability accounts: record employer liabilities raised against employees and the general amounts owed.

One line puzzles people more than the rest. Deductions without their own mapping all land in the default payroll liability account, which is why that balance can look larger than expected.

The category-first catch that blocks two mappings

Two of those slots can stay stubbornly unmappable. If you have never created categories for employee expenses or employer liabilities, the mapping screens have nothing to attach to, and the accounts cannot be assigned. The remedy sits upstream: create the missing categories in Payroll Settings, then return to the General Ledger section. The pattern generalises. Pay, deduction, and expense categories all have to exist before any of them can carry a ledger account.

Diagnosing a pay run that posts to the wrong place

When a journal surprises you, work the hierarchy from the bottom up. Check the pay or deduction category for its own mapping first. Then check whether the transaction carries a location, because location-level entries take priority the moment one is present. Only when every lower level stays silent does the top-level default apply.

The reverse also holds. If you want a particular cost separated in the books, attach an account at the category level rather than moving the top-level default, which would drag every other transaction along with it.

For reconciliation, the payment account is the anchor. Net pay should tie, through that clearing account, to the payment leaving the bank. Gross wages, employer costs, and liabilities then sit in their mapped slots for review.

The accepted reply offers no repair tool, because none is needed. The hierarchy is the whole story. Set the defaults once, override at category level where the books demand it, and reserve location-level mapping for sites that genuinely differ. Most mystery postings trace back to a mapping one level lower than the one the user was checking.