Free Progress Invoice Template

On long projects, sending a single invoice at the end is a recipe for cash flow stress and increased non-payment risk. Progress invoices, also called milestone invoices, let you bill incrementally as work advances. They smooth your income, prove value at each phase, and reduce the financial gap between work and payment.

This guide gives you a free progress invoice template designed for US freelancers and small businesses on multi-phase projects. You will learn how to structure milestones, how to define billable triggers, how to handle scope adjustments mid-project, and how to ensure each progress invoice maps cleanly to project outputs. By the end you will be billing every long project in stages without missing a phase or losing track of cumulative spend.

What a Progress Invoice Is

A progress invoice is an interim invoice issued during a long project to bill for a portion of the work completed to date. It is different from a final invoice (which closes a project) and different from a partial payment (which is a payment plan against a single invoice).

Common progress invoice scenarios:

Scenario one: percentage-of-completion billing. You bill at fixed percentages: 25 percent at project start, 50 percent at midpoint, 25 percent at completion. Common in construction, renovation, and large design projects.

Scenario two: milestone-based billing. You bill at defined milestones: kickoff, requirements complete, prototype delivered, testing complete, final delivery. Common in software development, consulting, and content production.

Scenario three: time-and-materials billing with periodic invoices. You bill biweekly or monthly for hours worked to date. Common in IT consulting, agency work, and ongoing development projects.

Scenario four: deliverable-based progress billing. You bill as each defined deliverable is completed and approved. Common in writing, design, and creative production.

In each scenario, the progress invoice covers work performed to date, references the overall project, accounts for prior progress invoices and deposits, and shows remaining project balance.

Required Elements of a Progress Invoice

A progress invoice includes everything a standard invoice includes, plus four elements specific to progress billing.

Standard invoice elements: your business identity, client info, unique invoice number, issue date, due date, line items, subtotal, sales tax if applicable, and total due. Standard payment terms.

Additional progress-specific elements:

Element one: clear identification as a progress invoice. Label as 'Progress Invoice [X] of [Y]' or 'Milestone Invoice' so the client knows this is not a final invoice. Reference the overall project clearly.

Element two: completion summary. Show what has been completed for this billing period. Example:

• Milestone 2 (Wireframes and content strategy) - completed April 15, 2026
• Deliverables transmitted: [link to files or attachment]
• Approval received via email April 18, 2026

Element three: cumulative billing tracker. Show the running total of project billing to date and the remaining balance. Example:

• Project total per engagement letter: $24,000.00
• Previously billed (Progress invoice 1, dated March 15): $6,000.00
• This invoice (Progress invoice 2, milestone 2): $6,000.00
• Total billed to date: $12,000.00
• Remaining project balance: $12,000.00

Element four: next milestone preview. State what is coming next. Example: 'Next milestone (3 of 4): visual design system, estimated delivery May 30, 2026. Estimated next progress invoice: June 1, 2026, $6,000.'

Together, these elements give the client clear visibility into the project's progression and remove ambiguity about what each invoice covers.

The Free Progress Invoice Template

Here is a complete progress invoice structure to copy. Open the free invoice generator at /free-tools/invoice-generator and customize the bracketed fields.

Header (top, large font): PROGRESS INVOICE 2 OF 4

From: [Your Business Name], [Address], [Phone], [Email], EIN: [your EIN]

Invoice Number: PRG-2026-0019 | Issue Date: April 22, 2026 | Due Date: May 6, 2026

Bill To: [Client Company], Attn: Accounts Payable, [Address], [AP Email]

Project: [Project Name and brief description] - Progress Invoice 2 of 4

Milestone Summary: Milestone 2 (Wireframes and content strategy) completed April 15, 2026. All deliverables transmitted via [link/method] on April 18, 2026. Client approval received via email April 19, 2026.

Deliverables Completed This Period:

• 12 wireframes covering all primary user flows
• Content strategy document (28 pages)
• Sitemap with metadata recommendations
• 1 hour review call held April 17, 2026

Line Items:

• Progress invoice 2 of 4 (Milestone 2: Wireframes and content strategy, 25 percent of project total) - $6,000.00

Cumulative Billing Tracker:

• Project total per engagement letter dated [date]: $24,000.00
• Progress invoice 1 (Milestone 1: Discovery and research, dated March 15): $6,000.00 [paid March 28, Receipt RCP-2026-0033]
• This invoice (Progress invoice 2): $6,000.00
• Total billed to date: $12,000.00 (50 percent of project)
• Remaining project balance: $12,000.00 (Progress invoices 3 and 4)

Next Milestone: Milestone 3 (Visual design system), estimated delivery May 30, 2026. Estimated next progress invoice: June 1, 2026, $6,000.00.

Subtotal: $6,000.00

Sales Tax: $0.00 (services not taxable in [state])

Total Due This Invoice: $6,000.00

Payment Terms: Net 14, due May 6, 2026. Late fees of 1.5 percent per month apply to balances past due.

Payment Methods: ACH bank transfer (preferred, free), credit card via Stripe ([link]), or check payable to [Your Business].

Reference: Per engagement letter signed [date].

Thank you for the productive milestone 2 cycle. Looking forward to kicking off the visual design phase next week.

[Your Name], [Your Business]

This template is approximately 300 words and gives the client complete visibility into project progress and cumulative spend.

Structuring Milestones for Effective Progress Billing

The quality of your progress invoicing depends on the quality of your milestone structure. Build milestones that are clear, billable, and aligned with real client value.

Principle one: milestones should be discrete and verifiable. 'Phase 1 complete' is vague. 'Wireframes for 12 primary user flows delivered and approved' is specific. The client should be able to look at the milestone deliverable and verify completion in 5 minutes.

Principle two: milestones should be roughly equal in scope. A project with milestones of 5 percent, 5 percent, 10 percent, and 80 percent creates a huge final payment that increases your risk. Aim for 4 milestones of 20 to 30 percent each, or 3 milestones of 33 percent each, with possibly a 10 to 20 percent upfront deposit.

Principle three: milestones should align with client value. The client should feel they have received something tangible at each milestone. Phases that are purely internal to your process (e.g., 'planning complete') do not deserve milestone billing. Phases that produce client-visible artifacts (wireframes, prototypes, drafts) do.

Principle four: milestones should be time-bounded. State the estimated completion date for each milestone in the engagement letter. If a milestone runs over schedule, communicate proactively. If it runs significantly over (more than 30 percent over), consider whether scope has expanded and whether additional billing is warranted.

Principle five: milestone approval triggers billing. The client formally approves the milestone deliverable (via email is sufficient), and you bill within 24 hours. Do not delay billing while waiting for the next milestone to start; cash arrives faster when invoices are sent immediately.

Sample 4-milestone structure for a typical $24,000 design project: 25 percent at kickoff (discovery and research approved), 25 percent at wireframes complete, 25 percent at visual design approved, 25 percent at final delivery. Each milestone is roughly 2 to 4 weeks of work and produces a visible, billable artifact.

Handling Mid-Project Scope Changes

Long projects almost always have scope adjustments. Handle them cleanly with change orders and updated progress invoicing.

When new scope is requested, document it as a change request. Specify the additional deliverables, additional time required, additional cost, and which milestone (existing or new) it attaches to. Get client written approval before doing the work.

Option one: add to existing milestone. If the change is small and aligns with an upcoming milestone, add it to that milestone's deliverables and invoice. Note the change on the invoice: 'Includes approved CR-002: addition of mobile responsive review, $800.'

Option two: create a new milestone. If the change is large enough to warrant its own phase, create Milestone 5 (or higher). The project total increases, the cumulative billing tracker is updated, and future progress invoices reflect the new structure.

Option three: separate side invoice. If the change is unrelated to the main project structure (e.g., a quick advisory call during the project), invoice as a one-off side invoice rather than disrupting the progress invoice sequence.

In all cases, update the engagement letter or attach an addendum documenting the change. Reference the addendum on the affected progress invoices. The cumulative billing tracker should always reflect the current, accurate project total.

Avoid silently absorbing scope creep. Each absorbed change erodes your effective rate and trains the client to expect more for less. Even if you decide to absorb a small change as goodwill, note it on the invoice: 'Goodwill: small layout adjustment provided at no charge ($200 value).' This shows the client what you absorbed and maintains professional positioning.

Common Progress Invoicing Mistakes

Mistake one: not sending progress invoices promptly after milestone approval. Send within 24 hours of milestone approval. The longer you wait, the more cash flow you sacrifice.

Mistake two: vague milestone descriptions on the invoice. 'Phase 2 work' is bad. 'Milestone 2: wireframes for 12 user flows and content strategy document, completed April 15' is good. Specificity prevents disputes.

Mistake three: not tracking cumulative billing. Without a clear cumulative tracker, both you and the client can lose sight of total project spend versus remaining balance. Include the tracker on every progress invoice.

Mistake four: skipping milestone approval before billing. Always get written approval (email is fine) before issuing the progress invoice. If you bill before approval and the client disputes the milestone, you have a complication that could have been avoided.

Mistake five: not handling rescoping cleanly. If milestones shift mid-project, update the engagement letter and the cumulative tracker. Do not let scope drift untracked.

Mistake six: using inconsistent invoice numbers. Use a clear naming convention like PRG-2026-0019 (progress invoice, 2026, sequential 19). Or include the milestone in the name like PRG-PROJECT-A-MS2. Consistency makes future searching easy.

Mistake seven: not pairing progress invoices with deliverable transmissions. Send the milestone deliverable email and the progress invoice at the same time, or in tightly coordinated sequence. The client sees the value, then sees the invoice; psychology of payment is maximized.

Mistake eight: not adjusting late milestones. If milestone 2 runs 2 weeks late, do not silently shift everything. Communicate the new timeline, update the engagement letter if needed, and reflect the change in the next progress invoice's 'next milestone' section.

Ready to structure progress billing for long projects? Try the free invoice generator at /free-tools/invoice-generator, which supports progress invoice templates with cumulative tracking. For full project-based billing including milestone management, automated invoicing on approval, and cumulative dashboards, upgrade at /pricing. Eonebill.ai turns long-project billing from chaos to predictable rhythm.

One broader lesson from progress invoicing: it teaches you to think in milestones, which improves project management even beyond billing. Freelancers who structure projects around clean, well-defined milestones consistently deliver better outcomes than freelancers who treat work as one long stream. The act of defining a milestone forces you to articulate what the client will see, when they will see it, and why it matters. That clarity benefits the client, the project, and your own focus.

For long-term client relationships, create a 'milestone library' of typical project shapes you have run. A 4-milestone web design project. A 5-milestone software build. A 3-milestone content strategy engagement. Each entry includes typical deliverables, time estimates, and pricing. The library accelerates new project scoping and ensures consistent quality. Over time, the library becomes one of your most valuable internal assets.

Finally, use progress invoicing as a relationship-building rhythm, not just a billing tool. Each milestone is an opportunity for a 15-minute check-in call: review the deliverable, hear client reactions, surface concerns, preview the next phase. Clients who experience this rhythm feel deeply involved in the project and develop trust that lasts beyond the engagement. Progress invoicing is the visible artifact of a much more important practice: collaborating with clients in clear, defined phases that produce strong work and strong relationships in equal measure.