Status and error codes

processing of your pain 001 001 03 input file and pain 008 001 02 input file input files creates pain 002 001 03 xml output files containing status and error information we provide status at the following levels when processing the files received from a customer group header information shown once in the file that is common to all the transactions in that file batch a block of either one or more transactions transaction a block containing a single transaction group header the group header building block in the xml file will show the file level status in the grpsts tag as follows status meaning actc the file was validated and authenticated successfully rcvd the file has been received but is still being validated rjct the file was rejected if a file is rejected, additional information is shown in the stsrsninf tag the cd "narr" value indicates that there is a reason the file was rejected, with the reason description appearing in the addtlinf tag as shown in this example \<grpsts>rjct\</grpsts> \<stsrsninf> \<rsn> \<cd>narr\</cd> \</rsn> \<addtlinf>number of transactions in file does not match with control record expected 12, but calculated 13\</addtlinf> \</stsrsninf> here are some examples of reasons that can appear in the additional information the number of transactions in the file doesn't match the number in the control record the sum of all transactions in the file doesn't match the number in the control record the total in the file exceeds the limit for the customer in this case, you should contact the cr client integration team a validation error was found in the file batch level the batch building block shows batch status as follows status meaning actc the batch was validated and authenticated successfully rcvd the batch is being checked rjct the batch was rejected pndg one or more transactions in the batch is pending part the transaction batch was partially accepted and partially rejected this means that the batch includes one or more rejected transactions as well as one or more transactions that have been accepted in the output file generated, you’ll be able to see which transactions were rejected so you can make the necessary changes and resend to cr if a batch is rejected, additional information is shown in the stsrsninf tag the cd narr indicates the reason the file was rejected, with the description appearing in the addtlinf tag here are some examples of what might appear in this tag the number of transactions doesn't match the number in the control record the control sums don't correspond with the total calculated the requested execution date is later than the current date and time the creditor's account currency isn't in usd the debtor's account currency isn't in usd transaction level statuses at the transaction level can be one of the following status meaning acpt the transaction has been accepted by the external payment processor for processing rjct the transaction was rejected acsc the transaction has been completed and the settlement has been confirmed on the debtor's account acsp the transaction was accepted and has been moved on for processing pdng the transaction is pending and requires further processing if the transaction is rejected, additional information is shown in the stsrsninf tag the cd tag will show either as "narr" for narrative or "aret" for a return, with a reason description appearing in the addtlinf tag here are some examples of what might appear in this tag the customer isn't enabled for this rail in this case, you should contact the cr client integration team the account is not set up for this customer in this case, you should contact the cr client integration team in the case of a return, cancellation, or notice of change (noc), a reason code and trace number will be provided here in the case of a wire cancellation, a message will tell you to please contact your rm for more information on this canceled wire