My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
02/07/2017 (4)
CBCC
>
Meetings
>
2010's
>
2017
>
02/07/2017 (4)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/29/2025 12:41:46 PM
Creation date
4/13/2017 12:25:01 PM
Metadata
Fields
Template:
Meetings
Meeting Type
BCC Regular Meeting
Document Type
Agenda Packet
Meeting Date
02/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.
/
223
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
Subject to the terms of this Agreement, Bank will process the transaction file containing Customer's Entries and transmit the Entries to the ACH <br />within applicable deadlines to meet the Effective Entry Date specked in the file, provided that Bank receives the file from Customer by the <br />applicable deadlines and the Customer complies with any Prefundmg requirements. A file contained on tape is received by Bank when die tape is <br />actually received at the location Bank specifies from time to time. A file transmitted to Bards via electronic transmission is received by Bank when <br />the transmission is completed and Bank is satisfied that applicable security procedures have been followed If Bank receives a file from Customer <br />after the applicable deadline, Bank will use reasonable efforts to process that file so that settlement can be completed as scheduled. However, Bank <br />will not be liable to Customer or to any third party if settlement is not met. Upon request, Bank will provide Customer with a list of days on which <br />Bank does not process files and changes to the list as they occur. <br />Customer agrees that Bank has no obligation to accept Entries and therefore may reject any Paltry submitted by Customer. Bank may reject any <br />Entry which does not comply with the requirements of the Agreement, including applicable security procedures and Prefunding requirements or <br />Limits (as defined below), or for which Bank has reason to believe Customer has breached one or more of the warranties Customer made to Bank <br />with respect to such Entry, or for any other reason permitted under the Rules. Bank may also reject an Entry (with subsequent notice of rejection <br />being forwarded to Customer) without liability to Customer i4 in Bank's reasonable judgment, processing the Entry would cause Bank to violate <br />any applicable law or regulation. If Bank rejects any Entry under this paragraph, Bank will use reasonable efforts to notify Customer the same day. <br />In any can, Bank will notify Customer no later than the Effective Entry Date. Bank shall have no liability to Customer for rejection of an Entry or <br />for failure to notify Customer of rejection and shall not be liable to pay any interest to Customer even if the amount of Customer's payment order <br />is fully covered by awithdrawable credit balance in Customer's Account or Bank has otherwise received full payment from Customer. <br />If Customer asks Bank to amend or cancel an Entry and Customer's request complies with applicable security procedures, Bank will use reasonable <br />efforts to comply with Customer's request prior to transmitting, it to the ACH or debiting or crediting the account of the Receiver for an Chi -Us <br />Entry. However, Bank will not be liable to Customer if Bank is unable to cancel or amend the Entry. Customer agrees to indemnify and hold Bank <br />harmless from and against any and all claims, demands, losses, liabilities and expenses, including reasonable attorneys' fees and costs, resulting <br />from compliance with Customer's cancellation or amendment request <br />If an Entry is returned to Bank through the ACH, Bank will notify Customer no later than the next business day after Bank receives the returned <br />Entry. Bank will have no obligation to retransmit a returned Entry unless Bank is required to do so by the Rules. Unless Bank is required by the <br />Rules to retransmit a returned Entry, Customer must retransmit the Entry to Bank. As an accommodation service to Customer, Bank may reinitiate <br />Entries returned for insufficient or uncollected funds if reinitiation is permitted by the Rules and Customer requests Bank in writing to provide this <br />service. <br />5. INTERNATIONAL ACH TRANSACTIONS MAT71. Customer shall not initiate any IAT Entries without Bank's prior approval. If <br />approved by Bank, the following provisions apply to IAT Entries originated by Customer. <br />"(a) IAT Entries are transmitted by Bank in U.S. dollars and converted to the local currency for receipt in the foreign country at the <br />exchange rate determined by Bank's processor on the date determined by Bank's processor. All risk of fluctuation in the applicable <br />exchange rate is borne by Customer. <br />(b) In the eventof a returned IAT Entry, consumer payments will be credited to Customer at the originated U.S. doll aramount; corporate <br />payments will be credited to Customer at the exchange rate determined by BarWs processor at the time of return <br />(c) In the event of an error in an Entry or duplicate entries, Customer acknowledges and agrees that Customer shall be liable for any and <br />all losses caused by and a direct or indirect result from the error or duplicate Entry. <br />(d) Customer shall originate all International ACH Transactions, as that term in defined in the Rules, with an IAT SEC code and <br />Customer hereby gees to abide by all of the Rules related to LAT Entries. <br />(e) Customer agrees that in the ease of a non -Consumer Account, Customer shall enter into an agreement with the Receiver whereby <br />the Receiver agrees to abide by the Rules in effect from time to time. <br />(f) Customer acknowledges that it has reviewed and understands Rules related to excepdons to the Rules for outbound IAT Entries and <br />Customer understands and agrees that laws, regulations, and rules of the country in which the Receiver is located shall govern the matters <br />listed within that subsection. Customer further acknowledges that Customer understands how such laws, regulations and rules differ <br />from the Rules. <br />(g) IAT Entries must be authorized as provided in the Rules. The form and content of the authorization, including whether such <br />authorization may be oral, electronic, or written, shall be governed by the laws andpayment system rules of the receiving country. <br />(h) Customer hereby indemnifies Bank from and against any and all resulting claims, demands, losses, liabilities, or expenses, including <br />attomeys' fees and costs, resulting directly or indirectly from Customer's origination of an IAT Entry.' <br />6. Settlement-focEntries. Customer agrees to maintain with Bank one or more designated Deposit Accounts during the term of the <br />Agreement (the "Account" or "Accounts") for settlement purposes, as designated in Section I of the Service Schedule. All Entries mast be settled <br />in the Accounts. Customer acknowledges that the Rules provide that payment of an Entry by the RDFT to the Receiver is provisional until receipt <br />by the RDFT of final settlement for such Entry. Customer understands that, if such settlement is not received, the RDFI will be entitled to a refund <br />from the Receiver ofthe amount credited and Customer will not be deemed to have paid the Receiverthe amount of the Entry. Customer also agrees <br />to send all Entries to Bank in an `unbalanced file format". This means Customer will not include any offset or balancing transactions in any of the <br />Entries Customer initiates. If Customer does not send Customer's Pastries in an unbalanced file format, Bank may suspend transmission of <br />17 of 29 <br />P56 <br />
The URL can be used to link to this page
Your browser does not support the video tag.