19
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.
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.


Thanks,
Surya Vaidyanathan,
PM, Expense

Comments

R

Hi all,


Anyone know if this is resolved? I'm on 10.0.30 (10.0.1362.77) and it's still the same issue.

Category: Expense Management

R

I can only support the previous comments. Having code that defaults a data element to some random value (and indeed one that may very well be actively selected by users) seems to be a poor design pattern.
Please don't default a random value.
There are plenty of better options:
* Fail the import if the category code cannot be found
* Offer some sort of parameter or configuration to let the admin select a default
* Import with a flag that forces the user to select a proper value later
* ...
Thanks

Category: Expense Management

R

This is a badly needed fix. I am unsure why this was changed to a default to a category (which seems to be meals type) with no way of changing what the default will be. When we were testing in an earlier version of D365, it was left blank, which is how it should behave. I also don't understand why merchant category codes would be mapped to expense categories when the two are not directly related. The merchant category code is based on the store and not the item that was sold and the category codes are sometimes assigned incorrectly. If it is a large department store where you can buy a number of different types of products which could be posted to different categories, you end up with some kind of general merchant code which you have to map to something specific and hope the employee fixes (they don't) or map it to a generic code that you have to create a policy for to make it be rejected. I have heard of a few companies creating this category and policy and mapping ALL 9000+ merchant codes there. If it were my choice mapping would be blank and categories would have to be selected by the employee, instead of trying to figure out a workaround.

Category: Expense Management