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

Schedule C not including all Business Income

wehrmeis

Windows Classic V R59.10, Build 27.1.59.10

After one of the recent updates, I noticed that the Schedule C - Profit or Loss from Business Report no longer shows all business income. It only shows the income for the first invoice that a payment was allocated to.

I have a cash-based business and regularly receive checks from a customer that cover more than one invoice. When entering the payment, I allocate it to all the applicable invoices. In the past, the full amount of the payment was included in the schedule C report. Now I am only seeing the amount for the first invoice covered by the payment.

Find more posts tagged with

Comments

wehrmeis

Note that each invoice has a single line item assigned to a business income category with Schedule C as the tax category. Each invoice has the business tag associated with this business. I have tried to edit and re-save the payment to see if that fixes the issue and it doesn't.

I submitted a service ticket to Quicken support and have not received a response.

Has anyone else seen this problem?

Jim_Harman

Did you submit the "service ticket" using the Help > Report a problem link?

You will not get a response to an electronic submission, but apparently they review and prioritize the submissions and use the data to help resolve problems they decide to work on.

Forum Moderators sometimes review issues discussed here and refer them to Development, but if you want Quicken to work on a problem, I recommend you contact Support via phone. Be sure the support agent understands the problem and gives you a ticket number for future reference.

wehrmeis

Jim - Yes, I submitted a ticket via the report a problem link. I'll try contacting support via phone as you suggest.

wehrmeis

This issue was fixed in release today:

Version R59.35

Build 27.1.59.35