Chart of accounts: 5 checks for accurate invoices

Key takeaways

• Check the income account for each invoice line before sending.
• Keep account codes unique and within 50 characters.
• Add accounts only for categories you need to track.
• Record current values and review the selection before a bulk update.
• Match incoming payments to invoices and explain any difference.

A wrong account on one invoice line is easy to miss when you send it, and harder to spot once payments start arriving and you reconcile them against the bank. Run the first four checks before you send a batch of invoices, and again after you change how your accounts are set up. Match payments as they arrive. Each one gives you something concrete to look at, fix, or confirm.

Zoho Books says its Chart of Accounts lists a set of default accounts that can be used in your business, grouped into categories like Income, Expenses, Equity, Liabilities, and Assets. To open it, go to Accountant on the left sidebar, and select Chart of Accounts. Keep that screen open while you work. Each check asks you to look at the accounts themselves, rather than rely on what you remember setting up months ago.

The checks suit a bookkeeper who sends invoices for several clients, and an owner who sends their own invoices and wants to be sure the books match. The steps are the same either way. A bookkeeper may want to record the reasoning in more detail, so that anyone who reviews the work later can follow it.

Does each invoice line point to the right income account?

Each line on an invoice should point to the income account that matches what it bills for. A line can look correct to your customer and still point to the wrong account in your books, so the check has to happen on the account side, not just on the invoice page.

Start with the items you invoice most often. Review the income account used for each invoice line. If a line bills for consulting, check that its account matches that revenue category. Do the same for one-off lines you type straight onto an invoice, because those are easy to skip when you are in a hurry.

Suppose you bill a client for a monthly retainer and also for a separate workshop. If both lines point to the same income account, the two may show up as one figure in any report that groups by account. That may be fine, or it may hide the split you care about. Decide which view you want before you send the invoice, not after a customer asks why the totals do not match their own records.

Then test the whole process on a few real invoices. Pick three recent invoices that cover different kinds of work, and trace each line back to its account in the chart. You are looking for three kinds of problem: a line that points to an account with a vague name, a line that points to an account you no longer use, and a line that has no clear account at all. Each one takes a few minutes to fix once you find it, and much longer to untangle after several months of reports.

Old items deserve the same look as new ones. An item created for a service you no longer offer may have settings that need review.

When you find a mismatch, decide which side is wrong before you edit anything. Sometimes the line is right and the account name is misleading, so the fix is to rename the account. Other times the account is right and the invoice line points elsewhere, so correct the account used for that line. Write down what you changed and why, so the next person who opens the chart can follow your reasoning.

This check covers only the Income group. Expense, equity, liability, and asset accounts matter too, but they are a different job, so do not let them slow down this pass. Finish the income review first, then move on. For a broader review before sending, use the invoice approval checklist.

Are your account codes unique and short enough?

Yes, if every code is unique and no longer than 50 characters. Zoho Books asks you to enter a unique code of up to 50 characters in the Account Code field, so that length is the limit to plan around.

Codes earn their place when you need to sort, compare, or refer to accounts outside Zoho Books, such as in a spreadsheet or in a note to your accountant. A name is easy to change, and a code gives you a fixed reference that stays the same when the wording of the name changes. That matters most when a second person is reading your numbers and needs to find the same account you are describing.

Pick a simple scheme and write it down. One approach is to give each category its own prefix, so income accounts share one leading pattern and expense accounts share another. Keep the rest of the code short enough to type and read. A code like INC-CONSULT is easy to scan; a long code that repeats the full account name is not. That example only illustrates a pattern and is not a format from Zoho Books, so use whatever pattern you can follow consistently.

Think about how the codes will look as the chart grows. A scheme that reads well for a small chart can become hard to scan later. Leave room in the numbering so new accounts fit where they belong without renumbering the rest. If you share the chart with a bookkeeper or accountant, agree on the scheme before either of you creates an account.

Check for duplicates before you save. If you are building codes in a spreadsheet first, sort the list and look for repeats. After you save, scan the chart once more and look for any account whose code makes you pause. If two accounts look alike, decide now which one stays and which one gets a clearer code, before invoices start using both.

Keep a short note beside the chart that records your scheme. Include the prefixes you chose, what each one means, and the date you set them up. When someone joins the team or you come back to the books after a long break, that note saves a lot of guessing. It also gives you something to check against when a code looks wrong, because you can see whether it breaks the pattern or simply belongs to a different group.

Do you need accounts beyond the default list?

Sometimes. Create an account when the default list does not give you a place to track what you need. Zoho Books says that if you need accounts apart from the default list of accounts, you can create them. A new account lets you track transaction amounts under a specific account instead of using the default ones.

The second point matters most for invoicing. Say you run a small design business with one default account for services and several different project types. If you want to see how much you earned from one project type over the course of a year, a dedicated account gives you that total directly. Without it, you would need another way to separate those invoice amounts for review.

Keep the list short, though. Each account you add is one more place a line could be posted, and one more account to check when you reconcile payments. Create accounts for the categories you will report on or compare against the bank, and skip the ones you would only use once. Do not create a separate account for each customer unless you genuinely need to track revenue that way.

Name each new account the way you name the item it supports. If the item says consulting, the account should say consulting too, so anyone reading the report can match the two without asking. Avoid names that describe a feeling or a plan, such as "misc" or "to sort." Those names look fine on the day you create them and become a problem later, when nobody remembers what they were meant to hold.

Before you create an account, ask whether a rename would do the job instead. Use a new account when the old one truly covers a different kind of revenue. Use a rename when the old one only has a poor name.

A useful test is to ask whether you would need to explain the account to someone else. If the answer is yes and the name does not explain itself, the name needs work before the account goes into use. It also helps to list the reports you actually read each month and check whether the default accounts answer the questions you ask of them.

Should you review a bulk update before you apply it?

Yes. Zoho Books says that you can select up to 1,000 accounts for a bulk update, so one wrong selection can touch a large number of accounts in a single action. A few minutes of checking is small next to the cost of finding and fixing that many accounts by hand.

Editing one account at a time is slow, but each change is visible as you make it. A bulk update is fast, and the mistake is easy to overlook once it has run. That difference is the reason to slow down. Treat the bulk step as the moment to be most careful, not the moment to rush.

Before you run one, write down the current values for every account you plan to change. Note the names, the codes, and any settings you expect to touch. A screenshot or a copy in a spreadsheet is enough, as long as you can read it back later. This is the record you will need if the result is not what you intended.

Then read the selection before you confirm it. Count the accounts you have chosen and compare that count with the number you expected. If they do not match, stop and find out why. Do not confirm a selection you cannot explain, even if it looks close enough. A selection that is almost right is the kind that causes problems later.

If the change is large, try it on a small group first. Check the result against your notes. If it matches what you wanted, run the rest of the update. If it does not, you have caught the problem while it is still small. If you are not sure what a change will do, ask the person who set up the chart or your accountant before you go ahead.

Read through the full selection, not just the part you see first. A bulk update reaches accounts you may have forgotten about, and the one you overlooked is often the one that causes the trouble.

After the update, look at a few recent invoices that used the changed accounts. Confirm that the lines still point to the expected accounts. This last look is quick, and it is the step that tells you whether the bulk change did what you meant it to do.

Should each payment match the invoice it settles?

Each payment should match the invoice it settles, or the gap should be explained before you close the invoice. Compare the amount and date of each incoming payment with the invoice it pays, and note any difference. The aim is that every payment you receive can be traced back to the invoice that asked for it.

When you reconcile, it helps to work from the bank side first. Find the deposit, then find the invoice or invoices it pays. Working this way keeps you from forcing a payment onto an invoice that does not quite fit. Use the guide to reconcile invoice payments with your bank for the payment review.

Start with exact matches. When the payment equals the invoice total, mark it and move on. These are the easiest to close, and clearing them first leaves you with a shorter list of questions. For anything else, decide what the gap is before you close the invoice, rather than leaving an unexplained difference for later.

A partial payment means part of the invoice is still open. An overpayment needs a decision about whether it is a credit, a refund, or a mistake. A short payment could come from a bank fee, a discount you gave, or a customer error, and you need to know which before you close the invoice. Write the reason next to the payment so the choice is recorded.

Suppose a customer pays most of an invoice and says the rest will arrive next week. That payment is a partial match. Leave the invoice open, note the expected remainder, and match the second payment when it arrives. Do not mark the invoice settled just because the customer has promised to pay.

A customer may also pay two invoices with one transfer. Match the payment to both invoices, and write down how the total was split between them. If the split is not obvious, ask the customer which invoices the money was meant for. A short note now is much easier than trying to reconstruct the split after the bank statement has moved on.

Work through the payments in the order they arrived, and keep a short note for each gap. Notes matter most when the reconciliation is reviewed later, because whoever reads the file will not have your memory of the call with the customer. Record the date, the amount, the reason, and your initials, so the next reader can see who made the call.

Choose a rhythm you can keep, such as checking accounts before each batch of invoices goes out, and matching payments as they arrive, and write it into your routine.

Run the five checks in order. Income accounts come first, followed by codes, new accounts, and bulk edits. Payments come last, because that is where earlier mistakes can show up. Finish the first four checks before sending; run the payment check as payments come in.

Illustrative example: a partial payment

An invoice totals 200 and a payment arrives for 180. The remaining balance is 20. Record the payment against the invoice, note the remainder, and leave the invoice open. These amounts are illustrative; the example shows why a payment arriving does not necessarily mean an invoice is settled.

What should you check today?

Today, pick three recent invoices that cover different kinds of work and trace their lines to the income accounts you intended to use. Record any mismatch before changing it.

Are your invoice checks in order?

Do all five checks happen before sending?

The first four checks happen before sending, and payment matching happens as payments arrive.

Should you create an account for every customer?

No, create a separate account only when you need that revenue split for tracking or reporting.