Client Invoicing SOP Template

Purpose & Scope

This section defines what the SOP covers and who it applies to: every retainer, project-based, and time-and-materials engagement your business bills. It states the objective in one line, generating accurate invoices and collecting payment on time without relying on any single person's memory, so a new hire or a covering teammate can run the entire invoicing cycle from this document alone. Most teams also note here which entities or subsidiaries the SOP applies to if the agency bills through more than one legal entity, and which accounting software (QuickBooks, Xero, or your own platform) the procedure assumes. Keeping this section tight, ideally under 100 words, means anyone opening the document for the first time understands the boundaries before they read a single step.

Roles & Responsibilities

List every role touching the invoicing cycle and what each one owns: the Account Manager confirms scope, rate, and billing trigger with the client before an invoice is drafted; the Finance or Billing Owner generates, sends, and reconciles the invoice and runs the late-payment escalation ladder; and the Agency Owner or Finance Lead approves any write-off, credit, or payment-plan exception above a set threshold. Naming individuals, not just titles, inside the live document removes the most common failure mode in small teams: an invoice that never goes out because everyone assumed someone else owned it. If your business is a solo operation, this section still matters. It forces you to decide, in writing, when you'll pause client work versus when you'll extend grace, before a real overdue invoice puts you in a stressful, reactive spot.

Invoice Generation Procedure

This is the operational core: confirm the billing trigger (a fixed retainer date, a signed-off milestone, or logged hours), assign a sequential invoice number, apply the client's purchase order or reference number if they require one, and itemize every line with the service, quantity or hours, rate, tax, and billing period. A short internal review step, someone other than the invoice creator checking totals and terms before it reaches the client, catches the two most common errors: a wrong rate carried over from an old contract, and a milestone billed before it was actually approved. Documenting the exact fields every invoice must include also makes it far easier to batch-generate invoices in bulk billing cycles, since every team member fills in the same template rather than improvising layout and detail level invoice by invoice.

Retainer vs. Milestone Invoicing

Most invoicing SOPs treat every invoice as the same event, but retainer and milestone billing behave differently and deserve separate rules. Retainer invoices go out on a fixed calendar date regardless of that period's deliverable status, since the client is paying for ongoing capacity, not a specific output. Milestone and project invoices, by contrast, should never be issued before the linked deliverable is marked approved, in writing or inside your project tracker, because billing ahead of approval is one of the fastest ways to trigger a payment dispute and damage trust. This section should also cover partial-milestone billing (for example, 50% on kickoff and 50% on delivery) and how change orders that shift scope get re-quoted and re-approved before the next invoice reflects the new total.

Sending & Delivery Terms

Define exactly how and from where invoices are sent (a dedicated finance address, CC'd to the account manager so nothing lives in one inbox), the default payment terms your business uses (Net 15 is the most common default for agencies, though Net 30 is standard for enterprise clients), and a same-day rule for confirming the client actually received it, by portal read-receipt, email open, or a quick reply. Stating the due date explicitly on the invoice itself, rather than leaving the client to calculate it from the terms, measurably reduces late payments because it removes any ambiguity a client could use to justify a delay.

Late Payment Escalation Ladder

This is the section most invoicing SOPs, and most competitor templates found online, leave dangerously vague: a single line that says "follow up on overdue invoices" with no timeline or tone guidance, which is exactly why so many teams either chase too aggressively too soon or let a balance drift for months out of discomfort. A concrete, day-by-day ladder removes that guesswork. Day 0 (the due date) triggers an automated, friendly reminder with the invoice reattached. Day 7 overdue moves to a direct, personal email from the account manager asking if anything is blocking payment. Day 14 overdue adds a phone or video call plus written confirmation of a firm new payment date. Day 30 overdue becomes a formal notice that references the contract's late-payment clause and pauses new deliverables until the balance clears. Day 45+ overdue escalates to the Agency Owner or Finance Lead to decide between a structured payment plan, a collections referral, or a full work stoppage. Documenting the exact tone and channel at each stage, not just the timing, is what actually protects client relationships during a collection process, because every team member sounds consistent and nobody has to improvise a difficult conversation from scratch.

Disputed Invoices & Credits

A disputed line item should never freeze an entire invoice or reset the escalation clock on undisputed charges. This section instructs the team to log every dispute the same day it's raised, pause escalation only on the specific disputed line, and resolve it or issue a credit note within a set window, five business days is a reasonable default for most agencies. Everything else on that invoice remains payable on its original due date. Without this rule, a client can indefinitely delay an entire payment by disputing a single small line item, which is a common, and sometimes deliberate, cash-flow tactic worth explicitly closing off in writing rather than discovering it live with a real client.

Reconciliation & Record-Keeping

Define how quickly a payment gets marked in your accounting system after it clears (one business day is a reasonable standard), how long signed invoices, payment confirmations, and dispute threads are archived (many businesses default to seven years for tax and audit purposes), and how often outstanding accounts receivable get reconciled against your project tracker so a milestone marked "invoiced" actually matches a real invoice number and status. A weekly reconciliation cadence catches the invoices that quietly fell through the cracks, sent but never followed up on, before they age into an uncomfortable conversation with a client three months later.

Compliance & Version History

Every SOP goes stale the moment tax rates, payment terms, or your billing platform change, so this section names who owns quarterly review (typically the Finance/Billing Owner) and requires a version log, date, author, and a one-line summary of what changed, at the bottom of the live document. This matters more than it sounds: when a new hire questions why the SOP says Net 15 but a specific client contract says Net 30, the version history and the linked contract are what resolve the ambiguity instead of a guess.