Current Budget Report showing zero for actual amount

When I run the "Current Budget" report, I am seeing zeros or incorrect amounts for one of my categories. For example, I record my interest expense in a subcategory of Housing in the format "Housing:Interest Expense", but the report shows "0.00" for every month. When I click on the "0.00" however, it opens a new window with the correct amounts; they just don't appear in the main report.

The item is budgeted, and I run the report with "Budgeted Categories Only," though i have the problem whether I run with all categories, or non-zero budgeted categories.

I have validated and super-validated the file, and I have confirmed that I am looking at the correct budget and fiscal year.

Has anyone else run into this?

Comments

  • UKR
    UKR Quicken Windows Subscription SuperUser ✭✭✭✭✭

    Which month's column are you looking at? The current month, i.e., November? Or some prior month?

    What date is the Housing:Interest Expense transaction due? Today is 11/19 … is it due after today?
    Has a real register transaction already been recorded or is it still a Scheduled Reminder?

    Please note that the Current Budget report prorates the budgeted amounts for the partial month, based on today's date.
    If you want to see the totals for November and the remainder of the year, try using the Historical Budget Report.

  • Gregory Allarding
    Gregory Allarding Member ✭✭
    edited November 20

    There is one Housing:Interest Expense Transaction every month, so it's in the current month (due 11/6), and all previous months. The transaction is in the register and is a reconciled transaction, albiet part of a split transaction if that matters.
    FYI, the Historical Budget report exhibits the same behavior.

  • UKR
    UKR Quicken Windows Subscription SuperUser ✭✭✭✭✭

    If you haven't done so already, please download and install the latest set of software updates. Release R 59.35 is said to have the bug fix for budget reports.

  • Thanks. I was on R59.18, just updated to R 59.35, yet the issue still persists.