User Interface
- Accessing the system from any networked workstation running Windows XP or Windows Vista operating system
- Shortcuts to frequently used screens, operations, account strings, etc., with different shortcuts for different types of users
- Viewing only the fields that are relevant to a particular task and user
- Using pick lists and searches
- Showing several attributes for each item on the list
- Filtering the list based on user-selected criteria
- Listing only items that are valid or authorized, so that after the user chooses one it will pass data validation
- Having some fields pre-populated with default values
- Entering a transaction for a future effective date
- Entering a future transaction to an account that is not yet active
- Ensuring that only valid data is entered
- Allowing only valid values for a field
- Allowing only valid combinations between fields—for example: a particular program may be valid for only one particular department; particular accounts may be valid only for particular types of transactions, etc.
- Restricting certain users to certain account objects, funds, etc.
- Preventing a transaction from being entered when the transaction date is before the effective date for an account, organization, project, etc., or after the inactive date for an account, organization, project, etc.
- Validating data right at the point where data is entered into the system
- Detecting potential duplicate journal entries, invoices, requisitions, vendors, customers, etc.
- Saving a partially completed form (such as a requisition) before submitting it for further processing, so that it can be retrieved, edited, and submitted at a later time
- Correcting previously posted transactions, generating adjusting entries with cross-references between original and correcting transactions
- Viewing complete information about a project, work order, employee, vendor, etc.—including current status, balances, history, etc.
- Customizing screens to hide unused objects
- Online help
- Context-sensitive help for fields or blocks on a screen
- Tool-tips (also called cursor-hovers and mouse-overs) for fields and icons on a screen
- Microsoft Excel interface
- Downloading data into a spreadsheet
- Uploading data from a spreadsheet into a journal entry, purchase order, budget, etc.
- Accessing timekeeping via telephone keypads (future implementation)
- Accessing some system functions via the Internet, with appropriate security (future implementation)
Attached Files
- Attaching files (.doc, .jpg, .pdf, etc.) to a purchase order, payment, receivable, work order, master-file record, etc.
Workflow
- Workflows for the following business processes:
- Budget development
- Budget transfers
- Purchasing—submitting and approving requisitions; soliciting bids; issuing purchase orders; authorizing and making payments
- Paying invoices for non-purchase-order items
- Personnel actions
- Employee-performance appraisals
- Leave-of-absence requests
- Submitting and approving timesheets
- FMLA processing—letters sent, medical certification of the illness, expiration dates, etc.
- Tuition reimbursements
- Work order request, approval, assignment, completion, and closure
- Building permits
- Workflow administration to set up queues, routing, business rules, etc.
Data Analysis and Reporting
- Running standard (“canned”) reports
- Adding, deleting, and modifying standard reports
- Creating ad-hoc reports and running ad-hoc queries (with user-selected data fields, values, date ranges, etc.)
- Using an Excel spreadsheet (with the Microsoft Query add-in feature) to query data, and subsequently re-running the query to update (refresh) the spreadsheet (also see item # 14)
Access Control
- Limiting users to authorized functions, screens, data, funds, and accounts
- Restricting users to view only transactions for their own department
- Preventing users from charging purchases and labor time to inappropriate accounts
- Restricting what functions can be accessed from outside the City’s physical network (if Internet access is implemented in the future)
External Electronic Interchange
- Electronically sending and receiving business-to-business transaction documents, such as purchase orders and invoices, with external parties who are set up to do this
Chart of Accounts
- Employing a chart of accounts that identifies:
- Fund
- Organization: departments, with some departments divided into divisions
- Object: breakdown of expenses, assets, etc. into categories such as salaries, benefits, office supplies, etc.
- Program, with some programs divided into activities
- Project, with some projects divided into phases, sub-projects, tasks, or milestones
General Ledger
- Setting up fiscal years (July 1 to June 30) and accounting periods (13 or more periods)
- Making journal entries
- One-time
- Recurring
- Statistical
- Setting up a template for a frequently used journal entry that spreads an amount among multiple accounts, so that when the template is called up and an amount entered, the template spreads that amount among the accounts
- Automatically reversing journal entries for accruals
- Cross-referencing correcting journal entries with the previous entries that are being corrected, with the cross-reference data available in report-writing
- Rolling up accounting data from lower levels in a parent-child tree to higher levels, and drilling down from higher to lower levels
- Distinguishing the transaction date (when money actually changed hands, a purchase order was issued, etc.) from the posting date (when system processed the data)
- Apportioning transactions among multiple funds, based on formulas or business rules
- Cost accounting
- Distributing purchases, payments, and labor costs to organizations, programs, activities, and projects
- Apportioning “general” time (timesheet hours that are not charged to a particular project or work order) among multiple programs, based on the programs’ funding percentages for that position
Fund, Grant, and Project Accounting
- Fund accounting
- Project accounting
- Project budgeting and allocation when a project is funded from multiple funds
- Budgeting by tasks or milestone payments
- Applying formulas or algorithms for apportioning project costs to funds, so that accurate project/fund balances can be maintained
- Tracking project status
- Tracking deposits due, activities, costs, fees, payments (or receipts), and balances for projects that are to be paid:
- By external parties to the City (also see # 89)
- By the City to external parties
- Multi-year projects
- Grant accounting
- Tracking the grant-funding process: grant money budgeted, awarded, spent on reimbursable costs, matched with matching funds, claimed (reimbursement requests), and received—across multiple years
- Track reimbursable costs
- Applying a single grant’s funds across multiple organizations, programs, and projects
- Applying multiple grants to a fund, organization, program, or project
- Appropriately charging employee benefit costs to the grant that is fully or partially funding the employee’s position
- When an employee’s position is grant-funded, associating that position or employee with a “home program” so that when the grant fund is maxed out any subsequent payroll cost is charged to the home program
- Multi-year grants
Budgeting
- Developing budgets on a two-year cycle
- Calculating salary and benefit budgets based on human-resource and position-control data:
- Authorized and funded positions, which may be limited to particular date ranges
- Position grades, which may change on particular dates
- Current pay of position incumbents
- Projected future dates for transfers, promotions, vacancies, and hires
- Supporting business rules about how to deal with delayed spending that crosses into the next fiscal year—for example, encumbered funds in open purchase orders are automatically carried over to the next fiscal year, but unencumbered money needs to be re-justified and re-budgeted
- Supporting business rules about the process of budget transfers and adjustments during the current budget year (after the budget has been adopted)—for example, departments can transfer salary savings into contract labor, but other transfers within a department need City Manager approval, and interdepartmental transfers need City Council approval (see the “Workflow” section of this report)
- Tracking changes from the original adopted budget to the current budget
- Projecting the budget impact of a hypothetical change in compensation rates, etc. (“what-if” scenarios)
Purchasing
- Maintaining a vendor master file
- Subdividing a vendor into multiple branches or remittance addresses, so that when a vendor is selected for a purchase order, the branches are displayed and one is selected
- Referencing a vendor by multiple doing-business-as (DBA) names and historical name changes
- Setting up vendor payment methods including electronic payments
- Checking for duplicate records in the vendor master file
- Associating commodity codes to vendors to facilitate bid and RFP distribution
- Vendor self-service for registering as a vendor in the City’s system, maintaining the vendor’s business information, viewing and responding to bid solicitations, etc.
- Preparing and submitting requisitions
- Searching and copying items from previous purchase orders
- Selecting commodity codes for items requisitioned
- Splitting charges among several organizations, programs, projects, tasks, or work orders
- Preventing requisitions from being entered if:
- There is insufficient money remaining in the budget line for each line item (budget amount minus amounts spent, encumbered, and pre-encumbered)
- The requestor is not authorized to charge against the account selected
- The commodity or fixed asset type is not consistent with the account selected
- Routing requisitions through a workflow for multiple approval steps depending on the dollar-limit authority of approvers, the type of commodity, etc.
- When a requisition is approved, pre-encumbering funds so that they are no longer available for any subsequent requisitions
- If the requisition is later cancelled, reversing the pre-encumbrance so the funds become available again
- If the dollar amount of the requisition is changed, correspondingly changing the pre-encumbrance
- Inquiring into the status of a requisition, including approval status, purchasing status, and payable status
- Querying the system to see prior orders, to aid in re-ordering
- Flagging fixed assets so that they are automatically entered in the fixed-assets register when received
- Indicating the fixed asset that is to be replaced by the requisitioned item, so that the new asset is linked to the asset it replaced, and as a reminder to track the old asset’s disposition
- Preparing and releasing purchase orders
- Recombining requisitions into purchase orders with a “many-to-many relationship” between requisitions and purchase orders
- Choosing between either:
- Charging the whole purchase order to one chart-of-accounts value
- Charging each line item to a different chart-of-accounts value
- Apportioning (distributing) sales and use tax to each line item
- Splitting purchasing charges among several organizations, programs, projects, tasks, or work orders
- For the whole purchase order
- For one line item on a purchase order
- Setting up a purchase order to span multiple fiscal years for multi-year contracts
- Adding state sales or use tax if applicable
- Processing change orders, using the same procedures as new orders, including approvals and encumbrance
- Encumbering funds when a purchase order is released, and adjusting or relieving encumbrances when the purchase order is closed or change orders are issued
- Issuing blanket purchase orders to set up terms for future releases drawn against the blanket orders
- Choosing whether to fully encumber a blanket order when it is issued (“up-front encumbrance”), versus to encumber releases when they are drawn against the blanket order (“as-you-go encumbrance”)
- Tracking requirements for vendor insurance, performance bond, licenses, and certification that apply to a purchase order, and tracking vendor compliance with those requirements (tickler function)
- Receiving purchased items into service, inventory, or fixed-assets register
- Receiving a partial shipment, indicating backorders and/or order-quantity adjustments
- At the end of the fiscal year, carrying outstanding encumbrances into the next fiscal year (after reviewing and closing purchase orders that are not to be rolled forward)—also see Functional need 44
- Tracking purchases employees make using City credit cards, so that this information fits into the same framework as other purchases
- Importing credit-card transaction data from the bank
Materials Inventory
- Receiving items into inventory
- Issuing stock to end-user departments
- Controlling inventory at multiple locations including a central warehouse, departmental storerooms, job sites, trucks, etc.
- Performing physical inventory counts
- Calculating the value of materials based on actual cost
- Returning inventory to stock or transferring inventory between locations
- Maintaining and communicating information about hazardous materials, recyclable materials, etc.
- MSDS (material safety data sheets)
Accounts Payable and Disbursements
- Issuing payments for items purchased via purchase order
- Associating a payment with a purchase-order line
- Avoiding redundant data entry for information that is already on the associated purchase order
- Applying the discounts or payment terms on the purchase order
- Accounting for deposits and holdbacks (retentions)
- Splitting a payment among several purchase orders, work orders, projects, tasks, organizations, programs, or accounts (when the purchase order is general and the invoice shows finer detail about items delivered)
- Paying state use tax when applicable
- Recovering reimbursable costs—see # 89
- Paying invoices for non-purchase-order items
- Splitting charges among several funds, organizations, programs, projects, tasks, or work orders
- Combining several invoices into one check
- Ensuring against duplicate payments
- Querying the system for ordering and payment histories to see who paid what to whom, when, for what
- Warning for duplicate invoice numbers (but not preventing the user from paying when appropriate)
- Preventing payments from exceeding budgeted funds
- Making recurring payments
- Using templates—see # 32
- Making corrections after invoices have been posted
- Scheduling daily check runs and issuing checks(
- Positive pay—sending the check data to the bank when the check is cut
- Sending electronic payments (electronic fund transfers, wire transfers, e-checks, ACH, etc.)
- Dealing with lost checks
- Voiding
- Reissuing
- Importing check-clearing data from the bank
- Reconciling bank statements
- Tracing a purchasing or disbursement trail—starting from any point in the process, tracing backward to the initiation action (such as a requisition), and forward to checks and fixed-asset records
- Viewing the status of all items in the purchasing process “pipeline”
- Issuing 1099’s
- Administering petty cash
Employee Travel Advances and Reimbursements
- Administering employee expense accounts, advances, and reimbursements
- Travel expenses
- Tuition reimbursement
- Deducting taxes for taxable tuition reimbursements—see # I.A.46
- For travel expenses, showing an overall trip cost along with a detail breakdown:
- By employee (traveler)
- By expense category (lodging, airfare, conference fees, etc.)
- By purchasing method (City credit card, employee reimbursement, purchase order, non-PO invoice, etc.)
Accounts Receivable
- Entering receivables, deposits, payments, and credits
- Setting up recurring receivables
- Generating receivables based on recoverable (reimbursable) costs
- Using projects and work orders to identify recoverable costs
- Associating specific expenditures and labor charges with cost-recoverable projects and work orders
- Tracing cost-recovery receivables to their source work orders, timesheets, purchases, etc.
- Updating cost-recovery receivables when the source transactions are reversed, corrected, or changed
- Generating and presenting invoices, statements, and remittance advice
- Paper bill presentment
- Electronic bill presentment
- Fax bill presentment
- Processing retroactive adjustments to receivables
- Viewing or printing bills that have been previously sent
- Setting up ticklers—for example, if a customer promises to pay in 10 days, setting up a tickler to remind a user to call the customer in 10 days to confirm that payment was sent
- Issue delinquent billings for overdue invoices
- Issue complete customer statements showing past-due invoices and related penalties, as well as payments received
Cash Receipts (Cashiering)
- Recording cash receipts and applying cash
- Handling credit-card payments
- Over-the-counter
- Web/online
- Splitting a cash receipt among multiple tender types (cash, credit card, etc.)
- Splitting a cash receipt among several receivables
- Searching for the proper receivable(s) for cash application, when cash is received without a clear reference to one particular receivable
- Reapplying misapplied cash receipts, with appropriate cross-referencing
- Cash-register function (for Library)
- Closing out cash drawers
- Recording bank deposits
- Issuing refunds and credits
- Handling bad checks
Human Resources
- Establishing and updating the basic personnel structure, made up of:
- Bargaining units
- Position grades within each bargaining unit
- Steps within each position grade
- Compensation rates (dollars per hour/week/month/year) for each step in each position grade