Data Report Sample Clauses

A Data Report clause outlines the requirements and procedures for providing, maintaining, or sharing data-related reports between parties. Typically, it specifies the type of data to be reported, the format and frequency of reporting, and the responsibilities of each party in preparing or reviewing these reports. For example, a vendor may be required to submit monthly usage statistics or compliance summaries to a client. The core function of this clause is to ensure transparency and accountability by establishing clear expectations for data reporting, thereby facilitating informed decision-making and monitoring of contractual obligations.
Data Report. On each Determination Date, the Servicer will transmit or deliver to the Notice Parties a data report in the form of magnetic tape or diskette or computer modem transmission, in a format reasonably acceptable to the Notice Parties, containing such information as the Notice Parties may reasonably require with respect to the Contracts as of the close of business on the last day of the preceding Collection Period, including without limitation the information necessary for preparation of the Servicer's Certificate (a "Data Report"). The Servicer shall also transmit to the Notice Parties a Data Report concurrently with the delivery of any Notice of Borrowing and Pledge, containing information with respect to any new Contracts to be added to the Collateral on or before the Funding Date and the Contracts included in the Collateral after giving effect to such Advance. The Backup Servicer shall verify that each Data Report is in a readable and usable form and covers all information necessary to service the Contracts, including, but not limited to, Aggregate Implicit Principal Balance of the Contracts, Available Funds, Delinquent Contracts, Defaulted Contracts, Recoveries, prepayments and bankruptcies. The Backup Servicer shall use each such monthly Data Report to confirm that the Servicer's Certificate delivered by the Servicer for the related Collection Period is correct with respect to the following information: beginning and ending Aggregate Implicit Balance of the Contracts; beginning and ending Total Outstanding Advances; the Implicit Principal Balance of Contracts that are 31-60, 61-90 and 91 or more days delinquent; the 31 to 60 Day Delinquency Ratio; the 61 to 90 Day Delinquency Ratio; the NPA Ratio; the sum of the Implicit Principal Balance of Defaulted Contracts for the related Collection Period; the Annualized Charge Off Ratio; the Borrowing Base; the Borrowing Base Deficiency, if any; and confirmation of concentrations by Customer, broker, type of Equipment, FinPac Custom Score and geographic territory as of the end of the related Collection Period. The Backup Servicer shall notify the Servicer and the Notice Parties of any material discrepancies in connection with such verification 11 Servicing Agreement and confirmation on or before the third Business Day following the applicable Determination Date. The Backup Servicer shall provide, before the end of the related calendar month, written certification to the Notice Parties that the information confirme...
View SourceView Similar (4)
Data Report. The results of the field exploration and laboratory testing will be presented in an appropriately illustrated data report. The report will contain a brief project and site description plus a site plan showing the locations of Consultant field explorations, logs of the field explorations, and laboratory test results by GPI and others.
View Source
Data Report. TERRA will produce a written report detailing the methods, procedures, locations and results of the trail count effort. This will include a picture of the camera setup, approximate location, count data and camera view from each location.
View Source
Data Report. The Contractor shall submit transportation data that identifies: A. The unduplicated number of members served; B. The number of trips provided by mode; C. Post trip review and verification report on a quarterly basis; D. Number of trips denied by reason denied; E. Number of trips scheduled; F. Number of trips canceled by the Contractor; G. Number of member no-shows (i.e. cancelled at the door; the transportation provider attempted pickup); H. The list of the “most costly” Members, (number to be determined by the Department and reported on a quarterly basis); I. Upon request of the Department, the number of trips completed, no show, and late by each transportation subcontractor. J. The number of multi-loading trips booked and fulfilled. d. Subsection 5. (Complaint Report) is deleted and replaced with the following:
View Source
Data Report. 46 SECTION 3.16.
View Source

Related to Data Report

  • DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with ▇▇▇. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A. b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and ▇▇▇, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915. c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., ▇▇▇▇▇▇▇ claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by ▇▇▇▇▇▇▇▇▇▇, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Data Retention 11.1 The Parties agree to erase Personal Data from any computers, storage devices and storage media that are to be retained as soon as practicable after it has ceased to be necessary for them to retain such Personal Data under applicable Data Protection Legislation and their privacy policy (save to the extent (and for the limited period) that such information needs to be retained by the a Party for statutory compliance purposes or as otherwise required by the contract), and taking all further actions as may be necessary to ensure its compliance with Data Protection Legislation and its privacy policy.