@edoardomoreni could you clarify what happens when users take the following actions from the transaction page:
Rename a transaction (rename button - top right of page)
Submit a Twitter handle (Something wrong button - bottom of page)
Both of these actions produce immediate changes within the app suggesting they are user/installation specific. Are these changes also reviewed by the Emma team for wider deployment?
Is auto application to future transactions dependent on Emma team reviewing and approving the changes?
Like @sean.read I have issues with my rename and logo changes not auto-applying to some future transactions. I did send several messages to support last year about this (highlighting specific transactions) but the situation never improved so I gave up.
The feedback is sometimes applied and other times is dismissed for everyone, but it will still work on your account.
All our detection is string based, so suggesting something like “FEE” as a StarlingBank transaction can not be applied to the whole user base, but you can still do it on your account for extra customisation.
Is the rename function supposed to auto-apply to future transactions as well?
If Emma team adopts the logo submission for whole user base, will it then apply to future transactions?
How specific is the matching (for both rename and logo submission)?
One of the problem merchants I have is Now TV. For whatever reason, every month they seem to slightly change one aspect of the transaction name that appears on my card statement (and also passed to Emma via open banking). For example one month it will be “NOW X7234 SPORTS, LONDON” and then the next month the second word will change to something else, e.g. “NOW 34EG1 SPORTS, LONDON”. I try to rename this “Now Sports” within Emma, but it never sems to stick for future transactions. Is this because Emma is trying to map the rename to an exact transaction name string (which would explain why it is not sticking) or is Emma rename function supposed to be a bit flexible and match similar strings?
NOW is something we can/need to sort internally cause the string changes every month, that’s why it won’t work on your side. It requires a specific rule that says “NOW + space + 5digits” assign it to NOW the merchant.
Ok thanks. So if Emma is repeatedly getting that merchant name wrong and that merchant doesn’t have a Twitter account, I suppose the only option is to alert customer support?
It might be helpful to put some of the information that has been provided in this thread in appropriate places in the app. For example, I didn’t previously know that rename won’t affect future transactions and I didn’t previously know that logo submission won’t affect future transactions unless approved by Emma team.