1. EU SEPA Credit Transfer User Guide
  2. Domestic Low Value Payments
  3. ACH Outbound Transactions
  4. Outbound SEPA CT Transaction Input

Outbound SEPA CT Transaction Input

User can perform ACH Outbound transaction. All transactions that are entered using this screen has payment type as ‘ACH” and transaction type as ‘Outbound’.

You can initiate a Fee or Interest Compensation Payment. When launched from the Response to Outbound SEPA CT Inquiry (PADOQRSP) screen, a pre-filled screen displays and input is restricted to only a few fields.

  1. On Homepage, specify PADOTONL in the text box, and click next arrow.
    Outbound SEPA CT Transaction Input screen is displayed.

    Figure 2-1 Outbound SEPA CT Transaction Input

    Description of Figure 2-1 follows
    Description of "Figure 2-1 Outbound SEPA CT Transaction Input"
  2. Click New button on the Application toolbar.
  3. On Outbound SEPA CT Transaction Input screen, specify the fields.

    For more information on fields, refer to the field description below:

    Table 2-1 Outbound SEPA CT Transaction Input - Field Description

    Field Description
    Transaction Branch code System defaults the transaction branch code with the user’s logged in branch code.
    Branch Name System defaults the Branch Name of the transaction branch code.
    Host Code System displays the Host Code of selected branch of the logged in user on clicking ‘New’ button.
    Host Code Description System defaults the Description of the Host Code.
    Source Code For manual transactions source code is defaulted as MANL. This denotes that the it is a manually input transaction.
    Source Code Description System defaults the description on selecting the Source Code.
    Network Code System displays the network code if only one Network is maintained with payment type as ACH for the host code. If more than one networks are present, you can select the network code from the available list of value.
    Network Code Description System defaults the description on selecting the Network Code.
    Transaction Reference number System generates the transaction reference number. For more details on the format, refer the Payments Core User Guide.
    User Reference Number System defaults transaction reference number. However you can modify this.
    Source Reference Number Specify the Source Reference Number.
    Prefunded Payments On checking ‘Prefunded Payments’, Debit Account Number gets defaulted, when the Prefunded GL is defined for that Source and Network
    • It is not mandatory to have a debit account /customer for the transaction if Pre funded Payments flag is checked, if the ‘Prefunded Payment GL’ maintained in Source Maintenance (PMDSORCE).
    • If debit account is not available, check ‘Prefunded Payments flag and click on ‘Enrich’ and ‘Save’ button to populate debit account details.
    • System will post the entries as per the GL’s maintained
    End to End ID Specify the End to End ID.

    Note:

    • There is a facility to process an outbound transaction with activation date and instruction date received in the request. It is possible to update the dates later from Network cutoff Queue /Future Value Queue considering the funds availability etc.
    • If the transaction is moved to Network cut off queue, it is possible to provide Activation Date and Instruction date while performing Carry Forward action. For Force release action, Instruction Date should be provided.
    • The’ Value Date change’ action from Future Valued Queue will allow providing a new Activation date & Instruction date.

Parent topic: ACH Outbound Transactions