Jobs Only

Sep 21, 2009 4 Replies

Just verifying that QB Premier 2009 (if that matters) cannot create a Job without having a customer first. True, without customers, you have no jobs. But...



I am working QB to support a non-profit and we are trying various avenues to distinguish (to be sortable, searchable, filterable) dues-paying members (on an accrual basis) with other types of people who give us money for the various "cost centers" (my boss's words, not mine).



I do have the book "Running your Non-Profit in QB" (or something like that), and there's some interesting advice. But I don't think it covers what I am truly wanting to discover...



I have not found a way to generate an Open Invoice Report or Aging Report (maybe others) that filters on a specific job. (I have a nice bookkeeper, but she doesn't know everything about QB.)



"Job Type," yes. But that may be too broad, maybe not. "Customer Type," haven't explored that. Maybe a good candidate is the Memo field or one of the Custom fields.



Does the Customer Center filter box use wildcards? That is, all customers whose first character is "M" with the sequence "Member" in it? (M*Member*) I could experiment, and I will, but I also ask because there may be someone who found a peculiar approach/answer to this problem.



(I'm an IT Director who's been asked to program a line of communication from our eCommerce store to QB via IIF. We sell annual memberships, advertising in our journal, and exhibit space at our conferences. And other stuff.)


My thought is to stop trying to filter on jobs but to filter on items sold. Perhaps a sales by customer detail report with a filter on the membership item?

Unfortunately QB doesn't support grep or wild cards and isn't a particularly good contact manager either.

What about classes? Would that be an option? My non-profit uses classes to identify events held.

Custom fields may or may not get passed down to all of the reports you are trying to run.

And, OP will need iiuc to make sure whatever choice(s) made are part of what can be imported via iif which ain't everything plus the potential problem of internal links aren't generated from iif importing...

--

My recommendation would to create a customer Customer Type list and then assign it when adding the customer. You can filter on them when running reports. If you want to get more specific, you can create classes in addition and classify each invoice / job and have multiple types of invoices under the same customer. These also can be filtered. Hope that helps.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required