Skip to content
AppDues
Log in
Contact salesSign up

Türkiye's 2026 Software Support: What the Approved List Means for App Teams

Türkiye's Presidential Decree No. 10962 took effect on January 1, 2026, replacing the older tiered framework under Decree 5447 with a simpler set of annual caps for service exporters. For app companies, the practical question is whether a subscription-management tool appears on the official approved software list — because that determines whether its cost can be counted toward the Software License Support program. This guide explains the program structure, the application route, and how to check whether a tool qualifies.

What Decree 10962 changes

The new decree consolidates several support programs that previously ran under separate rules. The headline reimbursement rate stays at 50% for most categories, but the annual ceilings rise substantially. Two structural shifts matter most for app businesses:

  • Tiered limits are gone. Under the old rules, platform-commission and marketing support dropped sharply after the first few apps. The new framework gives every app — up to ten — the same per-product cap.
  • Caps are larger. The total ceiling for platform commissions roughly doubles, and hosting support rises fivefold.

The comparison table below, drawn from the decree's published figures, shows the old 2024 limits against the new 2026 limits for a typical app developer. These are historical reference figures; confirm current thresholds with the administering authority before relying on them for a claim.

The approved software list and what it unlocks

The Software License Support program itself is not new. What changes for a given tool is whether it appears on the Desteklenen Yazılım Lisansları Listesi — the Supported Software Licenses List maintained under the program. Inclusion on that list is what allows an eligible Turkish company to count 50% of the tool's subscription fees toward reimbursement.

For a subscription-management platform, that means the cost of the tool can be treated as a supported software-license expense rather than an ordinary operating cost. The list is updated periodically, so the correct check is always against the current published version — not against a blog post or a vendor's own claim.

Checklist before assuming a tool qualifies:

  1. Confirm the tool's exact legal product name appears on the current approved list.
  2. Confirm your company meets the decree's eligibility conditions for service exporters.
  3. Confirm the invoice and contract are issued in a form the program accepts.
  4. Keep the approved-list entry and the invoice together in your claim file.

How the support categories fit together

The software-license reimbursement is one piece of a wider set of export supports. Treated separately, each cap looks like a line item; treated together, they describe a funding loop for an app business:

  • Subscription infrastructure produces the revenue data a company needs.
  • Software-license support offsets part of the cost of that infrastructure.
  • Platform-commission support offsets part of the app-store and Play-store commission a company pays.
  • Marketing support offsets part of the user-acquisition spend that follows.

The important distinction is that these are separate programs with separate caps. A software-license claim does not consume the platform-commission ceiling, and vice versa. A company that conflates them will either under-claim or file an ineligible expense. The decree's own table is the authoritative source for which category a given cost belongs to.

A worked example using the published caps

Suppose an eligible Turkish studio pays 400,000 TL per year for a subscription-management tool that appears on the approved list, and the applicable software-license ceiling is 2.5M TL per year at a 50% rate.

  • The 50% rate applies to the 400,000 TL spend, giving a potential reimbursement of 200,000 TL.
  • That 200,000 TL sits well inside the 2.5M TL annual ceiling, so the ceiling does not bind in this case.
  • If the same studio spent 6M TL on approved software, the 50% rate would imply 3M TL, but the 2.5M TL ceiling would cap the claim at 2.5M TL.

This example uses the figures published with the decree as a reference. It is not a calculation of any specific company's entitlement, and the actual ceiling depends on the program category and the current published limits.

The application route: HİB membership and DYS

The program is administered through the Ministry of Trade. Two access conditions sit in front of the claim itself:

  1. Membership in the Service Exporters' Association (HİB). Applications for membership are handled by HİB directly.
  2. Application through the Destek Yönetim Sistemi (DYS). Claims and supporting documents are submitted through this system.

A practical sequence is: confirm company eligibility, complete HİB membership, verify the tool appears on the current approved list, then file through DYS with the invoice and contract attached. Each step has its own processing time, so building the file in parallel with membership is usually faster than waiting for one step to close before starting the next.

A complete file matters: reimbursement depends on invoices and contracts that match the program's requirements, so finance and engineering should agree early on how tool costs are recorded. {{OWNER_PARTNER_DISCLOSURE}}

What to watch as the program matures

The decree signals that Türkiye intends to treat app exports as a strategic sector rather than an incidental one. For teams evaluating the program, three things are worth monitoring:

  • List updates. The approved software list is revised periodically; a tool that is absent today may be added later, and a tool that is present may be removed.
  • Cap adjustments. Annual ceilings are set by decree and can be revised; the figures in this guide reflect the 2026 framework.
  • Documentation standards. Reimbursement depends on invoices and contracts that match the program's requirements, so finance and engineering should agree early on how tool costs are recorded.

None of these points changes the core mechanic: eligibility depends on the company, the tool's presence on the approved list, and a correctly filed claim.

Old vs. new annual support limits for a typical app developer
Support ProgramOld Decree 5447 (2024 limits)New Decree 10962Change
Software License50%, ~1.83M TL/yr50%, 2.5M TL/yr+37%
Platform Commission50%, 2.5M TL/app (top 3), 600K TL/app (rest)50%, 4M TL/app (all 10), 20M TL total~70% effective increase
Digital Product Promo50%, 10M TL/app (top 3), 1.2M TL/app (rest)50%, 15M TL/app (all 10), 50M TL total~50% per-product increase
Hosting50%, 1M TL/yr50%, 5M TL/yr5x increase
General Marketing50%, ~11M TL/yr50%, 25M TL/yr~2.3x increase

Figures are the limits published with Decree 10962 as of the 2026 framework. They are a historical reference, not a current entitlement calculation; confirm current thresholds with the administering authority.

Frequently asked questions

Who is eligible for the software-license reimbursement?

Eligibility depends on three conditions: the company must meet the decree's service-exporter criteria, it must hold membership in the Service Exporters' Association (HİB), and the software must appear on the current approved software list. All three are checked before a claim is filed through DYS.

Is the reimbursement always 50%?

The decree sets 50% as the rate for most support categories, including Software License Support. The actual amount is also bounded by the annual ceiling for that category, so a large spend can be capped even when the rate is 50%.

Does a software-license claim reduce the platform-commission cap?

No. The categories are separate programs with separate annual ceilings. A software-license reimbursement does not consume the platform-commission ceiling, and the reverse is also true. Each claim should be filed against the correct category.

How do I check whether a tool is on the approved list?

Check the current published version of the Desteklenen Yazılım Lisansları Listesi. The list is revised periodically, so a vendor's own statement or an older article is not a substitute for the current list entry.