PackagePlans/PackagePlans - Revision history

Dcowan at 01:26, 21 February 2020

2020-02-21T01:26:08Z

Rlusher at 00:58, 20 February 2020

2020-02-20T00:58:09Z

Rlusher at 00:57, 20 February 2020

2020-02-20T00:57:35Z

Dcowan: clarified advance/arrears access fees

2019-10-30T23:43:31Z

clarified advance/arrears access fees

Dcowan at 06:57, 25 September 2019

2019-09-25T06:57:32Z

Dcowan: clarified Bill Months in Advance

2019-05-15T06:50:27Z

clarified Bill Months in Advance

Scarpenter at 04:44, 6 March 2019

2019-03-06T04:44:02Z

Scarpenter: /* Package Plan Fee Setup */

2018-05-17T23:58:15Z

‎Package Plan Fee Setup

Dcowan: corrected anchor

2018-04-11T02:45:05Z

corrected anchor

Dcowan: added saleable in signup portal

2017-06-22T01:00:29Z

added saleable in signup portal

@@ Line 89: / Line 89: @@
 ; <span id="AccessFeeProRata">Pro Rata</span> : Determines whether or not the first set of Access Fees generated for this plan will be pro-rated.  The 'Pro Rata' setting will also determine whether Period adjustment credits will be produced in the event that the period is adjusted for any reason.  Period adjustment will generally be due to a package cancellation effective as of mid period. This setting is ignored for periods that have been billed in advance; they will be credited back regardless.
-; <span id="AlignPkgPeriodtoInvoicePeriod">Align Pkg Period to Invoice Period</span> : This flag will align any newly created package subscriptions to this package plan to the underlying account invoice period of the given customer. This will ensure all access fees and usage fees are aligned to when an invoice is rendered. It is important to note that overriding this setting at this point may conflict with the account level setting [[Account/AccountCreation#Wizard_Screen_1:_Data_Definition | Align Pkgs to Account]], producing undesirable billing results. You must be certain you wish to over ride this setting when creating a new package plan. This setting may also impact the ability of the
+; <span id="AlignPkgPeriodtoInvoicePeriod">Align Pkg Period to Invoice Period</span> : This flag will align any newly created package subscriptions to this package plan to the underlying account invoice period of the given customer. This will ensure all access fees and usage fees are aligned to when an invoice is rendered. It is important to note that overriding this setting at this point may conflict with the account level setting [[Account/AccountCreation#Wizard_Screen_1:_Data_Definition | Align Pkgs to Account]], producing undesirable billing results. You must be certain you wish to over ride this setting when creating a new package plan.
 For example, a package bundle comprising month-to-month billing for an ADSL service and web hosting. These services will align to the underlying account invoice period nicely, as they are billed monthly. However if the package plan also contains a Domain Registration service (for 1 year, 2 years, or 3 years), it is not desirable for this to be aligned to the customer's account invoice period.

← Older revision		Revision as of 00:58, 20 February 2020
Line 93:		Line 93:


−	; <span id="DisableMigrateDuringPeriod"> Disable Migrations during Period </span> This flag will stop users carrying out migrations on package subscriptions associated with the package plan, within a package subscription period. Users will only be permitted to migrate at the end of the period. This setting is useful for service providers who do not want pro rata charges generated as a result of a migration.	+	; <span id="DisableMigrateDuringPeriod">Disable Migrations during Period </span> : This flag will stop users carrying out migrations on package subscriptions associated with the package plan, within a package subscription period. Users will only be permitted to migrate at the end of the period. This setting is useful for service providers who do not want pro rata charges generated as a result of a migration.

@@ Line 91: / Line 91: @@
 ; <span id="AlignPkgPeriodtoInvoicePeriod">Align Pkg Period to Invoice Period</span> : This flag will align any newly created package subscriptions to this package plan to the underlying account invoice period of the given customer. This will ensure all access fees and usage fees are aligned to when an invoice is rendered. It is important to note that overriding this setting at this point may conflict with the account level setting [[Account/AccountCreation#Wizard_Screen_1:_Data_Definition | Align Pkgs to Account]], producing undesirable billing results. You must be certain you wish to over ride this setting when creating a new package plan. This setting may also impact the ability of the
 For example, a package bundle comprising month-to-month billing for an ADSL service and web hosting. These services will align to the underlying account invoice period nicely, as they are billed monthly. However if the package plan also contains a Domain Registration service (for 1 year, 2 years, or 3 years), it is not desirable for this to be aligned to the customer's account invoice period.
 ; Created date : The date the service plan was initially created.

@@ Line 1: / Line 1: @@
 = Overview =
 A package plan is one of several billing objects used in Emersion.
@@ Line 68: / Line 66: @@
 ; <span id="Honour_First_Period_End_Date_if_Set">Honour First Period End Date if Set</span> : 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 | 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 [https://resources.emersion.com/display/EKB/Getting+Support+and+Help+from+Emersion Emerson Support Portal].
-; <span id="BillAccessFeesIn">Bill Access Fees in</span> : Specifies if you are billing access fees in arrears or in advance.
+; <span id="BillAccessFeesIn">Bill Access Fees in</span> : Specifies if you are billing access fees in arrears or in advance. This applies to package plan access fees, service plan access fees, service feature product charges & bolt on access fees. If '''advance''' is used, access fees will generate automatically at the start of the associated subscription period. If '''arrears''' is used, access fees will generate and the end of the associated subscription period (and only once the period is approved - either automatically or [https://resources.emersion.com/display/EKB/Period+Approval manually])
 ; Bill Months in Advance: Specifies how many months prior to the start of the next period you generate a cardline. The total periods billed is determine by the '''Periods in Advance''' setting.

@@ Line 113: / Line 113: @@
 * Grandfathered - the plan is no longer used. There maybe customers with active subscriptions on this plan, but it cannot be sold.
-; Saleable in Signup Portal : Enable to allow this package plan to be visible in the [[End User Portal and Customer Sign Up Portal|End User Signup Portal]].
+; Saleable in Signup Portal : Enable to allow this package plan to be visible in the [https://resources.emersion.com/display/EKB/The+Sign+Up+Portal End User Signup Portal].
 = See Also =
 * [[PackagePlans/LinkingPackageAndServicePlans|Linking Package Plans and Service Plans]]
 * [[PackagePlan/Advanced | Package Plans - Advanced features and functions]]

@@ Line 70: / Line 70: @@
 ; <span id="BillAccessFeesIn">Bill Access Fees in</span> : Specifies if you are billing access fees in arrears or in advance.
-; Bill in Advance: Specifies how far into the future you are going to create cardlines.
+; Bill Months in Advance: Specifies how many months prior to the start of the next period you generate a cardline. The total periods billed is determine by the '''Periods in Advance''' setting.
-; To clarify the difference between Periods in Advance and Bill in Advance, it can be thought of in the following way.  Periods in Advance refers to how many periods you are going to bill when the cardline is generated.  Bill in Advance is <b>when</b> you are going to bill.  In other words, Periods in Advance refers to the <b> volume </b> of periods you are going to bill, and Bill in Advance refers to how far in advance, or "when", you are going to bill these periods.
+ To clarify the difference between Periods in Advance and Bill Months in Advance, it can be thought of in the following way
 For example, imagine you have:
@@ Line 86: / Line 89: @@
 In addition, because you are billing 2 periods in advance, both periods 3 months in length each, the cardlines generated will cover the next *six* months in advance.
-; <span id="AccessFeeProRata">Pro Rata</span> : Determines whether or not the first set of Access Fees generated for this plan will be pro-rated.  The 'Pro Rata' setting will also determine whether Period adjustment credits will be produced in the event that the period is adjusted for any reason.  Period adjustment will generally be due to a package cancellation effective as of mid period.
+; <span id="AccessFeeProRata">Pro Rata</span> : Determines whether or not the first set of Access Fees generated for this plan will be pro-rated.  The 'Pro Rata' setting will also determine whether Period adjustment credits will be produced in the event that the period is adjusted for any reason.  Period adjustment will generally be due to a package cancellation effective as of mid period. This setting is ignored for periods that have been billed in advance; they will be credited back regardless.
 ; <span id="AlignPkgPeriodtoInvoicePeriod">Align Pkg Period to Invoice Period</span> : This flag will align any newly created package subscriptions to this package plan to the underlying account invoice period of the given customer. This will ensure all access fees and usage fees are aligned to when an invoice is rendered. It is important to note that overriding this setting at this point may conflict with the account level setting [[Account/AccountCreation#Wizard_Screen_1:_Data_Definition | Align Pkgs to Account]], producing undesirable billing results. You must be certain you wish to over ride this setting when creating a new package plan. This setting may also impact the ability of the

@@ Line 6: / Line 6: @@
 This article covers how to create a package plan.
-If you would like to understand what the package plan is and how it works with other Emersion billing objects, see our [[Billing_Objects|Introduction to Emersion's Billing Objects article]].
+If you would like to understand what the package plan is and how it works with other Emersion billing objects, see our [https://resources.emersion.com/display/EKB/The+Emersion+Billing+Objects Introduction to Emersion's Billing Objects article].
 == Prerequisites ==
 You can create a package plan on its own as an independent object. But it cannot be subscribed to by a customer until the following prerequisites are met:
-* The service plan(s) are linked to the pacakge plan.
+* The service plan(s) are linked to the package plan.
 * The service Plan(s) are in a ''saleable'' state.
 * The plan has a product rate card linked that is in a saleable state
@@ Line 66: / Line 66: @@
 ; Enable package subscription access fee overrides : Checking this flag enables subscribers to the plan to be given a different package plan access fee than the default access fee. This fee override is applied at the package subscription for the customer. A default package plan access fee must be set for any override to be applied. This flag cannot override service plan fees.
-; <span id="Honour_First_Period_End_Date_if_Set">Honour First Period End Date if Set</span> : 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 | 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 [http://support.emersion.com.au Emerson Support Portal].
+; <span id="Honour_First_Period_End_Date_if_Set">Honour First Period End Date if Set</span> : 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 | 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 [https://resources.emersion.com/display/EKB/Getting+Support+and+Help+from+Emersion Emerson Support Portal].
 ; <span id="BillAccessFeesIn">Bill Access Fees in</span> : Specifies if you are billing access fees in arrears or in advance.

← Older revision		Revision as of 23:58, 17 May 2018
Line 63:		Line 63:

	; Periods in Advance : determines how many PERIODS in advance the system should generate Access Fees. By default, it's set to 1. In other words, generate the access fee for a period when that period starts. In a real world example, if you have a Package that bills monthly and the date is 01/03/2011, it will generate access fees for 01/03/2011 to 31/03/2011 on 01/03/2011.If you set that value to 2 on a plan whose period length is 1 month, it would generate access fees for the period 01/04/2011 to 30/04/2011 on 01/03/2011. This works irrespective of the period length, so if you have 6 or 12 months periods on a Package with a 'Periods in Advance' setting of anything higher than 1, your customers will receive Package Access Fees well in advance of the current Period.		; Periods in Advance : determines how many PERIODS in advance the system should generate Access Fees. By default, it's set to 1. In other words, generate the access fee for a period when that period starts. In a real world example, if you have a Package that bills monthly and the date is 01/03/2011, it will generate access fees for 01/03/2011 to 31/03/2011 on 01/03/2011.If you set that value to 2 on a plan whose period length is 1 month, it would generate access fees for the period 01/04/2011 to 30/04/2011 on 01/03/2011. This works irrespective of the period length, so if you have 6 or 12 months periods on a Package with a 'Periods in Advance' setting of anything higher than 1, your customers will receive Package Access Fees well in advance of the current Period.
		+
		+	; Enable package subscription access fee overrides : Checking this flag enables subscribers to the plan to be given a different package plan access fee than the default access fee. This fee override is applied at the package subscription for the customer. A default package plan access fee must be set for any override to be applied. This flag cannot override service plan fees.

	; <span id="Honour_First_Period_End_Date_if_Set">Honour First Period End Date if Set</span> : 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 \| 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 [http://support.emersion.com.au Emerson Support Portal].		; <span id="Honour_First_Period_End_Date_if_Set">Honour First Period End Date if Set</span> : 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 \| 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 [http://support.emersion.com.au Emerson Support Portal].