Data Report Sample Clauses

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...
AutoNDA by SimpleDocs
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.
Data Report. 46 SECTION 3.16.
Data Report. The Contractor shall submit transportation data that identifies:

Related to Data Report

  • Data Reporting 1. Maintain and adhere to data system software and encrypted portable computer device updates, and interface capability requirements for each computer located within the facility, and as specified in the Contract and required by County.

  • 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., xxxxxxx 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 XxxxXxxxxx, 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.

  • Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.

  • Progress Report 10.1 If required, you shall submit progress reports in connection with the Service (“Report”) on at least a monthly basis, or as we may require. The Report shall include a summary of the activities and accomplishments during the previous reporting period.

  • Evaluation Report 20.5.4.1 The summary evaluation report shall be prepared by the Faculty Evaluation Committee and administrative evaluator(s) and shall include each evaluator’s individual rating. The summary evaluation report shall take into account the results of each of the evaluation components (Section 20.5.3) in order to arrive at an overall rating. When the committee and the administrative evaluator(s) cannot reach an agreement as to the overall rating, the report must include written explanation.

  • CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.

  • Monthly Report A. A Monthly Report shall be submitted within ten (10) calendar days of the end of each calendar month of the Period of Operation. Each Monthly Report shall be signed, dated, and certified by Concessionaire, Concessionaire’s Bookkeeper, or Accountant, and contain a Statement of Total Gross Receipts, excluding New Jersey State Sales Tax, derived by Concessionaire from operation of the Concession during the previous month. Each Monthly Report shall be based on the daily “Z” tapes or Point-of-Service (POS) device equivalent for that same month showing each day’s sales activity. Failure on the part of Concessionaire to provide the Monthly Report, when due, shall constitute a material breach of this Agreement subject to Suspension of Operations and/or Termination, in accordance with the terms and conditions set forth in Paragraphs 9 and 10. Concessionaire shall provide Department with any additional written clarification and/or information necessary to confirm the accuracy of any or all of Concessionaire’s Monthly Reports.

  • Implementation Report Within 120 days after the Effective Date, Xxxxxxxx shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • Final Report The goal of this subtask is to prepare a comprehensive Final Report that describes the original purpose, approach, results, and conclusions of the work performed under this Agreement. The CAM will review the Final Report, which will be due at least two months before the Agreement end date. When creating the Final Report Outline and the Final Report, the Recipient must use the Style Manual provided by the CAM.

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