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

Navigating digital services tax for foreign companies operating in Russia in the transport and logistics sector: a step-by-step overview

Kristina Kornouhova · July 2026 · 12 min read

Foreign transport and logistics firms in Russia face digital services tax registration obligations. A step-by-step compliance guide. Make an enquiry.

Following amendments to Russian tax legislation that brought digital services taxation into comprehensive effect for foreign providers, transport and logistics companies operating in Russia have faced a materially changed compliance environment. For general counsel managing cross-border operations – whether overseeing freight booking platforms, fleet management software, navigation and route optimisation tools, or cargo tracking systems delivered electronically to Russian counterparties – the question is no longer whether Russian digital services tax applies, but how to structure compliance before the Federal Tax Service identifies the gap. This guide sets out the registration, calculation, reporting, and payment obligations under Russian law as they apply to the transport and logistics sector specifically, and explains what in-house teams should prepare at each stage.

What does digital services tax cover – and does it apply to your transport operations?

Digital services tax in Russia is levied on the provision of electronic services to Russian customers by foreign companies that lack a permanent establishment on Russian territory. The Russian tax framework defines electronic services broadly: services delivered and consumed via the internet or other digital networks, with minimal human involvement in the delivery process. For the transport and logistics sector, this scope reaches further than many general counsel initially assume.

Freight management platforms that connect shippers with carriers, real-time cargo tracking services accessible via web or mobile interfaces, digital customs documentation tools, telematics and GPS fleet management subscriptions, and route-planning software provided under licence to Russian legal entities or individuals all fall within the definition. The critical threshold question is whether the service is delivered electronically and whether the recipient is a Russian person – broadly defined to include Russian legal entities, individual entrepreneurs registered in Russia, and Russian individuals. Membership of Russia in the Eurasian Economic Union and the Commonwealth of Independent States does not alter the digital services tax obligations of foreign providers: Russian customers trigger Russian tax liability regardless of whether the foreign provider is based in an EAEU member state.

The tax is calculated on the gross consideration received for covered digital services, without deduction for the foreign provider's own costs. The applicable rate follows the standard VAT rate under Russian tax law. Where a Russian business customer is registered for tax purposes and has been issued appropriate documentation by the foreign provider, the Russian customer may in certain circumstances account for the tax itself under a reverse-charge mechanism – but this does not eliminate the foreign provider's obligation to register and file unless the Russian counterparty explicitly accounts for the tax and the contract structure has been designed accordingly. In practice, many transport and logistics contracts are not structured to place the reverse-charge burden squarely on the Russian customer, leaving the foreign provider exposed.

If you are uncertain whether your digital services provided to Russian transport counterparties trigger registration obligations under Russian law, make an enquiry: info@vetrovpartners.com |

Step 1 — Map your digital service flows to Russian customers

Before initiating registration, conduct a structured mapping of all digital service flows that may touch Russian customers. This is not solely an IT exercise: it requires the legal, tax, and operations functions to work jointly.

What to prepare before starting this mapping:

The mapping exercise should identify: (a) which services are covered by the digital services tax rules; (b) which Russian customer categories are involved (legal entities versus individuals); (c) whether any existing contracts contain a reverse-charge allocation that may reduce direct filing obligations; and (d) the approximate annual revenue base subject to tax – which determines both the registration priority and the potential penalty exposure from any prior period of non-compliance.

For transport and logistics businesses, common service lines requiring scrutiny include: digital freight exchange memberships or access fees, telematics platform subscriptions, automated customs declaration software, cargo insurance digital policy issuance, and logistics management system licences. Physical transport services – moving goods from point A to point B – are not themselves electronic services and do not attract digital services tax. The tax attaches to the digital layer.

Step 2 — Register with the Federal Tax Service

Foreign companies providing digital services to Russian customers are required to register with the Federal Tax Service as a foreign organisation for digital services tax purposes. This is a distinct registration from any other tax or legal presence in Russia and does not of itself create a permanent establishment or otherwise alter the company's Russian legal status.

Registration is completed electronically via the Federal Tax Service's dedicated portal for foreign digital services providers. The application requires the following:

Identification details of the foreign company (legal name, country and place of incorporation, registration number in the home jurisdiction)Description of the digital services providedIdentification of an authorised representative for tax purposes (this may be an in-house tax officer or an appointed external adviser)Contact details for correspondence with the Federal Tax Service, including an email address used for official notices

The Federal Tax Service does not impose a minimum revenue threshold for registration: the obligation arises as soon as covered digital services are provided to Russian customers. In-house counsel should therefore not apply a materiality filter at the registration stage – the question of whether a particular service line is covered should be resolved at the mapping stage (Step 1), and once coverage is confirmed, registration should follow without delay.

Failure to register does not eliminate the tax liability; it merely accumulates arrears, penalties calculated on the unpaid amount per day of delay, and the risk of enforcement action once the Federal Tax Service identifies the unregistered provider – which it increasingly does through data shared by Russian payment systems and counterparties.

For in-house counsel managing digital service compliance for transport operations across Russia, our tax controversy team can advise on registration strategy and manage the Federal Tax Service registration process on your behalf: info@vetrovpartners.com |

Step 3 — Calculate the tax base for each reporting period

The tax base is the total value of digital services provided to Russian customers in the reporting period, expressed in Russian roubles. Where the consideration is denominated in a foreign currency, conversion applies at the rate published by the Russian Central Bank on the last day of the reporting period.

For transport and logistics companies, the calculation presents two recurring practical difficulties. The first is allocation: where a contract bundles digital services with physical transport or other non-digital components, only the digital services element attracts digital services tax. Contracts that do not separately price the digital and physical components require an allocation methodology – and the Federal Tax Service expects that methodology to be documented, consistent, and defensible. An undocumented allocation is a red flag in any tax audit.

The second difficulty is identifying the customer's location. Russian tax law establishes a hierarchy of indicators for determining whether a customer is Russian: the customer's registration or incorporation in Russia; the customer's payment through a Russian bank or using a Russian payment intermediary; the customer's IP address being Russian. For business-to-business services in the transport sector, the first indicator – the customer's registration in Russia – will typically be determinative, and the documentation burden is lower. For platform-based services reaching individual end-users, the location indicators require systematic review of transaction data.

Reporting periods are quarterly. The tax declaration is filed, and payment is due, within the specified period following the end of each quarter. The Federal Tax Service's portal used for registration also hosts the filing interface.

Step 4 — File the tax declaration and make payment

Filing is conducted electronically through the Federal Tax Service portal. The declaration requires the foreign company to report the total value of covered digital services provided to Russian customers in the quarter, the applicable tax rate, and the amount of tax due. Supporting documentation does not need to be submitted with the declaration but must be retained and produced on request in the event of a tax audit or enquiry.

Payment is made by bank transfer to the relevant Federal Treasury account. Foreign companies without a Russian bank account may encounter practical difficulties at this stage – most foreign banks require specific payment purpose codes and beneficiary identifiers that differ from standard international wire transfer fields. Identifying the correct payment details in advance of the first filing date reduces the risk of payment failure and the resulting penalty exposure.

Where a Russian customer has agreed in the contract to account for the digital services tax itself and has done so demonstrably, the foreign provider may be able to reduce its declaration accordingly. This requires written confirmation from the Russian counterparty of the amount self-assessed and paid. In practice, obtaining and retaining this confirmation for each relevant counterparty in each quarter is administratively demanding, and the tax team should establish a systematic process rather than relying on ad hoc requests.

For guidance on structuring contract terms with Russian transport counterparties to allocate digital services tax obligations effectively, or to discuss an FTS dispute arising from prior non-compliance, make an enquiry: info@vetrovpartners.com |

Step 5 — Manage ongoing compliance and audit risk

Once registered and filing, the compliance obligation is ongoing and quarterly. The main risk vector for transport and logistics companies after initial registration is not the headline tax calculation but the audit triggers that arise from inconsistency.

The Federal Tax Service cross-references digital services tax declarations against data from Russian payment processors, Russian counterparty filings, and – increasingly – information exchange mechanisms with foreign tax authorities. A declaration that reports materially lower revenue than the Russian counterparty's records suggest, or that omits a service line reported in a prior quarter, generates an automated discrepancy flag that may lead to a formal tax enquiry.

Practical steps to manage ongoing audit risk include: maintaining a fixed allocation methodology and applying it consistently across all periods; retaining records of each transaction for a minimum of four years; documenting any changes in service offerings that affect the tax base; and ensuring that the authorised representative's contact details with the Federal Tax Service remain current, since official notices are sent to the registered email address and failure to respond within the prescribed period can escalate a routine enquiry into a penalty assessment.

For businesses with significant Russian digital services revenue, a periodic internal review – aligned with the quarterly filing cycle – is a more proportionate risk management tool than a reactive audit defence. The firm's Tax Controversy practice can assist in designing a compliance review framework, reviewing prior-period declarations for consistency, and representing the company in any Federal Tax Service digital services enquiry or dispute.

For related analysis on digital services regulatory developments, see Rospatent guidance on digital services and comparative analysis of digital services tax for foreign companies. A wider summary of cross-border tax matters handled by the firm is available at /matters/.

Frequently asked questions

Q: How long does registration with the Federal Tax Service take for a foreign digital services provider?

A: Registration via the Federal Tax Service portal for foreign digital services providers is typically completed within a few business days of a complete application being submitted. The process is electronic and does not require physical presence in Russia. The primary delay risk is in preparing the application correctly – in particular, ensuring the description of digital services aligns with the Russian tax framework's categories and that the authorised representative's details are in order. In-house counsel should allow additional time to coordinate internally across legal, tax, and IT functions before submitting the application, since an incomplete or inconsistent description of services can prompt follow-up queries from the Federal Tax Service that extend the process.

Q: What documents does a foreign transport and logistics company need to retain for digital services tax purposes in Russia?

A: The core documentation set includes: contracts with Russian customers covering the digital services in question, including any clauses addressing VAT or digital services tax allocation; invoices or equivalent billing records for each transaction with a Russian customer; records of the conversion rate applied to foreign-currency transactions; payment records showing amounts received from Russian customers; and, where the reverse-charge mechanism applies, written confirmation from each Russian counterparty of the amount self-assessed and paid. Records should be maintained for a minimum of four years, as this corresponds to the standard limitation period applicable to tax audit assessments under Russian tax law. Electronic retention is acceptable provided the records are retrievable in a legible format on request.

Q: What happens if a foreign company has been providing digital services to Russian transport customers without registering?

A: Non-registration does not eliminate the underlying tax liability. The Federal Tax Service has authority to assess the tax due, together with penalties calculated as a proportion of the unpaid amount for each day of delay from the date the obligation arose. In practice, the Federal Tax Service identifies unregistered foreign digital services providers through a combination of counterparty data, payment system information, and – for larger providers – direct enquiry. Once identified, the foreign company faces the full arrears position plus accumulated penalties. The most effective approach for a company that has not yet registered is to take professional advice before contact from the Federal Tax Service occurs: a voluntary registration and prior-period declaration, made proactively, is generally treated more favourably in an administrative context than a response to an enforcement notice. The firm advises on regularisation strategies through its Tax Controversy practice and has experience acting for foreign companies across the Siberian and Ural federal districts in Federal Tax Service enquiries.

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