PAYEE DATA RECORD FORM STD 204: This form must be completed by all contractors that are not another state agency or other governmental entity.
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 Record Search The Reporting Financial Institution must review electronically searchable data maintained by them for any of the following indicia:
Inspection of Records Upon reasonable notice to the Administrative Trustees and the Property Trustee, the records of the Trust shall be open to inspection by Securityholders during normal business hours for any purpose reasonably related to such Securityholder's interest as a Securityholder.
MARC Records When applicable to the Licensed Materials, at Licensee’s request, Licensor shall provide full OCLC-quality batched sets of MARC records incorporating Licensee specifications at no additional cost by the date of the execution of this License Agreement. Updates to existing records and new title records, matching the schedule of release and delivery of new publications, will be provided on a mutually agreed-upon schedule and in a format that renders them useful to the Licensee and/or the Participating Institutions.
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.
SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.
Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts. Contractor shall maintain all Records, fiscal and otherwise, directly relating to this Contract in accordance with generally accepted accounting principles so as to document clearly Contractor's performance. Following final payment and termination of this Contract, Contractor shall retain and keep accessible all Records for a minimum of three years, or such longer period as may be required by law, or until the conclusion of any audit, controversy, or litigation arising out of or related to this Contract, whichever date is later.
Emergency Alert System The Franchisee shall comply with the applicable requirements of the FCC with respect to the operation of an Emergency Alert System (“EAS”) requirements of the FCC and applicable state and local EAS plans in order that emergency messages may be distributed over the Cable System.
Contractor’s Records The Contractor shall keep true and accurate accounts, records, books and data which shall correctly reflect the business transacted by the Contractor in accordance with generally accepted accounting principles. These records shall be stored in Orange County for a period of three (3) years after final payment is received from the County. Storage of records in another county will require written approval from the County of Orange assigned Deputy Purchasing Agent.
