It was supposed to be a simple payment.
Arjun, an independent technology consultant based in India, had completed a six-month project for a client in Singapore. The contract was signed, the work was delivered, the invoice had been raised, and the client was ready to make the payment.
The amount was not unusual for his business.
Then the bank called.
The remittance had been placed on hold.
The reason? A mismatch in the purpose code attached to the transaction.
Arjun initially thought it would be resolved with a quick email. After all, the money was legitimate and the consulting service had actually been provided.
But the bank wanted supporting documents, clarification of the nature of the service, and confirmation that the transaction was correctly classified under India's foreign exchange framework.
That was when Arjun realised something many consultants and exporters discover only after facing a banking query:
In Cross-border transactions, getting paid is only one part of the process. Getting the transaction correctly classified and documented is equally important.
The Small Field That Created a Big Problem
For businesses receiving or making international payments, a purpose code may look like a routine banking field.
It isn't something most business owners spend much time thinking about.
But the purpose code helps banks and regulators understand the nature of a foreign exchange transaction.
Is the payment for software services?
Professional consultancy?
Advertising?
Investment?
Refund?
Each transaction needs to be represented accurately according to its underlying economic purpose.
Arjun's problem started because the code used for his incoming payment did not properly reflect the consulting services mentioned in his contract and invoice.
Nothing about the underlying transaction was fraudulent.
The classification was simply wrong.
And that was enough for the bank to pause the transaction and ask questions.
Why Banks Take Purpose Codes Seriously
When money crosses India's borders, banks are not merely processing a payment.
They are also operating within India's foreign exchange and reporting framework.
Banks therefore need to understand the nature of transactions passing through their systems.
A transaction with an unclear or inconsistent purpose can raise questions such as:
- What is the payment actually for?
- Who is the remitter or beneficiary?
- Is there a genuine underlying transaction?
- Does the invoice support the stated purpose?
- Are the contractual documents consistent with the payment?
- Is the transaction compliant with applicable FEMA requirements?
- Are additional regulatory or reporting requirements involved?
This is why a FEMA compliance review should not be treated as something relevant only to large multinational companies.
Freelancers, consultants, exporters, startups, agencies and Indian businesses working with overseas clients can also encounter these issues.
The Invoice Was Correct. The Banking Trail Wasn't.
When Arjun's bank asked for documents, he submitted the invoice.
Then the contract.
Then proof of delivery of the consulting services.
Everything supported the fact that the Singapore client owed him money.
But the bank's question was different:
Did the banking classification accurately describe the transaction?
That distinction is important.
A genuine commercial transaction can still create a compliance issue if the documentation, invoice, accounting treatment and banking classification do not tell the same story.
This is one of the most common weaknesses in cross-border financial management.
Businesses often focus on the commercial side first:
"The client has paid me."
But the compliance side asks:
"Why has the client paid you, under what arrangement, and can the transaction be properly demonstrated through the financial records?"
The Problem Was Eventually Corrected
Arjun worked with his bank to provide clarification and the relevant supporting documentation.
The purpose of the transaction was reviewed against the underlying agreement and invoice, and the banking records were corrected through the appropriate process.
The transfer was eventually released.
But the experience changed how he handled international payments.
He created a simple pre-payment checklist covering:
Contract → Invoice → Nature of Service → Correct Purpose Classification → Bank Documentation → Accounting Entry
It added only a few minutes to his process.
But it significantly reduced the possibility of another payment being unnecessarily delayed.
What Consultants and Exporters Should Learn From This
Arjun's experience highlights a broader issue in FEMA compliance for consultants and service exporters.
International payments should be treated as a complete documentation chain rather than an isolated banking transaction.
Before receiving or making a cross-border payment, businesses should ensure that the following are aligned:
1. Contract
The agreement should clearly describe the services, payment terms, parties and commercial relationship.
2. Invoice
The invoice should accurately reflect what was actually provided and the amount payable.
3. Purpose of Payment
The nature of the transaction should be correctly represented in the banking documentation and applicable purpose classification.
4. Supporting Documents
Depending on the transaction, the bank may require documents supporting the underlying commercial activity.
5. Accounting Records
The transaction should also be appropriately recorded in the business books.
When these five elements tell the same story, compliance becomes considerably easier.
One Mistake Can Become a Pattern
The bigger danger isn't always one incorrect purpose code.
The real problem can arise when businesses repeatedly use incorrect classifications without understanding why.
Imagine a consultant receiving twenty international payments during a financial year.
If the underlying services are consistently consultancy but the transactions are repeatedly classified incorrectly, the issue is no longer an isolated mistake.
It becomes a process problem.
And process problems are much harder to defend when a bank, auditor, regulator or tax authority later asks for an explanation.
This is why businesses involved in cross-border payments, foreign remittances and international trade should periodically review their transaction processes rather than waiting for a payment to get blocked.
FEMA Compliance Is About More Than Avoiding Penalties
FEMA is often viewed purely from the perspective of restrictions and penalties.
In practice, effective FEMA compliance is also about making international business transactions smoother.
A properly structured process can help businesses:
- Reduce payment delays
- Maintain clearer banking records
- Respond faster to bank queries
- Maintain proper supporting documentation
- Improve audit readiness
- Reduce the risk of inconsistent reporting
- Create a stronger record of legitimate cross-border transactions
For consultants and exporters, this becomes especially important because international receipts are often directly connected with business revenue.
A delayed payment can therefore affect not only compliance but also cash flow and business operations.
Shunyatax's View:
Don't Let a Banking Field Become a Business Problem
At Shunyatax Global, we believe that FEMA compliance should be built into the transaction process — not handled after the bank raises a query.
A purpose code may appear to be a small part of an international payment.
But when the purpose code, invoice, contract and actual transaction do not align, a routine payment can quickly turn into a documentation exercise.
For consultants, exporters, startups, NRIs and businesses receiving or sending international payments, the objective should be simple:
The transaction should tell one consistent story from contract to bank account to accounting records.
If you are facing a blocked international transfer, FEMA compliance query, purpose-code issue, foreign remittance problem or documentation mismatch, Shunyatax Global can help review the transaction and its supporting financial documentation.
📞 +91 9461514198