How to set payment terms on an invoice as a consultant
Generic NET 30 clauses won't protect you when you're billing a $18k monthly retainer to a US corporate. Here's how to set payment terms that actually get enforced.
You sent a $15,000 invoice to a Fortune 500 procurement department. Your terms said "NET 30." Their purchase order said "NET 60 from receipt of approved invoice." Sixty-three days later, you're still waiting. Setting payment terms on an invoice is not a copy-paste exercise — it's a negotiation you mostly lose after the contract is signed if you haven't thought it through upfront.
This guide is for solo consultants billing high-value retainers and project work, often across currencies, often to clients whose AP departments treat your invoice like a utility bill. Here's how to set terms that hold up.
Understand what "payment terms" actually control
Payment terms define three things: when the clock starts, when payment is due, and what happens if the client misses it. Most consultants only think about the middle one.
When does the clock start?
"NET 30" is ambiguous on its own. NET 30 from what? Invoice date? Delivery date? The date procurement stamps it approved? US corporates often interpret it as "30 days from when we process it internally," which can add 7–14 days before the clock even starts.
Fix it with specificity. Write: "Payment due 30 days from invoice date." That one phrase removes the ambiguity that costs you two weeks every cycle.
The deposit trigger is your most powerful tool
For project work, a deposit is not just a cash flow gesture — it's a signal-to-noise filter. Clients who won't pay 30–50% upfront are clients who will dispute the final invoice.
A practical structure for a $20,000 strategy engagement:
- Invoice 1: $7,000 deposit, due on contract signature (Net 0 / Due on receipt)
- Invoice 2: $7,000 milestone invoice, due when deliverable 2 is approved
- Invoice 3: $6,000 final, NET 14 from final delivery
The milestone trigger on Invoice 2 is critical. Don't tie it to a date — tie it to an approval. Otherwise you absorb the client's internal delay.
Late fees: write them in, enforce them selectively
A 1.5% monthly late fee is standard and legally enforceable in most jurisdictions. The point is not to collect it — it's to give you leverage. When a payment is 45 days overdue, you can waive the fee in exchange for immediate payment. Without the clause, you have nothing to waive.
Include: "Invoices unpaid after [due date] accrue interest at 1.5% per month (18% per annum)." Check your jurisdiction — some countries cap the rate or require it in the contract, not just the invoice.
How to set payment terms when you're billing across borders
This is where generic advice falls apart. If you're a European consultant billing a US corporate in USD, or a US consultant billing an EU enterprise, you're dealing with two layers most guides ignore: currency and VAT.
Multi-currency payment instructions
If your invoice is in USD but your bank account is in EUR, you need to be explicit. Clients should not be guessing conversion rates or SWIFT fees. Specify:
- The invoice currency (USD)
- The receiving account details (wire to your USD account, or SEPA in EUR at today's rate)
- Who bears the transfer fee ("Client covers all wire transfer and intermediary banking fees")
If you accept multiple payment methods — ACH for US clients, SEPA for EU clients, or even Alipay for APAC — list them on the invoice itself. Ambiguity here is a real delay.
Reverse-charge VAT and payment terms in the same breath
EU B2B invoices add a compliance layer that payment terms clauses can't ignore. If you're a VAT-registered consultant in Germany billing a French company, you apply reverse-charge VAT: zero VAT on the invoice, with a note that the client accounts for VAT under Article 196 of the EU VAT Directive.
That note must appear on the invoice alongside your payment terms, not buried in a footer. Why? Because AP departments at large companies route VAT-exempt invoices through a different approval path. An invoice that looks like it's missing VAT (rather than correctly applying reverse-charge) gets kicked back to "pending review," and your NET 30 clock never starts.
How most consultants set payment terms
- Copy "NET 30" from an old invoice template and hope the client interprets it the same way.
- Add bank details in a footer note that often gets cut off when the client prints or exports.
- Chase overdue invoices manually with a fresh email every time.
- Add VAT notes as a text footnote with no enforcement, easy to miss.
- Reconcile multi-currency retainers in a spreadsheet at month-end.
How ZenPay does it
- Payment terms presets (Due on receipt, NET 7/14/15/30/45/60/90, or custom days) applied per invoice so the due date is always calculated from invoice date, unambiguous.
- Bank accounts, SEPA, ACH, and wire details added as named payment methods that print cleanly on every invoice automatically.
- Auto-reminders fire N days before and after the due date in your name, with an editable template, so the clause enforces itself.
- Reverse-charge VAT toggle on each invoice adds the legally required note and sets VAT to zero for EU B2B without manual editing.
- Multi-currency wallets show retainer totals per currency (USD, EUR, GBP) so you always know what's outstanding without a spreadsheet.
Negotiating terms with corporate procurement
Here's the uncomfortable truth: if a company's standard is NET 60 and your contract says NET 30, procurement will pay in 60 days and you will spend two emails explaining your terms to someone who does not have the authority to override AP policy.
Strategies that actually move the needle:
- Escalation contacts. Get the name of the AP manager and the budget owner (usually your day-to-day sponsor) at contract signature. CC both on invoices.
- Early payment discount. Offer 2/10 NET 30: 2% discount if paid within 10 days, full amount at 30. Some corporates have authority to take early-payment discounts that they don't have to override NET 60 terms. You lose 2% but gain 50 days of cash flow.
- Anchor your retainer invoices to a fixed calendar date. "Invoice delivered on the 1st, due on the 30th of the same month" is cleaner than "NET 30 from delivery" because it maps to their monthly AP run.
The clause and the enforcement are two different problems
Writing "NET 30" on an invoice is the easy part. The hard part is what happens on day 31. Most consultants send a polite email. The client says they'll look into it. You follow up three days later. They say it's in the queue.
The enforcement gap is not a relationship problem — it's a process problem. Auto-reminders solve it without you being the one who has to choose between being professional and being direct. When a system sends a reminder in your name three days before the due date and again on day 7 overdue, it's not nagging — it's running your accounts receivable policy.
Set the terms clearly, invoice on a predictable schedule, and let the reminders run. That combination closes the gap between what your contract says and what actually lands in your account.
Less admin.
More of what matters.
Your first invoice
within 2 minutes.
Keep reading
How to write a milestone invoice for a branding project
Stop chasing "after launch" payments. Structure your branding project into four clear billing milestones and write invoices that get paid before the next phase starts.
How boutique travel agencies handle FX risk on client deposits
Holding a 25–50% client deposit in EUR while owing suppliers in THB or USD is a slow cash leak. Here's how to shrink that FX window without a hedging desk.
Sponsored newsletter math: how creators bill list-based deals
Billing a newsletter sponsorship isn't like invoicing a video deal. Here's how to price, structure, and invoice list-based brand partnerships so procurement pays on time.