8/13/2021 Account

 > Temenos Transact >

Home

Account
AA products which are account based, use the Account Property Class to create the associated account record for an arrangement of the product.

This Property Class manages the descriptive and classification details of an arrangement and is used to create and maintain the account record that
is related to the arrangement.

Although account names are account specific, the user can also default the generic titles from the product and replace or give additional details at the
arrangement level.

Product Lines

The following Product Lines use the Account Property Class:

Accounts
Agent
Deposits
External Accounts
Facility
Insurance External Product
Lending
Rewards
Safe Deposit Box

Property Class Type

The Account Property Class uses the following Property Types:

Dated
Enable External
Enable External Financial
Enabled For Memo
Variations Supported

All attributes in the Account Property are stored at the arrangement level and do not track the underlying product.

Property type

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 1/10
8/13/2021 Account

Creation of Temenos Transact Account

When the user creates a financial arrangement, the system generates a Temenos Transact account record. The account record generated is
allocated a standard Temenos Transact account number according to the rules defined in the COMPANY application.

The ACCOUNT application needs to be configured to generate IDs automatically, for the arrangement module to generate an account record.

The Account record is built by mapping the relevant fields from the DEPT.ACCT.OFFICER, CUSTOMER, ACCOUNT and LIMIT properties of
the arrangement into the layout of the account record.
The Account record created cannot be modified directly using the ACCOUNT application, instead the associated properties have to be modified
using the appropriate maintenance activities from AA.ARRANGEMENT.ACTIVITY. The Account record holds the arrangement number in the
Arrangement ID field.
The difference between the arrangement account records and Temenos Transact accounts are as follows:
There is no CONDITION.GROUP allocated.
The Interest and Charges module does not apply to these accounts.

Using the Arrangement Account in Other Temenos Transact Applications

In order to pay funds into or withdraw funds from an arrangement, any existing Temenos Transact application that allows an account to be
defined, can be used, for example FUNDS.TRANSFER or TELLER.

In the application, the user can specify the account number, mnemonic, any alternate account ID linked or the arrangement number, when the
arrangement is in the same company as the transaction. To use the arrangement account in an application, in a different financial company to
the arrangement, the actual account number is the only option allowed.
The Alternate Acc IDs field is set to Y in ACCOUNT.PARAMETERto specify the arrangement number or an Alternate Account Number.

The FUNDS.TRANSFER application can be used to drawdown and commit or deposit funds to an arrangement. The Debit.Acct.No and
Credit.Acct.No are used to debit or credit the account record associated to the AA.ARRANGEMENT respectively.

Balance Prefix and Suffix

Account Property Class holds the below Balance Prefix:

Lending - Current, Due, Aged, Unspecified, Unallocated Debit, Available

Deposits - Current, Due, Aged, Unspecified, Unallocated Debit, Expected, Payable
Accounts - Current, Unspecified, Unallocated Debit
Agent - Unspecified
Safe Deposit Box - Current, Unspecified, Expected, Unallocated Debit
External Financial - Current, External

Related Balances

Loans

Current Principal Balance

For a loan contract, the current principal reflects the amount that has been disbursed and is not yet due to be repaid. The current
principal is identified with a prefix ‘CUR’.

Due Principal Balance

For a loan contract, the due principal reflects the loan amount that has been disbursed and is now due for repayment. The due principal
is identified with a prefix ‘DUE’.

Aged Principal Balance

For a loan contract, the aged principal balance reflects the due amounts of the loan that has aged, according to the stages defined in
Overdue property condition.

Due balances are aged, when the date since the bill that generated the due balance, passes the number of days specified in the
Overdue property condition. The billed balance assumes the associated status defined in the condition record. For a single arrangement,
there may be several aged and due balances reflecting the different ages of the outstanding bills.

The aged principal balance is identified with a prefix of the associated status in the OVERDUE property.

Unallocated Credit Balance

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 2/10
8/13/2021 Account

The unallocated credit balance reflects general credits made to the arrangement. This balance is also used to hold payments made
against future or issued bills prior to the due date. If the practice (defined in PAYMENT.RULES property) requires that advanced
payments not repaying the current principal, then, the repayment amount is allocated to the unallocated credit balance. The unallocated
credit balance is identified with a prefix ‘UNC’.

Unallocated Debit Balance

The unallocated debit balance reflects general debits made to the arrangement. It is identified with a prefix ‘UND’.

AVL - Available Balance

This is used for scheduled disbursement. It indicates the loan amount available for disbursement. This is a contingent credit balance on
the loan which is credited when the disbursement bill is made payable.

Deposits
The Deposits Product Line can have the following balance prefixes:

Expected Principal Balance

When a new arrangement is created, system credits this balance type to indicate the pending payment is awaited from the customer.
Currently, the sign is positive. The expected principal is identified by the balance prefix ‘EXP’.

Current Principal Balance

The current principal balance reflects the payment made by the customer towards the deposits. It may or may not be equal to the
expected balance. It is identified by the balance prefix ‘CUR’.

Aged Expected Balance

This is used in cases where the customer has not made payments on time and expected principal becomes overdue.

Unallocated Credit Balance

The unallocated credit balance reflects the general credit made to the arrangement. This balance holds the additional payments made
against the deposits. For example, when a new deposit new arrangement is created for 25000 USD and customer makes a payment of
50000 USD. In this case, it is possible to post 25000 USD in UNC balance.

Accounts

Current Account Balance

When a current or savings account is created, it is possible for the debits and credits for these account to update the relevant account
balances. All interest calculations are done based on these balances.

Attributes
Attributes associated with the Account Property Class are described below.

Account Definition at Product Level

Reporting Classification
In an AA product, the Category is used for reporting (that is, balance sheet) purposes only. Usually, a category is allocated to a specific
product or family of products, although this is not mandatory. The category can be amended, if required, at the arrangement level.

Generic Arrangement Titles and Names

Although account names are account specific, generic titles can be defaulted from the product in the Account Title field and can be replaced
or given additional detail at the arrangement level.

The Short Title field is an abbreviation of the account title and is used for enrichment.

Currency Market and Position Type

The Currency Market of an arrangement can currently be set to ‘1’ only, and Position Type can be set only to ‘TR’.

Account Definition at Arrangement Level

Attributes used in account definition at arrangement level is described below.

Arrangement Titles and Names

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 3/10
8/13/2021 Account

Product definition defaults Account Title and Short Title and can be overridden if allowed by the product attribute control settings. Customer
Reference allows a reference known by the customer of the arrangement, to be specified for information.

Alternate References
The following options are available for specifying alternate access references for the account.

Mnemonic field is an alternate key which can be defined by the user to reference the account. This is the name of the arrangement.

Alternate.ID field is multi-valued in ACCOUNT.PARAMETER, which is linked to the ALT.ACCT.PARAMETER file where alternative references
can be specified.

This is used to record other references by which the arrangement may also be referred.

If an IBAN number has to be generated for this product, then the value has to be set to ‘Yes’ against Generate IBAN field. The number is
auto generated for accounts that are created under this product.

Balance Treatment
Specifies if the account is off-balance or on-balance.

Off-balance accounts maintain principal balance in CUR<ACCOUNT>INF balance type as opposed to CUR<ACCOUNT> balance type.

Valid options are as follows:

Memo - Indicates the account is an off-balance account. When set to ‘Memo’, the system expects a special balance type
CUR<ACCOUNT>INF with reporting type set to ‘Internal’. Only the following accounts can be set to Memo:

AR accounts if BN (Balance Netting) is installed in the company.

External Financial Accounts (XP).
Null - Indicates the account is a real account.

External Posting
Specifies if accounting can be directly raised (either within Temenos Transact or outside of Temenos Transact) to the account. This is
mapped to EXTERNAL.POSTING in base account record. Valid options are as follows:

Yes - Accounting can directly be raised to the account. Null also indicates the same functionality as selecting ‘Yes’.
No - Accounting cannot be directly raised to the account. Any accounting on this account can only happen as a result of a posting
happening on one of its child accounts.

Multi Currency
Specifies if the account supports multiple or single currency. Valid options are as follows:

Yes - Account supports multiple currencies and accounting respects an entry in a different currency and starts maintaining balance.
No - Account does not support multiple currencies. Null also indicates the same functionality as selecting ‘No’.

On Restructure
The possible values for On Restructure are as follows:

Capitalise - Internal restructure capitalises the current period interest and charges defined in the payment schedule condition.
Null - Internal Restructure does not capitalise the current period interest and charges defined in the payment schedule condition.

Early Processing
Indicates that the schedule has to be processed intra-day instead of, during the scheduled Close of Business. Early Schedule processing is
the process of scheduling interest and charges on the scheduled date but earlier than the COB. This process gives flexibility to the financial
institutions in dealing with interdependencies between Temenos Transact and other systems with respect to interest and charges posting.

HVT flag
The HVT flag if set to ‘Yes’ Iindicates whether if the account is a High Volume Transaction account. This is applicable for Accounts product
line.

Passbooks for Arrangements

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 4/10
8/13/2021 Account

Passbook field in the Account Property Class, controls the printing of the passbook for an account. It is valid for any arrangement contract
with a category code defined in the SAVINGS record of ACCOUNT.CLASS application.

It is possible to change the value of the Passbook field from ‘Yes’ to ‘No’, and ‘No’ to ‘Yes’ for the existing arrangement, through update
Activity - ACCOUNTS-UPDATE-<ACCOUNT>.

Date Settings
Base Date Type field is used by AA to calculate several of the other Date fields of the arrangement and accepts values : ‘Agreement’ or
‘Start’ (Agreement is the default).

Agreement option results in other dates being calculated based upon the effective date of the New-Arrangement activity.
Start option results in other dates being recalculated when the first Disburse or Deposit activity occurs.

Anniversary field is used to store the anniversary of the account for restriction purposes and its value is stored in the format <MM DD>. In
conjunction with restrictions, this field can also be used for general configuration across all AA.PERIODIC.ATTRIBUTES classes.

Date Convention and Date Adjustment

Date Convention and Date Adjustment settings indicate the action which can be taken if the derived date is a non-working day. There are
four Date Convention options.

Backward - the payment date moves backward to the last working day.
Calendar - the payment date does not move regardless of whether it is on a working day.
Forward - the payment date moves forward to the next working day.
Forward Same Month - the payment date moves forward to the next working day provided it is within the same month. If it is not within
the same month, it is possible for the payment date to move backward to the last working day.

For all date conventions except ‘Calendar’, Date Adjustment is used to specify whether the new date represents an adjustment of the ‘Value
date’ of the entries or an adjustment of the ‘Period’ (both value and processing dates).

The holiday schedule for the country of an arrangement’s currency is referred to for determining the non-working days. Users can add
additional countries using Bus Day Centres field whose calendars can also be checked with regard to holiday validation.

In case of month end schedules please refer Month End Repayment Schedule in Payment Schedule property class.

Shadow Account
While entering new arrangement for account creation, system updates this field based on the value specified in the product condition of
Account property class.

If this field has 'YES' as value, then the balance details of this account is not maintained within Temenos Transact and it is held by an
external DDA system. Within Temenos Transact, only static information of this account is maintained.

If this field has the default NULL value, then it is like a normal Temenos Transact account, so and the balances are maintained by Temenos
Transact.

Inactive Months
Indicates the number of months (which can carry any values between 1 and 99) without customer activity before an arrangement account is
declared as ‘Inactive’. Based on this value, only the arrangement accounts are marked as ‘Inactive’. This field is mutually exclusive with
Dormancy property class.

Base Date Key

This provides the user with the option to specify the basis for deriving the future event dates. This definition is currently used for deriving
dates of Change Product, Rollover or Renewal and Periodic reset events only. The values allowed are as follows:

Previous – Last adjusted event date is used for deriving subsequent event date(s)
Base – Last unadjusted event date provided by user is used for deriving subsequent event date(s)
Null - Change Product, Rollover or Renewal events Base date is used for deriving every event date(s)

Periodic reset event actual date is used for deriving every event date(s)

Referral Code

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 5/10
8/13/2021 Account

This field is optional, multi-valued, has no default value,and does not allow duplicates . It specifies the conditions under which account
details or details of entries over the account are to be included; in an end of day report for referral to the account officer responsible. Referral
conditions can be defined depending on transaction such as transaction code, amount and sign, or the balance of the account. The code has
to be a valid record in REFERAL Table

Portfolio ID
An arrangement can be linked to customer's portfolio reference (SEC.ACC.MASTER ID) using this field. When the portfolio is linked, the
arrangement is also taken into consideration during portfolio valuation for the customer. This is not relevant for product conditions. The
portfolio reference has tp belong to the customer of the arrangement.

Parent Bv Date
Holds the date of the latest internal restructuring of the network of parent accounts above this account, that is, the latest date when the
network of parent accounts above this account, was changed. If the back value date of the statement entry is prior to this date, then the
statement entry copied to the parent account is adjusted to this date. The original statement entry is not impacted.

Allowed Bv Date
Holds the latest restructuring date of the network of parent accounts above this account. It is set to the date when an account was added to
the network of parent accounts as either a direct or indirect parent of this account. If the back value date of the statement entry is prior to this
date, then the transaction is rejected with an error message.

Balance Conversion Market

The currency market to be used for merging balances in multi-currency accounts and limit validations is indicated against this field. If it is not
entered, the currency market of the account is used.

Limit Account
Indicates if account is a contingent account created for limit balance purposes.

Read Accounts user guide, overdraft limits section for more information.

Posting Restriction
At the arrangement level, a posting restriction code (defined in POSTING.RESTRICT) can be used to restrict the following:

All Debits
All Credits
All Transactions

Other fields defined related to Posting Restriction multi-value group are:

Start Date
Used to specify from when posting restriction is applicable for the arrangement. When start date is a future date, then during Start of Day
(SOD), base account is updated with posting restriction.

There are two ways to effect the restriction immediately.

When the Start date is left blank, then the restriction is effected immediately.
When the Start date is defined as current system date, then restriction is effected immediately.

It is not allowed to be prior to:

Arrangement start date

Current system date, if arrangement activity date is backdated

NOTE: It is not allowed to update start date, once restriction is active.

Expiry Date
Used to specify when posting restriction finishes.

When expiry date is a future date, then during start of day, posting restriction is removed from base account record.
When expiry date is not defined, then it is meant that the posting restriction is for the entire life of arrangement.

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 6/10
8/13/2021 Account
NOTE: It is not allowed to be before arrangement start date; it is not allowed to be before start date.

Blocking or Unblocking Reason

Pre-defined set of blocking code that are defined in EB.LOOKUP ( BLOCK.REASON.CODES or UN BLOCK.REASON.CODES virtual table) is
linked to each posting restriction. Each blocking or unblocking code is linked to corresponding posting restriction by defining them in posting
restriction table without which the system does not allow to link the blocking or unblocking code.

Blocking or Unblocking Free Text

Used to capture free text information.

Balance Netting
Attributes related to balance netting are described below.

Memo Accounts

Balance Treatment attribute allows to define an Account product to be off-balance sheet.

When this is set, during Proof and Publish, and at arrangement level, system expects a Balance Type for the Account property
with a suffix ‘INF’ and that balance type has to be set with Reporting Type as ‘Internal’. For example, if BALANCE is the name
of the Account property, then this AC balance type is ‘CURBALANCEINF’.
Even if an account is set as Off- Balance (Memo), it is a fully operational account from a customer perspective (Cheques can be
issued, incoming or outgoing payments can be handled as usual).
All transactions posted are converted to a memo posting on this account and the real entry diverted to the linked real account
(specified in Linked AC Number).
All Interest and Fees specified on this Memo Account is treated as Memo Interest or Fees. The system automatically suppresses any
real accounting to the PL and Payables or Receivables.

It is still possible to specify capitalisation frequencies for these Memo Interest or Fees

Read Settlement Property Class for more information.

Link Ac Number attribute is used to specify any diversion account, at the arrangement level.
This then gets mapped to the Auto Pay Acct field in account record.
For a normal AR account to have Link AC Number populated would simply translate into the Auto Pay Account feature (where
the incoming Real entry is simply diverted to the linked account).

Read Financial Accounting user guide to know more on Memo Accounting Entry for Transaction Accounts.

Parent Account attribute is used to specify any parent account within a bundle hierarchy, at the arrangement level.
Input in this attribute is not allowed if the arrangement is not part of a bundle hierarchy.
These memo accounts can be on their own or as part of a bundle (Balance Netting) hierarchy

Read Balance Netting user guide for more information.

When part of a hierarchy, they can either be the accounts on which transactions are done performed or as a Summary Account.
When defined as a Transaction Account, it is important that they are linked to a Real Account for funds diversion so as to reflect the
aggregate position per currency. The Link AC Number attribute is used for that purpose.

The External Posting attribute is used to control who can raise postings on the account.

If it is set to ‘No’, the system does not post the transactions directly on these accounts; and that any posting on these accounts is only
a result of a posting happening on one of their child transaction accounts; or, as a result of funds diversion from a memo transaction to
an On-balance account.
The term External means any application outside the core accounting engine, which means even AA’s own schedule processing
cannot raise any accounting that hits the Principal Balance of that account (for example, Capitalise ).

Transactions on a TR Account in a Pool

The system, uses the Link Ac Number, to do memo posting on the TR account and a real posting on the relevant CT account, when a
credit or debit hits a TR account.

Using the PARENT.ACCOUNT at every level (TR, CS, SA and etc), the system also knows to raise memo posting on the parent accounts as
well.

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 7/10
8/13/2021 Account

EXAMPLE: Hierarchy where SA1 is the Parent of CS1, CS1 is the Parent of TR1 and CT1 is the corresponding Currency Top
Account, a Debit hitting TR1 results in the following:
Memo Dr on TR1

Real Dr on CT1

Memo Dr on CS1 (because it is defined as the PARENT.ACCOUNT in TR1)

Memo Dr on SA1 (because it is defined as the PARENT.ACCOUNT in CS1)

When a transaction is done on the TR, it can be observed that it is reflected as a memo on the TR, memo on SA and a real posting on
the CT. Individual Posting is reflected on the Linked AC Number (CT Account). The relevant balances are also updated in
EB.CONTRACT.BALANCES.

Multi Currency Memo Accounts

Multi.Currency attribute allows to enable a memo account to maintain balances (ACCT.BALANCE.ACTIVITY and
EB.CONTRACT.BALANCES) in currencies other than the currency of the account itself.
A multi-currency summary account in a Balance Netting Hierarchy can have children belonging to any currency.
Whenever a transaction hits the child, it gets replicated at the parent summary level. If this parent summary account is enabled for
multi-currency, then system starts to maintain its balance based on the incoming currency.
Accruals and Capitalisation or Make-Due or Pay still happens only in the currency of the account but the system can convert the
balances across currencies into the account currency and aggregate them as the source balance.
Balance Conversion Mktattribute can be optionally used to dictate the rates with which this Conversion (both at Limit Check and
Interest Processing) happens.

Arrangement Condition
The following attributes in Account property class are better captured at the arrangement level:.

Bundle Arrangement - used to capture the Arrangement reference of the Bundle Hierarchy
Link AC Number - the On-balance sheet diversion account
Parent Account - Parent account within the Bundle Hierarchy (Input is allowed only if Bundle Arrangement is specified)

Periodic Attribute Classes

Full Deposit - Periodic rule to control the deposit of full commitment amount.

Actions

The Account Property Class supports the following actions:

Action Name Description

ADJUST.BILL Used to adjust the account balance in a bill.

ADVANCE.REPAY Used when balances are paid in advance.

AGE.BILLS Used to age the Account balances that are overdue

ALLOCATE Used for Balance Update in Account

AUTO.CLOSE Used to auto close dormant account

AUTO.CLOSE.VALIDATE Used to validate the account to be closed

BALANCE.MOVEMENT Used during migration from AC to AR Account for Account balance movements.

BALANCE.TRANSFORM Used to raise entries for CUR<ACCOUNT> to AASUSPENSE

CANCEL.DEPOSIT Used during cancellation of a deposit arrangement

CANCEL.LENDING Used during cancellation of a loan arrangement

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 8/10
8/13/2021 Account

Action Name Description

CAPTURE.BILL Captures the Account details of the bills to be generated for the Lending, Deposits, Savings and Accounts product
lines.

CHANGE Used to update changes in the Account condition

CHARGEOFF Used to chargeoff the balances

CHECK.CANCEL Used to check for cancel period while funding or disbursing in an arrangement

CHECK.MEMO Used to check memo account

CLOSURE.VALIDATE Used to check the closure validations

CR.MOVEMENT Applies the credits to the arrangement Account Product Line for the current account balance.

CREATE.INVOICE.BALANCE Used to Create invoice balance based on working balance

CREATE.INVOICE.BILL Used to Issue bill for invoice balance

CREATE.RESIDUAL Used during creation of the residual amount of amortisation

CREDIT Applies the unallocated amount from a credit to the[GPD1] arrangement , to the unallocated credit balance of the
arrangement.

CREDITPRENOTE Used when during Credit action when Temenos Transact is either shadow or DDA

DATA.CAPTURE Used during data capture from legacy account to AR Account

DEBIT Applies the unallocated amount from a debit to the arrangement to the unallocated debit balance of the
arrangement.

DELINK Used in Balance Netting to delink an account

DEPOSIT Used during Deposit in Account

DISBURSE Used when a loan is disbursed. The action results in the current balance of the account property being debited.

DR.MOVEMENT Applies the debits to the arrangement Account Product Line for the current account balance.

EXPIRE.BILL Used in Expire Bill Action for Account Property Class

FORCE.CLOSE Used to clear external balances and force close an arrangement

FORCE.SUSP.TRANSFORM Used in Suspense for all forms of interest and charges in payment schedule

FORCECREDIT Used in Force Credit action of external DDA

FORCEDEBIT Used in Force Debit action of external DDA

FUTURECREDIT Used in future dated Force Credit action of external DDA

FUTUREDEBIT Used in future dated Force Debit action of external DDA

ISSUE.CLOSURE.BILL Used to issue closure bill for an arrangement

MAINTAIN Used whenever one of the properties linked to the Temenos Transact ACCOUNT record (CUSTOMER,
DEPT.ACCT.OFFICER, LIMIT, ACCOUNT) is modified. The action does not generate any accounting movement
but updates the related Temenos Transact ACCOUNT record to reflect the values for the arrangement property.
This results in the creation of a Temenos Transact arrangement account when the New-Arrangement activity is
processed. A scheduled MAINTAIN account activity LENDING-MAINTAIN-ACCOUNT is raised for the future
effective date, that is processed in the Start of Day of the effective date. The MAINTAIN activity updates the
ACCOUNT record with the future dated changes.

MAKE.DUE Applies the amount of principal due to be repaid to the DUE account property balance and reduces the current
account property by the amount to be made due. The amount to be made due is determined from the associated
bill that is being made due.

MOVE.BALANCE Used as a routine to move the PAY account balance to an internal account

OFFSET.INVOICE.BALANCE Used to Offset the invoice balance based on capitalise amount

PAY Used in Payout action for Accounts

RECEIVE Used in to Receive funds in an Account

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acco… 9/10
8/13/2021 Account

Action Name Description

REDEEM Used when an arrangement is matured and balances are to be redeemed to customer.

REPAY Allocates an amount of principal to be repaid to the appropriate account balance. Depending on the
PAYMENT.RULE applied, the repayment is made against billed or current amounts.Processing determines the
amount and balance to be credited based on the PAYMENT.RULE definition and can result in credit being applied
to the CUR, DUE or AGED balances of the account property.

RESERVEFUNDS Used for Debit action when Temenos Transact is either shadow or DDA

RESIDUAL Used to allocate Residual funds in an amortisation schedule.

RESTRUCTURE Used in Balance Netting to restructure an arrangement.

SETTLE.SUSP Used when suspended balances are settled

TRANSFORM Used to raise entries for AASUSPENSE to CUR<ACCOUNT>INF

UPDATE Used to apply the changes to the Account property attributes and does not result in any accounting updates.

UPDATE.APR Used to update the Annual Pay Rate (in APR calculation) - Apr Type and Apr Rate in the account condition

Accounting Events

The following actions generate accounting events as defined in Accounting field.

CREDIT
CR.MOVEMENT
DEBIT
DR.MOVEMENT
DISBURSE
MAINTAIN
MAKE.DUE
REPAY
CAPTURE.BILL
ADJUST.BILL
RESIDUAL
AGE.BILLS
ADVANCE.REPAY

Limits Interaction

The Account property does not directly interact with the LIMITS system, but the associated arrangement account record is closely linked.

The Limit Property Condition specifies the LIMIT.REFERENCE to be used for the arrangement product and this is the limit reference used in the
related ACCOUNT record.

Published on :
Copyright © 2020-2021 Temenos Headquarters SA Monday, July 19, 2021 7:37:10 PM IST

file:///D:/DOCUMENTS/USER-GUIDE-21/docs/Solutions/T24_Transact/Product_Management/AA/Arrangement_Architecture/Property_Classes/Acc… 10/10