A game developer's money is lumpy: a publisher milestone one month, a small store payout the next, and months with nothing. Costs are lumpy too, with asset packs, test phones and store fees arriving in bursts. A tracker that records each cost against the game it belongs to, and income by source, lets you see which title is paying for itself.
Which costs does a game developer carry?
- Engine licences, asset-store purchases and plugin packs
- Freelance artists, animators or sound designers paid per asset
- Test devices: budget Android phones, a tablet, a controller
- App store developer account fees, charged yearly or once
- Music and sound-effect licences
- Build servers, cloud storage and crash-reporting tools
- Playtest costs, from a snack to a small cash incentive
- Travel to a game jam, meetup or publisher meeting
How do you separate business and personal use?
A gaming PC or console that is also your leisure machine needs an honest split. A device bought only for testing builds is clean business. Games you buy to study a mechanic are a grey area; discuss it with your CA rather than assume. Rules change, so write down what you decided and why, and stick with it.
Which categories suit game work?
| Category | Includes |
|---|---|
| Engine and assets | Licences, asset packs, plugins |
| Art and audio freelancers | Sprites, animation, sound design |
| Test hardware | Phones, tablet, controller |
| Store and platform fees | Developer accounts, listing fees |
| Music and sound licences | Tracks, effects |
| Servers and tools | Build server, storage, crash reports |
| Playtests | Incentives, refreshments, venue |
| Events and travel | Jams, meetups, publisher visits |
How would one month look?
Say a publisher milestone brings ₹60,000 and a small store payout brings ₹9,000, so ₹69,000 comes in. Costs: engine and asset packs ₹4,500, an artist ₹10,000, a test phone instalment ₹3,500, a yearly store developer fee ₹2,000, music licence ₹2,500, build server ₹1,400 and playtest incentives ₹1,200. The total is ₹25,100. Income less costs is ₹69,000 minus ₹25,100, which is ₹43,900. Remember that the yearly fee will not repeat next month.
Why track each game separately?
If you have three prototypes and one publisher deal, a single pile of costs tells you nothing. Say a game cost ₹30,000 over four months and another cost ₹18,000. If only the first one brought money in, you now know where your effort went. Tagging by game also makes a cancelled project easy to explain: the page shows what was spent before you stopped, and your CA will not have to guess.
What should you not forget?
- Store payouts arrive late and net of the platform's cut, so the bank figure is lower than the sales figure
- Overseas payouts in dollars may differ from the amount shown in the store dashboard
- Cash incentives given to playtesters at a local event
- Asset purchases made on a personal card at midnight during a jam
When is a sheet not enough?
A sheet works while you have a handful of lines. Once you juggle several games, several accounts and dollar payouts, matching each credit to a statement by eye gets slow, and mistakes creep in. That is the moment to move to a tool that imports statements and keeps the entries in one place.
What routine keeps it manageable?
- When a store or publisher payment lands, record gross, deductions and the net received.
- Tag every cost by game as you pay it.
- At month end, import statements and fix any untagged lines.
- Each quarter, add up cost per game and compare with income per game.
SpendixAI supports foreign-currency expenses and has a foreign-currency spend report, and its custom categories can carry your game names as sub-categories. You choose the base currency before importing, and it cannot be changed afterwards.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


