Bookkeeping Basics
Build a clean category list for income, expenses, assets, liabilities, and equity without overcomplicating your books.
Best for: small businesses setting up spreadsheets, accounting software, or KanderBooks templates for the first time.
Important: This article is general bookkeeping education. It is not tax, legal, payroll, or accounting advice. Rules and correct treatment can depend on entity type, industry, location, software setup, and professional judgment.
A chart of accounts should be simple enough to use consistently and detailed enough to answer real business questions.
What this means
The chart of accounts is the category structure behind your bookkeeping. Every transaction is assigned to an account so reports can summarize activity.
Too few categories hide useful detail. Too many categories create inconsistent coding. The goal is practical clarity that supports monthly review and tax-prep handoff.
Core concepts
Separate major revenue streams only when the distinction helps you review performance.
Use categories that match how the business manages costs and prepares records.
Track each bank account, card, loan, tax liability, payroll liability, and equity account separately.
Write short notes explaining where common transactions belong.
Step-by-step workflow
- Gather the source records. Save statements, receipts, reports, screenshots, contracts, confirmations, or notes that support a chart of accounts.
- Identify the business event. Decide what actually happened before choosing a category or changing a report.
- Match the money movement. Compare the bookkeeping record to bank, credit card, loan, payroll, or platform activity.
- Choose the right treatment. Separate income, expense, asset, liability, equity, transfer, and owner activity instead of using one catch-all category.
- Review for duplicates and timing. Look for repeated entries, missing transactions, old balances, refunds, chargebacks, and period cut-off issues.
- Save final notes. Keep a clear explanation so the owner, bookkeeper, or accountant can understand the decision later.
Review checklist
- The period, account, and source report being reviewed are clearly identified.
- Transactions are not duplicated or counted in the wrong period.
- Unclear items are placed on a question list instead of guessed.
- Supporting documents are saved in the monthly records folder.
- The final report or template includes notes for unusual activity.
Common mistakes to avoid
- Guessing from the bank description only. Bank descriptions are helpful but often incomplete.
- Using miscellaneous too often. Too many miscellaneous entries make reports less useful.
- Skipping documentation. A correct number is harder to defend when the source is missing.
- Ignoring balance sheet effects. Some activity affects assets, liabilities, or equity rather than the P&L.
Example review map
| Area | What to review |
|---|---|
| Documents | Confirm the files supporting a chart of accounts are saved and named clearly. |
| Category | Confirm the category describes the business purpose and account type. |
| Balance | Confirm any related bank, card, loan, tax, payroll, or owner balance makes sense. |
| Questions | List missing details and assign follow-up before closing the month. |
| Handoff | Save a short note for the owner, bookkeeper, accountant, or tax preparer. |
FAQ
Should every vendor have its own account?
Usually no. Vendors identify who was paid; accounts describe the type of activity.
Can I rename accounts later?
Yes, but document changes so prior reports remain understandable.
Can I use this with a KanderBooks template?
Yes. Use the article as a workflow guide, then use the matching KanderBooks template to organize amounts, notes, dates, confirmations, and review questions.
When should I ask a professional?
Ask a qualified bookkeeper, accountant, payroll provider, or tax professional when the item affects taxes, payroll, loans, prior-period reports, legal compliance, or financial statements used outside the business.
Was this tutorial helpful?
Your feedback helps improve the KanderBooks tutorial library.