9.15. MultiGAAP
General #
In the General tab of the Multi GAAP System Parameters, you define the general setup of Multi GAAP, such as Estimation Frequency, Estimation Basis and which Booking Years to estimate.
Multi GAAP P&C System Parameters
Multi GAAP Life System Parameters
| Field | Description |
|---|---|
| Estimation Basis | The Estimation Basis determines how the estimations are booked to the ledger and how the sum up on the Portfolio Program is done. Accounting Year and Booking Year are the options available from the drop-down list. The key features of the two methods are listed below: Accounting Year: The estimated period starts from inception date of the Portfolio Program. Sum up of the Portfolio Program is done when adding up all 1st, all 2ndetc. periods. This won’t give the same results as what is booked or will be booked on the business ledgers of the Assumed Business. Instead it gives an overview as if all treaties start at the same date. This is useful when the accounting behaviour of your portfolio is of interest. It is also useful to know that all treaties of a certain portfolio are accounted in the same way, regardless of the inception date. The Multi GAAP Accounting order books the estimates to the accounting periods they belong to. The booking periods are provided per order run. When viewing the estimated bookings e.g. on the online statistics you should select Accounting Year. This gives the most accurate view. Booking Year: The estimated periods reflect booking periods regardless of the inception date of the business. On the Portfolio Program the same booking periods for all individual Assumed Business are summed up. This gives the same quarterly or monthly amounts on the Portfolio Program as on the Business Ledger of the connected Assumed Business, provided the Multi GAAP Accounting Order is run with the respective settings. This method should be used when balance sheet view is of interest. With this Estimation Basis the Portfolio Program can be used for budgeting purposes. The Multi GAAP Accounting Order always tries to book the estimations in the booking periods they were estimated for. This is not always possible because of closed booking periods. Accounting Period matches with the Booking Period if possible.. To configure the system for an Estimation Basis, Calculation Rules have to set up accordingly. Particularly when referencing values from a portfolio pattern the Calculation Rules have to be set up differently for Accounting Year and Booking Year method. Setting of the Estimation Basis should be done before any estimation rules or Calculation Rules are entered into the system. Each client should think carefully through which Estimation Basis to use before doing the basic system set up. Although the system does not prevent changing Estimation Basis while the system is in production, it is not recommended. All existing estimation on Portfolio Program and Assumed Business rely on the Estimation Basis. All bookings made by the Multi GAAP Accounting Order have their Booking Details set according to the Estimation Basis. |
| Estimation Frequency | Before you start using Multi GAAP, you need to decide which Estimation Frequency to use. The supported options are to estimate with a Quarterly or a Monthly frequency. The difference between the 3 Estimation Frequencies can be described as follows: Estimation Frequency = Quarterly * Period Estimates on business and portfolio programs are calculated, displayed and stored on a quarterly basis. * Default Period Estimates on the portfolio program can be defined with a Yearly and Quarterly pattern. * Calculation variables referring to a period will refer to a quarter, e.g. the variable Current Period From Date will return the start date of the current/estimated quarter. * Calculation Functions -> Calculated Amounts referring to a period, will refer to a quarterly value, e.g. the function Portfolio Estimates for Period will return values from the Quarterly patterns in the Default Period Estimates on the portfolio program. Estimation Frequency = Monthly * Period Estimates on business and portfolio programs are calculated, displayed and stored on a monthly basis. * Default Period Estimates on the portfolio program can be defined with a Yearly and Monthly pattern. * Calculation variables referring to a period will refer to a month, e.g. the variable Current Period From Date will return the start date of the current/estimated month. * Calculation Functions -> Calculated Amounts referring to a period, will refer to a monthly value, e.g. the function Portfolio Estimates for Period will return values from the Monthly patterns in the Default Period Estimates on the portfolio program. Estimation Frequency = Dependent on each business * This parameter is available only for life, not for P&C. * Period Estimates on business are calculated, displayed and stored depending upon each businesses Account Frequency defined in Administration condition. * If Administration Condition is not defined, or there is no Account Frequency defined in Administration condition, the Estimation Frequency will be shown as Quarterly. |
| Period Number According To The Calendar Time | * This parameter is available only for life, not for P&C. * This parameter is available to be used when Estimation Basis is Accounting Year and Estimation Frequency is Dependent on each business. * This parameter is applies to Assumed Business, Outward Cedent’s Contract, Retrocessionaire’s Participation. * When this system parameter is selected, the Account number in Administration Condition follows calendar time. * The Period number in the Period Estimate tab (both in Accounting Year view and Booking Year view) of Underwriters Estimates Condition is the same as the Account number in Administration Condition. The Account Numbers can be continuous (e.g. 1/2022, 2/2022, 3/2022, 4/2022…) or discontinuous (e.g. 1/2022, 3/2022, 4/2022, 3/2023…). * The combination of AccYr and AccPeriod in Technical Worksheet and Estimation Worksheet must exist in the Administration Condition. The Accounting Period To Date on the balances of Technical Worksheet and Estimation Worksheet will be the same as the Acct. as of Date of the same Account Period in the Administration Condition. * When running MultiGAAP Accounting Order and MultiGAAP Retrocession Order, system calculates booking amounts according to the Account Numbers in the Administration Condition. For instance, if the Account Numbers are 2/2022, 4/2022, 1/2023 in the Administration Condition, and the Booking Year and Period in the MultiGAAP Accounting Order or MultiGAAP Retrocession Order is 2022 Month 10, system creates the estimation worksheets considering the Periods in the Period Estimates that is equal to or smaller than 4/2022, e.g. 2/2022, 4/2022). |
| Change of Estimation Frequency | Changing the Estimation Frequency in an existing Multi GAAP environment will have large effect on the setup, and therefore several considerations have to be made. We would advise you to contact DXC before changing the Estimation Frequency. Some of the considerations that have to be made are as follows: * Most calculation rules can be reused with a different Estimation Frequency. However, some rules will have to be changed. For example, any rules using the Modulo functionality described in the Apply Daily Patterns chapter will have to be modified. * The Number of Periods field in the Period Estimation Rules may have to be changed. For example, if the current value is 8, i.e. 2 years in a quarterly Estimation Frequency, this will have to be changed to 24 if you still want the Estimation Item to be estimated for 2 years. * Any Quarterly Patterns defined in the Default Period Estimates on the Portfolio Program will no longer be displayed or used in calculations. New Monthly Patterns will have to be defined. * The stored Period Estimates on business or portfolio program will not change until they are recalculated. However, until the Estimates are recalculated, they will not be displayed correctly. You will therefore have to consider how you will treat estimations on periods which are no longer estimated (refer to the Booking Years to Estimate chapter below). |
Extended Estimation Period #
This Parameter is applicable oly for P&C, not for Life. In the Multi GAAP General tab it is possible to define an Extended Estimation Period. This is used by the Multi GAAP Accounting Order to allocate Accruals to the correct Occurrence year. The Extended Estimation Period is defined as number of months, and can be defined separately for each combination of Type of Business, Claim Basis and range of UW Years. When running the Multi GAAP Accounting Order, the defined Extended Estimation Period is applied to Businesses/Insured Periods/Sections with the defined Type of Business, Claim Basis and UW Year.

Add/Edit Extended Estimation Period
Define Extended Estimation Periods:
- Select System Administration on the SICS desktop
- Open System Parameter Maintenance
- Select Multi GAAP -> General
- Press the Edit button
- Right mouse click in the Extended Estimation Period area
- Select Add Extended Estimation Period from the menu
- The Add/Edit Extended Estimation Period window is opened
- Select a Claim Basis. Claim Basis is mandatory
- Select Type of Business or leave as None. When None is selected, the Extended Estimation Period applies to all Types of Business which do not have a specific Extended Estimation Period for the same Claim Basis
- Enter UW Year From and UW Year To. These fields are mandatory
- Enter Number of Months
- Press Save to save the Extended Estimation Period.
- Press OK to save the changes to the Multi GAAP General system parameters
Other Multi GAAP System Parameters #
| Field | Description |
|---|---|
| Extended Renewal Functionality: | Selected: When you renew a portfolio program, Default Period Estimate details, Loss Development Pattern, Default Pricing URL and Addition URL are copied to new validity period. When you renew an assumed business, the Loss Development Pattern is copied to the new insured period. If the assumed business is linked to a portfolio program, this link is kept on new period if the portfolio program has a validity period covering the assumed business section’s new period start date Cleared: When you renew a portfolio program, Default Period Estimate details, Loss Development, Default Pricing URL and Addition URL are not copied to new insured period. When you renew an assumed business, the Loss Development Pattern is not copied to new insured period. If the assumed business is linked to a portfolio program on current period, this link is not transferred to new period. Relevant when: In most cases, Loss Development Pattern, Default Period Estimates and the link between an assumed business section and a portfolio program are static information. Selecting this, will copy this information to new period and therefore reduce the workload. |
| Automatically Calculate Period Estimates when Inward Business Condition Changes | Selected: Period Estimates on Assumed Businesses are automatically recalculated when you: * Update any business condition which can be used in calculation of Period Estimates, e.g. Premium & Limit conditions, Deduction conditions, Profit Commission Conditions. The automatic recalculation of Period Estimates is triggered even if you do not use the updated condition in your calculation rules. E.g. even if you have no calculation of Profit Commission in your Period Estimates, an update of the Profit Commission condition will still trigger an automatic recalculation of Period Estimates. * Manually update/calculate Pricing or Adjusted Estimates. Running the Underwriters Estimation Calculation Order will NOT trigger a calculation of Period Estimates. Cleared: Period Estimates will only be calculated by pressing the calculate button in the Period Estimates or by running the Multi GAAP Recalculation Order. Relevant when: You want the make sure the Period Estimates are updated with the most recent Pricing/Adjusted estimates and the current business conditions. |
| Stop Calculation when Complete flag is set: | Selected: Estimated Items marked as Complete are not recalculated when running the Multi GAAP Recalculation Order or when you press the Calculate button in the Period Estimates. Also, they cannot be manually overwritten. Cleared: Estimated Items marked as Complete are recalculated and can be manually overwritten. Relevant when: You want to stop recalculating Estimated Items marked as Complete |
| Booking Years to Estimate | The parameter settings for the Booking Years to Estimate contain two Booking Years; Booking Year From and Booking Year To. The Booking Years that are entered in the fields represents the period for which the Estimate Items are calculated and stored on the Period Estimate window of the business |
| Period Estimate Offset Quarter | The Period Estimates offset quarter makes the system work for broken financial years, i.e. financial years that does not start at January 1 each calendar year. The input field (integer) allows for both positive and negative input Example “-3” or “1”. The offset indicates number of quarters offset the financial year is from the calendar year start date. Example of Period Estimate: Q1. If offset is 0 the system works for booking year period following calendar year. +1 means that the period estimates displays the previous Booking Year/quarter. -1 means that the period estimates displays the next quarter etc. The Multi GAAP Accrual Accounting order will select: Actual bookings from the Business Ledger with a Booking Year and Period less than or equal given Booking Year and Period. Match these bookings with period estimates belonging to correct quarter. Correct quarter is the quarter derived from the selected BYRP on the order, possibility shifted according the offset given in the system parameters. |
| Split Estimate Balances per Insured Period: | Selected: Balances created by the Multi GAAP Accounting Order and the Multi GAAP Retrocession order are split per Insured Period. Cleared: Balances created by the Multi GAAP Accounting Order and the Multi GAAP Retrocession order are NOT split per Insured Period. Relevant when: Generally, balances created by the Multi GAAP orders are not split per Insured Period, even if Insured Period is selected in Balance Split Options under Base Company Specific Settings in System Parameters. However, it may be useful to split the balances per Insured Period, e.g. if you want to mark Estimate Balances as settled when the estimation for an insured period is complete. |
| Split Estimate Balances on Liquid / Non-Liquid: | Selected: Balances created by the Multi GAAP Accounting Order and the Multi GAAP Retrocession order are split into separate balances for Liquid and Non-Liquid details. Cleared: Balances created by the Multi GAAP Accounting Order and the Multi GAAP Retrocession order creates balances including both Liquid and Non-Liquid details. Relevant when: You want Liquid and Non-Liquid details to be shown in different balances. This can be for example if you want Non-Liquid estimate balances to become settled when booked. |
| Period Estimation Calculation on Prop Outward Contracts: | Selected: Period Estimates on Proportional Outward Contracts are calculated based on the calculation rules defined in system parameters. Cleared: Estimates on Proportional OCCs come from the attached assumed businesses, ceded through the Retrocession Estimation Calculation Order.Period Estimates will show estimate bookings from the Business Ledger only, with an option to Adjust the amounts (in the Adj. column) if required. Period Estimates on Proportional OCCs cannot be calculated using the calculation rules defined in Multi GAAP system parameters. Relevant when: You want to calculate and book Period Estimates on OCC irrespective of what is being booked on the protected assumed businesses, i.e. with same functionality as on Non-Prop OCCs. |
| Closing Period: | In this parameter setting it is possible to define a Booking Year and a Booking Period. The Closing Period has impact on calculations using any of the 8 Functions/Calculated amounts for Booked Amounts for Accounting Period and Booked Amounts for Booking Period. These functions will only retrieve bookings with a Booking Year and Period equal to or prior to the defined Closing Period. Note: If the Closing Period is set as a Quarter or Half Year, and Booking Period on the transactions are Months, only bookings with a Booking Month within or prior to the closing Quarter/Half Year will be retrieved. |
| Closing Period-Booking Year: | A field for entering a year Values: A year Mandatory: No |
| Closing Period-Booking Period: | A drop down with possibility to select a Booking Period Values: Any Booking Period defined in reference table Booking Year (Code 00010) Mandatory: No |
| Closing Period-Stop Period Estimation Calculation / On Flagged Estimation Items/Periods | Selected: Estimation Items and Periods marked with Yes in the StopCalc column in Period Estimates are NOT recalculated. Cleared: There is no validation on the StopCalc flag when Period Estimates are calculated. Relevant when: You want to freeze the values on some or all Estimation Items upto a certain point. |
| Closing Period-Stop Period Estimation Calculation / On Closed Periods | Selected: Periods in Period Estimates equal to or less than the defined Last Closed Period are NOT recalculated. Cleared: All periods in Period Estimates are recalculated. Relevant when: You want to freeze the values on all Estimation Items on closed periods |
Estimation Item #
An Estimation Item will be shown within Underwriters Estimate Condition for Business Insured Period, given that the Period Estimation Rule matches Insured Period and it is classification. Estimation items are the names of items that are estimated for each individual Business & Insured Period (Portfolio Program, Assumed Business, OCC’s and Retrocessionaire Participation). Maintenance of these names takes place on this tab. A typical name of an Estimation Item will be e.g. ‘Estimated Written Premium’.
To maintain Estimation Items:
- Select System Administration on the SICS desktop
- Open System Parameter Maintenance
- Select Multi GAAP tab
- Click the Edit button
- From the pop-up menu on the Estimation Item tab you can select from a number of actions like New, Edit, View and Delete. It is also possible to move Estimation Items up or down. This order is how the Estimation Items are displayed in the Period Estimates.

Edit Multi GAAP System Parameter window,Estimation Item tab
Field Descriptions - Estimation Item
| Field | Description |
|---|---|
| Name: | Name of the item to be estimated. Different Estimation Items for various GAAP’s can be set up. However, for easier use it is recommended that the Estimation Name reflect which GAAP it belongs to. Values: Free text field. 30 positions. |
| Calc. Order: | Defines the sequence in which the Estimation Items are calculated. Values: Any number between 1 and 999 |
| Display Order: | Defines in which order the Estimation Items are displayed in Underwriters Estimate Condition for Business Insured Period, Period Estimates tab. Select an item and use the Move Up and Move Down buttons to change the order of the items. Values: A number |
| Calculate Accruals: | Selected: When Multi GAAP Accounting Order runs the system will calculate and book Accrual amounts on the Business Ledger. Cleared: No accruals will be calculated or booked on Business Ledger. Relevant when: Select this parameter when the system should to calculate and book on Business Ledger Accrual amount = Estimate amount minus Actual booked amount. |
| Is Hidden: | Selected: For users who have the option ‘Do Not Display Hidden Estimation Items’ selected in User Preferences, the Estimation Item is not displayed in the Period Estimates on the businesses. Note! Even if the Estimation Item is not displayed, it is calculated and stored as normal. Cleared: The Estimation Item is displayed in the Period Estimates for all users. Relevant when: Select this parameter if you want the Estimation Item to be hidden for some users. |
| Highlight Text: | Selected: The name of the Estimation Item is highlighted in the Period Estimates on a business. Cleared: The name of the Estimation Item is displayed in normal font/colour in the Period Estimates on a business. Relevant when: Select this parameter if you want to highlight some Estimation Items to improve readability in the Period Estimates. |
| Estimates To Be Booked: | Selected: When Multi GAAP Accounting Order runs the system will book Period Estimates from the Underwriters Estimate conditions onto the Business Ledger. Cleared: No estimate will be booked on Business Ledger. Note! If cleared the Proportional OCC’s will not be updated with the ‘as Original’ estimates from the Assumed Business. It will then be necessary to manually make estimates on the Proportional OCC’s. Relevant when: Select this parameter if Estimate amount should be booked on Business Ledger and retroceded to Proportional OCC’s. |
| Estimation Complete: | Selected: The Estimation items that are up for closing on the Period Estimates are shown on the Estimation Complete Mass Update window. Cleared: The Estimation item will not be visible on the Estimation Complete Mass Update window. Relevant when: Select this parameter for Estimate Items that shall have Estimation Complete set and that should be mass updated. |
Calculation Rules #
The rules that the system uses to calculate the Estimated Item amounts on the Period Estimates tab of the Portfolio Program and the Assumed Business are defined in this table. Calculation Rules have to be defined before creating Period Estimation Rules.
To create or edit a Calculation Rule:
- Select System Administration on the SICS desktop
- Open System Parameter Maintenance
- Click the Multi GAAP tab and then click the Edit button.
- From Calculation Rule tab select New, Edit, View or Delete from the pop-up menu. Note that it is only possible to Delete Calculation Rules that is NOT linked to a Period Estimation Rule.
- It is also possible to View the source code to see an existing calculation rule in program code.
- For reuse of existing Calculation Rule as template for new rule, the option Copy is useful.
- It is possible to turn the debug mode on and off here, see further down in this chapter for description of this functionality.

Edit Multi GAAP System Parameter window, Calculation Rule tab
Field Descriptions - Calculation Rules
| Field | Description |
|---|---|
| Name: | Used in the Period Estimation Rules table to reference this rule. Values: Free text field, 25 positions |
| Rule: | Is the actual Calculation Rule applied to Estimation Item(s) shown in Program code. Result of a calculation of the Calculation Rule is shown on Period Estimates tab on the ES-conditions as Estimation Item amount (calculated estimate). Validations: Syntax checking Values: User defined calculation edited in Calculation Rules tab |
| Description: | Is an annotation to the rule. As the Calculation Rule is a formula it is useful to describe it in “normal” language. It is strongly recommended to make a description of each Calculation Rule. Values: Free text editor. |
| Debug Mode: | Option to check the correctness of the Calculation Rule. It can be used to debug your Calculation Rule. Selected: When calculation of Underwriters Estimate Conditions takes place the system will do a debug and user can follow the calculations step-by-step. Cleared: No debug takes place in calculation of Underwriters Estimate Conditions, Period Estimates tab. Relevant when: This setting is usually used during system set up to check calculations. |
Set Up Calculation Rules #
Calculation Rules are set up using program code. To ease the work of writing Calculation Rules the Multi GAAP module presents a number of predefined variables, operators, and features. Usually they are enough to specify the Calculation Rules. For security reasons the access to other classes of the system is restricted.
You can enter your Calculation Rule either by using variables, features, and operators from the pop-up menu or by typing program code. If you use the Menu your entry is transformed into valid program code.
When you have entered a Calculation Rule you can perform a syntax check. Select the respective item from the right-mouse button menu. Note that if the syntax check is ok this does not mean that the rule will work. The system does not perform a semantic check.
Because there are some shortcuts that you can use in the Calculation Rules it is usually not pure programming code that is entered. With the View Source option you can see the generated program code. You can of course enter program code without using the shortcuts.
Using Searchable Calculation rules #
The variables, functions are categorized in different Sub categories based on their nature of calculating different values.
The Calculation rule categories are available in an expandable tree view and this tree can be expanded to the lowest level. To search for a specific Calculation rule, you can input three or more characters into the find field. Based on the text that is input, the Calculation rule categories that contain calculation rules that match the search text are listed.
A minimum of three characters should be entered in order to start finding matching items.
For example, when a text of ‘Premium’ is entered in the find field, all the Calculation rule categories that contain calculation rules having the word ‘Premium’ as a whole word or part of a word are listed in an expanded tree view
The user can then narrow down the search by entering more text and the search results will be narrowed down accordingly. Upon getting the desired calculation rule, the user can right click on it and can insert the code for calculation and for the calculation rules that requires selection, a pop up window will be prompted with list of details.
Using Variables #
There are a number of predefined variables. Their values depend on the context in which the Calculation Rule is executed. The context might be the business / section, the quarter or the Estimation Item. In general if a variable is referenced for which no value is entered in the conditions the returned value will be 0. For a detailed description, refer to the Appendix.
Using Operators #
The usual operators for calculation and comparison are available as buttons.
Using Features #
The features supplied by the system are the most powerful part of the Calculation Rules. This is mainly because the behaviour of the rules can change depending on a number of parameters, e.g. the number of the quarters for which the rule is currently executed and the pattern values specified on the Portfolio Program. For a detailed description of the available features, refer to the Appendix.
Comment your Calculation Rule #
It is recommended to comment the Calculation Rules and this can be done in two ways:
- You can use the description field for comments.
- You can use the ordinary programming comments. This is done by using double quotes (") at the beginning and at the end of the text. It might also be useful to know that this can also be used to deactivate parts of the Calculation Rule without deleting it.
Using the Option; Debug Mode #
When testing Calculation Rules it can be useful to track down which values the variables and features have during the execution of the rule. This is done when using the debug mode. The debug mode is set for each Calculation Rule individually. You can switch a Calculation Rule to Debug Mode even if you are not in edit mode by using the pop-up menu.
Note! The debug mode is not persistent nor does it affect other users working with the system. The debug mode applies only for your machine for the current session.
Each time a Calculation Rule in Debug Mode is executed same dialog boxes with information about the current values pop-up. You can continue the execution in Debug Mode or end it.
Edit Multi GAAP System Parameter window, edit Calculation Rule window
The format of the shown value is the ordinary programming language. Refer to the Smalltalk documentation for a detailed description.
Examples #
To follow the examples in this section you have to know which of the described features result in which code fragments. This is because in this section only the program code is shown (but without transforming the shortcuts like if then else end into program code).
The first example distributes the EPI linear to the estimated periods.
%premiumEPIAmount / %noOfPeriods
Two variables are used in this rule. See section below.
The second example uses the EPI amount entered in Limit- and Premium Condition of the Business. It also uses a pattern from the Portfolio Program to calculate the Estimated Item amount. The pattern is called ‘Written Premium’.
( %premiumEPIAmount *
( #FUNC getPortfolioEstimatesForYear: %bookingYear estimationItem: ‘Written Premium’) *
( #FUNC getPortfolioEstimatesForYear: %bookingYear period: %bookingPeriod estimationItem: ‘Written Premium’) ) / 10000
The booking quarter and year is used to reference the pattern. This is because the numbering of the portfolio defaults is like 01/2003, 02/2003, 03/2003, 04/2003, 01/2004 etc. which is reflected by the variables %bookingPeriod and %bookingYear.
It is assumed that the percentages of the pattern are specified like 60, 10, 10, 20 etc. to represent 60%, 10%, 10%, 20% etc. Therefore the result of the calculation has to be divided by 10000.
The third example illustrates how more than one value from the condition screens can be used:
( ( %premiumEPIAmount *
( #FUNC getPortfolioEstimatesForYear: %bookingYear estimationItem: ‘Written Premium’) *
( #FUNC getPortfolioEstimatesForYear: %bookingYear period: %bookingPeriod estimationItem: ‘Written Premium’) *
(%deductionCommissionPercentage: ‘COMM’ “Commission”) / 10000 ) +
( (%deductionCommissionAmount: ‘COMM’ “Commission”) *
( #FUNC getPortfolioEstimatesForYear: %bookingYear estimationItem: ‘Written Premium’) *
( #FUNC getPortfolioEstimatesForYear: %bookingYear period: %bookingPeriod estimationItem: ‘Written Premium’) ) ) * -1
In the first part of the rule the same pattern as for the first example is used to distribute the Commission in the same way as the Premium. A Commission Percentage is therefore multiplied by the Estimated Premium. Note that if this condition were not entered the first part would be zero. The second part of the rule applies the pattern directly to the Commission amount. This can also be zero if not entered. The total calculated amount is multiplied by -1 because it is a deduction item. Otherwise the booking result would also be positive.
The last example used the calculated premium to calculate the Commission. The problem with the calculation is that if the Estimated Premium is overwritten on the Period Estimate tab the calculation will not regard the overwritten amount. This is because it selects the EPI directly from the condition screen and the pattern values from the Portfolio Program. It does not regard the overwritten premium on the Period Estimate tab. In the next example the value for the Written Premium is selected directly from the Period Estimate tab. It calculates the Commission based on the actually entered amount of Estimated Written Premium.
( #FUNC getEstimatedAmountForEstimationItem: ‘Written Premium’) *
(%deductionCommissionPercentage: ‘COMM’ “Commission”)
Using Calculation Rules for Different Estimation Methods #
There are different methods of applying an Estimation Pattern. The Multi GAAP module is not fixed to specific methods or Estimation Bases. Instead you can create your own methods by specifying the Calculation Rules accordingly.
Note! The Estimation Basis that can be set in the System Parameters does not affect the application of the patterns.
Applying Yearly Patterns #
You can use the functionality Portfolio Estimates for Year to access the yearly pattern of a Portfolio Program.
( #FUNC getPortfolioEstimatesForYear: %bookingYear )
Depending on the inception date of the business this will return the first yearly pattern of the Portfolio Program in the first 1-4 quarters or 1-12 months. The second, third etc. yearly pattern is return for 4 quarters or 12 months each.
You could also use %accountingYear as a parameter
( #FUNC getPortfolioEstimatesForYear: %accountingYear )
Since %accountingYear always returns the same value you would get the same pattern value each time this Calculation Rule is executed. This might not be what you expected if you use the Accounting Year. If you are using a Quarterly Estimation Frequency, you may want to reference the first yearly pattern in quarter 1-4, the second yearly pattern in quarter 5-8 etc. no matter what the inception date is. To do this use the following rule:
( #FUNC getPortfolioEstimatesForYear: ( %accountingYear +
( ( ( %accountingPeriod / 4 ) - 0.25 ) truncated ) ) )
The Truncate a Number functionality is used to add 1 to the accounting year every 4 quarters. In the first 4 quarters the term on the second line returns 0. The next 4 quarters it returns 1 and so on.
Apply Quarterly or Monthly Patterns #
The quarterly or monthly pattern values are accessed using the feature Portfolio Estimates for Periods. Do not be confused about the name of the feature that appears in the calculation rule window. Although it is called getPortfolioEstimatesForYear the system knows that it has to pick the quarterly pattern values because of the specified periods.
Note! The below example assumes that Estimation Frequency in system parameter is set to Quarterly. In this example only the quarterly pattern is used without the yearly pattern values. Refer to the examples above to see how to use both quarterly and yearly patterns.
This first example shows a method of applying the estimation pattern that is according to the booking quarter and year. If this method is used for a business that incepts 1stApril 2000 then the second default period estimate of year 2000 is applied to the first estimated quarter.
If you want to apply the quarterly patterns in an accounting method style you can use the following formula. Note that the year is specified as in one of the examples above.
( #FUNC getPortfolioEstimatesForYear: ( %accountingYear +
((( %accountingPeriod / 4 ) - 0.25 ) truncated ))
period: %accountingPeriod )
Using this calculation rule the pattern is applied by shifting the first quarter of the pattern to the first quarter of the business.
Apply Daily Patterns #
Although you cannot specify patterns on a daily basis you can however apply patterns only partly to one quarter and partly to the next according to the start and end date of the quarter (pro rata). Hence the following examples are especially useful for business that do not incept at the beginning of a quarter (e.g. 1st January, 1stApril, 1st July, 1st October). The next Calculation Rules always refer to an Estimation Item called ‘Written Premium’. Of course you can replace this with any estimation you want or use the default one.
Note! The examples below assume that Estimation Frequency in system parameter is set to Quarterly.
( ( ( #FUNC moduloOf:
( #FUNC positiveDaysBetween: ( %insuredPeriodFrom ) and: ( #FUNC day: 1 month: 1 year: (%insuredPeriodFrom year) ) )
factor: 91.25 ) / 91.25 )
- ( #FUNC getPortfolioEstimatesForAccountingPeriod:
(%accountingPeriod +1) estimationItem: ‘Written Premium’) ) +
( ( 1 - ( ( #FUNC moduloOf:
( #FUNC positiveDaysBetween: ( %insuredPeriodFrom ) and: ( #FUNC day: 1 month: 1 year: (%insuredPeriodFrom year) ) )factor: 91.25 ) / 91.25 ) ) *
( #FUNC getPortfolioEstimatesForAccountingPeriod: %accountingPeriod estimationItem: ‘Written Premium’) )
This formula retrieves pattern values in an Accounting Year style. It retrieves two quarters in case the Business does not incept at the beginning of a quarter. It calculates the part of the first pattern value that “belongs” to the first quarter (second part of the formula) of the Business and the part of the second pattern value that “belongs” to this quarter (first part of the formula). The quarter is assumed to have 91.25 days.
Modulo feature is used in this example. This is to calculate the offset between the inception date and the 1stof January correctly even if the Business incepts in the 2nd, 3rd or 4thquarter. You could use the start date of the Portfolio Program, instead of the user-defined date for the 1st of January of the Inception Year. But the Portfolio Program usually starts at the 1stof January. Note that it does not matter in which year the portfolio starts. This difference is eliminated by modulo feature.
Note! If you want to use this formula you have to set up your pattern very carefully. This is because a Business could refer up to 5 pattern values. Therefore the total of the percentages could be greater than 100%. To avoid this you could only refer to the first 4 quarters in a circular way. See the next example:
( ( ( #FUNC moduloOf:
( #FUNC positiveDaysBetween: ( %insuredPeriodFrom ) and:
( #FUNC day: 1 month: 1 year: (%insuredPeriodFrom year) ) )
factor: 91.25 ) / 91.25 ) *
( #FUNC getPortfolioEstimatesForYear: %accountingYear period: (%accounting- Period + 1) estimationItem: ‘Written Premium’) ) +
( ( 1 - ( ( #FUNC moduloOf:
( #FUNC positiveDaysBetween: ( %insuredPeriodFrom ) and:
( #FUNC day: 1 month: 1 year: (%insuredPeriodFrom year) ) )
factor: 91.25 ) / 91.25 ) ) *
( #FUNC getPortfolioEstimatesForYear: %accountingYear period: %accounting-Period estimationItem: ‘Written Premium’) )
Note! A different feature for selecting the pattern values is used. The parameter %accountingPeriod goes from 1 to the number of estimated quarters. But the feature getPortfolioEstimatesForYear reduces it to a value less than 4 by applying modulo (this is done internally). This is the reason why the pattern values are referenced in a circular way. You could also use %bookingPeriod as parameter.
( ( ( #FUNC moduloOf:
( #FUNC positiveDaysBetween: ( %insuredPeriodFrom ) and: ( #FUNC day: 1 month: 1 year: (%insuredPeriodFrom year) ) )
factor: 91.25 ) / 91.25 ) *
( #FUNC getPortfolioEstimatesForYear: %accountingYear period: (%bookingPeriod + 1) estimationItem: ‘Written Premium’) ) +
( ( 1 - ( ( #FUNC moduloOf:
( #FUNC positiveDaysBetween: ( %insuredPeriodFrom ) and: ( #FUNC day: 1 month: 1 year: (%insuredPeriodFrom year) ) )
factor: 91.25 ) / 91.25 ) ) *
( #FUNC getPortfolioEstimatesForYear: %accountingYear period: %bookingPeriod estimationItem: ‘Written Premium’) )
Note! In this example the %bookingPeriod is used in conjunction with %accountingYear. The only difference is for Business that do not incept on the 1stof January. For those the referenced pattern value in the first estimated quarter might not be the first pattern value.
Starting from these examples you could easily create your own method of applying estimation pattern and write a Calculation Rule for it.
Period Estimation Rules #
Definition on which Estimation Items that will appear on which Level of Business is maintained on the Period Estimation Rule tab. Definition on which rules that will be used for the different kinds of business and more details regarding the estimation will also need to be set up herein.

Edit Multi GAAP System Parameter window, Period estimation Rule tab
To edit Period Estimation Rules:
- Select System Administration on the SICS desktop
- Click the System Parameter Maintenance icon.
- Click the Multi GAAP tab.
- Click the Edit button.
- Select the Period Estimation Rules tab and select an existing rule.
- From the pop-up menu on the Period Estimation Rule tab you can select from a number of actions like New, Edit, View and Delete.
- Select New from the pop-up menu and the Create Period .

Edit Multi GAAP System Parameter window, edit Period estimation Rule
Field Descriptions - Period Estimation Rules
| Field | Description |
|---|---|
| Period Estimate Name: | Title of the Period Estimation Rule, Period Estimation Rule will inherit same name as the Estimation Item. Values: All Estimation Items already created on the Estimation Item tab. |
| Number of Periods: | The number of estimation periods that applies for the business. It shall reflect the number of quarters/months in the Default Estimates of the Portfolio Program. If e.g. 12 are entered as Number of Periods estimates will be calculated for 12 periods in the Period Estimates tab of Underwriters Estimate conditions. Values: Numeric, 3 positions. |
| Valid Date Range: | Date range for which calculation rule is valid. The Validity Period Start Date of the Portfolio Program is matching the From Date on the Period Estimate Rule (recommended). The Period Start Date of the Business shall be within the Valid Date Range. Values: Date format |
| Calculation Rule: | Calculation used when calculating values displayed on Period Estimates tab in Underwriters Estimate conditions. Values: All Calculation Rules already created on the Calculation Rule tab. |
| Accounting Basis: | Possible with different Period Estimation Rules for different Accounting Basis. The Accounting Basis has to match the Accounting Basis of the Business, which is specified in the Administration Conditions. Select <None> if the Period Estimation Rule should match all different types of Accounting Basis. Note! If the value <None> is specified on the business, only <None> for the Period Estimation Rule will match this. Matching values determines validation; select the Accounting Basis that is wanted for the Period Estimate Rule to be valid. Validations: Checks against values in Administration Condition. Values: Accounting Year, Occurrence Year, Underwriting Year or <None>. |
| Accounting Basis Premium: | Similar as Accounting Basis above. Matching values determines validation; select the Accounting Basis Premium that is wanted for the Period Estimate Rule to be valid. Validations: Checks against values in Administration Condition. Values: <None>, Clean Cut and Run Off. |
| Accounting Basis Claim: | Similar as Accounting Basis Premium above. Matching values determines validation; select the Accounting Basis Claim that is wanted for the Period Estimate Rule to be valid. Validations: Checks against values in Administration Condition. Values: <None>, Clean Cut and Run Off. |
| True Up Match: | Entry Code Group, which is used in the true up match, for calculation of the Accrual booking = Estimate booking against the Actual booking. The bookings with Entry Codes listed in the selected Entry Code Groups are used when Multi GAAP Accounting Order calculates Accruals. Values: User defined in Entry Code Group Category ‘MULTI-GAAP Accounting’. Entry Code Groups for the True Up Match are set up in the Entry Code Maintenance window. All Entry Code Groups that can be used for the True Up Match must be defined in the Multi GAAP Accounting Entry Code Group Category. Unlimited number of Entry Code Groups can be defined in this category. |
| Estimation Entry Code: | This is the Entry Code that the Multi GAAP Accounting Order will use as output when calculated Estimated Item amount is booked as Estimate. Validations: Booking of Estimated amount will only take place if Estimates To Be Booked is Selected on the properties for the applicable Estimation Item. If Estimates To Be Booked is Cleared this field is disabled and no Estimate booking will take place by the order. Values: Valid Entry Code defined in Entry Code Maintenance. |
| Accrual Entry Code: | This is the Entry Code that the Multi GAAP Accounting Order will use as output when calculated Accrual amount is booked as Accrual (estimate). Validations: Booking of Accrual amount will only take place if Calculate Accruals is Selected on the properties for the applicable Estimation Item. If Calculate Accruals are Cleared this field is disabled and no Accrual booking will take place by the order. Values: Valid Entry Code defined in Entry Code Maintenance. Note! For different Period Estimation Rules with the same Estimation Item name use the same Entry Codes. It is possible that one can encounter problems on Proportional OCC’s and Retrocessionaire’s, because the true up on that Level of Business is using the Entry Code defined in the Period Estimation Rule and the Estimation Item name. |
| Accrual/Estimate Split: | Selected: Accruals or estimates will be split into different Accounting Classification and/or Occurrence Years using the rule defined in Split Rule. Cleared: General rules will apply for setting Accounting Classification and Occurrence Year on the accruals and estimates on this Estimated Item. Relevant when: You want to apply specific rules for splitting the accruals or estimates on this Estimated Item into different Accounting Classifications or different Occurrence Years. |
| Split Rule: | The rule used to split accruals or estimates into different Accounting Classifications and/or Occurrence Years Values: AC / Orig UW Year Split (P&C only), AC Split - Business, AC Split - Business / Occ. Year Split, Acc. Classification / Occ. Year Split, Accounting classification Split, Estimate AC Split Prior 12M (Life only), Estimate AC Split Prior 3M (Life only), Estimate AC Split Prior Month (Life only), Estimate AC Split Prior Year (Life only), Occ Yr Split from Book Yr (P&C only), Occurrence Year Allocation (P&C only), Occurrence Year Split Validations: Only enabled if Accrual/Estimate Split is selected Mandatory: When_Accrual/Estimate Split_ is selected Functional Impact: Multi GAAP Accounting Order and Multi GAAP Retrocession Order Refer to the SICS P&C and SICS Life User Guides for detailed description of the different split rules. |
| Split Group: | The Entry Code Group used as basis for the Accrual/Estimate Split Values: All Entry Code Groups defined in Entry Code Group Category Multi GAAP Accounting. Validations: Only enabled if Accrual Split is selected, and Split Rule is AC / Orig UW Year Split, AC Split - Business / Occ. Year Split, Acc. Classification / Occ. Year Split, Accounting Classification Split, Estimate AC Split Prior 12M, Estimate AC Split Prior 3M, Estimate AC Split Prior Month, Estimate AC Split Prior Year, Occ Yr Split from Book Yr or Occurrence Year Split Mandatory: When Accrual Split is selected, and Split Rule is AC / Orig UW Year Split, AC Split - Business / Occ. Year Split, Acc. Classification / Occ. Year Split, Accounting Classification Split, Estimate AC Split Prior 12M, Estimate AC Split Prior 3M, Estimate AC Split Prior Month, Estimate AC Split Prior Year, Occ Yr Split from Book Yr or Occurrence Year Split Functional Impact: Multi GAAP Accounting Order and Multi GAAP Retrocession Order |
| Estimation Level: | Selected: Estimated Item appears in the Underwriters Estimate conditions and Period Estimation tab of Portfolio Programs, Assumed Business, OCC’s, Retrocessionaire or any combination of these options. Cleared: Estimate will NOT appear in the Underwriters Estimate conditions and Period Estimation tab of Portfolio Programs, Assumed Business, OCC’s, Retrocessionaire or any combination of these options. Relevant when: If Estimated Item is only valid for one or some Level of Business. Portfolio Defaults means that specifically values on Period Estimates Default tab on Portfolio Program are considered. |
| Classification (tab): | A classification for each category that is in the list can be selected. Select Type and select Edit from pop-up menu, eventually double-click the Type to see list for Available and Selected values. Mandatory Classification Types: Type of Business, Main Class of Business, Class of Business and Base Company. Rest of the types are optional. Values: Selectable values refer to the applicable Reference Data Type in Reference Data Maintenance. Functional Impact: The Business shall have an exact match or be a subset of classifications matching the values in the Period estimates Classifications. When no values are selected it means that all values are valid. |
Set up Classification #
The Classification, Accounting Basis Premium, and Accounting Basis Claim are used in the Period Estimation Rule to find matching Business (Portfolio Programs, Assumed Business, OCC’s, Retrocessionaire’s). The system performs a subset match to determine if a Period Estimation Rule matches a Business. If the Classification of the Business including the Accounting Basis is a subset or is equal to the Classification of the Period Estimation Rule, they match hence the respective Estimation Item is displayed in Underwriters Estimates, Period Estimates tab. Accounting Basis <None> or blank matches any values.
In general, when you use the same Estimation Item name for different Period Estimation Rules you should set up the Classification of these rules very carefully. The Classification of two Estimation Rules with the same name should not overlap as this leads to confusion. It is strongly recommended that you are very careful when using the value <None> for a classification category and for the Accounting Basis. If you try to create Period Estimation Rules with overlapping Classifications the system issues a warning message. If you overrule this error it is impossible to add a currency to the Period Estimate tab of a Business as the system recognizes an overlap. This is for safety, as the system cannot tell which Period Estimation Rule of the overlapping to use.
You can have Additional Classification Types on your Business. For matching purposes they are only taken into account if they are defined on both the Business and the Estimation Rule. If they are only defined on the Business they are ignored while matching Business and Estimation Rule.
Set up Estimation Level #
The Estimation Level determines on which Level of Business a certain Estimation Item is shown. There are five options that can be chosen:
-
Portfolio: The item appears on the Period Estimate tab of a Portfolio Program.
-
Portfolio Defaults: The item appears on the Estimation Defaults tab of a Portfolio Program.
-
Business: The item appears on the Period Estimate tab of an Assumed Business.
-
Outward Cedents Contract: The item appears on the Period Estimate tab of an OCC.
-
Retrocessionaire: The item appears on the Period Estimate tab of a Retrocessionaire.
-
Calculate on Retrocessionaire: Enabled only when flag Retrocessionaire (above) is selected.
Selected: Period Estimates are calculated directly on Retrocessionaire on the basis of calculation rules defined in system parameter.
Cleared: Period Estimates on the Retrocessionaire is calculated as the Period Estimate amounts on the OCC multiplied with the Retrocessionaire’s share
Estimation Level should be set up with care. Firstly, distinguish between items that should only be estimated on Portfolio Program, only on Assumed Business or on both. Use the Portfolio and Business Check boxes accordingly. Secondly, if there are items that are the basis for Calculation Rules, these should be Portfolio Defaults.
In addition, determine which of the Estimation Items that should be shown on the OCC and Retrocessionaire. Usually OCC and Retrocessionaire are selected at the same time. By selecting Estimation Level OCC means that this item is shown on an OCC. If check box is NOT selected, the item is not shown. This does not mean that the estimations cannot be found on the Business Ledger of the OCC, as it is NOT possible to prevent this by setting the Estimation Level. To prevent estimations from being retroceded use the flag within Entry Code Properties.
An Accounting Entry Code is usually set up together with the Estimation. The Entry Code is used for different things depending on the Estimation Level. On all levels except Portfolio Defaults it is used for booking the estimates. If only Portfolio Defaults is selected the Accounting Entry Code can be left blank because it is of no use to the defaults. On the OCC and Retrocessionaire it is also used to sum-up the (estimate) figures from the Business Ledger to display them on the Period Estimates tab. If you have a Period Estimation Rule where Business level is the only box that is selected, this estimate will be booked on the ledger of the Assumed Business. It will also be transferred to the OCC’s Business Ledger ‘As Original’ and to Retrocessionaire’s via the Retrocession Estimation Calculation Order, but in this case estimates cannot be seen on the Period Estimates tab for the retro business.
Sometimes it can be useful to set up Period Estimation Rules for OCC and Retrocessionaire only. This is the case when, for example, there are manual estimation bookings on the Assumed Business that are transferred to the OCC. If the Entry Code of the manual booking is not one of the Entry Codes of the Period Estimation Rules, this booking cannot be seen on the Period Estimates tab.
Sub Calculations #
The Sub Calculations are rules that can be called by the Calculation Rules. This can be very useful if a calculation rule is very complex and large. By using the feature If…Then…Else…End in a calculation rule it is possible to call different Sub Calculations to be performed. The Sub Calculations cannot be used directly in a Period Estimation Rule but needs to go via a Calculation Rule. But they can be used as parameters in the system generated features.
Edit Multi GAAP System Parameter Window, Create Sub Calculations
All the Variables, Operators and Functions that can be used in the Calculation Rules are also available in the Sub Calculation Rules.
The only difference to the Calculation Rules is that an Identifier needs to be specified for the Sub Calculations.
Field Descriptions - Sub Calculations
| Field | Description |
|---|---|
| Name: | Used in the Period Estimation Rules table to reference this rule. Values: Free text field, 25 positions |
| Identifier: | To reference the Sub Calculation, can be used from the pop-up menu in the Calculation Rules window in Edit mode and selecting Add sub calculation… from the pop-up menu. Values: Free text field 35 positions |
Multi GAAP Life Cycle #
In general the Multi GAAP System Parameters should be set up before businesses that are affected by them are created.
To set up and maintain the Multi GAAP System Parameters;
- Create initial set of Estimation Items, Period Estimation Rules and Calculation Rules.
- Create / renew Portfolio Programs (and set up Period Estimation Defaults).
- Create / renew Assumed Business, OCC’s, and Retrocessionaire’s.
- Repeat step 2 and 3 for each underwriting year.
- Create new Period Estimation Rules and Calculation Rules.
- Repeat step 2 - 5 for each Portfolio Program.
Note! It is strongly recommended that you never change a Period Estimation Rule or a Calculation Rule that affects existing business. You should always limit the valid date range of your change by creating a new Period Estimation Rule and by using the ‘from’ and ’to’ dates. Never change a Period Estimation Rule that has a valid from date that is in the past. Never change existing Calculation Rules when they are used by Period Estimation Rules that are in effect. Always create a new Calculation Rule. Copy the old rule to the new one and change it with a new validity period.
Changes to the Multi GAAP system parameter affect the Period Estimation tabs (in the Underwriters Estimates window) of the different levels of business involved and changes should be made very carefully. Changes to Period Estimation Rules and to Calculation Rules can affect existing business in different ways:
- The estimate is no longer valid for a business because of a restricted classification.
- A new estimate is valid for a business because of a changed classification
- The Period Estimates are no longer valid because of a changed Calculation Rule.
- More / less Period Estimates are available because the number of periods for a Period Estimation Rule has changed.
Changes to the Multi GAAP System Parameters do not normally update the business automatically. This has to be done manually or by running the Retrocession Recalculation order. After changing a Period Estimation Rule and / or Calculation Rule that effects existing business, every business must be checked and updated accordingly.
To refresh Period Estimates according to new parameters on Assumed Business, Portfolio Programs, and Non-Proportional OCC’s:
- Click the button and select the Period Estimate tab.
- Switch to edit mode.
- Remove every currency and recreate them again. This will take the changed System Parameters into account.
- Click Save.
Note! Removing the estimate currency/ies will also delete all your adjustments made to the estimations. If you have just changed the calculation rule it is enough to click the Calculate button.
To refresh Period Estimates for Proportional OCC’s and Retrocessionaire’s:
- Click the button and select the Period Estimate tab.
- Switch to edit mode.
- Click Calculate
- Click Save.
Note! In this case your adjustments will be preserved as long as the Estimation Item is still valid and the number of quarters remains the same.
Appendix #
Variables #
Non-categorised variables #
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Accounting Period | %accountingPeriod |
Number | Column header in Period Estimates tab when in Accounting Year view mode. | This variable starts with a value of 1 in the first estimated period. It increases by 1 for each estimation period. In the last period, %accountingPeriod is equal to %noOfPeriods. |
| Accounting Year | %accountingYear |
Number | Column header of in Period Estimates tab when in Accounting Year view mode. | The Accounting Year variable is equal to the inception year. It has the same value for all Period Estimates. |
| Booking Period | %bookingPeriod |
Number | Column header of in Period Estimates tab when in Booking Year view mode. | The value of this variable is according to the calendar period. |
| Booking Year | %bookingYear |
Number | Column header of in Period Estimates tab when in Booking Year view mode. | - |
| Claim Basis | %claimBasis |
Alphanumeric | Claim Condition | Values: NONEBEGINOFCONSTRCAUSATIONCLMMADELORAAFTLORABEFLOSOCCURMANIFESTOCCURNOTIFIEDOCCURWITHSUNSETOCCURWITHOUTSUNRISKATT |
| Is Assumed Business Calculation | %isAssumedBusinessCalculation |
Boolean | - | This variable is set to Yes if the calculation is performed on an Assumed Business. Otherwise it is No. |
| Is Booking Exist | (%isBookingExist: '<code>' "<name>") |
Boolean | - | This variable returns true if any bookings on Entry Codes within the referenced Entry Code Group exists on an Accounting Year and Period corresponding to the Accounting Period in the Period Estimates. It will return true also if the bookings add up to zero. if no bookings exists, the variable will return false. Note that if you have monthly period estimates, but bookings are made on an accounting period covering several months, the bookings are linked to the first month in the that period. E.g. if the booking is made with a quarterly accounting period, the variable will return true only on the first month in the quarter, for the other 2 months it will return false. |
| Is Estimation Complete | (%is EstimationComplete: 'Estimation Item') |
Boolean | - | This variable returns ’true’ if the selected Estimation item is marked as ‘Complete’ on the business section, otherwise it returns ‘false’ |
| Is Portfolio Program Calculation | %isPortfolioProgramCalculation |
Boolean | - | This variable is set to Yes if the calculation is performed on a Portfolio Program Otherwise it is No. |
Date related variables #
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Closing Date | %closingDate |
Date | - | Last day in the month/quarter of the Default Booking Period in Booking Terms for the relevant Base Company. Taken from the Extended Booking Terms if that exists and has Multi GAAP Accounting Order selected as Order types, otherwise taken from the General Booking Terms |
| Current Period From Date | %currentPeriodFromDate |
Date | - | Start date of a period adjusted according to inception date of the business |
| Current Period To Date | %currentPeriodToDate |
Date | - | End date of a period adjusted according to inception date of the business |
| Current Year | %currentYear |
Number | - | Current year refers to the system date. |
| Insured Period Duration | %insuredPeriodDuration |
Number | Insured Period tab | Number of days that the business is valid |
| Insured Period From | %insuredPeriodFrom |
Date | Insured Period tab | Start date of the insured period. |
| Insured Period To | %insuredPeriodTo |
Date | Insured Period tab | End date of the insured period. |
| Launching Date | %launchingDate |
Date | Insurable Object with Type = Space | The Launching Date of an Insurable Object with Type = Space. Returns 31.12.9999 if blank |
| Portfolio Program Effective Period Duration | %portfolioProgramEffectivePeriodDuration |
Number | Insured Period tab | Number of days that the business is valid |
| Portfolio Program Effective Period From | %portfolioProgramEffectivePeriodFrom |
Date | Insured Period tab | Start date of the insured period. |
| Portfolio Program Effective Period To | %portfolioProgramEffectivePeriodTo |
Date | Insured Period tab | End date of the insured period. |
| Todays Date | %todaysDate |
Date | - | This variable contains the actual system date. It returns a different value every day. |
Premium related variables #
They all originate from the Limit- and Premium Condition:
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Premium EPI Amount | %premiumEPIAmount |
Decimal | Premium and Limit condition | Premium amount our share entered on the premium and limit condition in the same currency as the estimation currency. |
| Flat Premium Amount | %flatPremiumAmount |
Decimal | Premium and Limit condition of Non-Proportional business | - |
| Minimum Premium | %minimumPremium |
Decimal | Premium and Limit condition of Non-Proportional business, instalment tab | This variable is only valid for Non-Proportional business (it returns 0 for other types of business). It returns the Minimum Premium Our Share that is in the same currency as the estimation currency. |
| Deposit Premium | %depositPremium |
Decimal | Premium and Limit condition of Non-Proportional business, instalment tab | This variable is only valid for Non-Proportional business (it returns 0 for other types of business). It returns the Deposit Premium Our Share that is in the same currency as the estimation currency. |
Variables related to Total Amount Booked #
Both Variables originate from the Limit- and Premium/Installment Condition:
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Gross | %grossTotalAmountBooked |
Decimal | Premium and Limit condition of Non-Proportional business, instalment tab | This variable is only valid for Non-Proportional business (it returns 0 for other types of business). It retrieves the value from ‘Total Amount Booked’ - ‘Gross’ field in Installment Tab. |
| Net | %netTotalAmountBooked |
Decimal | Premium and Limit condition of Non-Proportional business, instalment tab | This variable is only valid for Non-Proportional business (it returns 0 for other types of business). It retrieves the value from ‘Total Amount Booked’ - ‘Net’ field in Installment Tab. |
Variables related to Total Amount Not Booked #
Both Variables originate from the Limit- and Premium/Installment Condition:
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Gross | %grossTotalAmountNotBooked |
Decimal | Premium and Limit condition of Non-Proportional business, instalment tab | This variable is only valid for Non-Proportional business (it returns 0 for other types of business). It retrieves the value from ‘Total Amount Not Booked’ - ‘Gross’ field in Installment Tab. |
| Net | %netTotalAmountNotBooked |
Decimal | Premium and Limit condition of Non-Proportional business, instalment tab | This variable is only valid for Non-Proportional business (it returns 0 for other types of business). It retrieves the value from ‘Total Amount Not Booked’ - ‘Net’ field in Installment Tab. |
Variables related to deduction amounts #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| Brokerage Amount | - | Decimal | Deduction condition | Amount of deduction type Brokerage as defined in the Reference Data maintenance. |
| Commission Amount | - | Decimal | Deduction condition | Amount of deduction type Commission as defined in the Reference Data maintenance. |
| Others Amount | - | Decimal | Deduction condition | Amount of deduction type Others as defined in the Reference Data maintenance. |
Variables related to deduction percentages #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| Brokerage Percentage | - | Decimal | Deduction condition | Percentage of deduction type Brokerage as defined in the Reference Data maintenance. |
| Commission Percentage | - | Decimal | Deduction condition | Percentage of deduction type Commission as defined in the Reference Data maintenance. |
| Others Percentage | - | Decimal | Deduction condition | Percentage of deduction type Others as defined in the Reference Data maintenance. |
Variables referring to Pricing and Adjusted Estimates #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| Underwriters Pricing Estimates | - | Decimal | Pricing Estimates tab under the Underwriters Estimates tab | The Estimation Items that have set to Yes in the Multi GAAP column defined in the Underwriters Estimate tab of the System Parameters will be available for use as a variable. |
| Underwriters Adjustment Estimates | - | Decimal | Adjusted Estimates tab under the Underwriters Estimates tab | The Estimation Items that have set to Yes in the Multi GAAP column defined in the Underwriters Estimate tab of the System Parameters will be available for use as a variable. |
IBNR Variables #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| Financial | %financialIbnrFactor |
Decimal | Upload from external .csv file. Upload performed from Ultimate Loss Ratio Import from desktop | Ultimate IBNR factor created by an Actuary. Can be uploaded to the Period Estimates tab of a Portfolio Program level by using this variable. |
| Statistical | %statisticalIbnrFactor |
Decimal | Upload from external .csv file. Upload performed from Ultimate Loss Ratio Import from desktop | Ultimate IBNR factor created by an Actuary. Can be uploaded to the Period Estimates tab of a Portfolio Program level by using this variable. |
Loss Ratio Variables #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| Financial | %financialLossRatio |
Decimal | Upload from external .csv file. Upload performed from Ultimate Loss Ratio Import from desktop | Ultimate Loss Ratio factor created by an Actuary. Can be uploaded to the Period Estimates tab of a Portfolio Program level by using this variable. |
| Statistical | %statisticalLossRatio |
Decimal | Upload from external .csv file. Upload performed from Ultimate Loss Ratio Import from desktop | Ultimate Loss Ratio factor created by an Actuary. Can be uploaded to the Period Estimates tab of a Portfolio Program level by using this variable. |
Currency Variables #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| Estimation Item Currency | %estimationItemCurrency |
Currency | Period Estimates tab | Possible to reference an estimation currency |
| Main Currency | %mainCurrency |
Currency | Limit/Premium conditions | Main currency of an Assumed Business |
| Main Currency of Portfolio Program | %mainCurrencyOfPortfolioProgram |
- | - | Main currency of a Portfolio Program |
No Claims Bonus / Profit Commission Variables #
| Variable Name | Code Name | Data type | Location in SICS | Description |
|---|---|---|---|---|
| No Claim Bonus | %noClaimBonusPercentage |
Decimal | Rebate Condition on Non-Proportional business | No Claims Bonus percentage entered |
| Profit Commission | %profitCommissionPercentage |
Decimal | Profit Commission Condition on Assumed Business | Profit Commission percentage entered |
| Sliding Scale Maximum Profit Commission | %slidingScaleMaximumProfitCommissionPercentage |
Decimal | Profit Commission Condition on Proportional Assumed Business | Maximum Sliding Scale Profit Commission percentage entered |
| Sliding Scale Minimum Profit Commission | %slidingScaleMinimumProfitCommissionPercentage |
Decimal | Profit Commission Condition on Proportional Assumed Business | Minimum Sliding Scale Profit Commission percentage entered |
| Sliding Scale Maximum Result | %slidingScaleMaximumResultPercentage |
Decimal | Profit Commission Condition on Proportional Assumed Business | Maximum Result percentage entered |
| Sliding Scale Minimum Result | %slidingScaleMinimumResultPercentage |
Decimal | Profit Commission Condition on Proportional Assumed Business | Minimum Result percentage entered |
Deposit Condition Variables #
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Deposit Loss Calculation Method | %depositLossCalculationMethod |
Alphanumeric | Deposit Cond, Loss tab | Values:PCTORGDEPPCTLOSSPORTPCTLOSSRES |
| Deposit Loss Interest on Deposit | %depositLossInterestOnDeposit |
Percent | Deposit Cond, Loss tab | Interest On Deposit % |
| Deposit Loss Percentage | %depositLossPercentage |
Percent | Deposit Cond, Loss tab | Percentage |
| Deposit Premium Calculation Method | %depositPremiumCalculationMethod |
Alphanumeric | Deposit Cond, Loss tab | Values:PCTORGDEPPERCENTAGEPCTPREMPORTPCTPREMRES |
| Deposit Premium Interest on Deposit | %depositPremiumInterestOnDeposit |
Percent | Deposit Cond. Premium tab | Interest On Deposit % |
| Deposit Premium Percentage | %depositPremiumPercentage |
Percent | Deposit Cond. Premium tab | Percentage |
Portfolio Condition Variables #
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Portfolio Loss Entry Calculation Method | %portfolioLossEntryCalculationMethod |
Alphanumeric | Portfolio Cond, Loss tab | Values: PCTORGDEPPCTLOSSRESLIABILITYORIGANDRES |
| Portfolio Loss Entry Percentage | %portfolioLossEntryPercentage |
Percent | Portfolio Cond, Loss tab | % |
| Portfolio Loss Withdrawal Calculation Method | %portfolioLossWithdrawalCalculationMethod |
Alphanumeric | Portfolio Cond, Loss tab | Values:PCTORGDEPPCTLOSSRES LIABILITYORIGANDRES |
| Portfolio Loss Withdrawal Percentage | %portfolioLossWithdrawalPercentage |
Percent | Portfolio Cond. Loss tab | % |
| Portfolio Premium Entry Calculation Method | %portfolioPremiumEntryCalculationMethod |
Alphanumeric | Portfolio Cond. Premium tab | Values:PCTORGDEPPERCENTAGE ORIGANDRESPCTPREMRESTEMPORISDIVISIONLIABILITY |
| Portfolio Premium Entry Percentage | %portfolioPremiumEntryPercentage |
Percent | Portfolio Cond. Premium tab | % |
| Portfolio Premium Withdrawal Calculation Method | %portfolioPremiumWithdrawalCalculationMethod |
Alphanumeric | Portfolio Cond. Premium tab | Values:PCTORGDEP PERCENTAGEORIGANDRESPCTPREMRESTEMPORISDIVISIONLIABILITY |
| Portfolio Premium Withdrawal Percentage | %portfolioPremiumWithdrawalPercentage |
Percent | Portfolio Cond. Premium tab | % |
Reserve Condition Variables #
| Variable Name | Code Name | Data Type | Location in SICS | Description |
|---|---|---|---|---|
| Reserve Loss Calculation Method | %reserveLossCalculationMethod |
Alphanumeric | Reserve Cond, | Values:ORIGINAL |
| Reserve Loss Percentage | %reserveLossPercentage |
Percent | Reserve Cond, | Percentage |
| Reserve Premium Calculation Method | %reservePremiumCalculationMethod |
Alphanumeric | Reserve Cond, | Values:ORIGINALPERCENTAGEDIVISIONTEMPORIS |
| Reserve Premium Percentage | %reservePremiumPercentage |
Percent | Reserve Cond. | Percentage |
Operators #
| Operator | Description |
|---|---|
+ |
Plus |
- |
Minus |
* |
Multiply |
/ |
Divide |
= |
Equal to |
~= |
Not equal to |
> |
Larger than |
< |
Smaller than |
>= |
Larger than or equal to |
<= |
Smaller than or equal to |
( |
Start bracket |
) |
End bracket |
| ` | ` |
&? |
And (Can be used in IF_THEN_ELSE functions) |
Functions - Calculated Amounts #
| Function Name | Booked Amounts for Accounting Period |
| Code Name | (#FUNC getBookedAmountsForAccountingPeriodForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve bookings from the Business Ledger with an AccYr and AccPeriod equal to the accounting period in the Period Estimates, i.e. the period shown when Estimation Basis is Accounting Year. For bookings with an AccPeriod with a wider span than the estimated periods (e.g. half yearly or yearly), the bookings will be uploaded to the estimated period which is equal to the first month or quarter in the AccPeriod. Bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’ and ‘Based on Period End Rate’. Only bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Estimate bookings and claim Bookings which is not transferred to ledger are not considered. Applicable to Assumed Business and outward Non Proportional Treaties. |
| Function Name | Booked Amounts for Accounting Period Booked Period Rates |
| Code Name | (#FUNC getBookedAmountsForAccountingPeriodBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Amounts for Accounting Period, but bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. |
| Function Name | Booked Amounts for Accounting Period Accumulated |
| Code Name | (#FUNC getBookedAmountsForAccountingPeriodAccumulatedForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve bookings from the Business Ledger with an AccYr and AccPeriod less than or equal to the accounting period in the Period Estimates, i.e. the period shown when Estimation Basis is Accounting Year. For bookings with an AccPeriod with a wider span than the estimated periods (e.g. half yearly or yearly), the bookings will be uploaded to the estimated period which is less than or equal to the first month or quarter in the AccPeriod. Bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’and ‘Based on Period End Rate’. Only bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Estimate bookings and claim Bookingswhich is not transferred to ledger are not considered. Applicable to Assumed Business and outward Non Proportional Treaties. |
| Function Name | Booked Amounts for Accounting Period Accumulated Booked Period Rates |
| Code Name | (#FUNC getBookedAmountsForAccountingPeriodAccumulatedBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Amounts for Accounting Period Accumulated, but bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. |
| Function Name | Booked Amounts for Booking Period |
| Code Name | (#FUNC getBookedAmountsForBookingPeriodForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve bookings from the Business Ledger with a Booking Year Period equal to (or within) the booking period in the Period Estimates, i.e. the period shown when Estimation Basis is Booking Year. Bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’and ‘Based on Period End Rate’. Only bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Estimate bookings and claim Bookings which is not transferred to ledger are not considered. Applicable to Assumed Business and outward Non Proportional Treaties. |
| Function Name | Booked Amounts for Booking Period Booked Period Rates |
| Code Name | (#FUNC getBookedAmountsForBookingPeriodBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Amounts for Booking Period, but bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. |
| Function Name | Booked Amounts for Booking Period Accumulated |
| Code Name | (#FUNC getBookedAmountsForBookingPeriodAccumulatedForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve bookings from the Business Ledger with a Booking Year Period less than or equal to the booking period in the Period Estimates, i.e. the period shown when Estimation Basis is Booking Year. Bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’and ‘Based on Period End Rate’. Only bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Estimate bookings and claim Bookings which is not transferred to ledger are not considered.Applicable to Assumed Business and outward Non Proportional Treaties. |
| Function Name | Booked Amounts for Booking Period Accumulated Booked Period Rates |
| Code Name | (#FUNC getBookedAmountsForBookingPeriod-AccumulatedBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Amounts for Booking Period Accumulated, but bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. |
| Function Name | Booked Amounts for Original Accounting Period |
| Code Name | (#FUNC getBookedAmountsForOriginalAccountingPeriodForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve bookings from the Business Ledger with an Original AccYr and Original AccPeriod equal to the accounting period in the Period Estimates, i.e. the period shown when Estimation Basis is Accounting Year. For bookings with an Original AccPeriod with a wider span than the estimated periods (e.g. half yearly or yearly), the bookings will be uploaded to the estimated period which is equal to the first month or quarter in the Original AccPeriod. Bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’ and ‘Based on Period End Rate’. Only bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Estimate bookings and claim Bookings which is not transferred to ledger are not considered. Applicable to outward Proportional Treaties. |
| Function Name | Booked Amounts for Original Accounting Period Booked Period Rates |
| Code Name | (#FUNC getBookedAmountsForOriginalAccountingPeriodBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Amounts for Original Accounting Period, but bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. |
| Function Name | Booked Amounts for Original Accounting Period Accumulated |
| Code Name | (#FUNC getBookedAmountsForOriginalAccountingPeriodAccumulatedForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve bookings from the Business Ledger with an Original AccYr and Original AccPeriod less than or equal to the accounting period in the Period Estimates, i.e. the period shown when Estimation Basis is Accounting Year. For bookings with an Original AccPeriod with a wider span than the estimated periods (e.g. half yearly or yearly), the bookings will be uploaded to the estimated period which is less than or equal to the first month or quarter in the Original AccPeriod. Bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’and ‘Based on Period End Rate’. Only bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Estimate bookings and claim Bookingswhich is not transferred to ledger are not considered. Applicable to outward Proportional Treaties |
| Function Name | Booked Amounts for Original Accounting Period Accumulated Booked Period Rates |
| Code Name | (#FUNC getBookedAmountsForOriginalAccountingPeriodAccumulatedBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Amounts for Original Accounting Period Accumulated, but bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. |
| Function Name | Booked Estimate Amounts for Accounting Period |
| Code Name | (#FUNC getBookedEstimateAmountsForAccountingPeriodForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve estimate bookings from the Business Ledger with an AccYr and AccPeriod equal to the accounting period in the Period Estimates, i.e. the period shown when Estimation Basis is Accounting Year. For estimates bookings with an AccPeriod with a wider span than the estimated periods (e.g. half yearly or yearly), the bookings will be uploaded to the estimated period which is equal to the first month or quarter in the AccPeriod. Estimates bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’ and ‘Based on Period End Rate’. Only estimates bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Estimate bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Applicable to Assumed Business and Outward Prop and Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Accounting Period Booked Period Rates |
| Code Name | (#FUNC getBookedEstimateAmountsForAccountingPeriodBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Estimate Amounts for Accounting Period, but estimate bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. Applicable to Assumed Business and Outward Prop and Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Accounting Period Accumulated |
| Code Name | (#FUNC getBookedEstimateAmountsForAccountingPeriodAccumulatedForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve estimate bookings from the Business Ledger with an AccYr and AccPeriod less than or equal to the accounting period in the Period Estimates, i.e. the period shown when Estimation Basis is Accounting Year. For estimate bookings with an AccPeriod with a wider span than the estimated periods (e.g. half yearly or yearly), the bookings will be uploaded to the estimated period which is less than or equal to the first month or quarter in the AccPeriod. Estimate bookings in different currency than the estimated currency are converted to the estimated currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’ and ‘Based on Period End Rate’. Only estimate bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Estimate bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Applicable to Assumed Business and outward Prop/ Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Accounting Period Accumulated Booked Period Rates |
| Code Name | (#FUNC getBookedEstimateAmountsForAccountingPeriodAccumulatedBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Estimate Amounts for Accounting Period Accumulated, but estimate bookings in different currency than the estimated currency are converted to the estimated currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. Applicable to Assumed Business and outward Proportional/Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Booking Period |
| Code Name | (#FUNC getBookedEstimateAmountsForBookingPeriodForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve estimate bookings from the Business Ledger with a Booking Year Period equal to (or within) the booking period in the Period Estimates, i.e. the period shown when Estimation Basis is Booking Year. Bookings in different currency than the estimated currency are converted to the period estimates currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’ and ‘Based on Period End Rate’. Only estimate bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Estimate bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Applicable to Assumed Business and outward Prop/ Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Booking Period Booked Period Rates |
| Code Name | (#FUNC getBookedEstimateAmountsForBookingPeriodBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Estimate Amounts for Booking Period, but estimate bookings in different currency than the estimated currency are converted to the period estimates currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. Applicable to Assumed Business and outward Prop/ Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Booking Period Accumulated |
| Code Name | (#FUNC getBookedEstimateAmountsForBookingPeriodAccumulatedForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | This function will retrieve estimate bookings from the Business Ledger with a Booking Year Period less than or equal to the booking period in the Period Estimates, i.e. the period shown when Estimation Basis is Booking Year. Estimates bookings in differ-ent currency than the estimated currency are converted to the period estimates currency using the current Daily Rate. However, if Accounting/Currency system parameter ‘Use Inception Rate Accounting’ is selected, conversion is done using Daily Rate valid at Insured Period Start Date, or Period Rate for the period prior to Insured Period Start Date, depending on parameters ‘Based on Daily Rate’ and ‘Based on Period End Rate’. Only estimate bookings on closed worksheets and with Entry Codes included in the referenced Entry Code Group will be uploaded. Estimate bookings with a Booking Year & Period higher than any Closing Period set in Multi GAAP General system parameters will not be uploaded. Applicable to Assumed Business and outward Prop/ Non Proportional Treaties. |
| Function Name | Booked Estimate Amounts for Booking Period Accumulated Booked Period Rates |
| Code Name | (#FUNC getBookedEstimateAmountsForBookingPeriodAccumulatedBookedPeriodRatesForEntryCodeGroup '<code>' "<name>") |
| Return Data Type | Decimal |
| Arguments | <code> and <name> is the code and name of the referenced Entry Code Group. Available Entry Code Groups are those within Entry Code Group Category ‘Multi GAAP Calculations’ |
| Description | Same as Booked Estimate Amounts for Booking Period Accumulated, but estimate bookings in different currency than the estimated currency are converted to the period estimates currency using the Period End Rate for the period corresponding to the Booking Year/Period on the booking detail. Applicable to Assumed Business and outward Prop/ Non Proportional Treaties. |
| Function Name | Estimated Item Amount For Accounting Period |
| Code Name | (#FUNC getEstimatedAmountForEstimationItem: '<name>' accountingPeriod: %accountingPeriod ) |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced item in single quotes |
| Description | This functionality retrieves the estimation amount from an Estimation Item that can be selected. By using -X after %accountingPeriod it is possible to retrieve estimation amounts for earlier periods. |
| Function Name | Estimated Item Amount |
| Code Name | ( #FUNC getEstimatedAmountForEstimationItem: '<name>') |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | Instead of performing a calculation rule that belongs to another Estimation Item you can reference the amount from the period estimate tab directly. To do so use this functionality. The advantage of using this functionality is that you can also execute calculation. |
| Function Name | Portfolio Adjusted Amount for Currency |
| Code Name | ( #FUNCgetPortfolioProgramAdjustedAmountForEstimationItem: '<name 1>'accountingPeriod: accountingPeriodcurrency: '<name 2>' ) |
| Return Data Type | Decimal |
| Arguments | <name 1> is the name of the referenced Estimation Item in single quotes. <name 2> is the name of the currency referenced in single quotes. |
| Description | By using this functionality it is possible to get the estimation amount in a specified currency for an entire portfolio by referencing an adjusted Estimation Item from the Period Estimates tab of the Portfolio Program. |
| Function Name | Portfolio Adjusted Amount |
| Code Name | ( #FUNCgetPortfolioProgramAdjustedAmountForEstimationItem: '<name>'accountingPeriod: %accountingPeriod ) |
| Return data type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | By using this functionality it is possible to get the estimation amount for an entire portfolio by referencing an adjusted Estimation Item from the Period Estimates tab of the Portfolio Program. |
| Function Name | Portfolio Aggregated Amount for Booking Period |
| Code Name | ( #FUNCgetPortfolioProgramAggregatedAmountForEstimationItem: '<name>'bookingYear: %bookingYearbookingPeriod: %bookingPeriod) |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | By using this functionality it is possible to get the estimation amount for an entire portfolio by referencing an Estimation Item from the Period Estimates tab of the Portfolio Program. For each period, the amount is captured from the booking period on the Portfolio Program equal to the booking period on the Assumed Business. Booking period here means the period shown in the Period Estimates when Estimation View = Booking Year |
| Function Name | Portfolio Aggregated Amount for Currency for Booking Period |
| Code Name | ( #FUNCgetPortfolioProgramAggregatedAmountForEstimationItem: '<name 1>'bookingYear: %bookingYearbookingPeriod: %bookingPeriodcurrency: '<name 2>' ) |
| Return Data Type | Decimal |
| Arguments | <name 1> is the name of the referenced Estimation Item in single quotes. <name 2> is the name of the currency referenced in single quotes. |
| Description | By using this functionality it is possible to get the estimation amount in a specified currency for an entire portfolio by referencing an Estimation Item from the Period Estimates tab of the Portfolio Program. For each period, the amount is captured from the booking period on the Portfolio Program equal to the booking period on the Assumed Business. Booking period here means the period shown in the Period Estimates when Estimation View = Booking Year. |
| Function Name | Portfolio Aggregated Amount for Currency |
| Code Name | ( #FUNCgetPortfolioProgramAggregatedAmountForEstimationItem: '<name 1>'accountingPeriod: %accountingPeriodcurrency: '<name 2>' ) |
| Return Data Type | Decimal |
| Arguments | <name 1> is the name of the referenced Estimation Item in single quotes. <name 2> is the name of the currency referenced in single quotes. |
| Description | By using this functionality it is possible to get the estimation amount in a specified currency for an entire portfolio by referencing an Estimation Item from the Period Estimates tab of the Portfolio Program. For each period, the amount is captured from the accounting period on the Portfolio Program equal to the accounting period on the Assumed Business. Accounting period here means the period shown in the Period Estimates when Estimation View = Accounting Year |
| Function Name | Portfolio Aggregated Amount |
| Code Name | ( #FUNCgetPortfolioProgramAggregatedAmountForEstimationItem: '<name>'accountingPeriod: %accountingPeriod ) |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | By using this functionality it is possible to get the estimation amount for an entire portfolio by referencing an Estimation Item from the Period Estimates tab of the Portfolio Program. For each period, the amount is captured from the accounting period on the Portfolio Program equal to the accounting period on the Assumed Business. Accounting period here means the period shown in the Period Estimates when Estimation View = Accounting Year |
| Function Name | Portfolio Converted Currency Adjusted Amount |
| Code Name | ( #FUNCgetPortfolioProgramConvertedCurrencyAdjustmentAmountForEstimationItem: '<name>'accountingPeriod: %accountingPeriod ) |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | If a converted currency has been added to the Period Estimates tab of a Portfolio Program this functionality will return the total converted adjusted amount for a referenced Estimation Item converted (again) to the currency of the estimation of each Assumed Business. |
| Function Name | Portfolio Converted Currency Amount for Booking Period |
| Code Name | ( #FUNCgetPortfolioProgramConvertedCurrencyAmountForEstimationItem: '<name>'bookingYear: %bookingYear )bookingPeriod: %bookingPeriod ) |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | If a converted currency have been added to the Period Estimates tab of a Portfolio Program this functionality will return the total converted amount for a referenced Estimation Item converted (again) to the currency of the estimation of each Assumed Business. For each period, the amount is captured from the booking period on the Portfolio Program equal to the booking period on the Assumed Business. Booking period here means the period shown in the Period Estimates when Estimation View = Booking Year. |
| Function Name | Portfolio Converted Currency Amount |
| Code Name | ( #FUNCgetPortfolioProgramConvertedCurrencyAmountForEstimationItem: '<name>'accountingPeriod: %accountingPeriod ) |
| Return Data Type | Decimal |
| Arguments | <name> is the name of the referenced Estimation Item in single quotes. |
| Description | If a converted currency have been added to the Period Estimates tab of a Portfolio Program this functionality will return the total converted amount for a referenced Estimation Item converted (again) to the currency of the estimation of each Assumed Business. For each period, the amount is captured from the accounting period on the Portfolio Program equal to the accounting period on the Assumed Business. Accounting period here means the period shown in the Period Estimates when Estimation View = Accounting Year |
| Function Name | Portfolio Estimates for Accounting Period (default) |
| Code Name | ( #FUNC getPortfolioEstimatesForAccountingPeriod: <period> ) |
| Return Data Type | Decimal |
| Arguments | <period> is the period. The period counts from the first period on the period defaults tab continuously to the last period. |
| Description | This functionality returns quarterly or monthly pattern values of the default Estimation Item. The difference to the functionality Portfolio Estimates for Period (default) is that you can use parameter values greater than 4 (for quarterly patterns) and 12 (for monthly patterns). In this case the functionality automatically retrieves the pattern value from the next year. |
| Function Name | Portfolio Estimates for Accounting Period. |
| Code Name | ( #FUNC getPortfolioEstimatesForAccountingPeriod: <period> estimationItem: '<name>') |
| Return Data Type | Decimal |
| Arguments | <period> is the period. The period counts from the first period on the period defaults tab continuously to the last period. <name> is the name of the referenced Estimation Item in single quotes. |
| Description | This functionality returns quarterly or monthly pattern values of the default Estimation Item. The difference to the functionality Portfolio Estimates for Period is that you can use parameter values greater than 4 (for quarterly patterns) and 12 (for monthly patterns). In this case the functionality automatically retrieves the pattern value from the next year. |
| Function Name | Portfolio Estimates for Period (default) |
| Code Name | ( #FUNC getPortfolioEstimatesForYear: <year> period: <period>) |
| Return Data Type | Decimal |
| Arguments | <period> is the period in the respective year <year> is the year that should be referenced. |
| Description | This functionality works similar to Portfolio Estimates for Period but it refers to the current Estimation Item. |
| Function Name | Portfolio Estimates for Period |
| Code Name | ( #FUNC getPortfolioEstimatesForYear: <year> period: <period> estimationItem: '<name>') |
| Return Data Type | Decimal |
| Arguments | <period> is the period in the respective year <year> is the year that should be referenced <name> is the of the referenced item in single quotes |
| Description | This functionality is similar to the Portfolio Estimates for Year. Instead it selects values from the quarterly or monthly pattern display list. So you have to supply the feature with a year and a quarter/month as parameter. |
| Function Name | Portfolio Estimates for Year (default) |
| Code Name | ( #FUNC getPortfolioEstimatesForYear: <year> ) |
| Return Data Type | Decimal |
| Arguments | <year> is the year that should be referenced |
| Description | In case you want to retrieve a pattern value that has the same name as the current Estimation Item (which is the case when you set the estimation level accordingly) you can use this feature instead of Portfolio Estimates for Year. |
| Function Name | Portfolio Estimates for Year |
| Code Name | ( #FUNC getPortfolioEstimatesForYear: <year> estimationItem: '<name>') |
| Return Data Type | Decimal |
| Arguments | <year> is the year that should be referenced <name> is the of the referenced item in single quotes. |
| Description | This functionality retrieves an amount from the yearly pattern display list of the attached portfolio. A year has to be specified to this feature. Also you have to specify the name of the pattern. Refer to the examples to see how this feature can be used. |
| Function Name | Premium Optional Amount |
| Code Name | ( #FUNC getPremiumAmountForOptionCode: '<type>' "<name>" ) |
| Return Data Type | Decimal |
| Arguments | <type> is the type of premium that should be retrieved <name> is the name of the premium. |
| Description | To reflect the very flexible way of entering premium in SICS in the calculation rule this functionality exists. It can retrieve all kinds of premiums that are defined in the system. You have to supply this functionality with code of the premium. The system presents you a list with all existing code where you can select the one that you wish to use. |
Date functions #
| Name | Days between Dates |
| Code Name | ( #FUNC daysBetween: ( <higherDate> ) and: ( <lowerDate> ) ) |
| Return Data Type | Number |
| Arguments | <higherDate> is the higher date from which the <lowerDate> is subtracted. |
| Description | This functionality calculates the number of days that lie between two dates. Depending on which date is supplied as the first and which date is supplied as the second argument this feature returns a positive or negative value. |
| Name | Days between Dates (always +ve) |
| Code Name | ( #FUNC positiveDaysBetween: ( <date 1> ) and: ( <date 2> ) ) |
| Return Data Type | Number |
| Arguments | <date1> and <date2> are two variables or terms that represent date values. |
| Description | Same as above but always returns a positive value. |
| Name | User defined Date |
| Code Name | ( #FUNC day: <day> month: <month index> year: <year> ) |
| Return Data Type | Date |
| Arguments | <day> is a number specifying a day <month index> represent the month where 1 is January, 2 is February etc. <year> is a number representing the year |
| Description | This functionality can be used to create new date values. A day, month and year is supplied. |
| Name | Add days to a date |
| Code Name | ( #FUNC addDays: <anInteger> toDate: <aDate> ) |
| Return Data Type | Date |
| Arguments | <anInteger> is a number <adate> is a date |
| Description | This functionality can be used to create new date values. |
| Name | Subtract days from a date |
| Code Name | ( #FUNC subtractDays: <anInteger> fromDate: <aDate> ) |
| Return data type | Date |
| Arguments | <anInteger> is a number <adate> is a date |
| Description | This functionality can be used to create new date values. |
| Name | The day of a date |
| Code Name | ( <date> dayOfMonth ) |
| Return data type | Number |
| Arguments | <date> is a variable or term of type Date |
| Description | For a given date this functionality returns a number that indicates which day of the month it is. |
| Name | The month of a date |
| Code Name | ( <date> monthIndex ) |
| Return data type | Number |
| Arguments | <date> is a variable or term of type date. |
| Description | Returns the index of the respective month. |
| Name | The year of a date |
| Code Name | ( <date> year ) |
| Return data type | Number |
| Arguments | <date> is a variable or term of type date |
| Description | Returns the year of a date value. |
Number functions #
| Name | Convert to Integer |
| Code Name | ( <aNumber> ) asInteger |
| Return data type | Number |
| Arguments | <aNumber> is a decimal |
| Description | This functionality converts a number to the nearest integer number. |
| Name | Exponent function |
| Code Name | ( #FUNC raise: ( <value> ) toPower: ( <exponent> )) |
| Return data type | Decimal |
| Arguments | <value> and <exponent> are numbers (integer or decimal). Both can be entered as fixed values, variables, functions or sub calculations |
| Description | Raises the Value to the power of the Exponent. The calculation follows the general mathematical rules for exponent functions. However, note that 0 raised to power of 0, and 0 raised to power of a negative value, will both be calculated as 0. |
| Name | Fraction of a Number |
| Code Name | ( <aNumber> ) fractionPart |
| Return data type | Decimal |
| Arguments | <aNumber> is a decimal |
| Description | Returns the fraction part of a number. |
| Name | Max |
| Code Name | ( <arg1> max: <arg2> ) |
| Return data type | Decimal |
| Arguments | <arg1> and <arg2> are decimals. |
| Description | Returns the greater of two values. |
| Name | Min |
| Code Name | ( <arg1> min: <arg2> ) |
| Return data type | Decimal |
| Arguments | <arg1> and <arg2> are decimals. |
| Description | Returns the smaller of two values. |
| Name | Modulo |
| Code Name | ( self moduloOf: <value> factor: <factor> ) |
| Return data type | Decimal |
| Arguments | <value> and <factor> are numbers (integer or decimal). <value> must be non-negative. <factor> must be positive. |
| Description | Returns the modulo of the given value using the supplied factor. |
| Name | Rounding function |
| Code Name | ( ( <aNumber> ) roundToDigits: <Decimal Places> ) |
| Return data type | Decimal |
| Arguments | <aNumber> is a decimal <DecimalPlaces> is a number |
| Description | Rounds a number to the supplied number of digits. |
| Name | Truncate a Number |
| Code Name | ( <aNumber> ) truncated |
| Return data type | Number |
| Arguments | <aNumber> is a decimal |
| Description | Applied to a number this functionality returns the integer part of the number. The fraction part is truncated. |
Perform Calculation #
| Name | Perform Calculation |
| Code Name | ( #FUNC performCalculation: '<crule>' ) |
| Return data type | Decimal |
| Arguments | <crule> is the name of the called calculation rule. |
| Description | If there is an already defined calculation that you want to use in another calculation you can use this functionality. It is meant as a shortcut. It would also be possible to repeat the (text of the) calculation again. Note therefore that the called calculation is performed in the context of the calling calculation. Any variables used in the called calculation will have a value related to the calling calculation. |
| Name | Perform Calculation (with Periods) |
| Code Name | ( #FUNC performCalculation: '<crule>' periodOffset: <period>) |
| Return Data Type | Decimal |
| Arguments | <crule> is the name of the rule that should be called <period> is the offset to the current period. |
| Description | This functionality is basically the same as the above. But you can additionally specify a period offset. Without a period offset the called calculation is performed with the current period. The offset is applied to the current period. |
User defined fields #
| Name | Business layout (up to 5) |
| Code Name | |
| Return data type | Boolean, Currency, Date, Decimal, Integer, Monetary amount, Percentage |
| Arguments | - |
| Description | There are five user-defined tabs available on business level and it is possible to set up references to Multi GAAP there. |
Calculation Rule features #
IF..THEN..ELSE..END #
| Feature Name | IF..Then..Else..End |
| Code Name | (#IF ( <condition> )#THEN<command1>#ELSE<command2>#END) |
| Return Data Type | Depends on return date type of <command1> or <command2> respectively. |
| Arguments | <condition> is a Boolean exclickion <command1> is one or more commands that are executed if <condition> evaluates to true <command2> is one or more commands that are executed if <condition> evaluates to false |
| Description | This functionality works like known from other programming languages. A condition is checked. Depending on the result (true or false) the Then branch or the Else branch is executed. |
Includes… #
| feature Name | Includes… |
| Code Name | ( #FUNC objectCollection: #( <object1> <object2> <etc..> ) includes: <anObject> ) |
| Return Data Type | To be used with If…Then…Else…End… |
| Arguments | - |
| Description | This functionality can be used with Variables that can return more than one value, for example Accounting Period. |