...
What else do we have to do / do we have to do in discussion with our customer prior to configuration
Configuration Process
NOTE: No customer data can end up in this guide, this will be published to Logisense.com
Back-end Configuration
We need to detail the configuration process we perform here step by step in chronological order. E.g. to enable rev rec reporting we set up stored procedures and then describe what each stored procedure does. This should not be written as numbered steps for the user to follow, this is a description (overview) of the back-end config work that we do and why we do it.
...
The LSB configuration is something the customer/prospect will want to see (we need a few screenshots).
Some info below from Chris B on details needed in the LSB UI config walkthrough:
====
the main settings we are going to want to talk about are: the custom field on the service called Rev Rec Rule. it looks like this:
...
We use this rule to determine how revenue is going to be recognized. It is tied to the order/contract the service/package is associated to.
for SSP "standalone selling price" we use the pricing set at the package frequency level. If someone were to apply a discounts on top the SSP would be calculated using the based prices defined in the product catalogue.
The Export reports that we talk about for Truphone are what we would typically provide.
====
Revenue Recognition Reports
Here we should detail the output of the configuration above:
...
Configuring how Revenue Recognition will work
Once the initial back-end configuration aspects are completed the rest of the configuration is handled inside the LogiSense Billing application.
<<determine if the report config or the custom field config comes first here>>
Rev Rec Rules
Rev Rev Rules are configured on custom fields in the system and allow you to define how revenue should be recognized according to your needs. The custom field is defined on the product sold (service).
<<how is the rev rec rule applied to sales orders and contracts if it is setup at the service level?>>
...
Standalone Selling Prices
To determine the standalone selling price (SSP) the pricing configured in the LogiSense Billing Product catalog is used. Specifically, the pricing set the package frequency level. If a discount were to be applied to a service the SSP would still be calculated using the prices defined in the catalog.
Revenue Recognition Reports
Thinking here we need:
to describe the report config (screenshot or two would be nice)
call out anything that’s important in the config (like the Rev Rec Rule UI above)
describe when the report is generated
describe the output and what you can do with it (again screenshot would be nice)
specific reports to talk about/demo are Billed Revenue, Deferred Revenue and Unbilled Revenue
as noted earlier)