Preparing Purchase Orders and Bookkeeping Functions Sample Clauses

Preparing Purchase Orders and Bookkeeping Functions. By o Processing HS/MS District Athletic Purchase Orders/Travel Requests for Athletic Director and coaches  Maintaining coaching professional development fund o Arranging bus/car transportation for coaches and teachers o Processing HS/MS sports payroll  Obtaining payroll signatures and forward to the District Office by the 5th of the month  Obtaining W-4 and payroll forms from workers for the District Office ESSENTIAL JOB RESPONSIBILITIES: CAREER & TECHNICAL EDUCATION
AutoNDA by SimpleDocs
Preparing Purchase Orders and Bookkeeping Functions. By o Preparing and maintaining CTE budget – updating to staff and CTE director o Processing district PO’s for CTE staff o Providing assistance to the District Office staff for processing leave forms

Related to Preparing Purchase Orders and Bookkeeping Functions

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • MANAGEMENT FUNCTIONS B-1 The Association recognizes that the management of the Hospital and the direction of the working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement, and without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to:

  • Meeting and Function Rooms to be Provided A. The Contractor shall provide to the Judicial Council the meeting and function rooms on the Dates and at the times set forth in Table 1, below, including necessary and appropriate set up. Prior to the Program, the Judicial Council will provide one

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Operations Support Systems Functions CBT shall provide CLEC, upon CLEC's request, nondiscriminatory access to CBT's Operations Support Systems functions for pre-ordering, ordering, provisioning, maintenance and repair and billing, in accordance with the terms and schedules established in the Commission’s Arbitration Award in Case No. 97-152-TP-ARB, August 14, 1997 (“Arbitration Award”). CBT shall provide CLEC advance written notice of any material changes to CBT operating support systems functions.

  • Purchase Order and Sales Contact Email Please enter a valid email address that will definitely reach the Purchase Order and Sales Contact. 2 xxxxx@xxxxxxxxxxxxxx.xxx Purchase Order and Sales Contact Phone Numbers only, no symbols or spaces (Ex. 8668398477). The system will auto-populate your entry with commas once submitted which is appropriate and expected (Ex. 8,668,398,477). 2 3 9566826005 Company Website Company Website (Format - xxx.xxxxxxx.xxx) 4 xxx.xxxxxxxxxxxxxx.xxx Entity D/B/A's and Assumed Names You must confirm that you are responding to this solicitation under your legal entity name. Go now to your Supplier Profile in this eBid System and confirm that your profile reflects your "Legal Name" as it is listed on your W9. In this question, please identify all of your entity's assumed names and D/B/A's. Please note that you will be identified publicly by the Legal Name under which you respond to this solicitation unless you organize otherwise with TIPS after award. 5 Superior Alarms Primary Address Primary Address 2 6 000 Xxx Xxxxxx Primary Address City Primary Address City 7 McAllen Primary Address State Primary Address State (2 Digit Abbreviation) 2 8 TX Primary Address Zip Primary Address Zip 9 78501 Search Words Identifying Vendor Please list all search words and phrases to be included in the TIPS database related to your entity. Do not list words which are not associated with the bid category/scope (See bid title for general scope). This will help users find you through the TIPS website search function. You may include product names, manufacturers, specialized services, and other words associated with the scope of this solicitation. security, monitoring, services, inspections, life safety, IP, surveillance, fire, IP cameras, access control, telephone, networking, GPS, fire alarm, voice evacuation, mass notification, panic, internet, and CCTV systems. Certification of Vendor Residency (Required by the State of Texas) Does Vendor's parent company or majority owner:

  • Systems Review The Construction Administrator will conduct reviews of proposed roof, structural, mechanical, electrical, plumbing, conveyance, sprinkler, telecommunications, and life safety systems, and will consider initial cost, availability, impact on the overall program, comfort and convenience, long-term maintenance and operating costs, and impacts on schedule.

  • Subscription Functions In cases where BellSouth performs subscription functions for an interexchange carrier (“IXC”) (i.e. PIC and LPIC changes via Customer Account Record Exchange (CARE)), BellSouth will provide the affected IXCs with the Operating Company Number (OCN) of the local provider for the purpose of obtaining end user billing account and other end user information required under subscription requirements.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

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