My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01/17/2017 (2)
CBCC
>
Meetings
>
2010's
>
2017
>
01/17/2017 (2)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/23/2017 1:44:52 PM
Creation date
4/13/2017 12:07:15 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC Regular Meeting
Document Type
Agenda Packet
Meeting Date
01/07/2017
Meeting Body
Board of County Commissioners
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
204
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
9. Recording and Use of Communications. <br />Customer and Bank agree that all telephone conversations <br />or data transmissions between thein or their agents made in <br />connection with this Appendix may be electronically <br />recorded and retained by either party by use of any <br />reasonable means. <br />10. Processing, Transmittal and Settlement of <br />Entries by Bank. <br />10.1 Bank will process, transmit and settle for <br />credit and debit Entries initiated by Customer as provided in <br />the NACHA Rules as in effect from time to time, and pursuant <br />to this Appendix. Exclusive of "Same Day ACH Entries," <br />which are described in Section 23 below, Bank will transmit <br />such Entries as an ODFI to the ACH Operator by the deadlme <br />of the ACH Operator, provided such Entries are received by <br />Bank prior to 8:00 p.m. Eastern Time ("ET") and the ACH <br />Operator is open for business on such Business Day. Entries <br />received after 8:00 p.m. ET will be deemed received the <br />following Business Day. If the Effective Entry Date falls on a <br />non -Business Day, final settlement will occur on the next <br />Busmess Day. Customer may submit a NACHA-formatted <br />file up to the time limit in advance of the Effective Entry Date <br />as the Services permit, or as may otherwise be permitted by <br />Bank under the teens of this Appendix. Customer will hold <br />Bank harmless from all charges and liabilities that may be <br />incurred as a result of the delivery of late Entnes. <br />10.2 If the file of Entries is received other <br />than in specified NACHA and Bank format, Customer will <br />be required to provide Bank with a corrected file. If a <br />corrected file of Entries is received later than 8.00 p.m. ET <br />on the delivery date with an intended Effective Entry Date <br />of next -Business Day, Customer will hold Bank harmless <br />from all charges and liabilities that may be incurred as a <br />result of the processing of late Entries. <br />10.3 For purposes of this Appendix, Entries <br />shall be deemed received by Bank, in the case of electronic <br />file transmission, when the transmission is completed as set <br />forth in Bank's Appendix for Data Transmission Services <br />and/or the Services' Setup Form(s). <br />10.4 If any of the requirements of this <br />Section 10 (or of Section 23 with respect to Same Day <br />ACH Entnes) are not met, Bank shall use reasonable efforts <br />to transmit such Entries to the ACH Operator by the next <br />deposit deadline on which the ACH Operator is open for <br />business. <br />11. On -Us Entries. Except as otherwise provided <br />herein, in the case of an Entry received for credit or debit to <br />an account maintained by Bank (an "On -Us Entry"), Bank <br />will credit or debit the Receiver's account in the amount of <br />such Entry on the Effective Entry Date, provided the <br />requirements set forth herein are otherwise met. If those <br />requirements are not met, by reason of stale or same-day <br />Effective Entry Dates on such Entries, Bank will credit or <br />debit the Receiver's account in the amount of such Entry on <br />the date the Entry was received by Bank, or if the Entry <br />was received on a non -Business Day, Bank will credit or <br />debit the Receiver's account in the amount of such Entry on <br />the next Banking Day following the date the Entry was <br />received by Bank. Bank will have the right to reject an On - <br />Us Entry as described in Section 12, Returned or Rejected <br />Entries. In the case of an On -Us Entry, Bank will have all <br />nghts of an RDFI including, without limitation, the rights <br />set forth in NACHA Rules. <br />12. Returned or Rejected Entries. <br />12.1 In the event any Entry is returned or <br />rejected by the ACH Operator or any RDFI or Intermediary <br />Depository Financial Institution for any reason whatsoever, it <br />shall be the responsibility of Customer to remake and <br />resubmit such Entry or otherwise resolve the returned Entry in <br />accordance with the NACHA Rules. <br />12.2 Bank shall remake such Entry in any <br />case where rejection by the ACH Operator was due to <br />mishandling of such Entry by Bank and sufficient data is <br />available to Bank to permit it to remake such Entry In all <br />other instances, Bank's responsibility will be to receive <br />rejected or retumed Entries from the ACH Operator, perforin <br />necessary processing, control and settlement functions, and to <br />forward such Entries to Customer. Except for an Entry <br />retransmitted by Customer in accordance with the <br />requirements of Section 5, Transmittal of Entries by <br />Customer, Bank shall have no obligation to retransmit a <br />returned Entry to the ACH Operator if Bank complied with <br />the terms of this Appendix with respect to the original Entry <br />12.3 Bank may reject any Entry which does <br />not comply with the requirements of Section 5, Transmittal of <br />Entries by Customer, or Section 7, Security Procedures. Bank <br />may also reject any Entry which contains a future Settlement <br />Date that exceeds the limits set forth within the Services. <br />Bank may reject an On -Us Entry for any reason for which an <br />Entry may be returned under the NACHA Rules. Bank may <br />reject any Entry or file if Customer has failed to comply with <br />its Settlement Account balance obligations under Section 2, <br />Customer Obligations, or Customer's Exposure Limit under <br />Section 3, Risk Exposure Limits. Notices of rejection shall be <br />effective when given. Bank shall have no liability to <br />Customer by reasons of the rejection of any such Entry or the <br />fact that such notice is not given at an earlier time than that <br />provided for herein. Bank may monitor Customer's rejected <br />or retumed Entries. Bank reserves the right, in its sole and <br />exclusive discretion, to require Customer to establish a <br />reserve Account in the event that an excessive number of <br />Customer's debit Entnes are rejected or returned. <br />12.4 In accordance with NACHA Rules, Bank <br />may monitor returned Entries, and in its sole discretion, may: <br />(1) require Customer to lower its retum rates, (2) invoke <br />premium penalty fees for unauthorized or excessive retum <br />rates, and/or (3) mvoke termination or suspension of the <br />Services and/or this Appendix in conjunction with Section 31 <br />of this Appendix. <br />13. Cancellation or Amendment by Customer. <br />Customer shall have no right to cancel or amend any Entry <br />or file after its receipt by Bank. However, if such request <br />complies with the Security Procedures applicable to the <br />HC 4814-6754-1149 26 of 58 022016 <br />P40 <br />
The URL can be used to link to this page
Your browser does not support the video tag.