Collection Functions Sample Clauses

Collection Functions. (1) receiving, applying and administering collections on the Auto Loans; (2) arranging for and administering repossessions of the Financed Vehicles related to the Auto Loans; (3) disposing of each Financed Vehicle related to a Receivable whether following repossession or otherwise; and (4) filing of insurance claims and performing the duties of the named insured under any VSI Policy with respect to each Auto Loan affected by a repossession or otherwise. Notwithstanding any other provision in this Agreement, the Servicer shall administer collections on Auto Loan at all times in such a manner that each Auto Loan shall remain eligible for coverage under the Insurance Policy. The Servicer, on behalf of the Trustee (and any named insured under the Insurance Policy), shall take such reasonable action as shall be necessary to permit recovery on each Auto Loan under the Insurance Policy and may engage such liquidation agents, skiptracers, remarketers, repossession agents or similar agents as it deems necessary.
Sample 1
AutoNDA by SimpleDocs

Related to Collection Functions

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • Collection Procedures (a) On or before the Closing Date, the Seller and the Purchaser shall have established and shall maintain thereafter the system of collecting and processing Collections of Receivables in accordance with Section 2.02 of the Servicing Agreement. (b) The Seller shall cause all in-store payments to be (i) processed as soon as possible after such payments are received by the Seller but in no event later than the Business Day after such receipt, and (ii) delivered to the Servicer or, if a Daily Payment Event has occurred, deposited in the Collection Account no later than the second Business Day following the date of such receipt. (c) The Seller and the Purchaser shall deliver to the Servicer or, if a Daily Payment Event has occurred, deposit into the Collection Account all Recoveries received by it within two Business Days after the Date of Processing for such Recovery. (d) Any funds held by the Seller representing Collections of Receivables shall, until delivered to the Servicer or deposited in the Collection Account, be held in trust by the Seller on behalf of the Trustee as part of the Trust Estate. (e) The Seller hereby irrevocably waives any right to set off against, or otherwise deduct from, any Collections. (f) The Seller acknowledges that Seller shall not have any right, title or interest in and to any Trust Account.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • General Servicing Procedures Section 6.01

  • Collection Services General 5-1 5.02 Solid Waste Collection 5-1 5.03 Targeted Recyclable Materials Collection 5-3

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

  • Custodial Services The charges and expenses of the custodian appointed by the Trust for custodial services;

  • General Servicing Obligations The Company shall sell any REO Property within two years after its acquisition by the REMIC unless (i) the Company applies for an extension of such two-year period from the Internal Revenue Service pursuant to the REMIC Provisions and Code Section 856(e)(3), in which event such REO Property shall be sold within the applicable extension period, or (ii) the Company obtains for the Purchaser an Opinion of Counsel, addressed to the Purchaser and the Company, to the effect that the holding by the REMIC of such REO Property subsequent to such two year period will not result in the imposition of taxes on "prohibited transactions" as defined in Section 860F of the Code or cause the REMIC to fail to qualify as a REMIC under the REMIC Provisions or comparable provisions of relevant state laws at any time. The Company shall manage, conserve, protect and operate each REO Property for the Purchaser solely for the purpose of its prompt disposition and sale in a manner which does not cause such REO Property to fail to qualify as "foreclosure property" within the meaning of Section 860G(a)(8) or result in the receipt by the REMIC of any "income from non-permitted assets" within the meaning of Section 860F(a)(2)(B) of the Code or any "net income from foreclosure property" which is subject to taxation under Section 860G(a)(1) of the Code. Pursuant to its efforts to sell such REO Property, the Company shall either itself or through an agent selected by the Company protect and conserve such REO Property in the same manner and to such extent as is customary in the locality where such REO Property is located and may, incident to its conservation and protection of the interests of the Purchaser, rent the same, or any part thereof, as the Company deems to be in the best interest of the Company and the Purchaser for the period prior to the sale of such REO Property; provided, however, that any rent received or accrued with respect to such REO Property qualifies as "rents from real property" as defined in Section 856(d) of the Code.

  • Duties and functions 23.2.1 The Independent Engineer shall discharge its duties and functions substantially in accordance with the terms of reference set forth in Schedule 16. 23.2.2 The Independent Engineer shall submit regular periodic reports (at least once every month) to the Authority in respect of its duties and functions set forth in Schedule 16.

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