My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2006-035
San-Marcos
>
City Clerk
>
03 Resolutions
>
2000 s
>
2006
>
Res 2006-035
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/2/2006 10:34:15 AM
Creation date
8/2/2006 10:18:33 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Agreement
Number
2006-35
Date
2/21/2006
Volume Book
166
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.
/
364
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).
Show annotations
View images
View plain text
<br />will be deemed received by us when we receive the complete file at the location <br />specified in the User Documentation. <br /> <br />-- <br /> <br />REJECTION OF ENTRIES <br />We may reject any Entry that does not comply with the requirements of this Booklet or <br />the applicable User Documentation, including any ACH processing limits described in the <br />User Documentation, or that we are unable to verify through use of the Security <br />Procedure. We may also reject any Entry that may be returned for any reason under the <br />NACHA Rules or if you have breached your payment obligations for any ACH Service we <br />provide to you. <br /> <br />Notice of rejection will be given to you by telephone. by electronic means, by facsimile or <br />by mail within the time period specified in the User Documentation and will be effective <br />when given. We are not liable for the rejection of any Entry and are not obligated to pay <br />you interest for the period before you receive the notice of rejection. If an Entry is rejected <br />for any reason, it is your responsibility to correct the Entry you intend to resubmit. <br /> <br />REVERSAL OR DELETION <br />We have no obligation to cancel or amend any Entry after we have received it. If you send <br />us a Reversal/Deletion Request and we are able to verify the authenticity of the <br />Reversal/Deletion Request using the Security Procedure, we will make a reasonable effort <br />to act on your Reversal/Deletion Request. We will not be liable to you if such <br />Reversal/Deletion Request is not effected. You agree to indemnify us in connection with <br />any such Reversal/Deletion Request as provided in UCC ~A. Your obligations under this <br />provision will survive the termination of any ACH Service. <br /> <br />, <br /> <br />PROVISIONAL PAYMENTS <br />You agree to be bound by the provision of the NACHA Rules providing that payment of a <br />credit Entry by the Receiving Depository Financial Institution (RDFf) to the Receiver is <br />provisional until the RDFI receives final settlement for the Entry. If final settlement is not <br />received, the RDFI is entitled to a refund from the Receiver of the amount credited. This <br />means that the Receiver will not have been paid. <br /> <br />Our payment of any debit Entry, returned credit Entry or credit Reversal is provisional <br />until we receive final settlement for the Entry or Reversal. If final settlement is not <br />received, we are entitled to a refund and we may charge your account for the amount <br />previously credited. We may delay the availability of any amount credited for a debit <br />Entry or credit Reversal if we believe that there may not be sufficient funds in your <br />account to cover any chargeback or return of the Entry or Reversal. <br /> <br />INCONSISTENCY OF NAME AND NUMBER <br />An RDFI can make payment to a Receiver based solely on the account number, even if the <br />name in the Entry differs from the name on the account. We will send an Entry to an RDFI <br />based solely on the bank identifying number you provide, even if you provide us with a <br />different RDFI name. <br /> <br />.1 <br />
The URL can be used to link to this page
Your browser does not support the video tag.