I'm aware of all that. I've read enough QBO support to know to take those steps when something comes up.
So, I:
1.made sure Chrome is up to date
- cleared Chrome's cache, etc.
- tried it again
- got EXACT same results
2. went into Chrome private mode
- got EXACT same results
3. went into MS Edge, updated, etc.
- got EXACT same results
4. went into Firefox, updated, etc.
- got EXACT same results
As a summary, then:
1. I get different possible matches for each specific type of transaction - Stripe deposits to my bank in this case - while using the same date range
2. I get the Suggested Matches option only on SOME Match Transaction attempts - but somehow QBO is consistent as to which ones
3. on some transactions, I've even INCREASE the number of possible matches when I NARROW the date range!!!
4. as far as remembering past transactions, QBO keeps suggesting the "Bank Fees" account for all my Stripe deposits - and I've NEVER categorized one into that account
I'm thinking that there MUST be something different about these transactions to create the different behavior - something that isn't visible to me. Why would QBO treat one Stripe deposit differently than another? The absolute only thing I see different from one to another (other than date and amount ) is a unique alpha-numeric code at the end of the Bank Memo, and I can't image that could influence much.
But can you tell me what criterion triggers the Suggested Matches, for instance? That would at least be a start.
Or is there possibly some difference between transactions that have come in via the QBO Bank import, as opposed to by the automatic downloads? Although the majority of 2020's transactions came in via QBO Bank import, my problems seem to involve only those.
Or is one version (i.e., Business vs Accountant view) that's superior? Would the Accountant version of QBO maybe help?
My QBO always opens as "app.qbo.intuit.com". I don't recall it starting with "app" in the past - is there maybe some other URL that might work better?
Anyway, I think there's every indication that the browser is not the problem.
