Hello everyone,

I’m experiencing the same issue and want to share what I’ve learned after engaging Intuit Support.

I opened Case ID #15150795790 and spent several hours over multiple days with two different support technicians. Both concluded that the issue required escalation to backend engineering, referred to internally as ES Triage.

The escalated team ultimately dismissed the issue as a “product limitation” and stated there was nothing they could do. That characterization is misleading.

Here is the actual problem:

The Custom Fields under Vendor Setup → Additional Info are explicitly designed to store user-defined data. When you customize a transaction report, these custom fields correctly appear as selectable columns. However, when the report is run, only the column header appears—none of the data entered in the Vendor Setup is displayed.

This is not a limitation of functionality; it is a reporting defect. The system recognizes the field, exposes it in report customization, but fails to return the stored data. That is a coding issue.

Labeling this as a “product limitation” avoids accountability while leaving users with broken functionality that behaves as if it should work—but doesn’t.

I’ve used QuickBooks for over 25 years, and this is not the level of transparency or quality I expect from Intuit. Calling a defect a limitation does not make it one. It’s disappointing, and frankly, undermines trust in the platform.

Posting this here so other users are aware—and so Intuit understands this is not an isolated complaint