When software companies are interested in Tensoft's Revenue Cycle Management (RCM) product, we first try to determine a fit for their requirements, so that no one's time is wasted.  Even if they have not yet created a requirements document, we find that a lot can come out of considering these three variables:

1) Billing. How does your company go to market (eCommerce, enterprise agreement, channel model, etc.)?  You'll want to look for a billing system or a billing support system that matches your go-to-market model.

2) Revenue Recognition. The rules for software industry revenue recognition are complex and changing. For the basics, you'll need a sub-ledger for deferred and recognized revenue analysis and appropriate methods and models to support your revenue recognition models.

3) Revenue Compliance. Could be part of the above, but is often a sub-set of that, and one that not every company needs.  There is no easy way to describe this, but if you have a sales process with multiple related elements in it (like software plus maintenance), and there are different recognition periods for the elements, you are most likely subject to more complex accounting guidelines.

Tensoft Revenue Cycle Management (RCM) supports billing requirements as well as complex software revenue recognition and contract management.