The STTR Convention Enters Force January 1. 83 Days to Get Your Monitoring Framework Right.
Albania's September 15 ratification activated the OECD's Subject to Tax Rule. No treaties are covered on Day 1 — but your provision team needs a watch list today.
Editorial source review — November 1, 2026. This machine-generated article has been reviewed, but is not certified accurate. Source-backed corrections are incorporated where established. Other legal, survey and product claims may remain unverified; check applicable primary authorities before relying on a deadline or tax position.
Findings in the original version: OECD confirms Albania's ratification brings the convention into force January 1, 2027. That is not entry into effect for every covered treaty or every taxpayer. STTR uses a 9% nominal-rate test, not GloBE's 15% ETR.
Albania ratified. San Marino was first. With Albania's accession on September 15, 2026, the OECD Multilateral Convention for the Pillar Two Subject to Tax Rule now has the two instruments it needs. The STTR Convention enters into force January 1, 2027.
No existing tax treaty will be "covered" on that date. The mechanism is treaty-by-treaty, not country-wide. Both parties to any bilateral treaty must join the Convention and notify the OECD that they want the treaty covered before the STTR applies to payments under it. That sequencing creates a false sense of safety. The monitoring framework you build — or fail to build — in Q4 2026 determines whether your tax team has visibility when the first treaties flip covered. That day is coming faster than most provisions teams have planned for.
What the STTR Actually Does
The Subject to Tax Rule is one of the most misunderstood pieces of the BEPS 2.0 architecture. It is not the GloBE income inclusion rule. It is not the QDMTT. It is a treaty-based mechanism that gives source jurisdictions a residual taxing right when covered income — interest, royalties, lease payments, and certain service fees — flows to a related party paying tax at below 9% on that income in its resident jurisdiction.
The mechanics are precise. If a source-country affiliate pays royalties to a related entity in a jurisdiction where that royalty income is taxed at an effective rate below 9%, the STTR gives the source country the right to impose a top-up withholding levy. The withholding is calibrated to the shortfall between the 9% floor and the actual effective rate paid on the covered income in the receiving jurisdiction. The source country is not taxing at a flat 9% on the gross payment — it is collecting the difference between what the receiving entity pays and the minimum floor.
That calibration matters enormously for the provision calculation. The top-up rate is not fixed. It is a function of the actual effective rate on covered income in the payee jurisdiction, which is itself a function of local tax rules, incentive regimes, and the payee's specific circumstances. A standard royalty rate table does not give you this number. A jurisdiction-level lookup does not give you this number. You need entity-level effective rate data at the payment type level.
Why "No Coverage on Day One" Is Not the Full Story
The treaty-by-treaty roll-out creates an asymmetric risk profile. You do not need to be in a covered-treaty jurisdiction to need a monitoring framework. You need your counterparty jurisdiction to be moving toward coverage — and you need to know when it crosses the threshold.
Developing-country members of the OECD Inclusive Framework are the primary drivers. Brazil, India, Indonesia, Mexico, South Africa — these are source countries. They pay royalties and service fees to MNE affiliates in low-tax jurisdictions. The STTR gives them a recovery mechanism. Many of them are active participants in the Inclusive Framework and are in the process of joining the STTR Convention or have already joined.
The sequence from "both Parties join" to "treaty covered" is months, not years. The OECD process requires both treaty partners to have joined the Convention and then made the coverage notification. For treaties between two Parties, the notification can be made and processed quickly. If your company has royalty flows from an Indian subsidiary to a low-tax IP holding vehicle, and India joins and notifies, you face a coverage event. The period between India's notification and your next quarterly provision close is not predictable from today.
The companies that are most exposed are the ones with the most classic BEPS structures: IP holding entities in low-effective-rate jurisdictions receiving covered income from high-activity subsidiaries in developing markets. Those structures were built before the STTR existed. The STTR was designed precisely for them.
The ASC 740 and IAS 12 Treatment
The FASB's staff position on Pillar Two GloBE was settled in 2023: top-up taxes under the IIR and UTPR are alternative minimum taxes. Reporting entities do not recognize or adjust deferred taxes for the estimated future GloBE burden. Top-up taxes on ordinary income expected to be incurred in a period are included in the estimated annual effective tax rate.
The STTR is structurally different, and the GloBE conclusions do not automatically transfer. The STTR is a withholding tax imposed at the source — levied on covered income at the time of payment, by the source-country tax authority, against the payor. It is a current-period tax expense of the payor entity in the period the payment is made and the withholding obligation arises.
For U.S. GAAP preparers: STTR withholding, once imposed under a covered treaty, is a current tax. The provision question is not how to classify it — it is whether to accrue for it in advance, and at what probability. Under ASC 740-10-25, uncertain tax positions require a more-likely-than-not threshold before recognition. For a covered treaty where the STTR rate, the payee entity's effective rate on covered income, and the payment amounts are all known, the accrual is not uncertain — it is current. For a treaty approaching coverage, the accrual lives in the range between probable and reasonably possible.
For IFRS preparers under IAS 12: the scope question is live. IAS 12 paragraph 2 excludes taxes outside the standard's scope. IASB staff have provided limited formal guidance specific to the STTR. The January 2023 IASB narrow-scope amendment provided temporary mandatory relief from recognizing and disclosing deferred tax arising from the Pillar Two legislation — but that amendment addresses the GloBE, not the STTR. Until the IASB provides STTR-specific guidance, IFRS preparers applying IAS 12 to STTR withholding should document their accounting policy choice and apply it consistently.
How F500 Tax Teams Are Getting Caught Flat-Footed
Most large-company tax departments now track GloBE legislative status by jurisdiction. Far fewer track the STTR Convention signature and notification status at the treaty-pair level.
The gap is data infrastructure. STTR monitoring requires four distinct layers: which intercompany payment flows involve covered income types; which jurisdictions are Parties to the STTR Convention; which treaty pairs have been notified on both sides; and what effective rate applies to covered income in the receiving entity's jurisdiction. Those four layers are not stored in any single system. The first lives in accounts payable and intercompany accounting. The second and third live on the OECD's treaty database. The fourth lives in local tax compliance records.
At Clarity Tax, we model this as a knowledge graph problem. Jurisdictions, treaties, notification status, payment types, and entity-level effective rates are nodes and edges. The monitoring question — does this payment flow trigger STTR exposure today? — is a query across that graph. A static spreadsheet cannot answer it at scale. A language model without the structured data cannot answer it correctly. The deterministic answer requires the current state of all four data layers, linked and queryable.
The companies that built GloBE provision infrastructure in 2023 and 2024 are better positioned. They already linked jurisdictional data to payment flows. They know their entity-level effective rates. The companies that deferred GloBE modeling are the same ones who have no data infrastructure for the STTR. The pattern from GloBE repeats: the companies that wait for formal coverage before building the model will be behind the moment the first treaty flips.
What to Do Monday Morning
1. Map your covered-income flows. Pull every intercompany payment involving royalties, interest, lease payments, and service fees. Flag the receiving-entity jurisdictions. This is your exposure map. 2. Download the current STTR Convention Parties list from the OECD. Cross-reference with your receiving jurisdictions. Any receiving jurisdiction that is already a Party, or is actively participating in Inclusive Framework discussions, belongs on your watch list. 3. For any watch-list jurisdiction, identify the bilateral treaty pair. Check whether the source jurisdiction (the one paying) is also a Party. If both sides are Parties, check whether coverage notifications have been made. This is the trigger event. 4. Calculate the effective rate on covered income for each at-risk entity. If the receiving entity's effective rate on the relevant income type is above 9%, exposure is zero. If it is below 9%, calculate the top-up rate at the actual shortfall. This is your STTR withholding exposure estimate. 5. Build the accrual logic into your Q4 provision framework now. Document the accounting policy on STTR under both U.S. GAAP and IFRS if applicable. Establish a quarterly review cadence for the Parties list and notification status. Assign ownership to a named person, not a function.
The STTR Convention enters force in 83 days. The work is not done when you note the date. The work is done when your provision system can respond — with a calculated number and a documented position — the day a treaty goes covered. That day is not January 1. It is the first time both parties to a treaty you care about complete the notification process. Build the monitor before the event. Not after.
Clarity Tax builds the data infrastructure that connects treaty status, entity effective rates, and intercompany flows into a queryable provision model — deterministic first, AI-assisted second. See how we approach Pillar Two STTR monitoring.