As mentioned in other UG threads, we are discussing how the 'Accept Payments Through Top Level Customer' feature can be enhanced to better meet our customers' needs in the future.
If you use or are interested in this feature, I would appreciate your feedback on the following questions:
1a. How many levels deep of parent/child customers do you use?
1b. Do you create invoices for mid-level parents & the top level parent, or always to the lowest level sub-customers? It would be helpful to better understand real world business cases for how hierarchies are used.
1c. If your trees go deeper than just 1 level of parent/child, is it critical to be able to accept payments through any customer in the hierarchy, top level only (like today), or lowest level and top level (but not necessarily parents in the middle)?
2. Would it be preferable to set, on the top level customer record for each 'tree', whether AR is managed per-sub-customer/through top level, or just be able to select either parent or child customer when you go to accept payment, to view open invoices?
3. If you use Accept Payments Through Top Level today, are you satisfied with the current behavior for displaying AR balances in customer records? (Each customer record in a tree displays the consolidated balances for the whole tree.) Would you rather see individual sub-customers' balances? If so, do you also need to see the whole tree's balances, or would it be enough to show them in the top level parent record only?
4. Do you need to be able to choose, on the fly, to generate statements for individual sub-customers or for an entire tree by selecting the top level parent (like today)?
5. Would you want to manage credit limits per sub-customer, one shared credit limit for the whole tree, or both at the same time? Does the top level parent need its own credit limit separate from the consolidated credit limit for the tree?