Software Company Accounting: Subscription Revenue, Development Costs and Incentives

This is written for managers and accountants of software firms, cloud service teams and systems implementation companies. It covers the three things most often recorded wrongly in this sector: when revenue is recognised, how development spending is treated, and how tax incentives are actually secured. In the technology files I have handled, most disputes with the tax office traced back to the gap between cash received and revenue earned.

Revenue models and when each is recognised

The common error is recognising a full year's subscription in the month it is collected: one inflated month, eleven empty ones, and tax paid before the profit exists. The underlying principle is in revenue recognition and the accrual basis.

Deferred revenue is the core account

Open a liability account for unearned revenue and keep a per-customer balance. Each month, that month's portion of every subscription moves to income. With any meaningful customer count this must come out of the subscription system itself, not a spreadsheet, or it will not be reliable at year end.

Development costs: expense or intangible asset

The largest cost in a software firm is the engineering payroll, and whether it is expensed or capitalised changes both reported profit and tax.

The standard's principle is simple. Research costs are always expensed. Development costs become an asset only when the full set of conditions is met simultaneously: technical feasibility of completion, intention to complete and use or sell, ability to use or sell, probable future economic benefits, sufficient resources, and reliable measurement of the expenditure.

That last condition is where most companies fail. Without timesheets by project, you cannot show which part of the engineering payroll went to which product. In this industry a timesheet is not merely a management tool — it is the supporting document for cost. Once the product is ready for use, the asset is amortised over its estimated useful life.

Knowledge-based and export incentives

Three incentive routes are typically available, and all share one condition:

1. Knowledge-based company incentives, subject to certification and renewal, and only for income from certified activities.
2. Export income incentives, subject to service export documentation and compliance with foreign exchange rules.
3. Special zone and science park incentives, subject to genuine establishment and activity within the zone.

All three require filing the return on time and keeping acceptable books. A relief accompanied by a late return or rejected books is lost in practice. Conditions are detailed in the knowledge-based exemption article.

E-invoicing and payment gateways

Two practical issues hit software firms harder than most sectors.

• Invoice date versus revenue date. Invoices usually follow the cash; revenue follows the service period. The difference is legitimate but must be documented with a reconciliation: invoices filed to the portal, revenue recognised, and the movement in deferred revenue must tie together. Filing requirements are in the taxpayer system guide.
• Payment gateways and aggregators. The amount landing in your account is net of fees, but your revenue is gross. Record the fee as an expense rather than netting it against income, and reflect settlement timing differences in the bank reconciliation.

Software services are in principle VAT-liable unless a specific exemption applies, with different mechanics for exported services. Confirm the current position for your product against the latest circular.

Public sector and enterprise contracts

A large share of the Iranian software market is institutional. Three points matter: withholding tax on payment under Article 104, performance retentions that remain your asset until released rather than a cost, and precisely defined delivery milestones, since those drive project revenue recognition. Long implementation contracts resemble contracting work structurally, and should be tracked by milestone.

Monthly indicators

• Monthly and annual recurring revenue and its growth trend
• Churn rate and the value of contracts not renewed
• Deferred revenue balance, a measure of committed future income
• Cost per project against hours recorded on timesheets
• Share of qualifying income in total revenue

Key takeaways

• Subscription revenue is earned across the term, not in the month of collection.
• Development costs cannot be capitalised without timesheets and project documentation.
• A gap between portal invoices and booked revenue is fine, provided you hold the reconciliation.
• Gateway fees are an expense, not a reduction of revenue.
• Incentives attach only to certified activity income, and the account split must exist from day one.