Skip to main content

QuickBooks Account Naming Conventions for Journal Entry CSV Imports

Nothing uploadedTested up to 200 MB

Learn how to write parent accounts and subaccounts in QuickBooks journal-entry CSVs, including the Parent account: Sub Account format.

Published: 2026-09-231 minCheck QuickBooks account names
Data workflow illustration for QuickBooks Account Naming Conventions for Journal Entry CSV Imports

The Account Name column in a QuickBooks journal-entry import must identify the account QuickBooks should post to. Parent accounts are simple names. Subaccounts need their hierarchy, separated by a colon.

Parent account and subaccount format

Use this pattern for a subaccount:

Parent account: Sub Account

Examples:

| Account type | CSV value | | -------------------- | --------------------------------- | | Parent account | Sales | | One subaccount level | Expenses: Merchant Fees | | Deeper hierarchy | Expenses: Fees: Card Processing |

QuickBooks can reject a journal line when only the subaccount is supplied. Including the parent path gives the importer the account hierarchy it expects.

Do not leave an empty segment such as Expenses: : Fees. The preparer flags empty colon-separated segments before it creates the output CSV.

Match the names that exist in QuickBooks

Correct punctuation does not create an account. The name still needs to correspond to the account structure in the QuickBooks company. Treat the CSV as a reference to your chart of accounts rather than a place to invent new hierarchy casually.

When the source system stores separate parent and child fields, combine them into the QuickBooks Account Name representation before import. When it already exports a complete path, map that source column directly.

A practical mapping example

account-mapping.csv

Source GL, QuickBooks Account Name4000, Sales6105, Expenses: Merchant Fees1010, Bank: Operating Account

The QuickBooks Journal Entry CSV Preparer validates the hierarchy syntax while it also checks journal dates, debit/credit cells, and per-journal balance. It does not guess which account a GL code should represent; you choose the mapping from your source data.

Keep the hierarchy readable

Use stable names that mirror the chart of accounts. Avoid unnecessary whitespace around the colon, and review any account path that changed in the source system before importing recurring journals.

quickbooks-journal-entry-csv-preparer

See the transformation

Awkward source headers become import-ready columns.

Rename the columns you need while keeping every value under the correct header.

cust_idcustomer_id
given_namefirst_name
mailemail

✓ Values stay with the right column