1. Bulk File Handling User Guide
  2. Bulk File Processing
  3. Status Reports
  4. Branch/Transaction Level Status Report (L2)

Branch/Transaction Level Status Report (L2)

Generation of batch level pain.002 status reports are done in the following cases:
  • All transactions in the batch are completed processing
  • All success (Case 1)
    • PaymentInformationStatus <PmtInfSts> is populated as ACSC - Settlement on the debtor's account has been completed
    • Reason code is not applicable
    • Transaction level details are not populated
  • All transaction are future valued (Case2)
    • PaymentInformationStatus <PmtInfSts> is populated as PEND - Settlement on the debtor's account has been completed.
    • Reason code is not applicable
    • Transaction level details is not populated
  • All cancelled or rejected (Case3)
    • PaymentInformationStatus <PmtInfSts> is populated as RJCT - Payment initiation or individual transaction included in the payment initiation has been rejected
    • PaymentInformationStatus <PmtInfSts> StatusReasonInformation <StsRsnInf> is populated for the batch
    • PaymentInformationStatus <PmtInfSts> StatusReasonInformation <StsRsnInf> is populated for the batch
  • Partly success, rest are rejected/cancelled/pending (Case4)
    • PaymentInformationStatus <PmtInfSts> is populated as PART- A number of transactions have been accepted, whereas another number of transactions have not yet achieved 'accepted' status
    • PaymentInformationStatus <PmtInfSts> StatusReasonInformation <StsRsnInf> is not populated for the batch
    • Number of transactions and transaction status is populated at payment information level
    • TransactionStatus <TxSts> & StatusReasonInformation <StsRsnInf> will be populated for rejected transactions. Reason code population is based on the error code mapping
  • For Case1, 2 & 3 listed above, transaction level details are not populated in pain.002. Batch level reason code is applicable for case 3.
  • A batch can be cancelled as a result of a cancellation request received or can be rejected manually from the exception queues due to the following validation failures:
    Batch Exception scenario Error code Status level
    Invalid debtor account (on cancellation from BO queue due to customer/account status validations) - Payment Information
    Duplicate Payment Information ID ((on cancellation from BO queue due to duplicate check) - Payment Information
    If cancelled from ECA queue - Payment Information
    FX queue cancellation   Payment Information
    Batch cancellation based on customer request   Payment Information
  • For case 4 transaction level details of the rejected/cancelled transaction and the reason code will be populated.
    Exception scenario Error code Status level
    Invalid debtor account (on cancellation from BO queue due to customer/account status validations) - Transaction Status
    Transaction Duplicate check - Transaction Status
    If cancelled from ECA queue - Transaction Status
    FX queue cancellation   Transaction Status
    transaction cancellation based on customer request   Transaction Status
  • If no linkage to reason code is found, no reason details are populated.

Parent topic: Status Reports