Does Your Company Pay for Software from Abroad? The DGII Could Change the Rules of the Game

The technological infrastructure of a modern company rarely ends at its borders. Management systems, cloud storage, cybersecurity, collaboration platforms, artificial intelligence tools, and specialized applications are increasingly being contracted out to international providers.

What might seem like a simple monthly subscription from an operational perspective can raise a much more complex question from a legal and tax standpoint: what is the company actually buying?

This distinction is particularly relevant in the Dominican Republic. The Dominican Republic's General Directorate of Internal Taxes (DGII) is currently holding a public comment period for a draft General Rule intended to regulate the tax treatment applicable to transactions involving software programs, including their acquisition, licensing, and the provision of associated services. The comment period remains open until September 15, 2026.

For Dominican companies, the potential impact extends beyond the tax department.

Contemporary technology contracts often bundle several components under a single invoice: access to a platform, user licenses, storage, technical support, implementation, maintenance, updates, and professional services. However, from a tax perspective, the business structure used by the supplier does not necessarily resolve the legal nature of each component.

Therefore, one of the most important questions for legal and financial management should be asked before signing: Does the contract describe precisely what is being paid for?

A seemingly innocuous clause can have significant effects on determining the applicable tax treatment, especially when the supplier is located outside the Dominican Republic.

The risk is multiplied in regional structures. A multinational company might negotiate a global software contract at its headquarters and then distribute the cost among subsidiaries. Another company might directly contract a foreign platform using a corporate credit card. A third might acquire the license through a local reseller along with implementation services.

Although from a technological standpoint, all three companies may be using the exact same product, the contractual and economic structure of each transaction may differ.

This makes the review of technology contracts a multidisciplinary task.

Four actions companies should take before their next payment for software abroad

First, compile an inventory of your main software and digital services contracts, especially those paid to non-resident providers.

Second, contractually separate, where applicable, licenses, implementation, support, maintenance, and other services, avoiding generic descriptions that make it difficult to determine the true nature of the transaction.

Third, review clauses related to taxes, gross-up, and withholdings. In many international contracts, the provider expects to receive the full agreed-upon price, passing on to the local client the economic impact of any tax obligations in the payer's jurisdiction.

Fourth, coordinate purchasing, technology, finance, and legal. The decision on how to procure software should not be made solely by the department that will use the tool.

The DGII proposal is still under discussion, and its final version may change. This makes it especially important to avoid definitive conclusions about obligations that are still undergoing the regulatory process.

But the direction of change already offers a clear signal: technology procurement is ceasing to be a purely operational matter.

For legal management, the real challenge won't be learning the technical architecture of each platform. It will be ensuring that the contractual architecture allows the company to know what it's acquiring, who is providing it, from where it's being provided, and what its true tax cost might be.

In an environment where virtually every company is becoming, in some way, a consumer of global digital services, that distinction can end up being as important as the price of the license itself.