The 2026 incentive map for mobile app businesses

Four distinct families of incentives

For individual developers, Income Tax Law Article 20/B provides a dedicated bank account and 15% withholding mechanism for certain app-store income. Companies cannot use this individual exemption. For companies, the service-export profit deduction, Technopark regime and Ministry of Trade IT export support may be relevant if their conditions are met.

These instruments do not automatically apply together to the same income. Advertising revenue, store sales, subscriptions and bespoke software services for a foreign corporate customer can have different contractual and tax consequences.

Organize the file around revenue flows

Track gross sales, platform commission, refunds, country and tax deductions in separate columns in App Store or Google Play reports. Treating the net bank receipt as revenue can misstate both gross income and expenses.

The app's rights holder, developer agreements, brand ownership and source-code ownership also matter in support applications. Resolve fragmented structures in which an individual owns the rights while a company receives the revenue.

Build an eligibility matrix before seeking support

For each income stream, show the customer, place of use, platform, invoice, collection account and intellectual property owner in one table. Then apply each incentive's requirements to that table.

Ministry of Trade programmes may have critical application, prior-approval and expenditure-document deadlines. Preparing the application timetable alongside the marketing plan is safer than looking for support after spending the money.

Defining the scope and the right question

The subject of “The 2026 incentive map for mobile app businesses” cannot be assessed reliably by looking at one rate or one provision in isolation. The parties, place of activity, manner in which income arises, contractual basis of the payment and economic risks assumed by the business must first be identified. four distinct families of incentives is therefore not a secondary technical point; it helps determine the direction of the review. Two transactions that appear similar may produce different accounting and tax outcomes when the status of the parties, date, country, delivery method or nature of the service changes.

The first practical step is to express the decision question in one clear sentence. Is the business trying to record an existing transaction, identify a historic exposure, compare structures before launch or prepare a recurring compliance process? Without this distinction the review quickly becomes unfocused. The observation that separate revenue channels and contracting parties first. should not be recorded as a bare conclusion. The file should also state the evidence required, the assumptions used and the date of the legislation and guidance on which the analysis relies.

Legal form and economic reality should be read together. A registered activity code, invoice description or contract heading is not sufficient on its own. The file should include the work performed by personnel, digital platforms used, output delivered to the customer, cancellation and refund terms, ownership of intellectual property and the route through which money is collected. This makes the conclusion on the 2026 incentive map for mobile app businesses depend on the real operational flow rather than on labels chosen for individual documents.

Timing requires a separate review. Conditions for an exemption, incentive or filing obligation may change during a year, while transitional provisions, administrative explanations and technical system changes may affect the result. The transaction date, invoice date, collection date and period in which the service or delivery is completed should therefore be recorded separately. When applying the observation that do not confuse the individual exemption with corporate tax incentives., the source dates should remain in the working papers and the same conclusion should not automatically be carried into a later period.

A useful review records the current position, missing evidence, responsible people and next actions. This turns the digital economy assessment into a traceable file that can be updated and explained when circumstances or legislation change.

Mapping the business model and money flow

The subject of “The 2026 incentive map for mobile app businesses” cannot be assessed reliably by looking at one rate or one provision in isolation. The parties, place of activity, manner in which income arises, contractual basis of the payment and economic risks assumed by the business must first be identified. organize the file around revenue flows is therefore not a secondary technical point; it helps determine the direction of the review. Two transactions that appear similar may produce different accounting and tax outcomes when the status of the parties, date, country, delivery method or nature of the service changes.

The first practical step is to express the decision question in one clear sentence. Is the business trying to record an existing transaction, identify a historic exposure, compare structures before launch or prepare a recurring compliance process? Without this distinction the review quickly becomes unfocused. The observation that do not confuse the individual exemption with corporate tax incentives. should not be recorded as a bare conclusion. The file should also state the evidence required, the assumptions used and the date of the legislation and guidance on which the analysis relies.

Timing requires a separate review. Conditions for an exemption, incentive or filing obligation may change during a year, while transitional provisions, administrative explanations and technical system changes may affect the result. The transaction date, invoice date, collection date and period in which the service or delivery is completed should therefore be recorded separately. When applying the observation that platform reports, bank receipts and intellectual property ownership form the backbone of the application file., the source dates should remain in the working papers and the same conclusion should not automatically be carried into a later period.

Assessing the tax character step by step

The subject of “The 2026 incentive map for mobile app businesses” cannot be assessed reliably by looking at one rate or one provision in isolation. The parties, place of activity, manner in which income arises, contractual basis of the payment and economic risks assumed by the business must first be identified. build an eligibility matrix before seeking support is therefore not a secondary technical point; it helps determine the direction of the review. Two transactions that appear similar may produce different accounting and tax outcomes when the status of the parties, date, country, delivery method or nature of the service changes.

The first practical step is to express the decision question in one clear sentence. Is the business trying to record an existing transaction, identify a historic exposure, compare structures before launch or prepare a recurring compliance process? Without this distinction the review quickly becomes unfocused. The observation that platform reports, bank receipts and intellectual property ownership form the backbone of the application file. should not be recorded as a bare conclusion. The file should also state the evidence required, the assumptions used and the date of the legislation and guidance on which the analysis relies.

Timing requires a separate review. Conditions for an exemption, incentive or filing obligation may change during a year, while transitional provisions, administrative explanations and technical system changes may affect the result. The transaction date, invoice date, collection date and period in which the service or delivery is completed should therefore be recorded separately. When applying the observation that separate revenue channels and contracting parties first., the source dates should remain in the working papers and the same conclusion should not automatically be carried into a later period.