Sending Your First Freelance Invoice

An invoice is a request for payment that a business can process. That single purpose explains every rule about what goes on one: a finance system, or a person acting like one, has to match it to a job, approve it, and pay it without asking you anything.

Everything on the document that does not help with that is decoration.

The eight lines it needs, and nothing more

The word Invoice, and a number. Both. A document headed "Work done" is not an invoice to the person paying it.

Your details: the name you are paid as, an email, and a business or tax registration identifier if you have one.

Their details: the legal business name, not the trading name on their signs, plus the billing contact or department.

The date you issued it.

What you delivered, described in their words. "Product descriptions, batch two, forty items" beats "content services". If there is a purchase order or job reference, put it here, because some finance systems cannot pay without it.

The amount, with the currency named in letters as well as symbols, since the same symbol belongs to several countries.

The date payment is due, written as an actual date.

How to pay: the rail and the details. Account name and numbers, or the payment link. This is the line people leave off, and it decides whether you are paid today or next week.

That is the document. No thank-you paragraph, no description of your process.

Numbering and dating so you can find it in a year

Number them sequentially, never reuse a number, and leave no gaps. A gap looks like a missing invoice to anybody reviewing your records, including you.

A scheme that carries information beats a bare counter: 2026-BRT-004 gives you the year, the client and the position without opening anything. Pick one and keep it.

Put two dates on the document and label both: issued, and due. Never express the due date only as a number of days — you and their finance team will count from different points.

Terms, said plainly

Terms are two sentences. When payment is due, and what happens if it is not.

Say the first as a date. Say the second without menace: a reminder on the due date, a second to the finance contact, then a stated step. Do not put threats of legal action or interest on a first invoice unless you agreed them in the contract — an empty threat teaches the client your words do not mean anything.

Ask one question before you invoice, once per client: how does your payment process work, and is there anything the invoice needs in order to go through? You will learn about the purchase order requirement, the approval chain, and the address invoices must actually go to.

If the answer describes a process longer than you can carry, that is a pricing conversation for new freelancers to have now, not a surprise later.

Sending it at the right moment

For a fixed-price job with a deposit, the deposit invoice goes out before any work starts, and work starts when it is paid. Not when it is promised.

The final invoice goes attached to the delivery, in the same message. Not the next day, not at the end of the month. The moment the client is looking at finished work is the moment payment feels obviously due.

For ongoing work, pick one billing day and hold it. Predictability is what gets you into a payment run instead of onto somebody's to-do list.

And send it to the right person. Whoever briefs you is not always whoever pays you, and an invoice in a project manager's inbox is invisible to accounts. Ask who it should go to and copy your contact so they can nudge it. Where the money travels once approved is the rail — how online clients pay you covers choosing one.

The reminder schedule before anything escalates

Reminder one, on the due date. Resend the same document with one line: invoice 2026-BRT-004 was due today, attaching it again in case it needs a nudge. No apology and no anger.

Reminder two, a few days later, to your contact and the finance address together. Same document, one added sentence stating what is outstanding and the original due date. Adding the second recipient does the work, because it makes the delay visible to somebody else.

Reminder three states the next step and puts a date on it. Then take that step on that date. A reminder schedule that never escalates teaches the client to ignore it.

Keep every reminder flat and identical in tone. You are not asking a favor; you are operating a process. Past reminder three it stops being an invoicing problem — what to do when a client will not pay is where it goes next.

Keeping copies of everything you send

Save the file you actually sent, not the template you generated it from — templates get overwritten, and the document that left your hands is the one that matters in a disagreement.

Save the message too, with its timestamp and the addresses it went to. If you send through a platform the record lives there, but export it periodically — access to a free tool is not permanent.

Keep the delivery message alongside it: what was handed over, when, and their reply acknowledging it. An invoice on its own is an assertion.

One folder per client, files named with the invoice number, and one index of what has been issued and what has been paid. Free invoicing software does a lot of this — free tools to start a business with no money has the shape of that toolkit — but the folder is yours and survives the tool.

When an invoice is the wrong instrument

When the platform bills the client. If a marketplace raises its own charges and pays you out, a separate invoice creates confusion and sometimes a double payment somebody claws back later. Check who issues the document before you issue one.

When nothing has been agreed. An invoice is not a way to open a price conversation; sending one to a client who has not agreed a number is the fastest route to having neither the money nor the relationship.

When the client asked for a quote or a proforma. Those are forward-looking documents for approval, and a finance team that asked for a proforma will not process an invoice instead. Ask which they need.

When the amount is disputed. Reissuing the same invoice into a disagreement does nothing. Send a plain statement of what was agreed, what was delivered and what is outstanding, settle the gap, then issue a corrected invoice referencing the old number.

And when you are being paid as an employee rather than engaged as a supplier — a real distinction with rules attached wherever you live. If a client asks you to invoice for work that looks like a job, ask your national revenue service before you accept.

Write your template once this week, with the eight lines and a placeholder for everything that changes. The first time you need one, you do not want to be designing it.