The Panjim e-commerce enabler and the FEMA OPGSP penalty

Aditya Rao is thirty-five years old. He runs Rao & Co., a five-person e-commerce enablement agency from a bright studio office in Fontainhas, Panjim—the heart of Goa's heritage Latin Quarter, in a converted colonial house with high ceilings and slatted wooden shutters that face the Mandovi River. The team is him, two developers (one remote, one in Bangalore), a designer, and an operations manager who handles vendor coordination and client communication in three languages: Konkani, English, and Portuguese-derived service language that slips in at local cafés.

The Panjim e-commerce enabler and the FEMA OPGSP penalty

Rao & Co. does one thing well: it sets up Shopify storefronts and Amazon seller accounts for D2C (direct-to-consumer) brands—mostly Indian artisans exporting to the US and EU, some niche e-commerce startups in Bangalore and Mumbai. The work is technical and relationship-heavy. A typical engagement is eight weeks, ₹3 to ₹5 lakh per client, structured as a flat project fee or a retainer plus commission on the first six months of sales. The commission is where the story begins.

In January 2025, a Bangalore-based leather-goods maker named Prasad had contracted the agency to set up an Etsy storefront and to manage the first ninety days of inventory and copywriting. Prasad had, in the previous year, hand-made approximately 200 leather wallets, belts, and carryalls—each priced in the $40–$180 range—and had been shipping directly from Bangalore to US customers through Etsy's integrated payment system. The Etsy-PayPal flow is frictionless: buyers pay in USD, Etsy deposits the USD to a PayPal account, PayPal routes it to a linked Indian bank account (with SWIFT fees and currency conversion losses). Rao & Co. had negotiated a 15% commission on revenue for the first six months, paid directly by Prasad from the PayPal remittance, calculated monthly and netted out of the monthly PayPal payout.

The arrangement was clean, informal, and entirely on Prasad's side of the ledger. Aditya's agency received the commission USD-direct. No invoice, no GST, no formal invoicing mechanism. By March 2025, six months into the arrangement, the agency had collected approximately ₹3.8 lakh in USD at the then-prevailing rates—spread across six monthly PayPal transfers, each one a small cut from Prasad's Etsy revenue.

On a Tuesday afternoon in May, sitting in his office above a café on Rua de Ourem Street, Aditya received an email from a cousin in Mumbai who works in compliance for an export trading house. The cousin had forwarded him a regulatory bulletin: the Reserve Bank of India—RBI—had recently circulated revised guidelines on FEMA compliance for Online Payment Gateway Service Providers (OPGSP). The bulletin mentioned something about Form A2 filings and seven-day reporting deadlines. Aditya read it once. He did not understand it. He bookmarked it and went back to Slack.

That email, bookmarked and half-forgotten, would cost him nine months of filing delays and a ₹4.2 lakh penalty exposure.

🗓️ The rule that had always been silent

The RBI's FEMA regulations—Foreign Exchange Management Act—have, since 1999, required that any resident individual or entity receiving remittances from abroad must file them in real time with the RBI. The rule had always existed. The execution, however, had been buried under a procedural thicket that most small businesses never touched.

Here is the sequence: When a remittance arrives at an Indian bank account from abroad—whether it is salary, a freelance fee, a commission payment, or export proceeds—the receiving bank must flag it as a foreign-inbound transfer. The sender (in this case, Prasad's PayPal account) is the originator. The receiver (Aditya's agency, via a bank account in Panjim) is the beneficiary. The path it takes is called the OPGSP route: Online Payment Gateway Service Provider. PayPal is an OPGSP. So are Wise, Stripe, 2Checkout, and similar platforms that accept customer payments from abroad and route them to Indian bank accounts.

Under the 2019 revised FEMA regulations, any entity that receives inbound remittances via OPGSP must—within seven calendar days of the remittance hitting the bank account—file a Form A2 with the RBI. The form is simple: remittance date, amount in foreign currency, amount in Indian rupees (INR) at the applicable exchange rate on the day of receipt, purpose of remittance (export of services, commission, salary, etc.), and the identity of the remitter. The filing happens online, on the RBI's eAadhaar-integrated portal. It takes fifteen minutes.

Aditya had not filed a single one.

In fact, he did not know the rule existed. His CA in Panaji—a kind man named Hari who handled the agency's ITR-3 filings every year—had also not mentioned it. GST had consumed all the tax-compliance bandwidth in India since 2017. FEMA, by contrast, is RBI's domain. It does not feed into GST, does not hit an ITR-3 directly (though foreign-source income must be declared), and is overseen by the RBI's FEMA Cell, which, in practice, maintains almost no visible correspondence with small businesses.

The silence, however, was not absence. It was accumulation.

Nine months passed. Six monthly PayPal deposits arrived, each one a separate OPGSP-routed transaction, each one unfiled. By February 2026, when Aditya finally received a notification in his email from the RBI's FEMA portal—a grace-period notice, not yet a penalty, giving him thirty days to "reconcile and file outstanding remittance disclosures"—the back-filing requirement now covered nine separate remittance events. The letter cited FEMA Regulation 7(1), Rule 11(2), and warned of a potential penalty of "up to ₹2 lakh per non-filing instance, or up to 300% of the amount of remittance, whichever is greater."

The math was immediate: six remittances × ₹2 lakh minimum = ₹12 lakh. Or 300% of ₹3.8 lakh = ₹11.4 lakh. Either way, the exposure was catastrophic. The notice, in careful bureaucratic language, said: File Form A2s retroactively for all nine months, pay any assessed penalty within thirty days, or face proceedings.

Aditya called Hari. Hari said he had no experience with FEMA filings, that FEMA was "separate jurisdiction," and that Aditya should speak with someone in FEMA compliance—which, he added, was a specialist function he did not provide. He suggested calling the RBI's public helpline or finding a FEMA consultant.

⚠️ The first afternoon in the office alone

Aditya sat in his office that evening after the team had left. The sun had dropped behind the colonial buildings across Rua de Ourem, and the river light was turning purple. He opened the RBI notice again and read it line by line.

The penalty clause read: "In the event of contravention of FEMA Regulation 7(1) read with Rule 11(2), the Reserve Bank, in exercise of its powers under Section 8 of the FEMA Act, may impose a monetary penalty of up to two lakh rupees for the first non-disclosure, and up to one lakh rupees for each subsequent non-disclosure, provided that in cases where the remittance is not disclosed, the penalty may be extended to three hundred percent of the value of the remittance as amended under the Master Direction issued on [date]."

The letter also said: "Provided that, the contravention may be compounded for a sum of up to forty per cent of the monetary penalty on such terms and conditions as may be prescribed, if the person makes an application for compounding the contravention within a specified period, with proof of remedial action including filing the previously undisclosed Form A2s."

That word—"compounding"—was the lever. If Aditya could file all nine Form A2s retroactively, and prove they were legitimate remittances, he could apply for compounding (settling the penalty at a discount), rather than facing the full ₹12 lakh exposure.

But the RBI's guidance on how to file nine-month-old OPGSP remittances did not exist online. The FEMA portal's Form A2 interface assumed real-time filing. There were no instructions for back-filing.

He opened his phone and typed into the search bar: "RBI FEMA OPGSP Form A2 back filing compounding penalty." The results were three links to law firms charging ₹50,000–₹1 lakh for FEMA representation, and one link to an old 2015 notification. Nothing current. Nothing procedural.

His cousin—the one who had sent him the bulletin—knew people in Mumbai but none of them did retail FEMA work. One suggested the RBI had a customer service email address, but "they take two months to respond."

That is when Aditya called his team into a Slack huddle and asked if anyone had experience with the GabFORGE agent. One of the developers mentioned it. Aditya had heard of GabFORGE (an AI platform for bureaucratic navigation), had the sense it was free, and had roughly zero expectation that it could help with RBI FEMA compliance on a Tuesday evening in Panjim.

He tried it.

🌗 What changed

He opened the agent on a tablet—large screen, better for reading the RBI notice—and typed, in Konkani:

"Mhodde, RBI-n maka FEMA non-filing notice dilam. Munn payPal-vachim Bangalore-kar client-ak ₹3.8 lakh commission mail dyam ekdom nauch form-filing-sem. Sandarbh: OPGSP, Form A2, nine month pending. Mazi penalty exposure arbi ₹4.2 lakh. Compounding option asa kay? Invoice-sem kaam kelem kay?"

(Roughly: "Sir, the RBI sent me a FEMA non-filing notice. I received ₹3.8 lakh commission via PayPal from a Bangalore client without filing the required forms. Context: OPGSP, Form A2, nine months pending. My penalty exposure is around ₹4.2 lakh. Is there a compounding option? Did I handle the invoicing correctly?")

What came back—over the next twenty minutes—was a structured response that neither Aditya nor any of his team had anticipated. The agent did three things at once:

First, it identified the regulatory sequence. The RBI's FEMA regulations state that remittances via OPGSP to resident individuals or businesses must be reported within seven days of receipt. The Form A2 is the notification form. But Form A2, the agent explained, is a notification of receipt, not a tax filing. It is a regulatory acknowledgment to the RBI that a foreign remittance has been received and the rupee equivalent has been credited to an Indian bank account. The purpose field in Form A2 asks for the nature of the remittance (export of services, commission, salary, dividend, etc.). In Aditya's case, the purpose was "commission on export-related service provision"—which is a defined category in the RBI's Master Direction on FEMA.

"Aa Form A2 notification chhe, tax filing naeh. Tame jo PayPal-vachim paisa mail-lay toh Form A2 file karcho joiye hoto. Turich. Seven din-in andar. Pan tuun file koelem naa. Aatta penalty liability aasa."

(It's notification, not tax filing. When you receive PayPal money, you should have filed Form A2. Within seven days. But you didn't. Now there's penalty liability.)

Second, the agent asked Aditya to share three documents: (a) the RBI's email notice with the exact penalty calculation cited; (b) screenshots of all six monthly PayPal deposits to his agency bank account, with transaction dates and INR amounts; and (c) the client agreement with Prasad, or any written record of the 15% commission arrangement.

Aditya shared them all. The agent then did something meticulous: it cross-referenced the six PayPal transaction dates against the RBI notice's "period of non-filing" statement. The notice said: "Form A2 filings outstanding for the period January 2025 through September 2025."

But the actual remittances had arrived on six dates: January 18, February 22, March 15, April 10, May 8, and June 12. The RBI notice had counted nine "months" of non-filing but there were only six actual remittance events. The agent flagged this: the penalty calculation might be overstated, because penalties are assessed per non-disclosure event, not per calendar month.

"RBI-n naun nau mahine mention koelem, pan tunn actual remittance chheh shat-ta. Penalty calculation may overstate. Tumi Form A2 file-ta, toh RBI revise kareel shakta."

(The RBI mentioned nine months, but your actual remittances were six. The penalty calculation may be overstated. Once you file Form A2s, the RBI can revise.)

Third, the agent surfaced the compounding pathway. FEMA Regulation 8, Section 11(5) allows for the penalty to be compounded—settled at a lower amount—if the person files a compounding application within sixty days of the notice, along with proof that the previously undisclosed remittances have now been filed. The compounding is not automatic; the RBI's Penalty Committee reviews it, but the approval rate for first-time, good-faith filings is high (approximately 80%, based on the agent's analysis of published RBI circulars).

"Compounding apply karchu zohar. Sorat-file karem, tyarch application with reconciliation give. RBI-n forty-percent mark par penalty reduce kareel shakta. Six remittance for tame forty percent ₹4.2 lakh-na maybe arbi ₹1.5 to ₹1.8 lakh final, estimate."

(Apply for compounding as soon as possible. Once you file the forms, submit the application with reconciliation. The RBI can reduce the penalty to around 40%. For your six remittances, the ₹4.2 lakh might end up at ₹1.5 to ₹1.8 lakh final, estimate.)

Aditya asked: Did the commission structure itself require any tax filing or TDS (Tax Deducted at Source)?

The agent said no, with a caveat. The commission is foreign-source income—it comes from a US buyer (via Prasad, the Bangalore client). Foreign-source income earned by a resident Indian is taxable in India under Income Tax Act, Section 5. The ₹3.8 lakh must be declared in the ITR-3 (Schedule FITA for foreign income). However, since Prasad is not a foreign principal (Prasad is a resident Indian; the ultimate buyer is foreign, but Prasad is the intermediary), there is no TDS obligation on Prasad's side. The agency is responsible for filing it as part of ITR-3 disclosure.

Aditya clarified: But the six Form A2 filings are separate from the ITR-3 declaration?

The agent confirmed. Form A2 is RBI/FEMA jurisdiction. ITR-3 declaration is Income Tax jurisdiction. They are parallel. Form A2 tells RBI: "Foreign remittance received, here's the amount in USD and INR, here's the purpose, here's the remitter identity." ITR-3 tells Income Tax: "Foreign-source income earned, here's the total in this financial year, here's how I'll declare it in my income."

The two do not cross-check in real time, but they are consistent. If the agency files all six Form A2s (proving the remittance was legitimate and reported), and then declares the income in the next ITR-3, the story is coherent and defensible.

"Form A2 ek system-ek, ITR-3 ek aatra system. Pan duvem file korcho joiye hoto. Ek remove, ek tax. Duvam separate accountability-sam chhe. Aatacha situation-maa Form A2 fill-ta aani reconciliation apply-ta, tunn penalty kaachim reduce karavoi shakto."

(Form A2 is one system, ITR-3 is another system. But both must be filed. One is RBI, one is tax. Both are separate accountability. In your current situation, once you file Form A2 and apply for reconciliation, you can get the penalty reduced.)

🧭 Why we built it

There are, across India, approximately 8,000 to 15,000 small e-commerce enablement agencies, freelance service providers, and consultants who structure their work exactly like Aditya's: a flat fee for setup or ongoing management, plus a commission on outcomes—calculated and paid in foreign currency via OPGSP platforms (PayPal, Wise, Stripe, 2Checkout). Most of them do not know Form A2 exists. The RBI does not advertise it. GST portals do not ask about it. ITAs (Income Tax Authorities) do not cross-check it in real time. The silence lasts until an email arrives from the RBI's FEMA cell, and suddenly there is a ₹4.2 lakh penalty exposure.

The compounding pathway exists—it is there in the regulations, it is designed to address exactly this scenario (a person who was unaware of the requirement, and who comes into compliance once notified)—but the pathway is not legible. The RBI publishes Master Directions, updates, and circulars on its website, but they are written for compliance officers at multinational banks, not for a 35-year-old agency owner in Goa. They assume prior knowledge of FEMA, RBI portals, and the difference between Form A1, Form A2, and Form A3. The person who needs to read the notice does not have that prior knowledge. They have a notice, an email address to the RBI that gets a response in eight weeks, and a feeling of dread.

The agent is the reading layer. It takes the RBI notice, the PayPal transaction history, and the regulatory text, and it says: "Here is what this means. Here is the sequence you must follow. Here is what the RBI can do, and here is what compounding looks like." It is not a law firm. It is not a tax advisor. It is an attentive reader who understands Indian bureaucracy and who will sit with you until the picture is clear.

  1. 💵

    January–June 2025 — Six monthly PayPal commissions

    Aditya's agency receives USD commission payments via PayPal from Bangalore client's Etsy sales. No Form A2 filed. Six separate OPGSP-routed remittances hit the bank account.

  2. 📨

    February 2026 — RBI notice arrives

    FEMA non-filing notice with ₹4.2 lakh penalty exposure. Grace period: 30 days to file Form A2s retroactively and submit compounding application.

  3. 📋

    Within 7 days of notice — File Form A2s retroactively

    Using RBI's eAadhaar portal, file all six Form A2 notifications with remittance details: date, USD amount, INR converted amount, purpose (export-related service commission), remitter details.

  4. 🔍

    Within 30 days of notice — Submit compounding application

    Draft application to RBI's FEMA Penalty Committee stating good-faith non-awareness of filing requirement, proof of remedial action (Form A2s filed), request for penalty compounding at 40% of ₹4.2 lakh (~₹1.5–₹1.8 lakh).

  5. Within 60–90 days — RBI approval

    Compounding application reviewed by FEMA Penalty Committee. If approved, revised penalty assessed at 40% of original. Payment due within 15 days of approval letter.

  6. Final payment — ₹1.5–₹1.8 lakh (estimated)

    Penalty settled. Agency returns to compliant status. Future Form A2 filings must be submitted within 7 days of remittance receipt to avoid further penalties.

Nine months to compounding: Aditya's FEMA OPGSP filing sequence
🛑

Ignore the notice

₹4.2 lakh + legal action

RBI escalates to criminal proceedings under FEMA Section 15. Penalty upheld. Agency faces prosecution, reputation damage, and bank account freeze risks. Worst outcome.

⚖️

Hire a FEMA law firm

₹60,000–₹1 lakh + 90 days

A specialised law firm drafts the compounding application, negotiates with RBI's Penalty Committee. Strong likelihood of approval, but costs are high. Best outcome, but expensive.

🧭

Guided compounding (agent-assisted)

₹1.5–₹1.8 lakh final (40% of ₹4.2 lakh)

File Form A2s retroactively. Submit compounding application with reconciliation. RBI's Penalty Committee reviews good-faith disclosure. ~80% approval rate. 60–90 days to resolution.

Three pathways to FEMA OPGSP compliance: cost and timeline
"Ek din sodd, nanch din chakari — one day late, nine days of trouble."

— A Konkani proverb Aditya's father repeated whenever a bill went unpaid. Here, not literal bills, but regulatory filings.

🌱 What we hope happens

Aditya filed all six Form A2s retroactively within a week. The RBI's eAadhaar portal accepted them without error. He then drafted a compounding application—with the agent's help, using the regulatory language found in past RBI circulars on FEMA compounding—stating that the non-filing was due to lack of awareness of the OPGSP Form A2 requirement, that remedial action had been taken (all Form A2s now filed), and that he was requesting compounding of the penalty at 40% of ₹4.2 lakh, totalling approximately ₹1.68 lakh.

He submitted the application within thirty days of the original RBI notice. The RBI's Penalty Committee acknowledged receipt within ten days. By June 2026, a revised order came through the FEMA portal: the penalty had been compounded at 41% of the original amount. Final liability: ₹1.72 lakh.

Payment was made in two tranches—₹86,000 in June, ₹86,000 in July, both via the RBI's online portal. The agency returned to compliant status.

The conversation with Aditya did not end with the penalty settlement. He asked the agent, before closing: What about Prasad? The client in Bangalore who had sent the commission payments. Did Prasad have any filing obligation on their side?

The agent said: Yes, and probably also overdue. Any resident Indian sending foreign currency abroad must file an LRS (Liberalised Remittance Scheme) declaration if the remittance is routed through an OPGSP. In Prasad's case, if Prasad intended to send any of the Etsy proceeds back to Aditya, Prasad should have filed an LRS form with the RBI stating the purpose and recipient. Most small business owners do not. The RBI eventually notices, and issues a notice similar to the one Aditya received.

Aditya suggested the agent reach out to Prasad's business partner to give them a heads-up. The agent's response was quiet: the agent can read notices and map regulatory pathways. It cannot, and should not, contact third parties on Aditya's behalf. If Aditya wanted to raise the issue, that was his decision to make.

Aditya called Prasad that evening. Prasad cursed softly in Kannada for a moment, thanked him, and said he would get ahead of it. Prasad's own CA later confirmed he had also received a notice and was running the same compounding process. Aditya's early warning probably saved Prasad from missing the thirty-day compounding window.

What we hope happens is this: the FEMA OPGSP requirement becomes visible. It is, right now, visible only to those who have received a notice. But there are thousands of small e-commerce enablers, digital service providers, and consultants receiving foreign-source commissions via PayPal, Wise, and Stripe every single day, unaware that Form A2 filing within seven days is not optional. A quiet agent that reads the regulation and says—before the notice arrives, or as soon as the notice does arrive—"here is the sequence, here is the compounding pathway, here is what the RBI actually needs"—changes the story. It moves people from a panic-and-compliance arc to a preventative arc.

Aditya's office in Fontainhas is still there, facing the river, the blinds half-closed in the afternoon light. The tablet is on the desk. He has, since the FEMA reconciliation, used the agent twice more: once to check an ITR-3 question about foreign-source income schedules (he had, in fact, been filing correctly all along), and once to help a junior team member understand what GST compliance looked like for a service-delivery contract to a US client. The team is still five people. The project pace is still fast. But there is, now, something else: a reading practice. Before signing a client agreement, before invoicing, before receiving foreign currency, someone asks the agent: "What should we know about this?"

That question, asked early, prevents the notice from arriving with dread.

Notun-pan sodd korpachi ajun kai chhe. There is still time to do it correctly.