Response Transaction Format Sample Clauses

Response Transaction Format. In the event that a record level exception is discovered, then the whole transaction is rejected.
AutoNDA by SimpleDocs
Response Transaction Format. When the recipient of a file rejects it as a whole, the response file that is sent to the originator follows the naming convention determined by the Transfer Mechanism Service Provider. Information on the rejected file is referenced in the response transaction, with a record identifier of XXXXX and associated reason(s).
Response Transaction Format. At the transaction level an acceptance or rejection response will be provided for each transaction received. A rejection will be sent in the event that a transaction, record or data error is discovered within the transaction, making it unusable.
Response Transaction Format. The MAM will indicate the reason for a cancellation or re-plan of the job in the response, including if it was due to an incorrect Meter Point address.
Response Transaction Format. In the event that a Data Item level exception is discovered, then the whole transaction is rejected. 104 e.g. where a Supplier has a contract that the MAM arranges a visit at a suitable time for the consumer but also on a date/time which is cost effective for the MAM, and the Supplier does not wish/have direct access to the MAM’s scheduling system.

Related to Response Transaction Format

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • Required Acceptance of Daily Load Deliveries and Notification If the State is harmed by purchaser’s refusal to accept up to 10 truck deliveries of any one sort per day, Purchaser will be in breach of contract and subject to damages as per the D-026.2 and D-027.2 clauses. A truck delivery is all the wood delivered including sorts on super trucks, mule trains and pups brought to the delivery point by a single truck. The Purchaser shall notify the Contract Administrator at least 48 hours in advance if: 1. Purchaser intends to limit the number of truck deliveries accepted on any day to less than that listed above, or 2. Purchaser intends to limit the number of truck deliveries accepted on any day to the number listed above.

  • Processing Transactions 2 2.1 Timely Pricing and Orders.................................... 2 2.2

  • Transaction Processing All orders are subject to acceptance by us and by the Fund or its transfer agent, and become effective only upon confirmation by us. If required by law, each transaction shall be confirmed in writing on a fully disclosed basis and if confirmed by us, a copy of each confirmation shall be sent to you if you so request. All sales are made subject to receipt of shares by us from the Funds. We reserve the right in our discretion, without notice, to suspend the sale of shares of the Funds or withdraw the offering of shares of the Funds entirely. Orders will be effected at the price(s) next computed on the day they are received if, as set forth in the applicable Fund’s current Prospectus, the orders are received by us or an agent appointed by us or the Fund prior to the close of trading on the New York Stock Exchange, generally 4:00 p.m. eastern time (“Close of Trading”). Orders received after that time will be effected at the price(s) computed on the next business day. All orders must be accompanied by payment in U.S. Dollars. Orders payable by check must be drawn payable in U.S. Dollars on a U.S. bank, for the full amount of the investment. If you have entered into a FundSERV Agreement with us to effect transactions in Fund shares through FundSERV, you are hereby authorized to act on our behalf for the limited purpose of receiving purchase, exchange and redemption orders for Fund shares executed through FundSERV. You represent and warrant that all orders for the purchase, exchange or redemption of Fund shares transmitted to FundSERV for processing on or as of a given business day (Day 1) shall have been received by you prior to the Close of Trading on Day 1. Such orders shall receive the share price next calculated following the Close of Trading on Day 1 .You represent and warrant that orders received by you after the Close of Trading on Day 1 shall be treated by you and transmitted to FundSERV as if received on the next business day (Day 2). Such orders shall receive the share price next calculated following the Close of Trading on Day 2. You represent that you have systems in place reasonably designed to prevent orders received after the Close of Trading on Day 1 from being executed with orders received before the Close of Trading on Day 1.

  • Notice to Proceed - Land Acquisition The acquisition of the Land shall not occur until the Director has issued a written Notice to Proceed for land acquisition to the Recipient (the "Notice to Proceed"). Such Notice to Proceed will not be issued until the Director has received a Request to Proceed acceptable to the Director and is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and any requirements for land acquisition set forth in this Agreement, including without limitation the OPWC's approval of the proposed Deed Restrictions and Title Agent. The Notice to Proceed also shall specify the time frame for the Closing.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!