Configuring Client Conditions
In Temenos Payments, client condition products are created to configure client conditions.
Client Condition Product
The user can configure a client condition product. To perform this, do the following actions:
- Go to Admin Menu > Payments > Payment Hub > Bank Operations Configuration > Client Conditions > Client Products. The list of client condition products are displayed on the upper pane. The lower pane enables the user to view and edit the record selected from the list.
- To view a record, click
.
- To amend or edit a record, click
.
- To reverse a record, click
.
- To view a record, click
- To create a new client condition product, click
.
- In the Client Condition Product field, enter the name of the product.
- Enter the description of the product in the required language.
- Validate and commit the product.
Customer Groups
Customers can be grouped using one or more fields available in the CUSTOMER application. To group customers, follow the steps provided in the below sections:

A bank can choose to group customers based on their attributes.
To group customers,
- Go to Admin Menu > Payments > Payment Hub > Bank System Administration > Static Data > Company Properties.
- Set the value of the EnableCustomerGrouping field to 'Y'.

Customers can be grouped using one or more attributes from the CUSTOMER application.
By default, the system is configured to group customers using the customer’s sector, target and residence. Based on requirement, the bank can add or remove customer attributes to be used for grouping. The grouping attributes can be edited for the POR.TRANSACTION record in the Condition Priority screen.
To access this screen, go to Admin Menu > Framework Parameter > Core > Condition Priority.
Field | Description |
---|---|
Apps Allowed | Indicates the applications whose fields can be used for grouping. This field is read-only and defaulted to the CUSTOMER application. |
Priority Item | Indicates the fields used for grouping the customers. The value in this field must be available in the CUSTOMER application. |
Prty Validation | The values configured in this field are used to enrich data in the Grouping Conditions screen. |

The rules used for grouping customers can be configured from the Gen Conditions screen. Multiple rules can be configured, where the values for each of the fields defined in the Condition Priority screen determines the group of each customer .
To access this screen, go to Admin Menu > Payments > Payment Hub > Bank Operations Configurations > Customer Grouping Conditions.
The customer group ID configured in this screen can be attached in the Business Line or Customer Group field in the Client Charge screen.
Field | Description |
---|---|
@ID | Indicates the customer group ID |
Description | Specifies the description of the customer group |
Item | Specifies the customer attributes defined in the Condition Priority screen |
Priority | Specifies the priority of the customer attributes defined in the Condition Priority screen |
Value | Defines the value against each item to define the group. For example, if the Item field is set as customer’s residence and the Value field is set as 'GB', then all customers with residence GB fall under this group. |
Client Conditions or Agreements
The user can configure a client condition. To perform this, do the following actions:
- Go to Admin Menu > Payments > Payment Hub > Bank Operations Configurations > Client Conditions > Client Agreements. The list of client conditions defined in the system are displayed on the upper pane.
- To view a record, click
.
- To amend or edit a record, click
.
- To reverse a record, click
.
- To create a new client condition product, click
.
- In Client Condition field, enter the name of the product.
- Enter the details related to the product configuration in the mandatory fields.
- Validate and commit the product.

The user can configure client specific features using various combination of input attributes in the Client Agreements page. Client conditions are configured for each company, hence, Company ID is mandatory. To perform this, do the following actions:
- Click the Client Condition tab.
- Enter the required details in the following fields:
Field Description Client Condition Product Indicates a valid client product to create client agreement. The client product is configured as an output of Product Determination module.Source Product Indicates the source where the payment originates. Configure a valid source or ‘*’. - A client product can be associated with multiple sources.
- The bank can configure different client products for different sources or one client product for a source group.
In batch transactions, the business line of the parent is used for debit side of child transactions. This is applicable for fields, such as Business Line, Client ID, Account Number, and Account CurrencyBusiness Line / Customer Group When customer grouping is enabled, this field indicates the group ID to which the customer belongs. This customer group must be a valid entry existing in the CUSTOMER.CHARGE application. Entries in CUSTOMER.CHARGE are built based on the rules defined in the Gen Conditions application.
When customer grouping is disabled, this field indicates the business line to which the customer belong. This is linked to the business line captured in the customer configurations (Target field). The user can configure a valid customer group or business line or ‘*’ in this field.
Client ID Indicates the customer ID created in Temenos Transact. - Configure a valid customer ID or ‘*’.
- If a client ID is configured, the client condition becomes specific for that customer.
Account Number Indicates the account number that is debited or credited based on the payment. - Configure a valid account number or ‘*’.
- If an account number is configured, the client condition becomes specific for the account.
Account Currency Indicates the currency of the account that is debited or credited based on the payment. Configure a valid currency code or ‘*’. Account Company ID Indicates the company to which the account belongs. Configure a valid company ID or ‘*’. Start Date Indicates the date from which the client condition record is active. Multiple records can be available for different activation dates. - Only one record needs to be active at a time.
- Defaults to current date.
End Date Indicates the date till which the client condition record is active. Multiple records can be available for different activation dates. - Only one record needs to be active at a time.
- Needs to be future dated

The bank users can configure multiple output attributes for each client condition. These attributes influence the payment processing by using the payment engine. The configurable output attributes are as follows.
Enter the required details in the following fields:

Field | Description |
---|---|
Language | Language in which the statement and advice is generated for the correspondent bank.
The default value is blank. |
Dr Statement Format Name | Debit account statement format.
|
Cr Statement Format Name | Credit account statement format.
|

Field | Description |
---|---|
Billing Indicator |
If the Billing Indicator is set as Y, the calculated charges are stored as informational charge in Temenos Payments. |

Field | Description |
---|---|
Separate Charge Booking | Charge booking preference of the customer.
|

Field | Description |
---|---|
Charge Posting in Details | Preference of the customer when multiple charges are applicable for the payment.
|

Field | Description |
---|---|
VAT on Principal |
|
VAT on Charge | Indicates whether the customer has to pay VAT on the charge amount. Configure one of the following values:
|
Tax ID | ID of the tax record for tax calculation. The TAX records are configured in the system by using the Temenos Transact TAX table, which has the tax rate. |
Tax Type | Tax condition group for tax calculation. |
- Customer grouping for tax is maintained using the TAX.GEN.CONDITION application.
- Customer group and Tax ID mapping is maintained using TAX.TYPE.CONDITION application.

Field | Description |
---|---|
Non STP Flag | Configure whether the payment for the customer is processed by using STP or manual intervention. Select one of the following values:
|
STP Limit | Configure a threshold amount in home currency.
This check is performed when non-STP is set as N (STP for all transactions). |

Field | Description |
---|---|
Non STP FX Flag | Indicates whether to process payments for the customer involving FX in STP or manual intervention (non-STP).
|
STP FX Limit |
Indicates the limit when Non STP FX Flag is set as N.
|

Field | Description |
---|---|
Debit special instructions | Special instructions for the Operator during debit. |
Credit special instruction | Special instructions for the Operator during credit. |

Field | Description |
---|---|
Currencycode | Configure a valid currency code or ‘*’. |
Incoming Lead Time | Incoming lead time used for date calculation. |
Outgoing Lead Time | Outgoing lead time used by Routing and Settlement. |

Field | Description |
---|---|
Debit float | Number of days to adjust the debit value date. |
Credit float | Number of days to adjust the credit value date. |

Field | Description |
---|---|
Cust Status Report On Settlement |
Indicates whether a Customer Status Report (CSR) is generated for each received and processed initiation file (where the settlement date of the bulk in file are equal to the current business date). Configure one of the following values:
This setting overrides the corresponding setting in Source Settings.
|
Tran ACKNACK Indicator | Specifies whether the customer initiating payment request requires an acknowledgement from Temenos Infrastrcture bank. Configure one of the following values:
|
Interim Status Indicator | Specifies whether the customer initiating payment request requires an interim status confirmation when processing a payment. This is applicable for INST and NRINST payments. Configure one of the following values:
Interim status is sent when payment is in the following statuses:
|
Customer Status Msg Type | Message type to be used when sending a payment confirmation to the customer who initiated the payment request. Configure a valid status message type already defined in the system. Pacs.002 is the message type used to send ACK/NACK, or Interim Status report to indirect participant (when using ISO20022 messaging). |

The user can configure the customer specific advice related attributes in the Client Agreements page. To perform this, do the following actions:
- Click the Client Cond Advice tab.
- Enter the required details in the following fields:
Field Description Advice Indicator Configure one of the following values: - If a customer specific advice needs to be sent, set as Y.
- If not, set as N.
If Advice Indicator is set as Y, configure the advice related fields given below. These fields are part of the associated multi-value set. The users can configure multiple advices and configure these fields for each advice.Debit/Credit Advice Type of the advice to be generated. - Configure one of the following values:
- For a debit advice, set as D.
- For a credit advice, set as C.
- For a charge advice, set as Ch.
Delivery Method Channel for delivering the advice to customer. - Configure one of the following values:
- To send the advice by email, set as Email.
- To send the advice by fax, set as Fax.
- To send the confirmation by phone call, set as Phone.
- To send the printed advice by post through Autoform, set as Post.
- To send the printed advice by post through Delivery Module, set as Print.
- To send the advice by SMS, set as Sms.
- To send the advice using SWIFT (MT900 for debit and MT910 for credit advice), set as Swift.
Refer Debit Advice and Credit Advice mapping sheets for customising the print advice posted through Delivery Module.Phone Confirmation Phone number to be contacted. This field is required when the Delivery Method field is set as Phone.Sms Mobile number to send SMS. This field is required when the Delivery Method field is set as SMS.Fax Fax number to send advice. This field is required when the Delivery Method field is set as Fax.Email Email ID to send the advice. This field is required when the Delivery Method field is set as Email.Mail Line 1(Post) Postal address line 1 of the customer address for sending advice by post. This field is required when the Delivery Method field is set as Post.Mail Line 2(Post) Postal address line 2 of the customer. Mail Line 3(Post) Postal address line 3 of the customer. Mail Line 4(Post) Postal address line 4 of the customer. SWIFT BIC of the bank to send advice by SWIFT. This field is required when the Delivery Method field is set as SWIFT.Attention Useful information text related to the advice. Advice Type Advice type that a customer requires. - Configure one of the following values:
- Single
- Group
- Blank
This is applicable when the advice is sent by SMS or email.Advice Transaction Lower Limit Lower limit of payment amount in home currency beyond which an advice is sent by SMS or email. This is applicable when the advice type is Single.
FX Discount for Customers
The user can configure the customer specific FX discounts in the Client Agreements page. To perform this, do the following actions:
- Click the Client Cond FXDiscount tab.
- Enter the required details in the following fields:
Field Description FX Discount Indicator Indicates whether to allow discount on FX rate for the specific customer or not.
Configure one of the following values:- If an FX discount needs to be provided, set as Y.
- If not, set as N.
The users can configure the values in Transaction Currency and Discount Percentage fields, when set to Y.
These fields are associated multi-value sets. Hence, allows to configure multiple records for separate currencies with corresponding discount percentage.Transaction Currency Payment currency for which FX discount is provided to the customer. - Configure a valid currency code.
Discount Percentage FX discount percentage for the currency to be provided to the customer. - Configure the discount percentage for the respective currency.

The user can configure the client-specific separate charge accounts in the Client Agreements page. To perform this, do the following actions:
- Click the Client Cond Charge Account tab.
- Enter the required details in the following fields:
Field Description Separate charge Account Indicator Indicates whether a separate charge account is required for the customer.
Configure one of the following values:- If separate charge account is required, set as Y.
- If not, set as N.
The user can configure this field, when Separate Charge Booking field in the Client Condition tab is set to Y.If Separate Charge Account Indicator is set to Y, the following fields are configured for entering details of the separate charge account (and at least one charge related record needs to be configured):
These fields are part of associated multi-value sets. Hence, multiple records can be configured (for example, debit, credit, etc.).Indicator For Charge Account Leg of the payment for which charge account configuration is done.
Configure one of the following values:- For credit transactions, set as C.
- For debit transactions, set as Y.
- For all transactions, set as A.
Transaction Currency Payment currency for which the charge configuration is applicable. - Configure a valid currency code defined in the system.
Charge Account Company ID Valid company ID of the charge account. Charge Account Currency Valid currency code of the charge account. Charge Account Number Valid charge account number from which transaction charges are collected. Balance Check On Chg Act Indicates whether balance check of debiting charges is performed on the configured charges account. - Configure one of the following values:
- If a balance check needs to be performed, set as Y.
- If not, set as N.
In this topic