Novosibirsk · Russian-qualified counsel Recognised by Pravo-300 · Best Lawyers · Kommersant
Tax

Navigating pre-declaration work and voluntary disclosure in Russia in the technology and software sector: a step-by-step overview

Kristina Kornouhova · June 2026 · 10 min read

For technology companies operating in Russia, voluntary disclosure before an FTS audit notice can significantly reduce penalty exposure. Make an enquiry.

Unlike many European tax systems, which provide a clearly codified voluntary disclosure regime with published safe-harbour deadlines, Russian tax law operates on a framework where the timing and quality of pre-declaration work — the preparatory analysis carried out before a corrective filing — determines whether a voluntary disclosure achieves full penalty relief or merely reduces it. For technology and software companies, this distinction carries particular weight. Royalty arrangements, licence fees, software-as-a-service structures, and cross-border IP cost-sharing agreements all fall within the Federal Tax Service's (FTS) stated enforcement priorities. Understanding the sequence of steps, and the points at which the opportunity to disclose voluntarily narrows or closes, is therefore a practical necessity for in-house counsel managing Russian subsidiaries or branches.

Step 1: Conduct an internal tax position review

Before any contact with the FTS is appropriate, a structured internal review is the essential starting point. For technology and software companies operating in Russia, this review has three distinct layers.

The first layer is a revenue-and-royalty mapping exercise. In-house counsel should identify every intercompany arrangement under which the Russian entity pays — or receives — royalties, licence fees, or software-subscription charges to or from a related party. Under Russian transfer pricing rules, these flows are subject to documentation requirements and arm's-length standards. A practical audit of whether documentation is current, whether pricing benchmarks have been refreshed in the past two to three years, and whether the characterisation of payments (royalty versus service fee versus distribution margin) is consistent with the substance of the arrangement is the minimum required.

The second layer addresses VAT treatment. Russian legislation introduced a VAT exemption for qualifying software products listed in the national software register. Whether a particular product qualifies, and whether the Russian entity has correctly applied the exemption or, conversely, incorrectly omitted to charge VAT on a supply that does not qualify, requires a careful product-by-product assessment.

The third layer is a review of permanent establishment risk. Software implementation, technical support, and product localisation activities carried out in Russia by personnel of a foreign group company can, depending on their duration and nature, create a taxable presence that has not been declared.

What to prepare before proceeding to Step 2:

If your internal review identifies potential exposures before FTS contact has been made, this is the moment to seek qualified Russian tax counsel. Make an enquiry: info@vetrovpartners.com |

Step 2: What does pre-declaration work actually involve in the Russian context?

Pre-declaration work, as understood under Russian tax practice, refers to the structured analysis and documentation work carried out before a voluntary corrective filing (an amended declaration, or uточнённая декларация) is submitted to the FTS. It is not simply an accounting correction. It is, in substance, the construction of a defensible legal and economic position that supports the corrected figures.

For technology and software companies, pre-declaration work typically involves four components. First, a legal characterisation analysis — determining whether the payments in question are properly characterised under Russian civil and tax law. A royalty under a licence agreement is treated differently from a service fee under a technical assistance agreement, and the difference affects not only the tax base but also the applicable withholding rate under a double taxation treaty. Second, an economic benchmarking exercise — producing or refreshing transfer pricing documentation to support the arm's-length nature of the corrected pricing. Third, a penalty exposure calculation — quantifying the underpayment amount and modelling the likely penalty and interest position under different disclosure scenarios. Fourth, a disclosure memorandum — a written analysis that records the reasoning, the corrections proposed, and the factual basis, structured to support the filing and to provide a record of the diligence process.

The quality of pre-declaration work matters because the FTS, when reviewing a voluntary corrective filing, does not treat all corrections as equivalent. A filing accompanied by documentation that demonstrates a thorough self-review — and that makes no attempt to conceal the origin of the error — is more likely to be processed without triggering a further field audit. A bare numerical correction with no supporting analysis, by contrast, routinely prompts additional scrutiny.

See also: Supreme Court enforcement trend in pre-declaration work — what changed?

Step 3: Submit the voluntary corrective filing — and understand the window

The corrective filing itself is submitted electronically through the FTS's standard declaration system. For corporate income tax, this means an amended declaration for the affected periods. For VAT, corrected returns are submitted period by period. The filing must be accompanied by payment of the underpaid tax and, where applicable, the statutory interest calculated on the underpayment from the original due date to the date of payment.

The penalty relief available on a voluntary corrective filing depends critically on when the filing is submitted relative to the FTS's own audit cycle. Under Russian tax legislation, if a corrective filing is submitted and tax and interest are paid in full before the FTS has notified the taxpayer of a scheduled desk or field audit covering the relevant period, the filing qualifies for full penalty relief — the penalty for underpayment is not applied. If a corrective filing is submitted after an audit notification has been issued but before the audit is formally completed, partial relief may be available, but it is not automatic and requires the FTS to acknowledge the correction in the course of the audit process.

This timing window is not theoretical. In practice, FTS field audits of technology and software companies — particularly those with intercompany IP arrangements — are initiated with relatively short notice, and the period between a desk audit query letter and a formal audit appointment can be weeks rather than months. For in-house counsel managing this risk, the practical takeaway is that the internal review described in Step 1, and the pre-declaration work described in Step 2, should not be deferred until an FTS query is received. By that point, the full penalty-relief window may already have closed.

Under Russian insolvency legislation and related enforcement practice, unpaid tax liabilities can create subsidiary liability exposure for directors and controlling persons of a Russian entity — a consideration that adds urgency for foreign groups where a senior executive holds a director position in the Russian subsidiary.

See also: Pre-declaration work and voluntary disclosure in Russia: legal framework analysis

For in-house counsel managing a Russian technology subsidiary with unresolved transfer pricing or VAT positions, the regulatory timeline leaves limited margin for delay. Request our practice review: info@vetrovpartners.com |

Step 4: How should technology companies engage with the FTS during and after a voluntary disclosure?

Post-filing engagement with the FTS is a discrete phase that many foreign companies underestimate. Submitting the corrective declaration and making payment does not end the process. The FTS will, in almost all cases, conduct at minimum a desk review of the corrected filing. For technology and software companies, this desk review will typically focus on three questions: whether the correction is arithmetically consistent with the supporting documentation; whether the transfer pricing benchmarking used supports the revised figures; and whether the corrected VAT position is consistent with the product classification applied.

The practical approach during this phase is to maintain consistent positions across all communications. Written responses to FTS queries should be coordinated with the pre-declaration memorandum produced in Step 2 — any inconsistency between the filing, the supporting documentation, and the written responses to queries creates a factual gap that the FTS is trained to identify and pursue. In-house counsel should ensure that all communications with the FTS during this phase are handled by — or at minimum reviewed by — Russian-qualified tax counsel, and that no informal verbal commitments are made by company personnel without prior coordination.

Where the corrective filing covers multiple tax periods or multiple transaction types (for example, both a royalty characterisation correction and a VAT exemption correction), the FTS may issue separate queries for each. Tracking these query streams and responding within statutory deadlines requires a project-management discipline that is easily underestimated by teams accustomed to tax authority engagement in other jurisdictions.

Step 5: Confirm closure and document the outcome

The final step is confirmation that the matter has been formally resolved. In the Russian context, this means obtaining from the FTS a reconciliation certificate (акт сверки) that records the absence of outstanding liabilities for the relevant periods. This certificate is not issued automatically after a corrective filing — it must be requested separately, and in practice it is advisable to request it once the applicable statute of limitations for a FTS challenge of the corrected period has run.

For technology and software companies with continuing intercompany arrangements, closure of one voluntary disclosure cycle should also trigger a forward-looking review. The factual and legal positions taken in the corrective filing become, in effect, the baseline from which the FTS will evaluate subsequent periods. If pricing, structures, or product classifications change, updated documentation should be prepared contemporaneously rather than retrospectively.

Vetrov & Partners' tax controversy practice advises on the full cycle — from internal risk review through corrective filing to FTS engagement and closure confirmation. A record of prior matters is available at /matters/.

Frequently asked questions

Q: How much time does a technology company typically have to submit a voluntary corrective filing before the FTS initiates a formal audit?

A: There is no fixed statutory window, and timing varies by company size, sector, and the FTS's own audit scheduling. In practice, technology and software companies with significant intercompany IP flows tend to attract desk audit attention within two to three years of a relevant transaction. The critical threshold is not the time since the transaction but the point at which the FTS issues a formal audit notification — once that notification is issued, the full penalty-relief window for voluntary disclosure closes. Companies should treat internal risk identification as the trigger for action, not the receipt of an FTS query.

Q: What documents does the FTS typically request when reviewing a voluntary corrective filing in the technology sector?

A: For technology and software companies, the FTS commonly requests transfer pricing documentation covering the corrected periods, including benchmarking studies and the economic analysis underlying the arm's-length position. For royalty and licence arrangements, the underlying agreements, any addenda, and payment records will be requested. For VAT corrections, product classification materials — including the basis on which a product was included in or excluded from the national software register — are typically required. Preparing this documentation as part of the pre-declaration work phase, rather than assembling it reactively after the FTS request, is materially more efficient and reduces the risk of inconsistency.

Q: Does a voluntary corrective filing in Russia protect against criminal liability for tax evasion?

A: Under Russian criminal law, a voluntary corrective filing that results in full payment of the underpaid tax and applicable interest before criminal proceedings are initiated is a recognised basis for exemption from criminal prosecution for a first-time tax offence. The conditions are specific and procedural — the filing must be voluntary, the payment must be made in full, and no criminal investigation may have been formally opened. This protection does not extend to repeat offences or to situations where the FTS has already referred the matter to investigative authorities. The interaction between the voluntary disclosure mechanism and criminal procedure requires careful assessment on a matter-by-matter basis.

Practitioner note

This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.

Facing a matter like this?

Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.

Make an enquiry