Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
| Table of Contents | ||||
|---|---|---|---|---|
|
Name conventions
| Name | Description |
|---|
...
| Product |
...
| can be of type 'Internet', 'Voip', 'Device', 'Credit', 'TV' |
...
| , 'Other' |
...
| or ' |
...
| Postal' |
...
| Item |
...
| is a Product |
...
| assigned to a Contract |
...
product (e.g. tariff or device)
...
Short introduction
- you can create your list of products (which can be devices or services)
- a product of type internet (colloquially also called tariff, if it's not a device) requires a QoS rule (i.e. a data rate)
- you link your customers to the products via assigning products to contracts
- we then call the product (which is now linked to the contract) an item
Important dependencies
The following designations are important regarding program design (of NMS Prime) and communication between ISP and their customers:
- network access
- QoS / data rates
- tariff / maturity (runtime)
Add a Product
- Martin Zimmerling: short introduction of how to add a product AND NOT a tariff
- Martin Zimmerling: add SEO stuff
By now, please also refer to the module chart.
Runtime / Maturity
You can add a minimum and a general maturity to all so called tariffs (a product of type 'Internet', 'Voip' or 'TV'). A contracts end of term shown on the invoice after executing the settlement run is determined by the assigned item. If you have multiple items with different types (and valid dates !) assigned to the customer the following order takes precedence:
- Internet
- Voip
- TV
So if there's a customer only having a Voip tariff (no internet) the maturity of the corresonding Voip product is used to determine the contracts end of term.
It's important to say that if the Internet item is bundled with a Voip item and the Voip item was added after the Internet item then the Voip items maturity is used to determine the contracts end of term.
The TV item is only used if the customer neither has a Internet nor a Voip item.
Yearly charged Products
How to setup when a product with yearly billing cycle (charged once in a year) will be charged.
You have to select the month (numerated from 1 to 12) in a CostCenter. Then you can select the CostCenter in the Contract or in the Product. The following two examples explain how it is handled:
Contracts CostCenter has 'Month to create bill' = 5. All products assigned to that contract (=items (german: Posten)) that do not have a CostCenter assigned will be charged in may.
Contracts CostCenter has 'Month to create bill' = 5. The customer has 2 yearly charged items. One of that has a CostCenter selected that has 'Month to create bill' = 10. So one item will be charged in may and the other one in october.
Overview of billing/payroll cycles (german)
| Name | Beschreibung |
|---|---|
| 3M | Abbuchung für die kommenden 3 Monate von Postenstart. Z.B. bei Beginn 15.11.23 wird im Nov, Feb, Mai und August abgebucht |
| vierteljährlich zum ersten Monat | Abbuchung vierteljährlich in den Monaten 1, 4, 7 und 10 jeweils für die kommenden 3 Monate. D.h. im Januar wird für Jan, Feb, März abgebucht. |
| einmalig | Abbuchung einmalig im kommenden Rechnungslauf |
| monatlich | Abbuchung monatlich für den letzten (nicht aktuellen) Monat |
| vierteljährlich | Abbuchung vierteljährlich in den Monaten 2, 5, 8 und 11 jeweils für den vorherigen, den aktuellen und den kommenden Monat. D.h. im Februar wird für Jan, Feb, März abgebucht. |
| halbjährlich | Abbuchung in den Monaten 1 und 7 jeweils für das kommende halbe Jahr. |
| jährlich | Abbuchung 1x im Jahr gemäß des eingestellten Abrechnungsmonats der zugehörigen Kostenstelle - aus Vertrag | Produkt | Posten (mit aufsteigender Priorität) |