Currently when running a billing or payment run you can run it for accounts in all batches in your tenant or just one batch. Due to our high volume of accounts, we have our accounts segregrated into 8 different billing batches. We run nightly bill and payment runs for all but one of these batches. It would help us greatly, if we could schedule this with just 1 nightly bill and payment run by selecting all applicable batches, rather than having to schedule one per batch.
... View more
Most organisations use batches to group accounts together logically for bill runs. It would be useful to have an option to automate the allocation of a batch to a particular account when various objects on the account get added/removed/updated. We need a way (like a rules engine) to automate which Batch an Account goes into when: It is created manually in the User Interface It is created through API It is created through Z4SF Details on the Account change Details of subscriptions on the Account change Details of charges on a subscription on the Account changes Data attributes we need to track/evaluate in order to ascertain what Batch an Account goes into: Account Billing Entity Account Currency Subscription Term Type (e.g. Evergreen or Termed) Subscription Status (e.g. Active or Cancelled) Subscription Charge Types (Advance or In Arrears)
... View more