Issued Check File Sample Clauses

Issued Check File. For Accounts identified in the Request and Implementation Forms, Client agrees to deliver or transmit the check number, date, payee and the exact dollar amount of each check drawn on an Account on the day such checks are issued (such data cumulatively, the “Issued Check File”) to Bank in the format and medium as specified by Bank. Each Account shall require an Issued Check File for all checks issued. Client shall submit the Issued Check File to Bank no later than 7:00 p.m. Central Time each Business Day that Client issues checks. With the exception of checks presented for immediate payment in person at Bank over the counter (“On-us checks”), Issued Check File data received by 7:00
AutoNDA by SimpleDocs
Issued Check File. You agree to provide us with a list of the serial numbers, issue dates, payee names (exact spelling) and the exact amounts (dollars and cents) of the checks that you have issued (“Issued Check File”). We will match the check numbers, payee names and amounts against items presented to us through normal interbank check clearing procedures (e.g., local clearinghouse, Federal Reserve, or direct send presentment cash letter) (“Presented Checks”). You authorize and instruct us to pay Presented Checks that match the serial numbers, payee names and amounts set forth in an Issued Checks File received by us in your name, without further investigation or review by us. You agree that: (a) Presented Checks that match the check numbers, payee names and amounts are, and should be treated by us as, properly payable; (b) we have no duty to inspect Presented Checks for unauthorized or improper signatures or alterations or otherwise to take steps to determine whether they are properly payable; and (c) we may compare Issued Check File information with information that is encoded on Presented Checks. We assume no duty to identify and/or return duplicate checks, checks with duplicate serial numbers, mis-encoded items, checks with non-matching issue dates, or checks lacking an encoded serial number. We will not be required to physically examine matching checks to confirm that they are properly signed, completed and encoded. You agree that we may rely on the process described above and that it will be deemed an acceptable standard of care for this Service and youraccount.
Issued Check File. Referenced sometimes herein as the “File” is a file issued by Company to the Bank which provides a list of all outstanding checks issued by Company against the designated accounts which were not previously listed on an Issued Check File.
Issued Check File. By transmitting the File, Company expressly warrants that all Presented Checks that match the information in the File are properly payable. The File must accurately state the check number, issue date, and exact dollar amount on each check drawn on the designated accounts. Before beginning the Positive Pay Service and providing its first File, Company must provide Bank a list of all outstanding checks on the designated accounts. Any Presented Check that does not appear in a File received by Bank or that is not manually uploaded by Company, shall appear as an Exception Item. In order to avoid having a large number of Exception Items, Company should upload the File or checks to Bank’s system by the deadlines provided in the Positive Pay Configuration/Training Checklist.
Issued Check File. The Customer shall submit an Issued Check File to the Bank. 2.1.1 The Issued Check File shall accurately state the check number, date and the exact dollar amount of each check drawn on an Authorized Account since the last Issued Check File was submitted. Each Authorized Account shall require an Issued Check File for all checks issued. 2.1.2 The Customer shall send the Issued Check File to the Bank in the format and medium as specified by the Bank and agreed to by the Customer. 2.1.3 In the event of system failure, either that of the Customer’s or of the Bank’s, and the Issued Check File cannot be received by the Bank or the Bank cannot process the file, the file shall be considered as not received, even if the Bank has possession of the file.

Related to Issued Check File

  • Database File The Servicer will provide the Successor Servicer with a magnetic tape (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Initial Cutoff Date, (ii) the Subsequent Cutoff Date, (iii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Service Transfer and (iv) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Service Transfer.

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

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

  • Record and File Retention Grantee must maintain these files for five years after the end of the applicable fiscal year, except that, if any litigation, claim or audit is commenced with respect to the transactions documented by such files before the end of the aforementioned five-year period and extends beyond the expiration of the five-year period, these files must be retained until all litigation, claims, or audit findings involving the files have been resolved.

  • Receivable Files Complete There exists a Receivable File pertaining to each Receivable. Related documentation concerning the Receivable, including any documentation regarding modifications of the Contract, will be maintained electronically by the Servicer in accordance with customary policies and procedures. With respect to any Receivables that are tangible chattel paper, the complete Receivable File for each Receivable currently is in the possession of the Custodian.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Monthly Reports No later than 10:00 a.m., Chicago, Illinois time, two Business Days prior to each Distribution Date, the Servicer shall deliver to the Trustees and each Rating Agency a Monthly Report.

  • Inspection Checklist (Check one)

  • Transaction Reports Subadviser shall provide Investment Manager a daily trade file with information relating to all transactions concerning the allocated portion of the Fund’s assets for which Subadviser is responsible and shall provide Investment Manager with such other information regarding the Fund upon Investment Manager’s reasonable request. Subadviser shall affirm or send a trade file of these transactions as instruction to the custodian of the Fund.

  • Physical File Characteristics 7.2.1 The EODUF feed will be distributed to Comcast Phone over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among Comcast Phone’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). 7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and Comcast Phone for the purpose of data transmission. Where a dedicated line is required, Comcast Phone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Comcast Phone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Comcast Phone. Additionally, all message toll charges associated with the use of the dial circuit by Comcast Phone will be the responsibility of Comcast Phone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. Version 4Q01 12/01/01 All equipment, including modems and software, that is required on Comcast Phone’s end for the purpose of data transmission will be the responsibility of Comcast Phone.

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