Short answer: A software invoice or freelance receipt to a foreign client is not automatically VAT-free. Exemption needs a non-resident customer and use of the service abroad, together. Work aimed at Turkish users, a Turkish branch or the local market makes a VAT-free cut wrong; the standard rate applies. When the tests hold, the document carries an exemption note and the VAT return shows the export-of-services line.
In Ankara files paid through Upwork, direct contracts or corporate overseas deals, the most common error is “the client is foreign, so no VAT.” A document cut from a home office in Çankaya can show a foreign country code while the product is used in Turkey. This article separates the break points of a wrong VAT-free cut, instead of repeating a generic “what is service export” summary. The base framework is in service export tax exemption; receipt lines are in freelance receipts.
If both tests are not met, a VAT-free cut is wrong
VAT exemption on exported services needs a customer abroad and enjoyment of the service abroad. Missing either one, writing “exempt” on the document, opening an empty exemption line on the return and planning cash without VAT are three faces of the same error. A foreign-titled company resident in Turkey, a Turkish branch, or a product built for end users in Turkey may look “overseas” on the letterhead while enjoyment sits in Turkey.
Sole traders on freelance receipts and limited companies on e-invoices fall into the same trap. The document type does not create the exemption; the place of use does. “Worldwide license” in a contract is not, by itself, a VAT-free warrant. Use should be visible in the file through email, delivery notes and access evidence.
| Scenario | VAT-free cut | Practical note |
|---|---|---|
| US client, software only in foreign operations | Possible if tests hold | Exemption note + return line |
| Foreign title, Turkish branch / TR users | High error risk | Enjoyment may be domestic |
| Foreign marketplace, sales to TR consumers | Usually wrong | Service ends in Turkey |
| Support SLA, servers in TR, mixed users | Split by file | One blended line is risky |
| Collected via Stripe / Payoneer | Not enough alone | Payment rail ≠ exemption proof |
Platform payout is not exemption proof
Dollars from Upwork or similar platforms prove collection, not residence and place of use. A Stripe fee explains gross-to-net; it does not complete the exemption tests. In Ankara closings, contract and delivery evidence are read before the bank slip. Reverse that order and a VAT-free document has no spine in review.

Traces a wrong VAT-free cut leaves in the file
A bad exemption does not stay on one invoice. The VAT return’s exemption line swells, input VAT and full-exemption logic drift, and a correction return appears later. Provisional tax and the annual return may still show the right profit while VAT needs its own fix. “We will correct it later” grows both delay and penalty risk.
If the commercial price was set VAT-inclusive, adding VAT afterwards starts a collection fight. The reverse also happens: a VAT-free quote becomes expensive for the seller when exemption fails. Ask place of use at proposal stage and write the split into the offer.
When a VAT-free cut is the right direction
The customer is non-resident, the service ties to their foreign activity, it is not aimed at a Turkish branch or end user, the document carries the exemption basis, and the period VAT return shows the matching exemption code. Freelance receipts and company invoices follow the same logic. See service export and receipt lines in freelance receipts.
Income relief or refund of input VAT carry separate conditions. Seeing exemption on the invoice does not auto-create a refund. This article’s job is stopping the wrong VAT-free cut.

Practical order in an Ankara file
Before month-end ask three questions: Is the customer truly abroad? Does the software open to a user in Turkey? Do the document and the return speak the same language? On a no or a maybe, charge VAT; doubt is read for safety, not for exemption. Channel choice does not change the exemption—see e-Invoice vs e-Archive.
Wrong exemption lines pile up toward year-end. Scanning overseas documents in November–December is cheaper than a bulk correction in January. Deadline rhythm is in when the VAT return is due; this piece focuses on the exemption error inside that rhythm.
Frequently asked questions
If the client has a foreign title, is the invoice VAT-free?
Not automatically. Title is not enough; residence and place of use are read together.
Does a Stripe dollar payout complete the exemption?
No. Collection proof and exemption tests are separate.
What about SaaS opened to users in Turkey?
If enjoyment is domestic, a VAT-free cut is usually wrong; the standard rate applies.
What if older invoices were cut VAT-free by mistake?
Correct the period; add a correction return and file notes. Do not bury it in the next month.
Do freelance receipts follow the same rule?
Yes. Receipt or invoice does not matter; the nature of the work does.
If VAT is exempt, does withholding disappear too?
Foreign buyers often sit outside Turkish withholding, but that does not replace the VAT analysis. Read them apart.
Conclusion
A VAT-free software document to a foreign client is correct only when both tests are visible in the file. A foreign name or a FX slip is not enough. Work aimed at Turkish users or a local branch makes a VAT-free cut wrong. Fix place of use at proposal stage, use the exemption note on purpose, and keep the return line in the same language.
At Ankara Muhasebeci in Kızılay we read contract, place of use and the VAT line in one folder. Find the office on Google Maps. For your own contract see tax advisory or freelance accounting, or contact us.
