Bookkeeping lessons · Accounting glossary

How should a small business structure its chart of accounts?

A useful chart separates the financial questions you need to answer while keeping account choices clear enough for consistent daily entry.

Key takeaways: begin with the business’s actual activity; separate codes, names, classifications and software roles; avoid duplicate accounts for the same purpose; and review reporting needs before copying another business’s chart.

What does the chart organise?

The chart organises transactions into accounts so the ledger and reports can explain cash, obligations, ownership, income and costs.

A chart of accounts is more than a list of labels. It gives recurring events consistent destinations. Without that consistency, two people may record the same type of payment in different places, making comparisons unreliable. Too little detail hides useful differences; too much detail creates ambiguous choices and encourages inconsistent entry.

Start with the decisions a reader needs to make. A business may need to distinguish its bank accounts, financing obligations and major income streams. It may not need a different ledger account for every stationery supplier or every customer. Ask whether a proposed category will change a useful report or control, and whether someone can select it reliably.

Which parts of an account have different jobs?

The code locates an account, the name describes it, the classification explains its financial nature, and a software role guides permitted operations.

Four separate account attributes
AttributePurposeExample or caution
CodeStable, convenient reference1000 can identify cash, but the number alone is not accounting authority
NameReadable descriptionMain operating bank is more useful than Miscellaneous 1
TypeFinancial classificationAsset, liability, equity, income or expense
Posting roleMeaning for an application serviceCash/bank or receivables; assigning it does not create a complete module

A renamed account should keep its history. Reclassifying an account that already holds postings is a different decision from correcting a spelling error. If a balance was recorded under the wrong type, investigate the affected entries and reports rather than changing the type silently. A stable identity lets an old journal remain understandable even when the display name becomes clearer.

What is a small starting example?

Use a compact chart that supports the events you actually intend to record, then add reviewed distinctions where evidence requires them.

Original teaching chart; not a universal installation template
AccountTypeQuestion it helps answer
Cash or operating bankAssetHow much recorded cash is available?
Loan payableLiabilityWhat principal obligation remains?
Owner capitalEquityWhat funding has the owner contributed?
Service incomeIncomeWhat completed service income is recorded?
Operating expenseExpenseWhat ordinary cost is recorded in the exercise?

The familiar 1,000.00 service receipt and 125.00 operating payment use three of these accounts. Cash closes at 875.00, expense at a 125.00 debit and income at a 1,000.00 credit. The loan and capital accounts stay unused. That is preferable to posting invented opening balances just to populate every row.

This is a teaching chart, not a recommendation to put every cost into one expense account. Real businesses may need more categories and different reporting mappings. The point is to understand why an account exists before adding it.

How do business models change the design?

Different activities need different supporting records. A business label is a starting question, not a complete accounting policy.

These are questions for scoping, not claims that one template or this release supports all seven operations. A chart can reserve meaningful accounts while a supporting module remains absent. Treating a named account as a working stock, customer or membership system is a common source of false confidence.

When is a separate account the wrong solution?

Use an account for a financial classification; do not make the chart carry every customer, location or document identity.

If you create one expense account per supplier, the same kind of cost becomes scattered across the chart. If you create one sales account per customer, a changing customer list can overwhelm the report. Detailed party balances usually belong in a subledger that reconciles to a control account. Dimensions such as project, branch or cost centre are another design question and should not be improvised through arbitrary tags or account names.

Before adding an account, write one sentence explaining how it differs from the closest existing account. If the distinction is only the person who entered the transaction, the transaction’s month or a spelling variation, improve entry rules or reporting filters instead.

How should you avoid duplicate and vague categories?

Use a short account-purpose note and a review process for new accounts, especially when several people enter transactions.

“Other,” “miscellaneous” and “general” categories can become places where uncertainty disappears. A temporary holding category may sometimes have a controlled purpose, but it needs review and resolution. Do not interpret a growing balance there as proof that classification no longer matters. Explain which evidence is missing, who will obtain it and when the record will be revisited.

Review a sample of real transaction types before approving the chart. Ask two operators to choose accounts independently and compare their answers. Disagreement reveals ambiguous categories. Resolving those ambiguities early is easier than reclassifying months of posted history later.

How do currency and monetary properties fit?

A designated account currency restricts what belongs in that account; it is separate from the currency used to display a report.

A USD bank account holds a USD amount even when the book measures its base carrying value in another currency. Currency properties and whether an account is monetary affect later valuation design. They require appropriate evidence and policies, not guesses based on the account number. PHP Ledger’s retained currency foundation stores these distinctions, while period-end revaluation and consolidation remain outside this release.

Do not change a used account’s currency to reinterpret old postings. Keep the original amounts and rates traceable. If the business needs a new denominated account or a reviewed migration, record that as a deliberate change rather than a label edit.

What should you review before importing opening balances?

Map every old balance to an intentional destination and reconcile the detail supporting control accounts.

  1. Compare old account names and classifications with the proposed chart.
  2. Resolve ambiguous mappings before confirmation.
  3. Retain the original account references in the migration evidence.
  4. Reconcile each receivable or payable control to unpaid-document detail.
  5. Check that no opening amount is posted twice.
  6. Review the resulting trial balance and account statements.

A balanced import can still put an amount into the wrong category. Inspect both the mapping and the accounting totals. The cutover lesson explains why an external unpaid schedule is supporting evidence rather than a second instruction to recognise the same income.

When should the chart change?

Change it when the business’s reporting or control needs change, using a documented review rather than ad hoc cleanup.

An unused account can be easier to adjust than one with historical postings. For a used account, distinguish future-entry guidance, a name improvement, an inactivation and a correction of prior classification. Retain inactive history in reports. Before a major change, compare a representative period under the old and proposed structures and identify what readers will see differently.

Practise the idea in PHP Ledger

Use account administration to inspect code, classification, purpose and activity before editing a name or active status. Public-demo account administration is restricted. Starter charts are preliminary examples; they do not establish a regional reporting framework or activate inventory and AR/AP documents.

The synthetic daily cash check and monthly review connect entries to reports. Inspect the current product features and limits before choosing software for a real business.

When PHP Ledger is not the right choice

Choose a supported system when your immediate needs include advanced stock operations, payroll, statutory tax filing or independently accepted reporting. The 0.4.0 starter adds invoice, bill, payment, credit and ageing screens. Optional Purchasing and Inventory add stock workflows; manually configured tax does not establish country applicability or filing support. A demonstration also cannot decide your accounting policies or provide an independent review of your books.

Continue learning

Common questions

Can I copy another business’s chart?

Use it as a reference, then review your own transaction types and reporting needs. A familiar chart may contain unsupported assumptions.

Does an account named Inventory mean inventory is implemented?

No. Inventory needs quantity, valuation and operational records. A general-ledger account name does not create those capabilities.

Sources and review boundary

Source links checked on 16 September 2026. These are further educational reading; the worked numbers and exercises on this page are original synthetic examples.

General bookkeeping education, not jurisdiction-specific advice. This page has not been reviewed by a qualified accountant. Review your entity, reporting framework and policies with your adviser; see the project and review boundaries.

Product screen

Development preview with synthetic sample data

Scroll the image to explore it. With a keyboard, focus the image area and use the arrow keys.