> 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/service-closure-manager.md).

# Service Closure Manager

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

## Product Overview

* **Digital Worker Name:** Service Closure Manager 
* **Release Version:** Q3 2026
* **Release Date:** Sep 15th, 2026

### **What's New**

This release introduces the Service Closure Manager Digital Worker, which validates completed service work, supports scope-level invoice preview creation and approval, and closes service requests following successful invoicing in IFS Cloud. 

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

* **Service Task Validation** reviews completed request tasks and coordinates the required validation checks before the work can progress to invoicing.  
* **Material & Return Validation** validates planned and reported material usage, return records, quantities, and related cost information against the completed service work.  
* **Time Reporting Validation** compares planned and reported personnel time and validates corresponding cost lines to identify missing or inconsistent time reporting.  
* **Invoice Readiness Validation** consolidates material, return, material usage, and time reporting results to determine whether a request task is ready for invoicing.  
* **Scope-Level Invoice Validation** validates all request tasks within a service request scope and prevents invoice creation when one or more tasks do not meet the required validation criteria.  
* **Invoice Preview & Approval** creates an invoice preview for successfully validated request scopes and supports explicit user approval before the service invoice progresses.  
* **Automated Request Closure** closes service requests once the required validations have passed and invoicing has been successfully completed. 
* **Exception & Human-in-the-Loop Review** provides detailed validation outcomes and routes failed checks or invoice approval decisions for user review and action. 

### Changes in Product Offering

<details>

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

This release introduces the Service Closure Manager Digital Worker as a new capability in the IFS Loops ecosystem, automating service validation, scope-level invoicing, and request closure following successful invoicing.

</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 service task validation, invoice readiness, and invoice processing scenarios for the Service Closure Manager Digital Worker in this release.

**Supported Service Closure Management Scope**

The digital worker supports warranty claim processing with the following characteristics:&#x20;

<details>

<summary><strong>Trigger Scope:</strong></summary>

* Webhook-based invocation when a service request scope transitions to Completed
* Automatic handoff of the affected request scope for validation and closure processing

</details>

<details>

<summary><strong>Service Request Task Scope:</strong></summary>

* Processing of individual service request tasks
* Retrieval of request task details, including descriptions, performed work, actions, remarks, and service notes
* Assessment of task context to determine whether materials and returns are expected
* Execution of all applicable validation checks, with detailed results for each task

</details>

<details>

<summary><strong>Material &#x26; Return Validation Scope:</strong></summary>

* Validation of planned and reported materials, quantities, and related cost lines
* Comparison of material usage against the completed service work
* Validation of return records where returned materials are expected
* Identification of missing or inconsistent material and return information

</details>

<details>

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

* Validation of planned and reported personnel hours against associated cost lines
* Identification of time variances and mismatches

</details>

<details>

<summary><strong>Invoice Readiness Scope:</strong></summary>

* Consolidated assessment of material, return, and time reporting results
* Completion of all applicable validation checks, even where an earlier check has failed
* Prevention of invoice progression when a request task does not pass the required validations

</details>

<details>

<summary><strong>Request Scope &#x26; Invoice Scope:</strong></summary>

* Retrieval of all request tasks associated with a service request scope
* Invoice preview creation only when all request tasks within the scope have passed the required validations
* Explicit approval of the service scope invoice following user review

</details>

<details>

<summary><strong>Request Closure Scope:</strong></summary>

* Closure of service requests following successful invoicing
* Verification of the request states before and after closure
* Reporting of the closure outcome through the configured communication channel

</details>

<details>

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

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

</details>

**Known Limitations & Edge Cases**

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

* A successful validation result does not override a failure from another required check.&#x20;
* Missing or inconsistent material, return, or time reporting information prevents the affected task from being considered ready for invoicing.&#x20;
* Validation failures do not automatically modify or override the underlying reported service information.&#x20;
* Request closure is performed only after the required validation, and invoicing steps have been successfully completed. A failed or incomplete process does not proceed to closure.&#x20;

In addition, Human-in-the-Loop (HITL) interactions provide visibility into validation results and control over invoice approval. Validation failures are presented with the underlying reason for review, while invoice approval requires explicit user confirmation before the invoice progresses.

### Prerequisites&#x20;

This section outlines the customer-side prerequisites that must already be in place to successfully set up and use the Service Closure 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>Service Task 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>Material &#x26; Return 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>Time Reporting 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>Invoice Readiness 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>Scope-Level Invoice 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>Invoice Preview &#x26; Approval </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 Request Closure </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>Exception &#x26; HITL Review </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 service closure validation, invoice processing, and request closure, customers must have the following technical setup in place:&#x20;

* IFS Cloud configured for service request, request task, cost and sales, and service invoicing processes &#x20;
* Webhook Event Trigger configured in IFS Cloud to invoke the Digital Worker when a service request scope transitions to Completed&#x20;
* Collaboration or communication channel configured for validation outcomes, exceptions, invoice review, and human-in-the-loop interactions &#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                                                               |
| --------- | ---------------------------------------------------------------------- |
| REQMGT    | RequestTaskHandling.svc (26R2 – 25R2) & JtTaskHandling.svc (25R1-24R1) |
| REQMGT    | RequestHandling.svc                                                    |
| REQMGT    | RequestCostAndSalesHandling.svc                                        |
| WO        | InvoicePreviewHandling.svc                                             |
| SRVOBJ    | ServiceObjectHandling.svc                                              |

&#x20;

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

The following IFS Cloud master and transactional data must already be configured and maintained by the customer to support automated processing:&#x20;

* Service requests, associated scopes, and request tasks with completed service reporting&#x20;
* Work performed information, actions, remarks, and service notes required for validation&#x20;
* Planned and reported materials, usage, and return records where applicable&#x20;
* Planned and reported personnel time&#x20;
* Request task cost and sales lines required for validation&#x20;
* Service invoicing and request closure configuration required to complete the invoicing and closure process&#x20;
  {% endupdate %}
  {% endupdates %}