Skip ahead to the main page
Partner Huddle
Pages

Invoice checks: 4 steps before sending a client bill

Partner Huddle Editorial Team · Published · 11 min read

Before sending a client bill, check its invoice number, sales tax line, supporting files, and payment and reminder settings.

  • Confirm the invoice number is unique and traceable.
  • Check the sales tax line against the rule that applies.
  • Open supporting files and match them to the client and invoice.
  • Review the payment method and reminder settings.

It is also the document your own team has to find later, when a payment is late, a question comes in, or someone needs to match a deposit to the right job. A bill that goes out with a wrong number, a missing tax line, or a broken payment path creates extra work for everyone who touches it afterward.

This post covers 4 checks that operations leads and billing staff at small accounting firms can run on each invoice before it leaves the office. Where a point comes from an official source, I link the page. Some of the rules here belong to one state or one software product, and I say so every time. Read the rules for your own clients and your own tools before you rely on any of them.

None of this replaces your firm's review process or advice from a tax professional. Think of it as a short, repeatable list that anyone on the team can work through in a few minutes.

Each of the four checks sits where a small error can pass unnoticed: a number, a tax line, a file, and a payment setting. None of them is hard on its own. The risk comes from skipping one on a busy day, when the bill looks finished and the send button is close at hand.

Does each invoice have a unique, traceable number?

You should also know what the software does when the sequence reaches its limit.

The invoice number is the handle everyone uses. Clients quote it when they pay, your staff quote it when they reconcile, and it shows up in any question about what was billed and when. If the same number appears twice, or if a number cannot be linked to a client file, the mistake is hard to untangle later. Before you send, search your billing system for the number and confirm it has not already been used for another client.

Start with where the sequence comes from. A number can come from the software's own automatic series, or from a scheme you set up yourself, such as a prefix by client or by year with a counter. Either approach can work. What matters is that everyone on the team follows the same rule and that the rule is written down somewhere they can find it. A new hire who invents a fourth prefix creates a gap in the records that nobody notices until a year-end review. Use your client intake checklist to keep the billing handoff clear.

FreshBooks' help article on creating invoices shows how default numbering can work. According to that article, the default number for your first invoice is set to 0000001, with a maximum of 10 characters, or you can select and enter your own alphanumeric number instead. So the first number may be a default you accept without thinking, or one you choose yourself. Make that choice on purpose and record it, so the next person knows what the series looks like and where it started.

The same article also covers what happens when a number reaches the limit of its increment. It says that if the invoice number reaches the limit of its increment, an extra character is added at the end so it can continue. Its example: if the last created invoice is #9999, the number increments to #10000 on your next invoice.

That is worth planning for. A number that gains a character changes its length, and any system that expects a fixed length may handle the change differently. An import into an accounting package, a client's own payables system, or a spreadsheet that sorts numbers as text can each react in its own way. You do not need to guess. Find the highest number in your current series, work out what the next one will look like, and test the change with one invoice before the series reaches it. A test now is much cheaper than fixing a batch of imports later.

Voided and deleted invoices need a rule too. Decide in advance how a number from a cancelled bill will be handled, and note it in the record. Reusing that number on a new bill makes the old and new documents hard to tell apart when someone asks about them later.

Record the number against the client file so a later question can be answered quickly.

Is the sales tax stated separately on the bill?

Tax lines deserve their own check because the rules that govern them vary from place to place. A bill that is correct in one state can be wrong in another. The Washington Department of Revenue publishes guidance on this exact point. Its page on sales tax not listed on the invoice says that Washington law requires sellers to separately state the amount of retail sales tax due on customer sales slips, contracts, invoices, or other sales documents.

The same page says that if the seller's invoice does not itemize retail sales tax, the department will assume that sales tax was not paid. Read that sentence carefully. It describes how the department says it will treat an invoice that does not itemize the tax. It is a Washington agency's position on Washington sales, and it does not tell you how any other state handles the same situation. It also does not say what other consequences might follow, so do not read more into it than the page says.

Before you send, compare the tax line to the taxable subtotal and confirm the two agree. If the arithmetic is off, fix the invoice before it goes out rather than explaining the difference afterward.

If your firm bills clients in several states, keep a short written list of which states you bill into and where each state's rule is published. Each state's rule has to be read on its own terms, and the agency for the place where the sale happens is the right source.

If you are not sure whether a particular line is taxable, that question belongs with your tax advisor before the invoice goes out. It should not be answered by whoever happens to be sending the bill that afternoon. A written answer from your advisor, filed with the client record, gives the next person something to rely on when the same line appears again.

Do the supporting files match the right invoice?

FreshBooks' help article on creating invoices describes an attachment step in its invoice workflow. According to the article, you select Add an attachment and upload files such as images, photos, PDFs, CSVs and spreadsheets, up to 30MB each, on individual invoices only.

The main risk with attachments is a mismatch. A timesheet from March can end up on a bill for June work, or a report for one client can be uploaded to another client's invoice because the file names look similar. Open every attachment before you send. Check that the client name, the period, and the figures in the file match the invoice the client is about to receive. Do not trust the file name alone, because file names are easy to copy and hard to keep current.

Size is the second check. If you use a different billing product, find its limit on its own help pages rather than assuming it matches FreshBooks. The point is to know the limit before you attach, not to discover it when the upload fails or the client calls to say the file is missing.

Privacy is the third check, and it is easy to skip when a file looks routine. Scroll through the attachment and look for anything that does not belong to this client. A spreadsheet exported from a shared report can carry rows for other clients. A PDF can contain a page from a different engagement.

File names deserve a convention too. A name that carries the client, the period, and the document type, such as a client code, a month, and "timesheet," makes a mismatch easier to spot when you open the attachment. Use the same pattern for every client so that a new hire can read a file name without asking.

Keep a list of attachments in the client file as well. The list should name each file, the invoice it went with, and the date it was sent. When a client later says they never received a document, you can answer from the record rather than from memory. If an attachment was redacted, keep the final redacted file and the sending record together. For related file checks, see workpaper recovery.

Illustrative example: catch an attachment mismatch

Suppose an invoice covers 10 hours of work, but its attached timesheet shows 30 hours. Hold the invoice and compare the billing entry with the supporting file. If the wrong timesheet was attached, replace it with the correct file and open that file again before sending. Matching the file to the bill catches the mismatch before the client has to question it.

Are your payment and reminder settings ready for this client?

Not until they have been checked, and Stripe's documentation gives you a clear place to start. It says that before you start sending email notifications and reminders, you can customize your branding.

Check that the branding is the firm's and that it looks the way you expect in a test message. A reminder that looks unfamiliar invites a question you could have avoided. Send a test to an internal address, read it as the client would, and fix anything that looks off before the real send.

If you offer bank debit payments through Stripe, the documentation sets its own timing, and those timings matter for scheduling. For ACH Direct Debit, Stripe's documentation says that customers have 10 days to verify their bank account with microdeposits. Build the schedule so the client has time to complete verification before the payment date you expect.

The same page says that Stripe can automatically retry each failed ACH Direct Debit payment a maximum of 2 times, no more than 40 days after the original payment attempt. Read that carefully. It describes the automatic retries Stripe can make, within a limited window. It does not promise that a retry will succeed. Someone on your team should still check payment status after a failure rather than assume the automatic retries will settle the bill.

Refunds also have a window. Stripe's documentation says that you have up to 180 days from the original payment to submit a refund using the Dashboard or Refunds API. Note the date when the payment is received so the window is easy to track.

These timings belong to Stripe's ACH Direct Debit product. They are not general rules for bank payments. A client who pays by card, by check, or through a different processor may follow different timing, and each of those methods needs its own check in its own documentation. Do not carry Stripe's numbers over to another payment method.

For a bank-debit client, write down the date verification was requested and the date you expect payment, and keep both in the client record. If a payment fails, those two dates tell you where to look first, and they show whether the client had the time the documentation describes.

Last, make sure the payment option on the invoice matches what the client agreed to. If the client has agreed to a bank debit, the invoice should not promise a card payment, and the reverse is also true. A mismatch between the agreed method and the invoice creates confusion that is easy to prevent at this stage.

Run all 4 checks in order before you send

Run the number, tax, attachment, and payment checks in that order, and hold the bill until each one passes. The order matters. The number is the first thing anyone looks for, so a clean number makes the rest of the review easier. The tax line depends on the amounts, so check it after the figures are final. Attachments and payment settings come last because they depend on the invoice already being complete.

Make the list a habit. Keep a one-page version beside the billing system, and have the person who prepared the bill sign off on it. A second person who reviews the bill before it goes out can catch errors the author has stopped seeing. This review does not need to be long. Done consistently, it can catch the errors that would otherwise turn into calls and corrections later, and it leaves a record that shows the bill was checked.

Keep the sources close, too. Software screens, product terms, and tax guidance change over time, so check the current page before you rely on any of them. If a client is in a place this post does not cover, or uses a product this post does not name, the right first step is to find the official page for that place or product and read it before you send.

Today, choose an unsent invoice, work through the checks, and save the review with its client record.

Before you send

What should you do if a check fails?

Hold the bill until the error is corrected. Keep the question with the client record so the next reviewer can see what needs attention.

Does every invoice need a long review?

No, the review can be short. Give the reviewer the invoice and its supporting files together so they can check them without searching.

Related guides: Review 8 CP2000 details before sending client replies · Bank reconciliation: 8 checks before client sign-off.

Sources