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; } } }

split registry entries getting changed when tabbing to next field or when adjusting the split total

gj8

I have been using Quicken for 20+ years. This is the first time I have seen anything like this. I enter an amount for a split entry and tab to the next field and the value I just entered gets changed. Sometimes by pennies, sometimes by more. When I verify all the values I have entered and then click on Adjust to ensure the total is accurate, the amounts of one or more entries actually get changed, and I have to go back to validate them. This happened after the most recent update to Quicken Classic Premier. If it is a simple registry entry then this does not happen. It only seems to happen when doing split values for a registry entry like itemizing for a credit card payment.

Please fix this issue ASAP!!

Find more posts tagged with

Windows

split transactions

Comments

Quicken Laura

Hi @gj8,

Thanks for reporting this. Based on your description, this appears to be related to a known issue with the new Split % column in Quicken.

When entering a split transaction and using the Tab key, the Split % field can unexpectedly receive focus even when the “Show %” option is unchecked. If a value is entered there, Quicken may recalculate the preceding split amount, which can make it appear that the amount you just entered has changed, sometimes by only a few cents.

This behavior is not expected and is being tracked under a known issue. The “Show %” setting works as designed, but the Split % field should not interfere with normal keyboard navigation when the option is unchecked.

Our team is currently working on a resolution. Any new updates will be posted in the community alert, so I recommend bookmarking it to stay informed.

Thank you again for bringing this to our attention.

mshiggins

@gj8 a workaround while you await a fix is to roll back to an earlier patch version. See this comment for more details:

https://community.quicken.com/discussion/comment/20579259#Comment_20579259

Jim_Harman

@gj8 Until this is fixed, another workaround for this problem is to use the mouse or the Enter key rather than the Tab key to move to the next split line.