Your chart of accounts is the list of buckets every transaction eventually lands in — Sales, Office Costs, Bank Current Account, VAT Control, and however many more categories your business needs. It sounds like the simplest part of bookkeeping, and mostly it is, but a chart of accounts with no structure underneath the names quietly breaks the reports built on top of it.
Leaf accounts vs. header accounts
Accounts sit in a hierarchy, not a flat list. A leaf account is one you can actually post a journal line to — Office Supplies, say, or a specific bank account. A header (or group) account exists only to total up the leaf accounts beneath it — "Total Office Costs" summing Office Supplies, Software, and Postage underneath it.
The rule that makes this hierarchy mean something: only leaf accounts accept postings. A header can't end up with a stray transaction sitting on it alongside the subtotal it's supposed to represent — which is exactly the kind of thing that, in a spreadsheet or a looser system, quietly makes a "total" line wrong without anyone noticing, because the total now includes both the subtotal calculation and an extra transaction posted straight onto it.
System accounts are protected, not just listed
Some accounts aren't ordinary categories — they're plumbing the rest of the ledger depends on. Your VAT control account is where every VAT-inclusive transaction's tax portion lands, read by the single calculation that produces your VAT return (see VAT, FX & reports). Your AR and AP control accounts are what your Aged Debtors and Aged Creditors reports tie out against. Retained earnings carries forward the result of every year-end close.
These are flagged as system accounts specifically so they don't get treated like an ordinary expense category — renamed into something that no longer matches what reads it, or retyped in a way that breaks the assumption the rest of the system makes about what lives there. An account that's already been posted to also can't simply be deleted outright: your historical reports depend on it existing, whether or not you're still using it for new transactions.
Why this matters more than it looks like it should
A chart of accounts with no governance degrades in predictable ways over time: two accounts with almost-identical names because someone typed a new one instead of finding the existing one, a posting that landed on what was meant to be a header/subtotal line, an account central to your VAT or debtor reporting getting renamed by someone who didn't realise what depended on it. None of these show up as an error message — they show up months later as a report that doesn't quite add up, and nobody can immediately say why.
Structure at the account level is what keeps that from being a slow, silent drift. Leaf-only posting means a subtotal line stays a subtotal line. Protected system accounts mean the handful of accounts your own reports are built on can't be casually reshaped. Between the two, your chart of accounts stays what it's supposed to be — a stable set of categories your reports can be trusted to group correctly, year after year, without you having to re-audit it yourself.
What this looks like day to day
You're free to build a chart of accounts that fits how your business actually thinks about its income and costs — add categories, reorganise them, retire ones you don't need. What you won't be able to do, by design, is post a transaction onto a subtotal line, or delete the VAT control account your own reports read from. Those aren't restrictions on customising your books; they're the structural guarantees that make the reports built from your books mean what they say.