...
We need to detail the configuration process we perform here step by step in chronological order (that we set up stored procedures and then describe what each stored procedure does, setting up SQL agent jobs, what they do, setting up Windows scheduler jobs and what they do, etc.). This should not be written as numbered steps for the user to follow, this is a description (overview) of the back-end config work we do and why we do it.
For this guide we will specifically cover the step required to get rev rec working and these three reports generated:
Billed Revenue
Deferred Revenue
Unbilled Revenue
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.). We’ll need to explain all the reports, what data they provide and if they adhere to any rev rec standards (i.e. make sure we note if we comply with ASC 606, IFRS or other standards).
The LSB configuration is something the customer/prospect will want to see (we need screenshots). If they have access to an LSB environment (demo system) they may even want to try out the configuration steps, so we should ensure these steps are detailed (i.e. “Go to xxxx / xxxx / xxxx screen and click xxxx button). Unlike the steps above that we perform these steps can be written with the user in mind (go here, click on this, select this, etc.)
Revenue Recognition Reports
Here we should detail the output of the configuration above (assuming this is all in reports/custom reports):
...
The rev rec reports that are available
...
What each report provides (why it’s useful from a rev rec standpoint and if the report meets any rev rec compliance standards)
...
How to generate the report
...
:
Screenshots of each Billed Revenue, Deferred Revenue and Unbilled Revenue report with dummy data