Invoice clients for test automation, manual QA, and quality assurance consulting. Professional invoices from Tidybill.
A QA engineer invoice covers work testing software systems to ensure they meet quality standards before release. QA engineers design test plans, write automated tests, perform manual exploratory testing, document bugs, and verify fixes. As businesses shift to continuous deployment, QA engineers increasingly build automated test suites using tools like Selenium, Playwright, Cypress, or pytest rather than doing purely manual testing. Contract QA engineers are often brought in at the testing phase of a project or to build a testing infrastructure that the internal team can maintain. Invoices should describe the testing activities performed, the tools used, the coverage achieved, and the number of bugs found and reported. For test automation projects, clearly distinguish the one-time cost of building the test suite from ongoing maintenance of automated tests.
| Service | Typical Rate | Unit |
|---|---|---|
| QA consulting (day rate) | 500 | day |
| Test automation suite development | 3000 | project |
| Manual exploratory testing | 60 | hour |
| Performance and load testing | 1000 | project |
| Security testing (OWASP top 10) | 1200 | project |
| Monthly test suite maintenance | 300 | month |
For project-based QA work, invoice on completion of each testing phase with a summary of what was tested, coverage achieved, and bugs found. For test automation projects, invoice at milestones: framework setup, initial suite complete, full coverage target achieved. For ongoing maintenance retainers, invoice monthly with a summary of test runs, new tests added, and flaky tests fixed.