Robert Rudd Delivery Architect

At present there is a one to one relationship between Expense reports and Travel Requisition however, this limits an Expense report to "one trip". The reality is for a lot of employees are travelling multiple trips in a month and will be submitting expenses relating to one or more trips at the same time. Furthermore, for expenses incurred on credit cards where there can be a delays in receiving the credit cards line, the timing on when expenses can be claimed varies considerably . Ultimately the travel requisition is matched at the line level, not the header level thus limiting an Expense report to one travel requisition does not make any sense either from a technical point of view or the user experience.

At present Expense Management allows the entry of guests in entertainment and other related expense types. In Australia, for tax purposes, the actual information required is the number of Guests, internal versus external only thus the requirement to enter the names of Guests means this feature does not get used often. This idea is to have an option to enter the number Guests rather than names. This would be helpful from an analysis point of view too as you could calculate the costs per head without imposing the requirement to enter the names.

There is no ability to make a sales tax group or item group inactive. When trying to optimize the sales tax setup over time particularly in the US or in a customer with operations in multiple countries within a single legal entity, it would be beneficial to be able to make a GST group or item group inactive as part of optimizing sales tax reporting. Currently once a GST group or item group are setup, they can only be deleted if not used.

At present, all expense categories are available with the travel requisition form to requisition travel. The reality of expense categories are they are typically a mixture of both indirect procurement i.e. stationary and pure travel categories i.e. flights, taxis, accommodation etc. This idea is to restrict certain expense categories to travel requisition form which relate to travel only.

Email notifications for things like approvals are sent for every workflow item even if the "grouped" user option is checked. The impact of this is if workflow approvals are completed at the line level for Expenses for example, a notification is sent for every line of the Expense Report.

Expense management workflows do not have request change option. This is a major drawback particularly for credit card transaction but overall it is a major issue. For credit card transactions this means if the person responsible for approval does not believe the workflow originator has assigned the correct expense category, description of the expense, right receipt attached etc., there is no option but to approve the transaction as rejecting the transaction is final state i.e. credit line will remain not processed. For out of pocket transaction at least the workflow originator can re-enter the transaction however, again this is a bad user experience due to the additional data entry

As part of importing credit card transactions, the system defaults a category into the credit card transaction when its imported into an expense report if there is no category mapped to the merchant code of the transaction. There are a couple of challenges with this approach: - There is no way of setting which category is the default - As users are often in a hurry, they can assume the default category has actually been mapped by the system and accepted this default. Ideally, it would be great if a default category was not required however, if this required due to a technical limitation, it would be better if a default could be selected.

At present, when the General Ledger period is closed, there could be transactions (General Ledger journals as example) which are not posted in the system with an accounting or transaction date which applied to the period to be closed. When the period is being closed, there is no warning these transactions are there. This idea is to have a warning when the period is attempted to close along the lines of" There are transactions in the General Ledger which are not posted, would you like to proceed?"

Disposal of a Fixed Asset either by scrap or sale is a big decision and can have a material impact on business if the asset is not disposed at the correct value or ensuring it cannot be put to productive use. The proposed new feature is to have a workflow approval associated with the disposal of the fixed asset.

For a number of transactions there is an ability to override the calculated sales tax amount to account for rounding differences. A new feature would be a tolerance for such overrides i.e. amount or percentage, preferably both, which would stipulate that any override could only be within tolerance.