Purpose Code S0212 - Booking of passages abroad (airline companies)

The S0212 purpose code is for paying a foreign airline directly for air tickets for international travel. Check who uses it, how it differs from business travel codes, and the tax points for this outward remittance.

The S0212 purpose code is used when someone in India pays a foreign airline for air tickets. The RBI description is "booking of passages abroad – airlines companies". A "passage" here is simply a seat on a flight. Most tickets are bought by card or through Indian agents in rupees, so no remittance is needed. S0212 is for cases where you send money abroad to the airline: a company paying a corporate invoice, a travel agent settling a group booking, or a person paying for a flight that starts outside India. It is a current account transaction. For individuals it counts toward the Liberalised Remittance Scheme (LRS) limit of USD 250,000 a financial year. The code covers the airfare only, not hotels or daily travel costs.

This Purpose Code should be used only where the transaction fits its defined regulatory scope. Here's when you should and shouldn't use this code:

You should use this code when:

• Corporate airline invoices - A company settles a monthly bill from a foreign airline for staff tickets.
• Group bookings - A travel agent pays a deposit for a block of seats for a conference group.
• Flights starting abroad - Tickets for an employee's onward flights between two foreign cities.
• Ticket changes - Fare differences and reissue fees billed by the airline abroad.
• Student or family tickets - An individual pays a foreign airline directly for a relative's flight.

Do not use this code when:

• You pay for travel by sea (use S0206 instead).
• You send an employee's hotel, meals and local travel money for a work trip (use S0301 instead).
• You buy a holiday package that includes flights and hotels (use S0306 instead).
• A foreign airline in India sends its fare surplus home (use S0207 instead).

RBI purpose codes are mandatory under FEMA to classify the nature of cross-border transactions entering or leaving India. They allow banks and regulators to accurately track foreign exchange flows and apply the correct regulatory, tax, and reporting treatment.

For individuals, businesses and institutions, correct purpose code usage:

• Ensures transactions are classified correctly under FEMA.
• Enables accurate reporting to the RBI and other regulators.
• Reduces delays caused by compliance checks or misclassification.
• Supports clean audit trails and tax reconciliation.

Bottom-line:

Using the correct purpose code helps ensure smooth processing, regulatory compliance, and faster credit of funds.

1. Select "S0212 – Booking of passages abroad (airline companies)" on Form A2 or your bank's outward remittance screen.
2. Upload the airline invoice, e-tickets or booking confirmation.
3. Individuals sign the LRS declaration; this code is on the list of payments that usually need no Form 145/146 (earlier Form 15CA/15CB).
4. The bank collects TCS where it applies and sends the payment to the airline.

Additional Notes:

• For individuals, TCS is nil up to Rs 10 lakh in a financial year across all LRS remittances, and 20% on the amount above that.
• Make sure the booking reference and passenger names on the invoice match the remittance details.
• Refunds for cancelled tickets come back as inward remittances. Keep the original S0212 record to match them.

• Using a generic or incorrect purpose code instead of the exact RBI-prescribed purpose code can lead to misclassification of the transaction under FEMA and trigger additional compliance checks by the bank.
• Mismatch between purpose code, invoice, and remittance narration may place the transaction on hold until clarification is provided.
• Submitting unclear or incomplete supporting documents that do not clearly describe the nature of the transaction often result in delays, as banks rely on documentation to validate FEMA compliance.
• Missing mandatory PAN or incomplete KYC documentation can prevent banks from releasing funds until verification is completed.
• Using service-related purpose codes for non-service transactions like capital receipts, investments, gifts, or refunds can result in incorrect regulatory treatment and potential reporting issues.
• Assuming small or recurring transactions do not require accuracy and repeated misclassification can attract regulatory scrutiny over time.

Cross-border payments require accurate purpose code selection and complete compliance documentation. Xflow helps businesses and individuals receive international payments while staying aligned with RBI and FEMA requirements.

With Xflow, you can:

• Select the correct purpose code with clarity
• Organize and maintain supporting documents
• Reduce compliance back-and-forth with banks
• Support FEMA compliant inward remittances