A professional invoice should make three things clear: who is billing, what was delivered, and when and how payment is expected. This guide provides a reusable invoice required fields checklist, practical templates by billing scenario, and a framework for choosing invoice payment terms that fit freelance, startup, retainer, subscription, and milestone work.
Overview
An invoice is both a payment request and a business record. It should give the client enough information to approve the charge, send payment correctly, and match the transaction to a contract, purchase order, or project. It should also give you a consistent record for bookkeeping, follow-up, and future financial reviews.
The exact invoice requirements can vary by country, tax status, industry, and client type. Before sending an invoice, check the rules that apply to your business and customer. Treat the checklist below as a practical baseline rather than a substitute for local accounting or tax advice.
Professional invoice checklist
- Invoice label and number: Use a clear title such as “Invoice,” plus a unique sequential invoice number. Choose a numbering system you can maintain across projects and billing periods.
- Issue date: Record the date the invoice was created. For recurring or delayed billing, also state the service period when relevant.
- Seller details: Include your legal name or registered business name, trading name if different, business address, email address, and another practical contact method.
- Client details: Add the client’s legal or billing name, billing address, contact person, email, and purchase order or project reference when one is required.
- Description of work: Identify the service, deliverable, product, or subscription clearly. Avoid descriptions such as “work completed” when a more specific explanation is possible.
- Dates and quantities: For hourly work, list dates or a billing period, hours, and rate. For fixed-fee work, identify the deliverable or milestone. For products, include quantity and unit price.
- Subtotal and adjustments: Show the subtotal before tax, discounts, credits, deposits, or other adjustments. Explain any unusual adjustment briefly.
- Tax details: Show applicable taxes separately when required, including the relevant rate or registration information where appropriate. Confirm the treatment before sending the invoice.
- Total due: Make the final amount prominent and use the correct currency. If the amount has already been partly paid, show the deposit or credit and the remaining balance.
- Payment instructions: State accepted payment methods and provide the exact information needed, such as a payment link, bank details, account reference, or instructions for card payment.
- Due date and terms: Include both a specific due date and plain-language terms, such as “Payment due within 14 days of the invoice date.”
- Notes and attachments: Add a short thank-you or project note if useful, and attach timesheets, milestone approvals, or expense records when the agreement calls for them.
Keep the visual hierarchy simple. The client should be able to find the amount due, due date, payment method, and invoice reference without searching through a dense page.
Checklist by scenario
Freelance project invoice
For a one-off freelance assignment, connect the invoice to the agreed scope. Name the project, summarize the deliverables, and list any approved expenses separately. If the work was billed hourly, show the rate and hours rather than only presenting a combined total. Reference the contract or statement of work if the client uses one.
A suitable payment instruction might be: “Please pay the total shown by the due date below. Include invoice 2025-014 as the payment reference.” Use your actual numbering system rather than copying this example.
Retainer invoice
A retainer invoice should identify the coverage period, such as a calendar month, and explain what the retainer includes. If unused hours roll over, expire, or are billed separately, state that in the contract and use the invoice note to point back to the agreed arrangement. Additional work outside the retainer should appear as a separate line item.
Subscription or recurring invoice
For recurring services, show the subscription name, billing period, renewal or service dates, amount, and cancellation or change instructions that were agreed with the client. If payment is collected automatically, state that clearly and identify the payment method or billing reference without exposing sensitive payment details.
Milestone invoice
For a staged project, label the milestone precisely: for example, “Design approval milestone” or “Phase two delivery.” Include the milestone amount, approval date if relevant, and the remaining project balance when that context helps the client. A milestone invoice should not imply that the full project is complete if later stages remain.
Deposit or upfront invoice
Identify the charge as a deposit, advance payment, or initial installment according to the contract. Explain how it will be applied to the project and whether it is refundable, subject to the terms that govern the engagement. Later invoices should show the deposit as a credit or previously paid amount when appropriate.
Startup vendor invoice
Startups often need invoices that pass through a finance or procurement workflow. Ask for the client’s legal billing entity, purchase order requirements, approval contact, required references, and preferred file format before billing. A correct invoice sent to the wrong entity can still be delayed.
Comparison of common payment terms
| Term | How it works | Best suited to | Check before using |
|---|---|---|---|
| Due on receipt | Payment is requested as soon as the invoice is received. | Small, completed jobs or clients with a fast approval process. | Whether the client’s process permits immediate payment. |
| Net 7, 14, or 30 | Payment is due a stated number of days after the invoice date or another agreed event. | Ongoing business relationships and standard project billing. | Whether the clock starts at issue, delivery, or acceptance. |
| Deposit plus balance | A portion is paid before work, with the remainder due at a defined stage. | New projects with setup costs or reserved capacity. | The deposit amount, application, and cancellation terms. |
| Milestone billing | Invoices are issued after specific deliverables or approvals. | Longer projects with clearly separated phases. | How completion or acceptance will be documented. |
| Recurring payment | A scheduled charge repeats for an agreed service period. | Retainers, subscriptions, and maintenance services. | Renewal, cancellation, failed-payment, and price-change procedures. |
| Late-fee provision | An agreed charge or interest may apply after the due date. | Businesses that need a clear overdue-account process. | Contract terms and applicable local rules before adding it. |
What to double-check
Before sending a professional invoice, compare it against the agreement, proposal, or purchase order. Confirm that the client name and legal entity match, the work description reflects the approved scope, and the totals reconcile with your calculations.
- Dates: Check the issue date, service period, milestone date, and due date. Do not rely on a generic “net 30” label alone when a calendar date is clearer.
- Arithmetic: Recalculate quantities, rates, discounts, taxes, deposits, and the final balance. A pricing or spreadsheet formula should be reviewed when the invoice contains multiple adjustments.
- Currency: Confirm that the currency matches the agreement and payment account. Make the currency visible wherever an amount appears.
- Tax treatment: Verify whether tax should be charged, shown separately, or handled another way for the transaction. Keep supporting records for your own review.
- Payment route: Test links and confirm that bank details are current. Send sensitive payment information through an appropriate secure channel.
- File and accessibility: Use a stable file name, such as “BusinessName-Invoice-Number,” and provide a readable PDF or the format requested by the client. Ensure text can be selected and read by common assistive tools when possible.
- Recordkeeping: Save the invoice, agreement, approvals, receipts, and payment confirmation together in a consistent folder or accounting workflow.
Common mistakes
The most avoidable invoicing problems are usually process problems rather than design problems. Sending an attractive freelance invoice without a clear due date does not make collection easier. Similarly, adding a late fee after the fact can create friction if it was not included in the agreement.
- Using vague line items that make the client ask what was delivered.
- Changing payment terms on the invoice without discussing the change first.
- Sending a recurring invoice with no service period or subscription reference.
- Mixing personal and business payment details without explaining the account name.
- Reusing an invoice number or leaving a draft invoice in the numbering sequence without a record.
- Including sensitive card or banking information in an unnecessarily exposed location.
- Ignoring the client’s purchase order, portal, naming, or file-format requirements.
- Failing to follow up because there is no reminder date or overdue workflow.
Keep a short written policy for payment terms, deposits, reminders, and overdue accounts. Apply it consistently, while allowing documented exceptions for specific clients or projects.
When to revisit
Review your startup invoice template before each new type of engagement and whenever your workflow changes. A freelance invoice template that works for hourly work may not contain enough detail for a subscription, international client, milestone project, or expense-heavy assignment.
Schedule a broader review before a new financial year or seasonal planning cycle, after changing payment platforms, when you introduce a new service or currency, and whenever a client’s procurement requirements change. Recheck tax fields and payment language when your business registration, location, or customer mix changes; local requirements may differ.
For a practical final pass, duplicate your current template, remove the sample values, and test it against one real scenario: a completed project, a monthly retainer, or an unpaid invoice. Confirm that another person could identify the payer, payee, service period, amount, due date, and payment method without asking a follow-up question. Then save the approved version with a clear date or version label and use it consistently until the next review.