Incoherent date in the “Date” column when the transaction type is “Expenditure”
According to the developer, the expenditure date comes from the invoice date and always comes from it (see documentation at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/030Invoicing/020Creating_Invoices).
As you can see there, the calculation of the exchange rate is also done according to this date: "By default, Alma calculates the value of the transaction based on the exchange rate on the date specified in Invoice Date."
Now we know where the date comes from when the type of transaction is “Expenditure”. However, in other types of transactions (transfer, allocation, encumbrance, etc.) the date that appears corresponds to the moment in which the transaction occurs. For this reason, it seems impractical that in the type of transaction “Expenditure” the invoice date is used and not the date on which the transaction is triggered, that is, the “create on” date.
We request to incorporate a new column in the table of visualization of transactions that is “create on”.
We provide explanatory screenshot of how it could be implemented.
-
Sion Romaine commented
I agree that it's entirely illogical that the Expenditure date is pulled from the invoice date and not the date the invoice was a) created in Alma or b) actually expended.
By using the invoice date, rather than the invoice creation date, Analytics may report that an invoice was expended in the wrong fiscal year. E.g., if our fiscal year runs July 1-June 30, but we do not pay an invoice dated June 29 until July 2, then Alma will record the expenditure date as June 29 - the previous fiscal year - even though it was not created in Alma until July 2, the next fiscal year.
This is illogical and misleading for those trying to create expenditure reports in Analytics.