> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/digitalworkers/ifs-loops-digital-workers/digital-worker-guides/time-entry-manager/faq.md).

# FAQ

## Capabilities & functionality&#x20;

**Q: What does the Time Entry Manager do?**&#x20;

A: The Time Entry Manager is a Digital Worker that prepares and submits project time reports in IFS Cloud. It uses an employee’s historical time reporting patterns to identify likely activities and estimate hours, validates those entries against activities and report codes valid for the employee and date, and automatically submits the resulting Project and MCPR time entries.&#x20;

**Q: How does the Time Entry Manager know which activities to suggest?**&#x20;

A: It reads an employee’s actual reporting history and ranks the activity and report code combinations they use most, weighted toward what they’ve done most recently.&#x20;

**Q: Can historical patterns cause an invalid code to be submitted?**&#x20;

A: No. Historical activity is used to rank and estimate entries, but it never overrides activity or report-code validity for the target date. Codes expire and assignments change, so validity is checked against the current date every time.&#x20;

**Q: Does the Time Entry Manager account for hours an employee already reported?**&#x20;

A: Yes. It weighs scheduled hours and time already reported, keeping estimates limited to what’s actually left to report for the target day.&#x20;

**Q: What happens when an employee can’t be resolved or information is missing?**&#x20;

A: The affected timesheet is held back rather than submitted incomplete, so nothing goes through with gaps.&#x20;

## Control & Collaboration&#x20;

**Q: Does a manager approve entries directly from the Digital Worker’s output?**&#x20;

A: No. Entries are submitted, not confirmed. The employee verifies and corrects any incorrect line first, and only then does the timesheet move on for manager approval.&#x20;

**Q: How does an employee review what the Time Entry Manager submitted?**&#x20;

A: A confirmation email is sent with an embedded button that takes the employee straight to their time entry page, where they can make any necessary edits before the entries go further.&#x20;

**Q: Why does verification happen before manager approval rather than after?**&#x20;

A: Requiring employee verification prior to manager approval ensures every entry is appropriately cross-checked: the person who did the work confirms what the record says before their manager reviews it.&#x20;

**Q: Does one employee’s issue delay the rest of the team?**&#x20;

A: No. Every employee and date is processed independently, so a record that needs additional human review never holds up entries already approved for someone else.&#x20;

## Integration & Technology&#x20;

**Q: What does the Time Entry Manager integrate with?**&#x20;

A: It integrates with IFS Cloud for employee, project, activity, report code, and time reporting data, and with email, such as Microsoft Outlook, for submission notifications.&#x20;

**Q: What triggers the Time Entry Manager to process a timesheet?**&#x20;

A: A predetermined schedule, so no manual trigger is required, or a user-initiated request for the signed-in employee, a named employee, or a manager processing their direct reports.&#x20;

**Q: What IFS Cloud components does the Time Entry Manager rely on?**&#x20;

A: Personnel file data, time registration and report time management, project activity lists, and valid report code data, alongside the underlying employee, project, and time reporting configuration.&#x20;

**Q: How are submission outcomes reported?**&#x20;

A: Successful, partial, and failed outcomes are reported individually for every employee and date processed, maintaining visibility across both individual and team-level runs.&#x20;

## Security & Reliability&#x20;

**Q: Can the Time Entry Manager submit a timesheet with missing required information?**&#x20;

A: No. Where an employee can’t be uniquely resolved or required reporting information is unavailable, the timesheet is not automatically submitted.&#x20;

**Q: What happens if one employee’s processing fails?**&#x20;

A: It doesn’t stop the rest. Employee/date combinations are processed independently, so a failure for one does not stop the remaining timesheets from being processed.&#x20;

**Q: Is there a check against outdated activity or report codes?**&#x20;

A: Yes. Every suggested entry is validated against the activities and report codes currently valid for that employee and date, regardless of what the historical pattern suggested.&#x20;

**Q: How is limited reporting history handled?**&#x20;

A: Limited or unavailable reporting history results in fewer suggestions or lower-confidence estimates, rather than the system filling gaps with an unsupported guess.&#x20;

## Customization & Performance&#x20;

**Q: Can the Time Entry Manager process an entire team at once?**&#x20;

A: Yes. A manager can have the worker process their direct reports as a team, with each employee and date handled independently so timesheets can be processed in parallel.&#x20;

**Q: Does the Time Entry Manager work for both Project and MCPR time?**&#x20;

A: Yes. Generated entries cover both Project and MCPR time reporting.&#x20;

**Q: What reduces the correction cycles that used to follow a timesheet review?**&#x20;

A: Validating suggested entries against valid activities and report codes before submission, combined with the employee’s own verification step, catches issues before they ever reach a manager for review.&#x20;

**Q: What are the five core capabilities behind the Time Entry Manager?**&#x20;

A: Intelligent Timesheet Generation, Activity & Report Code Validation, Employee & Team Processing, Working Hours Awareness, and Automated Time Submission & Notifications. Together, they take an employee’s reporting history through to a verified, submitted timesheet.&#x20;