React Developer Invoice Template

What This Template Includes

• Project or repository name
• Sprint or billing period dates
• Ticket or pull request references per line
• Component and feature development hours
• State management work (for example Redux or Context)
• API integration and automated test hours
• Code review, pairing and meetings
• Framework upgrades or migrations, priced separately
• Change order number and approval date (fixed-price work)
• Licences or services paid for the client, at cost
• Client purchase order number
• IP transfer and open-source licence note

How to Create Your React Developer Invoice

Recommended Payment Terms

Time-and-materials React work is usually invoiced every two weeks or monthly, at the end of a sprint, with net 14 or net 30 terms; short cycles keep the amount you are owed small if a client slows down. Fixed-price builds are billed by milestones the client can test, such as an approved prototype, a feature-complete staging build and production release, with each invoice due in 7 to 14 days. Corporate clients that pay net 30 after approving an invoice against a purchase order need the PO number on every invoice, and often a supplier form and W-9 before the first payment. State in the contract when copyright in the code passes to the client, typically on payment in full, and repeat it in the final invoice notes.

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

Tax Information

US business clients usually ask for Form W-9 before paying a contractor. For payments made in 2026, a client files Form 1099-NEC for a non-employee it pays $2,000 or more in the year (the threshold was $600 before 2026); payments by card or through a third-party payment network are reported on Form 1099-K instead (IRS Instructions for Forms 1099-MISC and 1099-NEC). Sales tax on custom software development, and on software delivered electronically, varies by state, and states often treat custom and off-the-shelf software differently, so check your state's guidance before adding tax. If you invoice clients abroad, state the currency and check whether your country's VAT or GST rules apply to digital services sold across borders. InvoiceQuickly applies one tax percentage per invoice and copies saved tax IDs to new invoice PDFs; check the saved IDs and PDF before sending when a client needs it. This is general information, not tax advice.

Industry context (2026)

React itself is open-source software released under the MIT licence, with copyright held by Meta Platforms, Inc. and affiliates, so a client never buys React from you: it buys the code you write on top of it. That is why the IP note matters. Under US copyright law, code you write as an independent contractor belongs to you unless it is a work made for hire or you assign it, and a transfer of copyright is valid only in a signed writing (17 U.S.C. sections 101 and 204), so contracts usually assign the code on final payment. Upgrade work is also a recurring cost of React projects: React 19 became stable on 5 December 2024, and the React team's upgrade guide lists breaking changes to work through, which is why upgrades are best quoted and invoiced as separate scope. For pay context, the US Bureau of Labor Statistics put the median annual wage for software developers at $135,980 in May 2025, and its wage data excludes self-employed workers, so a freelance rate has to sit well above the salary equivalent to cover taxes, equipment and unbilled time.

Worked example

Common mistakes to avoid

Invoicing Tips

• 1Reference tickets or pull requests on each line ('PR #412: booking calendar filters, 6.5 h'). An engineering lead can approve the invoice in minutes instead of asking what the hours were for.
• 2Separate building features from maintaining the codebase. Dependency updates, a React major-version upgrade or a build-tool migration are real work, but they are not the feature the client thinks they are paying for, so price them on their own lines.
• 3Bill code review, pairing and meetings as their own line, or state in the contract that they are included in your rate. Clients query them most when they appear inside feature hours.
• 4Pass through third-party costs at cost with the receipt, and say whose account they are in. Component library licences, hosting and testing services belong in the client's name.
• 5On fixed-price work, give every change request a number and an approval date before you start it, and bill it as a separate line so the original price stays visible.
• 6Put the IP clause on the final invoice: 'On payment in full, copyright in the deliverables transfers to the client under clause 9; open-source packages remain under their own licences.'

Related Resources

• All invoice templates
• How to invoice as a web developer: staged builds, launch payments, hosting and care plans
• How to invoice as an app developer: testable milestones and code ownership
• How to prevent scope creep: change orders before the work starts
• Invoicing for freelancers: W-9, 1099-NEC and a worked freelance invoice
• Pricing freelance services

Frequently Asked Questions