Terms of Data Reconciliation. With respect to a pair of Matched PCA Parties that have elected to supplement Matched PCAs by incorporating SBS II Schedule 4, data reconciliation shall be conducted as follows:
Terms of Data Reconciliation Sample Clauses
Related to Terms of Data Reconciliation
Reconciliation of records The Fiscal Agent will at least once every month reconcile its record of the IOA of the Notes with information received from the ICSDs (through the Common Service Provider) with respect to the IOA maintained by the ICSDs for the Notes and will promptly inform the ICSDs (through the Common Service Provider) of any discrepancies.
Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA.
Contract Reconciliation Grantee, within 45 calendar days after the end of each fiscal term year, will submit to the System Agency email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx, financial and reconciliation reports required by System Agency in forms as determined by System Agency.
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.
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.
PAYEE DATA RECORD FORM STD 204: This form must be completed by all contractors that are not another state agency or other governmental entity.
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.
Account Reconciliation You will verify and reconcile any out-of-balance condition, and promptly notify the Credit Union of any errors within the time periods established in the Membership and Account Agreement after receipt of your account statement. If notified within such period, the Credit Union shall correct and resubmit all erroneous files, reports, and other data at the Credit Union's then standard charges, or at no charge, if the erroneous report or other data directly resulted from the Credit Union's error.
On Reconciliation and Settlement If the year-end reconciliation and settlement process demonstrates that the HSP received Funding in excess of its confirmed funds, the LHIN will require the repayment of the excess Funding.
Annual Reconciliation By June 30th of each calendar year, or as soon thereafter as reasonably possible, Landlord shall endeavor to furnish Tenant with an accounting prepared with reasonable detail of actual Operating Expenses and Tax Expenses. Within thirty (30) days of Landlord's delivery of such accounting, Tenant shall pay to Landlord the amount of any underpayment. Notwithstanding the foregoing, failure by Landlord to give such accounting by such date shall not constitute a waiver by Landlord of its right to collect any of Tenant's underpayment at any time. Landlord shall credit the amount of any overpayment by Tenant toward the next Base Rent falling due, or where the Term of the Lease has expired, refund the amount of overpayment to Tenant. If the Term of the Lease expires prior to the annual reconciliation of expenses Landlord shall have the right to reasonably estimate Tenant's Share of such expenses, and if Landlord determines that an underpayment is due, Tenant hereby agrees to pay to Landlord the amount of such underpayment within thirty (30) days after Landlord's delivery of a demand therefor. If Landlord reasonably determines that an overpayment has been made by Tenant, Landlord shall refund said overpayment to Tenant within thirty (30) days after Landlord has made such determination. Notwithstanding the foregoing, failure of Landlord to accurately estimate Tenant's Share of such expenses or to otherwise perform such reconciliation of expenses, including without limitation, Landlord's failure to make a written demand for any underpayment from Tenant, shall not constitute a waiver of Landlord's right to collect any of Tenant's underpayment at any time during the Term of the Lease during the one (1) year period following the last day of the period to which such underpayment relates or at any time during the one (1) year period following the expiration or earlier termination of this Lease.
