> 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/supplier-invoicing-manager.md).

# Supplier Invoicing Manager

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

## Product Overview

* **Digital Worker Name:** Supplier Invoicing Manager 2.0&#x20;
* **Release Version:** Q3 2026&#x20;
* **Release Date:** Sep 15th, 2026

### What's New

This release enhances the Supplier Invoicing Manager Digital Worker with invoice posting and supplier payment capabilities, extending the automated supplier invoice lifecycle beyond invoice creation.&#x20;

Building on the invoice intake, validation, 3-way matching, and invoice creation capabilities introduced in version 1.0, the Digital Worker can now post successfully created invoices, support supplier payment processing, and complete final posting after payment.&#x20;

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

* **Charge Line Discrepancy Handling** identifies differences in charge lines between supplier invoices and corresponding purchase orders.&#x20;
* **Supplier Invoice Posting** posts successfully created supplier invoices in IFS Cloud and prepares them for payment processing. &#x20;
* **Supplier Payment Processing** creates mixed payments using the selected cash account and payment amount. &#x20;
* **Final Invoice Posting** completes final posting once the invoice has been fully paid. &#x20;
* **Enhanced Processing Controls** ensures invoices progress only when the required preceding financial steps are completed. &#x20;
* **Human-in-the-Loop Payment Contro**l maintains user control over posting, payment, and approval activities.&#x20;

### Changes in Product Offering&#x20;

#### New or Enhanced Functionality&#x20;

This release extends the Supplier Invoicing Manager Digital Worker with additional downstream financial processing capabilities.&#x20;

Supplier invoices that have been successfully created can now progress through invoice posting, mixed payment creation, and final posting in IFS Cloud. These capabilities extend the existing invoice processing workflow while maintaining user control over posting and payment activities.&#x20;

#### Deprecated Functions&#x20;

Not Applicable.&#x20;

#### Removed Functions&#x20;

Not Applicable.&#x20;

### Release Scope & Constraints&#x20;

This section outlines the new invoice posting and payment capabilities introduced with Supplier Invoicing Manager 2.0.&#x20;

The invoice intake, parsing, 3-way matching, variance handling, exception management, and invoice creation capabilities introduced in version 1.0 continue to be supported.&#x20;

#### Supported Supplier Invoicing Scope&#x20;

The following capabilities are introduced in this release:&#x20;

#### Charge Line Discrepancy Scope:&#x20;

* Identification of charge lines present on the supplier invoice but missing from the purchase order, and vice versa &#x20;
* Presentation of identified charge discrepancies for review&#x20;

#### Invoice Posting Scope:&#x20;

* Posting of successfully created supplier invoices in IFS Cloud&#x20;
* Progression of the invoice through the applicable posting state&#x20;
* Confirmation of the posting outcome before payment processing&#x20;

#### Supplier Payment Scope:&#x20;

* Creation of mixed payments for successfully posted supplier invoices&#x20;
* Selection of the applicable cash account and payment amount&#x20;
* Support for partial or full invoice payments&#x20;
* Approval of the created mixed payment before further processing&#x20;

#### Final Posting Scope:&#x20;

* Final posting once the supplier invoice has been fully paid&#x20;
* Progression of the invoice to its final paid and posted state&#x20;
* Confirmation of the final posting outcome in IFS Cloud&#x20;

#### Human-in-the-Loop Scope:&#x20;

* User-controlled initiation of posting and payment activities&#x20;
* User approval of mixed payments before processing continues&#x20;
* Processing errors or missing information returned for review&#x20;

### Known Limitations & Edge Cases&#x20;

The following processing constraints and guardrails apply to the new capabilities in this release:&#x20;

* Invoice posting is supported only for successfully created supplier invoices.&#x20;
* Payment processing uses the supported mixed payment flow and requires a valid cash account and payment amount.&#x20;
* Mixed payments require user approval before processing continues.&#x20;
* Partial payments are supported; however, the invoice must be fully paid before final posting.&#x20;
* Where a required step cannot be completed, the invoice does not automatically progress to the next financial stage.&#x20;

In addition, Human-in-the-Loop (HITL) interactions are used where user input, approval, or corrective action is required.&#x20;

#### Prerequisites&#x20;

This section outlines the additional customer-side prerequisites required to use the capabilities introduced with Supplier Invoicing Manager 2.0.&#x20;

All prerequisites established for Supplier Invoicing Manager 1.0 continue to apply, including the invoice mailbox, collaboration channel, required IFS Cloud permissions, and supplier and purchasing basic data.&#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"><strong>Feature</strong> </td><td colspan="6"><strong>Version</strong> </td></tr><tr><td>26R2 </td><td>26R1 </td><td>25R2 </td><td>25R1 </td><td>24R2 </td><td>24R1 </td></tr><tr><td>Charge Line Discrepancy 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><td><ul><li> </li></ul></td></tr><tr><td>Supplier Invoice Posting </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>Supplier Payment 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>Final Invoice Posting </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>Enhanced Processing Controls </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>Human-in-the-Loop Payment Control </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;

The technical prerequisites established for Supplier Invoicing Manager 1.0 continue to apply.&#x20;

For the capabilities introduced in this release, the Digital Worker service user must also have the required IFS Cloud permissions for invoice posting and mixed payment processing.&#x20;

IFS Cloud Components & Permission Sets: &#x20;

| **Component** | **API Name**                  |
| ------------- | ----------------------------- |
| INVOIC        | ManualSupplierInvoiceHandling |
| SINWOF        | PostingProposalHandling       |
| PAYLED        | CashAccountsHandling          |
| PAYLED        | PaymentHandling               |

&#x20;

The existing APIs required for supplier validation, purchase order processing, invoice creation, and document management continue to apply.&#x20;

&#x20;

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

The basic data prerequisites established for Supplier Invoicing Manager 1.0 continue to apply.&#x20;

For the capabilities introduced in this release, the following must also be configured where applicable:&#x20;

* Purchase charge types required for charge line validation &#x20;
* Cash accounts available for supplier payment processing &#x20;
* Payment configuration required for mixed payment processing&#x20;

{% endupdate %}

{% 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 %}
