|
|
|
|
The Unanet system uses a series of Statuses in order to keep track of where a particular Timesheet, Leave Requests, Expense Report or Expense Request is located in the approval process. The list of possible statuses includes:
Timesheet and Expense Report Statuses
MISSING
INUSE
SUBMITTED
APPROVING
COMPLETED
DISAPPROVED
EXTRACTED
EXTRACTED (historical)
LOCKED
LOCKED (historical)
INUSE (Adjustments)
SUBMITTED (Adjustments)
APPROVING (Adjustments)
COMPLETED (Adjustments)
DISAPPROVED (Adjustments)
Expense Request Statuses
REQUESTING
PREAPPROVING
AUTHORIZATION_APPROVED
DENIED
Leave Request Statuses
INUSE
SUBMITTED
APPROVING
DISAPPROVED
COMPLETED
LOCKED
CANCELED
The following sections provide a description of these various statuses and which areas of the system they apply, including:
If a user has not created a timesheet for a time-period, the timesheet will be listed as MISSING in the system.
As soon as the user creates a timesheet the status will be changed to INUSE.
This status will be maintained until the user presses the submit button and sends the timesheet for approval. At this point, the status of the timesheet may vary depending on whether the particular timesheet is subject to any approvals. If it is not, then the timesheet status would be set directly to COMPLETED. More commonly though, the timesheet may require some level of approval and thus the new status would be set to SUBMITTED. The status would stay in the submitted status until the first person in the approval process approves the timesheet.
Once the first person (whether it be a Manager, a Project Manager or a Customer) approves a timesheet, the status will be updated to APPROVING. The status will remain in the APPROVING state until all pending approvals have been completed.
At this point, the status will then be set to COMPLETED.
If the user chooses to edit the timesheet at any time during the approval process period, the timesheet can be withdrawn from the approval process and the status will be returned to INUSE. This timesheet would need to go through the entire approval process again.
If any approver disapproves the timesheet, the status will be set to DISAPPROVED. The timesheet would remain in this state until the user re-opens, edits, and saves the timesheet. At this point the timesheet will then go back to a status of INUSE.
If the Administrator extracts the timesheet from the system, the status will be set to EXTRACTED. Extracted timesheets are essentially frozen from any further manipulation by end users. In order to make changes to an Extracted timesheet, you would need to either use the Administrator Timesheet Adjustment feature, or enable the End User Timesheet Adjustment feature.
The LOCKED Status is a status between the COMPLETED and EXTRACTED status. It is NOT used by default, but can be enabled by enabling the Auto-Lock feature (Set Timesheets to Locked Upon Completion (unatime.autolock). When this status is enabled, timesheets immediately move to a LOCKED status upon completion. Once in the LOCKED status, timesheets are treated as if they are EXTRACTED, meaning any further changes to the timesheet will require either Administrative adjustments (the timesheet can no longer be pulled back to INUSE by anyone).
The LOCKED and EXTRACTED statuses may have a trailing (historical) indicator if the time associated with a particular time period was loaded via the Historical Time Import. Timesheets in these statuses cannot be manipulated via the user interface (though they can be deleted via the Historical Time Import - so long as the time has not be included in a Labor Cost Post or Billing and Revenue Post.
If the end user adjustment feature is being utilized, an extracted timesheet may be adjusted by an end user. These timesheets follow a similar approval process and the timesheet may be in any of the following statuses:
INUSE (Adjustments)
SUBMITTED (Adjustments)
APPROVING (Adjustments)
COMPLETED (Adjustments)
DISAPPROVED (Adjustments)
When a user creates an Expense Report the status is initially set to INUSE.
Once the user submits the Expense Report, the status is set to SUBMITTED.
Once the first person in the approval group approves an Expense Report it is set to a status of APPROVING.
If any approver disapproves the Expense Report, the status will be set to DISAPPROVED until the user edits and re-saves the Expense Report details. The status would once again be set to INUSE.
After the last person in the approval group has approved the Expense Report the status is set to COMPLETED (expense reports in this status can continue to be pulled back to INUSE for further editing).
If the Administrator extracts the expense from the system, the status will be set to EXTRACTED.
The LOCKED status is used if the Administrator would like to lock the expense reports so that it cannot be opened by the user again to edit, but to note that the expense report also has not been extracted yet. This status is used as an in-between status of COMPLETED and EXTRACTED. Expense Reports can be automatically set to the LOCKED status immediately following the event that set it to the COMPLETED if the Auto-Lock feature (Set Expense Reports to Locked Upon Completion (unasense.autolock)) is enabled.
Note that LOCKED or EXTRACTED expenses can be removed from the system via the Expense Import (so long as none of the line items have been included in the Expense Report Cost Post or the Billing & Revenue Post or a vendor invoice has been created from the expense report via the Create Vendor Invoice from Expense Report process). Otherwise, any further changes to that data would need to be in the form of an adjusting expense report.
If a user creates an Expense Request, the initial status is set to REQUESTING until the submit button is pressed at which point the status becomes PREAPPROVING.
The status remains PREAPPROVING until the last manager has approved the Expense Request.
At that point, the status becomes AUTHORIZATION_APPROVED in the Expense Request history and INUSE as a new Expense Report.
If a manager disapproves the Expense Request, the status will be set to DENIED until the user edits and re-saves the Expense Details, at which point the status would return to REQUESTING again.
As soon as the user creates a leave request the status will be set to INUSE.
This status will be maintained until the user presses the submit button and sends the leave request for approval. At this point, the status of the leave request may vary depending on whether the particular leave request is subject to any approvals. If it is not, then the leave request status would be set directly to COMPLETED. More commonly though, the leave request may require some level of approval and thus the new status would be set to SUBMITTED. The status would stay in the submitted status until the first person in the approval process approves the leave request .
Once the first person (whether it be a Manager or an Administrator) approves a leave request, the status will be updated to APPROVING. The status will remain in the APPROVING state until all pending approvals have been completed.
Once all approvals have been satisfied, the status will then be set to COMPLETED.
If the user chooses to edit the leave request at any time during the approval process period, the leave request can be withdrawn from the approval process and the status will be returned to INUSE. This leave request would need to go through the entire approval process again.
If any approver disapproves the leave request, the status will be set to DISAPPROVED. The leave request would remain in this state until the user re-opens, edits, and saves the leave request. At this point the leave request will then go back to a status of INUSE.
The LOCKED Status can also be used to prevent further change to a leave request. This status is NOT used by default, but can be enabled via the Auto-Lock feature ( Set Leave Requests to Locked Upon Completion (unatime.leave_request.autolock)). When this status is enabled, leave requests immediately move to a LOCKED status upon completion. Once in the LOCKED status the leave request can no longer be pulled back to INUSE by anyone.
If a user decides to not take leave after a leave request has been approved, they can cancel the request, at which point the status will be CANCELED.
