ACT - Account

This table holds all accounts used around parties. To identify
the associated parties of an account the two sets of HOL and SER
fields are available in the table.

/

INR

Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter ACT. The field INR is used to maintain links from other tables into this table.

Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

If multiple accounts exist, this field can be used to specify the order of priority in which a particular account may be used for defaulting in the settlement screen. Examples: Main account for L/C's Main account for fees Main account for all automatic settlements

If multiple accounts exist, this field can be used to specify the priority sequence in which a particular account may be used for defaulting in the settlement screen. Examples: Main account for L/C's Main account for fees Main account for all automatic settlements

This field holds the currency of the account

The currency in which the account currently being set up is to be held.

The external key is used to identify the account as unique. The external key can be used to search for an account that is already stored in the database.

The external key is used to identify the account as unique. The external key can be used to search for an account that is already stored in the database.

This field specifies the account number in the books of the account servicing institution. For all accounts that are maintained at third party institutions (e.g.: nostro accounts, customer account maintained at another bank etc.) that's there account number.

This field specifies the account number in the books of the account servicing institution. For all accounts that are maintained at third party instititutions (e.g.: nostro accounts, customer account maintained at another bank etc.).

This field specifies the type of the account servicing institution, and is selected from the list of permitted party types.

This field specifies the type of the account servicing institution, and is selected from the list of permitted party types.

This field specifies the unique identification number under which the Account Servicing Institution is stored.

The identification number (INR) of the account servicing institution.

This field specifies the optional 'control' account number of the account holder. For example, for a client (loro) account maintained with us, this field may contain the account number in the books of the account holder (client).

This field specifies the optional 'control' account number of the account holder. For example, for a client (loro) account maintained with us, this field may contain the account number in the books of the account holder (client).

This field specifies the (party) type of the account holder.

This field specifies the (party) type of the account holder. The party type may be selected from the list of defined party types via a combobox.

This field specifies the unique INR or identification number under which the account holder is stored in the database.

This field specifies the unique ID under which the account holder is stored in the database.

This field specifies if the account may be used for providing reimbursements under an import letter of credit.

Most banks hold a large number of nostro accounts, while not all of theses accounts are eligible for reimbursement authorizations under the import letter of credit. In order to reduce the number of accounts shown during LC Issuance (when the reimbursement authorization is generated), it is necessary to select this flag. Then, on panel reimbursement of the Import LC Issuance transaction (LITOPN) only nostro accounts flagged as reimbursement account are displayed and available as accounts in the outgoing MT740 (Reimbursement Authorization).

This field specifies if the account may be used for providing reimbursements under an import letter of credit. Most banks hold a large number of nostro accounts, while not all of theses accounts are eligible for reimbursement authorizations under the import letter of credit. <br/>In order to reduce the number of accounts shown during LC Issuance (when the reimbursement authorization is generated), it is necessary to check this checkbox. Then, on panel reimbursement of the Import LC Issuance transaction (LITOPN) only nostro accounts flagged as reimbursement account are displayed and available as accounts in the outgoing MT740 (Reimbursement Authorisation).

If this field does contain a non-empty value the account is treated as “deleted” thus not longer available in account defaulting.

In the Combobox value “X” is used as non-empty value. Thus, if flag is set by import programs, “X” should be used.

If this field contains a non-empty value, the account is treated as “deleted” and is thus not longer available in account defaulting.

In the Combobox, “X” is used as non-empty value. Thus, if the flag is set by import programs, “X” should be used.

This field holds the version counter to keep track of the version history of an ACT entry. The individual versions are controlled by entries in the SLG table.

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.

This field hold the information whether the account can be only debited or credited.

If this field is not filled, the account can be debited and credited.

This flag shows if the account can be used for debit, credit, or for both debit and credit bookings.

A non-empty value means that the foreign party has to be treated as bank in account defaulting.

This is set by ActSetFieldsForActDef in Actmod.

The contents can be reorganized by REOACT for all accounts.

A non-empty value means that the foreign party has to be treated as a bank in account defaulting.

Name of other party to be used as name in selection box of account.

This is set by ActSetFieldsForActDef in Actmod.

The contents can be reorganized by REOACT for all accounts.

The name of other party to be used when selecting an account.

A non-empty value means that the foreign party has to be treated as own party in account defaulting. If it is an own address (PTYTYP contains “A”), it's set to “A”, if only a branch it is set to “X”

This is set by ActSetFieldsForActDef in Actmod.

The contents can be reorganized by REOACT for all accounts.

A non-empty value means that the foreign party has to be treated as an own party in account defaulting.

If it is an own address, it is set to “A”, if only a branch it is set to “X”

The contents can be reorganized for all accounts using 'Reorganization of Accounts (ACT)'.

This field contains the first six digits to the foreign party for account defaulting. The digits 1 to 4 can be used to checks if the BIC is from the same organization. The digits 5 and 6 can be used to compare the country.

This is set by ActSetFieldsForActDef in Actmod.

The contents can be reorganized by REOACT for all accounts.

This field contains the first six digits of the foreign party for account defaulting. Digits 1 to 4 can be used to check if the BIC is from the same organization. Digits 5 and 6 can be used to compare the country.

The contents can be reorganized via 'Reorganization of Accounts (ACT)' (REOACT) for all accounts.

This optional field holds the IBAN to be used to identify the account.

This field is used to define the International Bank Account Number (IBAN).

This fields contains the date when the account owner authorized a SEPA Direct Debit mandate and allowed the account to be used for SEPA Direct Debit transactions.

This field contains the date when the account was defined for usee use as SEPA account.

This field shows the status of the SEPA account. For the first usage of the account, the status is FRST (First Usage). For following usages the status is always RCUR (Follow up).

he field defines the nature of the SEPA mandate. There are two options - COR and B2B. For further information, please read the SEPA documentation. If the date for the SEPA mandate is filled, this field is mandatory.

This field shows the status of the SEPA account. For the first usage of the account, the staus is FRST (First Usage). For following usages the status is always RCUR (Follow up).

This field defines the status of the SEPA account. When the account is first used for an SEPA booking, the value entered has to be FRST (first-time debit), for further use, RCUR (recurring debit). For further information, please read the SEPA documentation. If the date for the SEPA mandate is filled, this field is mandatory.

This table is defined on entitygroup level with separate entries for each entitygroup. This field holds the EXTKEY of the entity group which is the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the entitygroup of the current active entity are visible to the user.

This field holds the external key of the owning entity group to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity group are visible to the user.

This field contains the name of the account.

This field contains a descriptive name (of up to 40 characters) used to identify an account. Searching within a table is usually be done by entering parts of this field. All matches are then displayed to facilitate account selection.

This field defines the external account type.

This field defines the external account type.

Each account set up in the system is associated with a specific type, depending on its nature and for which account it is used. Examples are: Vostro Account Nostro Account Letters of Credit Liability Account etc. Each transaction type (Opening a Letter of Credit, Debiting Fees, Settlement of Documents Presented, etc.) is associated with one or more account types so that only the relevant accounts for that transaction are defaulted into the respective transaction panels

Each account set up in the system is associated with a specific type, depending on its nature and for which account it is used. Examples are: Vostro Account Nostro Account Letters of Credit Liability Account etc. Each transaction type (Opening a Letter of Credit, Debiting Fees, Settlement of Documents Presented, etc.) is associated with one or more account types so that only the relevant accounts for that transaction are defaulted into the respective transaction panels

This field holds the SEPA mandate ID. The ID can be used for checking external mandate administration

This field holds the SEPA mandate ID. The ID can be used for checking external mandate administration

This field holds the no. of days the pre notification must be send in advance

This field holds the no. of days the pre notification must be send in advance

Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.

Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.