Invoicing Terms Every Designer Should Know

You finished a logo and brand kit. Now you have to bill for it, and the invoice form wants line items, a subtotal, a usage grant, and a few other words you half-know. Get them wrong and you either undercharge yourself or hand the client a reason to stall. Here is what each term means and how it lands on an actual design invoice.

Line item: one row, one thing you did

A line item is a single row on the invoice. It names one piece of work or one deliverable, shows the quantity and rate, and gives a line total. Nothing more.

The rule that saves you arguments: one line, one thing the client can point at. Not "design work, $4,000" as a single block. Break it out so the client sees what they paid for and AP sees what they are approving.

For a brand project, your line items might read:

• Logo design, primary and secondary marks, 1, $2,500, $2,500
• Brand color and type system, 1, $900, $900
• Social media template set, 6 templates, $120, $720
• Revision round beyond the two included, 1, $300, $300

Each row stands on its own. If the client questions the revision charge, it is isolated on its own line, not buried in a lump sum. Spelling this out is half of what belongs on a design project invoice.

Subtotal, discount, and total: the math in order

The subtotal is every line item added up before anything else happens. In the example above, that is $4,420.

A discount comes off the subtotal. Say you gave a returning client 10 percent off. That is minus $442, applied to the subtotal, not to any single line. Show it as its own line so the client sees the full price and the break you gave them. A hidden discount reads like a mistake.

After the discount comes tax, if you charge it, then the total. The order matters: lines, subtotal, discount, tax, total. Do it in a different order and the numbers stop reconciling, which is exactly the kind of thing an AP team checks before they release payment.

Usage rights: the term that decides your price

Design work is not just the file. It is what the client is allowed to do with the file. Usage rights (sometimes called a license or usage grant) define where the work can appear, for how long, and in what markets.

This is not a decoration on the invoice. It is the thing that justifies your number. A logo used on one local website is not the same deal as the same logo on national billboards for three years. Same file, very different price, because the usage is different.

Put the grant in plain words on the invoice, as its own line or a note under the line items. For example: "License: exclusive, worldwide, perpetual use of the primary logo for all brand and marketing purposes. Social templates licensed for the client's owned channels only." Now the client knows what they bought, and if they later want broadcast rights, that is a new line on a new invoice, not an argument. A designer invoice that spells out usage prevents the awkward call six months later.

If usage is restricted, say so. Telling the truth about what the license does and does not cover is cheaper than clawing back rights after the fact.

Payment terms, PO number, and the words AP wants

Three more terms show up on almost every design invoice headed to a company with a finance department.

Payment terms. This is the deadline, written as a convention. Net 30 means payment is due 30 days from the invoice date. Net 15 is 15 days. Due on receipt means now. Pick one, state it, and put the actual calendar due date next to it so nobody has to count.

PO number. A purchase order number is the code a client's finance team assigns to approved spend. Many AP departments will not pay an invoice that lacks one, even when the work is done and signed off. If your client works this way, get the PO before you invoice, or leave a clear spot for it.

Billing entity. The legal name and address the invoice is addressed to. The person who hired you is often not the entity that pays. Get this right or the invoice bounces back for a reprint.

The friction with these three is that they usually surface after you have sent the invoice. The client realizes they need a PO added, or their billing address was the wrong office. That is where a static PDF turns into an email chain.

Where this lands in practice

JupiterInvoice is built so the recipient can fix the parts that are theirs to fix. On an invoice link, the client can add a PO number, correct the billing entity and address, and name their AP contact, all without an account. You get notified, and you can revert anything that looks wrong. The line items, pricing, and usage terms stay yours: the client comments to ask, you decide.

That split matches how design billing actually works. You own the numbers and the license. The client owns their own paperwork. If you want to see it set up for the way studios bill, there is invoicing built for designers, and you can create an invoice free with unlimited sends. For the full vocabulary beyond these terms, the invoicing glossary covers the rest.

Write one clean invoice: clear line items, an honest subtotal, a usage grant in plain words, and the terms stated. That invoice gets paid. The vague lump-sum one gets questions.