IRIS Financials Purchasing release 6.0.423 — October 2026

IRIS Financials Purchasing works with V600 and V700 IRIS Financials accounting systems.

This page covers the changes in release 6.0.423 only. For earlier changes, refer to the release notes for those releases and to the online help.

What's new in this release

This release includes these new features and changes.

New home page

A new home page opens after you sign in. It has the same tiles as before, with new icons.

New sign-in screen

The sign-in screen has a new design. It works in the same way as before.

User access to the Order and E-Procurement tiles

Administrators can now hide the Order tile, the E-Procurement tile, or both, for individual users. Both tiles show by default.

Use this setting when:

  • A requisition user can raise E-Procurement baskets but must not create purchase orders.

  • A user has the E-Procurement tile but does not need it.

Only administrators can change these settings. To hide a tile for a user:

  1. Select the E-Procurement tile on the home page.

  2. Select Settings.

  3. Find the user on the E-Procurement Tile Settings page.

  4. Select Hide Order Tile, Hide E-Procurement Tile, or both for that user.

  5. Select Save.

Use the search box to narrow the list of users. To show a hidden tile again, clear the selection and select Save.

To hide the E-Procurement tile for all users, go to Hiding the E-Procurement tile for all users.

E-Procurement order status page

When an E-Procurement order completes your approval process, IRIS Financials Purchasing sends it to the E-Procurement supplier. The new E-procurement Orders Status page shows the status of each order, including whether the order reached the supplier.

To open the page:

  1. Select the E-Procurement tile on the home page.

  2. Select Order Tracking.

Filter the list by supplier, date, status, or user ID. For each order, the page shows the supplier, date, user ID, purchase order number, order value, recipient name, and status. The status is TRANSMITTED when the order reached the supplier and FAILED when it did not.

Removal of Gainsight functionality

This release removes all Gainsight functionality from IRIS Financials Purchasing and from IRIS Financials Reports (MyReports). It follows IRIS Financials Gainsight suppression release — October 2026.

Fixes and improvements

This release includes these fixes and improvements:

  • We improved how search boxes handle the text you enter, to reduce slow searches.

  • We fixed security issues that our code analysis tools found.

  • We fixed reliability issues that our code analysis tools found.

Known issues

This release has these known issues.

Missing icons on the new home page

When you first sign in, the settings, licence, and sessions icons do not appear on the new home page.

To show the icons, select any tile and then return to the home page. Alternatively, use F5 to refresh the page.

The next release fixes this issue.

Purchase order status on the E-procurement Orders Status page

The E-procurement Orders Status page does not show the purchase order status (POPSTATUS). The next release adds it.

Installation and database changes

The installation process differs for PS Cloud customers and on-premises customers. IRIS provides 3 AutoUpdater packages to install the E-Procurement and Purchasing functionality.

Apply the 6.0.423 Purchasing package first. It includes database settings that the Punchout functionality needs.

Apply the packages in this order:

  1. ALL_PS Purchasing_Build 600.0.423_Patch General Release.abp

  2. IRIS Financials Purchasing Punchout V1.0.530.abp

  3. ALL_Iris MyReports_Build 1.0.37_Patch General Release.abp

Requirements

You need:

  • IRIS AutoUpdater utility build 0.11.1 or later, which needs Microsoft .NET 8.0 to run.

  • Microsoft .NET 10 installed in your server environment.

What the packages do

The packages:

  • Back up the existing application databases.

  • Apply the framework build (6.0.423), the Purchasing module (1.0.209), and the Punchout module (1.0.530).

  • Apply standard database changes that are not already present, such as stored procedures.

  • Create the PUNCHOUT database, if it is not already present.

  • Create a new Microsoft SQL Server user and apply the user configurations.

The 6.0.423 packages install Punchout for Amazon, KCS, ESPO, Findel, YPO, HBS, and HFS.

PS Cloud

IRIS installs this release automatically for PS Cloud customers.

To install on an individual PS Cloud machine, use the 3 AutoUpdater packages and select the PS Cloud option during installation. IRIS then sets the certificates and permissions for you.

  • For the PS Purchasing package, enter your PS Cloud server name. Ignore the On Premise Only options.

  • For the Punchout package, complete only the first 4 parameters. Ignore the On Prem Only options. The SQL Server name is likely to be the only value you need to enter. The package sets the SQL Server user name and certificates for you.

On-premises

On-premises customers must use the AutoUpdater packages. Involve your IT support team before you start.

SQL Server permissions

The Punchout package creates a new database, so it needs a SQL Server login with system administrator permissions. Give the PSFDBA login the sysadmin server role for the duration of the installation. If PSFDBA does not have this role, the package stops and shows a PSFDBA warning message.

Certificate requirements

IRIS Financials Purchasing now uses an https address, so it needs a valid Secure Sockets Layer (SSL) certificate. The certificate must be a Server or Server/Client type.

If you already make IRIS Financials Purchasing available outside your network, you already use SSL certificates. If you do not, ask your IT support team to get and install a certificate for your site. Certificates are a local network and infrastructure matter, so your IT support team provides them, not IRIS.

Parameters

For an on-premises installation, set the install type to On Premise in each package. In the Punchout package, also complete the 2 On Prem Only parameters.

  • Enter the SQL Server name. For a SQL Server instance, enter <servername>\<instance name>.

  • Enter a password for the new PODBA SQL Server login that the package creates. The password must meet your local password policy.

  • Enter the Internet Information Services (IIS) Punchout URL. This URL is likely to use the format https://<servername>.<CertificateName>/Purchasing. The host name format may differ if you use redirection or if the certificate name matches the server name.

  • In the PS Purchasing package, also enter the service account user name and password, and the PS Purchasing URL, for example https://<servername>.<CertificateName>/PSOnline.

Use a capital P in Purchasing. The capital letter is significant.

New PUNCHOUT database

This release adds a SQL Server database called PUNCHOUT. It holds the E-Procurement settings and basket data.

The release also adds a SQL Server login called PODBA, which controls access to this database.

This release also adds new settings to the PSF_SETTINGS table in the PSFSYSTEM database, under the setting class PURCHASING_V2_APP_URL.

Communication protocol

Amazon uses cXML (commerce XML) to communicate with the purchasing system. Businesses use this protocol to exchange business documents consistently between procurement applications, e-commerce hubs, and suppliers. You can find the data sent for each basket transaction in one of the Purchasing database tables.

Purchase order rule for E-Procurement order requests

IRIS Financials includes a rule called EProcurement Order Requests. The rule sends the purchase order back to the E-Procurement supplier only after every level of approval is complete.

Open the rule in the Rule Maintenance application to review its details. The rule reports success and failure messages on the Results page in Rule Maintenance.

Hiding the E-Procurement tile for all users

The E-Procurement tile shows on the home page for all users by default. To hide it for individual users, use the E-Procurement Tile Settings page.

To hide the tile for all users, contact IRIS Support.

The next deployment resets this setting to its default. Contact IRIS Support again to reapply it after each deployment.