|
|
| Line 1: |
Line 1: |
| − | == Introduction == | + | =This Content Has Moved House= |
| | | | |
| − | In some scenarios, you may have the need to manually control the end date of the first package subscription period when ordering a new service. There are a few different flags that control how the Emersion system creates different period types, and this one in particular will enable you to control the end date of the very first package subscription period. In effect this will also control how the system will create the future periods. (ie. setting a custom end date, will also set the next period start date)
| + | This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. |
| | | | |
| − | Note: Requires a subscription to the feature Set first period end date. If you would like to enquire regarding this feature, please raise a sales ticket in the [[http://support.emersion.com.au | Emerson Support Portal]].
| + | We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home. |
| | | | |
| − | [[File:First period end date 001.png]] | + | [https://resources.emersion.com/display/EKB/First+Subscription+Period+End+Date Take me to the Emersion Knowledge Base article] |
| − | <br />
| |
| | | | |
| − | == Configuring a package plan to support first period end date ==
| + | [[file:new_home_sm.jpg|900px]] |
| − | | |
| − | This setting can be enabled when you create a new package plan via <pre>Packages and Plans > Management > Package Plans (tab) > Create New [button]</pre>
| |
| − | | |
| − | The only thing that needs configuring is the [[PackagePlans/PackagePlans#Honour_First_Period_End_Date_if_Set|Honour First Period End Date if Set]] checkbox.
| |
| − | | |
| − | Simply check for Yes, or leave unchecked for No. This is an important checkbox to ensure is checked if you are actually planning on manually setting the first period end date when you manually activate a service
| |
| − | | |
| − | * Honour First Period End Date if Set
| |
| − | | |
| − | This setting permits a user (who is granted the relevant power) to set the end date of the first package subscription period when the package is activated during the Semi manual provisioning phase. This is designed for service providers who wish to control both the start date of the service (service activation date) and control when the first period will lapse separately. It requires a subscription to the feature Set first period end date. If you would like to enquire regarding this feature, please raise a sales ticket in the Emerson Support Portal.
| |
| − | | |
| − | [[File:First period end date 000.png]]
| |
| − | <br />
| |
| − | | |
| − | == Setting the first period end date when manually activating a service ==
| |
| − | | |
| − | The next step of the process is during [[Semi Manual Provisioning|manual service activation]] where you will need to supply a ''Service Start Date'' & a ''First Period End Date''.
| |
| − | <pre>Services > Manual Provisioning > Manage Provisioning > Activate [button]</pre>
| |
| − | | |
| − | [[File:First period end date 007.png]]
| |
| − | | |
| − | == Example Use Case ==
| |
| − | | |
| − | In this example, we have a mid month billing cycle. We want to be able to align our package & service subscription periods to an actual month (ie. 1st - 1st), and we want to be able to set a service start date anywhere within the month.
| |
| − | | |
| − | Assumptions:
| |
| − | * Service Provider is subscribed to the appropriate feature to enable access to setting the flag on package plans
| |
| − | * End User account invoice period is 12th - 12th of the month.
| |
| − | * End User account billing cycle is MONTHLY
| |
| − | * Pro rata access fees is enabled on the package plan
| |
| − | * Carrier usage is billed on a standard month basis (ie. 1st - 1st) and we wish to align the end user usage to this.
| |
| − | | |
| − | [[File:First period end date 004.png]]
| |
| − | | |
| − | * We need to ensure we have the ''Can set first period end date'' [[Admin/PermissionManagement|Power]] enabled on an appropriate Role.
| |
| − | | |
| − | [[File:First period end date 003.png]]
| |
| − | | |
| − | * Now we ensure the ''Honour First Period End Date if Set'' flag is enabled on the package plan we wish to subscribe to
| |
| − | We also want to ensure ''Align Pkg Period to invoice Period'' is NOT enabled (for the purpose of this example)
| |
| − | | |
| − | [[File:First period end date 002.png]]
| |
| − | | |
| − | * Go ahead a Order a new service (''beyond the scope of this quick example'') and then go to:
| |
| − | <pre>Service Manual Provisioning > Manage Provisioning > Activate [button]</pre>
| |
| − | | |
| − | * At this point, we would want to set the actual service start date (as activated at the carrier. Let's use the image as an example --> 15/6/2016) and the First Period End Date being the 1st of the following month (1/7/2016).
| |
| − | | |
| − | [[File:First period end date 007.png|centre]] | |
| − | | |
| − | * This will create a Package period from the 15/6/2016 - 1/7/2016. When it is time for the system to generate the next monthly period, we will see 1/7/2016 - 1/8/2016 (and so on).
| |
| − | Additionally, the system will generate a correct pro-rated access fee in advance from the 15/206/16 -> 1/7/2016, with an additional full month fee generated from the 1st-1st once the month ticks over (and then monthly going forward). Both of these access fees would end up on the invoice generated on 14th of July 2016. Usage charges in arrears will reflect the service subscription periods; Being 15/6/2016 - 1/7/2016 for the first month and then 1/7/2016 - 1/8/2016 for the second month. Again, the 15/6 - 1/7 usage would appear on the invoice generated on 14/7/2016.
| |
| − | | |
| − | [[File:First period end date 006.png|centre]]
| |
| − | | |
| − | * Now going forward, although the customer will have his start/end of month charges generated on the 12th of the month (with an invoice generated 2 days later on the 14th), each day's worth of usage will be received from the carrier and ''bucketed'' into the correct usage period. This will also enable you to reconcile usage between Emersion and your Carrier much easier.
| |
This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
