Most payment issues start before the invoice is sent. Use this checklist to align contract terms, milestone triggers, and follow-up cadence.

This is an execution checklist, not a billing-policy guide. Use it after the invoice workflow rule is already clear. If you are still deciding when invoices should trigger, where billing status should stay visible, or how milestone completion should work, go back to Invoice and Payment Workflow Setup for Freelancers and Consultants first.

What this page is for

Use this page to run a billing process that already has defined triggers, ownership, and follow-up rhythm. It is for execution consistency once the underlying billing rule is settled.

What this page is not for

Do not use this checklist to decide your payment policy, redesign milestone acceptance, or choose where invoice truth should live. Those are broader workflow or stack decisions.

Start upstream first if…

  • you still debate what counts as invoice-ready,
  • delivery approval is still vague,
  • payment status disappears between tools,
  • the contract handoff still leaves billing triggers unclear.

Go back first to Invoice and Payment Workflow Setup for Freelancers and Consultants, Best Home for Billing Status: Invoicing Tool vs System of Record, or Proposal-to-Contract Handoff Workflow Setup.

What this checklist assumes you already know

  • what event actually triggers each invoice,
  • where payment status is authoritative,
  • who owns follow-up,
  • how billing connects back to delivery records.

If those rules are still vague, this checklist is too early.

Phase 1: Before work starts

  • Confirm invoice schedule in contract (deposit, milestone, final).
  • Confirm payment terms (for example net-7 or net-14).
  • Confirm accepted payment methods.
  • Confirm late-payment policy.

If these are unclear, fix contract handoff first: Proposal-to-Contract Handoff Workflow Setup.

Phase 2: Before sending each invoice

  • Confirm milestone acceptance criteria are met.
  • Confirm deliverable evidence is documented.
  • Confirm invoice amount matches contract scope.
  • Confirm due date and payment instructions are present.

Practical rule: if you cannot point to the event that triggered the invoice, you are already one step behind. Tie billing to a visible workflow event, not a vague sense that “it is probably time.”

Phase 3: Sending and tracking

  • Send invoice from one consistent system.
  • Log send date and due date immediately.
  • Add reminder dates at +3 days and +7 days after due date.

If you use a separate billing app, mirror payment state back to the record you check during delivery reviews so overdue invoices do not become invisible.

Phase 4: Follow-up rhythm

  • Reminder 1: friendly reminder after due date.
  • Reminder 2: direct reminder with updated status request.
  • Reminder 3: escalation note referencing contract terms.

Keep follow-up professional and structured, not emotional.

Phase 5: Payment closeout

  • Mark invoice paid in your system of record.
  • Reconcile payment to milestone and project record.
  • Confirm whether next invoice trigger is scheduled.

Short reminder copy pattern

Use a simple structure for payment follow-up:

  • what invoice is outstanding,
  • the original due date,
  • payment link or method,
  • request for status confirmation if payment timing changed.

The goal is clarity, not pressure in the first reminder.

Common payment workflow failures

  • Invoices sent without documented milestone completion.
  • Payment terms not confirmed before kickoff.
  • No reminder cadence (manual memory-based follow-up).
  • Inconsistent records between project and billing tools.

Edge cases to account for

  • If the client requires PO numbers or internal approval before payment, collect that before the invoice is triggered.
  • If part of the project is paused by the client, document whether billing pauses too or continues based on the contract.
  • If the client approves work informally in chat, log the approval in your system of record before invoicing.

Completion check

This checklist is complete only when:

  • invoice trigger is documented,
  • invoice status is visible,
  • follow-up dates exist,
  • the next billing event is already clear.

Safest next step after this checklist

If invoices are still being sent late or payment state still disappears, move back up a level and fix the billing rule in the workflow page or the billing-visibility decision page rather than running this checklist harder.