# Supplier Invoicing Manager

{% updates format="full" %}
{% update date="2026-05-01" %}

## Product Overview

* **Digital Worker Name:** Supplier Invoicing Manager 1.0
* **Release Version:** Q1 2026
* **Release Date:** 1 May 2026

### **What's New**

This release introduces the Supplier Invoicing Manager Digital Worker, a new autonomous worker that helps manage the supplier invoice lifecycle from intake to posting readiness with minimal manual effort and strong financial control. &#x20;

It combines agentic automation with human oversight to keep invoice processing efficient, controlled, and auditable, while giving teams full visibility into actions and decisions across the process. &#x20;

This release also supports both IFS Cloud and IFS Applications 10 (Apps10), enabling broader adoption across ERP environments.&#x20;

#### What’s new at a glance:&#x20;

* **Automated Invoice Intake & Parsing** captures incoming invoices and extracts key supplier and invoice data for downstream processing.&#x20;
* **3-Way Match Engine** validates invoice lines against purchase orders and receipts to confirm alignment.&#x20;
* **Charge & Variance Interpretation** analyzes charges and identifies variances to help distinguish acceptable differences from true exceptions.&#x20;
* **Exception Handling** routes relevant financial exceptions for human-in-the-loop review.&#x20;
* **Invoice Posting & Financial Update** prepares clean, in-tolerance invoices for posting and supports downstream financial updates.&#x20;
* **Delivers end-to-end visibility and auditability** through the ERP and IFS Loops Agentic Studio.&#x20;

### Changes in Product Offering

<details>

<summary>New or Enhanced Functionality</summary>

This release introduces the Supplier Invoicing Manager Digital Worker as a new capability in the IFS Loops ecosystem, designed to automate core supplier invoice workflows. &#x20;

The digital worker delivers intelligent invoice intake, PO‑based matching, variance interpretation, and invoice creation, establishing a scalable foundation for autonomous accounts payable processing.&#x20;

</details>

<details>

<summary>Deprecated Functions</summary>

Not applicable.

</details>

<details>

<summary>Removed Functions</summary>

Not applicable.

</details>

### Release Scope & Constraints&#x20;

This section outlines the supported formats, known limitations, and processing considerations for the Supplier Invoicing Manager Digital Worker in this release.

<details>

<summary>Supported Invoice Intake Scope</summary>

The digital worker supports automated intake and processing of supplier invoices with the following characteristics:&#x20;

**Invoice Structure:**&#x20;

* Single‑invoice documents&#x20;

**Intake Channels:**&#x20;

* Email‑based invoice intake via Microsoft Outlook or Gmail&#x20;

**Supported Attachment Formats:**&#x20;

* PDF documents (native and scanned)&#x20;
* Image files (e.g., JPG, PNG)&#x20;

</details>

<details>

<summary>Known Limitations &#x26; Edge Cases</summary>

The following scenarios are either not supported or may require human‑in‑the‑loop (HITL) intervention in this release:&#x20;

* Handwritten invoices with poor scan quality&#x20;
* Invoices missing reliable reference signals (such as supplier, PO, part, or delivery date), may result in mandatory HITL escalation&#x20;

</details>

### Prerequisites

This section outlines the customer‑side prerequisites that must already be in place to successfully set up and use the Supplier Invoicing 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 width="173.78515625"></th><th width="93.09375"></th><th width="79.37109375"></th><th width="78.859375"></th><th width="77.66796875"></th><th width="80.12109375"></th></tr></thead><tbody><tr><td></td><td><strong>Version</strong> </td><td></td><td></td><td></td><td></td></tr><tr><td><strong>Feature</strong></td><td><strong>26R1</strong></td><td><strong>25R2</strong></td><td><strong>25R1</strong></td><td><strong>24R2</strong> </td><td><strong>24R1</strong></td></tr><tr><td>Automated Invoice Intake &#x26; Parsing </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>3-Way Match Engine </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>Charge &#x26; Variance Interpretation </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 Handling </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 Posting &#x26; Financial Update </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>

**Apps10 Compatibility:**&#x20;

<table data-header-hidden><thead><tr><th></th><th width="119.28515625"></th></tr></thead><tbody><tr><td><strong>Feature</strong> </td><td><strong>Apps10</strong> </td></tr><tr><td>Automated Invoice Intake &#x26; Parsing </td><td><ul><li> </li></ul></td></tr><tr><td>3-Way Match Engine </td><td><ul><li> </li></ul></td></tr><tr><td>Charge &#x26; Variance Interpretation </td><td><ul><li> </li></ul></td></tr><tr><td>Exception Handling </td><td><ul><li> </li></ul></td></tr><tr><td>Invoice Posting &#x26; Financial Update </td><td><ul><li> </li></ul></td></tr></tbody></table>

#### **Technical prerequisites:**&#x20;

To enable automated invoice processing and human-in-the-loop workflows, customers must have the following technical setup in place:&#x20;

* Invoice mailbox configured for receiving supplier invoices&#x20;
* Collaboration channel such as Microsoft Teams or equivalent for human-in-the-loop exception escalation and decision handling &#x20;
* Appropriate IFS Cloud components and APIs assigned to the service user permission sets for that digital worker identity, including:&#x20;

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

<table data-header-hidden><thead><tr><th width="123.03125"></th><th width="369.2421875"></th></tr></thead><tbody><tr><td><strong>Component</strong> </td><td><strong>API Name</strong> </td></tr><tr><td>ENTERP </td><td>SupplierHandling </td></tr><tr><td>PURCH </td><td>SupplierForPurchasePartHandling </td></tr><tr><td>PURCH </td><td>PurchaseOrdersHandling </td></tr><tr><td>PURCH </td><td>PurchaseOrderLinesHandling </td></tr><tr><td>INVOIC </td><td>ManualSupplierInvoiceAssistantHandling </td></tr><tr><td>DOCMAN </td><td>DocReferenceObjectAttachmentHandling </td></tr></tbody></table>

**Apps10 Components & Permission Sets:**&#x20;

<table data-header-hidden><thead><tr><th width="120.6328125"></th><th></th></tr></thead><tbody><tr><td><strong>Component</strong> </td><td><strong>API Name</strong> </td></tr><tr><td>ENTERP </td><td>SupplierHandling </td></tr><tr><td>PURCH </td><td>SupplierForPurchasePartHandling </td></tr><tr><td>PURCH </td><td>PurchaseOrdersHandling </td></tr><tr><td>PURCH </td><td>PurchaseOrderLinesHandling </td></tr><tr><td>INVOIC </td><td>ManualSupplierInvoiceAssistantHandling </td></tr><tr><td>DOCMAN </td><td>DocumentHome </td></tr></tbody></table>

#### &#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;

* Supplier master data&#x20;
* Master Part data&#x20;
* Purchase Part data&#x20;
* Supplier for Purchase Part relationships&#x20;
* Purchase Orders&#x20;
* Good Receipts/Register Arrivals \[Must be completed and available to enable 3‑way matching scenarios]&#x20;
* Voucher configuration, where application for downstream financial processing&#x20;
  {% endupdate %}
  {% endupdates %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.theloops.io/releasenotes/release-notes/digital-workers-release-notes/supplier-invoicing-manager.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
