Skip to main content
industry

Technical Writer Invoice Template

A technical writer invoice has to show what was documented, in units the client's engineering or product team can check. Technical writing is billed in more ways than most writing: per page or per topic for reference material, by the hour for discovery, interviews with subject-matter experts and editing, and as a fixed fee for a defined deliverable such as a getting-started guide or a documentation sprint tied to a release. Most invoices mix two or three of these, so this template keeps them apart: deliverables by title and count, hours by activity, review rounds included and any extra round, and tool or licence costs agreed in advance. It also asks for the release or product version the work covers, because documentation is approved against a release, not a month. The difference from a copywriting or freelance writing invoice is the unit and the reviewer: there is rarely a word count or a kill fee, and the person who signs off is often an engineer reviewing for accuracy rather than an editor. The download is an editable HTML invoice with invoice number, dates, a line-item table and totals. Fill it in your browser and print it or save it as PDF, or type or say what you delivered and InvoiceQuickly drafts an editable invoice for you to check before saving.

Draft this invoice
Preview this editable document

Download the HTML file to edit its fields, then print or save as PDF. Totals are entered manually.

What This Template Includes

  • Statement of work or agreement reference
  • Release, product version or sprint the work covers
  • Billing unit: per page, per topic, per hour or fixed fee, and how a page or topic is defined
  • Deliverables completed: document or topic titles and counts
  • Pages or topics billed, with the rate
  • Hours by activity (research, SME interviews, writing, editing) and rate
  • Review rounds included, and any extra round with the date requested
  • Tool or licence costs agreed in advance, at cost
  • Where the work was delivered: repository, help center or files
  • Client purchase order number

How to Create Your Technical Writer Invoice

  1. 01

    Describe your work

    Type a plain English description of the services you provided, the client, and the amount.

  2. 02

    AI generates your invoice

    InvoiceQuickly's AI drafts the client, line items, dates, and totals for you to review before saving.

  3. 03

    Review, download, and send

    Check every detail, download the PDF, or use Pro to email the PDF directly to your client.

Recommended Payment Terms

Bill fixed-fee documentation at agreed milestones (for example on approval of the outline, the first full draft and the final release) or at the end of each sprint, rather than once at the end of a long project. Hourly and per-topic work is usually invoiced every two weeks or monthly, with the deliverables listed. Software companies often pay through accounts payable on net 30, and many need a purchase order number on the invoice, so ask for it before the first invoice. Agree in the statement of work what happens when the client's reviewers are late: whether a milestone counts as accepted after a set number of days without comments, and whether waiting time is billable. Write the actual due date on each invoice, and refer to any late-fee clause in your contract.

Need help writing payment terms? Read our guide to invoice payment terms for best practices and templates.

Tax Information

In the United States, a business that pays you $2,000 or more for services in 2026 generally reports it on Form 1099-NEC (the threshold was $600 for payments made before 2026), so send Form W-9 before the first payment. Whether documentation services are subject to sales tax depends on the state and on what you deliver, so check your state revenue department rather than assuming they are exempt. Outside the US, charge VAT or GST only if you are registered and the place-of-supply rules for your client say so; many technical writers work for clients in other countries, where the rules for business customers can differ from those for consumers. InvoiceQuickly applies one tax percentage per invoice and copies your saved business tax ID to new invoice PDFs; check the saved IDs and PDF before sending when it must appear. General information, not tax advice.

Industry context (2026)

Technical writers 'prepare instruction manuals, how-to guides, journal articles, and other supporting documents', according to the US Bureau of Labor Statistics' Occupational Outlook Handbook (page modified 27 August 2026). The same source counts about 46,400 technical writer jobs in 2025, reports a median annual wage of $90,390 ($43.46 an hour) in May 2025, and projects employment to grow 1 percent from 2025 to 2035; it notes that some technical writers are self-employed freelancers or work for technical consulting firms. Those are employee wages, not freelance rates, and there is no reliable public rate card for freelance technical writing, so this page does not quote per-page or hourly benchmarks. What the work has in common is a review process: documentation is checked for technical accuracy by engineers or product owners as well as for clarity, which is why review rounds, release versions and acceptance dates belong on the invoice. Sources checked on 28 October 2026.

Worked example

Worked example (hypothetical writer and client; rates are illustrative, not market data). A freelance technical writer is documenting version 3.2 of a software company's public API under a statement of work of 5 October 2026: a fixed fee of $2,400.00 per two-week sprint for named guides, $95.00 per endpoint reference topic, $85.00 an hour for SME interviews and for review rounds beyond the two included per guide, and tools bought for the project at cost. Invoice INV-0019 is dated 2 November 2026 for sprint 2 (19 to 30 October), purchase order 7714, net 30, due 2 December. Line 1: sprint 2 fixed fee, getting-started guide and authentication guide, merged to the docs repository on 30 October, 1 × $2,400.00. Line 2: endpoint reference topics, Orders and Refunds resources, 14 × $95.00 = $1,330.00. Line 3: SME interviews with the payments engineering team, 22 and 27 October, 4.5 hours × $85.00 = $382.50. Line 4: third review round on the authentication guide, requested 28 October, 3 hours × $85.00 = $255.00. Line 5: diagramming tool subscription, one month, approved by email on 19 October, receipt R-5521, at cost, 1 × $24.00. Subtotal $4,391.50, tax 0%, total due $4,391.50. Notes: 'SOW of 5 October. One topic = one endpoint page in the API reference. Sprint 3 starts 2 November.' The lines answer the reviewer's questions in advance: the fixed fee is tied to two named guides, the 14 topics can be counted in the repository, and the $255.00 is visibly an extra round, not a change to the agreed fee. Whether to add tax depends on your location and your client's, so set it from your own rules, not this example.

Common mistakes to avoid

An undefined page

Billing '40 pages' when the client counts 28 help articles starts an argument. Use the unit defined in the statement of work, and count it the same way every time.

Unlimited review rounds

Without a cap in the agreement, a fourth and fifth round of engineering comments are part of the fixed fee. State the included rounds and bill extras as hours.

No release or version

'Documentation work, October' cannot be matched to the release the client is paying for. Name the version or sprint.

Absorbing tool costs

A licence bought mid-project and not agreed in advance is hard to recover. Ask the client to provide tools, or get written approval before you buy and bill at cost.

Hours with no activity

'12 hours' tells the client nothing. Split research, SME interviews, writing and editing so the reviewer can see where the time went.

Invoicing Tips

  • 1Define the unit in the statement of work before you invoice it. 'Per page' can mean a printed PDF page, a help center article or 300 words; 'one endpoint reference topic' or 'one help article' is easier to count and harder to dispute.
  • 2Name the release or version on every invoice ('Docs for API v3.2, sprint 2'). The client approves documentation against a release, and it keeps sprint invoices from overlapping.
  • 3List deliverables by title or topic count, with where they were delivered (a merged pull request, a published help center section). The reviewer can check them in minutes.
  • 4Show review rounds: how many the agreement includes, how many happened, and any extra round as hours with the date it was requested.
  • 5Ask the client to provide licences for its own authoring or publishing tools. If you buy a tool for the project, agree it first and bill it at cost with the receipt reference.
  • 6Track SME interview and waiting time separately from writing time. If the agreement makes waiting billable, it is your evidence; if not, it explains a missed date.

Related Resources

Frequently Asked Questions

What should a technical writer invoice include?

Your business details, the client and any purchase order number, a unique invoice number, the invoice and due dates, the statement of work reference, the release or sprint covered, each deliverable by title or count with its rate, hours by activity, any extra review rounds, agreed tool costs at cost, tax if you are registered to charge it, the total and how to pay.

Should technical writers charge per page, per hour or per project?

Per page or per topic suits reference material with a predictable shape, such as API endpoints or help articles. Hourly suits discovery, interviews and editing, where the effort is hard to predict. A fixed project or sprint fee suits a defined deliverable with clear acceptance criteria. Many technical writers combine them, for example a fixed fee for a guide and hourly billing for extra review rounds.

How do I define a page for per-page billing?

In the statement of work, before the project starts. Name the unit precisely: a finished page in the client's PDF layout, a help center article, an API reference topic, or a word count range. Then count that unit on the invoice. Vague units are the most common reason per-page invoices are disputed.

Can I bill for extra review rounds?

Yes, if your agreement limits the rounds included. State how many technical and editorial review rounds the fee covers, and bill any extra round as hours times rate, with the date the client asked for it and the document it covered.

Who pays for documentation tools and licences?

Whatever the agreement says. Clients usually provide access to their own authoring, publishing or source-control tools. If you have to buy a licence or subscription for the project, agree it in advance and bill it at cost with the receipt reference, or have the client buy it directly.

How much do technical writers earn?

The US Bureau of Labor Statistics reports a median wage of $90,390 a year ($43.46 an hour) for employed technical writers in May 2025. That is an employee wage, not a freelance rate: a freelancer's rate also has to cover unbilled time, tools, insurance and self-employment tax.

Can I create a technical writer invoice in InvoiceQuickly?

Yes. Type or say what you delivered and InvoiceQuickly drafts the client, lines, rates and due date into an editable invoice you review before saving. It has no project milestones, so enter pages and topics as line items; on Pro, hours can come from its timer and be billed into a draft invoice. Free covers 5 invoices, 5 clients and 3 AI drafts in total. Pro is $9 a month for unlimited invoices, email delivery, reminders, estimates and payment links through your own Stripe or PayPal account.