Normal Queue definition

Normal Queue means a queue of Direct Debit Instructions already input by or generated by CB and/or the queue mode specified by a Member or CB for an applicable payment instruction in relation to which such payment instruction (subject to Rule 6.3.1.5, Rule 6.3.3.5, Rule 6.3.4.3, Rule 6.3.9.5, Rule 6.3.13.5 and Rule 6.3.14.3(f)) or Direct Debit Instruction will be settled immediately if the available balance of the Member in its CHATS Ledger Account is sufficient to meet the payment instruction or Direct Debit Instruction where the payment instruction or Direct Debit Instruction is first in priority in the queue. Save in respect of OTC Clear Payment Instructions (whereby initial queue mode is determined according to the criteria stipulated in the Operating Procedures), the Clearing House Computer will treat the payment instruction as Normal Queue if the queue mode is not specified in an applicable payment instruction.
Sample 1Sample 2Sample 3
Normal Queue means a queue of Direct Debit Instructions already input by or generated by MA and/or the queue mode specified by a Member for an applicable payment instruction in relation to which such payment instruction (subject to Rule 6.3.1.5, Rule 6.3.3.5, Rule 6.3.4.3, Rule 6.3.8.5, Rule 6.3.10.5, Rule 6.3.14.6, Rule
Sample 1

Examples of Normal Queue in a sentence

  • When RTGS Liquidity Optimiser process starts, eligible CHATS Transactions in the Normal Queue as specified in the Operating Procedures will be extracted (“Selected Payments”).

  • CHATS Transactions (other than CHATS Transactions in respect of Articles) received by Clearing House Computer after commencement of the RTGS Liquidity Optimiser process will not be processed as part of that process and will be placed at the end of the Normal Queue and processed in due course in accordance with these Rules Provided that Direct Debit Instructions will be placed at the top of the Normal Queue.

  • If following an emergency HKSCC requires to roll back the data for system recovery all CCASS Payment Instructions in the Normal Queue and the Pending Queue will be cancelled in accordance with the Operating Procedures.

  • However, a paying Member can only cancel its OTC Clear Payment Instructions Value Today in the Normal Queue and the Pending Queue up to the CHATS Customer Cut-off time.

  • After the CHATS Value Date Cut-off and the completion of the processing of the CHATS Payment Instructions input prior to the CHATS Bank Cut-off or OTC Clear Payment Instructions generated prior to the CHATS Bank Cut-off, CHATS Payment Instructions Value Today or OTC Clear Payment Instructions Value Today in the Normal Queue will be cancelled automatically.

  • In this event, the GTRS Payment Instruction will be re-designated “Pending for Hold Funds” and will again be put in the Normal Queue at the next GTRS Window Open, until the last GTRS Preliminary Window Close of that Working Day.

  • However, a Member can only cancel its CHATS Payment Instructions Value Today in the Normal Queue and the Pending Queue up to the CHATS Customer Cut-off time.

  • On termination of the process of RTGS Liquidity Optimiser pursuant to Rule 6.12.6, all relevant Selected Payments and any CHATS Transactions (other than CHATS Transactions in respect of Articles) received by Clearing House Computer after commencement of the process of RTGS Liquidity Optimiser will be reinstated in the Normal Queue as if the process of the RTGS Liquidity Optimiser had not been commenced.

  • A paying Member shall be entitled to re-sequence the Normal Queue of its OTC Clear Payment Instructions Value Today at any time prior to the CHATS Value Date Cut-off or to transfer OTC Clear Payment Instructions Value Today from the Normal Queue to the Pending Queue or vice versa before the specified time as stipulated in the Operating Procedures.

  • Requests for re-sequencing and cancellation of its payments in the Normal Queue (including the Selected Payments and other CHATS Transactions (other than CHATS Transactions in respect of Articles)) initiated by the Selected Payment Member or MA after the start of RTGS Liquidity Optimiser process and before completion or termination of the process will be rejected.

Related to Normal Queue

  • Delivery Term has the meaning set forth in Section 1.1(b).

  • Delivery Year means the Planning Period for which a Capacity Resource is committed pursuant to the auction procedures specified in Tariff, Attachment DD, or pursuant to an FRR Capacity Plan under Reliability Assurance Agreement, Schedule 8.1.

  • Schedule of quantities means the schedule of quantities as specified and forming part of this contract.

  • Delivery Period means that period agreed in writing between the Parties in relation to Delivery of the Product or parts thereof by the Contractor, any delay in which shall be deemed a breach of this Agreement and entitle JOBURG MARKET to exercise its remedies in terms of this Agreement or at law.

  • The Schedule of Quantities means the schedule of quantities as specified and forming part of this contract.

  • Registrant Fax Ext 4321 Registrant Email: XXXXX@XXXXXXX.XXX Admin ID: 5372809-ERL Admin Name: EXAMPLE REGISTRANT ADMINISTRATIVE Admin Organization: EXAMPLE REGISTRANT ORGANIZATION Admin Street: 000 XXXXXXX XXXXXX Xxxxx Xxxx: ANYTOWN Admin State/Province: AP Admin Postal Code: A1A1A1 Admin Country: EX Admin Phone: +1.0000000000 Admin Phone Ext: 1234 Admin Fax: +1.5555551213 Admin Fax Ext: Admin Email: XXXXX@XXXXXXX.XXX Tech ID: 5372811-ERL Tech Name: EXAMPLE REGISTRAR TECHNICAL Tech Organization: EXAMPLE REGISTRAR LLC Tech Street: 000 XXXXXXX XXXXXX Xxxx Xxxx: ANYTOWN Tech State/Province: AP Tech Postal Code: A1A1A1 Tech Country: EX Tech Phone: +1.1235551234 Tech Phone Ext: 1234 Tech Fax: +1.5555551213 Tech Fax Ext: 93 Tech Email: XXXXX@XXXXXXX.XXX Name Server: NS01.EXAMPLEREGISTRAR.TLD Name Server: NS02.EXAMPLEREGISTRAR.TLD DNSSEC: signedDelegation DNSSEC: unsigned >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<< Registrar Data: Query format: whois “registrar Example Registrar, Inc.” Response format: Registrar Name: Example Registrar, Inc. Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxx@xxxxxxx.xxx WHOIS Server: whois.example-registrar.tld Referral URL: xxxx://xxx.xxxxxxx-xxxxxxxxx.xxx Admin Contact: Xxx Registrar Phone Number: +1.3105551213 Fax Number: +1.3105551213 Email: xxxxxxxxxxxx@xxxxxxx-xxxxxxxxx.xxx Admin Contact: Xxxx Registrar Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: xxxxxxxxxxxxx@xxxxxxx-xxxxxxxxx.xxx Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216 Email: xxxxxxxx@xxxxxxx-xxxxxxxxx.xxx >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<< Nameserver Data: Query format: whois “NS1.EXAMPLE.TLD”, whois “nameserver (nameserver name)”, or whois “nameserver (IP Address)” Response format: Server Name: NS1.EXAMPLE.TLD IP Address: 192.0.2.123 IP Address: 2001:0DB8::1 Registrar: Example Registrar, Inc. WHOIS Server: whois.example-registrar.tld Referral URL: xxxx://xxx.xxxxxxx-xxxxxxxxx.xxx >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<< The format of the following data fields: domain status, individual and organizational names, xxxxxxx, xxxxxx, xxxx, xxxxx/xxxxxxxx, postal code, country, telephone and fax numbers (the extension will be provided as a separate field as shown above), email addresses, date and times should conform to the mappings specified in EPP RFCs 5730-5734 so that the display of this information (or values return in WHOIS responses) can be uniformly processed and understood. In order to be compatible with ICANN’s common interface for WHOIS (InterNIC), WHOIS output shall be in the format outline above.