Quickbooks Credit Card Import Auto-Matching Transactions Never Input

Let's take a look on what is happening here, greh.

You mentioned that the Match function in QuickBooks Desktop started auto-matching your transactions and the transactions weren't posted to your register even after Approving them. We can do a few troubleshooting steps to verify that your company file and your QuickBooks Desktop are in good condition.

1. Update the QuickBooks Desktop release version.
2. Do the Verify and Rebuild process.
3. Close and reopen.

You can also use this link for additional reference if you encounter unexpected errors while doing the process: Fix data damage on your QuickBooks Desktop company file.

Let us know how this goes so we can provide you additional steps to fix this. Additional details about it would be much appreciated.

That is correct, it is Auto-Matching to transactions that were never posted/input in the first place (not sure what it "thinks" it is matching to).  If I select "Ignore" for these transactions they will re-appear in the case I import a credit card transaction period that overlaps a previously imported one (I will usually duplicate the last two days of the previous import to make sure I cover any lagging credit card transaction postings from their end).  If I select "Add/Approve" it clears them but it does not post to the credit card ledger (which is actually good because it is Auto-Matching the wrong account, which I cannot change).  If I select "Not a Match," this works for a few, that I can then re-code and edit the account, etc. and "Quick Add" and it posts properly.  However, for most, it just doesn't do anything to that transaction after selecting "Not a Match." 

So I followed the steps you have outlined.  I checked the release version, we are on R10 of 20.0 Enterprise, which seems to be the latest release according to the link you provided.  I then ran the Verify Data program, received result: "Quickbooks detected no problems with your data."  On the link provided it then states with this result that "no further action is needed."  However, should I still run the Rebuild Data program to see if this resolves my issue?

Thank you, this has solved the "auto-matching" issue, appreciate the help.

I do have one follow-up, however.  These transactions are now falling under a "Changed by Rules" category (which is okay because it is now coding to where I want it to), but there are a handful of other transactions that have all along been being "Changed by Rules" and I would prefer that to not be the case.  

When I click on "Rules" within the module, there are no rules listed, so I am not sure which "rules" these transactions are being changed by?

Any ideas on this?

Thanks for coming back here, greh.

To clarify, do these transaction shows under uncategorized income or expense? If so, this happens if QuickBooks couldn't find a match. The other possible reasons are the following: 

• Transaction is older than 180 days.
• The amount in QuickBooks is different than what is cleared on the bank.
• The transaction type is different in QuickBooks than at the bank. QuickBooks wants to match a check and an expense with ACH or debit/credit card swipe.
• Transaction was recorded in a different bank account.
• The transaction from the bank is a payment/deposit of two or more open transactions in QuickBooks.

You'll want to add each transaction or create another bank rule to post them to the correct category. 

I've got these articles to guide you with the process:

• Add and match Bank Feed transactions in QuickBooks Desktop
• Use renaming rules for Bank Feeds

Please keep me posted if you have any additional questions. I'll be around to help you out again. Take care and stay safe!

No they are all current transactions and generally code to the correct expense accounts (I just need to add more details to assign them to the correct job), it happens for the same recurring vendors.  I was just wondering why it becomes "changed by rules" if I have no rules.  Anyways, it is not a big deal like the auto-matching problem, which seems to be resolved (at least for now).  We can consider this matter closed and I will play around with the Rules section some more and review the links you have provided.

Thank you for your assistance.