Skip to content
English
  • There are no suggestions because the search field is empty.

What's New - July 27, 2026

Validation for mandatory custom fields on import files, plus corrected Payment type default when creating supplier invoices from Purchase Orders

Compulsory custom fields are now validated during imports

What is it

Import templates now validate agency-defined custom fields that are configured as compulsory. If a required custom field is missing, the record will not be imported until a valid value is provided.

Why it matters

Previously, imported records could be created without a compulsory custom-field value even though the same record could not be saved manually without completing the field on the UI. Applying the same validation to imports helps prevent incomplete master-file data and keeps imported and manually entered records consistent.

What to expect

When an import contains a record that is missing a compulsory agency-defined custom field, the import will identify the missing requirement so it can be corrected before the record is created.

Learn more about custom fields: Manage agency-defined custom fields

 

Supplier Invoices Created from POs Now Use the Supplier’s Default Payment Type

When a Supplier Invoice is created from a Purchase Order, the Payment Type now defaults to the payment type configured for the supplier. Previously, the system selected the first payment type in the list, which could result in an incorrect default.