...
Locate a backup of your pre-bill run database. For example, today's date is February 14th, you ran the February billing on February 2nd, locate the backup made then so that you can run the February bill run again on the new release
Restore the database
Sanitize database with UPDATE queries provided by LogiSense. This is available on request and scrubs the test database of sensitive information, server provisioning info, mail server info, customer email addresses and contact information etc.
If step three wasn't completed, be sure your DEV / TEST system is locked down via firewall so that credit cards can't be charged, emails won't go out from the system and services and switches cannot be provisioned to via the Job service or Event manager service should they be turned on for test purposes
Configure the bill run to match the production server configuration
Execute the bill run
Stop the EngageIP Billing service (this prevents the system from billing again before you have a chance to review the results)
Test or execute any provisioning required (provisioning may not solely be triggered by billing)
...