Concord CRM Chart of Accounts: Structuring the Ledger
Set up your Concord CRM chart of accounts once and get reports that reconcile: account codes, the five account types, hierarchy and the settings to fix first.
Eleven months into the financial year, the profit and loss report shows a 71% gross margin on a business everyone in the room knows runs at about 45. Nothing is missing and nothing was stolen. Server hosting, the single largest cost of actually delivering the work, was filed under an account that sits with administrative overheads, so it lands below the gross margin line instead of above it. The figure is arithmetically perfect and commercially useless.
That is what a badly structured Concord CRM chart of accounts produces: not errors, but correct-looking numbers that answer the wrong question. It is the one decision in CRM bookkeeping you cannot cheaply reverse, because everything downstream inherits it - every expense category, every default account, every automatically generated journal entry. Disclosure: we build and sell the accounting and bookkeeping module for Concord CRM described here, so weigh the article accordingly.
Why the Concord CRM chart of accounts is expensive to change later
An account is not a label. It is a foreign key that dozens of other records point at.
Expense categories map to GL accounts. Journal entry lines select an account per line. Bank accounts have a ledger counterpart. Default accounts in settings name specific accounts that automations reach for. When the module generates journal entries automatically for expenses, bills, payments, bank transactions, invoices and asset movements, every one of those entries hard-codes your structure into posted history.
So three different edits carry three very different costs:
- Renaming an account is cosmetic. Do it whenever you like.
- Renumbering an account breaks nothing in the data but breaks every printed report, every reference in a working paper and every habit your bookkeeper has. Cheap in software, expensive in humans.
- Changing an account’s type rewrites history. The posted entries do not move, but which report they appear on does. A twelve-month P&L that was right last week is wrong this week, and nobody gets an alert.
The last one is the trap, because double-entry bookkeeping will not catch it for you. Your Trial Balance stays perfectly balanced whether an expense sits in the right account or the wrong one - debits still equal credits. Balance is a guarantee that the entry is arithmetically sound, never that it is classified correctly.
The five Concord CRM account types and what a wrong one costs
The chart of accounts supports the five standard types: assets, liabilities, equity, revenue and expenses. The type is what decides an account’s normal balance and which report it lands on, so it is the field to be pedantic about.
| Type | Normal balance | Reports on | What a wrong type does |
|---|---|---|---|
| Asset | Debit | Balance Sheet | Spend classified as an asset never reaches the P&L, so profit reads high |
| Liability | Credit | Balance Sheet | Same disappearance, plus a balance sheet that grows for no visible reason |
| Equity | Credit | Balance Sheet | Owner drawings turn into operating costs, or costs vanish into equity |
| Revenue | Credit | Profit and Loss | Deposits and tax collected get counted as income you have not earned |
| Expense | Debit | Profit and Loss | Capital purchases hit one month instead of depreciating over years |
Four boundaries account for most misfilings:
- Client deposits taken before the work is done are a liability, not revenue. You owe either the work or the money back.
- Sales tax or VAT collected is a liability held on behalf of the tax authority. Keep it out of revenue, or your Tax Summary and your income statement will tell two different stories.
- Equipment above your capitalisation threshold is an asset, then an expense over its life through depreciation. The module’s asset workflows cover purchase, depreciation, maintenance and liquidation, and each of those movements needs an account to post against.
- A loan repayment is two things at once: principal reduces a liability, and only the interest portion is an expense. One payment, two accounts.
Account codes and hierarchy: designing the general ledger up front
Account codes are the sort order of your entire general ledger and the index your accountant navigates by. Use the conventional numeric blocks unless you have a specific reason not to:
1000assets2000liabilities3000equity4000revenue5000direct costs (the ones that scale with delivery)6000and above operating expenses
Two rules make the scheme survive growth. Step by ten inside a block, not by one - 4010, 4020, 4030 - because the account you will need to slot between two existing revenue lines next year is guaranteed to exist. And never encode a client, department or project into the account code. A ledger multiplied by your customer list is a ledger nobody can read, and it grows without bound precisely when the business is working.
Parents summarise, children get posted to
Hierarchical parent and child organisation is what gives you a readable report over a detailed ledger. The discipline is simple: post only to leaf accounts, and use parents purely to subtotal. An account that has both children and its own direct postings produces a report line whose total is genuinely ambiguous.
Two levels is enough for almost every small and medium business. Three is the ceiling before staff stop knowing where anything belongs and start guessing, which is worse than no hierarchy at all.
Before creating any child account, apply one test: can you name the report line it produces, and would you act differently based on it? Splitting software spend into fourteen vendor-named children gives you a P&L you have to squint at, and you can already pull that breakdown from the General Ledger report on demand. Aim for a P&L that fits on one screen - roughly 30 to 40 lines. Detail belongs in the ledger, not in the summary.
Mapping expense categories to GL accounts
Expenses in the module carry categories, and those categories map to GL accounts. This is the layer where the opening anecdote gets fixed or repeated.
The category is the vocabulary of the person filing the expense; the account is the vocabulary of the person filing the accounts. They should not be the same words. Someone submitting a receipt should see Client hosting or Team travel and never needs to know it lands in 5100 or 6400. That separation lets operational names stay meaningful while the ledger stays disciplined.
Three practical consequences:
- Many categories to one account is normal and good. Five travel categories can all post to one travel account. One category per account is how a chart of accounts reaches sixty lines nobody reads.
- Decide direct cost versus overhead at the moment you create the category, not at year end. The question is only ever: does this cost grow when we deliver more work? If yes it belongs in the
5000block, above the gross margin line. - Vendor bills use the same accounts. A cost entered as an expense with a receipt attached and the same cost entered as a vendor bill with a due date must reach the same place, or your A/P aging and your P&L disagree about the same supplier.
Concord CRM accounting settings to lock before the first entry
Central settings cover fiscal year, default currency, tax rates, default accounts, number prefixes and automation behaviour. Four of those are effectively one-way doors.
- Fiscal year defines the period boundaries for every report you will ever run, and for budgets built by account and period. Change it later and every comparative you have shown anyone is re-cut.
- Default currency is the base the Balance Sheet is expressed in. Multi-currency support and exchange rates handle foreign vendors and foreign bank accounts perfectly well, but the base currency is the measuring stick, not a preference.
- Default accounts are the quiet one. Whatever you set is what an automation reaches for when nothing more specific applies, and a wrong default never fails loudly - it posts, cleanly, hundreds of times.
- Number prefixes (
JE-,EXP-,BILL-,PAY-) should be set before the first document exists. A numbering series with two formats in it is a permanent footnote you owe your accountant.
Automation multiplies whatever structure you gave it
Optional automations generate journal entries for expenses, bills, payments, bank transactions, invoices and assets, and scheduled jobs process recurring entries, update overdue bills and recalculate balances. That is a real time saving, and it is also the reason to sequence the work carefully.
Manual bookkeeping produces mistakes at the rate a human makes them. Automation produces them at the rate the system runs. Switch it on after the chart is right, not before.
The safety net while you are still unsure is the posting workflow. Journal entries can be saved as drafts, posted when ready, and voided rather than deleted if they turn out wrong - which preserves the audit trail instead of quietly rewriting it. Run your first period in draft, read the Trial Balance and the General Ledger, and only then post.
One honest limitation worth stating: none of this validates your judgement. Import a bank statement by CSV, auto-match it, reconcile it, and the reconciliation will tie out perfectly against a P&L that still misclassifies half your costs. Reconciliation proves the data is complete. Only the chart of accounts decides whether it means anything.
The build order
Do it in this sequence, before a single transaction is entered:
- Write your numbering blocks on one page, gaps included, and agree them with whoever files your accounts.
- Set fiscal year, base currency, tax rates and the
JE-/EXP-/BILL-/PAY-prefixes. - Create parent accounts first, then only the children whose report line you can name out loud.
- Create bank accounts - checking, savings, credit card - alongside their ledger counterparts, in the right currency.
- Create expense categories and map each one to an account, deciding direct cost or overhead as you go.
- Set default accounts last, once every target account actually exists.
- Enter opening balances as one dated journal entry, not scattered across several.
- Post one full month with automation off. Run Trial Balance, P&L and Balance Sheet. Then switch automation on.
The rule that keeps it clean afterwards: if you cannot name the report line an account produces, do not create the account.