P0612 Purpose Code: Invoking of standardised guarantees

Purpose code P0612 is used when money is received in India because a standardised guarantee has been called and the guarantor has paid out.

What is the P0612 purpose code?

Purpose code P0612 covers money arriving in India when a standardised guarantee is invoked, meaning the guaranteed event has occurred and the guarantor is making good. It is the payout half of a pair: fees charged for providing the cover report under P0609, and money paid when the cover is called reports here. That relationship is the same one the insurance codes use, where premium and claim settlement take separate codes, and it is why standardised guarantees sit in this group rather than with the capital account codes. One-off guarantees negotiated individually work differently and report as capital transfers instead. Under RBI FEMA guidelines, this inward payment is classified under Insurance and Pension Services and reported accordingly.

When to use P0612 purpose code?

Use P0612 when a standardised guarantee is called and the payment reaches you in India. It is the correct RBI receipt code for the invoking rather than for the fee that was charged to provide the cover. Two things have to hold: the guarantee is a standardised one rather than a one-off negotiated arrangement, and the money is the payout rather than any fee. Where the classification of the guarantee is unclear, settle it with your bank before declaring.

When to use a different code:

• Use P0609 when the money is the fee for providing standardised guarantee cover rather than a payout
• Use P0607 when the money is an insurance claim settlement rather than a guarantee being invoked
• Use the matching S-code when you are paying a foreign vendor rather than receiving money

Who typically uses P0612 purpose code

Indian beneficiaries of standardised guarantees receiving payment when the cover is called, including exporters and lenders protected by export credit arrangements. The recipient is whoever the guarantee was written in favour of, since the code is declared on the money arriving here.

Examples of transactions covered under P0612 purpose code

• Payment received when a standardised export credit guarantee is called following a buyer default
• Settlement paid by an overseas guarantor on invoking of guarantee cover
• Money received in India where a guaranteed obligation has not been met and the guarantor makes good
• Payout on a guarantee issued under a standardised scheme rather than negotiated individually

When NOT to use P0612 purpose code

• The money is the fee charged for providing the guarantee rather than a payout on it (use P0609)
• The money is an insurance claim settlement rather than a guarantee being called (use P0607 or P0608 depending on the policy)
• The guarantee was a one-off negotiated arrangement rather than a standardised one, which is a capital transfer under P0028 or P0029
• You are paying a foreign vendor rather than receiving (use the matching S-code)

Documents required for P0612 purpose code

To receive a payment under P0612, keep the following documents ready so your bank or platform can verify the transaction and report it correctly under FEMA.

How is a P0612 Purpose Code declared?

Declaring the code is pretty straightforward. Here's how the payment gets tagged and reported.

1. Invoke the guarantee: Notify the guarantor that the guaranteed event has occurred and submit your claim under the scheme.
2. Agree the settlement: The guarantor confirms the amount payable and issues its advice.
3. Receive the payment: The money is remitted to your Indian bank account.
4. Declare the purpose: State the purpose of the inward remittance, on your bank's form or through your platform.
5. Get your FIRA: Once processed, your FIRA is issued as proof and the payment is reported under FEMA.
6. With a traditional bank you handle each step of your payment journey. But with a platform built for cross-border payments, you can preselect a default purpose code so that the payments land smooth.

Common mistakes to avoid while using P0612 purpose code

A few common slips can hold up your payment or cause compliance issues. Here's what to watch for.

1. Confusing the payout with the fee: Using P0612 for guarantee fees charged, when this code covers money paid out on invoking and the fee belongs under P0609.
2. Treating a one-off guarantee as standardised: Applying P0612 to a payout on an individually negotiated guarantee, which is a capital transfer under P0028 or P0029 rather than an insurance-group receipt.
3. Code and document mismatch: The code not matching what your guarantee documentation describes, which flags the payment.
4. Incomplete documents: Missing the notice of invocation or settlement advice, so the bank cannot establish that the guarantee was actually called and holds funds until provided.
5. Missing PAN or KYC: Incomplete verification stops the bank from releasing the payment.
6. Using an inward code for an outward payment: Applying a receipt code to money you're sending out instead of the matching outward code.

How Skydo simplifies inward remittance under P0612 Purpose Code

With a bank, you declare the purpose code on your own for every single payment. With Skydo, you can preselect your code once and every payment gets tagged automatically.

1. Preselect the code once: Set P0612 as your default and Skydo tags every incoming payment for you, so there's no form to fill on each one.
2. No repeat declarations: A bank makes you restate the purpose for every remittance. Skydo does it in the background, the same way each time.
3. Instant, free FIRA: Your remittance proof is generated and stored on every payment, ready for your CA, GST, and audits, with no request and no fee.
4. Zero FX markup: You get the live mid-market rate with a flat, visible fee, instead of a markup hidden inside the bank's rate.
5. Settled in 24 hours: Your payment reaches your Indian bank within a day, fully reported and compliant.