Our Finance Executive with invoice generation role does not need to access the configuration screen. The configuration usually will be done by IT so it will be beneficial for access control purpose to segregate these functions and can be assigned ...

It would be really useful if you could delete recurring charges/fees in bulk for just one cycle. We currently have different cycles for fees and disbursements. When a new cycle is generated the fees are automatically posted because we have set the...

This would make the system consistent with the other access options in the account details tab. It's going to be very helpful when we move over to the new cloud portal and need to give more staff access to the Cloud portal module.

Please may we suggest that the Bulk Payment Batch Number be increased from 6 Alpha Numeric digits to at least 10? We use the date of the Bulk Payment run to identify the Bulk Payment, however, sometimes we do 2 or 3 different runs on any one day &...

On generating a BACS18 file, if the process fails, there is no meaningful error message to investigate from. Instead, a support call has to be raised which takes time to resolve and sending a BACS file is time critical. It would be helpful if a me...

Please can we have the ability to - change the column width - export to Excelwithin Business Intelligence Setup page just as you can other iFinance pages?

Please could new Parent Portal accounts default to iSAMS 2FA enabled, not iSAMS 2FA disabled. At the moment we need to manually enabling it each time a new Parent Portal account is created. The ideal solution would be to allow schools to select wh...

Currently when the school receives a large volume of receipts over the period of a few days, we would much rather upload a bulk excel file using the transactions importer rather than inputting it one by one. However, the drawback to this is that t...

At the moment the tax code for AP inbox invoices defaults to the first code in an alphabetical list! So every invoice needs manually updating, which causes massive human error and is time consuming to correct. It makes the AP inbox unusable.

iFinance flags manual invoices where transaction date is for period that has already been closed so it makes sense if the system does the same for API invoices