Invoice Data Elements Sample Clauses

Invoice Data Elements. Contractor identification: Name and address of the contractor Name and address of the contractor official to whom payment is to be sent via Electronic Funds Transfer (EFT) (will be the same as designated in the Contract). Customer identification: FEDLINK ID Customer identification [see Sec. G.3.3.2.]. If no user ID or account number is assigned by the contractor, it should be stated on the invoice. Name and address of agency using services Complete FEDLINK Delivery Order number (ex: 00-XX.XXXX.0000) Order information: Order date in mm/dd/yyyy format. Order date is the date the FEDLINK customer placed the order with the contractor and must be within the funding year of the corresponding Delivery Order number cited. Invoice number. Invoice number should uniquely identify the invoice. Invoice date in mm/dd/yyyy format. (Note: invoice date should not be before the date of order.) Contract line item number, where practicable, or descriptive information sufficient to identify. Schedule B item which corresponds to invoiced item.. Description, quantity, unit, unit price, and extended price of supplies delivered or services performed Discount applicable to individual FEDLINK customers, either by line item or against the invoice total, as appropriate. Any prompt payment discount. Any other information or documentation required by other specific requirements elsewhere in the contract such as evidence of shipment, receipt or prepayment). An invoice copy submitted as replacement for an original will be certified as a duplicate original, signed and dated. Invoice Number. Individual invoices will have unique numbers. Any invoice (including credit invoices) with a number which duplicates another invoice’s number is defective and will be rejected.
Sample 1
AutoNDA by SimpleDocs

Related to Invoice Data Elements

  • Invoice Data The Contractor shall report invoice data from each paid or remitted invoice within 30 calendar days after the end of the reporting quarter, including the invoice data on task orders issued through the GSA AAS Business System Portal. (Note: Whatever method the Contractor chooses (e.g., “each paid” or “remitted”) the Contractor must be consistent in their reporting method throughout the term of the OASIS Contract). If no Invoice Data was received during a required reporting period for a specific task order, the Contractor shall report in the “Zero Invoice Data” screen located in the CPRM system for that particular task order. Regardless of contract type, the Contractor shall report the following into the CPRM:

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Invoice System The Contractor shall submit invoices using State Form A-19 Invoice Voucher, or such other form as designated by DSHS. Consideration for services rendered shall be payable upon receipt of properly completed invoices which shall be submitted to by the Contractor not more often than monthly. The invoices shall describe and document to DSHS’ satisfaction a description of the work performed, activities accomplished, the progress of the project, and fees. The rates shall be in accordance with those set forth in Section 4, Consideration, of this Contract.

  • Invoice Errors If You find a material error in an invoice, then You must notify Dell in writing within 10 days from its receipt. Any amounts Dell and You both agree in writing to correct must be paid before the later of: (a) 14 days following the date of Dell’s corrected invoice; or (b) the original due date. If You withhold payment on the basis that an invoice is incorrect and Dell finds that the amount is accurate, then You must pay interest on the unpaid disputed amount from the invoice due date until Dell receives payment. You may not offset, defer, or deduct any invoiced amounts that Dell determines are correct following completion of this process.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment.

  • Authorized User’s Statement of Work A competitive Mini-Bid is required for every transaction under this Centralized Contract. An Authorized User must prepare a detailed Statement of Work using Appendix F, Attachment 1, Mini-Bid Template. The Authorized User must distribute the Mini-Bid to all qualified Vendors per Lot(s) (unless a Vendor has removed itself from consideration via the Appendix F, Attachment 5, Mini-Bid Participation Interest Template). Contact information, organized by Lot, will be available on the OGS website for this Contract. An Authorized User shall conduct its Mini-Bid in accordance with the requirements set forth in Appendix F, Attachment 2, How to Use this Contract. The following terms and conditions shall apply to each Mini-Bid issued by an Authorized User:  An Authorized User may require the execution of unique forms, such as Confidentiality Non- Disclosure agreements; and  An Authorized User is required to make tentative award and non-award notifications to each Contractor who submitted a response to the Mini-Bid. Additionally, the minimum time, excluding the date of release, between issuance of the Mini-Bid by the Authorized User to the Mini-Bid Opening is as follows:  Xxx 0 Xxxx-Xxxx: Xxxx (0) Xxxxxxxx Xxxx  Xxx 0 Mini-Bids: Ten (10) Business Days

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Month, Assuming Institution shall provide Receiver:

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Data Center Location Upon the effective date of the Agreement, the Data Centers used to host Personal Data in the Cloud Service are located in the EEA or Switzerland. SAP will not migrate the Customer instance to a Data Center outside the EEA or Switzerland without Customer’s prior written consent (email permitted). If SAP plans to migrate the Customer instance to a Data Center within the EEA or to Switzerland, SAP will notify Customer in writing (email permitted) no later than thirty days before the planned migration.

Time is Money Join Law Insider Premium to draft better contracts faster.