Introduction to ISO20022-Account Reporting(IX)

The camt message produced by Temenos Transact is aligned with the Dutch-specific usage rules, as set by the Dutch Banking Association (NVB).

The NVB guidelines include the usage rules for the reporting of SEPA credit transfers and Single Euro Payments Area (SEPA) direct debits. The SEPA details required under NVB are reported in the camt statement if the required information is available in Temenos Transact.

A camt message has a nested structure with the building blocks as shown in the image below. The Temenos Transact Camt module is responsible to assemble the data necessary to produce a camt message for each statement triggered.

The camt.053 and the camt.052 messages both have the same structure, except that the header name is different.

• Camt.053 message has the following structure:

Bank to Customer Statements:

• Group Header
• Statement
• Entry
• Transaction Details
• Camt.052 has the following structure:

Bank to Customer Account Report:

• Group Header
  • Report
  • Entry
  • Transaction details

The following image shows the structure of a camt.053 message.

• Group Header (Statement Level Information):

The Group Header block of the camt message provides the information related to the statement and is specified for the camt message. This section of the message is mandatory.

It contains information like Message Identification, Pagination, Message Recipients and so on.

• Statement or Report (Account Level Information):

The Statement section of the camt message provides the details of the account(s) for which the statement(s) is being produced.

The camt message may contain information related to more than one account statement. However, Temenos Transact is producing one camt message for a single account statement.

Details required at this level are built from the Temenos Transact account and related statement production details. This includes details of the statement period, account identification, opening, closing and other account balances.

• Entry-Level Information:

One account statement can contain multiple account movements (a statement may have zero entries during the period). Information at this level is derived from the individual account movement from the Temenos Transact statement entry table.

Transaction-Level Information:

This section provides additional information for each entry displayed in the Entry Level section. The additional information may include:

• Additional details for an individual entry.
• Additional details for SEPA related transactions.
• Underlying entries of a netted entry which represents multiple debits and credits or a batch entry (this will be supported at a later stage).

The following screenshot shows the xml view of the camt.053 message.

This table is used to define the default details for an account statement when opening new accounts. It also holds the high-level parameter that is applicable to account statement at the system level.

The AC.STMT.PARAMETER application is also used to define the following:

• Provide the link between an entry and the EXTERNAL.SEPA.DETAILS table, which would hold the SEPA details from an external SEPA system.
• Provide a hook to plug-in APIs to filter and consolidate the list of entries for a specific camt message.

Link between the Entry and the EXTERNAL.SEPA.DETAILS table:

To identify the corresponding EXTERNAL.SEPA.DETAILS record that holds the SEPA details for a STMT.ENTRY, the STMT.ENTRY and the EXTERNAL.SEPA.DETAILS record should be linked.

A hook is available based on each implementation to attach a local API with the logic to link the STMT.ENTRY record to the EXTERNAL.SEPA.DETAILS. The API returns the key to the EXTERNAL.SEPA.DETAILS table.

The External SEPA Link API field in AC.STMT.PARAMETER application is the hook that gets the link from the entry to the EXTERNAL.SEPA.DETAILS table. It is a valid key to EB.API to hold the API that returns the link key to the EXTERNAL.SEPA.DETAILS table.

The camt account statements and reports are generated using the standard account statement functionality.

ACCOUNT.STATEMENT table is used to specify the dates and frequencies for producing account statements. A record is automatically created with the default settings when an account is set-up. It can then be defined specifically for each account based on the customer’s requirements. User can define up to nine statement cycles, and within each cycle, a combination of different types of messages can be generated.

The Xml Stmt Type field in the ACCOUNT.STATEMENT application is used to request a camt or MT type message for the first cycle for an account.

The Swift Statement-2 Type field is used to define the message types for the additional statement cycles.

The following screenshot shows the set-up for camt and MT type messages for two statement cycles.

Each building block of the camt message has a list of tags to hold specific information for the statement. The tags have the following attributes:

• Occurrence – Mandatory or Optional and Single or Multiple occurrence.
• Value – Defined as per ISO20022 or may be configured by account service provider.

Temenos Transact supports the following camt tags defined under ISO20022:

• All mandatory tags.
• Some optional tags with non-SEPA related details.
• The optional tags that are required under the Dutch Banking Association (NVB) usage rules to report additional SEPA details from an underlying Payments Clearing and Settlement (PACS) message.

The tags are defined internally using the Temenos Transact naming convention and are mapped to the ISO20022 camt schema during the data transformation process.

Read the Camt Generation Process section for more details on data transformation.

Mandatory Tags Supported:  

The following table shows the high-level mandatory tags that are supported by Temenos Transact with an indication of the tags, which can be configured by the bank based on the bank’s practice or local regulation.

Optional Tags Supported:

Optional tags are required under the NVB usage rules to report additional SEPA details.

The following table shows the list of high-level optional tags that are supported by Temenos Transact with an indication of which tags are required to report SEPA details and which tags may be configured by the bank based on the bank’s practice or local regulation.