.png?sv=2022-11-02&ss=b&srt=o&spr=https&st=2024-04-16T15%3A10%3A11Z&se=2024-04-16T15%3A20%3A11Z&sp=r&sig=RU4eeavgtCM%2BI65J2ES8f7Spv1q18cTLOJ945mRrx30%3D){kind=logo}
Time Entry Validation
- 18 Aug 2023
- Print
- PDF
Time Entry Validation
- Updated on 18 Aug 2023
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
When you accept time by selecting Save, Aspire verifies that no work ticket end time occurs later than the latest clock time for any user on the work ticket time entry.
This can be best explained by the example below. If the following clock-time entries were entered on the time entry screen:
Clock Time
| Clock Entry | Clock In | Clock Out | User |
|---|---|---|---|
| Clock 1 | 08:00 | 11:00 | Joe |
| Clock 1 | 12:00 | 16:00 | Joe |
The validity of work ticket time entries would be determined as follows:
Work Ticket Time
| Validity | Start Time | End Time | User | Rationale |
|---|---|---|---|---|
| Valid | 9:00 | 10:00 | Joe | Work ticket time stopped before 16:00 - the last clock-out for that user |
| Valid | 07:00 | 01:00 | Joe | Work ticket time stopped before 16:00 - the last clock-out for that user |
| Invalid | 08:30 | 16:05 | Joe | Work ticket time stopped after 16:00 - the last clock-out for that user |
If you enter invalid values, Aspire displays a warning message.
Rows for which the work ticket stop time extends beyond the last clock-out time for a user are shown in red. The work-ticket time entries for the affected users are shown in light green.
Was this article helpful?