Leslie Simmons Sure. I was just working with someone on a client service team at my firm on an issue she was having with custom fields. She had four custom fields that she wanted to print on customer invoices. QBO allows you to have four custom fields, but you can only print three of them on customer invoices. It seems like an arbitrary choice to allow four active custom fields but then allow only three of them to print on invoices.

Also, she had a special type of invoice that was only used for one customer, and she wanted different custom fields to appear on that special invoice type. QBO does not allow you to do this. If you select a custom field for printing on invoices, it prints on all invoice templates. You can't choose which custom fields to print on each invoice template.

Beyond that, I think it's really stingy of Intuit to only allow four custom fields. Custom fields are a great way to add flexibility to QBO and to accommodate clients of varying industries with different data tracking needs. It wouldn't cost them a thing to allow for 10 or 20 custom fields.

It's true that this is a very niche situation that might not apply to many QBO users. However, I will note that this particular client converted to QBO from QBD, and all of this custom field functionality was available in QBD. it continues to frustrate me that Intuit pushes users of its QBD product to convert to QBO, and yet QBO still doesn't have all of the functionality of QBD. When you press Intuit about it, they just kind of shrug.

Adam Messner, I haven't played with them yet. Mainly I haven't done so because the custom fields in QB Desktop Enterprise were unreliable for building reports or even showing up in some reports. Is that the kind of thing you are running into?

Mark, on Canny Feedback No. The fields aren't unreliable. It's just that the functionality is really poor. Custom fields seems like a half-baked feature that probably never should have been released. My understanding from Intuit is that they don't have any plans to add additional functionality to custom fields, either.