How to clean up messy merchant names in your transactions

To clean up messy merchant names, rename the garbled ones and merge the duplicates into one merchant. In Skwad, both happen on the Merchants page, and the change applies to every transaction already filed under that merchant.

Your bank knows where you spend money. It just doesn’t say so clearly. Friday’s dinner shows up as “SQ LOCAL BISTRO 492BNYC.” A phone charger from Amazon is “AMZN MKTP US*1K9A8B20Q.” The morning latte reads “TOAST COFFEE CO PORTLAND OR.”

The payee name is the one field that tells you where your money went, and it’s usually the one buried under reference codes and abbreviations. That’s more than an eyesore. Messy names break your automations, scatter one store across several spending lines, and make your reports hard to trust.

We built the Merchants page to fix this. Rename a merchant to something you’d recognize, merge duplicates into one, and see how many transactions each one has, all in one place.

Why merchant names get messy

Bank transaction formats date from the era of paper statements. Nobody needed them to be readable. They needed to identify the merchant and the transaction, so that’s what they do.

Square is a good example. A Square payment shows “SQ *” plus whatever name the business registered, which may not match the sign over the door. Amazon is worse. Depending on what you bought, you’ll see “AMZN MKTP,” “AMAZON.COM,” “AMZN PRIME,” or “AMAZON DIGITAL.” Amazon’s payment system treats those as separate merchants. You don’t.

Other processors tack on location codes, reference numbers, or timestamps. Some cut long names short. A chain can look different at every location, and paying with Apple Pay or Google Pay sometimes replaces the merchant name entirely.

So you end up with one coffee shop under three names, and two unrelated stores that look nearly identical. Budgeting on top of that means fixing transactions by hand, month after month, unless you clean up the merchants themselves.

How to clean up merchant names in Skwad

Every merchant Skwad has pulled out of your transactions lands on one page, Merchants. It’s in the main menu, and there’s a link to it in Settings too.

Each row carries a transaction count. Glance down that column and the priorities sort themselves out: the grocery store at 140 transactions is worth ten minutes, the parking lot you paid once is not.

Renaming merchants

Start here. Click a merchant’s name and type what you actually call the place.

“SQ *LOCAL COFFEE” becomes “Local Coffee Shop.” “AMZN MKTP US” becomes “Amazon.” “WHOLEFDS MKT” becomes “Whole Foods.” The new name shows on every transaction already filed under that merchant, back through your whole history.

The name sticks. When “SQ *LOCAL COFFEE” charges you again next month, Skwad files it under “Local Coffee Shop.”

Try to rename a merchant to a name you already use and Skwad stops you and suggests a merge. That keeps you from building a second “Amazon” when what you wanted was one (merging has its own tool, below).

Merging duplicate merchants

Renaming fixes ugly names. Merging fixes a different problem: one real store showing up as several merchants.

Shop at Amazon often and you could have “AMZN MKTP US,” “AMAZON.COM,” and “AMAZON DIGITAL” as three merchants in Skwad. Same company. Your bank’s payment processing just sees them differently.

Select the duplicates, pick the name to keep, and merge. Skwad moves every transaction from the others onto the merchant you kept, and the extra entries go away. None of the history is lost.

That pays off across Skwad:

Budget categories see one merchant instead of three, so the total is the real total
Automations need one condition for the merchant, not one per spelling
Search finds every Amazon purchase when you filter for “Amazon,” not just one variant’s
Spending reports show one combined line per merchant instead of scattered subtotals

Bulk actions with shift-click

Long cleanup lists go faster with shift-click. Click one merchant, shift-click another, and everything between them is selected. Then merge the whole set in one go.

This helps most on day one, when a few merchants have collected years of spelling variations. Select every Amazon variant, merge, and move on to the next one.

Drilling into transaction counts

Every merchant’s transaction count is a link. Click it and you land on your transaction list, filtered to that merchant.

Use it when a number looks off. Maybe purchases from different places got assigned to one merchant (you can move them to the right one). Maybe you really did visit that coffee shop 47 times last year, which is worth knowing before you set next month’s budget.

The count doubles as a check on your own work. Rename or merge, click it, and if every transaction you expected is sitting there, you’re done.

How merchant management improves your automations

Merchant is one of the conditions in Skwad’s automation engine. A rule like “if merchant is Amazon, categorize as Shopping” only works as well as your merchant data does.

With three Amazon spellings, you might need a rule for each. Merge the variants and a single rule covers every Amazon charge.

Fewer variants means fewer rules, and fewer edge cases to chase later.

How merchant management improves your spending reports

Skwad can show what you spent at each merchant over any date range. With messy data, that list is padded with near-duplicates that are really the same store. Clean it up and the list matches where your money actually went. Pair clean merchants with line item categorization and even a mixed Costco run lands in the right categories.

Take Target. Before merging, you might see “Target,” “TARGET *,” “TARGET.COM,” and “TARGET #1842” as four separate lines. After, it’s one “Target” line with the combined total, which is the number you need when you’re deciding how much of the month goes there.

Best practices for merchant cleanup

Start with high-frequency merchants: Your weekly grocery run outweighs a one-off hardware store trip in every report. Sort the merchant table by transaction count and work down.

Check for payment processor prefixes: A lot of confusing names start with a processor’s tag: “SQ *” (Square), “TST*” (Toast), “PP*” (PayPal), or “PYPL *” (also PayPal). Spot the tag and the real merchant is usually the name right after it.

Merge before automating: Clean up merchant names before you write rules for them. A rule pointed at a messy merchant can end up pointing at nothing once that merchant is merged away. Clean first, automate second.

Review periodically: New restaurant, new merchant. Every couple of months, shift-click through whatever showed up and merge any variants.

Use descriptive names: Your bank says “WHOLEFDS MKT 10234.” You say Whole Foods. Go with yours.

Frequently asked questions

Do renamed merchants stay renamed when new charges arrive?

Yes. Your names stick. When a new charge comes in from the original raw payee, Skwad files it under the merchant you renamed.

What’s the difference between renaming and merging?

Rename when one merchant has an ugly name. Merge when several merchants are secretly the same store: you pick the name that survives, and Skwad moves all their transactions onto it.

Where do I find merchant management?

Open Merchants from the Skwad sidebar. Every detected merchant is listed with its transaction count. Sort by the Transactions column to start with the merchants you visit most.

An hour of work that pays dividends for years

Cleaning up merchants isn’t exciting. It’s the work that makes the rest of Skwad better: reports you can trust, rules that fire when they should, and a transaction list you can read without decoding it.

Fixing names usually means renaming one transaction at a time. On the Merchants page you do it once, for your whole history.

To get going, open Merchants in the Skwad sidebar and sort by Transactions. The top of that list is where you spend most often, so it’s where a fix pays back fastest.

For each merchant that looks wrong: