Release 3.23 will be available in the Demo environment on Monday 21 January, then in Production on Monday 28th (US) and Tuesday 29th (Australasia)
Expenses Module 2.0
An increasing number of customers have requested the ability to manage expenses through Unimarket so that all spend can be managed through the same business and approvals process. To support the increasing demand we have upgraded the Expenses module with an improved user interface to make it easier to use and added the following new features:
Configurable Expense Types
The Community can configure specific Expense Types and determine custom fields and requirements for each. This supports specific customer expense policies by allowing customers to capture of specific data and make certain information mandatory. For example, a Mileage expense type may have different fields and requirements than an Accommodation expense.
Pre-defined Rates and Values
Communities can create pre-defined rates and values which can be used to calculate milage rates or present the user with a pre-defined list of values.
The Unimarket Expense module has the ability to minimise fraudulent claims by detecting if the same/similar expense line have been submitted as part of another claim. This information is alerted to approvers.
Account Code Validation
We have added support for Account Code Validation integration to the Expense module. This validates the GL account code used by the submitter.
Default GL Account Code (FOPAL)
Communities can configure a default GL Account Code (FOPAL) for each expense type that pre-populates when the expense type is selected.
Better Claim Visibility
Approvers now have greater visibility of the entire Claim even if they are not approving all the lines on the Claim.
Sourcing (RFx) Supplier Evaluation Criteria Upload
We have added the ability for suppliers to upload their Bid criteria responses to the Bid Request using a CSV format to save time. Suppliers download the criteria questions, complete their answers then upload the answers to the Bid Request.
Sourcing XML Interface
We have completed the Sourcing XML interface which can be used by Communities to receive all Bid related data into their finance system.
Small Changes and Bug Fixes
- Searching for RFQs / Bid Requests by ID should ignore the other filters.
- Make validate account codes integration point usage configurable (checkout, blanket orders, expenses).
- Display Purchase Requests in date order.
- Only send the Supplier Request Approval email once the supplier is connected to the community.