Short answer. Advances are allowed. Route the advance and the later payments through the same AD bank (or tell both banks), and the bank links the advance to your EDF entry once you invoice. Third-party payers are allowed when your bank is satisfied the deal is genuine. Declare the payer in Part 1 of the EDF, or be ready to show how the payer is linked to your client. No PO is fine under FEMA. Banks may ask for "an agreement or PO", but an accepted quote, a statement of work or a marketplace contract does the same job, and invoices up to ₹10 lakh close on your declaration anyway.
The edge cases at a glance
| Situation | Rule | What changes in your EDF | What the bank may want |
|---|---|---|---|
| Client pays some or all of it before you invoice | Regulation 10(1); Regulation 3(2)(b) for non-software services | Nothing in the form. Declare the invoice as usual; for non-software services you may file when the payment arrives | Contract, proforma invoice or PO for the advance; later, the invoice to link it to |
| Advance received, work never done | Regulation 18(1)(i) | No EDF, because there's no export | Refund request with Form A2, or reasons why a refund isn't possible |
| Parent, group company or agent of the client pays | Regulation 8 | Third-party name, address and relationship in Part 1 | Proof of the buyer–payer link if it isn't on the EDF or invoice |
| No purchase order | No FEMA rule requires one | Nothing | Over ₹10 lakh, an agreement, statement of work or equivalent |
| One payment for several invoices | Regulation 4(2) and the bank's matching | Nothing | An allocation by invoice number |
| You also buy from the same client | Regulation 7 (set-off) | Nothing | Written agreement with the client to set off, through the same bank |
| Invoice cancelled or cut after you declared it | Regulation 6 | Nothing. The existing entry is reduced | Your declaration up to ₹10 lakh; reasons and a credit note above it |
Advance payments
Advances are common for freelancers and agencies: a 30–50% deposit to start, a monthly retainer paid at the start of the month, or a prepaid block of hours. FEMA 23(R)/2026-RB allows all of them. The rules care about two things: which bank handles the money, and how the advance gets matched to an invoice later.
Keep it at one bank, or tell both
Regulation 10(1) says an exporter receiving an advance must route the advance and any later realisation through the same AD bank. You can use a different bank for the rest, but only if you've told both banks. DBS's policy adds that you should keep proof that you told them. In practice, this matters most if the deposit came to one account and you file EDFs with another bank. Send both banks a short letter naming the client, the contract and the advance's IRM reference.
When to file the EDF
The EDF is due within 30 days from the end of the month in which you raise the invoice (Regulation 3(2)). An advance doesn't start that clock, because there's no invoice yet. For services other than software, Regulation 3(2)(b) also lets you file the EDF on or before the day you receive payment. That's useful if your bank wants a declaration in hand when a large advance lands. If your work counts as software (see our Softex vs EDF guide), stick to the invoice-month deadline.
The purpose code on an advance
Banks often tag a pure advance with P0103 (advance receipts against export contracts). DGFT's eBRC FAQs accept P0103 for IT services alongside P0802, P0803 and P0807, and allow P0103 IRMs to be clubbed in an eBRC even though other codes can't be mixed. Some banks use the service's own code from the start. Either is workable, as long as your bank knows the payment is an advance against a named contract. Check the code in our purpose code lookup.
[Disclaimer] Banks differ on whether they want P0103 or the service code on a services advance, and on whether they open a separate advance entry in EDPMS. Ask your bank which it does before the first deposit arrives, so the advance and the invoice end up linked rather than as two loose entries.
Retainers and milestones
A retainer paid on the 1st for the month's work is an advance against that month's invoice. A 40% deposit on a three-milestone project is an advance against the first one or two invoices. Keep a simple ledger with the advance's IRM reference, the amount and the invoices it's been used against, and give your bank the same split. The bank can only close an EDF entry when it knows which money belongs to which invoice.
If the work never happens
Refund the advance through the bank that received it. DBS lists a request letter giving the reason and Form A2 for refunding an export advance. If a refund isn't possible, for example because the client agreed in writing that you keep the deposit for work already done, Regulation 18(1)(i) lets the bank close the advance entry after checking your reasons. Get that agreement in writing. An email from the client is better than nothing.
Interest on advances
Rare for freelancers, but if a contract pays the client interest on its advance, Regulation 10(4) caps it at the all-in-cost ceiling for trade credit under the Borrowing and Lending Regulations.
The GST side of an advance
For services, an advance can fix the time of supply under GST. If you export under an LUT, no IGST is payable, but you still issue a receipt voucher for the advance (Rule 50 of the CGST Rules) and adjust it in the final invoice. Our GST on export of services guide covers LUT, zero-rating and refunds.
[Disclaimer] How an advance for zero-rated services is reported in GSTR-1 depends on your registration and filing setup. Ask your CA before you file the return for the month the advance arrived.
Third-party payers
A third-party payment is one where the money comes from someone other than the client you invoiced. For service exporters it usually looks like one of these:
- The client's parent or group company pays from a central treasury, often in another country.
- The client's agency, reseller or prime contractor pays you for work done for its end client.
- An employer-of-record, payroll or accounts-payable provider pays on the client's behalf.
- The founder or a director of a small client company pays from a personal account.
Regulation 8 says your AD bank may allow third-party receipts if it's satisfied the transaction is genuine. That's a judgement for the bank, so make it easy.
Declare it in the EDF
Part 1 of the EDF has fields for the third party's name, address and relationship. Fill them when you already know who will pay. DBS's policy says a third-party receipt is permitted when the payer is declared in the EDF; otherwise it wants documents. Part 1 covers the whole EDF, so if only one invoice that month has a different payer, ask your bank whether it wants that invoice on a separate EDF. Our field-by-field EDF guide shows where the fields sit.
When you didn't know in advance
Often you find out only when the money lands. Banks then want evidence of the link between your client and the payer. Their 2026 policies list:
- a tri-partite agreement between you, the client and the payer,
- your invoice or the client's order naming the payer,
- a letter or email from the client confirming that the payer is paying on its behalf,
- evidence of common ownership, an invoice from the client to the payer, or a settlement letter (Axis).
A one-paragraph confirmation from the client is usually the quickest fix: "[Payer] has paid invoice [number] dated [date] for [amount] on behalf of [client], which is our [parent company / agent]."
Where the payer is matters
Axis says it accepts third-party receipts only through normal banking channels from countries that comply with FATF standards, and that receipts from countries on the FATF grey list need internal approval. Expect more questions if the payer is in a different country from the client, or in a higher-risk country.
A payer inside India is a different problem. GST treats a service as an export only if payment arrives in convertible foreign exchange, or in rupees where RBI permits. A domestic rupee transfer from someone in India paying for your foreign client usually doesn't meet that, and your bank may not match it to your EDF entry. Ask the client to pay from abroad.
eBRC and platforms
If you generate eBRCs for GST refunds, DGFT's FAQ 12 says to answer "yes" to "Is payment received from a third party?" on the self-generation screen. Payments through Skydo, Wise, Payoneer, Razorpay or Xflow show the platform or its partner bank as the remitter, which banks handle differently from a true third-party payer. See EDF when paid through Skydo, Wise or Payoneer.
[Disclaimer] Bank of America says it won't process a third-party receipt until any mismatch between the remitter and your documents is resolved. Other banks may credit first and ask later. If a payment from an unexpected payer is stuck, send the client's confirmation letter straight away rather than waiting for the bank to ask.
Clients with no purchase order
Plenty of overseas clients, especially startups and individuals, agree a price on a call or in a chat thread and never issue a purchase order. FEMA doesn't require one. The EDF asks for invoice details, and Regulation 4(2) asks the bank to be satisfied the transaction is genuine before crediting your account.
The gap is in the banks' internal policies. Axis lists a "Service Agreement / PO" among documents for services realisation. DBS lists the "underlying agreement / contract (where applicable)" and "service completion evidence (where applicable)". Bank of America wants export details, or purchase orders "or equivalent" for advances, on or before the day the money is credited.
Two things make this less scary than it reads:
- Up to ₹10 lakh per invoice, the entry can close on your declaration alone, invoice by invoice or in a quarterly bulk declaration. See the ₹10 lakh self-declaration guide.
- "Or equivalent" is broad. Banks want evidence that a real client agreed to buy a real service at that price, not a particular form.
A no-PO evidence pack
Keep these in one folder per client. Any two or three usually satisfy a bank asking for "an agreement":
| Document | What it proves | Strength |
|---|---|---|
| Signed engagement letter or statement of work | Parties, scope, price, payment terms | Strongest |
| Marketplace contract page (Upwork, Contra, Toptal) | Parties, rate, milestones, platform's record | Strong |
| Quote or proposal plus the client's "approved" email | Offer and acceptance | Strong |
| Chat or email thread agreeing scope and price | Agreement, informally | Fair; export a PDF with dates |
| Delivery proof: handover email, timesheets, repo or file access | The service was performed | Supports any of the above |
| Client company registry entry or website | The client exists and is outside India | Supports any of the above |
Fix it going forward
For new clients, send a one-page engagement confirmation and ask for a reply saying "agreed". Include: your legal or business name; the client's legal entity and country; who will pay, if different; the scope; the price and currency; the payment terms, including any deposit; and the SAC you'll invoice under. That one email covers the advance, third-party and no-PO questions in a single document.
Other awkward payments
| What happened | What to do |
|---|---|
| One payment covers several invoices | Send the bank an allocation by invoice number and amount. For eBRCs, one IRM can be split across several eBRCs. |
| Client paid more than the invoice | Tell the bank whether the extra is an advance on the next invoice or will be refunded, and keep the client's email saying which. |
| Client paid less (fees, tax withheld, discount) | Record the difference as a reduction under Regulation 6. See unpaid and short-paid invoices. |
| You buy software or services from the same client | Regulation 7 allows a set-off of what they owe you against what you owe them, within the realisation period. DBS asks for your request, a document showing both sides agreed, and both transactions routed through the same bank. |
| Invoice cancelled after you declared it | Issue a credit note and ask the bank to reduce or close the entry. DBS lists "credit note provided to buyer" among accepted reasons. |
| Payment arrived before you filed the month's EDF | Fine. File the EDF on its own deadline and give the bank the IRM reference so it can match the two. |
What three banks ask for
Regulation 19 makes every AD bank publish a policy and SOP for these cases. Here's what three of them say for the situations in this guide.
| Bank | Advances | Third-party payers | Agreement or PO |
|---|---|---|---|
| DBS Bank India | Disposal instructions and FEMA declaration; proof you told both banks if another bank is involved; refund needs a request letter and Form A2 | Allowed if declared in the EDF; otherwise documents explaining the payment, a business reason and no compliance concerns | "Underlying agreement / contract (where applicable)" and service completion evidence |
| Axis Bank | Credited on a per-payment or standing instruction; documents above set thresholds; an undertaking if the advance and the export documents sit with different banks | Normal banking channels from FATF-compliant countries; customer declaration, or evidence of the buyer–payer link if the payer isn't named in documents | "Service Agreement / PO", invoice, request letter with FEMA declaration, EDF |
| Bank of America (India) | Purpose code, FEMA declaration, PO, proforma invoice, contract or equivalent; more checks by size and tenor | Information confirming the buyer–remitter link; mismatches held until resolved | Export details or PO "or equivalent" on or before credit; deferral only by exception |
Charges for these steps vary. Our bank-by-bank tracker lists what we've found so far.
Worked example
Illustrative figures. A developer in Pune agrees a US$3,000 website build with a US startup over email. The founder replies "approved" to the quote. There's no PO.
- 12 August: the client pays a US$1,200 deposit to the developer's bank. The developer tells the bank it's an advance against the quote dated 8 August. The bank tags it P0103.
- 30 September: work delivered; invoice raised for US$3,000, showing the deposit received and US$1,800 due.
- By 30 October: the September EDF lists the invoice at US$3,000. The client has said its Singapore parent will pay the balance, so the parent's name, address and relationship go in Part 1.
- 20 October: the parent pays US$1,780 after a US$20 charge. The developer sends the bank an allocation: the August advance plus this payment, against the 30 September invoice. The US$20 is recorded as a reduction on the developer's declaration, since the invoice is under ₹10 lakh.
- Result: one invoice, one EDF entry, two payments linked to it, closed long before the realisation deadline (nine months from the invoice date, so 30 June 2027).
The routine
- Get a written yes before work starts. An accepted quote, a statement of work, a marketplace contract or a signed engagement letter. Name the client entity, the payer if it's different, the price, the currency and the payment terms.
- Tell your bank what each payment is. When money lands, say whether it's an advance, a final payment or a payment from a third party, and give the invoice or proforma number.
- Raise the invoice and declare it. Invoice the client entity, then list the invoice in that month's EDF. If someone else pays, fill the third-party fields in Part 1.
- Link payments to invoices. Ask the bank to adjust the advance against the invoice, and give an allocation when one payment covers several invoices.
- Close what doesn't add up. Record short payments, cancellations and credit notes as a reduction, and refund or settle advances for work that never happened.
Common mistakes
| Mistake | What goes wrong | Do this instead |
|---|---|---|
| Taking the deposit at one bank and filing EDFs at another without telling either | The advance and the invoice never link up | Use one bank, or write to both |
| Not telling the bank a payment is an advance | It's treated as a payment with no invoice, and stays open | Name the contract or proforma when it lands |
| Invoicing the payer instead of the client | The invoice no longer matches your contract | Invoice the client, and declare the payer as a third party |
| Accepting a rupee payment from an Indian contact "on behalf of" the client | May not count as export proceeds for GST or FEMA | Ask the client to pay from abroad |
| Relying on a call for the scope and price | Nothing to show the bank above ₹10 lakh | Send a one-page confirmation and get an "agreed" reply |
| Keeping a cancelled project's deposit with no paperwork | An advance entry stays open in EDPMS | Refund it, or get the client's written settlement and ask the bank to close the entry |
FAQs
Do I file an EDF when I receive an advance for a service?
The EDF is tied to the invoice: it's due within 30 days from the end of the month in which you raise the invoice. For services other than software, Regulation 3(2)(b) also lets you file it on or before the day payment arrives, so you can declare the export when the advance lands if your bank prefers. Either way, route the advance and the later payments through the same AD bank, or tell both banks if you switch.
Which purpose code should an advance for services carry?
Banks usually tag a pure advance with P0103 (advance receipts against export contracts). DGFT's eBRC FAQs accept P0103 for IT services alongside P0802, P0803 and P0807. Some banks use the service's own code instead. Tell your bank in writing that the money is an advance against a named contract or proforma invoice so it can link it to your later EDF entry.
What if I took an advance and the project was cancelled?
Refund the advance through the bank that received it. DBS, for example, asks for a request letter giving the reason and Form A2. If a refund really isn't possible, Regulation 18(1)(i) lets your bank close the advance entry in EDPMS after checking your reasons, for example a written settlement in which the client lets you keep the money for work already done.
Can my client's parent company pay my invoice?
Yes, if your bank is satisfied the deal is genuine (Regulation 8). Declare the payer's name, address and relationship in Part 1 of the EDF. If you didn't, banks ask for proof of the link: a tri-partite agreement, an invoice or order naming the payer, or a letter from the client confirming it. DBS, Axis and Bank of America all describe this in their 2026 policies.
Can someone in India pay on behalf of my foreign client?
Treat this as a red flag. An export of services under GST needs payment in convertible foreign exchange, or in rupees only where RBI permits. A rupee transfer from an Indian person usually doesn't meet that, and your bank may not accept it against your EDF entry. Ask the client to pay from abroad, and check with your CA before you accept it.
My client never sends purchase orders. Is that a problem for the EDF?
Not under FEMA, which asks for an invoice and an EDF, not a PO. Banks' internal policies do list an agreement or PO among supporting documents, but for invoices up to ₹10 lakh your declaration is enough to close the entry. Keep an accepted quote, a statement of work or a marketplace contract page on file in case the bank asks.
One payment covered three invoices. What do I tell the bank?
Give the bank an allocation: which invoice numbers the payment covers and how much goes to each. That lets it close all three EDF entries. If you generate eBRCs, DGFT lets you split one IRM across several eBRCs.
Related guides
Sources and limits
- Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026, FEMA 23(R)/2026-RB, amended up to 22 Sep 2026: Regulations 3, 4, 6, 7, 8, 10, 18 and 19 (RBI).
- DBS Bank India, Policy on Export, Import and Merchanting Trade (DBS): document checklist for export advances, refunds, set-off and third-party receipts; sections on third-party receipts and advance payment for exports.
- Axis Bank, export and import policy under FEMA 23(R)/2026-RB (Axis Bank): sections B.9 (third-party receipts) and C.2 (advances), and services realisation documents.
- Bank of America, N.A., India Branches, Policy on Handling International Trade Transactions under FEMA 23(R)/2026-RB (Bank of America): sections 3 (realisation and EDPMS closure) and 9 (export advances).
- DGFT FAQs on self-generation of eBRC, version 1.1, August 2025, FAQs 12, 26 and 27 (DGFT); DGFT Purpose Code and SAC Code Mapping, v1.0, as used in our lookup table.
- Section 2(6), IGST Act, 2017 (CBIC); Rule 50, CGST Rules, 2017 (receipt vouchers).
Sources checked on 22 October 2026. Bank policies change, and each bank applies its own thresholds. This guide isn't legal or tax advice. Confirm EDF and payment questions with your AD bank, and GST questions with your CA.