A Consultant Invoice for Fixed-Scope Work

You agreed a fixed fee for a defined engagement. Say, 12,000 dollars for a three-month strategy review. The work is done. Now the invoice has to say that clearly enough that the client's accounts payable team pays it without a single email back to you. That is the whole job of the document, and most consultant invoices fail it because they describe the work the way you talk about it, not the way AP reads it.

Here is the structure that gets a fixed-scope consulting invoice paid, part by part, with the wording that goes in each.

The header: who you are and what to call this invoice

Top of the page carries your business name, address, and tax identification (your EIN, VAT number, or local equivalent). Then the invoice number and issue date. These four things (your details, invoice number, issue date, and bank details lower down) do not change once you send. Lock them and forget them.

The invoice number matters more than it looks. AP files by number, and a duplicate or a gap creates questions. If you send more than a handful of invoices a year, set a format once and let it climb. A sequence like CONS-2024-018 reads fine to a human and stays sortable. If you have never thought about this, our take on invoice numbering best practices covers what to avoid.

Bill-to and the PO number that unblocks payment

The bill-to block names the legal entity paying you, not the person who hired you. "Acme Corp" and "Acme Holdings Ltd" are different entities to AP, and putting the wrong one on the invoice is a common reason it sits unpaid. Include the billing address the client's finance team uses, which is often not the office you worked in.

If the client runs purchasing through procurement, they issued a purchase order number. Put it on the invoice. No PO number on a PO-required account, and the invoice goes nowhere. If you did not get one, ask before you send, not after. The missing PO is the quiet killer here, and we wrote up how it stalls an otherwise clean invoice.

A practical problem with fixed-scope work: the client sometimes gives you the PO or the correct billing entity only after you have sent. On a static PDF that means a reissue. On JupiterInvoice the recipient can add the PO number and billing details themselves, and you get notified, so you are not retyping their own information for them.

The line items: describe the engagement, not the hours

This is where fixed-scope invoices differ from hourly ones. You are not billing time, so do not itemize by day. Bill by what you delivered.

For a single fixed fee, one line does the work:

Strategy review engagement, January to March 2024. Market analysis, competitive positioning, and 12-month roadmap. Fixed fee per signed statement of work dated 2 January 2024. 12,000.00

If the engagement had milestones or phases, split the fee across them so the client can match each line to what they signed off:

• Phase 1: Discovery and stakeholder interviews. 4,000.00
• Phase 2: Analysis and findings report. 4,000.00
• Phase 3: Roadmap and executive presentation. 4,000.00

Reference the statement of work or contract by date on the invoice. That one line ties your fee to something the client already approved, which is what stops a reviewer from asking "what is this for." If you billed a deposit at the start, show it as a negative line here so the balance is obviously the remainder, not a second full charge.

Anything outside the fixed fee (pre-agreed travel, a specific expense the contract allowed) goes on its own line, labeled plainly. Do not fold it into the fee. AP will want to see it separately, and so will you at tax time.

Totals, tax, and terms

Subtotal, then tax as its own line with the rate shown, then the total. If you charge VAT or GST, the rate and your registration number both need to appear or the invoice is not a valid tax document in most countries. For a rough sanity check on the arithmetic, the sales tax and VAT calculator handles a single line fast.

Payment terms go here in plain words: "Net 30" and the actual due date, spelled out. Do not make AP calculate it. "Payment due within 30 days of issue: 14 March 2024" leaves nothing to interpret. If you want the math done for you, the due date calculator gives you the date from the terms.

Payment details and how they pay

Bank name, account name, account number, and the routing detail your country uses (sort code, ACH routing number, IBAN and SWIFT for cross-border). Get these exactly right, because a wrong digit here is a payment that bounces two weeks later. If you invoice internationally, validate the account details before they lock onto the invoice.

If you want to offer card payment on top of bank transfer, connecting your own Stripe account lets the client pay from the invoice itself. JupiterInvoice does not hold your money; it presents your details and tracks the invoice from Sent to Viewed to Paid so you know where it stands without guessing.

Build it from a template that fits the engagement

You can lay all of this out by hand, but the fields are the same every time, so start from a consultant invoice template that already has the structure and fill in the engagement details. When you are ready to send it as a link the client can open, add a PO to, and pay from, create the invoice and skip the PDF loop entirely.

One last check before you send: run through the pre-send checklist. On a fixed-scope invoice, the two things that trip people up are the billing entity and the missing PO. Catch both now and the rest tends to pay on time.