> 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/releasenotes/release-notes/digital-workers-release-notes/time-entry-manager.md).

# Time Entry Manager

{% updates format="full" %}
{% update date="2026-09-15" %}

## Product Overview

* **Digital Worker Name:** Time Entry Manager 1.0 
* **Release Version:** Q3 2026 
* **Release Date:** Sep 15th, 2026 

### **What's New**

This release introduces the Time Entry Manager Digital Worker, a new autonomous worker that prepares and submits project time reports in IFS Cloud. 

It uses historical time reporting patterns to identify likely activities and estimate hours, validates the suggested entries against available reporting data, and automatically submits the resulting timesheet for employees or teams. 

**What’s new at a glance:** 

* **Intelligent Timesheet Generation** identifies likely time reporting activities and estimates hours using historical reporting patterns.  
* **Activity & Report Code Validation** ensures generated entries use activities and report codes that are valid for the employee and target date.  
* **Automated Time Submission** submits generated Project and MCPR time entries directly to IFS Cloud.  
* **Employee & Team Processing** supports time reporting for the signed-in employee, named employees, and managers acting on behalf of direct reports.  
* **Working Hours Awareness** considers scheduled hours, existing reported time, and the target working day when generating time entries.  
* **Concurrent Team Processing** processes each employee and date independently, allowing team timesheets to be handled in parallel.  
* **Submission Notifications** communicate the resulting time entries and submission outcome to the applicable employee. 

### Changes in Product Offering

<details>

<summary><strong>New or Enhanced Functionality</strong></summary>

This release introduces the Time Entry Manager Digital Worker as a new capability in the IFS Loops ecosystem, automating timesheet generation and submission for employees and teams using historical reporting patterns and validated IFS Cloud data.

</details>

<details>

<summary><strong>Deprecated Functions</strong></summary>

Not applicable.

</details>

<details>

<summary><strong>Removed Functions</strong></summary>

Not applicable.

</details>

### Release Scope & Constraints&#x20;

This section outlines the supported time generation, submission, and team processing scenarios for the Time Entry Manager Digital Worker.

**Supported Time Entry Management Scope**

The Digital Worker supports automated time reporting with the following characteristics:

<details>

<summary><strong>Trigger &#x26; Employee Scope:</strong></summary>

* Scheduled execution through the configured trigger or user-initiated processing
* Processing for the signed-in employee or a specified employee
* Manager-on-behalf processing for direct reports
* Independent processing of each employee and target date

</details>

<details>

<summary><strong>Timesheet Generation Scope:</strong></summary>

* Generation of Project and MCPR time reporting entries
* Selection of likely activities and report codes using historical reporting patterns
* Recency and occurrence-based ranking of previous reporting activity
* Estimated hours based on available historical reporting evidence
* Validation against activities and report codes valid for the employee and target date

</details>

<details>

<summary><strong>Time Submission Scope:</strong></summary>

* Automatic submission of generated time entries to IFS Cloud
* Consideration of existing reported time, absence requests and available working hours
* Independent submission outcomes for each employee and date
* Support for partial processing where individual entries or employees cannot be completed

</details>

<details>

<summary><strong>Communication Channels:</strong></summary>

* Human-in-the-loop validation outcomes, exceptions, and approval interactions through the configured communication channel

</details>

**Known Limitations & Edge Cases**

The following processing constraints and guardrails apply to this release:&#x20;

* Timesheet suggestions are based on available historical reporting patterns and currently valid IFS Cloud reporting data. &#x20;
* Historical activity is used to rank and estimate entries but does not override activity or report-code validity for the target date. &#x20;
* Limited or unavailable reporting history may result in fewer suggestions or lower-confidence estimates. &#x20;
* Employee/date combinations are processed independently; a failure for one does not stop the remaining timesheets from being processed. &#x20;
* Where an employee cannot be uniquely resolved or required reporting information is unavailable, the affected timesheet is not automatically submitted.&#x20;
* Employee email information to communicate draft timesheets is retrieved from the available data in IFS Cloud. &#x20;

Submission outcomes are reported individually, including successful, partial, and failed processing, to maintain visibility across employee and team-level runs.&#x20;

### Prerequisites

This section outlines the customer-side prerequisites required to set up and use the Time Entry Manager Digital Worker.&#x20;

These prerequisites are in addition to any configuration performed within IFS Loops.&#x20;

#### Supported Versions&#x20;

**IFS Cloud Compatibility:** &#x20;

<table data-header-hidden><thead><tr><th></th><th></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td rowspan="2">Feature </td><td colspan="6">Version </td></tr><tr><td>26R2 </td><td>26R1 </td><td>25R2 </td><td>25R1 </td><td>24R2 </td><td>24R1 </td></tr><tr><td>Intelligent Timesheet Generation </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Activity &#x26; Report Code Validation </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Automated Time Submissions </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Employee &#x26; Team Processing </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Working Hours Awareness </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Submission Notifications </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr></tbody></table>

&#x20;

#### Technical Prerequisites&#x20;

To enable automated time reporting, customers must have the following technical setup in place:&#x20;

* IFS Cloud integration configured for employee, project, activity, report code, and time reporting processes &#x20;
* Email integration such as Microsoft Outlook configured for submission notifications &#x20;
* Appropriate IFS Cloud components and APIs assigned to the service user permission sets for the Digital Worker identity, including:&#x20;

#### IFS Cloud Components & Permission Sets: &#x20;

| Component | API Name                        |
| --------- | ------------------------------- |
| PERSON    | PersonnelFileHandling           |
| TIMMAN    | ReportTimeManagerHandling       |
| PROJ      | ActivityListHandling            |
| PRJREP    | ValidReportCodesHandling        |
| TIMMAN    | TimeRegistrationManagerHandling |

&#x20;

#### IFS Cloud Basic Data Prerequisites&#x20;

The following IFS Cloud configuration and data must be available to support automated time reporting:&#x20;

* Employee and organizational information &#x20;
* Employee work schedules and working hours &#x20;
* Projects, activities, and valid report codes available for time reporting &#x20;
* Historical time reporting data used to generate time estimates &#x20;
* Project and MCPR time reporting configuration, where applicable &#x20;
* Employee work email information required for submission notifications&#x20;

&#x20;
{% endupdate %}
{% endupdates %}