Payment Data. The Construction Manager shall submit to the City, upon request, all payrolls, reports, estimates, records and any other data concerning the Work performed or to be performed or concerning materials supplied or to be supplied, as well as Subcontractor or Consultant payment applications or invoices and such Subcontractor’s or Consultant progress payment checks. The requirements of this Section shall be included in all contracts between the Construction Manager and its Subcontractors and Consultants. The City may exercise its rights under this Section as often as reasonably necessary in the City’s sole judgment to ensure the City has a complete and accurate understanding of all Project costs.
Payment Data. The Job Order Contractor shall submit to the City, upon request, all payrolls, reports, estimates, records and any other data concerning the Work performed or to be performed or concerning materials supplied or to be supplied, as well as Subcontractor or consultant payment applications or invoices and such Subcontractor’s or consultant progress payment checks. The requirements of this Section shall be included in all contracts between the Job Order Contractor and its Subcontractors and consultants. The City may exercise its rights under this Section as often as reasonably necessary in the City’s sole judgment to ensure the City has a complete and accurate understanding of all Job Order costs.
Payment Data. DPC must receive all Payment Data no later than three (3) business days prior to scheduled pay date. If Payment Data is received after this time, customer understands that there is a risk that payments to Payees may be delayed. The Customer shall provide DPC with all data necessary for the desired electronic funds transfers (Payment Data) in the form and at the time prescribed by DPC and shall make periodic checks to assure that the Payment Data is current and accurate at all times. DPC assumes no responsibility or liability for delays in service caused by Payment Data or changes which are not received within the time frames or in the format necessary to properly carry out its’ responsibilities. Customer warrants to DPC that all Payment Data delivered to DPC by Customer (a) will contain true and accurate information, (b) will be fully authorized by Customer and Payees, and (c) will be timely under the terms and provisions of this Agreement. DPC has no responsibility to review such data in any manner, including accuracy, consistency and conformity to prior Payment Data.
Payment Data. Operating Partnership shall provide SBC and SBC Sub with all information, data and calculations SBC and SBC Sub may request with respect to any Payments due to enable SBC and SBC Sub to verify Operating Partnership's and Prodigy's compliance with its obligations hereunder.
Payment Data. We may collect data necessary to process your payment if you make purchases, such as your payment instrument number (such as a credit card number), and the security code associated with your payment instrument. All payment data is stored by Paytech Technologies Limited. You may find their privacy notice link(s) here: .
Payment Data. 12.1. All Data obtained by the Contractor in order to provide the Services shall be stored and maintained by the Contractor on a separate and distinct information technology database which shall be SQL compliant.
12.2. All Payment records, Data and Biometric Data shall remain the property of SASSA, and may not be altered or disposed of without prior approval of SASSA.
12.3. SASSA shall have access to and be entitled to utilize, for the maintenance and development of its own systems, all the Data in the Contractor’s possession.
12.4. The Payment solution must have appropriate record keeping and transaction Data security provisions.
12.5. The Contractor shall ensure that SASSA is able to access the electronic data in respect of Enrolment, Payment information, statistical information, management information and any other agreed upon relevant information at any given time.
Payment Data. To effectuate payments of Fees and other transactions with Subscribers and/or Partners, Zwapgrid must collect and process payment details (account number, credit card information or similar).
Payment Data. DPC must receive all Payment Data no later than three (3) business days prior to scheduled pay date. If Payment Data is received after this time, customer understands that there is a risk that payments to Payees may be delayed. The Customer shall provide DPC with all data necessary for the desired electronic funds transfers (Payment Data) in the form and at the time prescribed by DPC and shall make periodic checks to assure that the Payment Data is current and accurate at all times. DPC will debit Customer’s Authorized Account at least two business days prior to pay date and will credit Xxxxx’s accounts on scheduled pay date. DPC assumes no responsibility or liability for delays in service caused by Payment Data or changes which are not received within the time frames or in the format necessary to properly carry out its’ responsibilities. Customer warrants to DPC that all Payment Data delivered to DPC by Customer (a) will contain true and accurate information, (b) will be fully authorized by Customer and Payees, and (c) will be timely under the terms and provisions of this Agreement. DPC has no responsibility to review such data in any manner, including accuracy, consistency and conformity to prior Payment Data.
Payment Data. Bank agrees to capture, combine and reformat electronic payment and remittance data originated by your customers through online banking or bill payment services at other financial institutions (“Payment Data”). You expressly authorize Bank and its service provider to accept and process the Payment Data and payment funds, such that the receipt of such Payment Data and payment funds by Bank or its service provider shall be deemed to be the same as receipt of such Payment Data and payment funds by you yourself.
Payment Data. With each payment, OLPG shall transmit to HSC-S data necessary for LSU to determine how to allocate the funds received among its various departments and faculty. OLPG and the Xxxx of HSC-S School of Medicine shall mutually agree on the data required and the appropriate format.
