...
This article provides an overview on how revenue recognition reporting is configured in LogiSense Billing.
...
What else do we have to do / do we have to do in discussion with our customer prior to configuration
Outline/detail the data we need from them during this stage of the process
Configuration Process
Back-end Configuration
We need to detail the configuration process we perform here step by step in chronological order. may need to rename this to something like “Initial configuration steps” or something else that describes the customer specific work we are doing based on cx discussions/data gathering
Need to determine how much we describe this portion of the configuration (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.
...
LogiSense Billing Configuration
Once we have the back-end step described in the proper order we can jump over to the LSB UI and cover how to setup the elements there (custom fields, custom reports, etc.)
The LSB configuration is something the customer/prospect will want to see (we need a few screenshots).
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?>>
...
Available Rules:
Evenly Distributed:
At Invoice Creation: revenue is recognized/calculated when the invoice is created?
At Charge Period Start:
At Charge Period End:
At Charge Date:
Milestone Event:
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.
...
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)
Auditing
Detail here what can be done using the audit log (screenshot would be nice)