What a graphic designer's invoice looks like
A design invoice has three kinds of lines: the design work (flat fee or by the hour), the usage rights and the costs you paid upfront on the client's behalf. The sample shows a corporate design for a bakery. The amounts are sample prices, not a fee recommendation.
| No. | Service | Qty | Rate | Amount CHF |
|---|---|---|---|---|
| 1 | Logo development: 3 concepts, 2 revision rounds | 1 | Flat fee | 2'400.00 |
| 2 | Final artwork and logo package (SVG, PDF, PNG, colour variants) | 1 | Flat fee | 450.00 |
| 3 | Letterhead and business card design | 6 h | 120.00 | 720.00 |
| 4 | Third revision round, extra as per quote | 2 h | 120.00 | 240.00 |
| 5 | Logo usage rights: exclusive, unlimited in time and territory, all media | 1 | Flat fee | 800.00 |
| 6 | Font licence, desktop and web, passed on at cost | 1 | 189.00 | 189.00 |
| Subtotal | 4'799.00 | |||
| VAT 8.1% | 388.72 | |||
| Total | 5'187.72 |
If you are not registered for VAT (under CHF 100'000 annual turnover), the VAT line disappears and the total is CHF 4'799.00.
What goes on the invoice:
- Your name and town, the client's name and town, invoice date and invoice number. For agencies, also their purchase order or job number, otherwise the invoice sits in their accounts department.
- Type and scope of the work: what you designed, how many concepts and revision rounds were included, and the period if it differs from the invoice date.
- Usage rights as their own line: non-exclusive or exclusive, for which media, which territory, for how long. Transferring one right only includes other partial rights if this was agreed (Art. 16 para. 2 Copyright Act, URG).
- Expenses kept separate: font licences, stock images, printing costs. Note whose name the licence is in.
- If you are VAT-registered: your VAT number, the VAT rate and the VAT amount (Art. 26 para. 2 VAT Act, MWSTG).
- QR payment slip and payment term, so the client pays by scanning it in their e-banking.
If you deliver AI-generated visuals, describe on the invoice which files the client receives and what they may use them for. That avoids arguments about the scope later.
