Account Transaction Audit information; if used for other than system generated Interest transactions can cause warning traces to be generated

If the Account Transaction Audit information is used for other than system generated Interest transactions it can cause warning traces to be generated when displaying the summary page in the Account form, Transaction page.

This is caused by the AccountTransaction.GetAuditDays function attempting to convert audit information into a finAccountCalcDays object - but the data is not valid for this.

finPOWER Connect now only attempts to convert to finAccountCalcDays if the Transaction is an Interest transaction that is System allocated.