One of the most frequent custom features that I have been asked to do is implementation of deferred revenue recognition. This is useful primarily for subscription based services, where a service plan can be sponsored or prepaid, but the revenue can't be consumed until the service is activated.
In previous releases (circa 6.x), this can be achieved by modifying multi-month cycle start/end dates before the cycle event is rated. The system would use the custom dates to set revenue start/end dates for the event. Sometimes the future dates confuse the system (remember it's supposed to be 'real-time no limit', so back-dated & future-dated are with limit), in that case I use post rating hook to rectify the situation.
In the more recent releases (circa 7.x), the rate flag used to determine rating scenarios is no longer set. It looks like rating process flow has changed quite a bit. I need to figure out soon what to do here to upgrade this feature. Just wish it is part of supported out-of-box features. As one of my colleagues always says 'Don't %@#$ with dates', so do it at your own risk. :)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment