The file's text, extracted by GovTribe without its formatting.
DEMONSTRATION SCRIPT
Master Banking Services Group 3: Purchasing Card Services
Vendor Instructions: Vendors determined to be both responsive and responsible to the solicitation’s requirements and shortlisted (if applicable), are required to demonstrate the below features of its offered solution (including any out-of-box, configurable, and customizable features). All Vendors will have equal time for demonstrations.
Demonstration Time: One (1) hour(s) (script and time subject to change prior to Demonstration date). Questions and Answer time is unlimited.
Technical Review Team (TRT) Instructions: During the Demonstration Meeting, each TRT member will place a mark (x) in the applicable column, along with a comment (if needed), for each criterion based on the vendor’s demonstration.
| No. |
| Functionality Checklist Item No. |
| Criteria |
| Demonstrated |
| Not Demonstrated |
| Comments |
| 1 | |
| 1.1 | |
| Demonstrate to access transactions data in real time for monitoring and reconciliation purposes. | |
| ☐ | ☐ |
| 2 | |
| 1.2 | |
| Demonstrate the assignment of cardholder profiles, including department, division, or other County identifiers. | |
| ☐ | ☐ |
| 3 | |
| 1.3 | |
| Demonstrate restriction of merchant category codes to support program controls. | |
| ☐ | ☐ |
| 4 | |
| 1.4 | |
| Demonstrate how merchant category codes can be applied to both the cardholder and program level. | |
| ☐ | ☐ |
| 5 | |
| 1.5 | |
| Demonstrate temporary adjustment to card limits with the ability to automatically revert to standard limits. | |
| ☐ | ☐ |
| 6 | |
| 1.6 | |
| Demonstrate the initiation of dispute request or inquiries related to transactions. | |
| ☐ | ☐ |
| 7 | |
| 1.7 | |
| Demonstrate to suspend or cancel cards immediately when necessary. | |
| ☐ | ☐ |
| 8 | |
| 2.1 | |
| Demonstrate how to create, update, and close cardholder accounts | |
| ☐ | ☐ |
| 9 | |
| 2.2 | |
| Demonstrate the management of card expiration date and renewal cycles. | |
| ☐ | ☐ |
| 10 | |
| 2.3 | |
| Demonstrate card replacement and reissuance processes for lost, stolen, or damage cards. | |
| ☐ | ☐ |
| 11 | |
| 2.4 | |
| Display options for card activation by phone, online, or other available methods. | |
| ☐ | ☐ |
| 12 | |
| 2.5 | |
| Demonstrate the process for batch card issuance for expired cards. | |
| ☐ | ☐ |
| 13 | |
| 3.1 | |
| Demonstrate real-time monitoring Capabilities. | |
| ☐ | ☐ |
| 14 | |
| 3.2 | |
| Demonstrate identification of declined transactions and reason codes. | |
| ☐ | ☐ |
| 15 | |
| 3.3 | |
| Demonstrate how transaction date is exported for reporting and financial reconciliation. | |
| ☐ | ☐ |
| 16 | |
| 3.4 | |
| Demonstrate dispute and chargeback processed related to card transaction. | |
| ☐ | ☐ |
| 17 | |
| 3.5 | |
| Demonstrate to flag or block transactions identified as suspicious or outside program guidelines. | |
| ☐ | ☐ |
| 18 | |
| 4.1 | |
| Display a detailed transaction report that includes merchant name, transaction amount, date, and merchant code category. | |
| ☐ | ☐ |
| 19 | |
| 4.2 | |
| Demonstrate reporting tools to support review and monitoring capabilities of card transactions.. | |
| ☐ | ☐ |
| 20 | |
| 4.3 | |
| Display reports identifying card status, suspected or confirmed fraudulent activity, changes made to cardholder profiles. | |
| ☐ | ☐ |
| 21 | |
| 4.4 | |
| Demonstrate reports and transaction data to be exported in commonly used formats such as CSV, Excel, or other standard formats. | |
| ☐ | ☐ |
| 22 | |
| 4.5 | |
| Show access to historical transaction data for a minimum of twenty-four (24) months. | |
| ☐ | ☐ |
| 23 | |
| 4.6 | |
| Demonstrate dashboard or summary reporting tools that allow P-Card Administrators to review program activity, spending trends, and overall card usage. | |
| ☐ | ☐ |
| 24 | |
| 5.1 | |
| Demonstrate fraud detection monitoring to identify unusual or potentially unauthorized activity. | |
| ☐ | ☐ |
| 25 | |
| 5.2 | |
| Demonstrate notification alerts for transactions flagged as potential fraud. | |
| ☐ | ☐ |
| 26 | |
| 5.3 | |
| Demonstrate role-based system permissions to control access to banking platform. | |
| ☐ | ☐ |
| 27 |
| 5.4 |
| Demonstrate row-level security for cardholder visibility and approvals. |
| 28 | |
| 5.5 | |
| Demonstrate encryption and masked PAN display for all transaction views and data transmissions. | |
| ☐ | ☐ |
| 29 | |
| 5.6 | |
| Demonstrate configurable transaction, daily, and cycle spending limits. | |
| ☐ | ☐ |
| 10 | |
| 5.7 | |
| Demonstrate error reporting for file failures, corruption, and processing anomalies. | |
| ☐ | ☐ |
Form Date 7/15/25 Page 2 of 2