Data Recordkeeping Sample Clauses

Data Recordkeeping. The IRS reserves the right to use a copy of all data provided under this agreement.
AutoNDA by SimpleDocs
Data Recordkeeping. 7.1 The Client acknowledges and agrees that VBCE will retain a record of all information provided by the Client. VBCE will record and track the Client’s use of VBCE’s Services.

Related to Data Recordkeeping

  • Recordkeeping A. To maintain its accounting records in accordance with generally accepted accounting principles (“GAAP”). GAAP are established by the Financial Accounting Standards Board (“FASB”).

  • REPORTING AND RECORDKEEPING The ownership of the property whether securities, cash and/or other property, and whether held by the Custodian or a subcustodian or in a depository, clearing agency or clearing system, shall be clearly recorded on the Custodian's books as belonging to the Series and not for the Custodian's own interest. Where certificates are legended or otherwise not fungible with publicly traded certificates (and in other cases where the Custodian and the Series may agree), the Series reserves the right to instruct the Custodian as to the name only in which such securities shall be registered and the Custodian, to the extent reasonably practicable, shall comply with such Instructions; provided, however, if the Custodian reasonably determines that compliance with such Instructions is not reasonably practicable or otherwise may conflict with applicable law, rule or regulation, the Custodian shall promptly notify the Series and shall comply with reasonable alternatives as to which the parties may agree. The Custodian shall keep accurate and detailed accounts of all investments, receipts, disbursements and other transactions for the Series. All accounts, books and records of the Custodian relating thereto shall be open to inspection and audit at all reasonable times during normal business hours of the Custodian by any person designated by the Series. All such books, records and accounts shall be maintained and preserved in the form reasonably requested by the Series and in accordance with the Act and the Rules and Regulations thereunder, including, without limitation, Section 31 thereof and Rule 31a-1 and 31a-2 thereunder. All books, records and accounts pertaining to the Series, which are in the possession of the Custodian, shall be the property of the Fund and such materials or (unless the delivery of original materials is required pursuant to applicable law) legible copies thereof in a format reasonably acceptable to the Fund, shall be surrendered promptly upon request; provided, however, that the Custodian shall be entitled to retain a copy or the original of any such books, records and accounts as may be required or permitted by applicable law and the Custodian's own policies and procedures. The Custodian will supply to the Series from time to time, as mutually agreed upon, a statement in respect to any property of the Series held by the Custodian or by a subcustodian.

  • Recordkeeping Requirements COLLEGE and SCHOOL DISTRICT shall comply with the requirements governing maintenance of records of each request for access to and each disclosure of, student education records set forth under Title 34, Code of Federal Regulations § 99.32 and under Education Code § 49064 as applicable.

  • Timekeeping Notwithstanding anything stated elsewhere in this Agreement. The Company may select and utilise for time keeping purposes any fraction or decimal proportion of an hour (not exceeding fifteen minutes) and will apply such proportion in the calculation of working time (including overtime) of an employee.

  • Recordkeeping and Reporting The Subadvisor shall maintain the records and information required by Rule 31a-1 under the 1940 Act described in Schedule B attached hereto, with respect to the Assets of the Series. In addition, the Subadvisor shall maintain such other records relating to the services the Subadvisor provides under this Agreement as may be required in the future by applicable SEC and other applicable rules, and shall retain such information for such times and in such manner as required by applicable rules, including but not limited to Rule 31a-2 under the 1940 Act. The records maintained by the Subadvisor hereunder shall be the property of the Fund and shall be surrendered promptly upon request; subject, however, to the Subadvisor's right to retain all such records as the Subadvisor is required to maintain under the Advisers Act and the rules and regulations promulgated thereunder; provided, further, that the Fund shall be entitled to make and maintain copies of any records so retained by request.

  • Electronic Records You acknowledge and agree that we may in our discretion store all records electronically; and that we will not retain and have no obligation to retain any original documents for any period of time. This applies to all documentation including but not limited to checks, transaction records, notes, mortgages, deeds of trust and other loan and/or security documentation. We will routinely destroy all original documentation. We may store records electronically via imaging, scanning, filming or other technology used in the financial services industry for the storage of documentation via internal processes or third-party processors that we approve for these services. You agree that such storage shall be secure, and further agree that such records shall for all purposes be recognized and admissible in evidence or otherwise to prove the agreements, rights and obligations of the parties pursuant to any such records.

  • Electronic Visit Verification (EVV). Provider shall cooperate with State requirements for electronic visit verification for personal care services and home health services, as applicable.

  • Time Keeping A Contractor may utilize brassing or other systems to check employees in and out. Each employee must check in and out. The Contractor will provide adequate facilities for checking in and out in an expeditious manner.

  • Electronic Visit Verification ("EVV Provider shall cooperate with State requirements for electronic visit verification for personal care services and home health services, as applicable.

  • 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.

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