Exception Item Processing Clause Samples

Exception Item Processing. One day after receipt of items, Fiserv will perform an automated exception item pull for all items identified by Client's account processing system for exception pull (NSF's, holds, large dollars, or other criteria mutually agreed to by Client and Fiserv). (a) Client's account processing servicer will provide an exception item file to Fiserv after posting and updating of customer accounts and on a mutually agreed schedule. (b) Fiserv will either reject or pay exception items in accordance with instructions, either written or oral, from Client's authorized officer(s) or employee(s). [FISERV(R) LOGO] 19 (c) In the event no instructions are received, Fiserv will follow Client's standing orders for exceptions, which will be provided in writing by Client. (d) For items to be returned, Fiserv will: (i) stamp and qualify the items and return them to the Federal Reserve Bank; or (ii) provide other services as agreed by Fiserv and Client.
View SourceView Similar (4)
Exception Item Processing. (i) Exception Item File Transmission (ii) Cycle Sort/Exception Item Pull
View SourceView Similar (2)
Exception Item Processing. Fiserv will either reject or pay items listed on the appropriate report, in accordance with written instructions, by Client's authorized officer or employee. The name of Client's officer or employee giving such instruction shall be noted on the item or on such other record as Fiserv may establish, together with the nature of the instruction. If Client has not instructed Fiserv regarding the disposition of any exception item drawn against Client by the agreed upon time each day, then Fiserv shall return it through the presentment chain to the depository bank or institution. Instructions to Fiserv on disposition of items that are received after the agreed upon deadline or are changed can result in a late charge. Should Fiserv's exception item processing fail to meet the performance standard for exception item processing set forth in Exhibit B - 3, and Client incurs a potential loss due to an error, Client shall use its best efforts to collect the amount in question from its customer (including without limitation, commencing legal action against the customer, obtaining a judgment, and attempting collection efforts based on said judgment) prior to submitting a claim for damages to Fiserv.
View SourceView Similar (2)
Exception Item Processing. Fiserv will either reject or pay items listed on the appropriate report, in accordance with written instructions, by Client's authorized officer or employee. The name of Client's officer or employee giving such instruction shall be noted on the item or on such other record as Fiserv may establish, together with the nature of the instruction. If Client has not instructed Fiserv regarding the disposition of any exception item drawn against Client by the agreed upon time each day, then Fiserv shall return it through the presentment chain to the depository bank or institution. Instructions to Fiserv on disposition of items that are received after the agreed upon deadline or are changed can result in a late charge. Should Fiserv's exception item processing fail to meet the performance standard for exception item processing set forth in Exhibit B-3, and Client incurs a potential loss due to an error, Client shall use its best efforts to collect the amount in question from its customer (including without limitation, commencing legal action against the customer, obtaining a judgment, and attempting collection efforts based on said judgment) prior to submitting a claim for damages to Fiserv. Prior to expending significant time or incurring out of pocket expenses in the collection process, Client shall consult with and obtain the authorization of Fiserv for any such expenditure, and the parties shall give consideration to the amount of potential loss and the likelihood of collection.
View Source
Exception Item Processing. One day after receipt of items, Fiserv will perform an automated exception item pull for all items identified by Client's account processing system for exception pull (NSF's, holds, large dollars, or other criteria mutually agreed to by Client and Fiserv). (a) Client's account processing servicer will provide an exception item file to Fiserv after posting and updating of customer accounts and on a mutually agreed schedule. (b) Fiserv will either reject or pay exception items in accordance with instructions, either written or oral, from Client's authorized officer(s) or employee(s). <PAGE> (c) In the event no instructions are received, Fiserv will follow Client's standing orders for exceptions, which will be provided in writing by Client.
View Source

Related to Exception Item Processing

  • Subprocessing The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.

  • Sub-Processing 10.1 In respect of any Processing of Personal Data performed by a third party on behalf of a Party, that Party shall: (a) carry out adequate due diligence on such third party to ensure that it is capable of providing the level of protection for the Personal Data as is required by the contract, and provide evidence of such due diligence to the other Party where reasonably requested; and (b) ensure that a suitable agreement is in place with the third party as required under applicable Data Protection Legislation.

  • Claims Processing BCBSM will process Provider's Clean Claims submitted in accordance with this Agreement in a timely fashion.

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.