Browse
Search
Agenda - 06-14-2001-4d
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2000's
>
2001
>
Agenda - 06-14-2001
>
Agenda - 06-14-2001-4d
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/29/2008 2:21:00 PM
Creation date
8/29/2008 10:33:00 AM
Metadata
Fields
Template:
BOCC
Date
6/14/2001
Document Type
Agenda
Agenda Item
4d
Document Relationships
Minutes - 06-14-2001
(Linked To)
Path:
\Board of County Commissioners\Minutes - Approved\2000's\2001
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
54
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
.Orange County <br />Needs Assessment Project <br />PAYROLL: <br />Page 11 <br />Issue 1: All off-cycle adjustments must be calculated and entered manually. Retroactive <br />pay adjustments and wage calculations for new employees starting during the pay cycle <br />are two. examples of manual processing that would be automated in an updated payroll <br />system. <br />Issue 2: For same departments, employee travel expenses can be required to be <br />manually reported on up to six (6) sepazate farms. A flexible reporting tool would allow <br />the County to create a travel template for recording employee expenses, reducing the <br />number of paper forms generated. The appropriate supervisor would approve the report <br />electronically. <br />Issue 3: The yeaz-end payroll accrual is currently being performed manually. This is a <br />labor-intensive process that is an automated function in most new payroll softwaze <br />applications. <br />Issue 4: All adjustments to employee W-2 forms must be handled manually in the <br />existing system. This is critical information that is supplied to the employee, the IRS, <br />and all other applicable government entities. The automation of this process .would <br />reduce the possibility of issuing an incorrect farm. <br />PURCHASING: <br />Issue 1: Purchase requisitions are created by the departments and sent to Purchasing far <br />processing. While the requisition form may be automated through a desktop application, <br />it is not integrated into any part of the existing financial system until a purchase order is <br />actually cut by the Purchasing Department. Since the present system provides no <br />tracking capability the actual status of a requisition in transit cannot be determined. This <br />presents the opportunity for significant delays of an order. A standazd purchase order <br />system, installed on a network, would allow for the electronic submission, approval and <br />tracking of all orders. <br />Issue 2: Information submitted on purchase requisitions is often inaccurate and/or <br />incomplete, which requires additional Purchasing staff.time to verify such information as <br />account numbers and/or account balances. Further, it involves time for the Budget Office <br />as well, since the status of any pending budget transfers is determined prior to returning <br />the order to the originating department. A purchase order system could be configured to <br />require a correct account number and budgeted funds before allowing the request to be <br />forwazded to Purchasing. <br />Issue 3: Vendor applications must be entered and maintained manually by Purchasing <br />department personnel. Additionally, since the Purchasing system does not maintain a <br />commodity code listing, the vendor is required to enter a descriptive list of its goods or <br />service offerings. This process results in additional manual entry and a vendor database <br />
The URL can be used to link to this page
Your browser does not support the video tag.