Technology & Services Exports: Current Action Guides
Reviewed by Finin2min Editorial Desk · Last reviewed 4 September 2026
Technology and service-export pages should connect contract, place of supply, LUT/refund, foreign exchange realisation, invoice evidence, data/privacy and transfer-pricing or withholding risk where relevant.
Quick View
Classify the transaction as export of service, OIDAR/digital service, SaaS subscription, consulting, royalty/licence, development service or data-processing support.
Create one export evidence file per customer or contract family.
Official source, working paper, approval, acknowledgement and correspondence.
A foreign customer address alone does not prove export treatment; payment, place of supply and recipient/use facts matter.
Workflow Map
- Identify customer, location, contract, service description, user location and delivery model.
- Check GST export/LUT/refund conditions and invoice wording.
- Map FEMA export realisation, bank evidence, purpose code and set-off/write-off rules where relevant.
- Review withholding, treaty, transfer-pricing and accounting treatment for group or IP-heavy services.
- Preserve contract, invoice, FIRC/e-BRC/bank advice, LUT, refund file, data-processing terms and correspondence.
Law and Source Map
| Area | What to check | Working control |
|---|---|---|
| GST export | Recipient, place of supply, consideration and LUT/refund conditions | Match invoice, contract, realisation and GST records. |
| FEMA realisation | Export proceeds, bank evidence and write-off/set-off conditions | Track timelines and AD bank correspondence. |
| Tax/IP | Royalty, FTS, transfer pricing and ownership of deliverables | Keep contract and tax memo with source support. |
| Privacy/cyber | Data processing, security and incident duties | Map data fields, processors and incident reporting route. |
Section-wise Decode
GST layer
Export of service requires more than a foreign client. Place of supply and receipt of consideration are key controls.
FEMA layer
Export realisation and bank evidence should be reconciled to invoices and accounting.
IP layer
Software development, licence and SaaS models can produce different tax and contract outcomes.
Data layer
Service exports that process personal data should keep data-processing and security evidence.
Working File and Reconciliation
For this technology and services export desk workflow, the working paper should not be a loose note. It should connect the official source, the user facts, the computation or decision, the filing or complaint route and the final evidence of closure. This is the control that prevents a guide from becoming generic advice.
| Record | Documents to keep | Reconciliation test |
|---|---|---|
| GST export | Source copy, fact note, approval trail, working sheet and closure evidence for recipient, place of supply, consideration and lut/refund conditions. | Match invoice, contract, realisation and GST records. Record who checked it, when it was checked and what exception was considered. |
| FEMA realisation | Source copy, fact note, approval trail, working sheet and closure evidence for export proceeds, bank evidence and write-off/set-off conditions. | Track timelines and AD bank correspondence. Record who checked it, when it was checked and what exception was considered. |
| Tax/IP | Source copy, fact note, approval trail, working sheet and closure evidence for royalty, fts, transfer pricing and ownership of deliverables. | Keep contract and tax memo with source support. Record who checked it, when it was checked and what exception was considered. |
| Privacy/cyber | Source copy, fact note, approval trail, working sheet and closure evidence for data processing, security and incident duties. | Map data fields, processors and incident reporting route. Record who checked it, when it was checked and what exception was considered. |
- Use the Technology and services export desk page with related internal routes only after the source row and workflow step have been matched to the facts.
- Keep a concise chronology if the matter involves a deadline, complaint, remittance, filing, notice, cyber event or board decision.
- Save the source material in the same folder as the working papers so that a later reviewer can reproduce the conclusion without relying on memory.
- Where the issue touches more than one law family, keep separate tabs for legal source, computation, portal filing, accounting entry and management approval.
Red Flags and Escalation Controls
Use this technology and services export desk page as a controlled workflow, not as a shortcut. Stop and escalate when the facts are incomplete, the official source has changed, or the evidence file cannot prove the conclusion independently.
- The source, facts or party status do not match the Technology and services export desk workflow.
- There is a statutory deadline, regulator notice, bank/portal query, complaint number, penalty exposure or money already at risk.
- The file has source material but no working paper explaining why that source applies to the present facts.
- Internal records disagree: books, portal acknowledgement, bank statement, tax return, statutory register or board paper show different facts.
When escalation is needed, preserve the current source copy, transaction chronology, working sheet, approvals, portal acknowledgements, correspondence and rejected alternatives. That record lets an adviser, auditor, banker or regulator see what was known on the decision date and why the action was taken.
Practical Example
Highlighted Points
- Keep the official source open while making the decision.
- Record the date, facts, conclusion and evidence owner.
- Escalate when money, penalty, licence, foreign exchange, personal data or limitation risk is present.
- Preserve portal acknowledgements and regulator correspondence with the working file.
Exam and Advisory Case Study
Exam case: A company claims export refund but cannot connect invoices to foreign remittances and contract scope. The tax position may be right, but refund evidence fails.
Advisory note: if the source, date, party status or evidence trail changes, redo the conclusion rather than copying a prior file note.
Finin2min Summary
Technology-export pages should join GST, FEMA, tax, contract, IP and data evidence instead of treating export as a single label.
Q&A
Does a foreign invoice automatically mean export?
No. GST export conditions and place-of-supply facts must be checked.
What evidence supports export realisation?
Bank advice, FIRC/e-BRC where applicable, invoice mapping and AD bank correspondence.
When is tax review needed?
Royalty, FTS, group transactions, IP transfer, treaty or withholding questions.
What should be linked internally?
LUT, export realisation, foreign software payments and privacy/data guides.
Primary Official Sources
Use the source as it stands on the decision date. Applicability can change with facts, dates, thresholds, entity type, residency and regulator instructions.