Can I invoice clients for work completed before final approval in the US?

Understanding the Question: What “Work Completed Before Final Approval” Really Means

Invoicing clients for work completed before “final approval” is one of the most common pain points for freelancers, agencies, consultants, and contractors in the United States. The short version is: yes, you often can invoice before final approval, but whether you should (and whether you’ll actually get paid on time) depends on your contract terms, your industry norms, and how you’ve structured milestones, acceptance criteria, and payment triggers.

Final approval can mean very different things to different clients. In a design project, final approval might mean the client signs off on the final creative. In a software project, it may mean user acceptance testing is complete and the deliverable passes defined tests. In construction, approval might mean a final inspection or certificate of occupancy. In marketing, it might mean the final campaign assets are delivered and scheduled. Because approval can be subjective, invoicing “before final approval” can be either perfectly normal (like billing on milestones) or a recipe for disputes (like billing for a deliverable the client claims is not acceptable yet).

This article explains when invoicing before final approval is typically allowed, how to write terms that support it, and how to reduce delays, pushback, and nonpayment. You’ll also see practical invoicing workflows you can implement in invoice24, so the process stays professional and easy to follow.

General Rule in the US: Contracts and Agreement Control

In the US, the right to invoice and the right to receive payment are mainly governed by the agreement between the parties. If your contract says you invoice at milestones, on delivery, or on a time-and-materials basis, you can invoice accordingly—even if the client’s internal “final approval” hasn’t happened yet—so long as you’ve satisfied the agreed trigger.

If you don’t have a written contract, your relationship may still be governed by an oral agreement, email threads, proposals, statements of work, invoices, and “course of dealing” (the pattern of how you and the client typically work). The more ambiguous the terms, the more likely you’ll face disputes about whether payment is due before approval.

Practically, if the client believes “final approval” is the moment payment becomes due, and you believe “delivery” is the moment payment becomes due, you can wind up arguing about definitions rather than focusing on getting paid. That’s why the smartest approach is to define invoicing and acceptance clearly upfront, and then follow that structure consistently.

Common Scenarios Where Invoicing Before Final Approval Is Normal

Many US businesses routinely pay invoices before a final sign-off, because they recognize the vendor’s time, costs, and partial deliverables still need to be compensated. Here are the most common “safe” scenarios where invoicing before final approval is widely accepted.

1) Time-and-materials work (hourly or daily billing)

If you’re billing hourly, it’s standard to invoice weekly, biweekly, or monthly based on time worked. Final approval of the end result is not usually a condition for paying labor already performed. Clients may still dispute certain hours if they believe work was unauthorized, outside scope, or unproductive, but “final approval” usually does not block billing.

2) Milestone billing

Milestones are designed specifically to allow invoicing before the entire project is “approved.” For example, 30% on kickoff, 30% on initial concept delivery, 30% on beta release, 10% on final handoff. The client may not love paying before “completion,” but milestone terms keep cash flow steady and help prevent the vendor from financing the project.

3) Progress billing for long projects

On long engagements, progress billing is a practical necessity. You invoice based on percentage completion or scheduled periods (like monthly draws). This is common in construction, engineering, and large implementation work.

4) Non-refundable deposits and retainers

Deposits and retainers are forms of pre-payment that can be invoiced and collected before approval is even possible. A deposit often secures scheduling and covers upfront work. A retainer can reserve capacity and may be applied against future invoices, depending on your arrangement.

5) Pass-through costs and reimbursable expenses

It’s common to invoice for approved third-party costs (like stock assets, hosting, travel, subcontractors, printing) as they occur, rather than waiting for final approval. These costs exist regardless of whether the client has approved the final deliverable.

When Invoicing Before Final Approval Can Be Risky

There are also scenarios where invoicing before final approval can create friction or nonpayment risk. You can still invoice, but you’ll want extra clarity and documentation.

1) Highly subjective deliverables

Brand strategy, creative direction, logo design, and other subjective work can prompt clients to argue that the work isn’t “complete” until they love it. If you invoice too early without clear milestone definitions, clients may stall payment with feedback cycles.

2) Undefined acceptance criteria

If you haven’t specified what counts as “accepted” (or when acceptance is deemed to occur), clients can claim they’re not obligated to pay until they sign off—even if they delay sign-off for reasons unrelated to your work.

3) Scope creep disguised as “approval”

Some clients treat approval as a moving target. They ask for additional features, rounds, or deliverables and claim they can’t approve until everything is included. Without firm boundaries, invoices become bargaining chips rather than normal business documents.

4) Procurement rules and internal policies

Some clients (especially larger companies) have internal controls that require a purchase order, receiving confirmation, or management approval before accounts payable processes an invoice. In those cases, invoicing “early” isn’t legally prohibited, but it may delay payment if their internal steps haven’t been completed.

Key Contract Clauses That Make Early Invoicing Work Smoothly

If you want to invoice before final approval in the US, the most effective strategy is to structure your agreement so it’s obvious, fair, and hard to dispute. The following clauses are common, reasonable, and easy to explain to clients.

Define payment triggers clearly

Instead of saying “payment due upon approval,” define triggers like:

• Payment due upon project start (deposit).
• Payment due upon delivery of milestone deliverable.
• Payment due on the first business day of each month for work performed in the prior period.
• Payment due upon completion of specified tasks listed in the statement of work.

This reduces the chance that “approval” becomes the only gateway to payment.

Acceptance criteria and deemed acceptance

Acceptance criteria specify how the client confirms that a deliverable is acceptable. Deemed acceptance prevents endless delays. A typical approach is: the client has a set number of days to review and either accept or provide written, consolidated feedback tied to the acceptance criteria. If they don’t respond within that timeframe, the deliverable is treated as accepted for invoicing and scheduling purposes.

Deemed acceptance is not about “tricking” a client; it’s about avoiding situations where a client disappears for weeks and expects you to hold the project open indefinitely without payment.

Revision limits and out-of-scope work

If you invoice before final approval, you should also define what the invoice covers. For example, include two rounds of revisions, and additional rounds are billed at an hourly rate. Or define a specific feature list, and changes are estimated and billed separately. This prevents a client from blocking payment by requesting additional work and calling it “required for approval.”

Payment terms and late fees

Clearly state due dates (for example, Net 15, Net 30, or due upon receipt) and what happens if the client pays late. If you choose to include late fees, be sure your terms are reasonable and clearly displayed on invoices. Even if you never enforce late fees, having them in writing helps encourage timely payment.

Suspension of work for nonpayment

One of the most powerful protections is the right to pause work if invoices are overdue. This is especially important if you’re invoicing on milestones or time-based billing. It helps prevent the situation where you keep delivering while payment stays unresolved.

Ownership and licensing tied to payment

Many service providers handle “approval” concerns by separating payment from final ownership transfer. For example, you can grant the client a license to use deliverables only once all invoices are paid. This makes it easier for clients to accept milestone billing because you’re not giving away everything without being paid.

Milestone Invoicing: The Best Middle Ground Between “Approval” and “Payment”

If you’re struggling with clients who want to pay only after final approval, milestones are often the most client-friendly compromise. They let clients feel they’re paying as value is delivered, while protecting you from financing the entire project.

A strong milestone plan has these characteristics:

• Each milestone represents a clear deliverable or measurable progress.
• Each milestone has an amount attached and a clear due date trigger.
• Review time is included (so the client isn’t surprised by the schedule).
• Approval is handled as part of the milestone (with acceptance criteria), not as a vague end-of-project event.

Example milestones for a website project might include discovery completion, wireframes, design comps, development beta, and launch support. Each stage can be invoiced when delivered, even though “final approval” only happens at the end.

What to Put on the Invoice When Billing Before Final Approval

An invoice can do more than request payment—it can communicate the business logic of why payment is due. When you invoice before final approval, clarity and professionalism matter even more. Here’s what to include to minimize disputes:

Use specific line item descriptions

Avoid vague descriptions like “Project work.” Instead, list what you delivered or completed, such as “Milestone 2: Wireframes delivered (Home + Product + Checkout)” or “January consulting hours (22.5 hours) – analytics audit and reporting.” Specific descriptions make it harder to argue that nothing was done.

Reference the agreement or statement of work

Add a short note such as “Billed per SOW dated [date] – milestone billing schedule.” This anchors the invoice to pre-agreed terms.

Include the billing period for time-based invoices

Time-based invoices should include a clear range (for example, “Work performed Jan 1–Jan 15”). Clients expect this, and it reduces confusion.

Include deliverable links or attachments when appropriate

If you delivered files, mockups, or reports, include a link or attach them. The easier it is for a client to confirm delivery, the fewer excuses there are to delay payment.

Make payment terms impossible to miss

Place due date and payment terms prominently. Also include accepted payment methods. If you offer multiple payment options, clients can pay faster.

Best Practice: Separate “Payment Due” from “Final Sign-Off”

A practical way to avoid the approval trap is to treat “final approval” as a project management milestone, not a payment gate. In other words, clients can still have a formal approval step, but payment is due based on time, milestones, or delivery. This keeps the project moving and protects your cash flow.

Here are a few examples of how this looks in real life:

• A marketing consultant invoices monthly for hours worked, while the client approves campaign changes separately.
• A designer invoices for concept development when concepts are delivered, even though the client will approve one direction later.
• A software developer invoices at sprint completion, while the product owner signs off during sprint reviews.

This model is not aggressive; it’s how many professional services businesses operate.

Handling Client Pushback: “We Don’t Pay Until Final Approval”

If a client says they don’t pay until final approval, it doesn’t always mean they’re trying to be difficult. Sometimes it’s habit, sometimes it’s their internal policy, and sometimes they’re protecting themselves from paying for something they fear won’t meet expectations. Your goal is to respond calmly and offer structures that feel fair to both sides.

Offer milestone-based payment

Explain that milestone billing reduces risk for both sides: the client pays as progress is made, and you’re not carrying all the financial risk. This is often the easiest “yes” for clients who resist deposits.

Offer an initial deposit plus smaller milestones

If they resist paying before approval, propose a smaller deposit (to secure scheduling) and then invoice in smaller increments tied to visible progress.

Clarify what “approval” means

Sometimes a client’s “final approval” is actually “internal stakeholder alignment,” which can take weeks. You can explain that you can’t be responsible for delays inside their organization, so payment must track your delivery and effort.

Use a simple acceptance window

A review window (for example, five business days) helps. It keeps approval from drifting indefinitely, while still giving the client a fair chance to evaluate deliverables.

Stay confident and professional

Clients often take cues from how you present your process. If you treat milestone invoicing as normal and standard, many clients will accept it as part of doing business.

What If the Client Refuses to Pay Because They Haven’t Approved Yet?

If a client refuses to pay an invoice because final approval hasn’t occurred, your next steps depend on your documentation and relationship.

Step 1: Re-anchor to the agreement

Reply with the exact milestone or payment trigger that applies. Keep the tone neutral. Point out what was delivered, when it was delivered, and what the payment terms are.

Step 2: Ask for specific objections tied to acceptance criteria

If the client claims the work isn’t acceptable, ask them to identify what acceptance criteria were not met. Vague dissatisfaction is not the same as a defined failure to deliver.

Step 3: Offer a path to resolution

Depending on the situation, you might propose a correction plan, a limited revision, or a paid change order for newly requested work. The key is to separate legitimate fixes from scope creep.

Step 4: Pause work if payment is overdue

If your terms allow it, pause until the invoice is paid or a written resolution is reached. Continuing to work without payment often worsens the imbalance.

Step 5: Escalate professionally

If the client continues to delay, escalate through a formal payment reminder sequence. In severe cases, you may need to consider collection options, mediation, arbitration, or small claims court depending on the amount and your contract terms. This article focuses on prevention and workflow, but the core message remains: the more clearly your terms support invoicing before final approval, the easier it is to enforce payment without conflict.

Industry-Specific Nuances Worth Knowing

While contract terms drive outcomes, different industries have different expectations. Understanding the “normal” for your sector helps you present your invoicing structure as standard.

Creative services (design, video, branding)

Clients often equate approval with personal preference. Milestones, revision limits, and clear deliverables help. Deposits are common, and staged payments reduce the risk of end-of-project nonpayment.

Software development and IT

Agile teams frequently invoice per sprint or per month. “Acceptance” can be tied to user stories or test cases. Change control is critical, because “final approval” can expand endlessly as new ideas appear.

Consulting and professional services

Monthly billing is typical. Approval is often about deliverable receipt rather than subjective sign-off. The key is documenting meetings, decisions, and outputs, because consulting value can be harder to “touch.”

Construction and trades

Progress billing and draws are normal, sometimes tied to inspections or percentage completion. Final approval may involve inspections, but work performed is still commonly billed along the way.

Using invoice24 to Invoice Before Final Approval Without Confusion

If your free invoice app is invoice24, the goal is to make early invoicing feel seamless and credible. A polished invoice and a consistent process can reduce the emotional friction clients sometimes feel when they haven’t “approved everything” yet.

Create clear estimates and convert them to invoices

Start with an estimate that outlines milestones, deliverables, rates, and payment triggers. When a milestone is reached or a billing period ends, convert the approved estimate items into an invoice in invoice24. This keeps the pricing consistent and shows the client you’re following a plan rather than inventing charges.

Use milestone line items

For milestone billing, create separate line items for each milestone. This makes it obvious what the client is paying for and reduces disputes about “what this invoice covers.”

Add invoice notes that reinforce your payment trigger

Use an invoice note like: “Milestone 2 invoice per agreement: design comps delivered for review.” Keep it short and factual.

Set clear due dates and payment terms

invoice24 should allow you to set due dates and terms like Net 15 or Net 30. Choose terms that match your cash flow needs and your client’s payment cycle. The most important thing is consistency: don’t set terms and then ignore them, because that trains clients to pay late.

Make it easy to pay

Fast payment is often about convenience. If invoice24 supports multiple payment methods, enable the options your clients prefer. The fewer steps between receiving the invoice and completing payment, the less likely “approval” becomes an excuse to delay.

Track invoice status and follow up systematically

When invoicing before approval, follow-up matters. A simple reminder schedule (for example, 3 days before due, on due date, and 7 days after due) keeps invoices from slipping through the cracks. invoice24’s tracking and reminders help you keep a professional rhythm without sounding confrontational.

Practical Payment Structures You Can Use Today

Here are several payment structures that commonly work well in the US for invoicing before final approval. You can adapt these to your service offering and client size.

Structure A: Deposit + milestones

• 30% deposit to start
• 40% upon mid-project deliverable
• 30% upon final handoff

This is straightforward and protects your upfront time.

Structure B: Monthly retainer

• Fixed monthly fee billed at the beginning of each month
• Scope defined as a set number of hours or deliverables
• Overage billed at an agreed rate

This reduces approval-related delays because payment is tied to reserved capacity.

Structure C: Biweekly time-based invoices

• Invoices issued every two weeks for hours worked
• Timesheet summary included
• Work pauses if invoice is overdue

This is effective when the scope is evolving or hard to define upfront.

Structure D: Phase-based fixed fees

• Phase 1: Discovery fee due upon completion of discovery deliverables
• Phase 2: Implementation fee due upon delivery of defined outputs
• Phase 3: Launch/support fee due upon launch support completion

This gives clients predictability while still enabling billing before the final project sign-off.

How to Prevent Disputes When Approval Is Subjective

If your work requires client “taste” or stakeholder alignment, you can still invoice before final approval, but you should control the process carefully.

Use a written creative brief or requirements document

When clients later say, “This isn’t what we wanted,” you can point to agreed requirements. It’s harder for approval to drift when the target is documented.

Limit feedback rounds and require consolidated feedback

Multiple stakeholders can create endless revisions. Require the client to consolidate feedback and designate a decision-maker. This keeps projects and invoices on track.

Confirm approvals as you go

Even if you invoice before final approval, you can still capture “micro-approvals” for each stage. A simple email confirmation is often enough: “Confirming we’re approved to proceed with Direction B.” That small step can prevent major disputes later.

Document delivery

Use clear delivery methods (shared folders, emailed links, project portals) and note delivery dates in your records. If a client claims they never received the deliverable, you can quickly prove delivery.

What Clients Expect: Transparency, Fairness, and Predictability

From a client’s perspective, paying before final approval can feel risky if they fear they’ll lose leverage. Your job is to replace “leverage” with “trust and structure.” When clients see that you have a consistent process, clear terms, and a track record of delivering, they’re much more willing to pay according to milestones or time.

Being transparent is also a competitive advantage. If you explain your invoicing approach upfront—before work starts—clients can decide whether it fits their expectations. Surprising a client with an early invoice, even if it’s justified, can create friction simply because it wasn’t anticipated.

Bottom Line: Yes, You Can Often Invoice Before Final Approval—If You Set It Up Correctly

In the US, invoicing clients for work completed before final approval is often allowed and frequently standard practice, especially for hourly billing, milestone billing, retainers, and progress billing. The key is to define payment triggers, acceptance criteria, revision limits, and review timelines so “final approval” doesn’t become an open-ended excuse to delay payment.

When you pair clear terms with a professional invoicing workflow—using invoice24 to create estimates, set milestones, apply due dates, offer easy payment options, and send consistent reminders—you reduce confusion and increase the likelihood of getting paid on time. The goal isn’t to pressure clients; it’s to build a fair system where you’re compensated for real work performed, while clients still have a clear process to review and approve deliverables.

If you consistently invoice based on defined milestones or time worked—and you communicate that structure clearly—most reasonable clients will accept it, and your business will be healthier for it.