GlassJar Accounting Software

fas fa-people-roof

Chart Of Accounts List

A list of all accounts used in the ledger, with their codes and descriptions.

What’s Included:

Select An Option To Add This Report To Your Account

Standard Date Range

— OR —

Comparison Date Range

Choose a default date range. You can further customize the date range once you add this report to your account.

accounting report

#8F58EE

#FAF5FE

### Who It’s For
The Chart Of Accounts List is for anyone who needs a clean, readable map of how your bookkeeping is organized in GlassJar. It’s especially useful for bookkeepers, accountants, and owners who want to understand what each account is for before they start posting, correcting, or reporting. If you’ve ever wondered, “What category does this actually belong in?” this is the place to start.

### What It Does
This report gives you the full chart of accounts your business uses, laid out in a clear list. Instead of hunting through settings or past reports, you get a single reference you can trust when coding transactions.

What you can learn from the report:

  • All accounts currently set up in your chart, so you can see what exists before you add anything new
  • How accounts are organized (for example, assets, liabilities, equity, revenue, and expenses)
  • The account names you’ll see when entering transactions, making it easier to code consistently
  • What you can and can’t report on, because your reports are only as accurate as your accounts
  • A quick way to spot missing accounts when a payment or invoice doesn’t fit anywhere

### Use Cases

1. Fixing “Where Should This Go?” Coding Confusion
A bookkeeper gets a batch of vendor invoices and notices that two different line items are being posted to the wrong expense accounts. They pull the Chart Of Accounts List and compare the current account names to how the company expects these costs to be categorized. Within minutes, they identify the correct accounts and update the coding so the reports match the actual intent of the invoices. No more guessing, no more rework later.

2. Preparing a Clean Month-End Close
An accountant runs month-end close and flags a few totals that don’t line up with expectations. Before chasing transaction details, they open the chart of accounts list to verify the account structure is correct. If they see an account that should exist but doesn’t, or an account that’s duplicated with slightly different naming, they can correct the setup first. That prevents chasing symptoms while the root cause stays hidden.

3. Reorganizing Accounts Without Breaking Reporting
A growing business decides to separate operational costs more clearly. They review the Chart Of Accounts List to confirm which existing accounts will be kept, which will be retired, and which new accounts need to be added. Because the report shows the current structure in one place, they can plan changes carefully and avoid creating overlapping accounts that lead to confusing totals. Teams often find this step keeps the cleanup from turning into a mess.

4. Auditing Consistency After Staff Changes
After an admin or junior accountant leaves, the team inherits their past coding habits. A senior accountant uses the Chart Of Accounts List to check whether the chart still reflects the intended structure and naming. If they see accounts that were created “just for convenience” and never standardized, they can consolidate. One of the first things they do is look for accounts that look right on paper but don’t match how transactions were categorized. This prevents new staff from repeating the same errors, even when the work looks fine at first.

5. Supporting Spreadsheet-To-Software Reconciliation
When a company migrates records from a spreadsheet, they need to map old categories to GlassJar accounts. The Chart Of Accounts List acts like the mapping reference. Someone can align “Office Supplies,” “Software,” and other legacy categories to the exact GlassJar accounts, then verify that every transaction has a home. This makes the migration smoother, and it reduces those annoying follow-up corrections that pop up after everyone assumes the mapping is done and done.