Emersion - User contributions [en]

Data Import/End User Accounts

2020-09-11T00:49:41Z

Rlusher: /* This content has moved house */

{{DISPLAYTITLE:Importing End User Accounts}}
= This content has moved house =
This article has been moved to the Emersion Knowledge Base.

[https://resources.emersion.com/x/LoCYAw Take me there...]

PackagePlans/PackagePlans

2020-02-20T00:58:09Z

Rlusher:

= Overview =
A package plan is one of several billing objects used in Emersion.

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 [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 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
* Rate cards have at least 1 rate and are in a saleable state (for telephony plans only)
* The Data Billing tab has been configured (for data plans)
* Package Plans and service plans (both BUY and SELL) are all linked together.

This article's scope is limited to creating the package plan. Other articles cover the other steps above. See the links at the bottom of this page for assistance in these tasks.

= Package Plan Searching =
Package Plans are created and maintained in Cumulus via the following path

Nav: '''Packages and Plans > Management > Package Plans'''

When the page loads, the following screen will appear listing all package plans that have been created.

[[File:Package-plan-list.png|1200px|The Package Plan List Screen]]

= Create a Package plan =
To create a new Package Plan, click the '''Create New''' button. The following page will be displayed.

[[File:Package-plan-create-new.png|1200px|The ''Create a New Package Plan'']]

There are 3 columns of settings. Complete all fields as required.

; Name : The internal name for the Package. This name is only visible in Cumulus.

; External Name : This is the External Name for the Package. This is what is printed on customer's invoices if ledger cardlines (eg Package Plan Access Fees), related to this Package, are created.

; Description : An optional description for the Package. Internal use only

; Reference Name : A way of providing a link to an External 3rd party. This could be represented as the name of a prior billing system if one existed. The field is entirely optional.

; Reference Key : A way of providing a link to an External 3rd party. This may be the name of this plan, as it existed in the old system if this were the case. This field is entirely optional.

; Buy or Sell : Indicates whether this is a Buy Plan or a Sell Plan. Please see the [[#Buy_and_Sell_Plans | Buy and Sell Plans]] section above for further information.

; Default Contract Type : Defines the default Contract that will be created when this Package is sold to downstream Customers. For a Contract to appear here, this Package must be part of a Contract Pool. Due to this, when initially creating a Package Plan, only the default Option, 'None' will be available. For more information on contract types & their configuration, please click [[PackagePlans/Contract|here]].

; Customer Contract Required : Indicates whether a mandatory physical customer contract document must be uploaded during the Order Confirmation & Finalise page. If this is enabled, you MUST upload a physical customer contract. If disabled, it is not mandatory to upload a physical customer contract. Not to be confused with 'Default Contract Type' above which refers to the contract instance that is created when an order is completed.

== Package Plan Fee Setup ==

; Setup Fee : The fee charged when a Subscription of this Package is created.
; Access Fee : A Rental or Service fee generated each period for the life of the Package Subscription.

Please be aware of both the '''Override''' tick boxes and also the note: ''Where a package access fee is not empty, it will override any service plan access fees that are defined''. It's possible to define a Setup Fee and an Access Fee at both the Package Plan and Service Plan level. If either the Access Fee or Setup Fee (or both) are empty, with the Override button unchecked, the system will create the Access Fees based on the attached Service Plans.

If the override button is ticked but no value is entered, please note that $0 will be saved (so effectively, you are creating a $0 plan).

; Period Length : The Period length defines how far in advance (or arrears) the system will generate access fees. It also defines how frequently the access fees are created.

; 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.

; 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 | 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].

; Bill Access Fees in : 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.

To clarify the difference between Periods in Advance and Bill Months 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 Months in Advance is when you are going to bill.
In other words, Periods in Advance refers to the volume of periods you are going to bill, and Bill Months in Advance refers to how far in advance, or "when", you are going to bill these periods.

For example, imagine you have:

<li> A monthly account invoice period </li>
<li> Periods Length is 3 months. </li>
<li> Periods in Advance is set to 2.</li>
<li> Bill Access Fees is set to: Advance </li>
<li> Bill in Advance is: 2 months. </li>

In this example, today is the 1st of April, and the subscription is to start on the 1st of May.
In this case what will happen is that because you are billing access fees 2 months in advance, the cardline will be generated today, on the 1st of April, not on the 1st of May.
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.

; Pro Rata : 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.

; Align Pkg Period to Invoice Period : 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.

; Disable Migrations during Period : 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.

; Created date : The date the service plan was initially created.

; Created by : Displays the user who created the plan.

; Date modified : Displays the date when the last modification was made to the service plan.

; Modified by : Displays the name of the user who last updated the service plan's.

; Saleable from : The date from which the plan is or was available to order.

; Saleable to : After this date passes, a plan is unavailable to the orders screens.

; Approval status : Status of the plan.
* Draft - Initial state for when the plan is being set up.
* Pending - The plan has been set up but needs review and is not ready for sale.
* Approved - The plan has been approved and is ready for sale.
* Saleable - the plan is able to be sold
* 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 [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]]

PackagePlans/PackagePlans

2020-02-20T00:57:35Z

Rlusher:

= Overview =
A package plan is one of several billing objects used in Emersion.

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 [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 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
* Rate cards have at least 1 rate and are in a saleable state (for telephony plans only)
* The Data Billing tab has been configured (for data plans)
* Package Plans and service plans (both BUY and SELL) are all linked together.

This article's scope is limited to creating the package plan. Other articles cover the other steps above. See the links at the bottom of this page for assistance in these tasks.

= Package Plan Searching =
Package Plans are created and maintained in Cumulus via the following path

Nav: '''Packages and Plans > Management > Package Plans'''

When the page loads, the following screen will appear listing all package plans that have been created.

[[File:Package-plan-list.png|1200px|The Package Plan List Screen]]

= Create a Package plan =
To create a new Package Plan, click the '''Create New''' button. The following page will be displayed.

[[File:Package-plan-create-new.png|1200px|The ''Create a New Package Plan'']]

There are 3 columns of settings. Complete all fields as required.

; Name : The internal name for the Package. This name is only visible in Cumulus.

; External Name : This is the External Name for the Package. This is what is printed on customer's invoices if ledger cardlines (eg Package Plan Access Fees), related to this Package, are created.

; Description : An optional description for the Package. Internal use only

; Reference Name : A way of providing a link to an External 3rd party. This could be represented as the name of a prior billing system if one existed. The field is entirely optional.

; Reference Key : A way of providing a link to an External 3rd party. This may be the name of this plan, as it existed in the old system if this were the case. This field is entirely optional.

; Buy or Sell : Indicates whether this is a Buy Plan or a Sell Plan. Please see the [[#Buy_and_Sell_Plans | Buy and Sell Plans]] section above for further information.

; Default Contract Type : Defines the default Contract that will be created when this Package is sold to downstream Customers. For a Contract to appear here, this Package must be part of a Contract Pool. Due to this, when initially creating a Package Plan, only the default Option, 'None' will be available. For more information on contract types & their configuration, please click [[PackagePlans/Contract|here]].

; Customer Contract Required : Indicates whether a mandatory physical customer contract document must be uploaded during the Order Confirmation & Finalise page. If this is enabled, you MUST upload a physical customer contract. If disabled, it is not mandatory to upload a physical customer contract. Not to be confused with 'Default Contract Type' above which refers to the contract instance that is created when an order is completed.

== Package Plan Fee Setup ==

; Setup Fee : The fee charged when a Subscription of this Package is created.
; Access Fee : A Rental or Service fee generated each period for the life of the Package Subscription.

Please be aware of both the '''Override''' tick boxes and also the note: ''Where a package access fee is not empty, it will override any service plan access fees that are defined''. It's possible to define a Setup Fee and an Access Fee at both the Package Plan and Service Plan level. If either the Access Fee or Setup Fee (or both) are empty, with the Override button unchecked, the system will create the Access Fees based on the attached Service Plans.

If the override button is ticked but no value is entered, please note that $0 will be saved (so effectively, you are creating a $0 plan).

; Period Length : The Period length defines how far in advance (or arrears) the system will generate access fees. It also defines how frequently the access fees are created.

; 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.

; 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 | 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].

; Bill Access Fees in : 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.

To clarify the difference between Periods in Advance and Bill Months 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 Months in Advance is when you are going to bill.
In other words, Periods in Advance refers to the volume of periods you are going to bill, and Bill Months in Advance refers to how far in advance, or "when", you are going to bill these periods.

For example, imagine you have:

<li> A monthly account invoice period </li>
<li> Periods Length is 3 months. </li>
<li> Periods in Advance is set to 2.</li>
<li> Bill Access Fees is set to: Advance </li>
<li> Bill in Advance is: 2 months. </li>

In this example, today is the 1st of April, and the subscription is to start on the 1st of May.
In this case what will happen is that because you are billing access fees 2 months in advance, the cardline will be generated today, on the 1st of April, not on the 1st of May.
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.

; Pro Rata : 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.

; Align Pkg Period to Invoice Period : 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.

; Disable Migrations during Period 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.

; Created date : The date the service plan was initially created.

; Created by : Displays the user who created the plan.

; Date modified : Displays the date when the last modification was made to the service plan.

; Modified by : Displays the name of the user who last updated the service plan's.

; Saleable from : The date from which the plan is or was available to order.

; Saleable to : After this date passes, a plan is unavailable to the orders screens.

; Approval status : Status of the plan.
* Draft - Initial state for when the plan is being set up.
* Pending - The plan has been set up but needs review and is not ready for sale.
* Approved - The plan has been approved and is ready for sale.
* Saleable - the plan is able to be sold
* 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 [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]]

Main Page/Provisioning/PSTN Preselect Provisioning Workflow

2019-01-01T23:39:11Z

Rlusher:

{{DISPLAYTITLE:Provisioning for Workflows PSTN/Preselect}}
== Introduction ==
* When the order is initially submitted, you will see a log entry saying “Pending Activity Collection”. Nothing has happened yet. This just means the service is queued up to be placed into an “activity file”.
* Every morning at around 8:00 am, the details of this service and order are placed into a file and submitted to the carrier. This log entry will say “FSR Request sent in file sequence XX”.
* Depending on your service provider agreement, SLA times and a variety of other factors, you won’t see any log entries for a successful churn until an item that says “Churn advice in file sequence” appears, usually after 5 to 10 working days. This means, generally the carrier has said ok to the churn.
* Shortly after you will see another log that states “Service activation Complete”.

 
It is important not to touch manual provisioning during any of these stages, or abort the subscription. While it may activate the service, it will interfere with the normal workflows.
 
 

* If the workflow is stuck on “Pending Activity File Collection” you should contact Emersion.
* If the last log is “FSR request file sent in file sequence XX” (I’d suggest waiting 5 to 10 working days), this means generally the carrier has not sent us a response in their “batch” files (AAPT for instance refers to these as Daily Event Files). You should follow up with your carrier.
* If the carrier claims they have submitted a response in a batch file, then contact Emersion with the Batch file name for investigation.

[[File:Provisioning Log PSTN.jpg]]

API/Services/PurchaseProduct

2018-11-22T00:19:06Z

Rlusher:

===Purchase Product===

'''Purpose'''
This method is used to create a product purchase on behalf of an existing client. This call supports creating pending cardline items for charging to next invoice.
For Products of type Credit, please enter a negative quantity.

'''Inputs'''
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:emersion:api" xmlns:urn1="urn:emersion:types">
<soapenv:Header/>
<soapenv:Body>
<urn:PurchaseProducts>
<urn:AccountID>?</urn:AccountID>
<urn:ShoppingCart>

<urn1:PurchaseItem>
<urn1:ProductID>?</urn1:ProductID>
<urn1:Quantity>?</urn1:Quantity>

<urn1:ExTaxPrice>?</urn1:ExTaxPrice>

<urn1:Tax>?</urn1:Tax>

<urn1:Note_Details>?</urn1:Note_Details>

<urn1:Note_Customer_Visible>?</urn1:Note_Customer_Visible>
</urn1:PurchaseItem>
</urn:ShoppingCart>

<urn:DeliveryAddress>

<urn1:PrimaryAddressID>?</urn1:PrimaryAddressID>

<urn1:Address ID="?">

<urn1:IsPrimary>?</urn1:IsPrimary>
<urn1:Details/>

<urn1:NearestCrossStreet>?</urn1:NearestCrossStreet>
<urn1:Country>?</urn1:Country>

<urn1:FormattedAddress>?</urn1:FormattedAddress>

<urn1:IsValidated>?</urn1:IsValidated>

<urn1:Type>?</urn1:Type>

<urn1:DateFrom>?</urn1:DateFrom>

<urn1:DateTo>?</urn1:DateTo>

<urn1:GnafPid ID="?">?</urn1:GnafPid>

<urn1:DPID>?</urn1:DPID>

<urn1:Barcode>?</urn1:Barcode>

<urn1:ExternalReferences>

<urn1:ExternalReference Type="?">?</urn1:ExternalReference>
</urn1:ExternalReferences>

<urn1:UploadSource>?</urn1:UploadSource>

<urn1:UploadSourceRef>?</urn1:UploadSourceRef>

<urn1:ImportIdentifier>?</urn1:ImportIdentifier>

<urn1:LastUpdated>?</urn1:LastUpdated>
</urn1:Address>
</urn:DeliveryAddress>
</urn:PurchaseProducts>
</soapenv:Body>
</soapenv:Envelope>

'''Important notes'''
- ProductID needs to be the ID of the Product in the Emersion system
- Quantity has to be non-zero and an integer
- ExTaxPrice and Tax are floating point numbers however tax is optional – a sale can be tax free.

'''Example Validation Error'''
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Validation Error</faultstring>
<faultactor>http://emersion.com.au/Services</faultactor>
<detail>Invalid or Missing Account ID</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>

'''Output'''

<SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://emersion.com.au/ServiceObjects">
<SOAP-ENV:Body>
<ns1:PurchaseProductResponse>
<ns1:AccountID>399301</ns1:AccountID>
<ns1:InvoiceID/>
<ns1:Cardlines/>
</ns1:PurchaseProductResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

'''Error Strings'''

* Invalid or Missing Account ID

* Could not find Account ID!

* You do not have permission to modify this Account

* No items have been provided to purchase in transaction.

* Cart item missing mandatory ProductID

* Cart item missing mandatory quantity

* Product purchase failed with an exception: '.$e->getMessage());

The following errors can only occur if a Delivery Address is provided.

* Provided Primary Address ID does not exist in system

* Primary Address ID should be Integer

* Missing Primary Address Post Code from Delivery Address

* Post Code should consist of 4 digits

* Post Code should contain digits only

* Missing Primary Address Suburb from Delivery Address

* Missing Primary Address Street Name from Delivery Address

* Missing Primary Address Street Name from Delivery Address

* Missing Primary Address Street Type ID from Delivery Address

* Invalid Value for Street Type ID (means that Street Type ID does not exist in the system)

* Street Type ID should be Integer

* Missing Primary Address Lot Number from Delivery Address

* Missing Primary Address Unit Number from Delivery Address

* Missing Primary Address State from Delivery Address

* Invalid Value for State (means that State ID does not exist in the system)

* State should be Integer

* Missing Primary Address Level from Delivery Address

* Missing Primary Address Level Type ID from Delivery Address

* Invalid Value for Level Type ID (means that Level Type ID does not exist in the system)

* Level Type ID should be Integer

* Missing Primary Address Unit Type ID from Delivery Address

* Invalid Value for Unit Type ID (means that Unit Type ID does not exist in the system)

* Unit Type ID should be Integer

* Missing Primary Address P.O. Box Number from Delivery Address

* Missing Primary Address Site Name from Delivery Address

* Missing Primary Address Street Type Suffix ID from Delivery Address

* Invalid Value for Street Type Suffix ID (means that Street Type Suffix ID does not exist in the system)

* Street Type Suffix ID should be Integer

New Tariffs

2017-12-19T01:21:12Z

Rlusher:

This page has now been moved to [Confluence https://confluence.emersion.com.au/display/EKB/New+Tariffs]

= New Tariffs =

As part of regular maintenance of the system, Emersion creates any new tariffs that are received from service suppliers in their data feed. When a usage record is received from the carrier, and the tariff is one Emersion has not processed before, the usage will be [[Quarantine | quarantined]] with the reason '''Non Existent Tariff Key Fault'''.
Once Emersion create the tariff in the system, users can set a price against the new tariff in the relevant [[ServicePlans/RateCard | Rate Card]]. After that, the usage can be rated. To rate the usage so it is properly billed to the customer, cleanse these records from Quarantine. Usage in Quarantine will not automatically be rated when Emersion creates the new tariff.

If you do not set a price against the tariff, and a price cannot be found, the usage will fall back into quarantine with the reason '''Missing Rate'''.

 WARNING 

Please be aware that if the date of the call record would mean that it would ordinary fall into an older billing period, unless that period is Open it will fall into the current open period. This may inflate usage for a current period and push people over data and usage allowances, if they are setup on your package/service plan.

This page lists batches of tariffs added by Emersion in a bi-monthly cycle.

== (14/11/2017) Tariffs ==

[[File:Non existent tariff keys 2017-11-14.zip|New Tariffs 2017-11-14]]

== (27/10/2017) Tariffs ==

[[File:New Tariffs 2017 10 27.zip]]

== (13/10/2017) Tariffs ==

[[File:NEW TARIFFS 13 10 2017.zip|New Tariffs 13-10-2017]]

== (28/09/2017) Tariffs ==

[[File:Non Existent Tariff Keys 28-09-2017.zip|thumbnail]]

== (19/09/2017) Tariffs ==

[[File:New Tariffs 2017-09-19.zip|thumbnail|New Tariffs 2017-09-19]]

== (31/08/2017) Tariffs ==

[[File:Tarifflisting 2017 08 31.zip|Tariff Listing 2017_08_31]]

== (17/08/2017) Tariffs ==

[[File:New Tariffs 2017 07 17.zip|New_Tariffs_2017_07_17.zip]]

== (29/06/2017) Tariffs ==
[[File:New Tariffs 2017-29-06.zip|New_Tariffs_2017-29-06.zip]]

== (14/06/2017) Tariffs ==
[[File:Tariff listing 2017 06 14.zip|Tariff_listing_2017_06_14.zip]]

== (30/05/2017) Tariffs ==
[[File:New Tariffs 30-05-2017.zip]]

== (15/05/2017) Tariffs ==

[[File:New Tariffs May 15 2017.zip|thumbnail|New Tariffs May 15 2017]]

== (19/04/2017) Tariffs ==

[[File:New Tariffs Added 2017-19-04.zip|New_Tariffs_Added_2017-19-04]]

== (28/03/2017) Tariffs ==

[[File:TARIFFS28032017.zip|Tariff Export Listing 28 03 2017]]

== (23/02/2017) Tariffs ==

[[File:Tariff Export Listing 23 02 2017.zip|Tariff_Export_Listing_23_02_2017]]

== (01/19/2017) Tariffs ==

[[File:Tariff 01-19-2017.zip|thumbnail|Tariff Listing 01 - 19 -2017]]

== (30/12/2016) Tariffs ==

[[File:Tariff key export 2016 30 12.zip|thumbnail|Tariff_key_export_2016_30_12.zip]]

== (15/12/2016) Tariffs ==

[[File:New tariff key listing 15 12 2016.zip]]

== (15/11/2016) Tariffs ==

[[File:New_tariff_listing_2016_11_15.zip|thumbnail|New Tariff Listing 15-11-2016]]

== (31/10/2016) Tariffs ==

[[File:New tariff listing 2016 10 31.csv|thumbnail|New Tariff Listing 31-10-2016]]

== (14/10/2016) Tariffs ==

[[File:New tariff listing 2016 10 14.csv|thumbnail|New Tariff Listing 14- 10 - 2016]]

== (12/09/2016) ==

[[File:Tariff listing 2016 09 12.csv|thumbnail|New Tariff Listing 12-09-2016]]

== (01/09/2016) ==

[[File:New Tariff Listing 2016 09 01.csv|thumbnail|New Tariff Listing 01 - 09 - 2016]]

== (18/08/2016) ==

[[File:Export tariff addition 18 08 2016.csv|thumbnail|New Tariffs 18_08_2016]]

== (29/07/2016) ==

[[File:New Tariffs 29 07 2016.csv|thumbnail|New Tariffs 29_07_2016]]

== (19/07/2016) ==

[[File:New Tariff 2016-07-19.csv|thumbnail|New Tariff Listing 2016-07-19]]

== (30/06/2016) ==

[[File:Tariff Listing 2016 30 06.csv|thumbnail|Tariff Listing 2016_30_06 Most Recent]]

== (14/06/2016) ==

[[File:New tariff 2016-06-14.csv|thumbnail|Tariff Listing 14-06-2016]]

== (30/5/2016) ==

[[File:New Tariff Listing 2016 05 30.csv|thumbnail|Tariff Listing 30-05-2016]]

== 18/05/2016 ==

[[File:Tariff List 2016 05 18.csv|thumbnail|AAPT Tariff List Additions 18-05-2016]]

== 28-04-2016 ==

[[File:AAPT Tariff 28 04-2016.csv|thumbnail|AAPT_Tariff_28_04-2016.csv]]

== 12/04/2016 ==

[[File:New Tariff Listing 2016-04-12.csv|New Tariff Listing - 2016-04-12]]

== 30/03/2016 ==

[[File:Tariff Listing New 30 03 2016.csv|New Tariffs 30th of March 2016]]

= See Also =

[[Quarantine | Quarantine]]

New Tariffs

2017-12-19T01:20:58Z

Rlusher:

This page has now been moved to [https://confluence.emersion.com.au/display/EKB/New+Tariffs]

= New Tariffs =

As part of regular maintenance of the system, Emersion creates any new tariffs that are received from service suppliers in their data feed. When a usage record is received from the carrier, and the tariff is one Emersion has not processed before, the usage will be [[Quarantine | quarantined]] with the reason '''Non Existent Tariff Key Fault'''.
Once Emersion create the tariff in the system, users can set a price against the new tariff in the relevant [[ServicePlans/RateCard | Rate Card]]. After that, the usage can be rated. To rate the usage so it is properly billed to the customer, cleanse these records from Quarantine. Usage in Quarantine will not automatically be rated when Emersion creates the new tariff.

If you do not set a price against the tariff, and a price cannot be found, the usage will fall back into quarantine with the reason '''Missing Rate'''.

 WARNING 

Please be aware that if the date of the call record would mean that it would ordinary fall into an older billing period, unless that period is Open it will fall into the current open period. This may inflate usage for a current period and push people over data and usage allowances, if they are setup on your package/service plan.

This page lists batches of tariffs added by Emersion in a bi-monthly cycle.

== (14/11/2017) Tariffs ==

[[File:Non existent tariff keys 2017-11-14.zip|New Tariffs 2017-11-14]]

== (27/10/2017) Tariffs ==

[[File:New Tariffs 2017 10 27.zip]]

== (13/10/2017) Tariffs ==

[[File:NEW TARIFFS 13 10 2017.zip|New Tariffs 13-10-2017]]

== (28/09/2017) Tariffs ==

[[File:Non Existent Tariff Keys 28-09-2017.zip|thumbnail]]

== (19/09/2017) Tariffs ==

[[File:New Tariffs 2017-09-19.zip|thumbnail|New Tariffs 2017-09-19]]

== (31/08/2017) Tariffs ==

[[File:Tarifflisting 2017 08 31.zip|Tariff Listing 2017_08_31]]

== (17/08/2017) Tariffs ==

[[File:New Tariffs 2017 07 17.zip|New_Tariffs_2017_07_17.zip]]

== (29/06/2017) Tariffs ==
[[File:New Tariffs 2017-29-06.zip|New_Tariffs_2017-29-06.zip]]

== (14/06/2017) Tariffs ==
[[File:Tariff listing 2017 06 14.zip|Tariff_listing_2017_06_14.zip]]

== (30/05/2017) Tariffs ==
[[File:New Tariffs 30-05-2017.zip]]

== (15/05/2017) Tariffs ==

[[File:New Tariffs May 15 2017.zip|thumbnail|New Tariffs May 15 2017]]

== (19/04/2017) Tariffs ==

[[File:New Tariffs Added 2017-19-04.zip|New_Tariffs_Added_2017-19-04]]

== (28/03/2017) Tariffs ==

[[File:TARIFFS28032017.zip|Tariff Export Listing 28 03 2017]]

== (23/02/2017) Tariffs ==

[[File:Tariff Export Listing 23 02 2017.zip|Tariff_Export_Listing_23_02_2017]]

== (01/19/2017) Tariffs ==

[[File:Tariff 01-19-2017.zip|thumbnail|Tariff Listing 01 - 19 -2017]]

== (30/12/2016) Tariffs ==

[[File:Tariff key export 2016 30 12.zip|thumbnail|Tariff_key_export_2016_30_12.zip]]

== (15/12/2016) Tariffs ==

[[File:New tariff key listing 15 12 2016.zip]]

== (15/11/2016) Tariffs ==

[[File:New_tariff_listing_2016_11_15.zip|thumbnail|New Tariff Listing 15-11-2016]]

== (31/10/2016) Tariffs ==

[[File:New tariff listing 2016 10 31.csv|thumbnail|New Tariff Listing 31-10-2016]]

== (14/10/2016) Tariffs ==

[[File:New tariff listing 2016 10 14.csv|thumbnail|New Tariff Listing 14- 10 - 2016]]

== (12/09/2016) ==

[[File:Tariff listing 2016 09 12.csv|thumbnail|New Tariff Listing 12-09-2016]]

== (01/09/2016) ==

[[File:New Tariff Listing 2016 09 01.csv|thumbnail|New Tariff Listing 01 - 09 - 2016]]

== (18/08/2016) ==

[[File:Export tariff addition 18 08 2016.csv|thumbnail|New Tariffs 18_08_2016]]

== (29/07/2016) ==

[[File:New Tariffs 29 07 2016.csv|thumbnail|New Tariffs 29_07_2016]]

== (19/07/2016) ==

[[File:New Tariff 2016-07-19.csv|thumbnail|New Tariff Listing 2016-07-19]]

== (30/06/2016) ==

[[File:Tariff Listing 2016 30 06.csv|thumbnail|Tariff Listing 2016_30_06 Most Recent]]

== (14/06/2016) ==

[[File:New tariff 2016-06-14.csv|thumbnail|Tariff Listing 14-06-2016]]

== (30/5/2016) ==

[[File:New Tariff Listing 2016 05 30.csv|thumbnail|Tariff Listing 30-05-2016]]

== 18/05/2016 ==

[[File:Tariff List 2016 05 18.csv|thumbnail|AAPT Tariff List Additions 18-05-2016]]

== 28-04-2016 ==

[[File:AAPT Tariff 28 04-2016.csv|thumbnail|AAPT_Tariff_28_04-2016.csv]]

== 12/04/2016 ==

[[File:New Tariff Listing 2016-04-12.csv|New Tariff Listing - 2016-04-12]]

== 30/03/2016 ==

[[File:Tariff Listing New 30 03 2016.csv|New Tariffs 30th of March 2016]]

= See Also =

[[Quarantine | Quarantine]]