Media, Entertainment & Gaming

Video Game - Post-Release Maintenance & Patch Costs (Expensed, Not Capitalized)

Expensing developer salaries and operational costs incurred after a game's commercial release for bug fixes, balance updates, and maintenance patches — these are post-release costs and cannot be capitalized.

Account NameTypeDebit ($)Credit ($)
Research & Development / Operations Expense - Post-Release MaintenanceExpense (+)3,200,000.00-
Salaries Payable / Cash - Live Ops & Maintenance TeamLiability (+) / Asset (-)-3,200,000.00

💡 Accountant's Note

After a game ships, developer costs transition from capitalizable to expensed. Post-release costs that are EXPENSED: bug fixes (patches that fix existing functionality without adding new features), routine balance updates, server maintenance, community management, and minor updates. The key distinction is maintenance vs. new feature development. Post-release costs that remain CAPITALIZABLE: significant new content additions that represent new features (DLC packs, expansions, new game modes — see separate entry). This maintenance vs. enhancement distinction requires ongoing judgment for live-service games (GaaS — Games as a Service) where the game is continuously updated.

Practitioner & Systems Framework

💻 ERP Architecture

For live-service games, time tracking systems must distinguish between: (1) live ops / maintenance work (expensed), (2) new DLC / content creation (potentially capitalizable), and (3) ongoing gameplay balance work (expensed). Many studios use separate project codes for 'live ops' vs. 'DLC development' to enforce the distinction. The line between a 'balance update' (expense) and 'new feature' (capitalize) requires a documented policy.

⚠️ Audit Flags

Auditors examine whether live-service game studios are properly expensing post-release maintenance. Companies that capitalize all developer costs after release (treating the entire live ops team as development) overstate intangible assets. Conversely, companies that expense all development costs miss capitalizing significant new DLC or expansion content that clearly represents new functionality.

📄 Required Documentation

Post-release development cost policy (maintenance vs. new feature determination criteria), time tracking records by project type (maintenance vs. new DLC), sprint/milestone documentation for post-release updates identifying maintenance vs. enhancement nature.

Professional Excel Template

Get the automated version of this entry. Includes built-in IFRS checks, VAT calculators, and SAP-ready upload formats.

Notify Me on Release
QA

Expert Analysis by Qusai Ahmad

General Accountant Supervisor & IFRS Specialist

Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.

LinkedIn Profile

Discussion & Community Questions