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

Can You Invoice Clients for Work Completed Before Milestone Approval in the US?

If you work on a milestone-based project in the United States—whether you’re a freelancer, consultant, agency, developer, designer, or contractor—you’ve probably run into a familiar tension: you’re making real progress and spending real time, but the contract says payment is tied to “milestone approval.” Then approval drags. Or the client goes quiet. Or the stakeholder who must approve is on vacation. Meanwhile, you’ve delivered value, you’ve incurred costs, and you’re trying to keep cash flow predictable.

So the practical question becomes: can you invoice for work completed before the client formally approves a milestone?

The realistic answer is: sometimes yes, sometimes no—and it depends primarily on your agreement and how you manage acceptance, documentation, and billing communication. In the US, invoices are not magical legal instruments that automatically create payment obligations. An invoice is a request for payment. Whether the client is obligated to pay it on a given timeline depends on your contract terms, any applicable statements of work (SOWs), and standard contract principles like performance, acceptance, and breach.

This article walks through how milestone approval typically works, what you can invoice for before approval, what to do when approval is delayed, how to structure contracts to avoid getting stuck, and how to invoice in a way that is fair, professional, and far more likely to be paid on time. It’s written for real-world business, not law school, and it focuses on practical steps you can use right away.

Milestone approval: what it means in practice

A “milestone” is usually a project checkpoint that triggers something: payment, a scope transition, a new phase, or the release of deliverables. “Approval” or “acceptance” often means the client confirms that the deliverable meets agreed requirements. Most disputes around milestone billing are not about whether work was performed—they’re about whether the client believes it was performed “to spec,” “complete,” or “ready” for the next step.

Milestone approval tends to show up in several common ways:

1) Payment upon approval. The contract may say something like “Client will pay within 15 days of milestone acceptance.” This ties the due date to a client action.

2) Payment upon delivery. Some contracts trigger payment when the deliverable is delivered (submitted), not approved. Approval may be part of the process, but it doesn’t control invoicing.

3) Time and materials with milestone check-ins. You bill hourly (or day rate) and milestones are mainly planning checkpoints. Approval may matter for moving forward but not for payment.

4) Partial payments. The project is milestone-based, but each milestone includes a deposit, progress payment, and a final payment upon approval.

If your agreement falls into the first category—“pay on approval”—you may still be able to invoice before approval, but the invoice might not be “due” yet under the contract. That matters because your invoice could be technically valid as a request, but the client can claim it’s not payable until the approval condition is met.

Invoices vs. payment obligations: a critical distinction

In the US, an invoice is evidence and a communication tool. It documents what you believe is owed, for what, and on what terms. But an invoice alone doesn’t override your contract. If the agreement says “pay after milestone approval,” the client may argue they have no obligation to pay until they approve, even if you’ve done the work.

However, the contract doesn’t exist in a vacuum. If the client is unreasonably withholding approval, delaying review, or using approval as a tactic to stall payment, the situation can shift. Depending on the wording and facts, you may have leverage under general contract principles. Still, relying on leverage after a dispute begins is expensive and stressful. The better approach is to structure your workflow and your billing so approval delays don’t destroy your cash flow.

So, can you invoice before milestone approval?

You can always send an invoice. The more useful question is whether you can invoice in a way that is consistent with your agreement and that encourages timely payment. In general, you have four workable options:

Option A: Invoice for a deposit or retainer before the milestone starts. This is the simplest and most common way to protect cash flow. If a milestone will take three weeks, it’s reasonable to collect a portion up front.

Option B: Invoice for progress payments tied to time or percentage completion. Instead of one payment upon approval, split the milestone into smaller payment triggers that don’t depend on final acceptance.

Option C: Invoice upon submission (delivery) with an approval window. You invoice when you submit the milestone and define that the client must accept or reject (with specific reasons) within a set number of days. If they don’t respond, it is deemed accepted.

Option D: Invoice after approval—strictly following the contract—but manage approval actively. If your agreement is rigid, you can still avoid delays by using clear acceptance criteria, review timelines, and structured sign-off steps.

Which option is “allowed” depends on what your contract says. If you already signed a contract that strictly ties invoicing to approval, you should be careful about sending “due now” invoices that contradict that language. But you can still send a progress invoice that clearly labels itself as “for work completed to date” and indicates when it becomes due per the agreement. That approach keeps your record clean and sets expectations without creating a direct conflict.

What your contract language likely says (and why it matters)

Milestone approval clauses often contain hidden traps. Here are the big ones to look for:

“Payment due upon acceptance” with no acceptance deadline. This allows a client to delay indefinitely. You can complete the work, submit it, and still wait weeks for approval and payment.

Vague acceptance standards. If the deliverable must be “satisfactory” or “in client’s sole discretion,” you’ve handed the client broad power to reject for subjective reasons.

No clear rejection process. If the contract doesn’t require the client to provide written reasons for rejection, you may end up with vague feedback like “not quite right” and endless revisions.

Unlimited revisions bundled into acceptance. When “approval” implicitly includes as many revision cycles as the client wants, you risk doing additional scope for free before you can invoice.

All deliverables bundled into one milestone. If a milestone includes 10 items and approval requires all 10, one delayed item can hold payment for the other nine.

If your agreement includes these issues, invoicing before approval is less about legality and more about negotiation and risk management. Your goal is to align your invoicing with objective triggers: time spent, work submitted, or defined acceptance steps with deadlines.

Acceptance vs. delivery: the submission strategy that protects you

A strong approach used by many US freelancers and agencies is to treat “delivery” (submission) as the invoicing trigger and “acceptance” as a review step with a deadline. In practical terms, you submit the milestone, send an invoice, and the contract gives the client a specific number of business days to accept or provide written issues. If they don’t respond, it’s automatically accepted.

This does three things:

1) It prevents endless silence. Non-response becomes acceptance after the stated window.

2) It encourages quick review. The client knows there is a defined timeline.

3) It keeps your billing predictable. You can plan cash flow and staffing.

If your current contract doesn’t include an approval window, you can still adopt a submission strategy operationally: when you deliver, include a message that outlines the review window you are working under. The client may not be legally bound if it conflicts with the contract, but in many situations it becomes part of the practical working relationship—and it’s hard for a client to argue they didn’t understand the expectation if you communicate it clearly every time.

When invoicing before approval is reasonable (even for milestone projects)

Clients often think milestones mean they only pay when everything is perfect. But businesses regularly pay for work in progress. Here are situations where invoicing before final approval is typically reasonable and commonly accepted in the US market:

Long milestones. If a milestone spans weeks or months, progress billing is normal. It’s not fair for the vendor to finance the project indefinitely.

High upfront effort. Discovery, architecture, design explorations, research, and initial builds often take significant time before a “final” deliverable is ready.

Client-driven delays. If approval depends on the client providing feedback, content, access, or decisions, it’s reasonable to bill for work completed while waiting.

Time-and-materials hybrids. Many projects use milestones for planning but still bill hours or days for the work performed.

Change requests and scope creep. If approval is delayed because the client keeps adding “small” extras, you should separate those extras from the original milestone and invoice accordingly.

Common scenarios and how to handle them

Scenario 1: You finished the milestone, but the client hasn’t approved it yet

This is the classic case. The key is to make your submission and your acceptance criteria unmistakable.

What to do:

Send the deliverables in a single, clearly labeled package. Include a short “Milestone X Submission” message that lists what is included, what “acceptance” means, and what you need from them (approve or provide a written list of issues). Give a reasonable review deadline (for example, five business days).

Billing approach:

If your contract allows invoicing on submission, invoice immediately. If it says “after approval,” you can still send a “work completed to date” invoice marked as “payable upon acceptance per agreement,” or you can wait but document that the milestone is complete and pending client approval.

Why this works:

It puts the next action on the client and creates a clear record that you delivered the milestone.

Scenario 2: The client approved the milestone verbally, but not in writing

Verbal approvals can be real, but they are hard to prove later. Your goal is to convert verbal approval into written confirmation.

What to do:

Send a friendly follow-up email: “Thanks for confirming in our call that Milestone X is approved. I’m noting approval as of today. I’ll send the invoice now—please reply if anything differs from your understanding.”

Billing approach:

Invoice immediately and reference the approval date. If the client doesn’t object, you’ve effectively created a written record.

Scenario 3: The client rejects the milestone, but the rejection is vague

“Not what we had in mind” or “needs work” without specifics is a recipe for endless iterations. Acceptance should be tied to requirements, not feelings.

What to do:

Ask for a written list of issues mapped to the agreed scope and acceptance criteria. If acceptance criteria were not defined, propose a structured list: functional requirements, brand requirements, content requirements, and any deliverable checklist you used.

Billing approach:

Invoice for work completed if your contract allows it, and separate any new requests as change orders or additional line items. If the rejection is essentially a scope change, treat it that way.

Scenario 4: The client is slow because their internal approver is unavailable

This is extremely common in corporate environments. Approval chains can involve legal, compliance, marketing, procurement, and executives. You shouldn’t be punished financially because someone is out of office.

What to do:

Build an approval schedule into your project plan and confirm who the approver is. If the approver is unavailable, request an alternate approver or a temporary sign-off process.

Billing approach:

If the work is complete and submitted, invoice on submission where possible. Otherwise, invoice for progress or billable time while waiting, if your agreement supports it.

Scenario 5: The client says they won’t approve until “everything” is done

Sometimes clients try to combine multiple milestones into one big “final acceptance” to delay payment. This is risky for you and often unnecessary for them.

What to do:

Point back to the milestone structure and the reason it exists: to approve work in stages. Ask what specifically prevents approving the current milestone. If their concerns relate to future milestones, separate them.

Billing approach:

Invoice per milestone submission and keep future work gated until payment is received or the approval process is followed.

How “deemed acceptance” clauses change everything

A deemed acceptance clause is one of the most powerful tools you can use in milestone projects. It says that if the client does not respond within a certain period after delivery, the milestone is considered accepted. This keeps projects moving and protects you from silence-based nonpayment.

A practical deemed acceptance workflow looks like this:

1) You submit the milestone with a clear checklist of deliverables and a request for approval.

2) The client has a defined window (for example, five business days) to accept or reject with written reasons.

3) If the client does not respond, acceptance is deemed granted on the next business day.

4) Payment is due based on acceptance (actual or deemed) within the payment term (for example, Net 15).

Even if your existing contract does not include deemed acceptance, you can still approximate it operationally by sending submissions with clear response deadlines and documenting follow-ups. While that may not automatically convert into a legal acceptance clause, it improves your ability to show you acted reasonably and the client did not.

Progress billing: the safest way to invoice before approval

If you want predictable cash flow, progress billing is usually the cleanest solution. Instead of waiting for a single approval, you invoice based on time periods, percentage completion, or defined intermediate outputs.

Common progress billing models include:

Weekly or biweekly invoices. Best for hourly or day-rate work. Milestones become planning tools, not payment triggers.

50/50 milestone billing. 50% due when the milestone begins, 50% due upon submission or approval.

30/40/30 billing. 30% deposit, 40% mid-point, 30% upon approval.

Fixed monthly retainer with milestone deliverables. Useful for ongoing work where deliverables are iterative and acceptance is continuous.

Progress billing also reduces the emotional charge around approval. If the client already paid part of the milestone, they are less likely to use approval as leverage. And you’re less likely to feel pressure to over-deliver just to unlock payment.

What about “time spent” before the milestone is approved?

If you are working under a fixed-fee milestone agreement, the client may believe they are buying a deliverable, not your time. That’s fine—until approval is delayed and you’re effectively financing the project. In those cases, you have two main options:

1) Convert part of the work into billable time. For example, add a clause that client delays beyond a certain review window convert waiting time, rework, or additional meetings into time-and-materials.

2) Add a “pause” mechanism. If feedback is not provided by a certain date, the project timeline shifts and you may pause work until approval is received. This is not invoicing for unapproved work, but it protects you from continuing to work without clear direction and without payment.

Both approaches are about setting expectations: approval delays have consequences, either in schedule or in cost.

How to write invoices that match milestone projects

When invoicing before approval (or even when invoicing after), clarity matters. Ambiguous invoices create room for clients to argue.

Here’s how to structure your invoice line items for milestone work:

Use milestone names and identifiers. Example: “Milestone 2: UI Design Delivery (as defined in SOW v3).”

Reference submission dates. Example: “Submitted on January 15, 2026.”

List what’s included. Keep it short: “Homepage, Pricing page, Dashboard layout; clickable prototype link.”

Separate add-ons and changes. If the client requested additional work, create separate line items: “Change Request #2: Additional onboarding flow screens.”

State payment terms clearly. Example: “Payment terms: Net 15 from acceptance (or deemed acceptance) per agreement.”

Include late fees only if your agreement allows them. If you intend to charge late fees, it’s best to have that in your contract and to apply it consistently.

Finally, keep invoices professional and unemotional. The invoice is not where you fight the approval battle. It’s where you document what’s owed and why.

How to handle disputes without blowing up the relationship

Approval disputes often feel personal because you’ve poured effort into the work. But the most successful approach is calm, structured, and documentation-based.

Step 1: Restate the scope and acceptance criteria. Use the SOW, proposal, or written requirements as your anchor.

Step 2: Ask for specific issues. “Please list the items that do not meet the agreed requirements.”

Step 3: Categorize feedback. Separate true defects (you fix them) from preference changes (change request) and new scope (new estimate).

Step 4: Offer a resolution path. For example: one revision pass included, additional revisions billed hourly, and a deadline for consolidated feedback.

Step 5: Keep billing and delivery aligned. If the milestone is substantially complete, invoice according to the contract and pause new work if needed until the payment or approval issue is resolved.

Many clients are reasonable when you provide structure. The chaos comes from vague feedback, unclear scope, and unlimited revision cycles.

Contract terms that make pre-approval invoicing easier (and safer)

If you haven’t signed the contract yet—or you can update it for future projects—these terms dramatically reduce your risk:

1) Clear acceptance criteria. Define what “accepted” means in concrete terms. If it’s creative work, define acceptance as meeting agreed deliverable formats, quantities, and high-level requirements, with reasonable artistic discretion.

2) Acceptance window. Require acceptance or written rejection within a specific period after submission.

3) Deemed acceptance. If no response arrives within the window, acceptance is automatic.

4) Limit included revisions. Example: “Two revision rounds included; additional revisions billed at $X/hr.”

5) Change control process. Any request outside scope is documented and approved before work begins.

6) Progress billing or deposits. Collect money at the start of each milestone and/or bill at defined intervals.

7) Pause rights for delayed feedback or overdue invoices. If the client does not provide feedback or pay on time, you may pause work without being in breach.

8) Define what happens with partial approval. If parts are approved and parts are pending, you can invoice the approved portion.

These terms don’t just protect you—they often make clients happier because the process is predictable.

What if the client refuses to pay unless you continue working?

This is a dangerous pattern: the client holds approval (and payment) hostage while demanding additional work. It can quickly turn into unpaid labor.

A professional stance is:

Deliver what was agreed. Submit the milestone and document it.

Separate new requests. Treat them as a change request with its own pricing and timeline.

Gate future work. If payment is overdue or approval is unreasonably delayed, pause further work until the issue is resolved.

In many industries, continuing to work without payment signals that the client can keep pushing boundaries. The earlier you enforce structure, the easier it is to maintain a healthy relationship.

What if you already did the work and the contract is strict?

If you’re already stuck in a strict “payment after approval” contract with no acceptance deadline, you still have options to improve the situation:

Use a written submission record. Make it clear that you have completed and delivered the milestone and that it is awaiting review.

Request a review date. Ask for a firm date and time for approval. Offer to walk through deliverables on a call to speed it up.

Offer limited, structured revisions. If the client has concerns, offer a defined revision pass aligned to the scope.

Propose an addendum. Suggest adding an acceptance window going forward. Many clients will agree once they realize the current process is causing delay.

Pause future milestones. If your agreement allows it (or if the client is in breach by failing to cooperate), you can reduce your risk by pausing until approval occurs.

Even in strict contracts, your leverage increases when you keep clean documentation and maintain professional, consistent communication.

How to communicate the invoice without escalating tension

When you invoice before approval (or when you invoice upon submission), how you message it matters. You want to be confident and matter-of-fact, not confrontational.

Here’s a communication structure that works well:

1) Confirm what was delivered. “Milestone 2 has been submitted: X, Y, Z.”

2) State what you need from them. “Please reply with approval or a written list of issues by Friday.”

3) Attach the invoice and terms. “Invoice #1042 is attached. Per our agreement, payment is due Net 15 from acceptance.”

4) Offer help to speed review. “Happy to do a 20-minute walkthrough if helpful.”

This positions the invoice as part of a normal process, not as a demand.

Invoice timing best practices for milestone work

To reduce friction and speed up payments, consider these invoicing habits:

Invoice immediately upon the trigger event. If you invoice days later, it disconnects the invoice from the value delivered.

Use consistent invoice numbering and references. Tie invoice numbers to milestones in your own tracking notes and internal records.

Keep line items short and specific. The more confusing the invoice, the more likely it is to be questioned.

Include a clear due date. Even if due date depends on acceptance, include language such as “Due: Net 15 from acceptance” and note the submission date.

Send reminders professionally. A reminder is not an accusation. It’s normal operations.

Offer multiple payment methods. The easier it is to pay, the faster you get paid.

Using invoice24 to invoice milestones cleanly and confidently

Milestone invoicing works best when your invoices are consistent, detailed enough to avoid confusion, and easy for clients to pay quickly. invoice24 is built to support real-world billing workflows so you can spend less time chasing approvals and more time delivering work.

Here are practical ways to use invoice24 for milestone projects:

Create milestone-specific invoice templates. Save a template for each milestone type (design, development, consulting, delivery). Then duplicate it for each project and adjust details.

Use clear line-item naming conventions. For example: “Milestone 1: Discovery & Requirements (SOW Section 2).” Clear naming prevents billing disputes.

Add notes for submission and acceptance terms. Include a brief note like “Submitted on [date]. Review window: 5 business days. Payment terms: Net 15.”

Split invoices into progress payments. Instead of one large invoice at the end, invoice24 makes it easy to issue separate invoices for deposits, midpoints, and final balances.

Track invoice status and follow-ups. A simple system for monitoring sent, viewed, and overdue invoices helps you follow up consistently and professionally.

Maintain a clean paper trail. Keeping invoices, descriptions, and dates consistent makes it much easier to resolve questions quickly if a client pushes back.

Key takeaways: the practical answer

In the US, you can send an invoice at any time, but whether the client must pay before milestone approval depends on your agreement and the acceptance process you’ve set up. If payment is strictly tied to approval and there’s no approval deadline, you risk long delays—even after you’ve delivered the work.

The best way to protect yourself (and keep relationships healthy) is to design a milestone workflow that doesn’t rely on vague, indefinite approval:

Use deposits or progress billing so you’re not financing the project.

Invoice upon submission with a defined review window.

Define acceptance criteria and limit revisions.

Separate scope changes into change requests and separate line items.

Document everything in a calm, consistent way.

If you’re already mid-project in a strict approval-based agreement, you can still improve outcomes by tightening submission communications, requesting specific feedback, setting review dates, and pausing new work when approvals or payments stall.

Milestones are meant to make projects smoother, not to trap you in unpaid limbo. With a clear process and professional invoicing habits—supported by a solid invoicing workflow in invoice24—you can reduce approval delays, get paid faster, and keep your client relationships strong.