Manually entered transactions are not being matched to downloaded ones (edited)

Do you mean that the manual transaction won't automatically link to a recurring transaction when it later matches to a downloaded transaction?

I hadn't really ever thought about it, but yes, if you enter a manual transaction, you have to link it yourself to a recurring transaction.

The manual transaction should match with the downloaded transaction if they are the same amount. This doesn't always work but usually does. I don't have much problem with that.

A downloaded transaction that matches to a manual transaction won't link to a recurring because QS logically thinks they are different transactions. At least, that is my experience.

If you mean something else, please clarify. And I apologize if I have misunderstood.

@shely6875

I don't think you are talking about recurring series, but I could be wrong about that. I think what you are saying is something like this:

1. You enter a manual transaction to represent, for example, a payment made from an account,
2. Later, Simplifi downloads transactions from that account, including one that represents that same payment,
3. Simplifi does not recognize that both transactions (manual and downloaded) represent the same payment,
4. So Simplifi does not merge them into one transaction and you end up with two transactions in the account.

Is that what is happening?

FWIW, in my experience Simplifi almost always merges such transactions but occasionally fails. But I don't manually enter very many transactions. @SRC54 does a lot of that, so he may be able to help.

@shely6875

It may help if you create a rule for the downloaded transaction that changes the Payee to something that matches the Payee you use for the manually entered transaction.

I say this because I have been told by staff that having the "Payee after rule applied" match the Payee on a recurring series assists the matching engine in making the match. It may work the same way for matching a manually entered transaction.

See thread below:

@shely6875

I've lost the plot here … I'm not sure what you are saying is happening here.

Merging Problem

I thought the problem was that you were entering manual transactions and they weren't merging with the appropriate downloaded transaction. But the "Transaction detail" window you show above says:

So did you only have a manual transaction in the SAPPHIRE account and not in the "Shea Reimburse/Transfer" (or is it "Shea Reimbursement/xfr") account? And did the matching/merging problem get solved somehow?

Clearing Problem

It sounds like the current problem is that when you edit either side of the transfer transaction (by marking the Status as Cleared and then clicking the Update button) you get an error message saying "the other side of the transfer is in a split." Is that right?

But in reality, only one side of the transfer transaction is actually in a split — the side in the SAPPHIRE account. Is that right? (You could post an image of the "Transaction detail" window for the Shea Reimburse… side to illustrate that.)

If that is the case — Simplifi claims both sides are in splits only one is — I think one of the coaches will have to weigh in on whether this is a bug in the program. It doesn't make sense to me.

PS: Your clearing problem may be related to the one discussed here:

@shely6875

In the other thread I linked above, I made the following suggestion:

This is a shot in the dark, but did you try marking the (merged and cleared) transaction containing the splits as Pending and then marking it as Cleared again?

In your case, that would mean marking the transaction in the SAPPHIRE account as "Pending," then clicking Update, then editing it again and marking it as "Cleared" and clicking Update.

Have you tried that?