Statement
Account statements can be generated based on the setup in Account application or Arrangement Architecture. Statement Property Class is used to configure the Statement setup in the AA Framework.
Product Lines
The following Product Lines use the Statement Property Class:
- Agent
- Account
- Deposits
- Facility
- Lending
- Rewards
- Safe Deposit Box
Property Class Type
The Statement Property Class uses the following Property Class types:
- Dated
- Enable External
- Enable External Financial
- Enabled For Memo
- Variations Supported
- Tracking
Property Type
The Statement Property Class is not associated with any Properties.
Balance Prefix and Suffix
The Statement Property Class does not hold any balances.

This attributes in each tab in the Statement Property Class are described below:

The following are the attributes in the Account Stmt tab:

This field specifies the start date and frequency for producing the regular (cycle 1) account statement. Statement of each cycle shows the details of all entries in the cycle since the last statement and regardless of other cycles.
This field value can be defaulted based on the customer preferences setup in DE.CUSTOMER.PREFERENCES. It can be sub-valued to provide other specific dates in a month for recurring statement generation. In this case, entries from the last statement date in cycle 1 are printed for each sub-valued date. The supported frequencies are:
- Daily
- Weekly
- Monthly
- Defined

This field specifies the start date and frequency for producing the account statement for additional statement cycles (2 to 9). The field in this cycle can also be sub-valued as mentioned in cycle 1. The supported frequencies are:
- Daily
- Weekly
- Monthly
- Defined

This field includes the details of the account movements and generating a detailed statement is optional. When the Detailed Statement field is set to Yes, the account statement includes the details of the movements; else, the summary information alone is updated.

This field specifies if:
- The cycle 1 statements should be printed
- There have been no movements over the account since the last statement.
The options in this field are:
- Y - Select to generate statements on the dates specified, regardless of any movements.
- No - Select if there are no movements since last statement and the statement is suppressed.
- No if 0 Balance - Select if the account has no movements during the statement period and the ledger balance is zero and the statement is suppressed.

This field allows generating special statements on multiple dates and the user can specify the unique set of dates upfront in specific frequency.
To have fixed set of unique statement dates instead of the regular frequency, the Follow Spl Stmt field should be set to Yes. The regular statements get discontinued and printed on specified unique dates. Special statements can be suppressed if account has zero balance and no movement in statement period.

The Print Attribute Name/Value associated fields given below in Statement Property Class enable the user to print the statements with or without images.
- Printing Option
- Statement Image
The Attribute Name is set at the product condition level and can be made non-negotiable at the arrangement level so the user or the customer can change only the Attribute Value from the options available. These are passed along with the statement output to be sent to a downstream system such as printing solution. These values can be defaulted based on the customer preferences setup in DE.CUSTOMER.PREFERENCES. In case of joint owners, the system defaults based on the values given for the first customer set up as Beneficial Owner.

This field specifies the account format enquiry, which is defined as a record from Print Statement.

This multi-value field indicates the optional add on formatting enquiry.
- Allowed add ons are defined in the Print Statement record of the Statement Type chosen. The system validates if the Add-on is an allowed Add-on for this Statement Type.
- Statement Add-On can be left negotiable to be chosen at the account level.
- It is also optional to print the Add-on statement in a new page.
Read the Account Statements feature for more information.

The following are the attributes in the Account Stmt (Additional) tab:

This field specifies if the statements should include any customer narrative entered at the time contracts.
- If this field is set to Y, the customer narrative may be printed on account statements, in addition to the standard transaction narrative .
- When the account statement records are generated automatically on account opening, this field is set to the value defined in AC.STMT.PARAMETER if available.
- Otherwise the field is set to NO, but it can subsequently be amended manually if required.

This field specifies the message type as either 941 or 942.
- Applicable value for 941 is STP to generate MT941 during the day on receipt of Inward MT920
- Applicable values for 942 are:
- Yes - To generate through DE.MT942.REQUEST
- No
- STP - To generate MT942 on receipt of Inward MT920

This field allows sending the following messages on ad-hot or timed daily basis.
- MT941 (Balance Report)
- MT942 (Interim Transaction Report)

This field allows sending the messages such as MT942 or CAMT052 on an ad-hoc basis. Messages can only be sent automatically if this field contains data. The format of message times should be hh:mm format. Where,
- hh is the hour (in 24 hour format)
- mm is the minutes past that hour.

This field is used in conjunction with the MT942 fields. This value is used as the floor limit indicator for the debit transaction on the Interim Transaction Report, and it is used to exclude smaller entries from the message details. On this message, when only one value is used, the floor limit applies to both debit and credit amounts. If this field is left blank, then ’0’ is used, which means all entries are detailed.

This field is also used in conjunction with the MT942 fields. This value is used as the floor limit indicator for the credit transaction on the Interim Transaction Report, and it is used to exclude smaller entries from the message details. On this message, when only one value is used in Debit Floor Limit, the floor limit applies to both debit and credit amounts. If this field is left blank, then ’0’ is used, which means all entries are detailed.

The Stmt Info Property indicates the Interest and Charge property to be printed in account statement. EIR can be calculated and printed in account statements. Only the interest property indicated in Stmt Info Property would contribute to EIR.
When EIR has to be calculated on the local requirement, the Rate Info Routine field can be used to indicate the local routine that can be attached for the API as per the requirement of the bank.

This field specifies the Property names whose information have to be printed in the account statement. This is a multi-value field and accepts a valid Interest or-and Charge Property, which belongs to the current product.
It indicates the Property for which rate change has to be recorded. The corresponding enquiry is added in a PRINT.STATEMENT record and linked as Allowed Addon in PRINT.STATEMENT of the account. It is possible to print the add on in a new page by setting Addon New Page as Y.

The following are the attributes in the Interest Statement tab:

When this field is set to Y, that is ,whenever an interest is applied, a detailed interest statement (scale) is produced, and the interest rate applied for the specified period with the accrual information can be obtained.

This field allows generating an advice when interest and charges are applied.

Interest Statements can be produced during COB on the given frequency for the specified properties. The set of associated multi-valued fields such as Stmt Frequency, Stmt Name and Property indicate the frequency to generate interest statements. For more information read account statements

When this field is set to Y, it indicates the consolidation of individual statements based on customer choice for arrangements. Arrangements here include loans, deposits, accounts and AA external plus arrangements.

It is a multi-valued field that specifies the participant account in a combined statement. When set, this frequency number for the participant account is synchronized with the lead account and individual statement generation is suppressed.

This field holds the reference to the lead account in the combined statement. When a combined statement is defined and committed, the system synchronizes the statement frequencies of the participant account with that of the lead account. Additionally, the system updates this attribute with the lead account reference,
Read the Account Statements feature for more information.
Add Statement Property to Existing Arrangements
The financial institutions can add the Statement property to the existing arrangements of the Accounts, Deposits, Lending, and Multi-Currency Accounts product lines using the Add New Property, New Prop Avl, and New Prop Avl Date fields in AA.PRODUCT.MANAGER.
Read Add New Property for more information on the configuration.
Periodic Attribute Classes
There are no periodic attribute classes associated with Statement Property Class.
Actions
The Statement Property Class supports the following actions.
Action Name | Description |
---|---|
DATA.CAPTURE | During the migration to AA, statement details can be captured using the Data.Capture action. |
PRODUCE.STATEMENT | Interest statements can be captured using the Produce.Statements action. |
SCHEDULE.STATEMENT | Interest Statement Action for the Statement can be scheduled using the Schedule Statement action. |
UPDATE | Statement Arrangement Condition record can be updated using the Update action. |
Accounting Events
The Statement Property Class does not perform actions that generate accounting events.
Limits Interaction
The Statement Property Class does not perform actions that impact the limits system.
In this topic