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

Budget report fails to recognize linked checking account

Paul Smith2

On Release 60.20 the budget report fails to recognize a linked checking account to an existing investment account. This is a new problem. A saved budget report from last year (2024) does not have the same problem. Same accounts in Quicken. In fact, I can change the date range in the old report and it readily picks up the expected transactions.

I've been trying to "fix" this problem by identifying changes in the "settings" for the report by only asking the report to use the linked checking account in question and not the underlying investment account, but this strategy hasn't worked.

I need some help here….

Find more posts tagged with

Investment Reports

Comments

q_lurker

Edit /Preferences has Early Access settings that affect reports. If those options are checked, try unchecking them.

Jim_Harman

On the Planning > Budgets page, click on Budget Actions and select Select accounts … Make sure the linked checking account is checked in the Banking section. The selections you make there affect which accounts "feed" the budget and Budget reports.

Please let us know what fixes this problem.

Paul Smith2

dps comments

Early Access settings are not checked to be active
The investment account in question does indeed have "linked checking account" checked

Apparently the process of report generation through the Planning/Budgets page (suggested by Jim Harman) impacts report generation more directly than simply modifying the errant report through the "Accounts" page on the report itself which I tried to do numerous ways.

Without changing anything in the investment account itself, simply removing the investment account (but not the linked checking account) from the list of accounts to be included through the Planning/Budgets interface cleared up the problem.

Thank you Jim Harmon!