Direct answer for founders

Indian startups should review export contracts before signing the first overseas customer, not after the invoice is raised. A clean export contract should answer six practical questions: can the company legally export, can it invoice correctly, can it receive and evidence payment, can it protect IP and data, can it manage tax and FEMA records, and can it enforce the contract if the foreign customer delays, rejects or disputes payment.

This matters for SaaS, IT services, design studios, AI tools, engineering services, D2C brands, hardware companies, deeptech exporters, consulting firms and manufacturers. A foreign customer can look simple in a sales pipeline, but the legal file is more demanding than a domestic purchase order. Founders must align commercial terms with DGFT, GST, RBI/FEMA, banking, data protection, IP, warranties and dispute clauses.

Use official sources as the base. DGFT says an Importer-Exporter Code is a key business identification number mandatory for exports/imports unless exempted, with a specific service-export exception where Foreign Trade Policy benefits are not being taken: https://www.dgft.gov.in/CP/?opt=iec-profile-management. The GST portal explains that registered taxpayers making zero-rated exports without IGST must furnish LUT in Form GST RFD-11 before such supply: https://tutorial.gst.gov.in/userguide/refund/Furnishing_of_Letter_of_Undertaking_for_Export_of_Goods_or_Services.htm. RBI’s Master Direction – Export of Goods and Services, updated as on 17 July 2026, covers export realisation, AD-bank handling and EDPMS: https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=10395.

Why export contracts need a separate checklist

Domestic contracts usually fail because the scope is vague, payment terms are weak or liability is uncapped. Export contracts can fail for those reasons plus extra cross-border problems: wrong contracting entity, missing IEC, wrong GST treatment, no LUT, unclear place of supply, delayed inward remittance, foreign withholding tax, no bank realisation evidence, unworkable governing law, data transfer restrictions, customs documentation, product-quality claims and foreign dispute costs.

The founder should not treat the invoice and the contract as separate files. The contract should support the invoice, the invoice should support the bank receipt, and the bank receipt should support GST, FEMA, books, tax and diligence records.

First decide what is being exported

Before drafting terms, classify the deal.

If the startup sells both software and implementation, do not hide everything under one vague “services” heading. Split licence/subscription, implementation, support, custom development, data processing and reimbursable expenses. This makes GST, revenue recognition, IP and liability easier to explain later.

IEC and entity identity

The contract should use the correct Indian legal entity name, not only the brand name. Match the legal name with PAN, GSTIN, IEC, bank account and board authority. If the entity is a private limited company, the contract should not be signed by a founder’s proprietorship or personal email by habit.

Prepare:

Do not wait for a foreign customer to ask for a vendor form. Create a vendor-onboarding pack with incorporation certificate, PAN, GST certificate if applicable, IEC where applicable, bank details, authorised signatory proof, tax residency documents if needed and contact points for notices.

GST, LUT and export invoice discipline

For registered taxpayers making zero-rated exports without payment of IGST, LUT is not a year-end cleanup item. The GST portal guidance says LUT in Form GST RFD-11 is to be furnished before such supply. Founders should check this before the first export invoice.

Export invoice controls:

1. Confirm whether the supply qualifies as export of goods or services.
2. Check whether the customer is outside India and whether place-of-supply conditions are satisfied.
3. File LUT for the relevant financial year before export without payment of IGST.
4. Mention LUT/IGST treatment correctly on invoices.
5. Keep the contract, purchase order, invoice, bank realisation and GST return aligned.
6. Preserve shipping bill, bill of export, airway bill, courier records or service delivery evidence where relevant.
7. Reconcile export turnover with books, GSTR-1, GSTR-3B and bank receipts.

If a startup exports services, it should avoid casual invoice descriptions like “monthly work”. Better descriptions such as “SaaS subscription for project management platform for August 2026” or “software implementation milestone 2 under SOW dated…” help tax, bank and diligence teams understand the transaction.

FEMA and RBI export realisation

The export contract should make payment realistic within India’s export-realisation framework. RBI’s Master Direction states that export proceeds are generally required to be realised and repatriated within the prescribed period, currently nine months from the date of export until further notice, with AD-bank extension mechanics in specified cases. For founders, the operating rule is simple: do not sign a contract that makes collection vague, indefinite or dependent on approvals nobody controls.

Payment clauses should cover:

Founders should track FIRCs/FIRAs, eBRC where applicable, SWIFT/MT103 evidence, bank advice, customer remittance emails and export invoice mapping. “Money came in” is not enough for investor diligence; the company should show which invoice the money settled.

Scope, milestones and acceptance

Overseas disputes often start with unclear delivery. Put the operational detail into the contract or SOW.

For services and SaaS implementation, include:

• Deliverables and exclusions.
• Timeline and customer dependencies.
• Milestone acceptance process.
• Deemed acceptance if customer is silent for a defined period.
• Change request process and pricing.
• Support hours and response targets.
• Customer data, access and cooperation obligations.
• Consequences of delayed customer input.

For goods, include:

• Product specification and tolerance.
• Quantity, packaging and labelling.
• Inspection process.
• Incoterms and delivery point.
• Title and risk transfer.
• Insurance responsibility.
• Rejection window.
• Replacement, repair or credit process.

A founder should never rely only on a Zoom call, WhatsApp approval or a purchase order with missing specs. Put the commercial deal in written terms.

IP and product ownership

Export customers may ask for broad ownership of deliverables. That can be dangerous when the startup is reusing its core product, libraries, templates, models, designs, manufacturing process or know-how.

Use a three-layer IP structure:

For SaaS, the customer usually receives access rights, not ownership of the platform. For custom development, define whether the customer gets exclusive ownership, non-exclusive licence, source code access, escrow rights or only output rights. For AI products, clarify whether prompts, input files, training data, feedback and generated outputs can be used for product improvement.

Data, privacy and security terms

If the overseas customer shares personal data, business confidential data, patient/user/employee data or customer records, the export contract needs data-processing language. This is not only a foreign-law problem. Indian startups also need to maintain DPDP readiness and protect enterprise trust.

Review:

1. What data will be shared?
2. Who is controller, fiduciary, processor or service provider under the relevant framework?
3. Where will data be stored and accessed?
4. Can subcontractors process data?
5. What security safeguards are promised?
6. What is the breach-notice timeline?
7. What happens to data on termination?
8. Are audit rights reasonable?
9. Does the contract restrict use of customer data for AI training?
10. Are cross-border data-transfer obligations workable?

Do not accept unlimited audit rights, unrealistic breach notice in one hour, or security warranties beyond actual systems. Enterprise customers ask for strong terms; the startup should respond with honest controls and clear limits.

Warranties, indemnity and liability

Foreign customers may send long templates with unlimited indemnity, broad consequential damages, product guarantees and parent-company obligations. Founders must review these carefully before signing.

Founder-friendly but credible positions:

If a customer insists on uncapped liability, the founder should price, insure and board-approve the risk. A small export contract with unlimited liability can become a diligence problem.

Dispute resolution and governing law

Founders often accept foreign governing law because the customer says it is standard. That may be commercially necessary in some enterprise deals, but it should be a conscious decision.

Check:

• Governing law.
• Court jurisdiction or arbitration seat.
• Language of proceedings.
• Interim relief.
• Cost allocation.
• Service of notices.
• Time zone and address for notices.
• Whether small-value disputes have a faster escalation route.

For mid-market contracts, a practical escalation clause can prevent immediate litigation: account managers, senior executives, written dispute notice, cure period, then arbitration or courts. Also include a right to suspend access or stop shipments for undisputed overdue invoices.

Export data-room folder

Build this folder before fundraising or overseas scale:

Investor counsel will look for consistency. If the contract says USD 50,000, the invoice says consulting fees, the bank advice has no invoice mapping and GST returns show a different number, the founder will spend diligence explaining avoidable confusion.

Mistakes founders should avoid

• Signing in the brand name instead of the legal entity.
• Assuming IEC is irrelevant without checking DGFT rules.
• Exporting without planning LUT, invoice language and GST return treatment.
• Giving the customer ownership of the core platform.
• Accepting unlimited liability for a small pilot.
• Leaving foreign withholding tax and bank charges undefined.
• Allowing the customer to delay acceptance indefinitely.
• Not collecting remittance evidence from the AD bank.
• Mixing founder personal accounts with company export receipts.
• Ignoring data-processing and AI-training restrictions.

A 15-day export-contract readiness plan

Founder next steps

Before the next overseas signature, prepare a one-page export contract note covering the legal entity, supply classification, GST/LUT position, payment timeline, FEMA evidence, IP position, data risk, liability cap and dispute forum. The Best CS Firm In India approach is to make export revenue clean enough that sales, finance, tax and diligence all tell the same story.

Sources

• DGFT IEC profile management: https://www.dgft.gov.in/CP/?opt=iec-profile-management
• GST portal LUT guide for export of goods or services: https://tutorial.gst.gov.in/userguide/refund/Furnishing_of_Letter_of_Undertaking_for_Export_of_Goods_or_Services.htm
• RBI Master Direction – Export of Goods and Services, updated 17 July 2026: https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=10395
• GST portal refund guide for exports without payment of IGST: https://tutorial.gst.gov.in/userguide/refund/Refund_of_ITC_paid_on_Exports_of_Goods_and_Services_without_payment_of_Integrated_Tax.htm
• DGFT services and export-import guidance: https://www.dgft.gov.in/CP/?opt=services

FAQ Section

Founder / Business Takeaway

Export revenue becomes valuable when it is enforceable, collectible and explainable. Founders should treat export contracts as a combined legal, tax, bank and diligence file.

Related BSA Resources

• Startup Legal Documentation: https://www.bhavyasharmaandassociates.com/services/
• FEMA Compliance: https://www.bhavyasharmaandassociates.com/services/fema-compliance-foreign-investment-startups-2025-delhi/
• Fund Raise Due Diligence: https://www.bhavyasharmaandassociates.com/services/fund-raise-due-diligence-service-for-startups-delhi-bangalore-gurgaon-2025/
• Blog: https://www.bhavyasharmaandassociates.com/blog/