How to Write SOW Payment Terms That Actually Get Paid

Most SOW payment terms are written to get the contract signed, not to get the invoice paid.

In most enterprise IT consulting engagements, the heavy lifting on payment terms lives in the Master Services Agreement — net terms, late fees, dispute resolution. The SOW references it. That works fine when the MSA is well-drafted. When it isn't, or when there is no MSA, the SOW is the only document standing between you and a payment problem.

Even with a solid MSA, there are payment protections that belong in the SOW itself — because they are engagement-specific and the MSA cannot anticipate them.

Know Your Invoice Trigger First

For T&M work, the invoice trigger is straightforward: bill at the end of each period for hours worked. For fixed-fee work, the trigger is milestone completion — which means your invoice right depends entirely on how clearly "complete" is defined in the SOW. Vague milestones are not just a delivery risk. They are a billing risk.

For fixed-fee milestones, your SOW should state explicitly: Invoices may be submitted upon written acceptance of the associated deliverable, or upon expiration of the client review period without written rejection. That second clause — the deemed-acceptance trigger — means silence becomes acceptance. Without it, you cannot invoice until the client actively approves, which they may never formally do.

What the SOW Should Own Even When an MSA Exists

Net terms usually live in the MSA. But these items are engagement-specific and belong in every SOW regardless:

• →Milestone acceptance criteria and review windowsthe MSA will not define these. The SOW must.
• →Not-to-exceed figures for T&M workor explicit language that estimates are not commitments, with a client notification obligation when hours approach a threshold.
• →Expense pre-approval thresholdswhat categories are reimbursable and when client sign-off is required before costs are incurred.
• →Work suspension rightstied to this specific engagement — if the MSA does not include them, the SOW should.

Net 30 Is a Starting Line, Not a Payment Date

Net 30 means payment is due 30 days after the invoice date. In practice, large enterprise clients treat it as a floor — internal approval chains, batch payment runs, and "we process invoices on the 15th" policies mean you may not see payment until day 45 or 60. If neither your MSA nor SOW includes a work suspension right for overdue invoices, you may keep working while invoices age with no contractual lever to pull.

Two practical adjustments worth negotiating: specify that the net period starts from invoice date, not receipt — you control when the invoice is sent, not when they claim to have received it. And name the payment method (ACH, wire, check) so "we're still setting up the vendor" cannot become a delay tactic.

Dispute Carve-Outs: Don't Let One Line Item Hold Up the Whole Invoice

Without a dispute carve-out, a client can withhold an entire invoice over a single disputed line item. Add language requiring the client to pay the undisputed portion by the due date and provide written notice of the disputed amount and the specific basis for the dispute.

This prevents a $2,000 expense question from holding up a $45,000 milestone payment. It is standard in well-structured professional services agreements and clients rarely push back on it.

The Advance Payment Question

A project kickoff payment — typically 10 to 25 percent of total contract value, applied to the final invoice — validates that the client's procurement process is actually functional before you commit resources. It also provides working capital during early project phases and signals that you operate as a professional services firm, not a vendor.

Many clients will resist it. That resistance is information. A client who will not make a modest upfront payment for a significant engagement is showing you something about how they view the relationship before the project starts.