3.7 Inbound Collections Transaction Input

Collections Incoming transactions can be created based on the upload of incoming DNF file received from Clearing Network or using Collections Incoming Transaction screen.

The UI screen is used to capture the details of incoming DD request received from creditor bank, if STP processing fails during Incoming transaction creation.

  1. On Homepage, specify PCDAITXN in the text box, and click next arrow.
    Inbound Collections Transaction Input screen is displayed.

    Figure 3-20 Inbound Collections Transaction Input

    Screen
  2. On Inbound Collections Transaction Input screen, specify the fields.
    For more information about the fields, refer to field description below:

    Table 3-13 Inbound Collections Transaction Input - Field Description

    Field Description
    Transaction Branch System displays the branch from which the user is logged in.
    Transaction Reference Number System displays a unique identifier of the Collections transaction and it is auto-generated. For more details on the format, refer the Payments Core User Guide.
    Source Reference Number This field is defaulted as Transaction Reference Number.
    User Reference Number This field defaults the User Reference Number field and you can modify the referenced required.
    Network Code Specify the Network Code from the list of values.
    Source Code This is defaulted to ‘MANL’ and it is non-editable for manually initiated transactions. For transactions created via upload, source would be SEPA & it is mandatory to maintain Source network preference for SEPA source.
    Host Code Specify the Host Code from the list of values.
    File Reference Number Specify the File Reference Number.

Parent topic: Collections Transactions