26-Functionality Checklist, Purchasing Card Services (Group 3), GEN2131264P1.xlsx
XLSX spreadsheet 23 KB Posted
- Attached to
- Master Banking Services
- Solicitation number
- GEN2131264P1
- Issued by
- Broward County, Florida
About this file
This is a Functionality Checklist for Solicitation No. GEN2131264P1, issued by Broward County, Florida, for Purchasing Card Services (Group 3) as part of a Master Banking Services procurement. The checklist requires vendors to indicate whether their proposed purchasing card solution provides specific functionality either out-of-the-box, through configuration, or not at all. Vendors must complete and submit the checklist by the solicitation's closing date to avoid receiving no evaluation points. The checklist covers eight primary sections: General card program capabilities, card program management functions, transaction management features, reporting requirements, security and fraud control measures, technical requirements, technical file format standards, and PeopleSoft integration specifications. Broward County permits vendors to submit proposals for one or multiple banking services across five groups, though vendors must perform all work themselves without subcontracting.
The checklist encompasses comprehensive functional requirements spanning real-time transaction monitoring, merchant category code restrictions, cardholder account management, dispute and chargeback processing, fraud detection capabilities, role-based access controls, and integration with the County's PeopleSoft ERP system. Technical requirements include support for multiple payment card formats (Visa VCF4, MasterCard CDF 2.0 and 3.0, American Express KR1025), secure file transfer protocols (SFTP, AS2, HTTPS), 64-bit server architecture compatibility, and 125-135 GB of storage capacity. The solicitation requires vendors to maintain 24 months of historical transaction data and provide reporting in standard formats such as CSV and Excel. Additional requirements include Enterprise Technology Services Vendor Security Questionnaire compliance and Payment Card Industry Data Security Standard adherence, with consideration given to Small Business Enterprise and County Business Enterprise procurement preferences.
View the file
Other files
Show all 48
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Solicitation No. GEN2131264P1
| Functionality Checklist |
| Solicitation No. GEN2131264P1 |
| Group 3: Purchasing Card Services |
| Indicate if the proposed solution provides the functionality and whether any configuration is required. |
Complete the Functionality Checklist (mark an "X" for applicable answer) and use the comments column to provide any additional explanation that will assist the County in its evaluation. Vendors that fail to submit completed checklist by solicitation’s closing date and time may receive no points (if applicable).
| Section | Functionality | YES | ||||
| (out-of-the-box) | YES | |||||
| (configurable) | Not Available | Vendor Comments | ||||
| SECTION 1: GENERAL | ||||||
| Sample | This is an example line for Vendors showing how to complete this form. | X | X | Notes can be left here. If additional documentation is supplied, use the same numbering scheme to allow for cross-referencing. | ||
| 1.1 | Allow Program Card (P-Card) Administrators the ability to access transactions data in real time for monitoring and reconciliation purposes. | |||||
| 1.2 | Support the assignment of cardholder profiles, including department, division or other County identifiers. | |||||
| 1.3 | Provide the ability to restrict merchant category codes (MCCs) to support program controls. | |||||
| 1.4 | Allow MCC restrictions to be applied to both the cardholder and program level. | |||||
| 1.5 | Allow temporary adjustment to card limits with the ability to automatically revert to standard limits. | |||||
| 1.6 | Allow cardholders to initiate dispute request or inquiries related to transactions. | |||||
| 1.7 | Allow authorized P-Card Administrators to suspend or cancel cards immediately when necessary. | |||||
| SECTION 2: CARD PROGRAM MANAGEMENT | ||||||
| 2.1 | Allow the County P-Card Administrators to create, update, and close cardholder accounts. | |||||
| 2.2 | Support management of card expiration dates and renewal cycles. | |||||
| 2.3 | Support card replacement and reissuance processes for lost, stolen, or damaged cards. | |||||
| 2.4 | Display options for card activation by phone, online, or other available methods. | |||||
| 2.5 | Allow batch card issuance for expired cards. | |||||
| SECTION 3: TRANSACTION MANAGEMENT | ||||||
| 3.1 | Provide real-time transaction monitoring capabilities. | |||||
| 3.2 | Identify declined transactions and provide reason codes. | |||||
| 3.3 | Allow transaction data to be exported for reporting and financial reconciliation. | |||||
| 3.4 | Support dispute and chargeback processes related to card transaction. | |||||
| 3.5 | Provide the ability to flag or block transactions identified as suspicious or outside program guidelines. | |||||
| SECTION 4: REPORTING REQUIREMENTS | ||||||
| 4.1 | Provide detailed transaction reports that include merchant name, transaction amount, date, and merchant category code. | |||||
| 4.2 | Provide reporting tools to support review and monitoring capabilities of card transactions. | |||||
| 4.3 | Provide reports identifying card status, suspected or confirmed fraudulent activity, changes made to cardholder profiles. | |||||
| 4.4 | Allow reports and transaction data to be exported in commonly used formats such as CSV, Excel, or other standard file formats. | |||||
| 4.5 | Maintain access to historical transaction data for a minimum of twenty four (24) months. | |||||
| 4.6 | Provide dashboard or summary reporting tools that allow P-Card Administrators to review program activity, spending trends, and overall card usage. | |||||
| SECTION 5: SECURITY AND FRAUD CONTROL | ||||||
| 5.1 | Provide fraud detection monitoring to identify unusual or potentially unauthorized activity. | |||||
| 5.2 | Provide notification alerts for transactions flagged as potential fraud. | |||||
| 5.3 | Support role-based system permissions to control access to banking platform. | |||||
| 5.4 | Provide row-level security for cardholder visibility and approvals. | |||||
| 5.5 | Provide encryption and masked PAN display for all transaction views and data transmissions. | |||||
| 5.6 | Provide configurable transaction, daily, and cycle spending limits. | |||||
| 5.7 | Provide error reporting for file failures, corruption, and processing anomalies. | |||||
| SECTION 6: TECHNICAL REQUIREMENTS | ||||||
| 6.1 | Provide integration capabilities with the County's ERP System (PeopleSoft) | |||||
| 6.2 | Support automated data transfer between the banking platform and County systems. | |||||
| 6.3 | Support a 64-bit server architecture and Windows People Tools client compatibility. | |||||
| 6.4 | Provide between 125–135 GB of storage for transaction, receipt, and integration files. | |||||
| SECTION 7: TECHNICAL REQUIREMENTS | ||||||
| 7.1 | Support Visa Commercial Format VCF4. | |||||
| 7.2 | Support MasterCard CDF 2.0 flat file format. | |||||
| 7.3 | Support MasterCard CDF 3.0 XML format. | |||||
| 7.4 | Support American Express KR1025 regional format. | |||||
| 7.5 | Include Employee ID, Level 2/3 data, and MCC codes in all transaction files. | |||||
| 7.6 | Support daily or monthly batch file delivery frequency. | |||||
| 7.7 | Provide an FTP/SFTP server for receipt and attachment transfers. | |||||
| 7.8 | Support secure file transfers via SFTP. | |||||
| 7.9 | Support AS2 communication with certificate-based authentication. | |||||
| 7.10 | Support HTTPS, REST, and SOAP integrations via PeopleSoft Integration Broker. | |||||
| SECTION 8: PEOPLESOFT INTEGRATION | ||||||
| 8.1 | Support loading staging files into PeopleSoft via Integration Broker or flat file upload. | |||||
| 8.2 | Support PeopleSoft Application Engines: PO_CCSTMT_WF and PO_CCEXP_WF. | |||||
| 8.3 | Provide voucher-build compatible staging data for Accounts Payable integration. | |||||
| 8.4 | Support staged transaction management including justification fields consistent with PeopleSoft workflow processes. | |||||
| Form Date 7/16/25 |
&10Functionality Checklist &A &P of &N
&P of &N
File details come from the government source that posted it. Updated .