How Startups Keep Invoices Clean Before Revenue

Your first invoice sets the pattern your books follow for the next five years. Get the numbering wrong on invoice one and you will be explaining a gap to an accountant long after you hire one. The good news: the habits that keep invoices clean cost nothing to set up, and they matter most before you have revenue, because that is exactly when nobody is checking.

Here is what to lock in before you send the first one.

Start your invoice numbers at a plain, sequential format

Do not start at INV-0001 because it looks small and new. Start there because sequential, gap-free numbers are what an auditor, a tax authority, and your future bookkeeper all expect. The rule in most places is simple: each invoice gets a unique number, and the numbers run in order with no gaps and no reuse.

Where founders trip up is trying to be clever. They encode the client name, the project, the quarter, and a lucky number into one string, then run out of room or break their own pattern by month three. Keep it boring. A prefix plus a running count (INV-0001, INV-0002) works until you are well past your first hundred clients. If you need a year, put it in front: 2025-0001.

The one thing you cannot do is skip a number because you deleted a draft. A deleted draft is fine. A sent invoice you later void still keeps its number; you issue a credit note against it rather than making it vanish. If you want the full reasoning, our guide on invoice numbering best practices covers the formats that survive an audit and the ones that quietly break.

Invoice under your real legal name, even pre-incorporation

Before you incorporate, you are invoicing as yourself: your legal name, your tax ID, your address. That is fine, and it is honest. What causes trouble is invoicing as "Acme (a trading name we made up last week)" when no such entity exists yet. A client's accounts payable team pays entities they can match to a contract and a tax record. A name that matches nothing gets held.

So put your actual registered name on the invoice, add the tax identification number you actually have (your personal one until the company has its own), and match the name on the invoice to the name on the bank account that receives the money. When the company is formed, switch the sender details on new invoices. Do not retroactively rewrite old ones. The old invoices are correct for who you were when you sent them.

If you are not sure which tax number belongs on the invoice, start with the basics in the taxpayer identification number entry and go from there.

Pick payment terms you can actually survive

Terms are the lever most first-time founders ignore, then regret. Net 30 is the default most B2B clients assume, which means a 30-day invoice is often really a 45- to 55-day wait once their AP cycle is added. If you have no revenue and no runway buffer, that gap can end you.

Two defensible moves before you have cash:

• Shorten the terms on smaller clients. Net 15 or due on receipt is normal for a new vendor with small amounts. Bigger clients with procurement will push back, so pick your battles.
• Ask for a deposit on larger work. A deposit invoice before you start is standard and gets you working capital without debt.

Whatever you choose, put the due date on the invoice as an actual date, not just "Net 30." People pay dates, not terms. If you want the tradeoffs laid out, picking the right payment terms walks through when each one makes sense, and why Net 30 invoices pay late explains the hidden delay.

Put complete bank details on every invoice, checked

The single most common reason a clean invoice still does not get paid: the client cannot work out where to send the money. Before you send anything, confirm the account name, account number, and routing details are exactly right. One transposed digit in an international bank account number can bounce a payment or send it to a stranger.

If you invoice across borders, include the SWIFT/BIC alongside the account number, and run the IBAN through a free check before you send rather than after the money goes missing. Domestic clients in the US need the account and routing number for an ACH transfer, not a wire.

Treat your bank details as locked once an invoice is issued. If they change, you do not edit a sent invoice, you issue a new one or send a clear correction. A payment detail that changed silently after sending is exactly the kind of thing that makes a cautious AP team stop and call you.

Set up version control before you need it

You will send an invoice, and a client will ask you to add a purchase order number, fix their legal entity, or change a line item. This happens on the first invoice as often as the hundredth. The clean way to handle it is to know which changes are a new version and which are a tracked amendment.

A changed line item or price is a new version of the invoice. A PO number or a billing address correction is an amendment to the current version, not a renumbered document. Keeping those separate means your records show what was agreed and when, without a pile of near-identical PDFs. The practical split is covered in versions versus amendments.

This is where a plain tool beats a spreadsheet. With invoicing built for startups before and after revenue, you send the invoice as a private link, the client adds their own PO number or billing entity, and you get notified and can revert anything that looks wrong. There is no account for them to create and no attachment to lose. When you do incorporate and connect payment, the same invoices keep working.

None of this requires accounting software. You can create your first invoice for free, set the numbering format once, and let it increment from there. The whole point of getting this right early is that you never have to go back and fix it.