Setup
This chapter discusses all the topics relevant to the facility.
Subscription Setup
General settings for subscription management can be defined on the Subscription Setup page.
General
Settings relevant to the application are made on the
![]() |
---|
Ill. Subscription Setup Tab General |
The following fields are available:
Field | Description |
---|---|
Limit Components to Billing Period | Limits the earliest and latest date on which a component is allowed to be recorded to the Start and End of Last Billing Period of the current Subscriptions. This can be overridden for each individual User through Settings in the User Setup. |
Allow Posting Component From | Specifies the earliest date from which component bookings are permitted. This can be overridden by a corresponding setting in the user setup for each individual user. |
Allow Posting Component To | Specifies the last date on which component bookings are permitted. This can be overridden by a corresponding setting in the user setup for each individual user. |
Collective invoices | Defines the circumstances under which Collective Documents are created if this is defined via the collective invoice group in the Subscriptions. The following options are available. Open Documents: Allows a collective invoice for all related Open Invoices or Orders. Unposted Documents: Allows a collective invoice for all related open or Released Invoices/Orders. Current batch only: Allows a collective billing only for related Documents that are generated in the same batch. Never: Categorically prohibits collective invoices, even if this is set up in Subscriptions. |
Zero Amt. Bill Handling | Specifies how Zero Amount Bills are to be handled. Zero Amount Bills can occur if, for example, there are Subscriptions that only contain Items that are billed according to consumption but have no consumption in the Current Billing Period. The following options are available: <empty>: Functions remain as in the BC Default. Zero Amount Bills may be generated that cannot be posted or automatically switched to the next billing period. The user must delete the Invoice manually and set the Dates for the next billing period in the Subscriptions manually. Create & mark Subscriptions: Zero Amount Bills are created if applicable, but in addition, Subscriptions that have caused a Zero Amount Bills are marked so that it can be easily checked whether the Zero Amount Bills are justified, or whether Consumption Qty. may have been neglected to be entered. This option also allows Zero Amount Bills to be posted. Error messages are no longer generated when an attempt is made to post a Zero Amount Bills, instead a posted Document without G/L items is generated. The accounting period is switched to the next Period during this posting. However, if this option is to be used, a value must be entered in the Zero Amount Bills field on the "Subscriptions" tab of the origin code facility (Default BC) in order for the zero invoice to be posted. The Zero Amount Bills posted are then marked with this value as the Source Code. Mark Subscriptions: None is created in principle, only the Subscriptions that would have caused a Zero Amount Bills are marked. Set next billing period: Does not create a Zero Amount Billing and does not mark the Subscription that would have caused a Zero Amount Billing, but switches the Billing Period of the Subscription that would have caused a Zero Amount Billing immediately to the next Period. Each of these Options is basically valid. Setup depends on the individual approach. However, we would not recommend blindly moving on to the next billing period. Instead, the "Mark Subscriptions" option appears to be recommended. |
Allow Line Prices | Defines whether line prices are allowed for subscriptions. Subscription-specific prices apply to the entire subscription. In some cases, the same item can be sold multiple times in the same subscription, each at different prices. It is therefore also possible to set up prices at subscription line level. The following options are available: Never: It is not possible to store prices at subscription line level. Selected Items: The storage of prices at subscription line level is only possible for selected selected items that are marked accordingly in the Allow Line Prices field on the item card. Always: It is always possible to store prices at subscription line level. How to deal with subscription line prices is a strategic consideration. Once subscription line prices have been stored, the option can only be switched off again in the Setup if all subscription line prices have been deleted beforehand. |
Auto-Create Line Prices | Determines whether line-specific subscription prices or only subscription-specific subscription prices should be created when automatically creating subscription prices, as is possible, for example, from the subscription itself and when creating a subscription from a sales quote. The following options are available: Never: Line-specific prices are never generated during the automatic creation of Subscriptions prices. If required: When Subscription Prices are created automatically, line-specific prices are only generated if the same Item appears multiple times in the same subscription. Always: When Subscription Prices are created automatically, line-specific prices are always generated. |
Product Version Level | Fixed at which level the Product Version Level can be maintained. The following options are available: Subscription: The Product Version can only be defined at Subscription Level. A Subscription Item of the subscription is defined as the product that specifies the version for all other subscription lines. Subscription line: At the subscription line level, the Product Versions and Named Users with Start and Ending Dates can be maintained individually for each subscription item. Both levels: Product Versions and any additional information regarding named Users can be maintained at both Subscriptions and Subscription Line level. Never: Product Versions and any additional information regarding named Users cannot be maintained. |
Allow Partner Accounts | Determines whether a Partner Account Type, e.g. VOICE, and a Partner Account can be assigned to the Subscriptions. |
Archive Watchlist Reasons | Determines whether the reasons why a Subscriptions has been placed on the Watchlist are archived. |
Save Latest Searches | Defines the number of the last usage search queries to be saved. None of the last 10 searches are saved if you do not specify a number. The maximum possible number is 100. This setting can be overwritten individually for each User. |
Deactivated Color | Lines Deactivated in Subscriptions can be displayed in the following colors: Yellow Gray Red + Italic Red + Italic + Bold The color yellow is the default setting. If you want the color coding to stand out more clearly, the color red + italics is a good choice. The color gray may not be displayed clearly enough on some browsers. |
Switch off color coding | Hide Color Coding, which indicates on the Subscriptions overview whether a subscription for the invoice is overdue or whether a still unposted Document has already been generated for a subscription. |
Numbering
![]() |
---|
Ill. Subscription Setup Tab Numbering |
Field | Description |
---|---|
Subscription Nos. | Defines the Code for the No. Series that is used to assign numbers to Subscriptions. |
Subscription Request Nos. | Defines the Code for the No. Series that is used to assign numbers to subscription requests. |
Component Identifyer Nos. | Defines the Code for the No. Series used to assign numbers to component IDs. Component Identifyers are used to define a unique ID for each Subscriptions Line. |
Subscription price list numbers | Defines the Code for the No. Series that is used to assign numbers to Subscriptions price lists. |
Tenant Nos. | Defines the Code for the No. Series that is used to assign numbers to Tenants. |
Users Default values
![]() |
---|
Ill. Abonnement Einrichtung Tab Benutzer Vorgabewerte |
Field | Description |
---|---|
Create Subscription Requests | Defines whether each User can create and edit subscription requests. This setting can be overridden for each individual User in the Subscriptions User Setup. |
Confirm Subscription Requests | Defines whether each User can confirm Subscription Requests so that they can be converted to Subscriptions. This setting can be overridden for each individual User in the Subscriptions User Setup. |
Subscriptions Default values
![]() |
---|
Ill. Subscription Setup Tab Subscription Default Values |
The following fields are available:
Field | Description |
---|---|
Billing Document to Create | Defines which Type of Document is generated from a Subscriptions for the purpose of creating Recurring Invoices. Three options are available: Invoice: A sales invoice is created for billing purposes. Order: A Sales Orders is created for Billing. G/L items: Documents are not created at all. Instead, it is posted directly to non-cash items. This option is particularly relevant in connection with recurring rental invoices, where the customer receives a one-off direct debit notification at the beginning of the Subscription Period, but no Invoice for each subscription interval thereafter. |
Price Calculation Date | Defines which date is used as the Reference Date for calculating the price for the current billing period. |
Billing Frequency Code | Defines the Billing Frequency Code Filter for the Subscriptions. |
Subscription Period Code | Defines the validity period of the Subscriptions. |
Grace Period Code | Defines the Periods during which the user still has access to the subscribed object or service, even though its validity period has already expired. |
Termination Period Code | Specifies a notice period that you would like to use as a default for Subscriptions. |
Renewal Billing Frequency Code | Specifies a Billing Frequency Code Filter that you want to use as a default when renewing the Subscriptions. |
Renewal Subscription Period Code | Specifies a Subscription Period that you want to use as a default when renewing the subscription. |
Auto-Sign after Trial | Determines whether a paid subscription should be taken out after the end of the trial version. This setting is adopted as the default in the Subscriptions. |
Auto-Renew Default | Determines whether the subscription should be renewed at the end of the Subscription Period. This setting is adopted as a default in the subscriptions. |
Auto-Price Renewal | Determines whether the existing Subscription Prices should also be automatically renewed when the Subscription is automatically renewed at the end of the Subscription Period. This is a content-based decision that depends on whether the customer should pay standard prices after the original subscription term expires, or whether their specific subscription prices should be extended. The following options are available: Never: Existing prices are not automatically renewed. Renewal End Date: Existing prices are automatically renewed by setting their Ending Date to the end of the New Term. Create New Price Line: Existing prices are automatically renewed by creating a new price line with the Start Date and Ending Date of the new term. The respective settings are transferred to the Subscriptions as a default. |
Auto-Grace Period Default | Defines whether a grace period should be taken into account at the end of the Subscription Period. This setting is adopted as a default in the Subscriptions. |
Subscription Design Code | Specifies a subscription design that is used by default for the subscriptions, unless you have assigned a different value in the subscription. |
Auto-Text Code | Specifies an Auto-Text that will be used by default for Subscriptions unless you have assigned a different value in the Subscription. |
Custom Text Code | Specifies the Default Custom Text that is applied to Subscriptions lines when no other Custom Text has been associated with the Subscription itself. Custom Text Codes can be used to customize the design of the additional information lines for a Subscription Item. |
Customer Subscription Code | Defines the Default Setup with which customer subscriptions are created. If nothing is entered in this field, the internal default values are used. |
Suggest Changes on Starting Date Update | Specifies whether to display a dialog with suggestions that allows you to update the Recording Date from component entries in the batch after you have manually changed the Starting Date of a Subscription. This function is only available if no Invoices or Orders have yet been created or posted from the Subscriptions. |
Dimensions
![]() |
---|
Ill. Subscription Setup Tab Dimensions |
Field | Description |
---|---|
Subscription Dimension Code | If this field is filled in, the system automatically creates a dimension value for each Subscription Nos. and adds it to the dimension set items of all the lines of the documents linked to the subscription. |
Subscription Type Dim. Code | If this field is filled in, the system automatically creates a dimension value for the subscription type assigned in the subscription and adds it to the dimension record items of all lines of the documents linked to the subscription. |
Customer Subscr. Grp. Dim. Code | If this field is filled in, the system automatically creates a dimension value for the Customer Subscription Group assigned to the subscription and adds it to the dimension record items of all lines of the documents linked to the subscription. |
Show Global Dimensions | Specifies whether the global dimensions are displayed on the subscription card. |
Auto-Text
![]() |
---|
Ill. Subscription Setup Tab Auto-Text |
Field | Description |
---|---|
Date Format Type | Specifies the Date Format Type you want to use in the Auto-Text for Subscriptions. |
Date Format | Specifies the Date Format for the Auto-Text |
Booking Description
![]() |
---|
Ill. ASubscription Setup Tab Booking Description |
Field | Description |
---|---|
Posting Description Type | Specifies what the booking description should look like. Please note that the booking description for collective invoices always consists of a list of subscription numbers, regardless of what you enter here. The following options are available: Business Central Default: The posting description consists of the Document Type and the Document Number. Subscription No.: The booking description consists of the Subscription Nos. Document No. + Subscription No.: The booking description is made up of the document number and the subscription number. Subscription No. + billing period: The booking description is made up of the subscription number and the current billing period of the subscription. Subscription description: The booking description is taken from the Subscriptions description field. Subscription description + Billing Period: The booking description is made up of the subscription description and the current billing periods of the subscription. Subscription No. + Description + Periods: The booking description is made up of the Subscription No., the Description and the Current Billing Periods of the Subscriptions. |
Booking description Date format code | Used as a shortcut to enter the Date Format for the accounting periods contained in the booking description in a user-friendly form. |
Date Format | Defines the format in which the dates are displayed in the subscription line. You can use the Date Format Type so that the system automatically creates the format for you. |
Flash Setup
The "Flash Setup" action starts a quick, fully automated Setup of bill-to. You should only run this function if you have not yet set up bill-to manually. The routine takes into account your access rights, which must be comprehensive for a successful automatic Setup.
![]() |
---|
Ill. Subscription Setup Action Flash Setup |
The following setups are made:
Subscription Setup
Field | Description |
---|---|
Date format code | April 05, 2021 |
Create Subscription Requests | Activated |
Confirm Subscription Requests | Activated |
Periods
Field | Description |
---|---|
Subscription Period | 1Y, One Year |
Accounting period | 1M, one Months |
Grace period | 1M, one Months |
Notice period | 3M, three Months earlier |
Document Design
Field | Description |
---|---|
Autotextcod | DEFAULT |
Subscription Design Code | DEFAULT |
No. Series
-
Subscription Nos.
-
Subscription Request Nos.
-
Component identifiers
-
Batch Invoicing Nos.
-
Subscription Price List Nos.
-
Tenant Nos.
Watchlist Reason Codes
The following Watchlist Reason Codes can serve as examples or are generated when the setup data is automatically generated by bill-to via the Flash Setup:
-
INQUIRY: The customer has a special request
-
RUNNING TIMES: The subscription is approaching the end of its term
-
NEW: New customer
-
PITCH: Subscriptions have been offered but not yet accepted
-
PROBLEM: There is a technical issue with the Subscriptions
-
REKLAMATIO: Customer complaint
-
VIP: Very important customer
-
WEITERGELE: The Subscriptions has been forwarded
Document Setup
Settings relating to the creation of subscriptions from sales quotes or the creation of purchasing documents from subscription order proposals can be stored in the document setup.
![]() |
---|
Ill. Subscription Document Setup |
The following fields are available:
Field | Description |
---|---|
Subscription Features Available | Defines in which sales quotations special functions for creating subscriptions from quotations should be available. The options are: Subscription Quotes: Subscriptions functionalities are only available in sales quotes that are explicitly marked as such via the Sales quote field. All Quotes: Subscriptions functionalities are available in all sales quotes. Never: Subscriptions are generally not available in sales quotes. This also means that no subscriptions can be generated from sales quotes. |
Skip Quote Text Line | Defines how leading or trailing texts in the Quote (e.g. introduction, closing formula) are to be handled when creating Subscriptions by Quote. You can choose from the following options: <blank>: Text lines are not treated separately. All text lines of the Quote are also included in the Subscriptions. All: All text lines of the Quote will be ignored; None of the text lines will be included in the Quote. Before the first item line: All text lines of the Quote that appear before the first item line are ignored and not included in the subscription. After the last item line: All text lines of the Quote that are after the last item line are ignored and not included in the subscription. Before the first and after the last item line: All text lines that appear before the first and after the last item line of the Quote are ignored and not included in the subscription. Ultimately, you can't go wrong even if you leave the value of this field blank, as bill-to initially presents the user with all the lines to be accepted for selection when creating a subscription from a Quote. Text lines that are not required can therefore still be deselected manually at this point. |
Item without Price | Defines how to proceed when creating a Subscriptions from the sales quote if no price line is available, but a price is only stored in the quote line itself. The following options are available: Leave without price: No price line is generated for the Item in Subscriptions either. Output Error Message: An Error Message is displayed and a Default Price Line must first be created for the Item. Generate price: A subscription price line is generated for the Item. |
Create Subscription Prices | Defines whether subscription-specific prices should always be created when a subscription is created from the sales quote. If this option is not activated, subscription-specific prices are only created if the quoted prices differ from the default prices for this Customer. |
Suppress Subscription Quantity | Suppresses the creation of component entries, i.e. Subscription Qty., when a subscription is created from a sales quote. It is still possible to create component entries, i.e. write Subscription Qty., when an existing subscription is updated in Subscription from a sales quote. Functions are also ignored when creating quota lines. |
Purchase Document Type Dflt. | When creating purchasing documents from the order proposals of the Subscriptions, the Document Type of the purchasing document must be specified. It can be preset via this field. The available options are: <empty>: The Document Type of the order proposal line is determined internally using the following logic: If the document type Invoice is to be generated from the Subscriptions in Sales, then the document type Invoice is also selected in the order proposal for Purchase; if the document type Order is to be generated from the Subscriptions in Sales, then the document type Order is selected in the order proposal for Purchase. Invoice: The order proposal lines are pre-assigned with the Document Type Invoice. Order: The order proposal lines are pre-assigned with the Document Type Order. The Document Type can still be changed in the order proposal itself. |
Qty. Suggestion | Defines how the suggested quantities are calculated when order suggestions are generated from a subscription. The following options are available: Sales quantity: The Qty. Suggestion is generated on the basis of the sales quantity. Commissioned Quantity: The Qty. Suggestion is generated on the basis of the Commissioned Quantity. |
Commission Calculation | This field can only be edited if the Qty. Suggestion field is set to the value "Commissioned Qty.". It specifies a date formula to determine how many Days in relation to today are taken into account when the proposed order quantity is calculated on the basis of the Commissioned Quantity. The date calculation is based on the Order Date of the Commissioned Quantity. If no date formula is specified, commissioned Qty. up to today are taken into account. |
Customer Subscription Setup
Customer subscriptions can be used to call up and edit all subscriptions for the same Customer in a general overview. This is an ideal tool for displaying and editing Subscription Items from the same Customer that are split across several subscriptions due to different terms and Billing Frequency Code Filters in a single overview.
One possible procedure for editing subscriptions is therefore to manage the continuous maintenance of subscriptions after the initial creation via the so-called customer subscriptions, which virtually bring several subscriptions into one view and make them editable in this view.
The type of virtual customer subscription can be configured in the customer subscription Setup. An unlimited number of setups can be created for customer subscriptions.
![]() |
---|
Ill. Customer Subscription Setup |
The following fields are available in the Customer Subscription Setup:
Field | Description |
---|---|
Code | Specifies the Primary Key of a customer subscription Setup. |
Description | Describes the customer subscription Setup in more detail. |
Scope | Determines the Scope of the Line. displayed in the customer subscription. The following options are available: Subscription Item: In the customer subscription, only the Subscription Item Lines of the subscription are displayed, but not e.g. text lines, group totals etc. Entire subscription: All lines of the respective subscription are displayed in the customer subscription. |
Skip Subscription Header | By default, the Customer Subscription displays a header line at the beginning of each Subscription of the same Customer, which contains the Subscription No. and Description. This switch can be used to deactivate the creation of this heading line in the customer subscription. |
Skip Empty Line | By default, the customer subscription generates a blank line between each subscription of the same Customer. This switch can be used to deactivate the creation of this blank line in the customer subscription. |
Subscription Type Group | The creation of a Customer Subscription is always filtered to the Subscriptions of the respective Customer. However, three additional filters can be set to restrict the consideration of certain subscriptions. The subscriptions to be taken into account in the customer subscription can be filtered via the Subscription Type Group, the Billing Frequency Code Filter and the Subscription Period. The Subscription Type Group field filters the subscriptions to be taken into account for the customer subscription to a specific subscription type group, e.g. MICROSOFT, RENTALS or similar. A filter can be preselected in the customer subscription Setup, but this can easily be changed again in the actual customer subscription. |
Billing Frequency Code Filter | The Billing Frequency Code Filter field filters the subscriptions to be taken into account for the customer subscription to a specific billing frequency, e.g. 1M, 1Y or similar. A filter can be preselected in the customer subscription Setup, but this can easily be changed again in the actual customer subscription. |
Subscription Period | The Subscription Period field filters the subscriptions to be taken into account for the customer subscription to a specific subscription period, e.g. 1Y, 3Y or similar. A filter can be preselected in the customer subscription Setup, but this can easily be changed again in the actual customer subscription. |
The following promotion is also available in the customer subscription Setup:
Field | Description |
---|---|
Recalculate Customers | It is possible that not all Customers have a subscription, but that only some of the Customers are billed via subscriptions, while others follow other business logics. The application keeps track of which Customers are subscription Customers and which are not. The Recalculate Customers action can be used to force a recalculation of the subscription Customers. |
In the Customer Subscription Code field on the "Subscription default values" tab of the Subscription Setup, you can specify which customer subscription Setup is to be used as the default.
![]() |
---|
Ill. Customer Subscription Code |
If there is no default for the structure of the customer subscription, the application itself decides on the structure.
Subscription User Setup
![]() |
---|
Ill. Subscription User Setup |
Field | Description |
---|---|
User ID | Specifies the ID of the User who posted the Entries (e.g. for use in the change log). |
Limit Components to Billing Period | Limits the earliest and latest date on which Users may enter a component to the Start and End of Last Billing Period of their Subscriptions. |
Allow Posting Component From | Specifies the earliest date on which the Users may post a change to the Quantity of the Subscription Item. |
Allow Posting Component To | Specifies the last date on which the Users may post a change to the Quantity of the Subscription Item. |
Allow subscription requests | Specifies whether the user is allowed to create new subscription requests and new lines in existing subscription requests. If this is not the case, Users can only Edit or Delete existing subscription data. If this option is set to "Default", the authorization is based on the General Setup in the subscription setup. |
Allow Request Confirmation | Specifies whether the Users is allowed to confirm subscription request lines so that they can be used to Create or Refresh subscription lines. If this is not the case, Users can only Edit or Delete existing subscription data. If this option is set to "Default", the authorization is based on the General Setup in the subscription setup. |
Edit Period Dates | Specifies whether the Users is allowed to change all Dates related to Billing Period and Subscription Period for the Subscriptions after the first Invoice has been issued. |
Save Latest Searches | Defines the number of the last usage search requests to be saved. None, the default number from the subscription setup is used. The highest possible number is 100. |
Salespers./Purch. Code | Specifies the Sell-to or Purchase Code for the Users. |
Specifies the Users E-Mail address. | |
Phone No. | Specifies the Users telephone number. |
Automatic Component Creation Setup
![]() |
---|
Ill. Automatic Component Creation Setup Tab Reference to Purchasing Line |
Field | Description |
---|---|
Upd. Subscription by Purch. Line | Specifies whether subscription lines can be refreshed by purchase lines. If you select the 'Direct' option, the Quantity of a subscription component can be refreshed directly by a Purchase if the "Component Identifyer" field in the Purchase line is filled. If you select the 'By Journals' option, a Journals line is created instead, which must be imported later. If you select 'Direct' but there is not enough information to create the quantity update directly, a Journals sheet will be created instead for later review and allocation. |
Subscription Book. sheet template | Defines the Subscription Jnl. Template to be used to create Purch. Line Jnl. Templates that represent component updates from Purch. Lines. |
Subscription Jnl. Batch Name | Specifies the Purch. Line Jnl. Batch Name to be used to create Purch. Line Jnl. Batches that represent component updates from purchase lines. |
![]() |
---|
Ill. Automatic Component Creation Setup Tab Reference to Purchase distribution |
Field | Description |
---|---|
Upd. Subscr. by Purch. Allocation | Specifies whether subscription lines can be refreshed by purchase line distributions. If you select the "Direct" option, the Quantity of a subscription component can be refreshed directly by a Purchase if the "Component Identifyer" field in the Purchase line is filled in. The "By Journals" option creates a Journals line instead, which must be imported later. If you select "Direct" but there is not enough information to create the quantity update directly, a Journals sheet will be filled instead for later checking and allocation. |
Subscription Book. sheet template | Defines the Subscription Jnl. Template to be used to create Purch. Line Jnl. Templates that represent component updates from Purch. Lines. |
Subscription Jnl. Batch Name | Specifies the Subscriptions Journal Batch Name to be used to create Journal Batch rows representing component updates from purchase row distributions. |
![]() |
---|
Ill. Automatic Component Creation Setup Tab Reference to Assembly |
Field | Description |
---|---|
Upd. Subscr. by Assembly | Specifies whether subscription lines of assemblies can be refreshed. If you select the "Direct" option, the Quantity of a subscription component can be refreshed directly by a Purchase if the "Component Identifyer" field in the Purchase line is filled in. The "By Journals" option creates a Journals line instead, which must be imported later. If you select "Direct" but there is not enough information to create the quantity update directly, a Journals sheet will be filled instead for later checking and allocation. |
Subscription Book. sheet template | Defines the Subscription Jnl. Template to be used to generate Assembly Jnl. Template lines that represent component updates from Assemblies. |
Subscription Jnl. Batch Name | Specifies the Assembly Jnl. Batch Name to be used to create Assembly Jnl. Batch rows representing component updates from Assemblies. |
Units
On this page, you can define Short Descriptions for the Units that are used in the details information of the subscription line. You can also define translations for these Short Descriptions for each applicable language. If you do not define Short Descriptions, the Description of the unit of measure is used.
![]() |
---|
Ill. Units |
Watchlist Reason Code
You can define Watchlist cause codes for subscriptions that you want to monitor and assign them to the subscriptions. These marked subscriptions are displayed in your role center.
![]() |
---|
Ill. Watchlist Reason Code |
Field | Description |
---|---|
Code | Specifies a Reason Code to be assigned to the Subscription Watchlist entry. |
Description | Provides a Description of what the Code stands for. |
No. of Subscriptions | Enter the number of Subscriptions that have this Watchlist Reason Code assigned. |
Distribution Categories
On this page, you can define distribution categories and associated values that you want to use in the subscription rows for the distribution of Turnover. The functionality can be used to display the actual Turnover. The distribution is reflected in the Subscription Ledger Entry.
Collective Invoice Groups
On this page, you can define collective invoice groups that you can assign to the subscriptions. Subscriptions for which a collective invoice group has been assigned are combined in a collective invoice during billing and not billed separately as usual.
![]() |
---|
Ill. Collective Invoice Groups |
Field | Description |
---|---|
Code | Defines a Code that identifies this collective invoice group. |
Description | Defines a Code that identifies this collective invoice group. |
Periods
This Section explains how the different Periods are set up and what their purpose is. The following Periods can be managed in bill-to:
-
Billing Frequency Code Filter
-
Subscription Periods
-
Grace periods
-
Notice periods
Billing Frequency Code Filters
On this page, you set up the Billing Frequency Code Filters that you have agreed with your customers and that are to be used in the Subscriptions.
![]() |
---|
Ill. Billing Frequency List |
Billing Frequency Code Filters are the Periods for which a Subscriptions is billed periodically. These can be one Monthly, One Year, Three Years or any other Periods. The list of Billing Frequency Code Filters shows all defined billing periods. New billing intervals are not created or edited directly in the list, but via the Billing Frequency Code Filter.
![]() |
---|
Ill. Billing Frequency Card |
The following fields are available on the billing interval card:
Field | Description |
---|---|
Code | Specifies a Code to identify the Billing Frequency Code Filter. The Code can be a maximum of ten characters long. |
Description | Enters an explanation of the Billing Frequency Code Filter. The Description can also be set automatically using the Frequency Type field. |
Deferral Code | Specifies the Accruals template that governs how accrued revenue is accrued for different accounting periods of sales transactions. It is recommended to select a Deferral Code that is set up for flexible determination of Periods or to create such an accrual template. This is done by checking the Subscription Deferral box on the General tab of the Deferral template card. |
Purch. Deferral Code | Specifies the Accruals template that governs how expenses incurred for different accounting periods are accrued from purchase transactions. |
No. of Subscriptions | Shows in how many subscriptions this Billing Frequency Code Filter is used. The drill-down function of this field can be used to branch to the subscriptions with this Billing Frequency Code Filter. This field is only displayed if the subscription is already activated, i.e. if the "Not ready for use" warning is no longer displayed. |
Frequency Type | Select a Frequency Type to automatically enter the calculation and Description of the Billing Frequency Code Filter date formula. You can also leave the Frequency Type blank and enter the billing interval calculation and Description manually. The Frequency Type is only an auxiliary function for entering the date formula in the Frequency Calculation field; only the date formula is decisive for the calculation. If you select a Frequency Type, the value of the Description field can be set automatically. |
Frequency Calculation | Specifies a formula that determines how the Billing Frequency Code Filter is calculated, e.g. when you determine the Next Invoice Date of a Subscriptions. The field is a date formula. For example, to describe a Billing Frequency Code Filter of one month, enter the formula 1M-1T (one month minus one day = e.g. March 1 to March 31 or April 1 to April 30). To describe a Billing Frequency Code Filter of one year, enter the formula 1J-1T (one year minus one day = e.g. January 1 to December 31 or April 1, 2023 to March 31, 2024). A whole Months is added to the Starting Date of the Billing Frequency Code Filter by this date formula, for example March 1, so that we would be at April 1; then a Day is subtracted, so that the Ending Date of the Billing Frequency Code Filter is set to March 31. You can have the date formula determined automatically by the application via the Frequency Type field. If no suitable Billing Frequency Code Filter is available as a proposal in this field, you must instead enter your Billing Frequency Code Filter manually using the date formula in the Frequency Calculation field. In both cases, only the date formula is decisive for the calculation; the Frequency Type field only quotes an auxiliary function. |
Frequency Variation | This field is only available if Billing is done Monthly, Yearly or Quarterly, but not for other Frequency Calculation. This field can be used to control how the billing periods are to be determined exactly. The following options are available: Interval period: The Periods are calculated strictly according to the Frequency Calculation starting from the last Date. With monthly billing and a Starting Date of January 30, 2023, the first three Months are as follows: 30.01.23 - 27.02.23, 28.02.23 - 27.03.23, 28.03.23 - 27.04.23. Calendar period: Periods are always calculated according to calendar periods. For monthly billing and a Starting Date of January 30, 2023, the first three Months are as follows: 30.01.23 - 31.01.23, 01.02.23 - 28.02.23, 01.03.23 - 31.03.23. Equally distributed Periods: The Periods are equally distributed based on the first billing period and calculated in multiples of the Starting Date. In the case of monthly billing and a Starting Date of January 30, 2023, the first three Months are as follows: 30.01.23 - 27. 2.23, 28.02.23 - 29.03.23, 30.03.23 - 29.04.23. With monthly billing and a billing start date on the first of the month, all three methods produce the same Results. In the case of monthly billing and the start of billing on or before the 28th of the month, the "Interval period" and "Equally distributed period" methods produce the same result. The Simulation action on the billing interval card can be used to display a simulation of the settings over the first 18 Months. The "Equally distributed Periods" option can be regarded as the Default setting. |
Auto-Renew Behavior | This field is used to control how the billing period is to be calculated after an Auto-Renewal of a Subscriptions. The following options are available: Continue seamlessly: The automatic renewal of the Subscription Period is interpreted as a continuous billing period. This has a particular impact on the "Calendar period" and "Equally distributed period" Frequency Variation. For example, if the subscription starts on 30.01.23, is billed Monthly for an annual term with Auto-Renew and the Frequency Variation is "Calendar Period", then the 13th Period, i.e. the first renewal period, runs from 01.01.24 to 31.01.24, and the 14th Period runs from 01.02.24 to 29.02.24. New billing period: Auto-Renew will of course be respected. However, before a new billing period begins, the last period of the previous term is closed. If the subscription begins on 30.01.23, is billed monthly for an annual term with automatic renewal and the Frequency Variation is "Calendar Period", then the 13th Period runs from 01.01.24 to 29.01.24, the 14th Period from 30. 1.24 to 31.01.24 and the 15th Period from 01.02.24 to 29.02.24. The transition in the renewal period is therefore analogous to the very first billing period. The Simulation action on the billing interval card can be used to display a simulation of the settings over the first 18 Months. The "Continue seamlessly" option can be considered the Default setting. |
Idle Time Calculation | Specifies a date formula that determines a downtime between the last and the next billing period. Normally, the next billing period begins exactly one day after the end of the previous one, i.e. it follows on seamlessly. You do not need to enter anything in this field. However, downtimes are useful for periodic services such as winter services. Define the Idle Time Calculation in the same way as the billing period. Example: If there is a billing period of five months and a downtime of seven months before the next billing period begins, set the billing period calculation to 5M-1T and the downtime calculation to 7M-1T. |
Status after Idle Time | This field can be used to automatically set the Status after Idle Time Status of a subscription. This is not necessary, as the next billing of the Subscriptions will only take place after the end of the standstill and the start of the following new billing period anyway. But perhaps the service should not be continued automatically after the end of the standstill, but only after dialog with the customer. The field has the following options: <empty>: The status of the subscription is not changed (i.e. usually remains at Active). Active: The status of the Subscriptions is set to Active. Suspended: The status of the subscription is set to Suspended. This means that the subscription is not automatically invoiced at the start of the next billing period, but only after it is manually set to Active again. |
Billing Day Calculation | Specifies when the billing should take place, for example at the End of Billing Period or at the beginning of the billing period. The following options are available for selection: Days before the start of the billing period Start of Billing Period Days after the start of the billing period Middle of the accounting period Days before the end of the billing period End of Billing Period Days after the end of the billing period End of the Current Months Beginning of the following month Fixed Days of the Current Months Fixed Days of the following month First defined day in payroll period |
Billing Day(s) | This field is only relevant if an option such as "Days before Start of Billing Period" or "Days after End of Billing Period" has been selected in the Billing Day Calculation field. The Billing Day(s) field is then used to determine exactly how many days before or after the billing period it is. The application automatically determines whether a value is required in this field or not. If None is required, it cannot be edited. |
Four additional actions are available:
Action | Description |
---|---|
Default Billing Frequency Code Filter | Calls up a selection that allows the user to set the preferred default settings in the fields Frequency Type, Frequency Calculation, Auto-Renew Behavior and Auto-Renew Behavior by clicking on the selection. |
Activate | If you have filled in all the fields for a Billing Frequency Code Filter, it still cannot be used. You must first perform the Activate action to achieve this. Before the Billing Frequency Code Filter is activated, the application automatically checks whether all the required fields have been completed. As long as the message Not ready for use is still displayed on the General tab, the Billing Frequency Code Filter cannot be used operationally. |
Check usability | Checks whether all the fields required for activation have been filled in and the Billing Frequency Code Filter can therefore be used and displays the result of this check. This does not activate the Billing Frequency Code Filter, it only checks it. You do not need to perform this action, as it is also performed in the background when the Billing Frequency Code Filter is activated via the Activate action. |
Simulation | Calls up a simulation that calculates and outputs the first 18 Periods according to the Settings in the fields Frequency Calculation, Auto-Renew Default and Auto-Renew Behavior. The Starting Date is initially set to 30.01.2023 because this date makes the differences between the Settings particularly clear. In the simulation, however, you can work with a different Starting Date and different Settings in these fields to see the effects of these changes. The simulation can also be called up via the AssistEdit functionality of the Frequency Calculation field. A Billing Frequency Code Filter requires certain settings. As a minimum, a Calculation Frequency, the Billing Day Calculation and - depending on the Options selected for the Billing Day Calculation - the specification of the Billing Days are required. If a Billing Frequency Code Filter is not completely defined, it cannot be used operationally. The Billing Frequency Code Filter must be made ready for use via the Activate action before it can be used. Before this, the General tab shows that the Billing Frequency Code Filter is not yet ready for use: |
![]() |
---|
Ill. Billing Frequency Not ready for use |
After successfully activating the Billing Frequency Code Filter via the Activate action, this warning disappears and the number of Subscriptions in which this Billing Frequency Code Filter is used is displayed instead:
![]() |
---|
Ill. Billing Frequency Activated |
Once the subscription interval has been activated, the following fields can no longer be edited:
-
Frequency Type
-
Frequency Calculation
Subscription Periods
On this page, you set up the Subscription Periods that you have agreed with your customers and that are to be applied in the Subscriptions.
![]() |
---|
Ill. Subscription Periods |
Field | Description |
---|---|
Code | Specifies a Code to identify the Subscription Period. |
Frequency Type | Select a Frequency Type to automatically enter the calculation and Description of the Subscription Period. You can also leave the Frequency Type blank and enter the calculation and Description of the Subscription Period manually. |
Period Calculation | Specifies a formula that determines how the Subscription Period is calculated, e.g. when you determine the Ending Date of a subscription. |
Description | Provides an explanation of the Subscription Period. |
Grace Periods
On this page, you set up the grace periods that you have agreed with your customers and that are to be applied in the Subscriptions.
![]() |
---|
Ill. Grace Periods |
Field | Description |
---|---|
Code | Specifies a Code to identify the grace period. |
Frequency Type | Select a Frequency Type to automatically enter the calculation and Description of the grace period. You can also leave the Frequency Type blank and enter the calculation and Description of the grace period manually. |
Period Calculation | Specifies a formula that determines how the Grace Period is calculated, e.g. when you determine the Grace Period Ending Date of a Subscription. |
Description | Provides an explanation of the grace period. |
Notice Periods
On this page, you set up the notice periods that you have agreed with your customers and that are to be applied in the Subscriptions.
![]() |
---|
Ill. Notice Periods |
Field | Description |
---|---|
Code | Specifies a Code to identify the grace period. |
Frequency Type | Select a Frequency Type to automatically enter the calculation and Description of the notice periods. You can also leave the Frequency Type blank and enter the calculation and Description of the notice period manually. |
Period Calculation | Specifies a formula that determines how the notice period is calculated, e.g. when you determine the Ending Date of the notice period for a Subscriptions. |
Description | Provides an explanation of the notice period. |
Prepayment Conditions
A prepayment condition can be used to add the prepayment obligation to a billing document generated from the subscription. The prepayment condition also offers the option of pre-filling all prepayment-relevant fields via the subscription.
The prepayment terms are set up in the Documents - Finance menu. The list view takes you to the prepayment terms card, where all values can be maintained:
![]() |
---|
Ill. Prepayment Conditions |
The following fields are available; most of them are used to fill in the fields of the same name in the sales document:
Field | Description |
---|---|
Code | Specifies a Code that uniquely identifies this set of prepayment terms. |
Description | Provides an explanation of the prepayment terms. |
Payment Terms Code | Specifies the code for the payment terms for prepayment invoices relating to the sales document. |
Prepayment % | Specifies the prepayment percentage for calculating the prepayment discount. |
Prepmt. Payment Discount % | Specifies the cash discount rate granted for the prepayment if the Customer pays on or by the date entered in the Prepayment discount date field. |
Posting Description Type | Specifies how the booking description of the prepayment is composed. The booking description is preceded by the word "Prepayment" for all Options described below. The following options are available: Business Central Default: The posting description consists of the Document Type and the Document Number. Subscription No.: The booking description consists of the Subscription Nos. Document No. + Subscription No.: The booking description is made up of the document number and the subscription number. Subscription No. + billing period: The booking description is made up of the subscription number and the current billing period of the subscription. Subscription description: The booking description is taken from the Subscriptions description field. Subscription description + billing period: The booking description is made up of the subscription description and the current billing period of the subscription. Subscription No. + Description + Periods: The booking description is made up of the Subscription No., the Description and the Current Subscription billing period. |
Compressed Prepayment | Specifies that prepayments are combined in the Sales Orders if they have the same G/L account for prepayments or the same dimensions. |
![]() |
---|
Personal supportwww.ckl-software.de/ |