eWIC Account Structure Requirements Sample Clauses

eWIC Account Structure Requirements. Requirement 373 Data in the eWIC EBT Subsystem shall conform to the constraints and Specifications defined in the State-approved MIS-EBT Interface Document developed by the eWIC MIS contractor. 374 The eWIC EBT Subsystem shall not allow access to WIC Benefits prior to midnight Pacific Time on the Benefit start date. 375 The eWIC EBT Subsystem shall make WIC Benefits available to Cardholders at midnight Pacific Time on the Benefit start date. 376 The eWIC EBT Subsystem shall not allow access to WIC Benefits after midnight Pacific Time following the Benefit end date. 377 Once created, eWIC EBT Account, Cardholder, and WIC-authorized Retailer Data shall remain on the System through the end of the Contract. 378 Once created, eWIC EBT Benefit Data shall remain on the System for a minimum of three (3) years. 379 The eWIC EBT Host System shall maintain a record of all changes to eWIC EBT Host System Data, including but not limited to transaction history and Card history, for a minimum of three (3) years. 380 After three (3) years, eWIC EBT transaction history and Card history shall be maintained on the eWIC EBT Host System or offline through the term of the Contract. 381 The Contractor shall maintain eWIC EBT transaction history and Card history records for subpoena requests for four (4) years after the termination or expiration of the Contract.
AutoNDA by SimpleDocs

Related to eWIC Account Structure Requirements

  • Health Spending Account (HSA Wellness Spending Account (WSA)/Registered Retirement Savings Plan (RRSP) utilization rates;

  • Requirements to Establish Escrow Accounts 11.10.1 To be acceptable, the Third Party escrow agent must meet all of the following criteria:

  • ISLAMIC ACCOUNTS 25.1 In the event that Customer, due to its observance of Islamic religious beliefs cannot receive or pay interest, Customer may elect to designate, in the manner provided by AvaTrade, its trading account to be an Islamic Account, which is not charged with, or entitled to, overnight interest and/or rollovers.

  • Accounting Requirements CONTRACTOR shall comply with all applicable COUNTY, State, and Federal accounting laws, rules and regulations. CONTRACTOR shall establish and maintain accounting systems and financial records that accurately account for and reflect all Federal funds received, including all matching funds from the State, COUNTY and any other local or private organizations. CONTRACTOR’s records shall reflect the expenditure and accounting of said funds in accordance with all applicable State laws and procedures for expending and accounting for all funds and receivables, as well as meet the financial management standards in 45 CFR Part 92 and in the Office of Management and Budget 2 CFR Part 200 “Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards.”

  • Match Requirements There is no match required on the part of the Grantee under this Agreement.

  • ACCURACY OF CUSTOMER’S PLANS AND MEASUREMENTS a) The Company is entitled to rely on the accuracy of any plans, specifications and other information provided by the Customer. The Customer acknowledges and agrees that in the event that any of this information provided by the Customer is inaccurate the Company accepts no responsibility for any loss, damages or costs howsoever resulting from these inaccurate plans, specifications or other information.

  • TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

  • OFFICE OF MANAGEMENT AND BUDGET (OMB) AUDIT REQUIREMENTS The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Specific Order Processes and Requirements 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders.

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