The "double vision" headache: why your marketplace transactions won't kiss and make up
There is a specific kind of frustration reserved for the YNAB-ing marketplace seller. You’ve just finished a productive week of sales on Etsy, Amazon, or eBay. You’ve been diligent. You manually entered your transactions as they happened, you assigned your category groups, and you’re feeling like a Rule 1 champion.
Then the bank import hits.
Suddenly, your perfectly balanced register is a mess. Instead of your manual entries and bank imports merging into a single transaction with that beautiful green "Matched" icon, they sit side-by-side like awkward strangers at a party. You have two entries for the same shipping label. Two entries for that $42.50 bulk bubble wrap order. One is manual; one is from the bank.
This "double vision" leads to a reconciliation spiral. Your bank balance doesn't match your YNAB balance, you start WAM-ing (Whacking-A-Mole) just to cover the ghost spending, and eventually, you’re tempted to hit the "nuclear option"—doing a Fresh Start and losing your data.
If you’ve ever stared at two identical transactions and screamed, "Why won't you just match?!" I've been there. Let's look at why marketplace merchant mapping fails and how to fix your workflow so you can get back to actually running your business.
Why marketplace mapping fails (the science of the mismatch)
YNAB relies on specific logic to trigger an auto-match. When marketplace sellers are involved, that logic often hits a brick wall. Here are the six primary reasons your transactions are refusing to merge.
1. The alias maze: Amazon*123 vs. Amazon
Marketplace sellers often deal with "messy" payee names. You might enter "Amazon" manually, but the bank import comes through as AMZN MKTP US*PR12345. To YNAB, these are two different entities. If the names don't look similar enough to the algorithm, it won't suggest a match.
As discussed on Reddit, even if you think they look identical, one might have a trailing space or a special character that breaks the link. It’s annoying, but the software is just being literal.
2. The 10-day matching window
YNAB has a built-in safety mechanism: it only auto-matches transactions that occur within 10 days of each other. For most people, this is fine. But marketplace processors like Stripe or PayPal often hold funds or delay payouts. If you record a sale on the 1st but the bank deposit doesn't clear until the 12th, the matching window is closed. The bank import appears as a brand-new transaction, and you're stuck with manual data entry fatigue. Source: r/ynab
3. The moving target of gross vs. net
This is the big one for sellers. Honestly, it's the most common way to break a budget. You sell an item for $100. You enter $100 in YNAB. However, the marketplace takes a $3.50 fee and deposits $96.50 into your bank. When the bank import hits for $96.50, YNAB looks at your manual $100 entry and ignores it because the numbers don't match. This is where your balances start to drift. Source: r/ynab
4. Merchant tip and fee adjustments
Similar to the gross/net issue, marketplace transactions are often updated by the merchant after the initial authorization. If you scan a receipt for a supply run that includes a tip or a post-purchase surcharge, the initial amount YNAB "saw" might change. If the imported amount doesn't perfectly match the manual amount to the penny, the auto-match won't fire. Source: r/ynab
5. Manual clearing vs. matching
I've seen this trip up even experienced budgeters. A common mistake is manually clicking the "C" (Cleared) button on a manual transaction before the bank import arrives. When you do this, you're telling YNAB this transaction is finished and confirmed. When the bank data eventually flows in, YNAB assumes it's a new cleared transaction rather than a duplicate. Source: r/ynab
6. Payees vs. transfers
When money moves from Stripe, PayPal, or your Amazon Seller Central account to your bank, it is a transfer between accounts, not a "payment." If you’ve set up your marketplace account as an "Off-Budget" or "Tracking" account, but you record the bank deposit as a standard income payee, YNAB's internal metadata won't allow them to match. The transaction types are fundamentally different.
Quick fix: the manage payees power move
If you're drowning in Amazon*123 and Etsy_Seller_99 aliases, the fastest way to fix your merchant mapping is the Manage Payees tool.
- Go to your web app (this is much easier on a desktop than a phone).
- Click on your budget name in the top left and select Manage Payees.
- Look for all the variations of your common marketplace sellers.
- Select them all and use the Combine feature.
- Create a Renaming Rule. Tell YNAB that anytime a transaction contains "AMZN MKTP," it should always be renamed to "Amazon."
By consolidating these aliases into a single mapping rule, you help YNAB recognize that your manual entry and the bank import are the same thing.
Long-term prevention: the marketplace seller workflow
To stop the reconciliation spiral, you need a workflow designed for the complexity of online selling. This isn't always straightforward, and that's okay.
Use a holding account
Don't have your marketplace payouts go directly to your "Ready to Assign." Instead, create a separate account in YNAB (either a Checking or a Tracking account) called "Stripe Holding" or "Amazon Balance."
- When you sell: Record the gross sale in the Holding account.
- When the fee is taken: Record a split transaction or a separate outflow in the Holding account for the fees.
- When the money hits your bank: Record this as a Transfer from the Holding account to your real-world bank account.
This bridges the gap between the gross sale and the net deposit. It ensures your real-world bank account matches YNAB to the penny.
Master the match button
Stop clicking the "C" button manually. If you see two transactions that should be one:
- Select both transactions using the checkboxes on the left.
- Click the Edit menu.
- Select Match.
This merges them into one, keeping your manual category while using the bank's cleared status. It also teaches YNAB's logic how to handle those merchants in the future.
Handle the moving target with splits
If you know a marketplace fee or a tip is going to change the final amount, enter the transaction as a Split.
- Line 1: The amount you expect to see at the bank.
- Line 2: The fee/adjustment. This ensures the net amount matches the bank's digital footprint, allowing the auto-match to trigger. Referencing Reddit troubleshooting.
When to try a different approach
Sometimes, bank sync is simply too slow or too messy for a high-volume seller. If you are processing dozens of orders a day, waiting 3–5 days for a bank import to prove you spent money on shipping is a recipe for a broken budget.
If you find yourself manually matching more than 50% of your transactions, it’s time to lean harder into manual entry with a bit of help.
This is where Snapt comes in. Instead of waiting for the bank to tell you what happened, you can scan your marketplace invoices, shipping receipts, or supply orders the second they happen.
Snapt extracts the merchant, the date, and the exact amount—including those pesky fees—and pushes it to YNAB instantly. By the time the bank import finally arrives 10 days later, the data in YNAB is so clean that the match logic actually works the way it was designed to.
No more reconciliation spirals. No more double vision. Just a business budget that actually reflects reality.
Ready to stop fighting with your bank imports? Try Snapt for free and see how AI-powered receipt scanning makes YNAB merchant mapping feel like magic again.