SARS Interface Requirements Sample Clauses

SARS Interface Requirements. Requirement 840 The System shall transmit batch Files specified in the Food and Cash EBT Interface Specification, Appendix I, to SARS. 841 The System shall complete transmission of daily end-of-day Files to SARS by 10:00 p.m. Pacific Time following the end of the Settlement Day. 842 The System shall transmit Report Files specified in the Reports Specification to SARS. 843 The System shall complete transmission of Files for all Settlement Day EBT Reports to SARS by 10:00 p.m. Pacific Time following the end of the Settlement Day. 844 The System shall complete transmission of Files for all calendar EBT Reports to SARS by 2:00 a.m. Pacific Time following the end of the previous Calendar Day. 845 The System shall complete transmission of other monthly and other periodic batch Files to SARS within five (5) Calendar Days after the last day of the batch File reporting period. 846 The System shall complete transmission of Report Files for weekly EBT Reports to SARS within two (2) Calendar Days after the last day of the reporting period. # Requirement 847 The System shall complete transmission of Report Files for monthly and quarterly EBT Reports to SARS within five (5) Calendar Days after the last day of the reporting period. 848 The System shall begin transmitting copies of daily and monthly food and cash Benefit batch Files to SARS no later than one (1) minute after completion of batch File processing. 849 The System shall begin transmitting copies of daily and monthly food and cash Benefit batch return Files to SARS within one (1) minute after completion of batch File processing. 850 The Contractor shall notify the SARS point of contact within fifteen (15) minutes if transmission of Files and Reports cannot be completed within the required timeframes.
Sample 1
AutoNDA by SimpleDocs

Related to SARS Interface Requirements

  • Interface Requirements 9.3.1 BellSouth shall offer LIDB in accordance with the requirements of this subsection.

  • Space Requirements The Construction Administrator will conduct a review of the adequacy of space allotments for maintenance of mechanical, telephone, and fire protection equipment.

  • Service Requirements Grantee shall:

  • Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:

  • Additional Service Requirements Grantee shall:

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

  • Construction Requirements a) All Life and Safety and applicable Building Codes will be strictly enforced (i.e., tempered glass, fire dampers, exit signs, smoke detectors, alarms, etc.). Prior coordination with the Building Manager is required.

  • Age Requirements If you are a sole proprietor, and you are not old enough to enter into a contract on your own behalf (which is commonly but not always 18 years old), but you are 13 years old or older, your Representative must be your parent or legal guardian. If you are a legal entity that is owned, directly or indirectly, by an individual who is not old enough to enter into a contract on their own behalf, but the individual is 13 years old or older, your Representative must obtain the consent of either your board or an authorised officer. The approving board, authorised officer, parent or legal guardian is responsible to Stripe and is legally bound to this Agreement as if it had agreed to this Agreement itself. You must not use the Services if you are under 13 years of age.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

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

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