We have a number of customer who have any number of "buyers" working for them.  At present, either we have to make entirely different accounts for each buyer, or roll them all into one account and invariably bother one or two of them because their names do not appear on the invoice, etc.
 
On top of which, having multiple accounts for customers makes it a delight to do a "statement".
 
Why not be able to have "sub" accounts so that each buyer can be listed individually, with contact information, yet all the purchases would get consolidated into a "master" account...  With the ability to track what each buyer is ordering??
 
Just and idea that would make our life easier and a number of our customer's happy...
 
John

Well, a great idea. Unfortunately the re-structuring of the data files and the subsequent re-writting of the code is REALLY REALLY significant to enable this sort of change. It is a pretty major change in a true relational database system with Object Oriented code, let alone in the DBA transactional database system with the TAS line-editor code.
 
Bottom line? I wouldn't hold my breath for ISTS to do something of this magnitude. They would have to charge too much to recoup the invested dev cost. Most DBA users simply don't want to pay.

The Customer account does have room for 5 different Contacts already with separate phone numbers and email addresses - are you already using these and need more?  Contact Manager can go to 9.  Allowing specification of which Contact's name and phone number was pulled into a Sales order and subsequently printed on the paperwork would be easy enough.
 
Also, SO-A already allows entry of an additional customer reference (immediately after the Payment Terms on the Header screen) so if you needed to use Karen's suggestion of additional customers, you could still use a single Bill To to make the Receivables and Statements simple and we could do something with the additional reference customer data on the paperwork.