Attachment 5 - Acceptance Requirements.xlsx

XLSX spreadsheet 177 KB Posted

Attached to
ENTERPRISE RESOURCE PLANNING (ERP) SOFTWARE AND SERVICES RFP
Solicitation number
147077
Issued by
Los Angeles County, California

About this file

This is an Acceptance Requirements spreadsheet for the City of Burbank's Enterprise Resource Planning (ERP) software and services Request for Proposal. The document provides standardized instructions and response templates for vendors to indicate their ability to meet 363 functional requirements across Finance, Budget, and Human Resources modules. Respondents must complete columns E through H for each requirement, indicating whether their proposed solution meets each requirement with responses of "Y" (requirement met), "Y-WC" (met with conditions requiring explanation), "N" (cannot be met), or "I" (insufficient information to respond). Requirements marked "Y" constitute binding commitments included in the offeror's fixed-fee implementation price, while "Y-WC" responses require detailed comments explaining conditions and impacts. The Finance section addresses 80 requirements spanning chart of accounts, journal entries, budget monitoring, project management, purchasing, accounts payable, accounts receivable, treasury functions, capital assets, and work orders. The Budget section contains 70 requirements related to budget planning, revenue forecasting, personnel budgeting, capital budgeting, and comprehensive financial reporting. The Human Resources section includes 363 requirements addressing position structure, employee records, certifications, training, personnel actions, succession planning, applicant tracking, benefits administration, compensation, leave management, scheduling, and payroll processing, with specific provisions for compliance with municipal employee unions and memoranda of understanding.

Respondents must organize proposals into three submission packages: Package I containing the primary submission with the completed Acceptance Requirements workbook plus separate Interface and Staffing Level of Effort workbooks, sample agreements, and litigation disclosures; Package II containing the completed Price Proposal Workbook (Attachment 18) with supporting pricing information; and Package III containing the Minimum Qualifications Form (Attachment 19) with supporting documentation. All non-spreadsheet responses must be submitted in PDF or DOCX format, while required workbooks must be in XLS or XLSX format, and sample agreements and litigation disclosures must be PDF files. The RFP requires vendors to maintain all pricing within Package II and indicates this is a fixed-fee implementation engagement with no separate line items visible in the acceptance requirements document itself.

View the file

Other files

File Type Posted
Attachment 18 - Price Proposal.xlsx XLSX spreadsheet
Attachment 11 - Staffing Level of Effort.xlsx XLSX spreadsheet
Attachment 6 - Interfaces.xlsx XLSX spreadsheet
RFP IT-2026-01 ERP Software and Services.pdf PDF

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

Instructions

City of Burbank
Acceptance Requirements
Please use the descriptions below to complete columns E - H on the subsequent tabs.
Indicates input cell for Respondent to supply information.
ColumnHeaderDescription
AReq #Requirement number
BFunctional AreaThe functional areas described in the Process Scope of the RFP
CProcessThe specific process area within a Functional Area
DUser Story RequirementSpecific requirement the City has for the new ERP system
EResponseRespondent replies with its ability to meet the requirement
FModule / SystemThe module or system (within the ERP or a third-party system) that will meet the requirement
GPhaseAnticipated phase in which requirement will be met
HCommentFor the Offeror to provide additional context or clarification as needed. For responses of Yes - With Conditions (Y-WC) a comment is required to explain the condition.
Response Key - Column E: Response
Available ResponseDescription
YRequirement is met by proposed solution, either out of the box or through configuration. All requirements marked "Y" constitute a binding commitment that the Offeror’s proposed solution will deliver the described functionality as part of the implementation services included in the Offeror’s fixed‑fee price.
Y-WCRequirement is principally and materially met, but with minor, defined limitations, dependencies, or exceptions. Offeror must describe all conditions and impacts in the Comments field that prevent the requirement from being a "Y" response. This response signifies that the Offeror can and will deliver the requirement as part of the contracted implementation scope and within the fixed‑fee price, subject only to the specific conditions explicitly disclosed in the Offeror’s written response.
NRequirement cannot be met by the proposed solution.
IOfferor cannot respond without additional information. Provide explanation.
Response Key - Column G: Phase
Available ResponseDescription
1The Offeror proposes delivering the Requirement the first go-live phase. If the proposed project is full "big bang" implementation, all requirements would be Phase 1.
2The Offeror proposes delivering the Requirement the second go-live phase. For example, a project that proposes Financials go-live first, followed by HCM would have the Financials Requirements as a "1" and the HCM Requirements as a "2." The effort to deliver Phase 2 shall be included in the fixed fee price.
XThe Offeror proposes delivering the Requirement during a subsequent phase. The effort to deliver Phase X shall be included in the fixed fee price.

Finance Attachment 6 - Acceptance Requirements

Req #Functional AreaProcessUser Story RequirementResponseModule / SystemPhaseComment
1CoAChart of AccountsSystem will support GASB and GAAP Accounting Standards
2CoAChart of AccountsSystem provides a chart of account structure with multiple independent segments
3CoAChart of AccountsSystem tracks funds, organizational units, programs, accounts, and projects as independent segments
4CoAChart of AccountsSystem provides hierarchies within any segment (example: department and division)
5CoAChart of AccountsSystem tracks programs across multiple departments
6CoAChart of AccountsSystem will support both the modified and full accrual methods with the ability to convert modified accruals to full accruals
7BWPMultipleSystem will accommodate all needs for Burbank Water and Power relative to the ERP of the City of Burbank as a utility housed within the City
8BWPMultipleSystem will accrue costs to multiple jurisdictions outside of the City of Burbank
9BWPMultipleSystem will hold assets and assign costs for capital asset inventory before utilization in the field
10BWPMultipleSystem will provide approval workflows processes for all transactions and interactions with the ERP system
11GLJournal EntryJournal entries are entered by accounting staff and routed through an approval workflow
12GLJournal EntryJournal entries are validated against the chart of account structure for valid accounts (example: valid fund, department, program combination)
13GLJournal EntryJournal entries are validated against available funds (budget check or cash availability check)
14GLJournal EntryJournal entries are validated against balancing entries (make sure all entries balance)
15GLJournal EntrySystem will enable users to import journal entries from spreadsheets (e.g., Microsoft Excel)
16GLJournal EntryImported transactions from spreadsheets are validated using the same business rules as transactions made in the system
17GLJournal EntrySystem enables users to reverse journal entries with proper security and approvals
18GLJournal EntrySystem enables users to schedule accrual auto-reversals
19GLJournal EntrySystem enables users to attach files/documentation to journal entries
20GLJournal EntrySystem enables posting of transactions for multiple fiscal years at the same time
21GLJournal EntrySystem enables users to enter and schedule journal transactions using effective dates (e.g., posting does not occur until effective date)
22GLJournal EntryPosted journal entries provide generic notifications alerting the next level of approval in the workflow (due to public records requests)
23GLJournal EntrySystem will provide workflow notifications and approvals (in lieu of emails) that are not subject to FOIA requests
24GLJournal EntrySystem generates audit reports that identify information on journal entries along with user information for who initiated, reviewed, and posted entries
25GLRecurring Journal EntrySystem provides templates and notifications for recurring journal entries with the same dollar value
26GLRecurring Journal EntrySystem provides templates and notifications for recurring journal entries with varying dollar amounts
27GLRecurring Journal EntryRecurring journal entries occur at regular frequency (can set start and stop dates)
28GLRecurring Journal EntrySystem allows journal entries to be scheduled (example: lease/debt schedules)
29GLBudget MonitoringBudget control can be set to soft error (Warn user but allow)
30GLBudget MonitoringBudget control can be set to hard error (Do not allow)
31GLBudget MonitoringSystem enables budgeting at one level and controlling at a different level (Example: budget by account/object but conduct budget control at department level)
32GLBudget MonitoringSystem provides role focused budget to actual dashboard with information relevant to user’s department, division, project, and program.
33GLBudget MonitoringSystem provides notifications to specific users when budgetary amounts are below an (X%) threshold
34GLBudget MonitoringSystem will enable departmental users to enter budget adjustments via approval workflows prior to posting
35GLProject Set UpSystem supports multiple-year projects
36GLProject Set UpSystem supports parent/child relations for projects and sub-projects
37GLProject Set UpSystem tracks funding sources (multiple funding sources for each project)
38GLProject Set UpSystem uses project start and end dates for determining eligible expenditures and prohibits transactions outside the project eligibility period
39GLProject Set UpSystem enables projects to be established across multiple funds and departments
40GLProject Set UpSystem will enable project sub-levels to be user-defined and to differ across projects
41GLProject Set UpSystem will identify and track user-defined, multiple sub-levels of a project (e.g. design, pre-construction, construction, post construction, completed)
42GLProject Set UpSystem will prepopulate values instead of defaulting to a “Misc” or “Other” value
43GLProject Set UpSystem will enable projects to identify matching fund requirements
44GLProject Set UpSystem will enable projects to carry key receivables data elements, including, but not limited to batch name, customer number, and revenue GL distribution for AIC [Aid in Construction] related projects.
45GLProject BudgetSystem will establish project budgets for the entire project
46GLProject BudgetSystem will establish project budgets by fiscal year within multi-year projects
47GLProject BudgetBudget control for projects can be set for the calendar year
48GLProject BudgetBudget control for projects can be set for periods other than the City’s fiscal year (e.g., grantor fiscal year)
49GLProject BudgetBudget control for projects can be set for the entire life of project (e.g., multi-year)
50GLProject BudgetSystem will provide budget control at the project level with the ability to amend
51GLProject BudgetSystem will control budget at the sub-project level (example: phase, task, etc.)
52GLProject BudgetSystem will enable setting the level of budget control differently for each project
53GLProject BudgetSystem will limit projects’ expenses based the funding available from their sources
54GLProject BudgetSystem will track and control budgets for multiple projects using the same funding source
55GLProject/Grant TrackingSystem tracks encumbrance to project through purchasing
56GLProject/Grant TrackingSystem tracks expense to project through accounts payable
57GLProject/Grant TrackingSystem tracks direct costs and indirect costs (encumbrance and expense) to project through journal entries
58GLProject/Grant TrackingSystem applies internal cost rate for each project
59GLProject/Grant TrackingSystem enables employees to charge time to projects and sub projects
60GLProject/Grant TrackingSystem tracks salary and benefit costs (expense) to project through payroll
61GLProject/Grant TrackingSystem allocates indirect costs to projects based on pre-determined cost drivers and allocation schedules
62GLProject/Grant TrackingSystem identifies eligible expenses for reimbursement based on criteria identified for each project (by account)
63GLProject/Grant TrackingSystem identifies and tracks funding sources for projects
64GLProject/Grant TrackingSystem will split the cost of projects across various funding sources by Percentage (e.g. 70% grant, 30% bond)
65GLProject/Grant TrackingSystem will split the cost of projects across various funding sources by Priority (Grant first, local funds next)
66GLProject/Grant TrackingSystem will split the cost of projects across various funding sources by priority up to a limit (example: Charge grant first up to $10,000 then charge local funds)
67GLRevenue (Grants)System will split revenue sources across multiple projects
68GLRevenue (Grants)System will use multiple revenues sources for a single project
69GLRevenue (Grants)System will split multiple revenue sources across multiple projects (each project has multiple sources)
70GLRevenue (Grants)System will track grant revenue as deferred revenue until expended by projects
71GLGrant ManagementSystem tracks grant applications
72GLGrant ManagementSystem tracks grant budget for grant application
73GLGrant ManagementSystem provides workflow to approve grant application and grant award
74GLProject/Grant BillingSystem links projects with accounts receivable to provide all billing, aging, and tracking capabilities.
75GLProject/Grant BillingSystem generates revenue/receivable transactions from grants expenditure data
76GLProject/Grant BillingSystem generates invoices for any project costs (e.g., bill to contractors, residents, other governments, or grants)
77GLProject/Grant BillingSystem generates invoices for eligible billable expenses at any time, including project completion, milestones, or other specified points.
78GLProject/Grant BillingSystem provides project billing based on actual expenses (e.g., using current salary and benefit information)
79GLProject/Grant BillingSystem prepares internal billing for cost transfer between departments
80GLProject/Grant ReportingSystem prepares 425A FFR Grant Reporting
81GLProject/Grant ReportingSystem provides required SEFA grant reporting
82GLProject/Grant ReportingSystem provides export of detailed grant transactions
83POSupplier RegistrationSystem maintains multiple location addresses for each vendor
84POSupplier RegistrationSystem identifies default payment remittance address
85POSupplier RegistrationVendor file stores vendor payment preference (e.g., ACH, check, or other e-payable)
86POSupplier RegistrationSystem identifies preferences for electronic payments and makes all payments electronically for those indicated
87POSupplier RegistrationVendor files will identify the terms and conditions that are applied to purchase orders for that vendor
88POSupplier RegistrationSystem records multiple commodity (NIGP) codes to classify vendors
89POSupplier RegistrationVendor file stores insurance levels information
90POSupplier RegistrationSystem identifies cumulative purchase history, including p-card purchases, by vendor to identify common vendors
91POSupplier RegistrationSystem confirms verification of vendor disbarment (SAM.gov)
92POSupplier RegistrationSystem identifies one-time vendors—vendors set up with a normal vendor file but are identified as a one-time vendor for easier data entry and system search functions
93POSupplier Self ServiceSystem provides an online vendor registration portal for new and existing vendors
94POSupplier Self ServiceSystem enables vendors to enter vendor information
95POSupplier Self ServiceSystem enables vendors to update vendor information
96POSupplier Self ServiceSystem enables vendors to upload w-9s and other required files during the registration process
97POSupplier Self ServiceSystem submits all vendor changes to staff via approval workflows
98POSupplier Self ServiceSystem enables vendors to store multiple contacts (and have multiple users)
99POSupplier Self ServiceSystem provides an alternative category or payment methodology for retirees who receive payment from the City but are not a "vendor"
100POSupplier Relationship ManagementSystem reports on the total spend with vendors (including PO and p-cards)
101POSupplier Relationship ManagementSystem provides vendor performance metrics reporting (e.g., on-time performance, number of issues recorded)
102POSupplier Relationship ManagementSystem reports on all contract activity with vendors
103POSupplier Relationship ManagementSystem reports on the status of contract milestones by vendor
104PORequisitionSystem will enable department staff to initiate the purchasing process through requisition entry
105PORequisitionSystem will enable requestors to attach files to requisitions
106PORequisitionSystem will enable requisitions to be split into multiple budget lines
107PORequisitionPurchase requisitions will use project accounts at line-item level
108PORequisitionPurchase requisitions will enable users to add NIGP commodity codes to line items
109PORequisitionSystem will enable users to record information for informal quotes
110PORequisitionPurchase requisitions enables users to identify contract for requisition
111PORequisitionSystem will enable users to identify the budget year to enter requisition (Example: at end of fiscal year where there may be a need to transact in current and future year)
112PORequisitionSystem records pre-encumbrance when purchase requisition is saved or submitted through workflow
113PORequisitionSystem notifies users if item on requisition is currently under contract with vendor (by commodity code)
114PORequisitionSystem notifies users if amount of requisition will exceed not to exceed limit of contract
115PORequisitionSystem provides options for emergency purchases that will bypass workflow approvals and create purchase orders
116PORequisitionSystem routes purchase requisitions for approval/notification by chart of account information (e.g., object/account code)
117PORequisitionSystem routes purchase requisitions for approval/notification by dollar amount
118PORequisitionSystem routes purchase requisitions for approval/notification by determining if it is a capital item
119PORequisitionSystem routes purchase requisitions for approval/notification to additional users based on purchase type/commodity code (e.g., IT equipment to IT or vehicle purchase to fleet).
120PORequisitionSystem enables users to cancel requisitions before they are approved
121PORequisitionSystem ensures cancelled requisitions or cancelled requisition line items release pre-encumbrance
122PORequisitionSystem provides requisition cancellation en masse (such as at the end of a fiscal year)
123PORequisitionSystem provides requisition cancellation, or releases, at any stage of the process with Purchasing Manager override
124PORequisitionSystem will roll open purchase orders at year end to the next fiscal year
125POPurchase OrderSystem will roll open purchase orders at year end to the next fiscal year
126POPurchase OrderSystem will roll the associated encumbered budgets of any open purchase order rolled to the next fiscal year and will apply them against the new fiscal year budget
127POPurchase OrderSystem links purchase orders to the requisition process
128POPurchase OrderSystem automatically creates POs after requisitions are approved based on dollar thresholds
129POPurchase OrderSystem will ensure the creation of purchase orders triggers the creation of encumbrances
130POPurchase OrderSystem will send purchase orders to vendors via email
131POPurchase OrderSystem will ensure purchase orders contain default contract terms based on the type of purchase and commodity code
132POPurchase OrderSystem will notify the appropriate department when a purchase order (PO) has insufficient funds, requires a release or line to be created, or has a status of Not Approved.
133POPurchase Order ChangeAny open purchase orders can be modified by a change order
134POPurchase Order ChangeCity (department) staff are enabled to modify purchase orders via change order requests with approval workflows
135POPurchase Order ChangeDepartments are enabled to initiate purchase order change requests to increase quantities or amounts
136POPurchase Order ChangeDepartments are enabled to initiate purchase order change requests to decrease quantities or amounts
137POPurchase Order ChangeDepartments are enabled to initiate purchase order change requests to cancel line items
138POPurchase Order ChangeDepartments are enabled to initiate purchase order change requests to cancel entire POs
139POPurchase Order ChangeDepartments are enabled to initiate purchase order change requests to add line items
140POPurchase Order ChangeDepartments are enabled to initiate purchase order change requests to change chart of account strings
141POPurchase Order ChangeSystem will ensure change orders exceeding X% of an original purchase order require an additional change order workflow approval
142POPurchase Order ChangeSystem includes PO cancellation en masse (such as at the end of a fiscal year)
143POPurchase Order ChangeSystem provides PO cancellation at any stage of the process with Purchasing Manager override
144POPurchasing CardSystem provides automatic transfer of purchasing card transaction details from the bank
145POPurchasing CardInterface with bank provides amount, vendor, MCC code, vendor name, p-card holder, date
146POPurchasing CardSystem automatically identifies vendors based on file from bank
147POPurchasing CardAny new vendor (not in vendor file) where a P-card is used is added to vendor file
148POPurchasing CardSystem enables users to identify the correct account for each p-card transaction
149POPurchasing CardSystem enables users to identify the correct project (including sub-project) for each p-card transaction
150POPurchasing CardSystem enables users to identify correct contract for each p-card transaction
151POPurchasing CardSystem enables users to identify the corresponding purchase order for each p-card transaction
152POPurchasing CardSystem enables users to identify the correct NIGP commodity code for each p-card transaction
153POPurchasing CardSystem will upload scanned receipts
154POPurchasing CardSystem uses a mobile camera to capture receipts, and enters them into the system
155POPurchasing CardSystem will charge a single p-card transaction across multiple accounts
156POPurchasing CardSystem enables users to identify p-card vendors (link to vendor file)
157POPurchasing CardSystem records expenses when cardholders process p-card transactions to update accounts
158POPurchasing CardSystem provides workflow approval of p-card transactions
159POPurchasing CardSystem provides workflow approval of monthly p-card statements
160POCompetitive SolicitationSystem publishes online solicitation documents including any necessary RFP/Bid attachments
161POCompetitive SolicitationSystem will interface with Planet Bids
162POCompetitive SolicitationSystem will provide access to vendors to review open solicitations
163POCompetitive SolicitationSystem will enable prospective vendors to sign in and register with the City
164POCompetitive SolicitationSystem will enable vendors to submit bids/proposals online
165POCompetitive SolicitationSystem provides a portal for the evaluation team to review bids/RFP submissions
166POCompetitive SolicitationSystem provides tools to support evaluation team scoring
167POContract ManagementSystem enables users to attach files to contracts
168POContract ManagementSystem tracks the required insurance, performance bonds, vendor licenses, or other contract requirements
169POContract ManagementSystem tracks expiration dates of insurance, vendor licenses, or other contract requirements.
170POContract ManagementSystem will apply purchase orders/requisitions against contracts
171POContract ManagementSystem will ensure purchase orders encumber funds against contracts
172POContract ManagementSystem tracks service performance against contracts (e.g., milestones and/or deliverables).
173POContract ManagementSystem tracks and automatically flags contract expiration dates with sufficient lead time to extend or re-solicit contracts
174POContract ManagementSystem tracks contract pricing (e.g., unit prices for various items under contract)
175APInvoice ApprovalSystem will scan invoices, electronically receive, and initiate workflows
176APInvoice ApprovalSystem will populate information for invoices from purchase orders
177APInvoice ApprovalSystem enables approved users to enter direct claims without purchase orders
178APInvoice ApprovalSystem provides workflow approval paths for invoices from purchase orders
179APInvoice ApprovalSystem provides workflow approval paths for invoices without purchase orders
180APInvoice ApprovalSystem provides workflow approval paths for invoices via interfaces with other systems.
181APInvoice ApprovalSystem will route invoices through approval workflows based on amounts
182APInvoice ApprovalSystem will route invoices through approval workflows based on point of entry (e.g., entered by department vs. AP)
183APInvoice ApprovalSystem will route invoices through approval workflows based on PO vs no PO
184APInvoice ApprovalSystem will route invoices through approval workflows based on chart of account information
185APInvoice ApprovalSystem will enable partial invoice payments
186APInvoice ApprovalSystem will automatically check for and prevent duplicate invoice numbers for the same vendor (e.g., don't pay same invoices twice)
187APInvoice ApprovalSystem will enable users to attach files to invoices
188APInvoice ApprovalSystem will automate self-accrual of sales tax for invoices based on category codes
189APInvoice ApprovalSystem will manage both prepaid and accrual payments (e.g., prepaid expenses in the future FY and accrual expenses in the prior year)
190RMReceiving and MatchingSystem will provide 2-way matching (e.g., purchase order, invoice)
191RMReceiving and MatchingSystem will provide 3-way matching (e.g., purchase order, receiving document, invoice)
192RMReceiving and MatchingSystem will provide matching at the line-item level
193RMReceiving and MatchingSystem will enable limits on PO and invoice prices for matching based on percentages and limits (e.g., invoices can't be greater than 105% of purchase order or $5 [whichever is greater])
194RMReceiving and MatchingSystem will exclude freight and shipping charges from matching requirements
195RMReceiving and MatchingSystem will provide notifications when there is not a match
196RETAINRetainageSystem will identify payments associated with retention and automatically credit the retention account based on the fund from which the payment was made
197RETAINRetainageSystem will identify payments subject to withholding and will apply a 7% withholding to payments for services performed in California; it will also remove the withholding if the services were performed outside of California
198APEmployee Expense ReimbursementSystem provides an online portal for employees to request expense reimbursement
199APEmployee Expense ReimbursementEmployees are enabled to initiate request for travel/expense approval prior to event
200APEmployee Expense ReimbursementEmployee travel/expense requests will be routed through approval workflows
201APEmployee Expense ReimbursementEmployees are enabled to upload receipts to request travel/expense reimbursement
202APEmployee Expense ReimbursementEmployees are enabled to request reimbursement of approved per-diem rates
203APEmployee Expense ReimbursementSystem stores per diem rates per City policy
204APEmployee Expense ReimbursementSystem tracks taxable reimbursements and adds them to employee earnings as imputed income
205APEmployee Expense ReimbursementSystem will provide a travel reimbursement workflow with continued notifications and information for employees on tax implications for non-compliance with required timelines
206APRefunds, RebatesSystem processes refunds to one-time customers
207APRefunds, RebatesSystem will upload refunded payments from other systems (e.g., Utility Billing, Parks and Rec)
208APRefunds, RebatesSystem initiates refund payments to customers for overpayment
209APRefunds, RebatesSystem initiates refund payments to customers for cancelled payments
210APRefunds, RebatesSystem updates third party systems with refund information (if payment originated from third party system)
211APRefunds, RebatesSystem will track credits from returns made to vendors (Staples, etc.) to be used in next/future transaction
212APPayment ProcessSystem will schedule approved invoices for payment based on invoice date (example: 30 days after invoice date)
213APPayment ProcessSystem will schedule approved invoices for payment based on date entered by AP clerk
214APPayment ProcessSystem will schedule approved invoices for payment based on grouping of invoices
215APPayment ProcessSystem will pay vendors electronically (ACH, wire transfer, check, etc.) via automated workflows using standard NACHA formats (ctx).
216APPayment ProcessSystem will automatically post approved ACH/WIRE payments to the general ledger.
217APPayment ProcessSystem will enable AP staff to modify the payment batch by adding or removing payments prior to the checks being printed
218APPayment ProcessThe system prints checks based on regular schedule
219APPayment ProcessThe system prints on-demand payments (e.g., single check printing, single ACH transmission)
220APPayment ProcessSystem enables authorized users to reprint checks when necessary (e.g., jammed printer, checks inserted incorrectly)
221APPayment ProcessSystem enables authorized users to void check payments and, when required, reissue replacement checks for the same payment obligation
222APPayment ProcessSystem will provide an escheatment process that voids eligible checks and transfers the corresponding funds to a designated escheatment account
223APPayment ProcessSystem provides and sends electronic payment files to bank
224APPayment ProcessSystem sends electronic remittance advice for EFT payments to vendors through email
225APPayment ProcessSystem permits users to select to pay one invoice per check (issue multiple checks to one vendor in a single check run).
226APPayment ProcessSystem combines multiple invoice payments onto one check (issue one check for multiple invoices in a single check run)
227APPayment ProcessSystem provides positive pay
228APPayment ProcessSystem saves templates for generating invoices (e.g., different templates for each AR type)
229APPayment ProcessSystem will enable users to verify payment details before payments are generated
230APPayment ProcessSystem will enable users to send forms and other information via attachments to employees and vendors when processing ACH transactions (e.g., workers comp)
231APPayment ProcessSystem will enable payments by ACH or Credit Card
232APEnd of Year ProcessSystem will roll open purchase orders at year end to the next fiscal year
233APEnd of Year ProcessSystem will roll the associated encumbered budgets of any open purchase order rolled to the next fiscal year and will apply them against the new fiscal year budget
234APEnd of Year ProcessSystem will monitor cumulative payments to 1099 vendors
235APEnd of Year ProcessSystem will provide on-demand 1099 form generation
236APEnd of Year ProcessSystem will collect necessary information for generating Federal 1099s at year-end (both manually and per IRS approved file; all types of 1099)
237APEnd of Year ProcessSystem will produce electronic files to send 1099 related forms to IRS
238APEnd of Year ProcessSystem will define and remove non-taxable payments (e.g., returned payments for pre-payments or fees) so they are not taxed in the 1099
239ARMiscellaneous BillingDepartments will use system to create customer invoices for various charges manually
240ARMiscellaneous BillingUsers will create customer invoices for each type by entering dollar amount
241ARMiscellaneous BillingSystem enables users to create customer invoices for each type by entering financial or non-financial parameters, and will calculate appropriate fees according to pre-defined business rules (e.g., fee schedule), actual costs and wages for project
242ARMiscellaneous BillingSystem generates statements with due invoices
243ARMiscellaneous BillingSystem generates statements with real-time, standard receipts for applied payments for all types of invoices per customer accounts
244ARMiscellaneous BillingSystem prints invoices with statement balance information and customer account location type
245ARMiscellaneous BillingSystem will support multi-fund accounting on a single customer invoice by allowing multiple AR and Revenue GL distributions
246ARMiscellaneous BillingSystem will create customer invoices with multiple funds for both receivable and revenue distributions
247ARMiscellaneous BillingSystem will generate an informational customer invoice or payment request for voluntary contributions, donations, sponsorships, or other non-billable transactions that do not establish an Accounts Receivable balance or post General Ledger
248ARMiscellaneous BillingSystem will generate customer invoices that include a detachable remittance advice (payment stub) to accompany customer payment
249ARMiscellaneous BillingSystem will provide scheduled report delivery to users
250ARMiscellaneous BillingSystem will provide configurable approval workflows for adjustments (e.g., write-offs, credit memos, refunds)
251ARIntegration BillingSystem creates receivables for all general billing in the General Ledger
252ARIntegration BillingSystem enables users to create receivables manually for bills generated outside the system
253ARIntegration BillingSystem will import receivables (aggregate) from bills generated from external systems (e.g., utility bill, permits, etc.) (see integration list)
254ARIntegration BillingSystem updates third party billing system when invoices are paid
255ARRecurring BillingSystem accommodates recurring customer invoices (regular invoices to occur at set dates or duration) (example: rent)
256ARRecurring BillingSystem allows recurring customer invoices to be set up to handle customer invoices scheduled at set dates for same amount
257ARRecurring BillingSystem allows recurring customer invoices to be set up to handle customer invoices scheduled at set dates for different amounts
258ARRecurring BillingSystem saves templates for generating customer invoices (different template for each AR type)
259ARAgingSystem stores schedule of penalties and interest to apply to open receivables
260ARAgingSystem will apply penalties (or not applied) by type of receivable
261ARAgingSystem will apply penalties as flat fee amounts
262ARAgingSystem will apply penalties as a percentage of the original amount
263ARAgingSystem will apply interest charges monthly
264ARAgingSystem will generate aging reports
265ARCollectionSystem will provide an automated collection workflow
266ARCollectionSystem will provide configurable reminder notices
267ARCollectionSystem will provide collector work queues that prioritize collections by risk or aging
268ARCollectionSystem will provide promise to pay tracking
269ARCustomerSystem stores common customer files that can be used for all system generated invoices
270ARCustomerSystem provides common customer file to be used by third party billing applications
271ARCustomerSystem tracks customer history (example: payment history, adjustments, disputes, collection activity)
272ARCustomerSystem tracks customer address history
273ARCustomerSystem notifies user if payments outstanding when processing accounts payable transaction to same entity/individual
274ARPoint of SaleSystem records payments for point-of-sale items (e.g., no invoices)
275ARPoint of SaleSystem loads AR information from third party systems
276ARPoint of SaleSystem records payments against open receivables
277ARPoint of SaleSystem applies sales tax to point of sale transactions
278ARPoint of SaleSystem updates third party system that invoice has been paid
279ARPoint of SaleSystem provides customer receipts
280ARPoint of SaleSystem records payments with cash, credit, check
281ARPoint of SaleSystem ensures credit card transactions are PCI compliant
282ARPoint of SaleSystem provides web payment option for open receivables
283ARPoint of SaleAllow payments by ACH or Credit Card
284TREASCash ManagementSystem provides cash flow forecasts projecting outstanding payables, outstanding receivables, recurring payments, expected contract payments, and current position
285TREASCash ManagementSystem manages multiple bank accounts (e.g., operating and payroll account)
286TREASCash ManagementSystem manages pooled cash where all funds share cash account and utilize due to / due from accounts
287TREASCash ManagementSystem imports daily bank activity and balances and reconciles to recorded receipts and disbursements
288TREASCash ManagementSystem reconciles both cash/check transactions as well as credit card payments with potential lag in posting date with workflows
289TREASCash ManagementSystem reconciles cleared checks
290TREASCash ManagementSystem provides real time forecasting that incorporates aging payments in its forecast
291TREASACH ManagementSystem will process international ACH transactions
292TREASDebt ManagementSystem will track the City’s debt portfolio
293TREASDebt ManagementSystem will provide integration of Bloomberg data
294TREASDebt ManagementSystem will provide forecasting of liquidity needs, cash balances, existing and future loan need, from multiple banks.
295TREASPayment ReceiptSystem generates deposit slips
296TREASPayment ReceiptSystem routes deposit slips for workflow approval
297TREASPayment ReceiptSystem applies single payments to multiple receivables (customer account and point of sale transactions) regardless of the customer account to which the receivables are assigned
298TREASPayment ReceiptSystem enables using multiple payment methods to pay for one customer invoice (example: cash and credit card)
299TREASPayment ReceiptSystem automatically generates general ledger distribution entries needed to record receipts
300TREASBank ReconciliationSystem receives daily bank activity / balances and reconciles them to recorded receipts and disbursements
301TREASBank ReconciliationSystem will perform bank reconciliation based upon electronic media (daily or monthly data) sent by various banks
302TREASBank ReconciliationSystem clears checks automatically based on bank file data
303TREASBank ReconciliationSystem bank reconciliation process will post receipt/deposit corrections for deposit discrepancies
304TREASBank ReconciliationSystem will generate a list of outstanding checks
305CAAsset AcquisitionSystem will track capitalized items
306CAAsset AcquisitionSystem will enable assets to have multiple account distributions, including multiple funds (e.g., governmental and enterprise funds [including Southern California Public Power Authority, Water, Light, etc.])
307CAAsset AcquisitionSystem will provide parent-child relationships for assets (example: Facility as parent asset and individual components as child assets)
308CAAsset AcquisitionSystem will link component units (parent/child relationship) whereby each component maintains its own financial and historical information and depreciable life
309CAAsset AcquisitionSystem will reference previous asset during asset replacement
310CAAsset AcquisitionSystem will track the useful life of assets
311CAAsset AcquisitionSystem defaults to useful life based on type of asset (vehicle, equipment, facility, etc.)
312CAAsset AcquisitionSystem will track the expiration dates of assets
313CAAsset AcquisitionSystem will track the replacement costs of assets
314CAAsset AcquisitionSystem will track the warranty information of assets
315CAAsset AcquisitionSystem stores photo of asset
316CAAsset AcquisitionSystem enables users to enter unique asset ID tag numbers
317CAAsset AcquisitionSystem will enable assets to identify their custodians (e.g., cell phones identify their users)
318CAAsset AcquisitionSystem links capital assets to purchase requisition, purchase order, and accounts payable transaction
319CAAsset AcquisitionSystem will store GIS information on assets or links to City GIS system for all infrastructure / facility assets
320CAAsset AcquisitionSystem will identify/record all capitalized costs associated with the construction or purchase/acquisition of an asset (from project accounting)
321CAAsset AcquisitionSystem enables users to identify/classify costs as capitalized costs / non capitalized costs
322CAAsset AcquisitionSystem will recognize fixed/capital assets when they are completed, regardless of whether the project has been completed/closed
323CAAsset AcquisitionSystem enables users to enter and track value of donated assets
324CAAsset AcquisitionSystem will track non-capitalized items
325CAAsset AcquisitionSystem will track leased assets
326CAAsset AcquisitionSystem records financial transactions as required by GASB 87 for all leased assets
327CAAsset AcquisitionSystem will track SBITA assets
328CAAsset AcquisitionSystem records financial transactions as required by GASB 96 for all SBITAs
329CAAsset AcquisitionSystem provides conversion entries for government-wide statements.
330CAAsset AcquisitionSystem will track the quantity of assets
331CAProject CapitalizationSystem will move a project to Capital Assets but allow for any subsequent expenditures to be charged to that project
332CAProject CapitalizationSystem will transfer construction-in-progress accounts to capital asset accounts at project close, partial project completion, or completion
333CAProject CapitalizationSystem will enable one project to be converted into multiple assets
334CAProject CapitalizationSystem will eliminate associated budget authority when asset or project is capitalized and moved from a departmental budget
335CADepreciationSupport modified Infrastructure Approached defined by GASB 34
336CAPhysical Asset InventorySystem produces asset list by department for physical inventory
337CAPhysical Asset InventorySystem tracks vehicles, equipment, infrastructure, facilities, and land
338CAPhysical Asset InventorySystem produces asset list by location/department for physical inventory
339CAPhysical Asset InventorySystem produces asset list by custodian for physical inventory
340CAPhysical Asset InventorySystem will enable departments to validate assets are present
341CAPhysical Asset InventorySystem produces asset list of non-capitalized assets by department
342CAPhysical Asset InventorySystem provides asset repots as of specific date
343WOWork OrdersSystem will charge parts, labor, and service charges to individual work orders
344WOWork OrdersSystem will automatically generate Preventive Maintenance work orders based on mileage, hours, or other user-defined criteria
345WOWork OrdersSystem will provide multiple, unique preventative maintenance schedules for stationary equipment, facilities, or pieces of equipment based on user-defined criteria
346WOWork OrdersSystem will re-assign work orders to other technicians, or re-assign for other reasons
347WOWork OrdersSystem will provide work order accessibility via mobile devices
348WOWork OrdersSystem will enable work orders to display and print special instructions
349WOWork OrdersSystem will enter information specific to a job when a work order is created or executed
350WOWork OrdersSystem will assign work orders to individuals or multiple people (e.g., multiple assignments such as Crew chief, workman, etc.) (Please include limitations in the comment field)
351WOWork OrdersSystem will track all dates throughout the work order life cycle (e.g., date received, date scheduled, date started, etc.).
352WOWork OrdersSystem will record the date, time, changes made, and users who made changes to any work order
353WOWork OrdersSystem will link work orders to timesheets to track time to specific work order tasks and projects
354WOWork OrdersSystem will print out work orders for technicians for field use
355WOWork OrdersSystem will create work orders that contain multiple tasks
356WOWork OrdersSystem will produce scheduled work orders on a weekly, monthly, quarterly, and annual basis for facilities and equipment
357CATransfer, Disposal, RetirementUpon disposal, system will calculate partial period depreciation and generate appropriate profit/loss calculation
358CATransfer, Disposal, RetirementUpon disposal system will clear the balance from asset cost, accumulated depreciation, and balance in how acquired for general government assets
359CATransfer, Disposal, RetirementSystem tracks reason for disposal
360CATransfer, Disposal, RetirementSystem stores information on disposed assets
361CATransfer, Disposal, RetirementSystem provides workflow approval/notification for disposed assets
362CATransfer, Disposal, RetirementDisposal tracks revenue from disposal on asset
363CATransfer, Disposal, RetirementSystem notifies users of any restrictions on asset disposal (purchased with federal grant)
364CATransfer, Disposal, RetirementSystem notifies users of upcoming asset expiration dates
365CANon-Capital AssetsSystem tracks non-capitalized assets (e.g., items to be tracked but not capitalized, including assets with valuation below capitalization threshold
366CAAsset EnhancementSystem enables enhancements to asset extending useful life and increasing the value of assets
367CAAsset EnhancementAsset enhancements recalculate depreciation schedules for future depreciation transactions
368CAAsset EnhancementSystem enables staff to edit asset information
369CAAsset EnhancementSystem stores asset impairment information
370CAAsset EnhancementSystem maintains history of all asset changes and edit history by user
371FRFinancial ReportingSystem will produce all necessary reports/schedules for ACFR
372FRFinancial ReportingSystem will prepare, produce, and publish the entire Annual Comprehensive Financial Report (ACFR)
373FRFinancial ReportingSystem will produce the ACFR to be compliant with applicable disability standards
374FRFinancial ReportingSystem will produce the Popular Annual Financial Report
375FRFinancial ReportingSystem will produce monthly close
376FRFinancial ReportingSystem will produce annual close
377FRFinancial ReportingSystem will produce State Controllers Report information
378IMProcessSystem will integrate with existing Inventory Management System (e.g., Ward, WAM, etc.)
379IMProcessSystem will periodically generate random cycle counts to ensure accurate counts
380IMProcessSystem will support multiple inventory cost methods, including standard and average costing

Budget Attachment 6 - Acceptance Requirements

Req #Functional AreaProcessUser Story RequirementResponseModule / SystemPhaseComment
1BUDBudget PlanningSystem enables users to establish multiple versions of the budget
2BUDBudget PlanningSystem will support multi-year budgeting
3BUDBudget PlanningSystem will support budgeting by sub-year (quarter or month)
4BUDBudget PlanningSystem will separate budget categories between operating and growth costs for all enterprise funds if not all budget strings
5BUDBudget PlanningSystem enables budget staff to set up “standard costs” so that certain budgets are auto calculated. (e.g., Travel & Training, Cell Phones, Computers, etc.)
6BUDRevenue BudgetSystem will forecast City major revenue sources
7BUDRevenue BudgetSystem provides forecast capabilities using activity levels
8BUDRevenue BudgetSystem provides forecast capabilities using external information
9BUDRevenue BudgetSystem provides long-term forecast for revenue
10BUDBudget RequestSystem enables users to view multiple years of actual and budget data while preparing budget requests
11BUDBudget RequestSystem enables departments to enter budget requests, including requested budget amounts
12BUDBudget RequestSystem enables departments to enter justifications / explanations of changes from previous year’s budget requests
13BUDBudget RequestSystem enables departments to enter budgets for department/division/program up to target budget amount
14BUDBudget RequestSystem will prepare & submit budgets for revenues and expenses
15BUDBudget RequestSystem enables departments to enter department and narrative information along with budget requests (e.g., program goals, challenges, highlights of major changes, etc.)
16BUDBudget RequestDepartments can attach documents to budget request line items
17BUDBudget RequestDepartments can enter notes/justification for budget requests
18BUDBudget RequestDepartments can enter information on service level (or what is proposed for budgeted program)
19BUDBudget RequestSystem enables budget requests to be grouped into decision packages (multiple line items that go together)
20BUDBudget RequestSystem enables users and/or budget team to create different budget projections/scenarios (e.g., what if 5% cut)
21BUDBudget RequestUsers can flag one-time budget events, and the system automatically removes them from the next years' budget
22BUDBudget RequestSystem will identify new budget requests
23BUDPersonnel BudgetingSystem projects and budgets tax and benefit costs based on current regular employee salary and current benefit elections
24BUDPersonnel BudgetingSystem projects and budgets tax and benefit costs based on position salary range and default benefit elections
25BUDPersonnel BudgetingSystem enables users to propose new positions in proposed budgets
26BUDPersonnel BudgetingSystem enables users to propose changing position status as part of budget development (funded - unfunded positions)
27BUDPersonnel BudgetingSystem will allocate position costs to multiple segments of the Chart of Accounts (i.e. organizational codes, programs, projects, grants, etc.)

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 .