A mobile app developer should keep the store payout report for every period, a numbered invoice for every client payment, bills for cloud and tools, invoices for test devices, and a note on shared items. Hand them to your CA monthly. The record most often missing is the gross-to-credit trail for store payouts, because the bank shows only the final amount. Rules and limits change, so your CA decides what is claimable.
What proves the money coming in?
- Store payout reports for each period, saved as files the day they are issued.
- Bank credits matched to those reports, with a note on the period covered.
- Client invoices numbered in a single series, with a received or pending column.
- Contracts or work orders showing milestones and scope.
- Advance payments with a note of which milestone they relate to.
| Source | What you see in the bank | What you should also keep |
|---|---|---|
| Store payout | One net credit, possibly in rupees after conversion | The payout report showing gross, deductions, net |
| Client milestone | A credit with the client's name | Invoice and contract reference |
| Subscription revenue from your own app | A series of small credits or one monthly credit | A monthly summary from the payout source |
| Client advance | A credit before the work | A note of which milestone it is meant for |
Which cost documents belong in the folder?
- Cloud and backend bills by month.
- Tool, SDK and analytics subscriptions, including those billed in dollars.
- Store developer account charges, with dates.
- Invoices for test devices, with model and purchase date.
- Design asset receipts.
- Subcontractor invoices.
- Co-working, internet and power backup bills.
What if store payouts and bank credits do not add up?
Say the payout report for a period shows gross sales equal to ₹60,000, deductions of ₹18,000 and a net of ₹42,000. The bank should show a credit near ₹42,000, subject to any conversion or bank charge. If it shows ₹41,200, the ₹800 gap is a charge or conversion difference, and your note should say so. Do not adjust the report to match the bank. Keep both and explain the gap.
Keep release records too. A short list showing which app version went live on which date, and which client or product it belongs to, helps your CA understand why costs jumped in a particular month. A launch brings test devices, cloud load and design assets in the same few weeks, so a note on the cause turns a puzzling spike into an explained one.
How do I hand it over?
- Bank and card statements for the month.
- Store payout reports and client invoice register.
- A folder of cloud, tool and device bills.
- A list of subcontractor payments with their invoices.
- A note of items billable to clients.
- Your open questions at the top of the email.
Which mistakes are specific to this work?
- Recording only the net credit and losing the gross and deduction detail.
- Not keeping an invoice for a second-hand test device.
- Missing a developer account renewal because it was billed to an old card.
- Leaving a client's push-service or hosting bill inside your own costs.
- Mixing income from your own app and from client work in one total.
When a sheet stops being enough
If statements are the slow part, SpendixAI can import them as PDF, CSV or Excel files, let you review rows before saving, and keep receipts with transactions. The Export centre includes a standard all-transactions file you can send to your CA. It does not read store reports or raise invoices.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


