Exhibit_A_-_Requirements_Fit_Form.xlsx
XLSX spreadsheet 50 KB Posted
- Attached to
- RFQ: Cloud-Based Enterprise Resource Planning (ERP) System and Implementation Services State and local contract opportunity
- Solicitation number
- 2026-RFQ-056
- Issued by
- North Carolina
About this file
This is a Requirements Fit Form (Exhibit A) for the Town of Mooresville, North Carolina's cloud-based Enterprise Resource Planning (ERP) system procurement (RFQ 2026-RFQ-056). The Town seeks to replace its current platform with a centralized ERP solution to support finance, human resources, payroll, utility billing, parks and recreation, and financial planning operations. Vendors must respond to 428 functional requirements organized across eight process areas: Budget, Grants & Financial Reporting (41 requirements); Departmental Operations & Point-of-Sale (102 requirements); Finance & Accounting (57 requirements); Legal/Procurement (12 requirements); Procurement (33 requirements); Utility Billing (78 requirements); Human Resources (62 requirements); and Information Technology (43 requirements). For each requirement, vendors must select a fit code from the following options: Full Fit Standard (FS), Full Fit with Configuration (FC), Full Fit with Platform Scripting/Customization (FD), Add-On with Pre-built Integration (PI), Add-On with Custom Integration (CI), Partial Fit (PF), or Not Fulfilled (NF). Vendors may provide clarifying comments identifying specific modules, partner solutions, or explain limitations in the accompanying comments column.
Of the 428 total requirements, 362 are designated "Must Have," 43 are "Should Have," 21 are "Could Have," and 2 are "Will Not Have." The solution must be delivered as a cloud-native SaaS platform with no on-premises infrastructure requirements, include SOC 2 Type II certification, support SAML-based Single Sign-On integration with Azure Active Directory, enforce multi-factor authentication, and provide comprehensive audit logging. The Town is open to best-of-breed solutions with third-party add-ons and integrations provided they deliver a cohesive integrated experience. Key functional areas include real-time budget-to-actual reporting, capital and long-range planning, configurable revenue forecasting, comprehensive accounts payable and receivable workflows, grants management, fixed asset tracking, utility billing with mobile field operations, comprehensive HR and payroll functionality, and advanced reporting and analytics capabilities without reliance on spreadsheets.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| RFQ:_Cloud-Based_Enterprise_Resource_Planning_(ERP)_System_and_Implementation_Services_(Addendum_#3_Revision).pdf | ||
| Town_of_Mooresville_-_ERP_Pre-Proposal_Presentation.pdf | ||
| Exhibit_B_-_Pricing_Proposal_Form.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Vendor Instructions
| EXHIBIT A — REQUIREMENTS FIT FORM | |
| Town of Mooresville, North Carolina | ERP System Procurement | 2026-RFQ-056 | |
| Instructions to Vendors | |
| Vendors must complete the Requirements tab by responding to each of the 428 functional requirements. For each requirement, select the Fit Code from the dropdown in Column F. Use the Comments column (Column G) to provide clarifying notes, identify specific modules or partner solutions, or explain limitations. Incomplete submissions will result in scoring deductions during evaluation. | |
| Fit Code Reference | |
| FS | Full Fit Standard — Requirement is fully satisfied through standard out-of-the-box ERP functionality. |
| FC | Full Fit with Configuration — Requirement is fully satisfied through moderate to complex system configuration, but without custom code or scripting. |
| FD | Full Fit with Platform Scripting / Customization — Requirement will be satisfied through scripting or coding within the ERP's native development platform. |
| PI | Add-On with Pre-built Integration — Requirement is fully satisfied through a proven third-party solution with a pre-built, certified integration. |
| CI | Add-On with Custom Integration — Requirement will be satisfied through a third-party solution requiring custom integration via iPaaS or custom development. |
| PF | Partial Fit — Requirement is partially satisfied but requires workarounds, configuration, or uncertified third-party solutions. |
| NF | Not Fulfilled — Requirement cannot be met with current product capabilities, marketplace solutions, or planned releases. |
| Vendor Information | |
| Vendor / Company Name: | |
| ERP Product Name: | |
| Product Version: | |
| Prepared By (Name): | |
| Prepared By (Title): | |
| Date Completed: |
Requirements
| EXHIBIT A — REQUIREMENTS FIT FORM | Town of Mooresville ERP Procurement | 2026-RFQ-056 | ||||||
| Req # | Process Area | Topic / Category | Requirement | Priority | Fit Code ▼ | Vendor Comments |
| BUDGET, GRANTS, & FINANCIAL REPORTING | ||||||
| 1 | Budget, Grants, & Financial Reporting | Budget Adjustments & Amendments | System supports formal budget amendment workflows, including documentation and approval tracking. | Must Have | ||
| 2 | Budget, Grants, & Financial Reporting | Budget Adjustments & Amendments | System supports amendment workflows that align with governing board approval requirements. | Must Have | ||
| 3 | Budget, Grants, & Financial Reporting | Budget Adjustments & Amendments | System clearly distinguishes between budget transfers and budget amendments while maintaining consistent governance controls. | Must Have | ||
| 4 | Budget, Grants, & Financial Reporting | Budget Development & Data Management | System serves as the system of record for budget data, eliminating reliance on spreadsheets for core budgeting activities. | Must Have | ||
| 5 | Budget, Grants, & Financial Reporting | Budget Development & Data Management | System supports budget versioning and comparison (e.g., requested vs. recommended vs. adopted). | Must Have | ||
| 6 | Budget, Grants, & Financial Reporting | Budget Development & Data Management | System provides data validation and error checking during budget entry and consolidation. | Must Have | ||
| 7 | Budget, Grants, & Financial Reporting | Budget Governance & Workflow | System supports an end‑to‑end budget lifecycle from initial request through draft, review, adoption, and final approval with clear status tracking. | Must Have | ||
| 8 | Budget, Grants, & Financial Reporting | Budget Governance & Workflow | System provides configurable, role‑based workflows for budget submissions, reviews, approvals, rejections, and revisions. | Must Have | ||
| 9 | Budget, Grants, & Financial Reporting | Budget Governance & Workflow | System maintains a complete audit trail of budget changes, approvals, and decision history. | Must Have | ||
| 10 | Budget, Grants, & Financial Reporting | Budget Governance & Workflow | System supports role‑based budget entry and approval responsibilities (e.g., department head, administrator, finance). | Must Have | ||
| 11 | Budget, Grants, & Financial Reporting | Budget Governance & Workflow | System automatically notifies users of budget approval, denial, or revision requests within the system. | Must Have | ||
| 12 | Budget, Grants, & Financial Reporting | Budget Governance & Workflow | Budget Entry Approval Workflow at Department level, including manager, director, asst. town manager | Must Have | ||
| 13 | Budget, Grants, & Financial Reporting | Budget Monitoring & Controls | System provides real‑time budget‑to‑actual reporting, including actuals, encumbrances, and remaining budget. | Must Have | ||
| 14 | Budget, Grants, & Financial Reporting | Budget Monitoring & Controls | System clearly reflects commitments and encumbrances when calculating available budget. | Must Have | ||
| 15 | Budget, Grants, & Financial Reporting | Budget Monitoring & Controls | System supports configurable alerts when spending approaches or exceeds defined budget thresholds. | Must Have | ||
| 16 | Budget, Grants, & Financial Reporting | Capital & Long‑Range Planning | System supports capital budgeting and planning aligned with the operating budget. | Must Have | ||
| 17 | Budget, Grants, & Financial Reporting | Capital & Long‑Range Planning | System supports multi‑year financial forecasting across operating and capital budgets. | Must Have | ||
| 18 | Budget, Grants, & Financial Reporting | Capital & Long‑Range Planning | System allows shared assumptions and data between annual budgets, CIP, and long‑range financial plans. | Must Have | ||
| 19 | Budget, Grants, & Financial Reporting | Integration & Data Exchange | System supports integration with external tools used for budget publication, agenda management, and reporting. | Must Have | ||
| 20 | Budget, Grants, & Financial Reporting | Integration & Data Exchange | System supports automated, scheduled data exchange to minimize manual file handling. | Must Have | ||
| 21 | Budget, Grants, & Financial Reporting | Internal Service Funds & Allocations | System supports budgeting and forecasting for internal service funds (e.g., Fleet, IT). | Must Have | ||
| 22 | Budget, Grants, & Financial Reporting | Internal Service Funds & Allocations | System supports allocation of shared costs and internal service charges across departments and funds. | Must Have | ||
| 23 | Budget, Grants, & Financial Reporting | New Initiatives & Transformational Requests | System allows departments to classify budget requests (e.g., base vs. new/transformational initiatives). | Must Have | ||
| 24 | Budget, Grants, & Financial Reporting | New Initiatives & Transformational Requests | System requires structured justification and funding source identification for new or transformational budget requests. | Must Have | ||
| 25 | Budget, Grants, & Financial Reporting | New Initiatives & Transformational Requests | System supports prioritization and ranking of new initiatives for leadership review. | Should Have | ||
| 26 | Budget, Grants, & Financial Reporting | Purchasing & Pre‑Encumbrance Controls | System displays available budget prior to purchase order or requisition submission. | Must Have | ||
| 27 | Budget, Grants, & Financial Reporting | Purchasing & Pre‑Encumbrance Controls | System enforces budget controls during requisition and purchase order processing. | Must Have | ||
| 28 | Budget, Grants, & Financial Reporting | Reporting & Decision Support | System provides role‑based dashboards showing budget status, percent spent, and remaining funds for managers. | Must Have | ||
| 29 | Budget, Grants, & Financial Reporting | Reporting & Decision Support | System provides dashboards for leadership and governing boards, including operating budgets and capital project status. | Must Have | ||
| 30 | Budget, Grants, & Financial Reporting | Reporting & Decision Support | System allows users to create and run ad‑hoc budget and financial reports without reliance on spreadsheets. | Must Have | ||
| 31 | Budget, Grants, & Financial Reporting | Reporting & Decision Support | Ability to create the PAFR | Should Have | ||
| 32 | Budget, Grants, & Financial Reporting | Reporting & Decision Support | Access to PAFR Data Points | Must Have | ||
| 33 | Budget, Grants, & Financial Reporting | Reporting & Decision Support | System tracks budget KPIs and strategic goals during budget entry | Must Have | ||
| 34 | Budget, Grants, & Financial Reporting | Revenue Forecasting | System supports configurable revenue forecasting models using drivers, assumptions, and trend analysis. | Must Have | ||
| 35 | Budget, Grants, & Financial Reporting | Revenue Forecasting | System supports multiple revenue forecast scenarios and comparisons. | Must Have | ||
| 36 | Budget, Grants, & Financial Reporting | Salary & Personnel Forecasting | System supports detailed personnel budgeting, including positions, vacancies, and projected compensation changes. | Must Have | ||
| 37 | Budget, Grants, & Financial Reporting | Salary & Personnel Forecasting | System supports “what‑if” and scenario analysis for salary and personnel cost projections. | Must Have | ||
| 38 | Budget, Grants, & Financial Reporting | Salary & Personnel Forecasting | System allows personnel costs to be budgeted and forecasted in a way that aligns with actual payroll structure. | Could Have | ||
| 39 | Budget, Grants, & Financial Reporting | User Experience & Security | System supports role‑based security and access aligned with user responsibilities. | Must Have | ||
| 40 | Budget, Grants, & Financial Reporting | User Experience & Security | System provides a consistent user experience tailored by role (e.g., department user, manager, finance). | Must Have | ||
| 41 | Budget, Grants, & Financial Reporting | User Experience & Security | System provides an intuitive, easy‑to‑navigate interface suitable for infrequent and non‑financial users. | Must Have | ||
| DEPARTMENTAL OPERATIONS & POS | ||||||
| 42 | Departmental Operations & POS | Budget Management | Track expenses by program, event, or initiative within departmental budgets. | Must Have | ||
| 43 | Departmental Operations & POS | Budget Management | Provide visibility into encumbrances, commitments, and remaining budget balances. | Must Have | ||
| 44 | Departmental Operations & POS | Budget Management | Provide budget-versus-actual spending reports by program or event. | Must Have | ||
| 45 | Departmental Operations & POS | Customer Experience | Track citizen inquiries and service requests in a centralized system. | Must Have | ||
| 46 | Departmental Operations & POS | Customer Experience | Route citizen service requests to the appropriate department. | Must Have | ||
| 47 | Departmental Operations & POS | Customer Experience | Maintain status tracking and history for each citizen inquiry. | Must Have | ||
| 48 | Departmental Operations & POS | Customer Experience | Provide customer service staff access to account information through ERP integration. | Must Have | ||
| 49 | Departmental Operations & POS | Customer Experience | Deliver customer service training modules to staff. | Could Have | ||
| 50 | Departmental Operations & POS | Customer Experience | Track completion of training modules by employee. | Could Have | ||
| 51 | Departmental Operations & POS | Customer Experience / CRM | Support integration with CRM platforms used for citizen and customer engagement. | Must Have | ||
| 52 | Departmental Operations & POS | Customer Experience / CRM | Integrate CRM data with ERP where a financial impact exists. | Must Have | ||
| 53 | Departmental Operations & POS | Customer Experience / CRM | Integrate with work order systems where applicable. | Must Have | ||
| 54 | Departmental Operations & POS | Events & Concessions | Support mobile POS for merchandise and concessions. | Must Have | ||
| 55 | Departmental Operations & POS | Events & Concessions | Support inventory tracking for event sales. | Will Not Have | ||
| 56 | Departmental Operations & POS | Events & Concessions | Integrate event revenue into ERP automatically. | Must Have | ||
| 57 | Departmental Operations & POS | Events & Concessions | Support sales tax reporting by event. | Could Have | ||
| 58 | Departmental Operations & POS | Events & Concessions | Provide event profitability reporting. | Could Have | ||
| 59 | Departmental Operations & POS | Financial Integration & Reconciliation | Support configurable GL account mapping. | Must Have | ||
| 60 | Departmental Operations & POS | Financial Integration & Reconciliation | Support program-level revenue dashboards. | Must Have | ||
| 61 | Departmental Operations & POS | Financial Integration & Reconciliation | Provide accounting staff access to summarized POS data. | Must Have | ||
| 62 | Departmental Operations & POS | Financial Integration & Reconciliation | Support automated reconciliation to bank deposits. | Must Have | ||
| 63 | Departmental Operations & POS | Financial Integration & Reconciliation | Provide audit-ready transaction traceability. | Must Have | ||
| 64 | Departmental Operations & POS | Financial Integration & Reconciliation | Support configurable revenue recognition rules. | Must Have | ||
| 65 | Departmental Operations & POS | Financial Integration & Reconciliation | Provide variance reporting between POS and ERP. | Must Have | ||
| 66 | Departmental Operations & POS | Financial Management | Allow summarized revenue deposits from external ticketing platforms to be recorded against events. | Must Have | ||
| 67 | Departmental Operations & POS | Financial Management | Support reconciliation of ticketing settlements received from ticketing vendors. | Must Have | ||
| 68 | Departmental Operations & POS | Golf Operations | Integrate golf POS (Jonas) system revenue with ERP. | Must Have | ||
| 69 | Departmental Operations & POS | Golf Operations | Support tee time booking integration with financial reporting. | Must Have | ||
| 70 | Departmental Operations & POS | Golf Operations | Provide tournament and outing revenue tracking. | Must Have | ||
| 71 | Departmental Operations & POS | Library Operations | Support integration with a specialized Integrated Library System (ILS) for managing library materials, patron accounts, and circulation activity outside the ERP. | Will Not Have | ||
| 72 | Departmental Operations & POS | Library Operations | Support recording of library-related revenue without storing patron-level or item-level PII. | Must Have | ||
| 73 | Departmental Operations & POS | Library Operations | Support multiple revenue codes for library transactions while retaining detailed item and patron data within the ILS. | Could Have | ||
| 74 | Departmental Operations & POS | Library Operations | Support cashiering at multiple library locations, including cash and credit card transactions, with centralized financial posting. | Must Have | ||
| 75 | Departmental Operations & POS | Library Operations | Support batch settlement of cashiering transactions for daily balancing and financial posting. | Must Have | ||
| 76 | Departmental Operations & POS | Library Operations | Support credit card payments across multiple channels (front desk, phone, online, kiosks, copiers/CBAs) with consolidated posting to a single financial system of record. | Must Have | ||
| 77 | Departmental Operations & POS | Library Operations | Support integration with third-party payment processors for online library fee payments. | Should Have | ||
| 78 | Departmental Operations & POS | Library Operations | Support replacement of legacy server-hosted e-commerce solutions with a modern, centrally managed payment approach. | Should Have | ||
| 79 | Departmental Operations & POS | Library Operations | Support manual payment entry workflows for payments collected outside of integrated POS, with clear distinction from fully integrated POS transactions. | Must Have | ||
| 80 | Departmental Operations & POS | Library Operations | Support room rental revenue processing and supporting self-service booking. | Should Have | ||
| 81 | Departmental Operations & POS | Library Operations | Allow room rental payments to be recorded independently of the library materials system. | Must Have | ||
| 82 | Departmental Operations & POS | Library Operations | Support blanket purchase orders for library vendors with draw-down against a single encumbrance as invoices are received. | Must Have | ||
| 83 | Departmental Operations & POS | Library Operations | Support invoice processing through an integrated document management and workflow tool. | Must Have | ||
| 84 | Departmental Operations & POS | Library Operations | Allow the Library to maintain a single high-level materials budget in the general ledger while detailed collection-level tracking remains within the Library system. | Must Have | ||
| 85 | Departmental Operations & POS | Library Operations | Support reporting by description or tag (e.g., adult fiction, youth services, local history) without requiring formal budget allocation codes. | Must Have | ||
| 86 | Departmental Operations & POS | Library Operations | Support standardized, selectable categories or attributes for internal reporting where feasible. | Must Have | ||
| 87 | Departmental Operations & POS | Library Operations | Support P-card transaction allocation and coding workflows, allowing Library staff to assign budget codes after charges are imported from the credit card provider. | Must Have | ||
| 88 | Departmental Operations & POS | Library Operations | Support monthly and on-demand reporting for Library financial activity, including expenditures, encumbrances, and remaining balances. | Must Have | ||
| 89 | Departmental Operations & POS | Library Operations | Support stable, reliable cashiering functionality with minimal system resets, payment failures, and hardware/software disconnects. | Must Have | ||
| 90 | Departmental Operations & POS | Library Operations | Support fixed asset tracking at the Town level with departent (e.g. Library) participation in periodic verification. | Must Have | ||
| 91 | Departmental Operations & POS | Merchant Services & Payments | Support transaction-level revenue posting. | Must Have | ||
| 92 | Departmental Operations & POS | Merchant Services & Payments | Support separate recording of gross revenue and merchant fees at the transaction level. | Must Have | ||
| 93 | Departmental Operations & POS | Merchant Services & Payments | Support integration with municipal-grade merchant processors. | Must Have | ||
| 94 | Departmental Operations & POS | Merchant Services & Payments | Support credit card dispute tracking. | Must Have | ||
| 95 | Departmental Operations & POS | Merchant Services & Payments | Support automated refund processing with audit trail. | Must Have | ||
| 96 | Departmental Operations & POS | Merchant Services & Payments | Generate daily settlement reports aligned to bank deposits. | Must Have | ||
| 97 | Departmental Operations & POS | Merchant Services & Payments | Support consolidated merchant reporting across departments. | Must Have | ||
| 98 | Departmental Operations & POS | Merchant Services & Payments | Support PCI compliance requirements. | Must Have | ||
| 99 | Departmental Operations & POS | Merchant Services & Payments | Support sales tax tracking by item category. | Must Have | ||
| 100 | Departmental Operations & POS | Parks & Recreation | Support online account creation with household and guardian relationships. | Must Have | ||
| 101 | Departmental Operations & POS | Parks & Recreation | Support residency validation using GIS or address verification logic. | Must Have | ||
| 102 | Departmental Operations & POS | Parks & Recreation | Support resident and non-resident pricing structures. | Must Have | ||
| 103 | Departmental Operations & POS | Parks & Recreation | Support configurable late registration fees. | Should Have | ||
| 104 | Departmental Operations & POS | Parks & Recreation | Support multi-sibling discounts and scholarship pricing rules. | Must Have | ||
| 105 | Departmental Operations & POS | Parks & Recreation | Support automated duplicate account detection with override capability. | Should Have | ||
| 106 | Departmental Operations & POS | Parks & Recreation | Support configurable eligibility rules (age, residency, program limits). | Must Have | ||
| 107 | Departmental Operations & POS | Parks & Recreation | Provide a real-time public facility availability calendar. | Must Have | ||
| 108 | Departmental Operations & POS | Parks & Recreation | Support public shelter and facility rental booking workflows. | Must Have | ||
| 109 | Departmental Operations & POS | Parks & Recreation | Support configurable approval routing for special rentals. | Must Have | ||
| 110 | Departmental Operations & POS | Parks & Recreation | Support automated waitlist management. | Must Have | ||
| 111 | Departmental Operations & POS | Parks & Recreation | Support SMS notifications for urgent alerts. | Should Have | ||
| 112 | Departmental Operations & POS | Parks & Recreation | Support automated email communications for season launches. | Must Have | ||
| 113 | Departmental Operations & POS | Parks & Recreation | Support coach scheduling constraints and team assignment logic. | Should Have | ||
| 114 | Departmental Operations & POS | Parks & Recreation | Support tournament bracket scheduling. | Could Have | ||
| 115 | Departmental Operations & POS | Parks & Recreation | Support policy acknowledgment prompts during checkout. | Should Have | ||
| 116 | Departmental Operations & POS | Parks & Recreation | Support electronic capture of refund policy acknowledgments. | Should Have | ||
| 117 | Departmental Operations & POS | Parks & Recreation | Support integrated medical form capture for accredited camps. | Should Have | ||
| 118 | Departmental Operations & POS | Parks & Recreation | Support API integration with third-party medical platforms (e.g., EPACT). | Must Have | ||
| 119 | Departmental Operations & POS | Parks & Recreation | Allow secure access for third-party program partners. | Could Have | ||
| 120 | Departmental Operations & POS | Parks & Recreation | Provide program-level revenue and participation reporting. | Must Have | ||
| 121 | Departmental Operations & POS | Parks & Recreation | Provide exportable attendance and roster reports. | Must Have | ||
| 122 | Departmental Operations & POS | Parks & Recreation | Manage reservable facilities using a calendar-based booking interface showing real-time availability. | Must Have | ||
| 123 | Departmental Operations & POS | Parks & Recreation | Prevent double-booking by displaying existing reservations across rooms and spaces. | Should Have | ||
| 124 | Departmental Operations & POS | Parks & Recreation | Allow staff to create and manage event reservations, including setup details and scheduling. | Must Have | ||
| 125 | Departmental Operations & POS | Events & Concessions | Maintain inventory of reservable event equipment, including linens, chairs, lighting, and decor. | Could Have | ||
| 126 | Departmental Operations & POS | Events & Concessions | Automatically reserve inventory items when assigned to an event booking. | Could Have | ||
| 127 | Departmental Operations & POS | Events & Concessions | Display remaining available quantities of inventory items during booking. | Could Have | ||
| 128 | Departmental Operations & POS | Events & Concessions | Support reporting on available, reserved, and in-use inventory items. | Could Have | ||
| 129 | Departmental Operations & POS | Events & Concessions | Generate invoices for facility rentals and reservable inventory items. | Could Have | ||
| 130 | Departmental Operations & POS | Events & Concessions | Record payments for event bookings, including cash, check, and credit card transactions. | Should Have | ||
| 131 | Departmental Operations & POS | Permits & Licensing | Support configurable multi-department approval workflows for permits | Must Have | ||
| 132 | Departmental Operations & POS | Permits & Licensing | Support conditional logic-based application forms. | Must Have | ||
| 133 | Departmental Operations & POS | Permits & Licensing | Provide a public-facing permit application portal. | Must Have | ||
| 134 | Departmental Operations & POS | Permits & Licensing | Support integrated online payment processing. | Must Have | ||
| 135 | Departmental Operations & POS | Permits & Licensing | Provide automated status updates to applicants. | Must Have | ||
| 136 | Departmental Operations & POS | Permits & Licensing | Support role-based review and comment tracking. | Must Have | ||
| 137 | Departmental Operations & POS | Permits & Licensing | Maintain historical permit data for compliance reporting. | Must Have | ||
| 138 | Departmental Operations & POS | Permits & Licensing | Provide dashboard reporting on permit volume and revenue. | Must Have | ||
| 139 | Departmental Operations & POS | System Integration | Integrate permitting, ticketing, and payment systems with the ERP to automatically transmit financial transactions. | Must Have | ||
| 140 | Departmental Operations & POS | System Integration | Support automated posting of revenue transactions from external applications into the financial system. | Must Have | ||
| 141 | Departmental Operations & POS | System Integration | Support elimination of manual re-entry of payment transactions currently keyed into the financial system. | Must Have | ||
| 142 | Departmental Operations & POS | System Integration | Support integration with external payment processors, including credit card platforms. | Must Have | ||
| 143 | Departmental Operations & POS | Vendor Management | Maintain vendor documentation including W-9 forms, insurance certificates, and contracts. | Must Have | ||
| FINANCE & ACCOUNTING | ||||||
| 144 | Finance & Accounting | Accounts Payable | System supports electronic invoice intake from multiple sources, including shared email inboxes and scanned documents. | Must Have | ||
| 145 | Finance & Accounting | Accounts Payable | System supports OCR to automatically extract invoice data such as vendor, invoice number, amount, and sales tax. | Must Have | ||
| 146 | Finance & Accounting | Accounts Payable | System provides configurable approval workflows based on role, dollar amount, department, and transaction type. | Must Have | ||
| 147 | Finance & Accounting | Accounts Payable | System provides real‑time visibility into invoice approval status and approval queues, including delegated or administrative views. | Must Have | ||
| 148 | Finance & Accounting | Accounts Payable | System supports batch‑level invoice approvals with the ability to drill into individual transactions when needed. | Must Have | ||
| 149 | Finance & Accounting | Accounts Payable | System integrates purchase order receiving into the invoice workflow to prevent missed receiving steps. | Must Have | ||
| 150 | Finance & Accounting | Accounts Payable | System detects potential duplicate invoices using invoice number, vendor, amount, date, and other matching logic. | Must Have | ||
| 151 | Finance & Accounting | Accounts Payable | System allows invoices and supporting documents to be attached to AP transactions and retained through payment. | Must Have | ||
| 152 | Finance & Accounting | Accounts Payable | System displays payment details (check/EFT number, date, method) directly on the invoice record. | Must Have | ||
| 153 | Finance & Accounting | Accounts Receivable & Billing | System supports billing and invoicing for revenue streams that do not have dedicated POS systems. | Must Have | ||
| 154 | Finance & Accounting | Accounts Receivable & Billing | System supports recurring invoices and billing schedules. | Must Have | ||
| 155 | Finance & Accounting | Accounts Receivable & Billing | System supports integration with multiple POS systems via APIs or standardized imports. | Must Have | ||
| 156 | Finance & Accounting | Accounts Receivable & Billing | System retains transaction‑level detail or provide traceable references to source POS systems. | Must Have | ||
| 157 | Finance & Accounting | Accounts Receivable & Billing | System supports separate entities with independent reporting and controlled consolidation. | Must Have | ||
| 158 | Finance & Accounting | Controls, Compliance, & Security | System enforces North Carolina pre‑audit requirements prior to financial commitments. | Must Have | ||
| 159 | Finance & Accounting | Controls, Compliance, & Security | System supports granular, role‑based security to enforce segregation of duties. | Must Have | ||
| 160 | Finance & Accounting | Controls, Compliance, & Security | System restricts access to sensitive vendor data such as W‑9s and banking information. | Must Have | ||
| 161 | Finance & Accounting | Controls, Compliance, & Security | System provides comprehensive audit logs for financial transactions and approvals. | Must Have | ||
| 162 | Finance & Accounting | Financial Reporting & Analytics | System provides standard government financial reports including balance sheet, trial balance, and budget‑to‑actual reports. | Must Have | ||
| 163 | Finance & Accounting | Financial Reporting & Analytics | System supports year‑over‑year, period‑over‑period, and growth/variance analysis within the system without reliance on Excel. | Must Have | ||
| 164 | Finance & Accounting | Financial Reporting & Analytics | System allows finance users to build ad hoc reports without technical or vendor assistance. | Must Have | ||
| 165 | Finance & Accounting | Financial Reporting & Analytics | Provides tools to assist with balance sheet reconciliations, including filtering, tagging, and identifying balance‑carrying transactions. | Must Have | ||
| 166 | Finance & Accounting | Financial Reporting & Analytics | Provides role‑based dashboards for finance users showing key metrics and statuses. | Must Have | ||
| 167 | Finance & Accounting | Financial Reporting & Analytics | System supports the generation of ACFR‑level financial statements at any point throughout the fiscal year | Should Have | ||
| 168 | Finance & Accounting | Fixed Assets | System supports tracking of capital assets including acquisition, depreciation, and disposal. | Must Have | ||
| 169 | Finance & Accounting | Fixed Assets | System supports streamlined asset imports without complex formatting requirements. | Must Have | ||
| 170 | Finance & Accounting | Fixed Assets | System supports asset reporting by fund, department, category, and asset class. | Must Have | ||
| 171 | Finance & Accounting | Fixed Assets | System supports identification and tracking of grant‑funded assets for compliance purposes. | Must Have | ||
| 172 | Finance & Accounting | Fixed Assets | System supports integration with fleet management systems such as Faster. | Must Have | ||
| 173 | Finance & Accounting | General Ledger & Chart of Accounts | Supports a multi‑segment chart of accounts including, at minimum, Fund, Organization, Department, Object, and Project/Feature dimensions. | Must Have | ||
| 174 | Finance & Accounting | General Ledger & Chart of Accounts | System allows configurable account segments and validation rules without requiring vendor customization or code changes. | Must Have | ||
| 175 | Finance & Accounting | General Ledger & Chart of Accounts | System supports hierarchical fund and sub‑fund structures for tracking high‑revenue and restricted activities. | Must Have | ||
| 176 | Finance & Accounting | General Ledger & Chart of Accounts | Supports a dedicated mechanism to identify and report on grant‑related activity without overloading core accounting segments. | Must Have | ||
| 177 | Finance & Accounting | General Ledger & Chart of Accounts | Supports configurable journal entry fields (e.g., batch number, source system reference) to improve traceability and reconciliation. | Must Have | ||
| 178 | Finance & Accounting | General Ledger & Chart of Accounts | System provides robust search functionality for journal entries, including partial matches and filtering by custom fields. | Must Have | ||
| 179 | Finance & Accounting | Grants Management (Post-Award) | System supports post‑award grant accounting, including grant budgeting, expenditures, revenues, and remaining balances. | Must Have | ||
| 180 | Finance & Accounting | Grants Management (Post-Award) | System supports tracking grant sub‑recipients and associating expenditures and revenues with those sub‑recipients. | Must Have | ||
| 181 | Finance & Accounting | Grants Management (Post-Award) | System supports grant‑specific reporting, including compliance and audit‑ready reporting. | Must Have | ||
| 182 | Finance & Accounting | Grants Management (Post-Award) | System supports integration (API or structured import/export) with third‑party grant management systems such as Grant Vantage. | Must Have | ||
| 183 | Finance & Accounting | Payments & Banking | System supports multiple payment methods including checks and ACH/EFT. | Must Have | ||
| 184 | Finance & Accounting | Payments & Banking | System generates bank‑compatible payment files for electronic payments. | Must Have | ||
| 185 | Finance & Accounting | Payments & Banking | System supports positive pay file generation for check payments. | Must Have | ||
| 186 | Finance & Accounting | Payments & Banking | System tracks outstanding checks and support aging, reporting, and reissuance workflows. | Must Have | ||
| 187 | Finance & Accounting | Payments & Banking | System supports unclaimed property reporting, including generation of state‑required export files. | Must Have | ||
| 188 | Finance & Accounting | P-Cards & Expense Management | System supports automated import of P‑card transactions from the issuing bank. | Must Have | ||
| 189 | Finance & Accounting | P-Cards & Expense Management | System allows electronic attachment of receipts to P‑card and expense transactions. | Must Have | ||
| 190 | Finance & Accounting | P-Cards & Expense Management | System supports configurable expense and P‑card policy rules and exception reporting. | Must Have | ||
| 191 | Finance & Accounting | P-Cards & Expense Management | System supports electronic expense reporting, including pre‑authorization and post‑trip reimbursement. | Must Have | ||
| 192 | Finance & Accounting | P-Cards & Expense Management | System supports employee reimbursements without requiring employees to be set up as vendors. | Must Have | ||
| 193 | Finance & Accounting | Purchasing & Requisitions | System supports electronic requisitions with configurable approval workflows. | Must Have | ||
| 194 | Finance & Accounting | Purchasing & Requisitions | System supports purchase order creation, tracking, and association with invoices. | Must Have | ||
| 195 | Finance & Accounting | Purchasing & Requisitions | System provides a simplified, guided purchasing interface for occasional or non‑finance users. | Must Have | ||
| 196 | Finance & Accounting | Purchasing & Requisitions | System supports approval routing based on configurable approval limits and roles rather than job titles alone. | Must Have | ||
| 197 | Finance & Accounting | Transparency | System supports ACFR preparation through structured financial reporting and exports. | Must Have | ||
| 198 | Finance & Accounting | Transparency | System provides change tracking or audit logs to identify financial statement changes. | Must Have | ||
| 199 | Finance & Accounting | Transparency | System supports public transparency reporting consistent with North Carolina requirements. | Must Have | ||
| 200 | Finance & Accounting | Transparency | System allows controlled drill‑down into financial data for transparency reporting. | Must Have | ||
| LEGAL / PROCUREMENT | ||||||
| 201 | Legal / Procurement | Contract Management | Provide a native or fully integrated contract lifecycle management system tied directly to requisitions and POs. | Must Have | ||
| 202 | Legal / Procurement | Contract Management | Maintain standardized contract templates with clause management and version control. | Must Have | ||
| 203 | Legal / Procurement | Contract Management | Support contract amendments with automatic roll‑up of parent and amendment values. | Must Have | ||
| 204 | Legal / Procurement | Contract Management | Route contracts through legal, risk, finance, and executive approvals based on policy and dollar thresholds. | Must Have | ||
| 205 | Legal / Procurement | Contract Management | Flag contracts requiring board approval and prevent execution prior to approval. | Must Have | ||
| 206 | Legal / Procurement | Contract Management | Support collaborative redlining, comments, and tracked changes without document lock conflicts. | Must Have | ||
| 207 | Legal / Procurement | Contract Management | Prevent data loss with auto‑save, draft recovery, and robust version history. | Must Have | ||
| 208 | Legal / Procurement | Contract Management | Provide native or embedded e‑signature with role‑based signatory routing. | Must Have | ||
| 209 | Legal / Procurement | Contract Management | Track contract execution status and automatically release dependent requisitions/POs upon execution. | Must Have | ||
| 210 | Legal / Procurement | Contract Management | Track contract terms, renewal dates, and auto‑renewal flags with proactive notifications. | Must Have | ||
| 211 | Legal / Procurement | Contract Management | Identify current contract year and associated financial exposure without manual review of documents. | Must Have | ||
| 212 | Legal / Procurement | Contract Management | Maintain a centralized, searchable repository for executed contracts and related documents. | Must Have | ||
| PROCUREMENT | ||||||
| 213 | Procurement | Document Management | Enforce state‑mandated document retention schedules automatically. | Must Have | ||
| 214 | Procurement | Document Management | Enforce role‑based access to sensitive procurement and contract documents. | Must Have | ||
| 215 | Procurement | Purchasing & Requisitioning | System must support standardized requisition entry with guided fields and validations to reduce user error and incomplete submissions. | Must Have | ||
| 216 | Procurement | Purchasing & Requisitioning | Encumber budget automatically at requisition creation and prevent submission when insufficient funds exist. | Must Have | ||
| 217 | Procurement | Purchasing & Requisitioning | Provide configurable, dollar‑based approval routing for requisitions across departments, budget, purchasing, and pre‑audit. | Must Have | ||
| 218 | Procurement | Purchasing & Requisitioning | Provide real‑time requisition status visibility to requestors without requiring manual notes or follow‑ups. | Must Have | ||
| 219 | Procurement | Purchasing & Requisitioning | Notifications to alert approvers and purchasing staff when requisitions are stalled or exceed defined approval SLAs. | Must Have | ||
| 220 | Procurement | Purchasing & Requisitioning | System automatically identifies when a requisition requires a contract based on rules (amount, category, vendor, term). | Should Have | ||
| 221 | Procurement | Purchasing & Requisitioning | Enforce informal quote and formal bid/RFP thresholds per North Carolina procurement regulations and the Town's purchasing policy, with consistent approvals and documentation before purchases are made. | Must Have | ||
| 222 | Procurement | Purchasing & Requisitioning | Allow requisitions to reference cooperative or state contracts and bypass bidding when permitted. | Must Have | ||
| 223 | Procurement | Purchasing & Requisitioning | Support multi‑year requisitions with year‑specific pricing, renewal indicators, and budget planning visibility. | Should Have | ||
| 224 | Procurement | Purchasing & Requisitioning | Automatically generate purchase orders from approved requisitions without re‑keying. | Must Have | ||
| 225 | Procurement | Purchasing & Requisitioning | Distribute approved purchase orders to vendors electronically with attachments. | Must Have | ||
| 226 | Procurement | Purchasing & Requisitioning | Support PO change orders with approval workflow and audit history. | Must Have | ||
| 227 | Procurement | Reporting & Analytics | Report on requisition‑to‑PO cycle time and approval bottlenecks. | Must Have | ||
| 228 | Procurement | Reporting & Analytics | Report total contract value, amendments, and remaining obligations. | Must Have | ||
| 229 | Procurement | Reporting & Analytics | Provide vendor spend reporting across departments and fiscal years. | Must Have | ||
| 230 | Procurement | Reporting & Analytics | Provide role‑based dashboards highlighting pending actions, expirations, and exceptions. | Must Have | ||
| 231 | Procurement | Security & Controls | Enforce segregation of duties across requisitioning, contracting, and payment. | Must Have | ||
| 232 | Procurement | Security & Controls | Provide complete audit trails to support procurement and financial audits. | Must Have | ||
| 233 | Procurement | Systems Integration | Ensure bi‑directional integration between procurement, contracts, AP, and budgeting modules. | Must Have | ||
| 234 | Procurement | Systems Integration | Support integration with bidding portals and external contract systems. | Must Have | ||
| 235 | Procurement | User Experience | Provide centralized work queues for purchasing and contracts staff to manage workload by exception. | Must Have | ||
| 236 | Procurement | Vendor Management | Maintain a single, authoritative vendor master shared across purchasing, contracts, AP, and reporting. | Must Have | ||
| 237 | Procurement | Vendor Management | Support guided vendor onboarding with required documentation (W‑9, COI, ACH) and validations. | Must Have | ||
| 238 | Procurement | Vendor Management | Provide secure vendor self‑service for profile updates, banking changes, and document uploads. | Must Have | ||
| 239 | Procurement | Vendor Management | Route vendor setup and banking changes through dual controls and approvals. | Must Have | ||
| 240 | Procurement | Vendor Management | Prevent duplicate vendors through EIN/Tax ID validation and matching logic. | Must Have | ||
| 241 | Procurement | Vendor Management | Ensure ACH setup is consistently applied across all remit‑to addresses. | Must Have | ||
| 242 | Procurement | Vendor Management | Maintain full audit history for vendor changes including who, when, and what changed. | Must Have | ||
| 243 | Procurement | Vendor Management | Provide robust vendor search supporting DBA names, aliases, and historical records. | Must Have | ||
| 244 | Procurement | Vendor Management | Provide tools to identify inactive, duplicate, or incomplete vendor records. | Must Have | ||
| 245 | Procurement | Vendor Management | Support bank account verification and fraud‑prevention integrations. | Must Have | ||
| UTILITY BILLING | ||||||
| 246 | Utility Billing | Adjustments & Special Billing | Provide online leak adjustment submission form with document upload. | Must Have | ||
| 247 | Utility Billing | Adjustments & Special Billing | Automatically validate leak adjustment eligibility (one-time rule enforcement). | Must Have | ||
| 248 | Utility Billing | Adjustments & Special Billing | Automate 12-month average consumption calculation for adjustments. | Must Have | ||
| 249 | Utility Billing | Adjustments & Special Billing | Differentiate workflows for leak adjustments vs billing corrections. | Should Have | ||
| 250 | Utility Billing | Adjustments & Special Billing | Support charge-code-based credits on future bills. | Could Have | ||
| 251 | Utility Billing | Adjustments & Special Billing | Maintain full audit trail of adjustments. | Must Have | ||
| 252 | Utility Billing | Adjustments & Special Billing | Support batch write-offs with automated flagging of written-off accounts. | Should Have | ||
| 253 | Utility Billing | Adjustments & Special Billing | Automatically detect payments received on written-off accounts. | Must Have | ||
| 254 | Utility Billing | Adjustments & Special Billing | Automate reversal and reapplication of write-offs when payment is received. | Must Have | ||
| 255 | Utility Billing | Adjustments & Special Billing | Support state income tax setoff export functionality. | Could Have | ||
| 256 | Utility Billing | Billing & Invoicing | Support monthly billing cycles with flexibility for multiple billing groups. | Should Have | ||
| 257 | Utility Billing | Billing & Invoicing | Reduce lag between meter read and invoice generation. | Could Have | ||
| 258 | Utility Billing | Billing & Invoicing | Integrate with third-party print/mail vendors. | Must Have | ||
| 259 | Utility Billing | Billing & Invoicing | Support electronic billing enrollment and management. | Must Have | ||
| 260 | Utility Billing | Billing & Invoicing | Provide customer access to PDF invoices online. | Must Have | ||
| 261 | Utility Billing | Billing & Invoicing | Support tiered rate structures for residential, commercial, industrial, bulk, and hydrant accounts. | Must Have | ||
| 262 | Utility Billing | Billing & Invoicing | Allow sewer billing based on water consumption. | Must Have | ||
| 263 | Utility Billing | Billing & Invoicing | Support inside/outside rate structures. | Must Have | ||
| 264 | Utility Billing | Billing & Invoicing | Allow effective-dated rate tables. | Must Have | ||
| 265 | Utility Billing | Billing & Invoicing | Provide automated recalculation when rates change. | Must Have | ||
| 266 | Utility Billing | Billing & Invoicing | Support annexation-based rate changes with notifications. | Must Have | ||
| 267 | Utility Billing | Customer Service & Portal | Provide full self-service portal for move-in/move-out processing. | Must Have | ||
| 268 | Utility Billing | Customer Service & Portal | Enforce mandatory required fields for applications. | Must Have | ||
| 269 | Utility Billing | Customer Service & Portal | Automatically reject incomplete applications. | Must Have | ||
| 270 | Utility Billing | Customer Service & Portal | Allow document upload during application process. | Must Have | ||
| 271 | Utility Billing | Customer Service & Portal | Provide real-time account creation and status tracking. | Should Have | ||
| 272 | Utility Billing | Customer Service & Portal | Display usage history, bills, payments, and adjustment status. | Must Have | ||
| 273 | Utility Billing | Customer Service & Portal | Provide graphical usage and billing visualizations. | Must Have | ||
| 274 | Utility Billing | Customer Service & Portal | Support SMS and email notifications for billing, leaks, and disconnections. | Must Have | ||
| 275 | Utility Billing | Customer Service & Portal | Provide chatbot with live-agent escalation option. | Must Have | ||
| 276 | Utility Billing | Customer Service & Portal | Provide dashboard for tracking application and service request volumes. | Must Have | ||
| 277 | Utility Billing | Meter Reading & Consumption Management | Integrate with meter reading software (radio and manual). | Must Have | ||
| 278 | Utility Billing | Meter Reading & Consumption Management | Support automated import/export of meter reading files. | Must Have | ||
| 279 | Utility Billing | Meter Reading & Consumption Management | Validate imported reads using configurable high/low/zero thresholds. | Must Have | ||
| 280 | Utility Billing | Meter Reading & Consumption Management | Allow configurable exception reporting logic without vendor programming. | Must Have | ||
| 281 | Utility Billing | Meter Reading & Consumption Management | Provide (internal) dashboard with 24-month historical usage and trend graphs. | Must Have | ||
| 282 | Utility Billing | Meter Reading & Consumption Management | Allow filtering exceptions by route, vacant status, and consumption type. | Must Have | ||
| 283 | Utility Billing | Meter Reading & Consumption Management | Enable batch creation of work orders from exception lists. | Must Have | ||
| 284 | Utility Billing | Meter Reading & Consumption Management | Provide audit tracking of exception review decisions. | Must Have | ||
| 285 | Utility Billing | Meter Reading & Consumption Management | Support centralized digital documentation of meter changes and new installations. | Must Have | ||
| 286 | Utility Billing | Meter Reading & Consumption Management | Automatically update billing records upon meter install to refelect new service start date. | Could Have | ||
| 287 | Utility Billing | Meter Reading & Consumption Management | Generate alerts for unbilled new connections. | Must Have | ||
| 288 | Utility Billing | Meter Reading & Consumption Management | Support sewer-only metered accounts. | Must Have | ||
| 289 | Utility Billing | Meter Reading & Consumption Management | Automate averaging calculations for malfunctioning meters. | Could Have | ||
| 290 | Utility Billing | Payments & Lockbox Processing | Support online payments (credit card, ACH, digital wallets). | Must Have | ||
| 291 | Utility Billing | Payments & Lockbox Processing | Support IVR, kiosk, in-office, and ACH auto-draft payments. | Must Have | ||
| 292 | Utility Billing | Payments & Lockbox Processing | Automate lockbox file imports. | Should Have | ||
| 293 | Utility Billing | Payments & Lockbox Processing | Provide intelligent matching logic using account, bill, and customer identifiers. | Must Have | ||
| 294 | Utility Billing | Payments & Lockbox Processing | Prevent duplicate identifiers across account, bill, and customer records. | Must Have | ||
| 295 | Utility Billing | Payments & Lockbox Processing | Flag payment exceptions prior to posting. | Could Have | ||
| 296 | Utility Billing | Payments & Lockbox Processing | Provide real-time validation before batch posting. | Should Have | ||
| 297 | Utility Billing | Performance & Operational Governance | Ensure fast account lookup and bill reprint functionality. | Must Have | ||
| 298 | Utility Billing | Performance & Operational Governance | Eliminate performance lag during customer service interactions. | Must Have | ||
| 299 | Utility Billing | Performance & Operational Governance | Provide configurable special condition flags. | Must Have | ||
| 300 | Utility Billing | Performance & Operational Governance | Reduce unnecessary pop-up alerts for staff efficiency. | Must Have | ||
| 301 | Utility Billing | Performance & Operational Governance | Support cross-department notifications for annexations and approvals. | Must Have | ||
| 302 | Utility Billing | Reporting & Analytics | Provide modern, supported reporting engine to replace legacy reporting tools. | Must Have | ||
| 303 | Utility Billing | Reporting & Analytics | Allow self-service report builder with parameter-driven filters. | Must Have | ||
| 304 | Utility Billing | Reporting & Analytics | Generate cut-off, turn-on, and completed work order reports. | Must Have | ||
| 305 | Utility Billing | Reporting & Analytics | Generate debt setoff eligibility reports. | Must Have | ||
| 306 | Utility Billing | Reporting & Analytics | Generate billing audit and reconciliation reports. | Must Have | ||
| 307 | Utility Billing | Reporting & Analytics | Provide lockbox reconciliation reporting. | Must Have | ||
| 308 | Utility Billing | Reporting & Analytics | Generate top water and sewer user reports annually. | Must Have | ||
| 309 | Utility Billing | Reporting & Analytics | Provide consumption analytics across 21,000+ accounts. | Must Have | ||
| 310 | Utility Billing | Reporting & Analytics | Support export to Excel and other formats. | Must Have | ||
| 311 | Utility Billing | Reporting & Analytics | Provide dashboard metrics for call volume and processing times. | Must Have | ||
| 312 | Utility Billing | Work Orders & Field Operations | Provide fully digital, mobile-enabled work order management. | Must Have | ||
| 313 | Utility Billing | Work Orders & Field Operations | Allow real-time status updates (created, assigned, completed, canceled). | Must Have | ||
| 314 | Utility Billing | Work Orders & Field Operations | Support route-based technician assignment. | Must Have | ||
| 315 | Utility Billing | Work Orders & Field Operations | Allow real-time cancellation/modification of work orders. | Must Have | ||
| 316 | Utility Billing | Work Orders & Field Operations | Provide offline mobile capability with automatic sync. | Must Have | ||
| 317 | Utility Billing | Work Orders & Field Operations | Display meter number, account history, and notes in the field. | Must Have | ||
| 318 | Utility Billing | Work Orders & Field Operations | Automate cut-off list generation. | Must Have | ||
| 319 | Utility Billing | Work Orders & Field Operations | Provide real-time payment visibility during disconnection processing. | Must Have | ||
| 320 | Utility Billing | Work Orders & Field Operations | Automate reconnection fee assessment. | Must Have | ||
| 321 | Utility Billing | Work Orders & Field Operations | Track and enforce one-time courtesy waivers automatically. | Must Have | ||
| 322 | Utility Billing | Work Orders & Field Operations | Generate notifications for disconnection, payment receipt, and service restoration. | Must Have | ||
| 323 | Utility Billing | Work Orders & Field Operations | Log customer communication attempts related to field activity. | Must Have | ||
| HR | ||||||
| 324 | HR | Core HR, Payroll, & Benefits | System must provide a single system of record for employee demographic, job, compensation, and employment status data, eliminating duplicate entry across multiple systems. | Must Have | ||
| 325 | HR | Core HR, Payroll, & Benefits | System must support end-to-end employee lifecycle management (hire, promotion, transfer, reclassification, leave, termination) through integrated workflows without reliance on external forms or spreadsheets. | Must Have | ||
| 326 | HR | Core HR, Payroll, & Benefits | Replace manual Employee Action Forms (EAFs) with native, configurable workflows that route approvals, update downstream systems, and maintain full audit trails. | Must Have | ||
| 327 | HR | Core HR, Payroll, & Benefits | Maintain centralized position control tied to job class, department, pay plan, FTE, and budget authorization, with vacancies tracked in real time. | Must Have | ||
| 328 | HR | Core HR, Payroll, & Benefits | Hiring requisitions must validate against approved budget and authorized positions before posting or offer approval. | Must Have |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .