Why Your Remittance to India Got Rejected: Fixing CityRemit Docs

Sending money from Japan to India should be straightforward. You log in, enter the details, hit send, and expect the rupees to land in your family's account. But then the dreaded notification arrives: "Transaction Rejected" or "Action Required: Documentation Pending."

If you are using CityRemit, a popular choice for the Japan-to-India corridor, a rejection usually stems from Japan's strict Act on Prevention of Transfer of Criminal Proceeds (APTCP) and the Reserve Bank of India's (RBI) incoming remittance guidelines. The good news? 90% of these rejections are due to fixable documentation mismatches.

This guide breaks down exactly why CityRemit rejects transfers to India, the specific documents you need to prepare, and how to ensure your next JPY to INR transfer sails through compliance checks.

Understanding the "Why": Compliance in the Japan-India Corridor

Before diving into specific errors, it helps to understand the regulatory pressure. Japan’s Financial Services Agency (FSA) requires all registered funds transfer operators (like CityRemit, JpRemit, SmileRemit, and JapanRemit) to perform rigorous Know Your Customer (KYC) and transaction monitoring.

Simultaneously, the RBI mandates that inward remittances to India must declare a Purpose Code. If the sender's declared purpose in Japan doesn't match the receiver's purpose code in India—or if the sender's identity isn't verified to the required "Level 2" or "Level 3" standard—the transfer stops dead in its tracks.

CityRemit acts as the gatekeeper. Their compliance engine flags discrepancies automatically. It isn't personal; it's algorithmic.

Top 5 Reasons CityRemit Rejects Your India Remittance

Based on common user reports and compliance guidelines for the JPY-INR corridor, here are the primary culprits.

1. My Number Card vs. Residence Card Mismatch (The #1 Killer)

This is the single most common error for foreign residents in Japan.

• The Rule: For transfers exceeding 100,000 JPY (or sometimes lower thresholds depending on the provider's internal risk policy), you must have completed Identity Verification Level 2 or 3.
• The Error: You registered with your Residence Card (Zairyu Card) initially, but your My Number Card (Individual Number Card) has a different address, name spelling (Romaji vs. Kanji), or expiration date.
• The Fix: Ensure your CityRemit profile matches your My Number Card exactly. If you updated your address at the ward office but not on your My Number portal, the verification API will fail. Update CityRemit after the ward office confirms the change.

2. Incorrect or Missing RBI Purpose Code

Every rupee entering India needs a "Purpose Code" (e.g., S1301 for Family Maintenance, S0021 for Software Consultancy).

• The Error: Selecting "Family Maintenance" (S1301) but the receiver is a business account, or selecting "Gift" (S1302) for a recurring monthly salary transfer.
• The Fix: Ask your beneficiary in India which code their bank expects. CityRemit usually maps your selection (e.g., "Living Expenses") to the code, but if you choose "Other," you must input the specific code manually. Mismatches trigger an automatic rejection by the Indian correspondent bank (often SBI, HDFC, or Axis).

3. Beneficiary Name Mismatch (Kanji/Romaji vs. Bank Passbook)

Japanese systems use Romaji/Kanji; Indian banks use English/Latin script strictly as printed on the passbook.

• The Error: You enter "SHARMA RAJESH KUMAR" (Western order) but the Indian passbook reads "RAJESH KUMAR SHARMA" (Indian order). Or you omit the middle name.
• The Fix: Copy the name exactly as it appears on the beneficiary's Indian bank passbook or cancelled cheque. Do not translate. Do not reorder. If the passbook says "R K SHARMA," enter "R K SHARMA."

4. IFSC Code / Branch Address Errors

• The Error: Using an outdated IFSC code (common after bank mergers, e.g., Syndicate Bank -> Canara Bank, Allahabad Bank -> Indian Bank) or entering the wrong branch address.
• The Fix: Verify the IFSC on the RBI website or the beneficiary's current cheque leaf right before initiating the transfer. CityRemit validates the IFSC format, but not always the "active" status of merged branches.

5. Source of Funds (SOF) Documentation Gaps

For high-value transfers (typically > 1,000,000 JPY or cumulative high volume), CityRemit's compliance team will manually request Proof of Income.

• The Error: Submitting a Salary Slip (Kyuyo Meisai) that doesn't match the declared annual income on your Tax Certificate (Kazei Shomeisho) or Withholding Tax Slip (Gensen Choshu Hyo).
• The Fix: Prepare a "Source of Funds Pack" before you send:
  1. Latest Gensen Choshu Hyo (Dec/Jan) or Kazei Shomeisho (June onwards).
  2. Last 3 months Salary Slips.
  3. Bank statement showing salary deposit matching the slips.
     Upload these proactively via the CityRemit app "Document Upload" section to avoid the "Pending Review" limbo.

Step-by-Step: Fixing a Rejected Transfer in the CityRemit App

If your transfer is currently "On Hold" or "Rejected," follow this workflow immediately.

Step 1: Check the "Notification" or "History" Tab

Don't just look at the status. Tap the specific transaction. CityRemit usually provides a Rejection Code or a specific message (e.g., "Beneficiary Name Mismatch," "Sender Verification Expired").

Step 2: Resolve Sender Verification (If Prompted)

• Go to Menu > My Page > Identity Verification Status.
• If it says "Level 1" or "Expired," tap Upgrade Verification.
• Pro Tip: Use the My Number Card + PIN (Signature/Utilization) method via the app's eKYC camera. It is instant. Uploading photos of Residence Card + My Number notification card (paper) takes 1-2 business days for manual review.

Step 3: Correct Beneficiary Details

• Go to Beneficiary List.
• Do not edit the existing entry. Delete it and Add New Beneficiary.
• Why? Editing often retains the old "verified" hash in the backend, causing the same error. A fresh entry forces a clean validation against the IFSC directory.
• Enter details exactly from the cancelled cheque/passbook photo sent by your family.

Step 4: Re-initiate with Correct Purpose Code

• Start a new transfer.
• Select the exact Purpose Category matching the code.
  • Family Maintenance / Living Expenses -> S1301 (Most common for NRIs/foreign workers).
  • Gift / Donation -> S1302 (Tax implications differ in India; use carefully).
  • Investment (NRE/FCNR) -> S0001 / S0002 (Requires beneficiary NRE account).

Step 5: Upload SOF Docs Before Support Asks

If sending > 500,000 JPY (or your personal limit), go to Menu > Document Upload immediately after creating the transfer order. Upload your Gensen Choshu Hyo. This moves you to the front of the manual review queue.

CityRemit vs. The Field: How Documentation Handling Differs

Understanding how CityRemit handles docs vs. competitors helps you choose the right tool for your specific situation.

Provider	Verification Method	Doc Upload UX	Typical Rejection Speed	Best For
CityRemit	App eKYC (My Number Card) + Manual Review	Dedicated "Document Upload" section in Menu	Fast (Auto-reject) / Slow (Manual SOF review)	Regular salary remittances; Users with My Number Card
Wise	App eKYC / Video Call	Automatic prompt during transfer flow	Very Fast (Real-time checks)	Speed & Transparency; First-time users
SmileRemit	App eKYC / Postcard	Email/Link based upload	Medium	High volume; Corporate/Business remittances
JpRemit	Postcard / App	Email/FAX heavy	Slow (Legacy workflows)	Users without smartphones/My Number Card
BrastelRemit	Postcard / App	App Upload	Medium	Filipino community focus; Cash pickup options
JapanRemit	App / Postcard	App Upload	Medium	Nepal/India focus; Competitive rates
KyodaiRemit	App / Postcard	App Upload	Medium	Community-based; Specific corridors

Key Takeaway: CityRemit is excellent if you have a My Number Card and keep your SOF docs ready. If you lack a My Number Card or hate manual uploads, Wise or SmileRemit often offer smoother automated verification flows.

Pro Tips to Never Get Rejected Again

1. The "Pre-Flight Checklist" (Save this screenshot)

Before hitting "Confirm Send