Reso 2021-3185 - Laserfiche WebLink

Home Browse Search

The DID, combined with the card and account validation rules, is queried against the WEX database for verification and transaction authorization. If valid, the transaction is authorized. The WEX card cannot be electronically activated without entering a valid DID, making the card useless to someone who has found or stolen it and does not know the DID. The authorization process acts as a security measure, and provides a layer of protection against fraudulent activity. 2.34 System must allow for Program Administrator to create an approval path of setting specific card limits higher than Entity established limits. 2.35 System must allow for Program Administrator and/or Cardholder to mark transactions sent to accounting for payment. 2.36 System must be able to send notifications of pending approval(s) based on established approval path. 2.37 System must allow for Program Administrator to lock transaction accounting code data from editing. 2.38 If capable, system must allow for Program Administrator to create templates for card/account set up (i.e. same billing address, TIN, workflow, etc.). The WEX system allows for templates with different functions within the site as well as the ability to utilize "clone" functionality, which acts in the same manner as a template. Cloning functionality exists for card and authorization profile information to leverage like information (address, cost center, TIN, org/department, user defined fields, etc.) associated between card or driver types. • Templated default limits for authorization profile & set-up • Clone function The WEX team lead by an assigned Strategic Relationship Manager and Premium Fleet Services Account Manager will work to set-up and establish these with customer during the initial implementation. For needs that arose after implementation the Premium Fleet Services Account Manager will be able to assist in setting up these functions. 2.39 If capable, system must allow for Users, with multiple roles within a program, (i.e., Cardholder & Program Administrator) to opt to have one login to be able to access all aspects of their accounts (dual role). If yes, provide details on how that functionality works/is implemented. The flexibility of the WEXOnline° module allows for each user's User ID to have one assigned role. However, this requirement can be met by creating a Custom Role with all necessary levels of permissions to support scenarios where a user maybe both a cardholder and Program Administrator or have other roles and responsibilities with a given agency. Another example is when the user is a cardholder who also carries financial responsibilities and also need to access the system for pulling invoices and reporting, and making payments. The module allows for this user's access to be customized to the specifications specific to their job function. 3. DATA COLLECTION AND MANAGEMENT 3.1 System must capture and display transaction data at the following minimum levels: • Cardholder • Approving official • Entity office or unit • Account/billing (available at different levels) MASTER AGREEMENT No. 00819 - FLEET CARD SERVICES PAGE 80 OF 138