Business

Records a game developer should keep for the CA

Records a game developer should keep for the CA: publisher agreements, store payouts, asset bills, freelancer payments and statements across the year.

Editorial illustration for Records a game developer should keep for the CA

A game developer should give the CA the agreements behind each income stream, proof of every payout received, and bills for what was spent on each game. Because income can come from a publisher, a store and a client, in rupees or dollars, the paper trail matters more than for most freelancers. The CA decides what is claimable, and rules change, so confirm the current position with your CA.

What documents should be in the folder?

  1. Publisher or client agreements showing fee, milestones and rights.
  2. Milestone invoices you raised, numbered in a single series.
  3. Store payout statements for each platform, with the period they cover.
  4. Bank statements that show each payout arriving.
  5. Bills for engine, asset, audio and server costs, labelled by game.
  6. Payments to freelance artists and sound designers with their invoices.

How do you handle store payouts?

A store statement usually shows sales, the platform's share and what is paid to you. Keep both the statement and the bank credit, and write on the statement which credit it matches. If a payout is delayed or combined with another period, add a one-line note. The CA can then tie your sales to the money received without guessing.

What about foreign-currency income?

If a payout arrives in dollars, keep the credit advice or statement that shows the rupee amount actually credited. Do not recompute it from a rate found online. Ask your CA how foreign income and any related registration should be treated; the rules are specific and change.

Income sourceProof to keep
Publisher milestoneAgreement, invoice, bank credit
Store payoutPayout statement, bank credit
Client workContract, invoice, bank credit
Grant or prizeAward letter, bank credit

Which mistakes are common in game work?

  • Mixing costs for two games and being unable to say what each one cost
  • Buying test devices on instalments and keeping only the monthly debits, not the original bill
  • Paying artists through UPI with no invoice or note of the asset delivered
  • Losing store account fee receipts because they go to an old email
  • Not recording unreleased projects, so abandoned costs have no explanation

What about advances and recoupment?

Some publisher deals pay an advance that is later set against your share of sales. Keep the agreement page that explains this and a running sheet showing the advance, the sales credited against it and the balance. Without it, a later payment can look like new income or a missing amount. Ask your CA how an advance should appear, since the treatment depends on the contract and the rules change.

What should you do when a game is cancelled?

Close the ledger page with a line: date, reason, total spent, anything still owed to freelancers or a vendor. Keep licences and assets in case you reuse them. If a refund or a partial payment comes later, add it to that page, not to a new one, so the whole story sits in one place for your CA.

How do you hand it over?

Prepare a folder per year with subfolders for agreements, invoices, store statements, bills and statements. Add a note listing active games, any title released or cancelled during the year, and any month when you worked for a salary or a studio. If a payment is in dispute, tell the CA now rather than at filing time.

A tool can reduce the typing: SpendixAI can take statement files, keep receipts with transactions, and give you a CSV plus Tally, Zoho Books or QuickBooks style exports. It does not file returns or decide tax treatment.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports