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

Salary splits all messed up [Edited - Language]

Aholiab

This is a known problem, and I can't tell that anyone is attending to it.

My monthly salary reminder is set to split into expected categories, taxes, etc. I reported this last autumn, and I just looked at my June salary, and the numeric inputs are disassociated with their categories. That's very bad.

I use Classic for Windows and Android; I use both multiple times daily, so I depend on them.

But Quicken isn't trustworthy.🤔

I have the most recent version of everything, but not betas.

Find more posts tagged with

Windows

Bill Reminders

split transactions

Comments

Quicken Kristina

Hello @Aholiab,

Thank you for letting us know you're still seeing this issue! To clarify, are you seeing the same issue you described in this earlier post?

https://community.quicken.com/discussion/7970608/when-will-quicken-fix-the-bug-that-rearranges-all-the-split-items-within-a-regular-salary-payment

You mentioned that the split items are disassociated from their categories. Is the category blank, or is it like the categories in the splits are scrambled (correct categories, but lining up with the wrong number)? Are the numeric inputs correct?

I look forward to your response!

NotACPA

And in your message of last autumn, you stated:

"I do use the mobile app, and even the web app, so I hesitate to turn off synchronization.
This only happens at the end of each month, so I'll put up with the problem for now."

Since the Mobile app is the well suspected culprit, and you're apparently unwilling to turn it off, why are you still complaining???

Chris_QPW

I think @Aholiab has a perfect right to complain. If Quicken Inc is going to have a feature, it should work.

Yeah, I wouldn't touch Sync to Mobile/Web with a 100-foot pole, but it isn't unreasonable to complain about a feature that doesn't work right.

On other hand, I would say the main reason something like this doesn't get addressed is because they can't fix it.

Before the developer can fix a given bug, they have to reproduce it. Bugs like this, if even possible to reproduce, take way more time than Quicken Inc is willing to put into it. They just aren't going to dedicate a developer to weeks on end trying to reproduce/fix it.

NotACPA

I'm merely noting that the remedy, if not a fix, is well known … and the OP is unwilling to take it. So, the complaints ring hollow.