Laserfiche WebLink
EXHIBIT G <br />FLEET CARD SERVICE REQUIREMENTS <br />This exhibit details Fleet Card service requirements and Contractor responses to how these <br />requirements will be met as submitted with their bid. <br />1. RESERVED— Identifies card products available in Exhibit A. <br />2. ADMINISTRATION OF ACCOUNTS <br />2.1 System must allow for Program Administrator to setup new accounts online — including ordering <br />and registering cards, establishing User ID and password. <br />2.2 System must allow for Program Administrator to add, edit, or remove single or multiple Product <br />Codes (PC) or Merchant Category Codes (MCC) from multiple card accounts at once. <br />2.3 System must allow for Program Administrator to initiate one-time overrides per transaction. <br />2.4 System must allow for Program Administrator to establish roles, access, and authority levels for <br />all user types (i.e. managers, approvers, cardholders) within the Purchasing Entity. <br />2.5 System must allow for Program Administrator to unlock system access, reset User ID and reset <br />password for any User within the Purchasing Entity. <br />2.6 System must allow for Program Administrator to see changes made to a card profile and who <br />made those changes. <br />2.7 System must allow for system to allow Program Administrator to view cancelled, deactivated and <br />suspended cards within the Entity. <br />2.8 System must allow for Program Administrator to order and issue replacement cards (singular or <br />multiple simultaneously) online. <br />2.9. System must allow for Program Administrators and Cardholders to access statements online. <br />2.10 System must allow for Program Administrators and Cardholders to mark accounts for paper or <br />paperless statement delivery. <br />2.11 System must notify Program Administrators and Cardholders of statement availability. <br />2.12 System must allow for Program Administrator and Cardholders to check status of cards and view <br />account information including but not limited to: <br />• balances <br />• limits <br />• charges <br />• declined transactions <br />• spend history <br />• default accounting codes <br />• demographics <br />2.13 System must allow for the Program Administrator to choose the billing cycle close date for the <br />Purchasing Entity. The billing cycle date will be established at account implementation and will <br />be set for the Purchasing Entities' agreement period. <br />MASTER AGREEMENT No. 00819 — FLEET CARD SERVICES PAGE 73 OF 138 <br />