A QA tester freelancer should keep a record for every project billed, every platform payout received, and every device or tool paid for. Because income comes in pieces from different sources, a single sheet that lists source, date and amount does most of the work. The CA decides what is claimable, and rules and limits change, so confirm the current position with your CA.
What goes in the folder?
- Statements of work or emails stating the scope, rate and test period for each project
- Invoices to clients, numbered in order and tied to the period tested
- Payout statements from any crowd-testing or freelancing platform
- Bank statements showing each payment arriving, in full months
- Bills for devices, accessories, tool seats and data plans
- A device register listing each phone, its purchase date, price and whether it is still in use
Why keep a device register?
A shelf of phones is an asset trail. A register with one line per device, what you paid and when, answers the CA's question about what you bought and what is still used. When you sell or retire a device, add the date and the sale price. If you paid cash with no bill, note the seller and a photo of any handwritten receipt.
How do you record platform payouts?
Each payout statement shows tasks completed, fees and net payment. Keep the statement and note which bank credit it matches. If a platform pays in a foreign currency, keep the statement that shows the rupee amount credited. Do not try to recalculate it from a rate found later. Ask your CA how foreign-source income should be handled.
| Month | What to check |
|---|---|
| Each month | Match payouts and invoices to credits |
| Quarterly | Update the device register and cancel unused tool seats |
| Mid-year | Review unpaid invoices and any client who has stopped replying |
| Before year-end | Collect bills, tag mixed-use items, add a cover note |
Which mistakes are common among testers?
- Treating small platform payouts as too minor to record
- Keeping device bills only as photos on a phone that later breaks
- Not separating a testing SIM from a personal plan
- Missing an invoice for a project that ended on 31 March but was paid in April
- Skipping the note when a client cut the scope and paid less than agreed
What do you do about unpaid or part-paid projects?
If a client pays only part of a project, record what was received, what is still due and the date you last asked. If you agree to a smaller sum, write the agreed figure and the reason. A cancelled test cycle, a bug that was disputed and a scope cut all leave the same trace: money billed but not received. Make sure that trace is visible and explained, rather than left as a mystery.
What should the cover note say?
List the accounts used, which devices and plans are shared with personal use and in what proportion, any client that paid in cash, any payout in a foreign currency, and any project that spans two years. Mention any month with no income so the CA knows it is a quiet month and not a missing file.
Where does an app fit in?
Begin by building the device register and a payout sheet. Two simple tables, started today, will answer most of what your CA asks about assets and income at year end.
SpendixAI can import statements, keep receipts with their transactions and export a CSV, and its reports group spending by category and month. It does not read messages or connect to banks, so statement files and hand entries are what you work from.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

