2.2.5 NEFT ISO FCRA Processing

Describes the process of handling NEFT transactions using ISO messaging standards for Foreign Contribution Regulation Act (FCRA) compliant payments.

NEFT ISO FCRA Processing

Transactions are initiated from the PTDOTONL screen:

• The user is required to select Category Purpose Code asFCRA.
• The set of fields for capturing Donor Details are available under the Additional Details tab. For FCRA transactions, these fields are mandatory. If left blank, the system displays an errormessage.
• WhenDonor Details fields are enabled, the Sender to Receiver Information (Lines 1-6) and Indo-Nepal Information fields are disabled for input.
• Duringmessage generation, the system sets the Category Purpose Code to FCRA and maps the Donor Details to Tag RmtInf/Ustrd, Loop 1 to Loop 4, respectively.

FCRA remittance information is mapped as explained below:

Table 2-13 Field and Tag Mapping for RmtInf/Ustrd with and without Batch Time in Pacs.008 Messages

Field/Tag	Code to be Used	Tag - RmtInf/Ustrd with Batch Time	Tag - RmtInf/Ustrd without Batch Time
CtgyPurp / Cd (in Pacs.008 message)	FCRA	loop 1: Batch time	loop 1: Donor Address|Donor Address
CtgyPurp / Cd (in Pacs.008 message)	FCRA	loop 2: Donor Address|Donor Address	loop 2: Name of the Donor|Purpose ofremittance
CtgyPurp / Cd (in Pacs.008 message)	FCRA	loop 3: Name of the Donor|Purpose of remittance	loop 3: Country of the Donor|Currency and Amount
CtgyPurp / Cd (in Pacs.008 message)	FCRA	loop 4: Country of theDonor|Currency and Amount	loop 4

Initiation of Transactions from SPS Requests and C2B Uploads (pain.001 Files)

Transactions are initiated from SPS Request and C2B Upload (pain.001 file):

• Ifthe Category Purpose Code is FCRA, the system validates that RmtInf/Ustrd Lines 1 to 4 are not blank and that Donor Details are available.
• Thevalues received in RmtInf/Ustrd Lines 1 to 4 are mapped to the new Donor Details fields under the Additional Details tab in the PTDOTONL screen.
• Messagegeneration follows the same logic as described for transactions initiated from the PTDOTONL screen.

For each line of type VARCHAR2(140) with no delimiters, the system validates that exactly one pipe (|) delimiter is present in each line or loop.

Eachsegment in the line (i.e., text between delimiters) must be between 1 and 35 characters in length. This needs confirmation from the bank.

If data is missing on either side of the delimiter, the system populates 'NA' in the respective segment.