Required Vendor Sales Reporting By responding to this Solicitation, you agree to report to TIPS all sales made under any awarded Agreement with TIPS. Vendor is required to report all sales under the TIPS contract to TIPS. If the TIPS Member entity requesting a price from the awarded Vendor requests the TIPS contract, Vendor must include the TIPS Contract number on any communications with the TIPS Member entity. If awarded, you will be provided access to the Vendor Portal. To report sales, login to the TIPS Vendor Portal and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS.
Reporting Frequency During any period of time when you are subject to the requirement in paragraph 1 of this award term and condition, you must report proceedings information through XXX for the most recent five year period, either to report new information about any proceeding(s) that you have not reported previously or affirm that there is no new information to report. Recipients that have Federal contract, grant, and cooperative agreement awards with a cumulative total value greater than $10,000,000 must disclose semiannually any information about the criminal, civil, and administrative proceedings.
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: 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
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Reporting TIPS Sales Vendor must report all TIPS Sales to TIPS. If a TIPS sale is initiated by Vendor receiving a TIPS Member’s purchase order from TIPS directly, Vendor may consider that specific TIPS Sale reported. Otherwise, with the exception of TIPS Automated Vendors, who have signed an exclusive agreement with TIPS regarding reporting, all TIPS Sales must be reported to TIPS by either: (1) Emailing the purchase order or similar purchase document (with Vendor’s Name, as known to TIPS, and the TIPS Contract Name and Number included) to TIPS at xxxxxx@xxxx-xxx.xxx with “Confirmation Only” in the subject line of the email within three business days of Vendor’s acceptance of the order, or; (2) Within 3 business days of the order being accepted by Vendor, Vendor must login to the TIPS Vendor Portal and successfully self-report all necessary sale information within the Vendor Portal and confirm that it shows up accurately on your current Vendor Portal statement. No other method of reporting is acceptable unless agreed to by the Parties in writing. Failure to report all sales pursuant to this provision may result in immediate cancellation of Vendor’s TIPS Contract(s) for cause at TIPS’ sole discretion. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx.
Ad Hoc Sales Reports The Department may require additional Contract sales information such as copies of purchase orders or ad hoc sales reports. The Contractor shall submit these documents and reports in the format acceptable to the Department and within the timeframe specified by the Department.
Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).
Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.
B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.
CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.
EDD Independent Subrecipient Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, Subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the State.” The term is further defined by the California Employment Development Department to refer specifically to independent Subrecipients. An independent Subrecipient is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm
