How to Account for an Advance Received Against Exports?

TL;DR - Summary
- What is an advance received against export of services? - An advance received against export of services is an upfront payment, full or partial, that an overseas client makes to an Indian service provider before the services are delivered or completed.
- What is the accounting entry for an advance received against export? - Debit your bank account and credit Advance from Customer / Unearned Export Revenue with the INR equivalent on receipt, such as ₹8,32,000 for $10,000 at ₹83.20. Recognize revenue as the service is performed, not simply when an invoice is raised.
- How does the accounting entry for an advance received against export change when the exchange rate moves? - A non-monetary advance settled by delivering services stays at its historical rate. Exchange differences can arise separately on an unpaid foreign-currency receivable or an EEFC balance, not merely because the invoice-date rate changes.
- What are the common mistakes in the accounting entry for an advance received against export? - The common mistakes in accounting for an advance received against export are recording the advance as immediate revenue, ignoring forex fluctuations, mismatching invoice and bank records, applying incorrect GST treatment, failing to track partial shipments, and mixing up bank charges with the advance amount.
What Is an Advance Received Against Export of Services?
An advance received against export of services is an upfront payment, full or partial, that an overseas client makes to an Indian service provider before the services are delivered or completed. The unearned portion remains an advance liability; recognize revenue as the service is performed or on completion under the applicable standard.
The advance has two commercial purposes. It gives the Indian exporter working capital, and it acts as commitment security from the foreign client.
Consider an Indian software agency that receives $10,000 from a UK client before a single line of code is written. That $10,000 is an export advance. It becomes revenue as the related work is earned under the applicable standard, not simply because payment arrived.
How to Account for an Advance Received Against Export?
Record an export advance as a liability because you still owe the client services. Debit the Bank Account / EEFC Account and credit Advance from Customer / Unearned Export Revenue, normally a current liability for a short-term contract. AS 9 links service revenue to work performed through proportionate completion or the completed service contract method; Ind AS 115 recognizes revenue when or as performance obligations are met. Raising an invoice alone does not create revenue. The entries below assume a short-term, non-monetary advance settled through services, not a cash refund.
Entry 1: On Receipt of the Advance
- Debit: Bank Account / EEFC Account, with the INR equivalent of the foreign currency received (for example, $10,000 × ₹83.20 = ₹8,32,000).
- Credit: Advance from Customer / Unearned Export Revenue Account (Current Liability), ₹8,32,000.
Use the transaction-date exchange rate required by the applicable accounting standard. Keep the bank credit and conversion advice, remittance document and fee breakdown to support the foreign-currency amount, INR credit, date and rate used.
Entry 2: On Raising the Export Invoice and Recognizing Revenue
- Debit: Advance from Customer Account (liquidating the liability), ₹8,32,000.
- Credit: Export Sales Account, ₹8,32,000.
Recognize revenue as the service is performed under the applicable standard; the invoice date may differ. If earned revenue exceeds the advance, record an unpaid unconditional right to payment as Accounts Receivable / Debtors. Under Ind AS 115, an earned right still subject to another condition is a contract asset instead.
Entry 3: Forex Gain or Loss on Settlement (If Applicable)
Do not record a forex gain or loss just because the invoice-date rate differs from the receipt-date rate of a non-monetary advance. Exchange differences arise separately on monetary items such as an unpaid foreign-currency receivable or an EEFC balance.
For a fully prepaid $10,000 service, a move from ₹83.20 at receipt to ₹83.75 at invoicing does not create a ₹5,500 gain on the non-monetary advance. The advance and the revenue it funds remain ₹8,32,000. A retained foreign-currency bank balance is a separate monetary asset.
AS-11 Treatment of the Advance Liability
Under AS 11, classification depends on the obligation. An advance settled by providing services rather than paying a fixed or determinable amount of money is non-monetary and stays at its historical transaction-date rate. An obligation to repay a fixed or determinable foreign-currency amount is monetary and is restated at the closing rate. Assess the actual contract and refund obligation rather than treating every advance alike.
Foreign-currency debtors and bank balances, including EEFC funds, are separate monetary items and use the closing rate. For Ind AS reporters, Ind AS 21 Appendix B specifically uses the date a non-monetary advance is first recognized to set the rate for the related revenue. Each advance receipt has its own transaction date; this appendix is not part of AS 11.
GST Treatment on Export Advance
- Export of services: A qualifying export of services is zero-rated. Under a valid LUT or bond, it can be supplied without payment of IGST, subject to the export conditions and Rule 96A. An overseas client alone does not establish an export: the place of supply, permitted payment and other export conditions must also be met.
- Export of goods: GST is generally not payable merely on receipt of an advance for goods under the current rules. Apply the export invoice and LUT or tax-payment requirements when the supply is made.
- Reporting: Keep an advance register and report the export invoice in GSTR-1 Table 6A. Table 11A covers advances that create tax liability; do not treat every LUT export-service advance as a mandatory Table 11A entry or a separate zero-rated advance category.
FEMA / RBI Compliance Loop
- Purpose code: Give your AD bank the true purpose of the receipt and supporting contract or invoice. P0103 is the listed code for advances against goods-export contracts; services generally use the relevant service code. Confirm software-advance coding with your bank, as DGFT also accepts P0103 in specified IT-service eBRC workflows.
- Remittance evidence: Obtain the FIRA or other applicable remittance advice or certificate when available. Keep it with the bank credit, contract, invoice and payment reference. Check the document needed for each bank, tax or trade filing; FIRA and FIRC are not the same document.
- EDPMS matching: Give your AD bank the required export declaration, invoice and remittance details so it can update or close the relevant EDPMS entry. Separately, where you need an eBRC, reconcile the bank-uploaded IRM and self-certify the eBRC on DGFT.
Example of Accounting for an Export Advance
Assume an Indian software agency receives full payment of $10,000 for a $10,000 service contract, converts it to INR at ₹83.20, and completes and invoices the service when the rate is ₹83.75. There are no fees, and the advance is a non-monetary obligation to provide services. The advance and earned revenue are both ₹8,32,000; the later rate creates no forex gain on that advance.
Step 1: Receipt of Advance
| Account | Debit (₹) | Credit (₹) |
|---|---|---|
| Bank / Inward Remittance A/c | 8,32,000 | - |
| Advance from Customer A/c (Liability) | - | 8,32,000 |
This entry records the cash received and the matching obligation to deliver the service. Revenue is not touched.
Step 2: Invoice Raised and Revenue Recognized
| Account | Debit (₹) | Credit (₹) |
|---|---|---|
| Advance from Customer A/c | 8,32,000 | - |
| Export Sales A/c | - | 8,32,000 |
This entry releases the liability and books revenue when the service is earned; completion and invoicing coincide in this example. For milestones, release the related advance as revenue is earned. An unpaid excess is a receivable only when the right to payment is unconditional; otherwise Ind AS reporters may have a contract asset.
Step 3: Forex Gain or Loss Entry
| Account | Debit (₹) | Credit (₹) |
|---|---|---|
| No forex entry on the fully adjusted advance | 0 | 0 |
| Exchange Fluctuation Gain / Loss A/c | 0 | 0 |
No forex entry is needed for this fully prepaid, INR-converted example: $10,000 × ₹83.20 = ₹8,32,000. The later ₹83.75 rate does not remeasure the non-monetary advance. If foreign currency remains in an EEFC account, revalue that bank balance separately; an unpaid receivable can also create exchange differences.
Support the receipt-date rate with transaction and conversion records. Keep the historical rate for the non-monetary advance; use the applicable recognition, closing and settlement rates for separate monetary items.
What Are the Common Mistakes When Accounting for Export Advances?
Common mistakes include recording an advance as immediate revenue, confusing non-monetary advances with monetary balances, mismatching invoice and bank records, applying incorrect GST treatment, failing to track milestones, and mixing up bank charges with the advance amount.
- Treating the advance or invoice as automatic revenue: Credit a liability when the advance arrives. Recognize revenue when the applicable service-performance requirements are met, which may be over time or at completion. Neither receipt nor invoicing alone proves that revenue has been earned.
- Ignoring the type of forex balance: Record a non-monetary advance at its historical transaction-date rate. Do not revalue it merely because an invoice-date rate changes. Separately revalue monetary balances, including foreign-currency receivables and EEFC funds, and book the relevant exchange differences.
- Mismatching invoice, FIRA and export records: Keep a clear link between the advance remittance, bank credit, invoice and export declaration. Where an eBRC is required, reconcile the bank-uploaded IRM with the export details on DGFT. Resolve differences in amounts, dates, fees or references before relying on the records for a filing.
- Incorrect GST treatment: A qualifying export under a valid LUT or bond is supplied without payment of IGST, subject to the export conditions. Confirm eligibility and meet Rule 96A requirements rather than assuming an overseas client or LUT alone makes every service zero-rated. Keep the advance and invoice records reconciled.
- Not tracking partial shipments or milestones: When an advance covers multiple deliveries, release the related liability as revenue is earned. Maintain a running schedule of advances received, amounts applied and the remaining obligation, so each reporting period shows the right revenue and liability.
- Confusing gross receipts with net bank credit: Debit the bank only for the amount actually credited. If the client paid the full advance and a documented fee was deducted from your proceeds, debit Bank Charges separately and credit the gross customer advance. Check who bears the charge under the contract rather than reducing the client’s advance automatically.
How Does Skydo Simplify Receiving International Payments?
Once the accounting entries are sorted, the next task is matching the foreign-currency receipt, INR settlement, fees and remittance documents. Skydo provides payment tracking and automatically generated FIRA to help you keep these records together.
This is where Skydo comes in. Here is how it handles the inward remittance:
- Free FIRA: Skydo automatically provides a free Foreign Inward Remittance Advice for payments received through its platform. Download it from your inbox or dashboard after settlement and retain it with the invoice, bank credit and fee records.
- Free local receiving accounts: Skydo offers receiving details in currencies including USD, EUR, GBP, SGD, AUD and CAD. Overseas clients can use the relevant local payment route, and we convert and settle the funds to your Indian bank account. These are payment-receiving details, not your own foreign bank account.
- Settlement in 24 hours: Eligible payments can settle within 24 hours. Timing depends on the currency, payment method and checks. Our terms provide for commercially reasonable efforts to credit funds within one to three business days after screening and compliance checks, subject to other banks completing their checks.
- eBRC assistance: Skydo can help with export-realisation records. Confirm the available workflow with our support team. DGFT eBRC generation uses bank-uploaded IRMs and exporter self-certification; it is separate from your AD bank’s EDPMS update or closure.
- Setup and support: Sign up online and complete the required verification before receiving payments. Our India-based support team can help with payment and documentation queries by phone and WhatsApp.
Is GST applicable on advance received for export of services?
A qualifying export of services under a valid LUT or bond is supplied without payment of IGST, subject to the export conditions. Keep records of the advance and its adjustment against the invoice. Table 11A covers advances attracting tax liability; export invoices go in Table 6A. Do not treat Table 11A as a blanket reporting requirement for LUT advances.
What is the purpose code for advance received against export?
What happens if the advance is not utilised within the stipulated period?
Should the advance from a foreign client be restated at the year-end closing rate?
What document should I use as the exchange rate source for my journal entry?
How do I close the EDPMS/eBRC loop after adjusting the advance against an invoice?






