Licensing Software to Foreign Customers from Pakistan

A Karachi company signs a licence with a customer in Riyadh, Dubai or Frankfurt. The code ships in minutes. The money is where the law begins. Between the invoice and the rupees in the company's account sit Pakistan's exchange-control regime, the customer country's withholding rules, Pakistani tax treatment of export income, and a contract that — often without its drafters noticing — has already decided how each of those regimes will classify the payment. This briefing walks the money's path as the law stands in July 2026, and ends with the checklist we use when reviewing a cross-border licence.

Getting paid: exchange control on the export side

Pakistan's Foreign Exchange Regulation Act 1947 and the State Bank of Pakistan's Foreign Exchange Manual govern not just money leaving the country but money owed to it. Export proceeds — including proceeds of software and IT-enabled services — must be realised through banking channels and brought into Pakistan within a prescribed period from the export or invoice [applicable chapter and current realisation period for services exports — TO BE VERIFIED BY REVIEWING LAWYER]. Unrealised proceeds are not a private matter between you and a slow-paying customer: the authorised dealer reports them, and persistent non-realisation is a regulatory problem with the State Bank, not merely a receivables problem.

Three practical consequences follow. First, invoice through the same banking channel every time, in the contract currency, against a contract the bank has seen — banks match inward remittances to export declarations, and mismatched descriptions stall funds. Second, structure payment terms the regime can live with: long deferred-payment arrangements and netting-off against amounts you owe the customer may need specific permission [netting and set-off treatment — TO BE VERIFIED BY REVIEWING LAWYER]. Third, exporters of IT and IT-enabled services are permitted to retain a portion of their proceeds in special foreign-currency accounts for meeting expenses abroad, with the permitted percentage set by circular [current retention percentage and conditions — TO BE VERIFIED BY REVIEWING LAWYER]. That retention is one of the few pieces of working-capital flexibility the regime offers, and it is routinely left unclaimed.

The home tax position: the incentive that must be verified

Pakistan has for years treated IT and IT-enabled services exports favourably, but the mechanism has changed more than once — from outright exemption to a final-tax regime applied at a concessional rate on export proceeds, conditional on registration with the Pakistan Software Export Board and on bringing proceeds in through banking channels [current regime under the Income Tax Ordinance 2001, the applicable rate, and the PSEB registration condition — TO BE VERIFIED BY REVIEWING LAWYER]. Because Finance Acts adjust this area frequently, the current-year position should be confirmed before it is priced into anything. What has stayed constant is the architecture: the concession attaches to export proceeds realised through the banking channel, which means the tax benefit and the exchange-control compliance are the same fact. A company that lets proceeds sit offshore, or routes them through a founder's personal account, is not just risking FERA questions — it is walking out of its own tax concession. PSEB registration, renewed on time, is the cheap ticket that keeps the whole position intact [registration mechanics — TO BE VERIFIED].

The foreign tax position: royalty or service fee

Now stand at the customer's end. When your customer's finance team processes your invoice, their law asks one question with expensive consequences: is this payment a royalty or a fee for services? Payments characterised as royalties — classically, payments for the right to use copyright in software — attract withholding tax in most customer jurisdictions, commonly at rates of ten to fifteen per cent under domestic law, reduced or not by the tax treaty between Pakistan and that country [treaty rates for key markets — TO BE VERIFIED BY REVIEWING LAWYER]. Payments for services, or business profits of a company with no permanent establishment in the customer's country, frequently attract no withholding at all under the same treaties.

The line between the two is not what your marketing calls the product; it is what the contract grants. A licence that conveys rights to reproduce, modify or sublicense the software leans toward royalty. A subscription to access hosted software — SaaS on your infrastructure — leans toward services or business profits in many jurisdictions, though practice varies and some tax authorities characterise aggressively [treatment in principal markets — TO BE VERIFIED BY REVIEWING LAWYER]. Three contract terms manage the consequences. A gross-up clause decides who absorbs any withholding — without one, the exporter does. A cooperation clause obliges the customer to apply treaty rates and provide withholding certificates, without which you cannot claim foreign tax credit in Pakistan [credit mechanism — TO BE VERIFIED BY REVIEWING LAWYER]. And a tax-residence certificate from the FBR, obtained each year, is the document the customer's tax authority will demand before applying any treaty rate at all.

The contract: choices that decide everything above

Most disputes we see in this area were decided at signature. Grant language decides tax characterisation, so write it deliberately: licence, subscription, or development-for-hire are different animals to a withholding agent and to the State Bank's export framing alike. IP ownership needs explicit words, because default rules differ across borders — a bespoke build without an assignment clause leaves ownership ambiguous in two legal systems at once. Governing law and forum should be chosen with enforcement in mind: an arbitration clause seated in a New York Convention state gives you an award enforceable in Pakistan under the Recognition and Enforcement (Arbitral Agreements and Foreign Arbitral Awards) Act 2011, and enforceable against the customer at home — which a Pakistani court judgment may not be. Currency and payment mechanics should match what your authorised dealer can process without queries. And termination should deal with the licence's afterlife: what the customer keeps, what is deleted, and who certifies it.

Founders scaling into foreign markets face these questions alongside entity and employment choices abroad; we cover that wider picture in our note on cross-border expansion for startups, and the contract-level questions sit with our technology-law practice.

Cross-border licensing checklist

• Register with the Pakistan Software Export Board and diarise the renewal [conditions — TO BE VERIFIED].
• Confirm the current tax treatment of IT-export proceeds before pricing any deal [rate and regime — TO BE VERIFIED].
• Invoice every export through one authorised dealer, in the contract currency, referencing the contract.
• Know the realisation deadline for your proceeds and track receivables against it [period — TO BE VERIFIED].
• Claim the exporter's foreign-currency retention entitlement and document its use [percentage — TO BE VERIFIED].
• Decide characterisation deliberately: licence, SaaS subscription, or services — and make the grant language match.
• Check the Pakistan tax treaty with each customer country for royalty and services withholding rates.
• Obtain a fresh FBR tax-residence certificate annually and deliver it before first invoice.
• Include a gross-up clause or price the withholding you have agreed to absorb.
• Oblige the customer to provide withholding tax certificates within a fixed period after each payment.
• Put IP ownership and licence-back terms in express words for any bespoke development.
• Seat dispute resolution in a New York Convention jurisdiction and confirm enforceability both ways.
• Align termination consequences: surviving rights, deletion, certification, and final payments.
• Keep a per-customer remittance file: contract, invoices, bank credit advices, withholding certificates.

What this means for you

Treat the banking channel as the spine of the business: the exchange-control obligation, the tax concession and the evidentiary record all run along it, and every shortcut around it costs more than it saves. Verify the current IT-export tax regime and your PSEB status before pricing deals, not after year-end. Fight the characterisation battle in the contract, where it is cheap — the difference between a royalty and a service fee can be fifteen per cent of revenue, and it turns on grant language you control. Paper the treaty position annually with a residence certificate, and never absorb a withholding you did not price. And build the remittance file as you go, invoice by invoice, because the day you raise outside investment or sell the company, the cleanliness of the export record is the first thing diligence will test.