Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
Use the chart of accounts for the economic nature of a transaction, class for a reusable segment such as department or program, location for the transaction-level site or channel, project for one customer engagement, customer for the commercial relationship, and custom fields for governed supplemental attributes. Confirm current plan limits, assign one business question to one dimension, test every transaction type and report, and prohibit duplicate coding across dimensions.
Best for: finance teams designing departmental, location, project, customer, or operational reporting in QuickBooks
What this guide covers—and what it does not
The page owns one search intent: choosing and governing QuickBooks tracking dimensions for reliable management reporting. Related jobs have their own canonical guides so you can move between them without mixing product selection, setup, troubleshooting, and migration advice.
- This page owns analytical-dimension selection, naming, permissions, completeness, reporting tests, and cleanup.
- The Projects guide owns project operations; the reports guide owns report execution and interpretation.
- Dimensions do not replace separate books for legal entities or a subledger for operational detail QuickBooks cannot govern.
Evidence-first workflow
Design a reporting dimension from question to close
Start with the management decision and required report, then work backward to the smallest reliable field.
- 1
Question
State the decision, grain, period, owner, and report that the dimension must support.
Evidence: The field has one defined business purpose.
- 2
Choose
Select account, class, location, project, customer, item, or custom field by its accounting behavior.
Evidence: No existing dimension already answers the question.
- 3
Govern
Define values, hierarchy, naming, creation rights, required transactions, and inactive-value procedure.
Evidence: A controlled data dictionary exists.
- 4
Test
Post representative sales, expenses, bills, payroll, journals, imports, credits, and integrations.
Evidence: Entry screens and reports preserve the intended value.
- 5
Close
Review unassigned, invalid, duplicate, and changed values and reconcile management reports to the ledger.
Evidence: Reported totals tie to financial statements.
Decision control
Choose from evidence, not a feature list
Use the same four gates for choosing and governing QuickBooks tracking dimensions for reliable management reporting: define the job, surface constraints, choose the smallest workable option, then verify the records.
Select the dimension by the question it answers
Do not encode the same meaning in account names, classes, locations, and custom fields merely to make it visible everywhere.
| Your situation | Direction | Why |
|---|---|---|
| What happened economically? | Chart of accounts and item mapping | Revenue, expense, asset, liability, and equity nature belongs in ledger classification. |
| Which department, fund, program, or product line? | Class where supported | A reusable segment can support income-statement analysis across transactions. |
| Which store, branch, property, or channel? | Location where supported | Location generally applies to the transaction as a whole and supports site-level reporting. |
| Which customer engagement? | Project | Projects group engagement income, cost, time, and profitability. |
| Which supplemental attribute or approval code? | Custom field | A governed field can carry non-ledger information when reporting and form availability meet the need. |
Map each business question to one authoritative field
List the required reports and decisions: statutory financial statements, department P&L, location margin, donor program, customer/project profitability, sales representative, contract, or approval reference. Record the required grain and whether a value belongs to a full transaction, individual line, master record, or project.
Create a decision matrix showing field purpose, allowed values, owner, required transaction types, plan availability, limits, imports, integrations, and reports. If one question cannot be answered without combining several inconsistent fields, redesign before migration.
Verify product limits and form/report coverage
QuickBooks Online plan limits and feature availability change. Intuit currently documents different availability and limits for classes, locations, custom fields, users, and chart-of-accounts entries. Confirm the live account rather than relying on a historical comparison.
Test line-versus-header behavior, bills, expenses, invoices, credits, payroll, journal entries, bank feeds, recurring transactions, imports, mobile, apps, and each required report. A field that appears on one form may not survive every data path or report.
Govern values and prevent unassigned activity
Use stable codes and names, prohibit ambiguous “other” or person-specific values without policy, limit creation and merging, and make obsolete values inactive only after open transactions and integrations are addressed. Maintain parent-child hierarchy where the product supports it and the report requires it.
Review unassigned values, invalid combinations, duplicates, unexpected new values, and changes to historical transactions at least monthly. Use warnings where supported but do not assume a warning forces correct line-level coding.
Clean dimensions without rewriting history blindly
Export the value lists and transaction detail, map old to approved values, identify closed and reconciled periods, and test the effect on every management report. Separate spelling duplicates from genuine historical distinctions.
Use controlled batch changes only after preserving the original report and approval. Reconcile post-change financial totals and each dimension report; document values merged, inactivated, retained, and rejected.
A tracking dimension is a management-reporting choice. It does not create legal-entity, donor-restriction, trust-account, tax, or statutory separation on its own.
Completion checklist
Do not call the decision or setup complete until someone independent of the initial change can verify these items.
Frequently asked questions
What is the difference between class and location in QuickBooks?
A class commonly represents a reusable segment such as department or program and can be assigned at supported line or transaction levels; a location commonly represents the whole transaction site or channel. Test current product behavior.
Should each project be a class?
Usually not when the Projects feature supplies engagement-specific income, cost, and profitability. Reserve class for a reusable reporting segment unless a documented design requires otherwise.
Can I use classes for separate companies?
A class does not create separate legal books, balance sheets, permissions, tax records, or bank reconciliations. Use separate company records and an approved consolidation process where entities require separation.
Still comparing adjacent tasks? Use the complete guide library to find the one page that owns your intent.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.