Dual Approval Security Feature Sample Clauses

Dual Approval Security Feature. The security procedures for the OCD service include the option to use a dual approval security protocol. The dual approval security feature requires that at least two authorized users be involved in the check image capture and approval process in order to submit an OCD file for deposit. One user must scan the check images and then a second user with approval permissions must release and send the check image file to the bank. Only users with approval permission can submit the file to the bank for processing. We highly recommend this internal control process for any company large enough to have more than one employee involved in accounts receivable and check collection and deposit processes.
Sample 1
AutoNDA by SimpleDocs

Related to Dual Approval Security Feature

  • ROAD WORK PHASE APPROVAL Purchaser shall obtain written approval from the Contract Administrator upon completion of each of the following phases of road work:  Drainage installation  Subgrade compaction  Rock compaction SUBSECTION RESTRICTIONS

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • FAA APPROVAL This Agreement may be subject to approval of the FAA. If the FAA disapproves this Agreement, it will become null and void, and both Parties will bear their own expenses relative to this Agreement, up to the date of disapproval.

  • Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation

  • Rating Impact on Student Learning Growth ESE will provide model contract language and guidance on rating educator impact on student learning growth based on state and district-determined measures of student learning. Upon receiving this model contract language and guidance, the parties agree to bargain with respect to this matter.

  • Payment for Material Completion The Contractor may request payment of the remaining contract balance, including retainage, less amounts credited the Owner or incurred as liquidated damages, and less amounts withheld for the Punchlist by reason of Minor Items or Permitted Incomplete Work (See Paragraph 6.5.3.2). Payment for Material Completion shall be made by a check payable jointly to the Contractor and Surety and shall be mailed to the Surety.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Web-based-WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the HTTP response for only one HTTP request. If Registry Operator implements a multiple-step process to get to the information, only the last step shall be measured. If the RTT is 5-times or more the corresponding SLR, the RTT will be considered undefined.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!