What Belongs on a Design Project Invoice

· 5 min read

A design invoice fails for boring reasons. The PO number is missing. The line item says "Design work, June" and the AP clerk has no idea which project that maps to. The bill is addressed to the founder's personal email instead of the billing entity in the client's accounting system. None of this is about your work. It is about the document. Below is the structure that holds up under scrutiny, with the wording to use in each field.

The header: who is billing whom, and which invoice this is

The top of the invoice answers three questions in under two seconds: who is this from, who is it to, and which invoice are we talking about. Put your studio or freelance name, address, and tax ID (VAT number, ABN, EIN, whatever applies in your country) on the left. On the right: the word Invoice, an invoice number, an issue date, and a due date.

Use a numbering scheme you can defend. 2024-0142 beats INV-7 because it is sortable and shows continuity. If you are still picking a format, the post on how to design an invoice numbering system that scales walks through the trade-offs. Keep the scheme stable. Skipping numbers or restarting at the new year creates audit questions you do not want.

Underneath, the bill-to block. Use the client's legal billing entity, not the trading name on their website. "Northwind Studios Ltd, 14 Old Street, London EC1V 9BX" is correct. "Northwind" is not. If your contact at the client has already told you they need a purchase order number, it goes here, prominently. AP teams that require POs will reject anything without one, and you will lose two weeks finding out.

Line items: describe the deliverable, not the activity

This is where most design invoices go wrong. "40 hours design" tells AP nothing. "Brand identity sprint, week 2 of 3" tells them what they are paying for and ties it to the contract.

Write each line item in this shape: deliverable, scope marker, quantity, unit, rate, amount. Concrete examples:

  • Logo exploration, three directions, fixed fee, 1, project, 2,400.00, 2,400.00
  • Brand guidelines document, 24 pages, fixed fee, 1, project, 3,800.00, 3,800.00
  • Web design revisions, round 3 (out of contracted 2), hourly, 6.5, hours, 140.00, 910.00
  • Stock photography license, pass-through cost, 1, license, 320.00, 320.00

Notice the third line names the round and flags that it is beyond the contracted scope. That preempts the email asking why this charge exists. If a client questions a line, you are debating one row, not the whole invoice. For mid-project billing, the article on progress billing stage by stage covers how to split a fixed fee across milestones cleanly.

Below the line items, three rows: subtotal, tax (with the rate shown, for example "VAT 20%"), and total. If you are billing in a currency other than your home currency, state the currency code (USD, EUR, GBP) next to every amount. "$2,400" is ambiguous across half the world.

Payment terms and bank details: leave nothing to interpretation

Payment terms go in their own block, not buried in the footer. Write the term and the date: "Net 30. Due 14 August 2024." If you are unsure which term to set, the guide to net 30 payment terms explains how clients actually interpret them.

Then bank details. For a domestic US client: account name, ACH routing number, account number. For a European client paying in EUR: account name, IBAN, BIC/SWIFT. For a UK client in GBP: account name, sort code, account number. If you take card, list a payment link separately and note the surcharge if you pass one on. Do not list five payment methods and let the client guess. Pick the cheapest method for you and lead with it.

Add a late fee line only if your contract says so. "A late fee of 1.5% per month applies to balances unpaid after the due date" is clear. Vague threats are worse than none.

The fields clients always want to change

Design clients edit invoices. They add a PO after the fact, swap the billing entity from the parent to a subsidiary, or want a different AP email on file. With a static PDF, every one of those turns into a back-and-forth thread and a V2 attachment. With invoicing built for designers, the recipient opens a private link, adds the PO number themselves, updates the billing address, and forwards it to their AP contact. You get notified and can revert anything that looks wrong. The invoice number and your bank details stay locked.

If a client wants to change pricing, currency, or payment terms, that becomes a tracked change request you approve or decline, and approval creates a new version. The difference between an amendment and a new version is covered in the piece on invoice versions versus amendments.

The footer: small print that protects you

The footer holds the things nobody reads until something goes wrong. Your tax ID again, your registered company number if you have one, a one-line refund or revision policy, and a contact for billing questions. If you sell internationally, state who pays bank transfer fees: "All bank charges, including intermediary fees, are payable by the remitter (OUR)." That single sentence has saved more invoices from short-payment than any clever email.

A reusable starting point

If you want to skip building this from scratch, grab the graphic designer invoice template and adapt the line item wording above. When you are ready to send something the client can interact with rather than a flat PDF, create the invoice and send the link. The structure stays the same. The friction goes away.

Send an invoice your customer can actually respond to

JupiterInvoice lets recipients add PO numbers, update billing details, request changes, and approve for payment, all from a private link. No account needed on their side.

Create an invoice