How to Create an Invoice: A Practical Guide

To create an invoice, list your details, the client's details, a unique invoice number, the issue date and a due date, line items with descriptions and amounts, the subtotal, any tax, the total, and how to pay. An invoice is the formal request for payment after the work is done, separate from a quote or a receipt.

I used to think the email mattered more than the PDF. The PDF is what finance files, forwards, and pays against. If you are figuring out how to create an invoice for the first time, start from that: you are giving someone else a clean story their system can accept. A year in, I wish I had stopped treating the invoice like a formality. I would send friendly paragraphs and bury the total at the bottom. What worked was a dull page with the same fields every time, sent the same day the work stopped dragging.

What goes on an invoice?

An invoice carries your details, the client's details, a unique sequential invoice number, the issue date, the due date, one line per item with a description, quantity, rate, and line total, the subtotal, any tax, the total, and payment instructions. Add the currency when you bill across borders. Every field exists so accounts payable can match it to their records.

Your details first: the name you trade under, email, and enough address that a stranger could mail you. If you are VAT registered, put the number on there. Clients in the EU often need it before they can process you at all.

Theirs next: company name, contact name, and billing address. If you are sending to a person, still list how they want their name and address to read. Accounts payable does not pay vibes; they pay what matches their vendor record.

Invoice number and dates. The number should be unique and sequential. The issue date is when you send it. The due date is when you expect the money. Line items: one row per thing you are charging, with a plain description, quantity, rate, and line total. Subtotal, then tax if it applies, then the total. Payment instructions: bank details, PayPal, or whatever you actually use. If they have to reply to ask how to pay, you have already lost a week.

Add a currency if you work across borders. If one line is in hours and another is a flat fee, say so in the description column, not only in your head. A notes field is fine for "PO reference 77821" or "per agreement dated Feb 2." Keep the story short. Long essays in the footer get skipped.

That list covers almost every first freelance job. The shape stays the same whether you are billing like a photographer with a shoot fee and editing hours, or a graphic designer with concepts and final files. Tradespeople doing emergency callouts often split labor and parts the same way on a plumber style bill. Later, if you hand monthly PDFs to a bookkeeper, they will hug you for line items that already match your bank feed. The labels change; the structure does not.

How do you number invoices?

Pick a prefix and a counter, then never skip or reuse a number: INV-001, INV-002, or 2026-001, 2026-002. Gaps look like errors or fraud to an auditor. To correct an amount, do not reuse the old number; issue a credit note or a fresh invoice number with one line pointing back to the original.

Gaps also make you sound unsure when you say "the invoice after the one I sent in March." I restart the year sometimes with 2026-001 so I can find things fast. You do not need a fancy system. You need a rule you will not break.

Some tools label the correction "CN-006" or "INV-014-R." Pick a pattern and stay consistent.

Here is a concrete example. Say you trade as Northline Edit Studio. Your first invoice to Cascade Retail Co. might be NE-2026-014, dated March 3, with one line: "Spring campaign copy deck, rounds one to two," quantity one, rate $2,450. Subtotal $2,450, tax line if your jurisdiction needs it, total $2,450, due March 20. That is boring on purpose. Boring is what gets paid.

How do you set payment terms?

Payment terms set when you expect the money, counted from the invoice date unless you say otherwise. "Net 30" means thirty days; spell it out or give a calendar date so nobody guesses. Match the term to the client: net 30 or 45 for corporate procurement, net 7 to 14 for small jobs, net 15 for familiar monthly work.

"Due on receipt" sounds firm but people interpret it differently, so I prefer a calendar date or net 14 or net 30 spelled out. Creative work that goes through a marketing department often lands on net 30 or net 45 because procurement moves slowly. Smaller jobs for individuals might be net 7 or due within two weeks. Retainer or web developer style monthly work is often net 15 from invoice because the scope is already familiar.

If you need a deposit, say it before the work starts, then repeat the same schedule on the invoice. First invoice: 40% deposit, balance on delivery. Second invoice: remainder tied to a specific deliverable. Do not invent new terms on the PDF that you never mentioned in email. That is how you get a five-day argument instead of a transfer.

How do you handle milestones?

Milestones help when a job runs longer than a month. Name the milestone in the line item, not only in your contract. "Milestone two: wireframes approved" reads clearer than "phase two" to someone who did not sit in your meetings. If the client slips the approval, your due date should still point to something you can prove, like file delivery, not their internal signoff unless they agreed to that in writing.

What mistakes delay invoice payment?

The biggest delay is missing payment details: a total with no IBAN. Vague line items come next, since "Consulting, $4,000" makes a buyer reopen the thread. Wrong or missing purchase order numbers stall corporate pay runs. Sending the wrong total after a scope change traps you too, and late invoicing pushes your own cash date back.

Missing payment details is the big one. You would be surprised how many first invoices go out with a total and no IBAN. Vague line items are the next. "Consulting" for $4,000 makes a buyer open the thread again. "Workshop facilitation, Feb 12, eight hours at $500" does not. Wrong or missing purchase order numbers stall corporate pay runs. If they gave you a PO, put it on the line where they expect it.

Sending the wrong total after a last-minute scope tweak is another trap. Update every line that changed, then update the total, then read the number out loud once. Attachments matter: a password-protected PDF with no password in the email costs you two days.

Late invoicing hurts you more than late payment. Every day you wait to send the bill pushes your cash date back. Send it the day you finish, or the day the milestone clears, not when you feel composed.

How do you send an invoice?

Email still wins. Use a clear subject line with the invoice number and your business name, then three short sentences: you are attaching the PDF, the total, the due date, and one line on how to pay. Attach a single PDF with a sensible filename, and copy both the person who signs and the person who pays.

A concrete subject line reads "Invoice NE-2026-014 from Northline Edit Studio." Ask them to confirm receipt if their process requires it, and name the file something sensible, not "final_final_v3.pdf."

A usable body sounds like this: "Hi Sam, please find invoice NE-2026-014 for $2,450, due March 20. Bank transfer details are on page one. Let me know if you need anything else from my side." That is it. You are not pitching again; you are handing them a ticket they can forward.

If you work like a business consultant with long engagements, copy the person who signs and the person who pays. If you only copy your friendly contact, the invoice can sit in their personal inbox while AP never sees it.

What should you do when an invoice is not paid?

First, confirm you sent it to the right address and that the due date has truly passed. Then send a short reminder quoting the invoice number and amount, since most late payers are simply busy. If silence continues, call or send a firmer email, mention any contractual interest, and keep a paper trail of invoices, reminders, and delivery.

Before you panic, check you sent it to the right address and that the due date has actually passed. Then send a short reminder that quotes the invoice number and amount. Most late payers are buried in work, not stealing from you. If silence continues, pick up the phone or move to a firmer email that still sounds human, the way chasing an unpaid invoice lays out step by step. After that, your options depend on jurisdiction and how much you are owed. Small claims, a collections letter, or walking away all hurt. You still want a paper trail: numbered invoices, dated reminders, proof of delivery.

If your contract allows late fees or interest, mention them once you are past the polite reminder stage, not as a threat in the first ping. People respond better to "Invoice NE-2026-014 is ten days past due. Can you confirm payment date?" than to instant penalty language. Save the heavier wording for when you have repeated silence.

I keep a spreadsheet of invoice number, client, amount, sent date, due date, and paid date. That habit cost me ten minutes a month and saved me hours of guessing.

You do not need perfect language on day one. You need a complete PDF, a clear due date, and instructions that make paying you the path of least resistance. Everything else you can tighten as you go.