I see a lot of problems with how the Slave & Sub Accounts deal with billing cycle items. I understand the billing cycle item for a slave account gets saved as a billing cycle item of the main reseller account, but i still see many problems with it. For example, Billing Cycle Server Actions do not work on slave accounts. Instead of triggering the server action for the slave, it triggers it for the main reseller account. I know you have said you were working on this and it should be available in the next version. This limits the products we can offer to slave account to only 1 product since we need to use the default server events. We cannot offer multiple products to slave customers since we can only use 1 server action (default) for slave accounts. If the slave accounts support Billing Cycle Server Actions we could offer any product to a Slave account. Also, I have "Show Billing Cycle With Domain/Emails" set to Yes. If I add a Domain to a slave account and enter the billing cycle item in the Services window, it does not show up under the Slave account's billing cycle items, nor does it show up under the main reseller account's billing cycle items. Nor does the billing cycle item get added to the main reseller accounts' generated monthly invoice.
Billing cycle events will always be based on the customer that "owns" it (the master account). The slave account technically does not have any billing cycle items, and the whole slave account "customer" basically is just there for informational purposes.