Invoicing for people who are not a business yet

You did some work for someone and now they need an invoice. You are not a company. You have no accounting system, possibly no business name, and the advice online is written for people with an accountant and a VAT number.

An invoicing app is software that produces a numbered request for payment and keeps a record of what you sent and whether it was paid. That is all it needs to do. The question is not which one has the most features — it is which constraints apply to you before you have a business at all.

What an invoice has to contain

Less than people assume, and more than most first attempts include. The requirements vary by country, but a document with these is accepted almost everywhere:

• A unique invoice number, sequential and never reused. This is the part beginners skip and the part that matters most, because it is how both sides refer to the document afterwards.
• The date issued, and the payment due date as an actual date rather than "30 days".
• Your name and address — your own if you have no registered business. A trading name with no legal entity behind it is fine in most places, but it must be traceable to you.
• The client's name and address, matching whoever is actually paying. Billing the wrong entity within a company is the most common cause of a delayed payment.
• A description of what was done, itemised enough that someone who was not in the room can approve it.
• The amount, the currency, and the tax position — including an explicit statement when no tax is charged.
• How to pay, with complete bank details or a link.

Most invoices are paid late because they were sent to a person rather than to whoever processes payments. That is an addressing problem, not a design problem.

What changes when you have no company

Three constraints apply specifically to individuals, and only one of them is about the invoice itself.

You still invoice under your own name. In most jurisdictions an individual can invoice without registering anything. The document is a request for payment; being a company is not a prerequisite to asking to be paid.

Tax is your responsibility. Nobody withholds it, so a portion of every payment is not yours. Set it aside as it arrives rather than at year end — this is the single most consequential habit in the whole subject, and it is not a software feature.

Some clients cannot pay an individual easily. Larger organisations have vendor onboarding, and it may need a tax identifier or a registration you do not have. Ask before starting the work, not after sending the invoice.

The third one is worth checking early. A client who cannot process a payment to an individual is a problem discovered before the work, not after.

Do you need an invoicing app at all?

An invoicing app is one of four realistic options, and each costs you something different.

For fewer than a handful of invoices a month, a document plus a spreadsheet works and costs nothing. The point at which it stops working is specific: when you cannot answer "which invoices are unpaid right now" in under a minute, the manual approach has failed and the tool pays for itself.

What actually matters in an invoicing app is unglamorous:

Automatic sequential numbering. Removes the error that causes real problems later.

A record of sent and paid. The ledger is the product; the PDF is just output.

Export you can leave with. Your invoice history should be extractable as data. A tool that will not let you take your records is a bad trade regardless of price.

It works where you work. If invoices get raised on a phone between jobs, an app that is only usable at a desk will not be used at all. Tools built for that pattern — such as Ordava, which handles invoices and orders from a phone — fit the actual working day better than a desktop system used once a week.

Cost proportional to volume. Paying monthly for a tool used twice is a poor deal, and several options are free below a low threshold.

Skip, for now: multi-currency accounting, inventory, payroll, project time-tracking. An invoicing app carrying all of these is built for a business several stages ahead of yours. These are for later, and their presence is a sign you are looking at software aimed at someone else.

Getting paid, which is a separate problem

The invoice is the easy half. Payment is behaviour, and four things move it measurably.

1. Send it immediately. The correlation between sending promptly and being paid promptly is strong, and it costs nothing to act on.
2. Send it to the right address. Ask for the accounts email at the start of the work. A document sitting in your contact's personal inbox is not in the payment system at all.
3. State the due date as a date. "Due 14 November" is acted on; "net 30" requires the reader to calculate, and calculation is delay.
4. Follow up on a schedule, not on a mood. One polite message the day after the due date, another a week later. Late payment is usually process, not refusal, and a reminder is a normal part of the process.

Agree the amount in writing before starting, even in a message. A disputed invoice is almost always a scope disagreement that predates it, and two sentences agreed in advance prevent most of them.

For anything substantial, ask for a deposit. A client who will not pay anything up front is telling you something worth hearing.

A workable setup for the first year

Five things, in order.

Pick a numbering scheme and never break it. Whether you use an invoicing app or a folder of documents, this is the rule that matters. 2026-001 upward is enough. Do not restart it, do not skip numbers, do not reuse one.

Keep one folder of PDFs and one list. Number, client, date, amount, paid yes or no. That list is your accounts.

Open a separate account for the money. Not a business account necessarily — just not the one you buy groceries from. It makes the tax portion visible.

Set aside the tax on arrival, as a fixed percentage moved on the day the money lands.

Keep everything for as long as your tax authority requires, which is commonly five to seven years. Storage is cheap and reconstruction is not.

More comparisons in best tools, the surrounding software in software, and workflow picks in productivity software. Requirements vary, so check your own tax authority — the UK's guidance on invoicing is a clear example of what a national rule set looks like.

The short version

An invoicing app needs to do three things: number invoices sequentially, keep a record of what is paid, and let you export it. Everything else is for a business you do not have yet.

Invoice under your own name, put the tax aside on the day each payment arrives, send the document to whoever processes payments rather than to the person who hired you, and state the due date as an actual date — then follow up on a schedule, because late payment is usually process rather than refusal.