Timesheet Status

This document outlines the standardized Timesheet Status workflow across all platforms including Aqore Zen Time, Mobile Application, Contact Portal, Employee Portal, Office Staff Portal, and others. The document is segregated in terms of Actors who are Employee, Contact and Office Staff. Likewise, System explains the state of the transaction before any changes are made to them by any users.

System

Action	New Status
Transaction Created Initially by the System	New

Employee

Action	New Status
Employee Enters hours from Employee Portal	Pending
Employee Sends time entry for approval	Pending for Approval
Employee Clocks In or Punches In time from Time Clock or Aqore ZenTime	Pending for Approval

Contact

Action	New Status
Contact Enters Hours or edits them through Contact Portal.	Pending for Approval
Contact Rejects Hours from Contact Portal.	Rejected.
Contact Approves Hours from Contact Portal.	Approved and submitted
Contact Enters or Edits hours from Time Clock or Admin Summary	Pending for Approval
Contact Approves hours from Time Clock or Admin Summary	Approved and submitted
Contact Rejects hours from Time Clock or Admin Summary	Rejected.

Office Staff

Action	New Status
Office Staff enters or edits hours from TMS> Timesheet or Work Board	Pending
Office Staff edits a rejected Time Entry	Pending
Office Staff updates transaction with status Approved and Submitted	Approved and submitted
Office Staff updates transaction with status Submitted	Submitted
Office Staff runs/views Transaction Batch Report	No Change in Status
Office Staff closes Transaction Batch	Submitted

Batch Status of Transaction

The batch status of transaction explains how defined actions update the status of the Transaction Batch.

Condition	Status
Initial Status	Open
After Transaction Batch is Closed	Closed
Transactions are tagged in at least one of the Payroll or Invoice Batch	Processing
When Transactions have both Payroll and Invoice completed.	Completed

Additional Notes

The Timesheet Status behavior is consistent across all platforms.
Status changes are triggered by user actions or system processes as described.