nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Quickfill specifying Transfer does not create entry in the other account

HVW

I have set up quickfill rules to record a transfer between accounts. When these get applied upon import from my financial institution the rule appears to be applied in the imported account but no record is generated in the other account of the transfer. This appears to be a bug unless there is some other explanation. Can this get fixed please?

Find more posts tagged with

Comments

HVW

Not sure where to find the rule to screenshot but I can confirm that "Transfer:[otheraccountname]" does appear in the Category field as shown here. I can also confirm that "Allow creation of linked transfers using the category field" is checked in Quicken > Settings > Register.

HVW

Thanks - setting it up as a scheduled transaction would not really be practical as there are different amounts whenever this happens and it is not on a consistent schedule. I'll take a look at your suggestion and try to figure things out. I am still suspicious this is a bug though.

HVW

Found it - here is what I see

Screenshot 2023-04-29 at 10.37.38.png

jacobs

In your register for the account you are showing (e.g. not B2B Bank), could you temporarily make the Transfer column visible. Then double click the transfer transaction and see what it shows in the Transfer column. I'm curious if there is a red circle with an arrow like this:

Screen Shot 2023-04-29 at 11.26.47 AM.png

or a gray circle with a red line through it, like this:

Screen Shot 2023-04-29 at 11.31.44 AM.png

Either of those indicates Quicken thinks it's an invalid transfer. A transfer should look like this:

Screen Shot 2023-04-29 at 11.29.37 AM.png

and clicking on the circle/arrow icon should open a separate window for the other account, showing you the transfer's other side.

UKR

As far as I can determine, you don't need the 2nd Split line in the Quickfill rule. You're transferring money from [otheraccountname] to [B2B Bank], so only 1 Split line would be needed.

The Category or Transfer field in the transaction must name the transfer-to account which is receiving the money. The transaction itself must be created in the account register where the money comes from, e.g., you're transferring money from [ABC Checking] to [B2B Bank]. When done correctly, a matching pair of transfer transactions will exist in your registers, one in ABC Checking, one in B2B Bank.
If the transaction you're showing is/was created in the B2B Bank register, then you'd be transferring money back into the same account … which is incorrect.

HVW

@UKR - thanks - The transfer is created in the other account (not B2B Bank). The second line in the split shows up without my doing anything and cannot be deleted (I did not use a split when I created the rule). I am able to create the transfer manually.

When the Quickfill has failed to create the other side of the transaction I can delete the category altogether and save the transaction. Then I can edit the category manually to make it a transfer again and the other side of the transaction DOES appear. This is why I think it is a bug.

HVW

@jacobs - thanks for the suggestions - I will have to wait until I have a new import now to do this experiment

HVW

@RickO yes - I am certain - I started to spot this when the balances in the other account were wrong. The other side of the transaction was definitely missing

jacobs

The symbol in the Transfer column, when you next download one of these transactions, will give us some indication of what Quicken is doing with the transaction. Usually if there is an invalid transfer in the Transfer field, Quicken will change the Category field to a generic "Transfer" (without the account name), but that doesn't appear to be happening in your case based on your first screen shot.

mmorgan21

I am having the same problem - this is a bug and is not consistent. It is always resolved by changing the originating transaction to another category then back to the transfer category. The entry then shows up in the destination account.

Quicken, please add this to your backlog to investigate.

jacobs

@mmorgan21 Quicken, please add this to your backlog to investigate.

This website is not Quicken Support, and the developers are unlikely to ever see your comment here. If we are able to figure out a way to consistently reproduce this issue, though, it can be reported and added to Quicken's bug database.

HVW

> @jacobs This website is not Quicken Support, and the developers are unlikely to ever see your comment here. If we are able to figure out a way to consistently reproduce this issue, though, it can be reported and added to Quicken's bug database.

It happens consistently for me so pointing Quicken Support to this thread should provide sufficient detail. Where does one file bug reports so that they can investigate?

jacobs

It happens consistently for me so pointing Quicken Support to this thread should provide sufficient detail. Where does one file bug reports so that they can investigate?

@HVW You can document the issue with text and screenshots and submit a bug report from the Quicken program, using Help > Report a Problem. Be as detailed as you can about how someone at Quicken can reproduce and see the problem. You can include the URL of this thread if you think it will help in explaining/depicting the problem.

The problem with Report a Problem is that it's a one-way flow of information into a black hole. Your submission won't be acknowledged. There's no way to know if they were able to verify it and document it as a bug to be fixed or unable to verify it and discarded the report. And if they can reproduce it, there's no way to know how long it will be until it's fixed; some bugs get fixed in the next release, while others languish for months or years.

The other approach, which allows for some interaction, is to call Quicken Support. They can do a screen share to view what you're seeing on the screen, and then if necessary, pull log files if they will help document the issue. If you can get them to see the problem you're seeing, and if you have a good support representative on the phone, they can escalate the issue to the developers as a bug report.