Invoice templates

Software development invoice template

Milestone or sprint-based line items, tied to a signed SOW — so every invoice references the specific deliverable it's billing.

Preview

See the template as a client-facing document, then open the same starting point inside Hanko.

Use it in Hanko

Invoice

Software Development Invoice

Atlas Software Co.

billing@brightlinestudio.com

Invoice

Invoice #: INV-2026-014

Issue date: September 30, 2026 | Due date: September 30, 2026

SOW reference: Partner Portal Build, Milestone 2

Total due

$19,000

Card, ACH, wire or stablecoin

From / Bill to

Atlas Software Co. / Northstar Labs

From / Bill to

Atlas Software Co. / Northstar Labs

DescriptionQtyAmount
Milestone 1: API architecture1$6,000
Milestone 2: Client dashboard1$9,000
Milestone 3: Integration QA1$4,000

Payment methods

Card, ACH, wire transfer or USDC.

Subtotal$19,000
Total due$19,000

What this is

A software development invoice bills a fixed-price milestone or a block of time-and-materials hours, referencing the SOW and milestone number so there's no ambiguity about what work the payment corresponds to.

When to use it

  • Billing a fixed-price milestone on completion
  • Invoicing a weekly or bi-weekly time-and-materials block
  • Billing a change order for work outside the original SOW

What to include

SOW and milestone reference

The specific SOW number and milestone being billed, so the invoice is traceable to agreed scope.

Acceptance status

Whether the milestone has been accepted per the SOW's acceptance criteria, not just delivered.

Hours breakdown (if T&M)

For time-and-materials billing, a summary of hours against the estimated range in the SOW.

Template text

Copy this into your own document, or open it directly as a branded starting point in Hanko. Bracketed text like [Client Name] is a placeholder to fill in.

Invoice

Invoice #: [INV-001]

Issue date: [Date] | Due date: [Date]

SOW reference: [SOW #001], Milestone [2]

From / Bill to

[Your Company Name] / [Client Company Name]

Line items (fixed-price milestones)

Description Amount

Product Discovery & Architecture $4,000

Sprint 1 — Core Backend & API $8,000

Sprint 2 — Frontend Integration $8,000

QA, Deployment & Handoff $3,000

— or — time & materials

Description Hours Rate Amount

Development (per SOW #001) [X] $[rate]/hr $[amount]

Totals

Subtotal: $[amount]

Total due: $[amount]

Payment terms & methods

Due within [15] days of issue date.

Card, ACH, wire transfer [and stablecoin — USDC, if applicable].

How to customize it

  • Reference the exact SOW and milestone number on every invoice, fixed-price or T&M
  • For T&M billing, include or offer a detailed time log to back the hours billed
  • Bill change orders as their own line, separately quoted and approved before work begins

Common mistakes

  • No SOW/milestone reference, making disputes about what was actually delivered harder to resolve
  • Billing a milestone before it meets the SOW's stated acceptance criteria
  • Folding change-order work into a regular milestone invoice instead of billing it as separately approved scope

Frequently asked questions

Should a software invoice reference the SOW?

Yes — include the SOW number and specific milestone on every invoice, so there's no ambiguity about which agreed deliverable the payment corresponds to.

When is a fixed-price milestone billable?

Once it meets the acceptance criteria stated in the SOW, not simply once the calendar date for that milestone has passed.

Running this whole industry's workflow

See how Hanko fits the complete client workflow for this industry, not just the invoice.

Other templates

Bill your next milestone against a signed SOW

Milestone invoices tied to your Statement of Work, reconciled automatically in Hanko.

One account for proposals, agreements, invoices, client payments and contractor payouts.

Get Started

Product updates and the occasional tip, about once a month.