A SaaS business selling subscriptions to customers abroad still files one EDF per month, with each invoice as a row in Part 2B — even if that month has 400 invoices of USD 29 each. The practical challenges are volume, payouts that arrive in batches net of fees, and usage-based invoices whose amounts aren't known until the billing period closes. The good news: most SaaS invoices are under ₹10 lakh, so once paid they can be closed on a periodic declaration rather than invoice-by-invoice matching.
Key takeaways
- Each customer invoice is a Part 2B row; one monthly EDF covers all of them.
- With hundreds of invoices, ask your bank whether it accepts the Part 2B rows as an annexure or file upload — don't invent your own summary format.
- Usage-based invoices belong to the month of their invoice date, not the usage period.
- Card and aggregator payouts arrive batched and net of fees; keep payout reports that map each invoice to a payout.
- The ₹10 lakh declaration is your friend: one periodic declaration can close many small invoices.
Why SaaS strains the EDF
The EDF was designed around businesses with a handful of invoices a month. A typical SaaS company looks different:
| Characteristic | Traditional services exporter | SaaS business |
|---|---|---|
| Invoices per month | 3–20 | 100–5,000 |
| Average invoice | ₹2–20 lakh | ₹1,000–₹1 lakh |
| How customers pay | Bank wire | Card, wallet, payment link, sometimes wire for enterprise |
| What reaches the bank | One credit per invoice | Batched payouts, net of fees and conversion |
| Invoice amount known in advance? | Usually | Not for usage-based plans |
| Customer type | Businesses | Businesses and sometimes individuals |
None of this changes the rules. It just means you need a system rather than a spreadsheet you fill by hand.
Part 2B with hundreds of rows
The Regulations treat each invoice as one row in Part 2B. For a SaaS company that could mean a very long form.
What to do:
- Ask your bank how it wants high-volume EDFs. Some banks may accept a Part 2B annexure as a spreadsheet or a structured file alongside the signed form. Others may have a portal upload. Your bank's published policy under Regulation 19 is the authority.
- Don't collapse invoices into one "summary" row unless your bank explicitly accepts that. Each invoice is a separate export with its own realisation clock.
- Export directly from your billing system. Customer name, country, invoice number, date, currency, amount and plan description should come out in one report.
Our EDF form generator handles many Part 2B rows and totals them for field 1.22.
Usage-based billing: which month?
For metered or usage-based plans, the invoice is usually generated after the billing period closes. The invoice date decides which EDF it goes on and when its 9-month realisation clock starts.
| Billing period | Invoice generated | Goes on EDF for | Realise by |
|---|---|---|---|
| 1–31 Oct 2026 usage | 1 Nov 2026 | November 2026 (due 30 Dec 2026) | 1 Aug 2027 |
| 15 Oct–14 Nov 2026 | 15 Nov 2026 | November 2026 | 15 Aug 2027 |
| Annual plan, paid upfront | 20 Oct 2026 | October 2026 (due 30 Nov 2026) | 20 Jul 2027 |
Credits for downtime or overage reversals should be handled as credit notes, not by editing an invoice already declared.
Payouts: matching batches to invoices
When customers pay by card through a payment processor, your bank sees a payout — say USD 18,422.60 — covering dozens of invoices, after processor fees and possibly currency conversion. To close EDPMS entries, you need to connect the payout to the invoices.
Keep, for every payout:
- the processor's payout report listing each charge, the invoice it relates to, and fees
- the bank credit advice or FIRA for the payout
- your own reconciliation showing invoice totals, fees and the net amount
Decide with your bank and CA whether NRV in Part 2B should be the gross invoice amount or net of expected processor fees, and stick to it. Our guide to getting paid through Stripe covers processor payouts in more depth.
A worked example: Ledgerleaf
Ledgerleaf Software Pvt Ltd, a fictional Kochi SaaS company, sells an invoicing tool to small businesses in the US, UK and Australia. October 2026:
| Plan | Customers | Price | Invoices | Total |
|---|---|---|---|---|
| Starter (monthly) | 212 | USD 19 | 212 | USD 4,028 |
| Growth (monthly) | 96 | USD 49 | 96 | USD 4,704 |
| Annual plans renewed | 14 | USD 468 | 14 | USD 6,552 |
| Enterprise (wire, usage-based Sept) | 2 | Various | 2 | USD 7,850 |
| Total | 324 | USD 23,134 |
Ledgerleaf's October EDF has 324 Part 2B rows, exported from its billing system as an annexure in the format its bank asked for. At ₹84 per USD, field 1.22 is ₹19,43,256. Due 30 November 2026.
Every invoice is far below ₹10 lakh. Each quarter, Ledgerleaf gives its bank a single ₹10 lakh realisation declaration covering all invoices paid in that quarter, backed by processor payout reports. Unpaid invoices — failed cards that were never recovered — are listed separately so it can discuss them with the bank and its CA.
Failed payments, refunds and churn
| Situation | What to do |
|---|---|
| Card fails, customer never pays | Invoice stays unrealised; track it and discuss write-off with your bank and CA |
| Customer requests a refund after paying | Issue a credit note; keep the refund record; tell your bank if the invoice was declared |
| Invoice voided before sending | Don't list it; keep your billing system's void record |
| Customer upgrades mid-cycle | Pro-rated invoice is a new row on the EDF for its invoice date |
Our article on refunds to foreign clients after filing the EDF covers the refund side.
GST notes for SaaS
Selling SaaS to customers abroad is generally an export of services if the Section 2(6) conditions are met, including the customer being outside India and payment in convertible foreign exchange. With small, self-serve customers, keep evidence of customer location — billing address, card country, IP — because the GST position depends on it. Online services to individual customers can raise additional questions; ask your CA.
The EDF doesn't change any of this. For a broader view, see our guide to EDF for SaaS companies.
This is general information, not legal or tax advice.
Frequently asked questions
Do I need to list every SaaS invoice on the EDF?
Yes. Each invoice is a separate export and a separate row in Part 2B. Ask your bank whether it accepts the rows as an annexure or file upload when you have hundreds of invoices.
Can I put one summary line for all small subscriptions?
Only if your bank explicitly accepts that format. The Regulations treat each invoice as its own row with its own realisation date, so a single summary line may not let the bank track realisation properly.
Which month does a usage-based invoice belong to?
The month of the invoice date. Usage from October invoiced on 1 November belongs on the November EDF, and its 9-month realisation period starts on 1 November.
How do I prove realisation when card payouts are batched?
Keep the processor's payout report mapping each invoice to a payout, plus your bank's credit advice. For invoices up to ₹10 lakh, the bank may close entries on your periodic declaration that the money has been realised.
What about invoices for customers whose cards failed?
They remain unrealised. Track them against the 9-month deadline, try to recover payment and talk to your bank and CA about write-off if they can't be collected.
Bottom line
SaaS volume doesn't change the EDF rules; it changes how you produce the form. Export Part 2B straight from your billing system into our free EDF form generator, and close small paid invoices each quarter with the ₹10 lakh declaration.
This guide is general information for Indian businesses, not legal or tax advice. Rules and bank processes change — confirm specifics with your AD bank or chartered accountant.