Summary
Outlining three issues with transaction merchant data I’ve noticed over the last few months that seem to lead to multiple transaction merchant profiles for a single merchant. Apologies for the long post, but I’ve found it difficult to explain the issues succinctly.
NB: Android user.
Issue 1 - Lowercase postcode issue
TL;DR
Unfilled “Country” section in merchant details causes lowercase postcodes. Also leads to multiple merchant profiles for a single merchant (discussed further in Issue 3).
Issue in Depth
– This issue is best illustrated using an example.
Image 1 - transaction view of merchant (“The Slug”). Note uppercase postcode and correct logo present. AKA Profile 1.
– Image 1 shows the transaction view of a merchant in MONZO. Note that merchant has the correct logo and the postcode is all uppercase as it should be. The merchant profile for this transaction will referred to as ‘Profile 1’.
Image 2 - transaction view of same merchant (“The Slug”). Note lowercase postcode (boxed in red) and no logo present. AKA Profile 2.
– Image 2 shows a different transaction from the same merchant. However, in this transaction, the logo is now gone and the postcode is lowercase, except the the first letter. The merchant profile for this transaction will referred to as ‘Profile 2’.
– Exploring these merchant profiles further by going into “IMPROVE NAME, LOCATION OR LOGO” ⇒ “Improve the name or location” ⇒ “Add merchant details manually” gives image 3 for Profile 1 and image 4 for Profile 2.
Image 3 - merchant details for ‘Profile 1’. Note the postcode is in uppercase and “United Kingdom” is the value under country.
Image 4 - merchant details for ‘Profile 2’. Note the postcode is in uppercase, but there is no value in the “Country” section (boxed in red).
– I have found a number of transaction merchant profiles for different merchants, including a Dutch one, which have this same issue. Profiles with an unfilled “Country” section always have a lowercase postcode, while profiles with a filled “Country” section have an uppercase postcode.
– There are also cases where the correct logo is present on the merchant profile with a lowercase postcode and no logo is present on the merchant profile with an uppercase postcode. An example of this is given in image 5 and image 6. Both these merchant profile exhibit the behaviour in their merchant details as outlined in the previous point (ie: unfilled “Country” = lowercase postcode).
Image 5 - transaction view of merchant (“The Clapham Grand”). Note uppercase postcode and no logo.
Image 6 - transaction view of merchant (“The Clapham Grand”). Note lowercase postcode (boxed in red) and correct logo present.
– MONZO treats these two merchant profiles as completely separate merchants even though they are actually transactions from the same merchant. This can be seen by the discrepancy between the “Number of payments” value in the images: one in image 5 and two in image 6 .The separate profile even show up as separate merchants on the monthly reports in the “Spending” tab as seen in issue 3.
Suggested Fix
– Make filling out the “Country” section compulsory for MONZO users when submitting transaction merchant details manually.
– Make filling out the “Country” section compulsory for MONZO employees when confirming transaction merchant details.
Issue 2 - “Somewhere in” issue
TL;DR
Some merchant profiles have “Somewhere in” before their address for no apparent reason.
Issue in Depth
– For some merchant profiles the words “Somewhere in” appear before the full, correct address of the merchant.
Image 7 - transaction view of merchant (“The Clapham Grand”) with uppercase postcode and no logo. The words “Somewhere in” appear appear before the merchant’s address.
Image 8 - transaction view of merchant (“Chimayo”) with lowercase postcode and correct logo. The words “Somewhere in” appear appear before the merchant’s address.
– Images 7 and image 8 demonstrate that the issue seems to be unconnected to Issue 1.
Suggested Fix
– Automatically remove “Somewhere in” if a house number or name is provided in the address (“Somewhere in” makes sense if only street or road is specified).
Issue 3 - Multiple merchants profiles for the same merchant
TL;DR
Multiple merchant profiles exist for same merchant. MONZO treats each profile like a completely different merchant (ie: separate merchants in “Spending” tab, counts number of transactions separately) . Possibly due to different card readers.
Issue in Depth
– A number of transaction merchant profiles have been created for a single merchant. MONZO treats these merchant profiles as independent merchants even though they are transactions from the same merchant.
– “Number of payments”, “Average spend” and “Total spent” values are calculated independently for each merchant profile.
– Each merchant profile shows up as a separate merchant in the “MERCHANTS” section of the monthly reports found in the “Spending” tab as seen in images 9 & 10.
Images 9 & 10 - overview of “MERCHANTS” section in “Spending” tab displaying different merchant profiles for a single merchant (“The Clapham Grand”) over a month. Unrelated transaction merchants have been blacked out.
– Images 9 & 10 show that there were five separate merchant profiles for “The Clapham Grand” in a single month:
- Uppercase postcode, correct logo.
- Lowercase postcode, correct logo.
- Uppercase postcode, no logo, “Somewhere in”.
- Lowercase postcode, correct logo (again).
- Uppercase postcode, incorrect logo.
– Originally some of the transaction names contained numbers such as “Clapham Grand 5” and “Clapham Grand 11”, before I reported them, which makes me think they might be linked to separate card readers.
Suggested Fix
– Method of reporting separate merchant profiles which belong to the same merchant for MONZO staff to check and combine into a single merchant profile.
Suggested implementation
– Option in the “IMPROVE NAME, LOCATION OR LOGO” section for reporting that transaction A is a multiple merchant profile (poosible name = “Report multiple merchant profiles”. This would open a view of all your transaction merchants with the same name as transaction A where you can select all the merchant profiles that should be combined. The information would then be passed on to MONZO staff to be combined into a single merchant profile.
Issue 4 - Differing Website Addresses for Online Transaction Merchants
TL;DR
Different website address forms for website addresses in online transaction merchants.
Issue in Depth
– There are also cases of multiple merchant profiles for single online transaction merchants. Both merchant profiles in image 11 are online merchants profiles for the same merchant (“Uber”).
Image 11 - overview of “MERCHANTS” section in “Spending” tab displaying different merchant profiles for a single online merchant (“Uber”) over a month. Unrelated transaction merchants have been blacked out.
– Going into “IMPROVE NAME OR LOGO” ==> “Improve the name or location” gives image 12 for a transaction belonging to the Uber merchant profile at the top (£81) and image 13 for a transaction belonging to the one at the bottom (£26).
Image 12 - details for transaction belonging to top merchant profile in image 11. Note the website address boxed in red.
Image 13 - details for transaction belonging to bottom merchant profile in image 11. Note the website address boxed in red.
– The website addresses and logos are the only differences between the two profiles.
– I have also come across website addresses of the form “https://www.monzo.com/”, “www.monzo.com” and “monzo.com” (MOZO web address used as example).
Suggested Fix
– Standardise website address form would allow MONZO to easily locate multiple profiles as they could just search for profiles with the same details - ideally “www.” (automatically remove “https://”). “www.” appearing automatically can be used as a prompt for people to not include “https://”. (I’ll expand on the ‘appearing automatically’ point in a seperate post in the future).
EDIT: included issue 4 on online transaction merchants
EDIT 2: suggested method to implement combining multiple merchants under "Issue 3 - Suggested Fix