FAQ

Capabilities & functionality

Q: What does the Service Closure Manager do?

A: The Service Closure Manager is a Digital Worker that validates completed service work before it progresses to invoicing in IFS Cloud. It reviews reported materials, returns, and time against a service request task, determines whether the work is ready for invoicing, and supports scope-level invoice preview creation and approval.

Q: What does the Service Closure Manager check on a completed task?

A: It checks planned and reported materials and returns, quantities and related cost lines, and planned and reported personnel time against the cost lines it generated. These results are consolidated into a single invoice readiness assessment for the task.

Q: What happens if one check fails but the others pass?

A: A successful result from one validation never overrides a failure from another. All required checks are processed even after an earlier one has failed, and the task is only considered ready for invoicing once every required validation has passed.

Q: Does the Service Closure Manager create invoices itself?

A: It creates an invoice preview once every task in a request scope has passed the required validations. The service invoice does not progress until a person explicitly approves that preview.

Q: What happens to a request task that fails validation?

A: The underlying reason for the failure is presented for review. The Service Closure Manager does not modify or override the reported service information; the person responsible corrects the record in IFS, in the normal place, and the task is validated again.

Control & Collaboration

Q: Can an invoice preview be approved automatically?

A: No. Invoice approval always requires explicit user confirmation before the service invoice progresses, regardless of how cleanly the underlying scope validated.

Q: What does a reviewer see when a task fails validation?

A: The validation outcome and the underlying reason for the failure, routed through the configured communication channel, so the person responsible can see exactly what needs correcting and why.

Q: How is an invoice preview reviewed?

A: It is presented through the configured communication channel along with the validation results behind it. A person reviews it and gives explicit approval before the invoice progresses.

Q: Can the Service Closure Manager correct a failed record on its own?

A: No. Validation failures do not automatically modify or override the underlying reported service information. Correcting the record is a human action, taken in IFS where it would normally happen.

Integration & Technology

Q: What does the Service Closure Manager integrate with?

A: It integrates with IFS Cloud, where service requests, request tasks, cost and sales lines, and service invoicing are configured. Human-in-the-loop interactions, validation outcomes, exceptions, invoice previews, and approvals are routed through a configured communication channel.

Q: What IFS Cloud data does the Service Closure Manager use?

A: Service requests and their associated scopes, completed request tasks with their descriptions, performed work, actions, remarks and service notes, planned and reported material information, material usage and return records, planned and reported personnel time, and the request task’s cost and sales lines.

Q: Is invoice preview creation supported at the individual task level?

A: No. Invoice preview creation and approval are performed at the service request scope level, not for individual request tasks.

Q: What has to be in place in IFS Cloud before the Service Closure Manager can be used?

A: IFS Cloud needs to be configured for service request, request task, cost and sales, and service invoicing processes, and a collaboration or communication channel needs to be set up for validation outcomes, exceptions, invoice review, and human-in-the-loop interactions.

Security & Reliability

Q: Can the Service Closure Manager change the underlying service record?

A: No. Validation failures never automatically modify or override the underlying reported service information. Every correction is a human action taken directly in IFS.

Q: How consistent is validation across tasks?

A: All applicable validation checks are executed for every task, and a task’s readiness is only determined once every required check has run, even where an earlier one has already failed. The same checks apply to every task processed.

Q: What happens if material or time reporting information is missing?

A: Missing or inconsistent material, return, or time reporting information prevents the affected task from being considered ready for invoicing, and is surfaced for review rather than silently passed.

Q: How is visibility maintained into what was checked and why?

A: Human-in-the-loop interactions provide visibility into validation results and control over invoice approval. Validation failures are presented with the underlying reason for review, and invoice approval requires explicit user confirmation.

Customization & Performance

Q: What triggers validation on a task?

A: A completed service request task triggers the Service Closure Manager’s review, retrieving the task’s details and running the applicable material, return, and time reporting checks.

Q: How does invoice readiness scale from task to scope?

A: Each task is individually validated and assessed for readiness. At the request scope level, every associated task is retrieved and validated, and a scope-level invoice preview is only created once every task in that scope has passed its required validations.

Q: What are the core capabilities that make up the Service Closure Manager?

A: Service Task Validation, Material & Return Validation, Time Reporting Validation, Invoice Readiness & Scope-Level Validation, and Invoice Preview & Approval. Together, they take a completed task from initial review through to an invoice a person has explicitly approved.