Reso 2021-3185 - Laserfiche WebLink

Home Browse Search

• Entity Program Administrator or alternates (available at different levels) • Participating State (all state entity transactional data, statewide administrative level and compliance review group) 3.2 System must have the ability to view transaction authorization/declines in real time. 3.3 System must post transactions within twenty-four (24) to forty-eight (48) hours of receipt from merchant. 3.4 System must have the ability to capture and display Level 1, Level 2, and Level 3 transaction data as made available from the merchant. 3.5 System must allow for Users to add notes, comments, and additional descriptions to a transaction in a separate field. This field must: • Allow for alpha, numeric, and special characters. • Be searchable • Be reportable • Be accessible to all hierarchies within the system 3.6 System must be able to capture and display merchant Tax Identification Number (TIN) or similar unique identifier. 3.7 System must allow for user to input a minimum of 150 character of Entity defined accounting code structure/segments at the transaction level. 3.8 System must allow for the Purchasing Entity to set requirements for accounting code segments (i.e. mandatory, non -mandatory, etc.) 3.9 System must allow for Purchasing Entity to define, edit, maintain, and upload valid value tables for each accounting code segment. 3.10 System must actively validate accounting segment data against valid value table data as determined by the Purchasing Entity. 3.11 System must allow for Program Administrator to assign, edit, and delete "default" accounting codes for all program hierarchies within the Purchasing Entity. 3.12 System must allow for User to save and edit frequently used accounting codes. 3.13 System must allow for a minimum of 99 accounting code splits per transaction. 3.14 System must allow for User to manually enter tax detail at the transaction level. 3.15 System must allow Program Administrator to download the entire Fleet Card number for use in other systems. 3.16 Participating States and Purchasing Entities have a need to access past transaction detail data in real time for a minimum of thirty-six (36) months throughout the life of the Master Agreement and Participating Addendum. WEX's system maintains past transactional data for a period of seven years (84 months). In the WEXOnline® module, files are retained for a period of 24 months. WEX's Premium Fleet Services Account manager can fulfill requests from NASPO participating entities for transaction details going back to 84 months. In addition, WEX Fleet ClearViewT"' data analytics module has no cap on accessible data, so users of WEX Fleet ClearView"' Essentials and Snap modules, offered as part of WEX's core product MASTER AGREEMENT No. 00819 - FLEET CARD SERVICES PAGE 81 OF 138