Reject. The grievance fails in one or more respects to meet the contractual requirements for filing. The reason for the rejection will be stated in the response rejecting the grievance.
Reject. The grievance fails in one or more respects to meet the definitions in this Section or the requirements for filing as stipulated in Section F of this Article.
Reject. Bank may reject the Payment Message if: (i) The Account identified in the Payment Message is: (ii) Closed, invalid, or being monitored for fraudulent or other illegal activity, or (iii) Is not a “transaction account” as defined in the Federal Reserve Board’s Regulation D 12 C.F.R. Part 204;
Reject. (i) We may reject the Payment Message if:
Reject. A Reject occurs when a credit transfer is not accepted for normal execution before Interbank Settlement i.e. settlement between the Originator Bank and the Beneficiary Bank. Return: A Return occurs when a credit transfer is diverted from normal execution after Interbank Settlement. Interbank Settlement: Settlement of accounts between Originator Bank and Beneficiary Bank through the Use of Clearing and Settlement Mechanisms or Intermediaries as same is defined in the SEPA Credit Transfer Scheme Rulebook.
Reject. A ‘Reject’ occurs when an ICT Inst Transaction is not accepted for normal execution under the Scheme. If the rejection is at the point at which the Originator instructs the Originator PSP i.e. being an ICT Inst Instruction, for the purposes of the Scheme, the Originator PSP need only inform the Originator of the reason. If it occurs in the Inter-PSP Space the Reject must be instant and sent as specified in DS-03 in section 4.5. • The main characteristics of a Reject (DS-03) are: • the amount will be the Original Amount of the ICT Inst Transaction; • the Reject message is routed through the same path taken by the original ICT Inst Transaction with no alteration of the data contained in the initial ICT Inst Transaction; • a record of the relevant data relating to the initial ICT Inst Transaction, sufficient to provide an audit trail, is included; • the initial ICT Inst Transaction is identified by the original reference of the Originator PSP; • Reject messages contain a reason code (attribute AT-R004). Reject messages should be transmitted within the maximum execution time defined in section 4.2.3. The document ‘Guidance on reason codes for ICT Instant Credit Transfer R-transactions’ ([15]) prescribes which ISO codes should be used for initiating a Reject. The step-by-step process flow for Rejects is as follows: CT-01.02R The Originator PSP must inform Immediately the Originator and make the appropriate details available to the Originator. CT-01.05R The concerned party in the Inter-PSP Space must send the Reject message being a negative confirmation message, to the Originator PSP within the maximum execution time defined in section 4.2.3. The Originator PSP must inform the Originator Immediately that its ICT Inst Instruction has been rejected. The Originator PSP Immediately cancels the Reservation of the Amount on the Originator’s Payment Account and makes the appropriate details available to the Originator based on the information received in the dataset DS-03. CT-01.06R The Beneficiary PSP must send the Reject message being a negative confirmation message, to the Originator PSP within the maximum execution time defined in section 4.2.3. The Originator PSP must inform the Originator Immediately that its ICT Inst Instruction has been rejected. The Originator PSP cancels the Reservation of the Amount on the Originator’s Payment Account and makes the appropriate details available to the Originator based on the information received in the dataset DS-03.
Reject. Checks may be rejected for the following reasons: missing proper endorsement, unable to clearly read image, missing information, any reason listed under “Excluded Items” in this Agreement or any other reason to doubt collectability. Further, we reserve the right to reject any item transmitted through MDC, at our discretion, without any liability to you. If a check is rejected, Xxxxxxxx CU will attempt to contact the account holder as soon as possible. Contact method may include, but are not limited to: email, telephone call, SMS message, Home Banking Secure Message and USPS mail.
Reject. In respect of each Party Category that was eligible to vote, the sum of the Weighted Votes of the Groups in that Party Category which voted to accept the implementation date was less than 50% in all Categories. PART ONE / PART TWO Part One – Authority Determination Required DCP 195 Alternative WEIGHTED VOTING DNO IDNO SUPPLIER DISTRIBUTED GENERATOR GAS SUPPLIER CHANGE SOLUTION Accept Reject Accept n/a n/a IMPLEMENTATION DATE Accept Reject Accept n/a n/a
Reject. In respect of each Party Category that was eligible to vote, the sum of the Weighted Votes of the Groups in that Party Category which voted to accept the implementation date was less than 50% in all Categories. PART ONE / PART TWO Part One – Authority Determination Required PARTY DCP 195 SOLUTION DCP 195 IMPLEMENTATION DATE DCP 195 ALTERNATIVE SOLUTION DCP 195 ALTERNATIVE IMPLEMENTATION DATE WHICH DCUSA OBJECTIVE(S) IS BETTER FACILITATED? COMMENTS DNO PARTIES Electricity North West Ltd Accept Accept Accept (with preference) Accept We support the working group’s view that both change proposals better facilitate objectives 1, 2 and 3 for the reasons stated in the Change Report. We favour DCP195A because it better facilitates objective 1 more than DCP 195 as it delivers a more efficient notification process of when an appointment has been made with the Customer. It also provides for a better service to Customers whereby Suppliers can utilise the information to keep their Customers updated with progress regarding the Smart Meter installation. It also supports Suppliers in meeting their SMICOP obligations. Northern Powergrid - Northern Electric Distribution Ltd Accept Accept - Staged implementation: - with supplier roll-out plans due 6 months after date of approval by Ofgem ,and SLAs for defect Accept (with preference) Accept Objective 1 -The development, maintenance and operation by each of the DNO Parties and IDNO Parties of an efficient, co- ordinated, and economical Distribution Northern Powergrid can see the merit in changing the MRA in advance of the vote on this change in order to lay the foundations for its potential approval. We also note that CP3422, Notification of Agreed or Cancelled Appointment resolutions coming in 12 months after supplier roll out plans becoming available System. For both - Network issues are reported to DNO’s and rectified within the timescales Objective 2 The facilitation of effective competition in the generation and supply of electricity and (so far as is consistent with that) the promotion of such competition in the sale, distribution and purchase of electricity. For both – will help suppliers and DNO’s meet their customers’ expectations Objective 3 The efficient discharge by each of the DNO Parties and IDNO Parties of the obligations imposed upon them by their Distribution Licences. with Xxxxxxxx, was heard at the MDB on 26 June 2014 and the decision to reject it was overturned. However, until such time as this change is ag...
Reject. Select “Reject”. A comment field now opens in which a reason for the rejection must be entered (mandatory field). After entering the comment click “Submit”. The workflow of the person submitting the request is canceled and a PDF document is created with the details of the request and the reason.
