Issue File Sample Clauses

Issue File. Customer agrees to provide the Bank an Issue File with the following information: (1) Item Issue Date; (2) Dollar amount of the Item; (3) Item Payee; (4) Check Number of the Item. The Issue file should be sent the day the items are issued/drafted. The Bank will use the Issue File and compare it against the Outstanding File to produce a Suspect File (see Suspect File section).
AutoNDA by SimpleDocs
Issue File. You agree to transmit an Issue File to us in a file format that has been approved by us. The Issue File must accurately state the check number, the issue date, and the exact amount of each check drawn on each Authorized Account since the last Issue File was transmitted. Each Issue File must be transmitted via Business Online/Internet Banking by 4 p.m. Pacific Time.
Issue File. An electronic file containing account number(s), check number, dollar amount, issue date, and Payee name (when applicable) for every check issued by Company.
Issue File. You agree to transmit to us an Issue File in the file format we specify. The Issue File must accurately state the check number, the issue date, and the exact amount of each check drawn on each Authorized Account since the last Issue File was transmitted. Each Issue File must be transmitted via SANDeCRM no later than 6:00 p.m.

Related to Issue File

  • Appendix A – HRIS File Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives:

  • Employee File 27.01 Upon request to their immediate supervisor, employees are entitled to read, review and be provided with one (1) copy of any document in their human resources file at a mutually agreed time. The Senior Union Official, or designate, with the written authority of the employee, shall be entitled to review the employee's human resource file in the workplace, in order to facilitate the investigation of a grievance. The employee or the Senior Union Official, as the case may be, shall give the Employer seven (7) days' notice prior to examining the file. Employees shall have the right to rebut in writing any document, including but not limited to disciplinary notices and evaluations, in their human resources file. Such rebuttals, other than grievances, shall be attached to the document and placed in the personnel file.

  • Grievance File Records involving the processing of an employee's grievance, such as the grievance form, step appeals/responses, and settlement documents, will be kept in a file separate from the employee’s personnel file. It is not the intent of this section to exclude from the employee's personnel file final disciplinary action documents, including those that result from a settlement agreement.

  • Separate Grievance File All documents, communications and records dealing with the processing of a grievance shall be filed in a separate grievance file and shall not be kept in the personnel file of any of the participants.

  • Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.

  • EMPLOYEE FILES 10.01 A copy of any completed formal evaluation which is to be placed in an employee’s file shall be first reviewed with the employee. The employee shall initial such evaluation as having been read and shall have the opportunity to add her or his views to such evaluation prior to it being placed in her or his file. It is understood that such evaluations do not constitute disciplinary action by the Employer against the employee. Having provided a written request to the Director of Care, or her designate, an employee shall be entitled to her personnel file for the purpose of reviewing any evaluations or formal disciplinary notations contained therein, in the presence of the Director of Care, at a mutually agreeable time.

  • Access to File 12.01 An employee shall upon written request, made a reasonable time before the time of viewing, have an opportunity to view their personnel file in the presence of the Director of Human Resources or their designate. The information the employee may review will be:

  • Public Records Request (09/17) Contractor acknowledges that the City of Portland is subject to the Oregon Public Records Act and Federal law. Third persons may claim that the Confidential Information Contractor submitted to the City hereunder may be, by virtue of its possession by the City, a public record and subject to disclosure pursuant to the Oregon Public Records Act. The City’s commitments to maintain certain information confidential under this Contract are all subject to the constraints of Oregon and federal laws. All information submitted by Contractor is public record and subject to disclosure pursuant to the Oregon Public Records Act, except such portions for which Contractor requests and meets an exemption from disclosure consistent with federal or Oregon law. Within the limits and discretion allowed by those laws, the City will maintain the confidentiality of information.

  • Electronic Files a. It is the Buyer's responsibility to maintain a copy of any original Electronic File provided by the Buyer.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

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