How to Invoice Without Accounting Software

That is why this guide spends only a short section on the document itself and most of its length on numbering, the register, and part payments. Those are the pieces accounting software quietly handles for you, and they are the pieces you have to replace by hand.

One boundary up front. This is a how-to on mechanics, not tax or legal advice. What an invoice must contain, and how sales tax appears on it, varies by state and by what you sell. For those rules, ask your state revenue department or an accountant. Everything below is the operational layer that works regardless.

What must an invoice include?

Start with the fields that let a customer pay without calling you and let you prove later what was billed. Here is the checklist, split into the fields you always need and the ones that depend on your situation.

Always include:

• The word "Invoice" at the top, so nobody mistakes it for a quote or a receipt.
• Your business name and contact details, and the customer's name (and billing address if you have one).
• A unique invoice number (the rule for that is two sections down).
• The invoice date.
• A due date written as a calendar date, not "net 14". A date cannot be argued with.
• Line items: what was done or sold, quantity or hours, price per unit, line total.
• The total due, and the amount already paid if a deposit was taken.
• How to pay: bank details, a payment link, or "cash or check", plus who a check is made out to.

Include when they apply:

• Sales tax as its own line, if you charge it. Your state decides whether and how, so check with the revenue department.
• A purchase order or job reference, if the customer's accounts person asks for one.
• Late-payment terms, if you actually enforce them. Do not print terms you will not follow.
• A short note on the scope, such as "includes two revisions", where disputes tend to start.

The test for the whole list: could somebody who was not on the job read this page and know what was done, for whom, for how much, and how to pay it? If yes, it is complete enough.

Which tool should make the invoice document?

Whatever you will actually open every time. The practical options, in rough order of effort:

Tool	Good for	Where it hurts
A word-processor template (Word, Google Docs)	Service businesses with a handful of line items	Totals are typed by hand, so arithmetic errors are yours
A spreadsheet template (Excel, Google Sheets)	Anything with quantities and rates, since formulas add the lines	Easy to overwrite last month's file and lose the original
A free online invoice generator	One-off invoices when you want a clean PDF fast	Often no saved history, so the register matters even more
Pen and a pre-printed invoice book	Trades that bill on the doorstep	The carbon copy is your only record

Pick one and build the template once. Put your details in, set up the fields from the checklist above, and save a blank copy that you never edit directly. Each new invoice starts as a copy of the blank, and gets saved as a PDF under its invoice number. That habit, "copy the blank, never edit the blank", is the single cheapest protection against version drift.

If you use a spreadsheet, let the formulas do the multiplying and adding, and lock those cells so a stray keystroke cannot change a total. Then export to PDF before sending, so the customer receives a document that cannot be edited and you keep exactly what they received.

How should you number invoices so they never collide?

Pick a rule once and write it down in the first row of your register. Two rules cover nearly everyone.

Plain sequence: 001, 002, 003 and on. Dead simple, but the number tells you nothing about when it was issued, and the count resets awkwardly if you ever start over.

Year plus sequence: 2026-001, 2026-002, and a fresh 2027-001 in January. This one survives a year better because the year is in the number, the sequence restarts cleanly, and a glance at the number tells you roughly when it was sent.

Whichever you pick, three rules keep it from colliding:

1. One counter, not one per template. If you use a different layout for different kinds of work, they still draw from the same sequence. Two templates with two counters is how two invoices end up numbered 014.
2. The number is taken when the invoice is created, not when it is sent. Write the number in the register first, then use it. If you cancel the invoice, keep the number in the register and mark it void. A gap with a note ("void, customer changed scope") is better than a reused number.
3. Corrections get a new number. If an invoice was wrong, void it and issue a fresh one that references the old number in the note. Editing a sent invoice and sending it again under the same number leaves two different documents with one identity.

The register is what makes this rule enforceable. The next number is always the last line of the register plus one. You never have to open a folder of PDFs to find out where you are.

For what it is worth, IRS Publication 583 does not prescribe an invoice numbering scheme. It lists invoices among the supporting documents that show the amounts and sources of your gross receipts, and says to keep records in an orderly fashion. A clean numbering rule is how you meet "orderly" in practice.

Where do you record an invoice once it is sent?

In a register: one line per invoice, written the moment it goes out. This is the part of the system that replaces software, and it is smaller than people expect. Seven columns are enough.

Column	Example entry
Invoice number	2026-014
Date sent	2026-10-01
Customer	The name on the invoice
Job or note	Kitchen repaint, two coats
Amount	The total due
Due date	2026-10-15
Status	Open, part paid, paid, or void

Two more columns earn their place once you take deposits: paid so far and balance. The status column does the real work. Anything not marked paid is, by definition, money you are still owed, so the open lines are your receivables list without a separate report.

The checklist for making the register line, in order:

1. Take the next number from the last line of the register.
2. Write the line before you send anything. Number, date, customer, amount, due date, status "open".
3. Build the invoice from the blank template using that number.
4. Save the PDF under the invoice number, so file name and register row match.
5. Send it, and note the method if it matters ("emailed", "handed over").
6. When money arrives, change the status and record the date. Do not delete the line.

That is about forty seconds of work per invoice, and it gives you three things the invoice document alone never will: the next number, a list of what is outstanding, and a trail you can follow back from any payment to the work behind it.

The register can live in a notebook, a spreadsheet, or in the money module of the SMBDashboard. To be straightforward about scope, SMBDashboard does not generate invoice documents. Make those in whatever template you like. What it holds is the record: log each invoice as an open entry when it goes out, mark it paid when the money lands, and the unpaid ones stay on the screen. The free tier holds 200 money entries, which is plenty for a small invoicing business, and your data stays in your browser unless you turn on Pro sync.

Once the register exists, chasing late payment becomes mechanical. The follow-up schedule, with wording to copy, is in how to track unpaid invoices without software. The register is what feeds it.

How do you handle deposits and part payments?

Deposits are where manual systems quietly break, because the invoice says one amount and the bank shows another. The fix is to decide, before it happens, that a deposit changes the register and not the original invoice.

Deposit up front. If you take a deposit before the work, issue a deposit invoice for that amount with its own number and its own register line. When the job is finished, the final invoice lists the full price, shows the deposit as a credit line, and asks for the balance only. Now the register shows two invoices that add up to the job, and each one is paid or open on its own terms.

Part payments on one invoice. If a customer pays an invoice in pieces, keep one register line and use the two extra columns: paid so far and balance. Update the balance each time money arrives. The status is "part paid" until the balance is zero.

Staged payments on a long job. Set the stages in the quote (for example, on start, at midpoint, on completion), then raise one invoice per stage. Each stage invoice references the job in the note so you can add them up later.

Whichever method fits, the principle is the same: never overwrite an amount on a sent invoice to reflect a payment. The invoice records what was billed. The register records what has been collected. Keeping those two facts separate is what lets you answer "what is still owed on this job" in one glance. For the wider picture of how money timing affects the business, cash flow basics for small business owners covers why a paid-in-part invoice and a paid-in-full one feel so different at the end of the month.

Do you need to keep copies of invoices you send?

Yes, keep them. How long is a question for the record retention rules. The IRS publishes its general retention periods on its page about how long to keep records, which gives three years as the default period and longer for certain situations, such as employment tax records and years when no return was filed. Your own situation, and any state rules, may differ, so treat that page as the starting point and confirm with an accountant.

In practice, keep the PDF of every invoice and the register together, organized by year. If the PDFs are named by invoice number and the register has the same numbers, finding any invoice takes seconds. Back the folder up somewhere other than the one laptop. The register is small enough to export or print monthly if you want a copy that does not depend on any device.

When does invoicing software start earning its fee?

Honestly, at the point where the manual register costs more time than the subscription costs money. The signals are specific:

• Volume. When typing invoices into a register and a template starts eating hours you could be billing, the arithmetic of your hourly rate against the software fee tips.
• Recurring billing. If the same invoice goes to the same customers every month, automation that generates and sends it on a schedule is worth paying for.
• Online card payment. Customers who expect to pay by clicking a link need a payment processor attached to the invoice, which a template cannot do on its own.
• Several people invoicing. One register in one spreadsheet works for one person. Two people raising invoices against the same counter collide quickly.
• Your accountant asks for it. If the bookkeeping side is handed to a professional, ask which format they want records in before choosing anything. The SBA's guide to managing your finances describes accounts receivable as one of the things a business needs to keep tabs on, and recommends bringing in a CPA or bookkeeper for the accounting itself.

Until one of those is true, the template, the numbering rule and the register are a complete system. If you do move later, nothing is wasted: the register is a ready-made list of past invoices and customers to import, and the numbering rule tells you where the new tool should pick up.

A weekly look at the register also pairs naturally with the printable weekly business report, which puts open invoices next to the week's other numbers on one page.

What is the quickest way to start today?

Set up in this order, which takes about half an hour:

1. Build one invoice template with the fields from the checklist and save a blank copy.
2. Choose your numbering rule and write it in the first row of the register.
3. Create the register with the seven columns, plus paid so far and balance.
4. Raise your next real invoice using the six-step routine above.
5. Look at the open lines once a week.

If you want the register on a screen rather than in a notebook, open the money module free, log each invoice as an open entry when it goes out, and mark it paid when the payment lands. Open the dashboard and the unpaid work stays visible without any setup beyond the first entry.

FAQ

Can I make an invoice in Word or Google Docs?

Yes. Both work, and plenty of small businesses do exactly this. Build a template with the fields from the checklist, keep a blank copy, and export each finished invoice to PDF before sending so the customer gets a document that cannot be edited and you keep the same version. The tool matters much less than the numbering and the register that sit alongside it.

Is there a required format for a small business invoice?

There is no single layout every invoice must follow. What matters is that the invoice carries the information a customer needs to pay and a record needs to stand up: who billed whom, what for, how much, when, and how to pay. Requirements around sales tax and certain industries differ by state, so check with your state revenue department or an accountant for anything specific to your business. IRS Publication 583 lists invoices among the documents that support your records of gross receipts.

How should I number my invoices?

Use one counter and one rule. Either a plain sequence (001, 002, 003) or year plus sequence (2026-001). Take the number when you create the invoice and write it in your register immediately. If an invoice is cancelled, keep the number and mark it void rather than reusing it, and issue corrections under a new number that references the old one.

Do I need to keep copies of invoices I send?

Yes. Keep a PDF of each invoice and the register line that matches it. The IRS gives three years as its general default for keeping records, with longer periods in specific situations, on its record retention page. Confirm the right period for your situation with an accountant.