Payments

R24 AMR | Min(s) read

Feedback

Configuring Product Determination

This section helps the user to understand the configuration of product determination

Heavy Weight

To configure heavy weight products, go to Admin Menu > Payment Hub > Product Determination > Product Condition – Heavy. It displays the list of heavy weight products defined in the system.
Do one of the following:

To view a record, click .
To amend or edit a record, click .
To create a new product, click .

This page is used to define the product conditions (input attributes) to determine a product for heavy weight payment and corresponding output attributes. A product is determined and output attributes are linked to various subsequent processing components given below.

Fee
Ledger
Client Condition
Posting and Routing

This is based on the payment characteristics that are defined by using the product conditions. Additionally, it is linked to various transaction codes that are used for booking the payments. It also influences the payment flow based on the STP indicator, imposed flag, and message priority.

Input Attributes

A heavy weight product is defined for each company. This is the company of the debit account and processing company of the payment. The bank user uses the following input attributes to configure heavy weight products:

Field	Description
CTRBTR Indicator	Configure one of the following values: For customer payment, set as C. For bank transfer, set as B. Customer transfers are relevant for client conditions, while bank transfers are not. The charging structure for customer and bank transfers differ. Hence, it becomes an input for fees. Defines the Client Condition, Fee and Posting product. Additionally, the output generation component uses this for SWIFT validations.
Payment Direction	Configure one of the following values: For incoming payment, set as I. For outgoing payment, set as O. For re-direct payment, set as R. For book payment, set as Book. Invokes the following: Routing and Settlement (R&S) component for outgoing or redirect routing. Credit party determination for incoming and book payments. The Payment Direction along with the Charge Type (BEN or SHA or OUR or *) determines the fee processing. Defines the R&S and Fee products.
Domestic International	Configure one of the following values: For international payment, set as I. For domestic payment, set as D. Payments are categorised as Domestic or International based on currency and geography. This enables to define Output channel, charges to be applied, R&S, and Fee products.
Message Priority	A valid numeric priority (1 to 9). For normal payments, set 1 to 5. For urgent payments, set 6 to 10. Incoming priority can be modified by codewords or in product determination by setting a new priority.
Single Batch Clearing	Configure one of the following values: For single payments, set as S. For batch parent, set as P. For batch child, set as C. For clearing settlement, set as Y. For clearing payment, set as N. Defines specific Fee, Routing & Settlement, and Posting products. The bank receives single (SWIFT customer transfer) or batch payments (salary processing). Batches have a parent and child relationship. Child transactions are released once the parent is processed. For batch transactions, the fee for the child transactions is borne by the parent (if charge option is SHA or OUR). Clearing transactions can be customer payment or settlement transactions. Settlement transactions does not have any fee, routing and different posting. Therefore, single, batch or clearing indicator influences the following: Fee R&S Posting products
Originating Source	Bank receives payments from different sources: External channels (For example, SWIFT, TARGET, FEDWIRE, FPS, and so on.) Internal sources (For example, internet banking, trade platform, and so on.) Apply different client conditions and charges depending on the source or source product group (combination of sources). Set the Client Condition and Fee products.
Return Trigger/Incoming Message Type	Indicates whether it is a return or an incoming message type. Configure one of the following values: Message Type - Different types of payment messages are received from various channels. For example, incoming payments from SWIFT can be 101, 103, 202, and so on. These SWIFT messages can result in outgoing or re-direct payments. Messages received from Order Entry and Standing Order result in Outgoing or Book payments. The message type influences the fees and output generation, and its attributes are used to set the Routing and Settlement (R&S) product. In combination with originating source, fees can be skipped for certain payments and hence a separate fee product or output parameter can drive the processing Y – The Return Trigger is set when an incoming payment is returned (manually from repair or automatically based on configuration) to denote that a return payment needs to be created. This influences the routing, fees, and output generation. * - This is the default value.
Currency	Configure one of the following values: Valid currency code Currency group maintained in the system Set the PSD output flag. The fees for processing the payment differs according to the currency.
Charge Type	Configure one of the following values: For customer transfers, set as BEN, SHA, OUR or ‘’ For bank transfers, set as ‘’ Fees component uses Charge Type field along with the Direction field to process the charges on the payment. Influences R&S and different Routing groups. For example, ‘OUR’ payments can be routed by using specific correspondent banks whose ‘OUR’ charges are lesser or offers more discounts. Enables the R&S to decide on the channel. If the Charge Type is SHA, choose SEPA as a channel to influence the Routing Group.
Ordering Institution BIC Present	Determines whether the payment can be STP (MT103+) and Output Channel for the payment is SEPA. Hence, this field Influences R&S and Fee products. To configure this field, set the value as Y (Yes) or * (default).
Beneficiary BIC Present	Determines whether the payment can be STP (MT103), and output channel for the payment is SEPA. These decisions require the appropriate R&S and Fee products to be set. Sets the non-STP indicator. To configure this field, set the value as Y (Yes) or * (default).
Ordering Party IBAN Present	Presence of IBAN of the ordering party (Account in Tag 50) is included to process the message STP (103+). Determines if the output channel for the payment is SEPA. Hence, it influences R&S and Fees. Ensures that the payment is EC compliant. To configure this field, set the value as Y or * (default).
Beneficiary Party IBAN Present	Presence of beneficiary IBAN (Account in Tag 59) is included to process the message STP (103+). Determines whether the output channel for the payment is SEPA. Hence, it influences R&S and Fees. Ensures that the payment is EC compliant. To configure this field, set the value as Y or * (default).
Chargeable Change	Configure one of the following values: Yes (Y) No (N) * (Default value) Available when Tag 57 is repaired by the automated SWIFT message repair tool (PayFix). If beneficiary BIC is repaired, the bank makes the payment as PSD non-compliant. Influences the payment fees.
Final Code Word	Configure one of the following values: Valid code word (already defined in the system) ‘*’ (default) Bilaterally agreed codewords in the message (apart from standard SWIFT Code words) can drive the processing. Multiple codewords can be available in a payment message. Code Word component assigns a final code word, which becomes an input to product determination. For example, if 23E (INSBNK) field has INTC and PHOB, then INTC can become the ’Final Codeword’ as it influences the payment fees.
Code Word Text	Text associated with the Final Code Word. It influences the payment processing of other components, such as Date Determination, R&S and Fees. For example, bilateral codewords available in Tag 23E of a MT101 are as follows: OTHR in the codeword BBDD in the Beneficiary Bank Due Date field REACH BENEFICIARY QUICKLY in the Code Word Text field The ‘BBDD’ influences the Credit Value Date. This is directly referred by the codeword component and appropriate flag is set for the dates component. The ‘REACH BENEFICIARY QUICKLY’ set an appropriate Routing product. Some banks exchange bilaterally agreed codewords in Tag 72 with standard SWIFT code word ‘REC’ and the bilateral codeword in the text following it. Bilateral code word available after ‘REC’ is updated by the codeword component in Code Word Text for further processing in product determination.
Intra Company Payment	Configure one of the following values: ‘Y’ ‘’ (Default) A standard SWIFT codeword (INTC) identifies ’Intra-Company’ payments. This value needs to be available in the Final Code Word* assigned by the codeword component. Book payments originated by corporate clients from their direct access channels have a specific codeword, when both the debit and credit account belong to the same client or client group. Set during mapping for payment router messages. There is a discount on fees for such payments, which influences the Fee product.
Banking Priority	Configure one of the following values: For normal, set as N. For urgent, set as U. SWIFT messages with Tag 113 (banking priority) in User Header (Block 3) have a codeword to indicate the urgency of the payment. For example, General Interbank Recurring Order (GIRO) payments are processed within a specific time window (2 hours). Hence, this influences the Routing product to choose an urgent channel and set a higher priority.
Configure one of the following in Originating DebitParty Country, OrderingParty IBAN Country, and Sender Country fields: Valid country Country group code ‘*’ (default)
Originating Debit Party Country	Ordering Institution (Tag 52A). It determines the country where the payment is originated to check whether the ‘Debit Leg’ of the payment is PSD and EC 924/2009 compliant. EU or EEA country ensures that the payment is PSD or EC compliant. Influences regulatory reporting.
Ordering Party IBAN Country	If Tag 52A is not available, use the country code in the IBAN of the ordering party (Tag 50A) to determine the country where the payment originates. Determines whether the ‘Debit Leg’ of the payment is PSD compliant (subject to interpretation by banks).
Sender Country	If the originating debit party country cannot be retrieved from the payment (Tag 52A not present), the sender country is treated as the originator of the payment to check whether the debit leg of the payment is PSD and EC compliant. EU or EEA country ensures that the payment is PSD or EC compliant.
Ordering Party Residency	Configure one of the following values: Non-resident (N) Resident (R) ‘*’ (Default value) If the ordering (debit) party is a non-resident, there can be special requirements for regulatory reporting.
Beneficiary Country	Configure one of the following values: Non-resident (N) Resident (R) ‘*’ (Default value) Country where the beneficiary has an account. Country of the account with institution (Tag 57A or Tag 58A), where it is not the same as the ‘Receiver’. Determines the final destination of the payment to check PSD or EC compliance for the credit leg of the payment. EU or EEA country ensures that the payment is PSD or EC compliant. Specifies a different Fee product and defines regulatory reporting requirements.
Beneficiary Party IBAN Country	Configure one of the following values: Valid country Country group code ‘*’ If the beneficiary country (57A) is not present, the ultimate destination of the payment can be derived from the IBAN Country Code (Tag 59A). Checks PSD/EC compliance for the credit leg of the payment (subject to interpretation by banks).
Receiver Country	Configure one of the following values: Valid country Country group code ‘*’ Checks PSD or EC compliance for the credit leg of the payment. EU or EEA country ensures that the payment is PSD or EC compliant. Sets a different Fee product and define regulatory reporting requirements.
Debit Account Type	Configure one of the following values: For Client account, set as C For Nostro account, set as N For Vostro account, set as V For Internal account, set as I For P&L, set as PL For default value, set as ‘*’ If the debit account is a PL, then fees is not applicable for that payment. Hence, a different Fee product can be set. For example, refund of charge to the client by using Fee product output, skipping the fees or setting to 0.
Configure one of the following values in Sender BIC, Receiver BIC, and Incoming Message Type fields: Valid BIC ‘*’
Sender BIC	Bank offers discounts on payments within its own network (inter-company). Hence, it needs to identify payments originating and ending within its network. For example, Bank A sends a payment to Bank B and both companies exist in Temenos Transact. Hence, the ordering institution (sender) BIC and beneficiary (or receiver) BIC are included in product determination to identify such payments.
Receiver BIC	BIC of the account with Institution (57A) or receiver of the message (if 57A is not available). Identifies payments within own network to offer discounts.
Validation Flag	Configure one of the following values: Validation flag of SWIFT MT message header tag 119 (such as STP) ‘*’ Differentiates a normal MT103 from a MT103+ (STP) and an MT202 from an MT202 (COV) message. If it is not relevant for MT202 COV messages, this enables the bank to charge differentially for MT103+ (STP) payments and normal MT103 payments.
From Amount	Start of the amount range. Amount can be low or high value, and different client conditions and fees can be applicable depending on the value of the payment.
To Amount	End of the amount range. Payment amount can be low or high value, and different client conditions and fees can be applicable depending on the value of the payment.

To distinguish the amount, set the products with an amount range in Fromamount and Toamount fields. These fields are part of an associated multiple-value set. The user can configure multiple product condition records for different amount range.

To enter a new amount range, click .
To delete an amount range, click .

The entire set of output attributes are configured in the Output Parameters tab for each amount range. For example, if the input attributes are defined for two amount ranges, then two sets of output parameters are configured corresponding to each amount range.

Output Attributes

Field	Description
Client Condition Group	Client condition product. It is used as an input for client condition component.
Source Product Group	Configure one of the following values: Source (S) Group (G) If the Source Indicator is S, product determination refers it and enters the ‘Source’ product with Originating Source. Checks the `Source Product Group` table and the updates the relevant source product linked. Client conditions and Fees components use this with Client Condition product to define client conditions and fees for a specific product and source.
Routing Product Group	Routing product that becomes an input for Routing & Settlement.
Impose Routing Flag	Indicates the system’s actions when the routing product configured in Routing Product Group is not found during processing. If left blank, the system processes the payment using the default Routing product. If set as Y, the system does not process using default Routing product.
Fee Product Group	Fee product that is used as an input parameter for fees.
Posting Product Group	Posting product that is used as an input parameter for posting scheme.
Filtering Product Group	Payment Filtering product that is used as an input parameter for filtering component.
Duplicate Type	ID of the EB.DUPLICATE.TYPE core application. It is used for functional duplicate check processing.
Debit Book Code	Booking code for the debit entry on the payment transaction amount. Defined as an output of product determination to enable setting of different debit booking codes based on transfer type (customer, bank) and message type (103, 202), without the necessity to replicate the posting set.
Debit Charge Book Code	Booking code for the charge debit.
Debit VAT Book Code	Booking code for VAT debit.
Credit Book Code	Booking code for the credit entry on the payment transaction amount.
Credit Charge Book Code	Booking code for the charge credit.
Credit VAT Book Code	Booking code for VAT credit.
The user needs to configure the Debit Book Code, Debit Charge Book Code, Debit VAT Book Code, Credit Book Code, Credit Charge Book Code, and Credit VAT Book Code fields, which becomes an input parameter for posting scheme.
Regulatory Reporting Indicator	Indicates whether the payment meets regulatory reporting requirements. Configure one of the following values: If regulatory reporting is required, set as Y. If regulatory reporting is not required, leave it blank.
New Priority	Configure one of the following values: If there is no change in priority, leave it blank. To set a new priority, enter a value from 1 to 9. New priority of the payment. The user can ignore the existing priority and define a new priority.
Non STP Indicator	Enables to move the payment to Manual Repair instead of processing using STP. Configure one of the following values: To move payment to Manual Repair, set as Yes. To process in STP, set as No. To use STP for processing, leave it blank.
PSD Compliant Flag	Defines whether the payment is PSD compliant. onfigure one of the following values: If debit leg is PSD compliant, set as D. If credit leg is PSD compliant, set as C. If both legs are PSD compliant, set as Y. If it is not PSD compliant, set as N. To ignore or PSD is not applicable, set as I. Used by Date Determination and Fee components for processing the payment. If both legs are PSD compliant, then charge is set as SHA for R&S component to choose SEPA as a channel and fee component. Ensure to install PPPSDC component to configure this parameter.
EC Compliant Flag	Defines whether the payment is EC compliant. Configure one of the following values: If the payment is EC compliant, set as Y. If the payment is not EC compliant, set as N.
Forward Entry Flag	Defines whether forward entries are raised for the payment. Configure one of the following values: To raise forward entry, set as Y. If not, set as N.
Switch Account	Allows to enable or disable account switching in Temenos Payments at product determination level. This is applicable for inward payments and book payments. If configured, Temenos Payments validates whether the credit main account is switched out. Configure one of the following values: If left blank, the system processes the payment without checking for account switching. If set as Y, the system performs account switching by receiving the switch out details and redirecting the payment to the switched account in the other bank. This feature is available with PH license.
STP Indicator Payment Order	Decides whether a payment coming from `PAYMENT.ORDER` (`PO`) application or any other external application needs to be processing STP or non-STP. Configure one of the following values: For STP processing, set as Y. For non-STP and to move the payment to Manual Repair, set as N.
Currency Market	Identifies the correct exchange and revaluation rates to be applied to each Currency in case of FX transactions. Select one valid currency market, which is already defined.
Txn Stop Map Rule	If this field is configured, it denotes that Transaction Stop Check needs to be performed on the debit main account. A stop instruction is captured in this field and it links to the Transaction Stop Module, which performs blacklist checking for the debit main account. If this field is not configured, then Transaction Stop check is not performed on the account. The value configured needs to be a valid record in `TZ.TRANSACTION.STOP.MAP.RULES`.
Rate Fixing	Configure one of the following values in this field Select 'Yes' to park the payment until new rate is available without reservation Select 'No' to process the payment with the existing rate Select 'Blank' If Rate Fixing definition at Company Properties table need to prevail Select 'Yes, With Reservation' to reserve funds at mid-rate before parking the payment until new rate is available Indicates the definition of rate fixing at product condition level precedes over the configuration at company level (PP.COMPANY.PROPERTIES)
Dates Product Group	Defines the date product, which is the input for selecting boundary date record. It is not a mandatory field. If the date product is not configured, then default record is used for processing the payment.

Medium Weight

To configure medium weight product, go to Admin Menu > Payment Hub > Product Determination > Product Condition – Medium. It displays the list of medium weight products defined in the system.
Do one of the following:
- To view a record, click .
- To amend or edit a record, click .
- To create a new product, click .

This screen defines the product conditions, determines a product for medium weight payments and corresponding output parameters. The product is determined and output attributes are linked to various subsequent processing components given below.

Fee
Ledger
Client Condition
Posting and Routing

This is based on the payment characteristics defined using the product conditions. Additionally, it is linked to various transaction codes that are used for booking the payments. It also influences the payment flow based on the STP indicator, imposed flag, and message priority.

Input Attributes

A medium weight product is defined for each company. This is the company of the debit account and processing company of the payment. The bank users can configure medium weight products by using the following product conditions (input attributes):

Field	Description
Payment Direction	Configure one of the following values: For incoming payments, set as I. For outgoing payments, set as O. For re-directing, set as R. For book payments, set as B. Invokes the following: R&S component for outgoing or redirect routing. Credit party determination for incoming and book payments. The Payment Direction field along with Charge Type field (BEN, SHA, OUR or *) determines the fee processing. Defines the R&S and Fee products.
Clrg Trn Type	Clearing transaction type for the payment. Configure a valid clearing transaction type already defined in the system. Example Credit Transfer (CT) Direct Debits (DD)
Domestic International	Configure one of the following values: For international payments, set as I. For domestic payments, set as D. Payments are categorised as Domestic or International based on currency and geography. Output channel, charges to be applied, R&S and Fee products are defined based on this parameter.
Single/Batch/Clg	Configure one of the following values: For single payments, set as S. For batch parent, set as P. For batch child, set as C. For clearing settlement, set as Y. For clearing payment, set as N. Bank receives single payments or batch payments (such as salary processing). Batches have a parent and child relationship. Defines specific Fee, R&S and Posting products.
Charge Type	Configure one of the following values : BEN OUR SHA The Use Charge Type field along with the Direction field for processing the payment charges. Influences R&S Set different routing groups based on Charge Type.
Currency	Configure one of the following values: Valid currency Currency group (maintained in the system)
From Amount	Start of the amount range. Payment amount can be low or high value, and different client conditions and fees can be applicable depending on the value of the payment.
To Amount	End of the amount range. Payment amount can be low or high value, and different client conditions and fees can be applicable depending on the value of the payment.

To distinguish the values, set the product amount range in Fromamount and Toamount fields. These fields are part of an associated multi-value set. The user can configure multiple product condition records for different amount range by performing the below actions.

To enter a new amount range, click
To delete an amount range, click .

The entire set of output attributes are configured in the ‘Output Parameters’ tab for each amount range. For example, if the input attributes are defined for two amount ranges, then configure two sets of output parameters corresponding to each amount range.

Field	Description
Source Group	Source group of the payment
Message Type	Type of the payment message
Clearing Nature Code	Nature of the clearing payment
The user can configure one of the following values in Source Group, Message Type, and Clearing Nature Code fields: ‘*’ Valid source (defined in the system)
Ben Pty IBAN Ctry	Country code or country group in the IBAN of the beneficiary party.
Ord Pty IBAN Ctry	Country code or country group available in the IBAN of the ordering party.
The user can configure one of the following values in Ben Pty IBAN Ctry and Ord Pty IBAN Ctry fields: ‘*’ Valid country code Country group code
Beneficiary Party IBAN Present	Indicates presence of beneficiary party IBAN.
Ordering Party IBAN Present	Indicates presence of ordering party IBAN.
Ben BIC Present	Indicates presence of beneficiary party BIC.
Ord BIC Present	Indicates presence of ordering party BIC.
The user can configure one of the following values in Ordering Party IBAN Present, Ben BIC Present, and Ord BIC Present fields: If IBAN is available, set as Y. If IBAN is not available, set as *.
Ord Pty Residency	If the ordering (debit) party is a non-resident, special requirements can be available for regulatory reporting. Configure one of the following values: If the ordering party is a non-resident, set as N. If the ordering party is a resident, set as R. For default value, set as *.
Final Codeword	Codeword component assigns a final codeword, which becomes an input to product determination as multiple codewords in a payment message can be available. Configure one of the following values: Valid codeword (already defined in the system) ‘*’

Output Attributes

Field	Description
Client Condition Group	Defines the Client Condition product, and is used as an input for client condition component.
Source Product Group	Configure one of the following values: For source, set as S. For group, set as G. Product determination refers the Source Indicator. If the Source Indicator is S, enter the Source product with Originating Source. Checks the `Source Product Group` table and updates the relevant Source product linked to the table. Defines Client Conditions and Fees for a specific product and source by using client conditions and fees components along with Client Condition product.
Routing Product Group	Defines the Routing product and is used as an input for R&S.
Impose Routing Flag	Indicates the system’s actions, when the Routing product configured against Routing Product Group is not found during processing. To process the payment using default routing product, leave it blank. To process using default routing product, set as Y.
Fee Product Group	Fee product that is used as an input parameter for fees.
Posting Product Group	Posting product that is used as an input parameter for posting scheme.
Filtering Product Group	Payment Filtering product that is used as an input parameter for filtering component.
Duplicate Type	Has the ID of the EB.DUPLICATE.TYPE core application. Used for duplicate check processing in Temenos Payments.
Debit Book Code	Booking code for the debit entry on the payment transaction amount. Defined as an output of product determination to enable setting of different debit booking codes based on transfer type and message type without the necessity to replicate the posting set.
Debit Charge Book Code	Booking code for the charge debit.
Debit VAT Book Code	Booking code for VAT debit.
Credit Book Code	Booking code for the credit entry on the payment transaction amount.
Credit Charge Book Code	Booking code for the charge credit.
Credit VAT Book Code	Booking code for VAT credit.
The user needs to configure the Debit Book Code, Debit Charge Book Code, Debit VAT Book Code, Credit Book Code, Credit Charge Book Code, and Credit VAT Book Code fields, which becomes an input parameter for posting scheme.
Regulatory Reporting Indicator	Indicates whether the payment meets regulatory reporting requirements. Configure one of the following values: If regulatory reporting is required, set as Y. If not required, leave it blank.
New Priority	New priority of the payment. Enables to ignore the incoming priority and define a new Priority. Configure one of the following values: If there is no change in the priority, leave it blank. To set a new priority, set the value 1 to 9.
Non STP Indicator	Enables to move the payment to Manual Repair instead of processing using STP. Configure one of the following values: To process using STP, leave it blank. To move the payment to Manual Repair, set as Y.
PSD Compliant Flag	Defines whether the payment is PSD compliant. Configure one of the following values: If the debit leg is PSD compliant, set as D. If the credit leg is PSD compliant, set as C. If both legs are PSD compliant, set as Y. If it is not PSD compliant, set as N. to ignore when PSD is not applicable, set as I. This indicator is used by Date Determination and Fee components to process the payment. If both legs are PSD compliant, then Charge field is set to SHA for R&S component to choose SEPA as a channel and for fee component. If the debit leg is PSD compliant, set as D. If the credit leg is PSD compliant, set as C. If both legs are PSD compliant, set as Y. If it is not PSD compliant, set as N. to ignore when PSD is not applicable, set as I. This indicator is used by Date Determination and Fee components to process the payment. If both legs are PSD compliant, then Charge field is set to SHA for R&S component to choose SEPA as a channel and for fee component. This indicator is used by Date Determination and Fee components to process the payment. If both legs are PSD compliant, then Charge field is set to SHA for R&S component to choose SEPA as a channel and for fee component. PPPSDC component needs to be configured.
Settlement Type	Specifies whether the product is determined for a pre or post settled direct debit clearing. Configure one of the following values: Presettle Postsettle Influences the date calculation.
Clearing Holiday	Indicates the clearing for which the non-working days are checked for the payment (during date calculation). Required for DD clearing batch parent and child that are book payments. Calculates the settlement date considering the clearing business date. This is used to settle the child payments .
EC Compliant Flag	Defines whether the payment is EC compliant. Configure one of the following values: If the payment is EC compliant, set as Y. If the payment is not NC compliant, set as N.
Switch Account	Allows to enable or disable account switching in Temenos Payments at product determination level. This is applicable for inward payments and book payments. If configured, Temenos Payments validates whether the credit main account is switched out. Configure one of the following values: If left blank, the system processes the payment without checking for account switching. If set as Y, the system performs account switching by receiving the switch out details and redirecting the payment to the switched account in the other bank. This feature is available with PH license.
Currency Market	Identifies the correct exchange and revaluation rates to be applied to each currency (during FX transactions). Select a valid currency market that is already defined.
Txn Stop Map Rule	If this field is configured, it denotes that Transaction Stop Check needs to be performed on the debit main account. A stop instruction is captured in this field and it links to the Transaction Stop Module which performs blacklist checking for the debit main account. If this field is not configured, then the Transaction Stop check is not performed on the account. The value configured needs to be a valid record in TZ.TRANSACTION.STOP.MAP.RULES.
Rate Fixing	Configure one of the following values in this field: Select 'Yes' to park the payment until new rate is available without reservation Select 'No' to process the payment with the existing rate Select 'Blank' If Rate Fixing definition at Company Properties table need to prevail Select 'Yes, With Reservation' to reserve funds at mid-rate before parking the payment until new rate is available Indicates the definition of rate fixing at product condition level precedes over the configuration at company level (PP.COMPANY.PROPERTIES).
Dates Product Group	Defines the date product, which is the input for selecting boundary date record. It is not a mandatory field. If the date product is not configured, then default record is used for processing the payment.

Light Weight

To configure light weight products, go to Admin Menu > Payment Hub > Product Determination > Product Condition – Light. It displays the list of light weight products defined in the system.
Do one of the following:
- To view a record, click .
- To amend or edit a record, click .
- To create a new product, click .

This screen is used to define the product conditions to determine a product for light weight payments and corresponding output parameters. A product is determined and output parameters are linked to various subsequent processing components given below.

Fee
Ledger
Client Condition
Posting and Routing product

This is based on the payment characteristics defined using the product conditions. Additionally, it is linked to various transaction code that are used for booking the payments. It also influences the flow of payment based on the STP indicator, imposed flag, and message priority.

Input Attributes

A light weight product is defined for each company. This is the company of the debit account and processing company of the payment. The bank users can to configure light weight products by using the following product conditions (input attributes):

Field	Description
Source	Identifies the originating source group of the payment. Configure one of the following values: Valid source (defined in the system) ‘*’
Msg Type	A valid message type of the payment.
Domestic International	Configure one of the following values: For international payments, set as I. For domestic payments, set as D. Payments are categorised as Domestic or International based on currency and geography. Output channel, different charges to be applied, R&S and Fee product are defined based on this parameter.
Clearing Transaction Type	Identifies the clearing transaction type. Distinguishes between returns or refunds, credit transfers or direct debits, and so on. Configure one of t,he following values: Valid clearing transaction type (defined in the system) ‘*’
Clearing Nature Code	Nature of the clearing transaction. Configure one of the following values: Valid clearing nature code (defined in the system) ‘*’
Settlement Indicator	Identifies whether the payment is a settlement transaction or not. Configure one of the following values: To indicate settlement transaction, set as Y. If not, set as ‘*’.
Payment Direction	Direction of the payment. Configure one of the following values: For incoming payment, set as I. For outgoing payment, set as O. For book payment, set as Book. For redirect payment, set as Redirect. If not, leave it blank.

Output Attributes

Field	Description
Client Condition Group	Client Condition product that becomes the input for client condition component.
Source Product Group	Configure one of the following values: Source (S) Group (G) To enable Product Determination to refer the Source Indicator and enter ‘Source’ product with Originating Source, set the Source Indicator as ‘S’. Checks the `Source Product Group` table and updates the relevant Source product linked in the table. Client conditions and fees components are used along with Client Condition Product, to define it for a specific product and source.
Routing Product Group	Routing product that is used as an input for R&S.
Impose Routing Flag	Indicates the system’s actions when routing product configured against Routing Product Group is not found during processing. To enable the system to process the payment by using default routing product, leave it blank. If not, set as Y.
Fee Product Group	Fee product that is used as an input parameter for Fees.
Posting Product Group	Posting product that is used as an input parameter for posting scheme.
Filtering Product Group	Payment Filtering product that is used as an input parameter for filtering component.
Duplicate Type	The ID of the EB.DUPLICATE.TYPE core application`.` It is used for duplicate check processing in Temenos Payments.
Debit Book Code	Booking code for the debit entry on the payment transaction amount. Defined as an output of product determination to enable setting of different debit booking codes based on the transfer and message types without the necessity to replicate the posting set.
Debit Charge Book Code	Booking code for the charge debit.
Debit VAT Book Code	Identifies the booking code for VAT debit.
Credit Book Code	Booking code for the credit entry on the payment transaction amount.
Credit Charge Book Code	Booking code for the charge credit.
Credit VAT Book Code	Booking code for VAT credit.
The user needs to configure Debit Book Code, Debit Charge Book Code, Debit VAT Book Code, Credit Book Code, Credit VAT Book Code and Credit VAT Book Code fields, which is used by the posting scheme.
Regulatory Reporting Indicator	Indicates whether the payment meets regulatory reporting requirements. If regulatory reporting is required, select the check box.
Non STP Indicator	Indicates whether to process the payment using STP or Non-STP. To indicate non-STP and move the payment to Manual Repair, select the check box.
PSD Compliant Flag	Defines whether the payment is PSD compliant. Configure one of the following values: If both legs are PSD compliant, set as Y. If it is not PSD Compliant, set as N. To ignore when PSD is not applicable, set as I.
Settlement Type	Specifies whether the product that is determined, is for a pre or post settled direct debit clearing. Influences the date calculation. Configure one of the following values: Presettle Postsettle
Clearing Holiday	Indicates the clearing for which the non-working days is checked for the payment during date calculation. It is required for DD clearing batch parent and child that are book payments. Calculate the settlement date considering the clearing business date using which the child payments are settled.
EC Compliant Flag	Defines whether the payment is EC compliant. Configure one of the following values: If the payment is EC compliant, set as Y. If the payment is not NC compliant, set as N.
Forward Entry Flag	Defines whether forward entries needs to be raised for the payment. Configure one of the following values: To raise forward entry, set as Y. To not raise a forward entry, set as N or leave it blank.
Switch Account	Allows to enable or disable account switching in Temenos Payments at product determination level. This is applicable for inward payments and book payments. If configured, Temenos Payments validates whether the credit main account is switched out. Configure one of the following values: If left blank, the system processes the payment without checking for account switching. If set as Y, the system performs account switching by receiving the switch out details and redirecting the payment to the switched account in the other bank. This feature is available with PH license.
Currency Market	Identifies the correct exchange and revaluation rates to be applied to each currency (during FX transactions). Select a valid currency market that is already defined.
Txn Stop Map Rule	If this field is configured, it denotes that Transaction Stop Check needs to be performed on the debit main account. A stop instruction is captured in this field and it links to the Transaction Stop Module, which performs blacklist checking for the debit main account. If this field is not configured, then Transaction Stop check is not performed on the account. The value configured needs to be a valid record in TZ.TRANSACTION.STOP.MAP.RULES.
Rate Fixing	Configure one of the following values in this field: Select 'Yes' to park the payment until new rate is available without reservation Select 'No' to process the payment with the existing rate Select 'Blank' If Rate Fixing definition at Company Properties table need to prevail Select 'Yes, With Reservation' to reserve funds at mid-rate before parking the payment until new rate is available Indicates the definition of rate fixing at product condition level precedes over the configuration at company level (PP.COMPANY.PROPERTIES).
Dates Product Group	Defines the date product, which is the input for selecting boundary date record. It is not a mandatory field. If the date product is not configured, then default record is used for processing the payment.

Product Output Refinement

Configuring product output refinement involves creating refinement ID as discussed below.

Creating Refinement ID

Below table shows the refinement IDs for different activation phases.

Component	Refinement ID
Product Determination	Activation Phase-Weight-Product Determination ID Activation Phase - PRODET (Product Determination) Weight - H, M, L (Heavy, Medium, or Light) Product Determination ID - Actual ID of the product to be refined All the above-mentioned parameters are mandatory.
Debit Client Condition	There are two types of refinement IDs. Activation Phase-Weight-Product Determination ID Activation Phase-Output parameter If both types of refinements are present, then the refinement with the product determination ID takes precedence. Activation Phase DBTCC - for debit client condition CTRNS - for credit transfer routing product CDTCC - for credit client condition FILTER - for filtering product CHARGE - For fee product Weight Weight - H, M, L (Heavy, Medium, or Light) (Mandatory when defined with product determination ID) blank - No input is required when defined with output of product determination Product Determination ID/Output Attribute Product Determination ID - Actual ID of the product to be refinement Output Parameter - The output parameter of the product determination ID for the payment
Routing Product
Credit Client Condition
Filtering Product
Fee Product

Below image shows the various refinement records created in different activation phases.

Input Parameter of Refinement

Expand the following sections for more information on each input parameter:

Attribute

Indicates the attribute of the payment to which the rule is to be applied. This contains three groups.

Click the respective buttons for more information about the Primary, Secondary, and Party groups.

Some fields of POR.TRANSACTION is represented as primary. Following table provides the mapping between the fields in POR.TRANSACTION and the drop-down value to interpret and use for defining the rules.

Table	Field Name	Drop-down Value
POR.TRANSACTION	CompanyID	Primary - Company ID
POR.TRANSACTION	PaymentDirection	Primary - Payment Direction
POR.TRANSACTION	CTRBTRIndicator	Primary – CTR BTR Indicator
POR.TRANSACTION	OwnAccountIndicator	Primary - Own Account Indicator
POR.TRANSACTION	IntraCompanyPayment	Primary - Intra Company Payment
POR.TRANSACTION	MessagePriority	Primary - Message Priority
POR.TRANSACTION	DomesticInternational	Primary - Domestic International
POR.TRANSACTION	MessageFormat	Primary - Message Format
POR.TRANSACTION	PriorityCode	Primary - Priority Code
POR.TRANSACTION	CompanyRegion	Primary - Company Region
POR.TRANSACTION	SenderAddress	Primary - Sender Address
POR.TRANSACTION	ReceiverAddress	Primary - Receiver Address
POR.TRANSACTION	BankOperationCode	Primary - Bank Operation Code
POR.TRANSACTION	TransactionTypeCode	Primary - Transaction Type Code
POR.TRANSACTION	DebitMainAccountCompanyID	Primary - Debit Main Account Company ID
POR.TRANSACTION	DebitMainAccountCurrencyCode	Primary - Debit Main Account Currency Code
POR.TRANSACTION	DebitPartyLine1	Primary - Debit Party Line1
POR.TRANSACTION	DebitCurrencyPair	Primary - Debit Currency Pair
POR.TRANSACTION	CreditMainAccountCompanyID	Primary - Credit Main Account Company ID
POR.TRANSACTION	CreditPartyLine1	Primary - Credit Party Line1
POR.TRANSACTION	CreditCurrencyPair	Primary - Credit Currency Pair
POR.TRANSACTION	FinalCodeWord	Primary - Final Code Word
POR.TRANSACTION	TransactionCurrencyCode	Primary - Transaction Currency Code
POR.TRANSACTION	HomeCurrency	Primary - Home Currency
POR.TRANSACTION	GLHomeCurrency	Primary - GL Home Currency
POR.TRANSACTION	InstructedCurrencyCode	Primary - Instructed Currency Code
POR.TRANSACTION	OutTransactionCurrencyCode	Primary - Out Transaction Currency Code
POR.TRANSACTION	DetailsOfCharges	Primary - Details Of Charges
POR.TRANSACTION	BusinessLine	Primary - Business Line
POR.TRANSACTION	OriginatingSource	Primary - Originating Source
POR.TRANSACTION	ReceivedSource	Primary - Received Source
POR.TRANSACTION	OriginatingChannel	Primary - Originating Channel
POR.TRANSACTION	SourceProduct	Primary - Source Product
POR.TRANSACTION	IncomingMessageType	Primary - Incoming Message Type
POR.TRANSACTION	OutputChannel	Primary - Output Channel
POR.TRANSACTION	OutgoingMessageType	Primary - Outgoing Message Type
POR.TRANSACTION	PmtMsgSent	Primary - Pmt Msg Sent
POR.TRANSACTION	CovMsgSent	Primary - Cov Msg Sent
POR.TRANSACTION	BatchIndicator	Primary - Batch Indicator
POR.TRANSACTION	SingleMultipleIndicator	Primary - Single Multiple Indicator
POR.TRANSACTION	SettlementTransactionIndicator	Primary - Settlement Transaction Indicator
POR.TRANSACTION	ServiceIdentifier	Primary - Service Identifier
POR.TRANSACTION	BankingPriority	Primary - Banking Priority
POR.TRANSACTION	ValidationFlag	Primary - Validation Flag
POR.TRANSACTION	ClearingNatureCode	Primary - Clearing Nature Code
POR.TRANSACTION	ClearingReturnCode	Primary - Clearing Return Code
POR.TRANSACTION	ClearingTransactionType	Primary - Clearing Transaction Type
POR.TRANSACTION	OutputChannelImposedFlag	Primary - Output Channel Imposed Flag
POR.TRANSACTION	ChequeType	Primary - Cheque Type
POR.TRANSACTION	CoverFlag	Primary - Cover Flag
POR.TRANSACTION	SkipFeeFlag	Primary - Skip Fee Flag
POR.TRANSACTION	SkipBalanceCheck	Primary - Skip Balance Check
POR.TRANSACTION	ClaimMethod	Primary - Claim Method
POR.TRANSACTION	BundledClaim	Primary - Bundled Claim
POR.TRANSACTION	AssociatedClaim	Primary - Associated Claim
POR.TRANSACTION	ClaimMsgSent	Primary - Claim Msg Sent
POR.TRANSACTION	SLAID	Primary - SLA ID
POR.TRANSACTION	CompanyBIC	Primary - Company BIC
POR.TRANSACTION	DefaultClientID	Primary - Default Client ID
POR.TRANSACTION	CompanyCountryCode	Primary - Company Country Code
POR.TRANSACTION	DefaultLanguageID	Primary - Default Language ID
POR.TRANSACTION	TimeZone	Primary - Time Zone
POR.TRANSACTION	FinalCodeWordText	Primary - Final Code Word Text
POR.TRANSACTION	OrderingPartyResidency	Primary - Ordering Party Residency
POR.TRANSACTION	OrderingPartyIBANCountry	Primary - Ordering Party IBAN Country
POR.TRANSACTION	BeneficiaryPartyResidency	Primary - Beneficiary Party Residency
POR.TRANSACTION	BeneficiaryPartyIBANCountry	Primary - Beneficiary Party IBAN Country
POR.TRANSACTION	STPEntryPoint	Primary - STP Entry Point
POR.TRANSACTION	RepairFlag	Primary - Repair Flag
POR.TRANSACTION	RiskFilterAuthorized	Primary - Risk Filter Authorized
POR.TRANSACTION	CancelFlag	Primary - Cancel Flag
POR.TRANSACTION	RejectFlag	Primary - Reject Flag
POR.TRANSACTION	ReturnTrigger	Primary - Return Trigger

Represents fields of POR.SUPPLEMENTARY.INFO and computed payment parameters. Only below computed values are allowed.

Local field name and value in POR.SUPPLEMENATRYINFO. In order to refine based on the local field name value, the user has to choose Secondary – Custom Attribute and define the local field name and value in the Value field. For example: Generated company>GB0010001
All fields in Level 2 and Level 3 across PP.HEAVYWEIGHTPRODUCTCOND, PP.MEDIUMWEIGHTPRODUCTCOND and PP.LIGHTWEIGHTPRODUCTCOND that are already not part of the Primary group.
Output channel of the original payment
Originating source of the original payment
Credit account type (Debit account type is already part of level 2 in PD)
For the following drop-down options, the user can provide the values from COUNTRY or COUNTRY.GROUP

Secondary - Beneficiary Party Iban Ctry
Secondary - Ordering Party Iban Ctry
Secondary - Originating Debit Party Country
Secondary - Sender Country
Secondary - Beneficiary Country

Following table provides the mapping between the fields in POR.SUPPLEMENTARY.INFO and the drop-down value to interpret and use for defining the rules

Table	Field Name	Drop-down Value
POR.SUPPLEMENTARY.INFO	RET.REJ.ORIGINATED.BY	Secondary - Return Reject Originated By
POR.SUPPLEMENTARY.INFO	MANUAL.RET.REJ.FLAG	Secondary - Manual Return Reject Flag
POR.SUPPLEMENTARY.INFO	RECALL.INDICATOR	Secondary - Recall Indicator
POR.SUPPLEMENTARY.INFO	PAYMENT.METHOD	Secondary - Payment Method
POR.SUPPLEMENTARY.INFO	CLEARING.SYSTEM.ID.CD	Secondary - Clearing System Code
POR.SUPPLEMENTARY.INFO	SCHEME	Secondary - Scheme
COMPUTED	Credit Account Type	Secondary - Credit Account Type
COMPUTED	Output Channel of Original Payment	Secondary - Orig Pymt Output Channel
COMPUTED	Originating Source of Original Payment	Secondary - Orig Pymt Originating Source
COMPUTED	Clearing Transaction type of Original Payment	Secondary - Orig Pymt Clearing Transaction Type
COMPUTED	Ordering Institution BIC Present	Secondary - Ordering Institution Bic Present
COMPUTED	Beneficiary BIC Present	Secondary - Beneficiary Bic Present
COMPUTED	OrderingParty IBAN Present	Secondary - Ordering Party Iban Present
COMPUTED	BeneficiaryParty IBAN Present	Secondary - Beneficiary Party Iban Present
COMPUTED	Chargeable Change	Secondary - Auto Repair Charged
COMPUTED	Ben Pty IBAN Ctry	Secondary - Beneficiary Party Iban Ctry
COMPUTED	Ord Pty IBAN Ctry	Secondary - Ordering Party Iban Ctry
COMPUTED	Originating DebitParty Country	Secondary - Originating Debit Party Country
COMPUTED	Sender Country	Secondary - Sender Country
COMPUTED	Beneficiary Country	Secondary - Beneficiary Country
COMPUTED	Receiver Country	Secondary - Receiver Country
COMPUTED	Debit Account Type	Secondary - Debit Account Type
COMPUTED	Source Group (Originating source)	Secondary - Source Group Type
COMPUTED	LOC.FIELD.NAME	Secondary - Custom Attribute

Represents BIC, LEI, Account, Clearing system code or clearing member ID for the following party roles.

Party Role	Party Role Name
ACWINS	Account with Institution
ASVINS	Account servicing Institution
BENFCY	Beneficiary
BENINS	Beneficiary Institution
DBTAGT	Debtor Agent
DEBTOR	Debtor
ORDINS	Ordering Institution
ORDPTY	Ordering Party
RECVER	Receiver
SNDCBK	Senders Correspondent Bank
SENDER	Sender
RCVCBK	Receivers Correspondent Bank
TRIMINS	Third Reimbursement Agent
INTINS	Intermediary Agent

The system does not support any other party apart from the mentioned above. Maximum of 10 attributes can be defined in a condition

Output Parameters of Refinement

Expand the following sections for more information on each output parameter:

Substitute

If the rule is satisfied, then the output that needs to be applied can be defined in this field. The output can vary based on the refinement record defined for various activation phases such as PRODET, DBTCC, CTRNS, CDTCC, FILTER, and CHARGE.

Activation Phase	Description
PRODET	Any output of Heavy, Medium or Light weight product condition
DBTCC	Client conditions product, Routing product, Impose Routing product flag, Filtering product, Debit book code, Credit book code, Debit charge book code, Credit charge book code, Debit VAT book code, Credit VAT book code, Fee product, output channel, posting product
CTRNS	Routing product, Impose Routing product flag, Filtering product, Debit book code, Credit book code, Debit charge book code, Credit charge book code, Debit VAT book code, Credit VAT book code, Fee product, posting product, output channel. CTRNS is applicable only for outward and redirect credits.
CDTCC	Client conditions product, Filtering product, Debit book code, Credit book code, Debit charge book code, Credit charge book code, Debit VAT book code, Credit VAT book code, Fee product
FILTER	Filtering product, Debit book code, Credit book code, Debit charge book code, Credit charge book code, Debit VAT book code, Credit VAT book code, Fee product, posting product
CHARGE	Fee product, posting product

It is possible to define multiple substitute field but the feature is limited to unique values. The system does not allow duplicate fields and values.

Substitute Value

If the rule is satisfied, then the value of the output that needs to be applied can be defined in this field. This field supports the following values.

ORIG.PAYMENT.CREDIT.BOOK.CODE
ORIG.PAYMENT.DEBIT.BOOK.CODE
ORIG.PAYMENT.DR.CHG.BOOK.CODE
ORIG.PAYMENT.CR.CHG.BOOK.CODE
ORIG.PAYMENT.CR.VAT.BOOK.CODE
ORIG.PAYMENT.DR.VAT.BOOK.CODE

It is possible to refine based on local field conditions in payment processing. Refer to the Refining Payment Processing using Local Field Names and Values section.

Below screenshots represent the input and output parameters of the Refinement table.

Refining Output at Product Determination Stage

Following steps explain how to refine product determination.

To configure the refinement, go to Admin Menu > Payments > Payment Hub > Bank operations configuration > Product determination > Define product output refinement.
In the Product Output Refinement section, select the Product Condition (heavy or medium or light) to be refined (user can select any PD ID for which the output of the product is to be refined) and select Product Determination in the dropdown.
Configure the conditions in the Refinement tab.

In PRODET activation phase - Any output of Heavy, Medium or Light weight product condition can be refined. After validating the descriptions and conditions that are configured in the Refinement tab, the user can view them in the Derived Rule tab. If the condition mentioned in the derived rule is satisfied, then the particular refinement becomes successful.

Configure the condition and commit the record.

Refining Output at Debit Client Condition Stage

The following sections explain how to refine debit client condition using product determination ID and client condition output derived from product determination. The user can use anyone of the methods.

To configure the refinement, go to Admin Menu > Payments > Payment Hub > Bank Operations Configuration > Product Determination > Define Product Output Refinement.

Refining Output at Routing and Settlement Stage

The following sections explain how to refine routing and settlement using product determination ID and routing product output derived from product determination.

To configure the refinement, go to Admin Menu > Payments > Payment Hub > Bank Operations Configuration > Product Determination > Define Product Output Refinement.

Refining Output at Credit Client Condition Stage

The following sections explain how to refine credit client condition using product determination ID and credit client condition output derived from product determination. To configure the refinement, go to Admin Menu > Payments > Payment Hub > Bank Operations Configuration > Product Determination > Define Product Output Refinement.

The user can follow either one of the following procedures. If both are configured the refinement using product determination ID takes precedence.

Refining Output at Filtering Stage

The following sections explain how to refine filtering product using product determination ID and filtering product output derived from product determination. To configure the refinement, go to Admin Menu > Payments > Payment Hub > Bank Operations Configuration > Product Determination > Define Product Output Refinement.

The user can follow either one of the following procedures. If both are configured the refinement using product determination ID takes precedence.

Refining Output at Fee Stage

The following sections explain how to refine fee product. To configure the refinement, go to Admin Menu > Payments > Payment Hub > Bank Operations Configuration > Product Determination > Define Product Output Refinement.

The user can follow either one of the following procedures. If both are configured the refinement using product determination ID takes precedence.