New Features and Enhancements in Foundations Winter 2025

The following new features have been introduced in the Winter 2025 release of Foundations.

If you are upgrading from a previous version, see Upgrading to Foundations Winter 2025. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.

Enhancements to Accounts Payable Automation

Using this feature, payable invoices can be automatically created when vendor invoice attachments are scanned. When an email containing an invoice attachment is received, the invoice is automatically scanned, and a scanned payable document is created. If all the required information is correct then a payable invoice is automatically created in Accounting. This process streamlines your invoicing process, saving you time and costs. It eliminates data entry and provides accuracy.

However, if it fails to create a payable invoice, then you can use the manual process.

To start using Accounts Payable Automation, you must complete the setups explained in Setting up Accounts Payable Automation.

To enhance this feature, we have included support:

  • Included support for the automatic population of the Company field in scanned payable documents.
  • Scan multiple invoice attachments' from a single vendor email.
  • Configure a shared generic email address for all companies, or an email per company.
  • Included support for recognizing vendor accounts and populating the Account field in scanned payable documents by using the vendor account information in fields such as Account Name, Phone, and Email.
  • Included support for automatically populating the PSA Project and Dimension 1-4 fields on the scanned payable document.

Forcing Matching Fields Types for Custom Mappings

When using the MappingDescriber Apex API to create custom mappings, you can now force matching field types. This means that fields can only be mapped to fields of the same type. For example, a Date field can only be mapped to a Date field, and not to any other field type such as a Text. Additionally, the mapped fields must have the same maximum length, and number fields must have matching maximum decimal places. For more information, see Permission Sets and Other Technical Documentation.

Fixes

Fixes are listed on the Known Issues page of the Certinia Community. You can access this page from the Community Support Hub. For a brief description of the issues that have been fixed in this version of Foundations, see the relevant section of the Known Issues page.