- Sub-account
A sub-account is an account nested under a parent account so that detail can be tracked without losing the parent's total. Transactions post to the sub-account. The parent shows the sum of its sub-accounts and nothing else. One chart can therefore produce a short report at the parent level and a detailed report at the sub-account level, from the same entries.
The hierarchy exists to answer one question: how much detail should the books carry? Too little, and a manager cannot see which cost moved. Too much, and the person coding transactions makes more mistakes than the extra detail is worth. Parent and sub-accounts let you choose the answer for each area of the business instead of for the whole chart at once.
Structure
The generic chart below has one parent with three sub-accounts. Payroll (6100) never receives a transaction directly. Salaries and Wages, Payroll Taxes, and Employee Benefits do, and 6100 reports their sum. The numbering follows the convention from the account numbering page: the parent takes the round number, and each sub-account takes the next ten within it.
| Row | Account | Number | Type | Purpose |
|---|---|---|---|---|
| 01 | Cash - Operating | 1000 | Bank | Main operating checking account |
| 02 | Payroll Liabilities | 2100 | Other Current Liabilities | Wages and taxes withheld, not yet paid out |
| 03 | Service Revenue | 4000 | Income | Fees earned from clients |
| 04 | Payroll | 6100 | Expenses | Parent. Reports the sum of 6110 to 6130; nothing posts here |
| 05 | Salaries and Wages | 6110 | Expenses | Sub-account of 6100. Gross pay for the period |
| 06 | Payroll Taxes | 6120 | Expenses | Sub-account of 6100. Employer share of payroll taxes |
| 07 | Employee Benefits | 6130 | Expenses | Sub-account of 6100. Health, retirement match, and similar |
| 08 | Rent | 6200 | Expenses | Office lease |
| 09 | Office Supplies | 6300 | Expenses | Consumables; not split, because nobody asks |
The chart above started as a flat one. The change that turned it into a hierarchy is small, and it shows the rule in action: one blended line became a parent with three children, and one line that nobody questions stayed as it was.
- 6100Payroll Expenseone blended line
- 6100Payrollparent, no direct postings
- 6110Salaries and Wagessub-account
- 6120Payroll Taxessub-account
- 6130Employee Benefitssub-account
- 6300Office Suppliesleft flat on purpose
Two rules keep a hierarchy honest. First, a parent with sub-accounts should not receive direct postings. If it does, the expanded report shows an amount on the parent line that none of the children explain, and the reader has to guess what it is. Second, every sub-account under a parent should share the parent's type. A sub-account of an expense parent cannot be an asset. Most accounting systems enforce the second rule; the first one is a habit you keep yourself.
Recording
Posting to a sub-account looks exactly like posting to any other account. The hierarchy changes nothing about the entry. It changes only where the amount appears on the report afterwards. Figures are illustrative.
| Account | Debit | Credit |
|---|---|---|
| 6110Salaries and Wages | 18,400 | |
| 6120Payroll Taxes | 1,410 | |
| 6130Employee Benefits | 2,150 | |
| 2100Payroll Liabilities | 21,960 | |
| Totals | 21,960 | 21,960 |
Three sub-accounts, one entry. The parent, 6100, is not on the entry at all; it will show 21,960 on the report because its children add up to that.
The entry above is what a payroll run looks like once the split exists. A flat chart would record the same 21,960 as a single line to Payroll Expense. Nothing is wrong with that entry. It simply throws away the fact that 2,150 of the total was benefits, and no later report can recover it.
| Account | Debit | Credit |
|---|---|---|
| 2100Payroll Liabilities | 2,150 | |
| 1000Cash - Operating | 2,150 | |
| Totals | 2,150 | 2,150 |
Settling the liability touches no expense account. The cost was recognized in Entry 1; this entry only moves cash.
Notice what the second entry does not do. It does not post to 6130 again. The expense belongs to the period the employees worked, and it was recorded then. Paying the invoice later is a separate event that reduces cash and reduces the liability. Keeping those two events apart is what lets the sub-account total mean "benefits cost for the period" rather than "benefits paid this month".
Reporting
The same entries produce two reports. The first is what the owner reads on a Monday morning. The second is what the owner opens when the payroll line looks high.
| Service Revenue | 64,000 |
| Operating expenses | |
| Payroll | 21,960 |
| Rent | 4,500 |
| Office Supplies | 380 |
| Total operating expenses | 26,840 |
| Net income | 37,160 |
Example figures.
| Service Revenue | 64,000 |
| Operating expenses | |
| Payroll | |
| Salaries and Wages | 18,400 |
| Payroll Taxes | 1,410 |
| Employee Benefits | 2,150 |
| Total Payroll | 21,960 |
| Rent | 4,500 |
| Office Supplies | 380 |
| Total operating expenses | 26,840 |
| Net income | 37,160 |
Example figures.
The totals agree to the dollar. That agreement is the whole point of the hierarchy: the detailed report is not a second set of books, it is the same books read one level deeper. When the two reports disagree, something posted directly to the parent, and the fix is to move that entry into a sub-account.
Insight
- 01Payroll rose 12 percent this year. Was it headcount, a tax rate change, or the new health plan? One blended payroll line answers with a single number.
- 02The benefits renewal quote is 20 percent higher. What did benefits actually cost last year? Without a sub-account, the answer requires re-reading twelve months of invoices.
- 03A lender asks for salaries separate from employer taxes. Can the report be produced from the books, or does it have to be rebuilt in a spreadsheet?
The temptation runs in one direction. Owners rarely regret a split they made for a question they had. They often regret a hundred sub-accounts created "in case", each holding a few hundred dollars, none of them read. The test is not whether the detail could be useful. The test is whether it is used.
No industry guide links here yet.
- Principles of Accounting, Volume 1: Financial Accounting, Chapter 3 · OpenStax, Rice University
Every industry guide applies this rule to its own accounts: where a restaurant splits food cost from beverage cost, where a contractor splits labor by job phase, and where a clinic keeps one line because nobody asks for more. Browse the industry guides to see the split that fits your business, then test your own chart.
Frequently asked questions.
How many levels of sub-accounts should I create?
Two levels covers most small businesses: a parent and its sub-accounts. A third level is worth it only when a manager reads reports at that depth. Beyond three, the chart becomes harder to code correctly than it is useful to read.
Should every account have sub-accounts?
No. Split an account only when the detail answers a question someone asks every month. An account that nobody reads at the detailed level costs coding effort and adds no information.
Can I post directly to a parent account?
Most systems allow it, but avoid it. Once a parent has sub-accounts, every transaction should land in one of them, so the parent total equals the sum of its children and the expanded report has nothing unexplained.
The principles are easy. Applying them is the work.
This guide is the theory. The free demo helps you review a real QuickBooks Online chart with a score, structural diff, and prioritized cleanup plan.
- +Score the chart across the health dimensions
- +Compare structure against a reference pattern
- +Prioritize cleanup work before changing books
- +Review recommendations before anything is applied