Writing an invoice sounds simple until you’re staring at a blank page trying to remember what actually needs to go on it, and whether “please pay within 30 days” sounds too aggressive or not aggressive enough for this particular client.
Here’s a straightforward way to think about it: an invoice has to do two jobs at once. It has to give the client every piece of information they need to pay you without asking a follow-up question, and it has to set the right tone so paying feels like the obvious next step rather than something to think about later.
The Core Structure
Every invoice, regardless of industry or client type, needs the same seven components:
- Your business information and the client’s information
- A unique invoice number
- The invoice date and a specific due date
- An itemized list of what’s being billed
- The total amount, with tax shown separately if applicable
- Payment terms and accepted methods
- Any notes, including late fee policy if you have one
The order rarely matters much. What matters is that none of these are missing, because a missing field is usually what turns a same-day payment into a week-long email exchange.
Writing the Line Items: Specific Beats Vague
This is where most invoices actually go wrong, not in the formatting, but in the wording of what’s being billed.
The second version tells the client exactly what they’re paying for and gives them something to check against their own notes or contract. If a client’s accounts payable department needs to route the invoice for internal approval, which is common at any company larger than a handful of people, a vague line item is often what gets an invoice bounced back with a request for more detail, adding days to your payment timeline for no real reason.
For project-based work with multiple phases, break out each phase as its own line rather than bundling everything into one lump sum:
| Website redesign, discovery phase | $800 |
| Website redesign, wireframes and design | $1,200 |
| Website redesign, development | $2,400 |
| Revision hours beyond scope (4 hrs) | $300 |
This also protects you if a client questions the total later. It’s much easier to point to a specific line than to defend one large number.
Setting the Tone: Wording for Different Client Types
The core information on an invoice shouldn’t change based on who you’re billing, but the surrounding language reasonably can.
For an established corporate client, keep the tone neutral and formal. Something like:
“Please remit payment by the due date above. Questions regarding this invoice can be directed to [email].”
For a smaller business or long-term client you have a more personal relationship with, a slightly warmer note is fine and often helps:
“Thanks again for the project, this was a fun one. Let me know if anything needs adjusting before the due date.”
For a new client on their first invoice, it’s worth being explicit about payment methods even if it feels slightly redundant, since they haven’t paid you before and don’t yet have a habit or process for it:
“Payment can be made via the link above, or by bank transfer to the details attached. Let me know if you’d prefer a different method.”
In every case, the goal of the note is the same: remove any reason for the client to hesitate or ask a clarifying question before paying.
Handling Due Dates and Payment Terms Clearly
“Net 30” is standard shorthand, but shorthand invites ambiguity. Does the 30 days start from the invoice date or the date the client actually received it? Most of the time this doesn’t matter, but occasionally it becomes a real few-day gap, especially with clients who are looking for any reason to delay.
Remove the ambiguity by stating both:
A specific date is something a client can put directly into their own calendar or accounts payable system. A term alone requires them to do math first, and anything that requires an extra step is one more small reason a payment slips.
A Full Example, Put Together
Here’s what a complete, well-written invoice actually looks like once every piece above comes together:
The PDF looks exactly like the example below. The Word version is formatted for easy editing, so minor spacing differences are normal there.
[email protected]
Date: July 21, 2026
Due Date: August 4, 2026
| Description | Total |
|---|---|
| Brand identity package, logo + guidelines | $1,800 |
| Business card and letterhead design | $350 |
| Subtotal | $2,150 |
| Tax (0%) | $0 |
| Total | $2,150 |
Payment Methods: Bank transfer, card, [payment link]
Late Fee: 1.5% per month on balances past due
Thank you for the opportunity to work on this project. Please reach out with any questions before the due date above.
Nothing here is complicated. It’s specific, it’s complete, and it gives the client no reason to write back with a question before they can pay.
Writing Invoices at Scale
Writing one invoice carefully is manageable. Writing a good one every time, for every client, while also tracking who’s paid and following up on who hasn’t, is where manual invoicing starts to break down. At that point, the writing itself doesn’t need to change, the structure and wording above still apply, but the process of generating, sending, and tracking it benefits from being automated rather than rebuilt from scratch each time. Here’s what that looks like in practice.