en:app:020cor:070ovs:010pty:0120dbiact

Maintaining Accounts

Transaction DBIACT

This transaction is used to maintain accounts.

The following transactions can be started from here by clicking the icons the list below for:

“Party” is the party, used to search for/select an account in subsequent transactions. This typically corresponds to the “Account Holder” shown below. But for Nostro accounts, it is the external bank on whose books the account is served, i.e. the “Account Server” indicated below.

“Type” indicates the type of account. This account type determines the nature of transactions it can be used for.

“Currency” describes the currency in which the account is held.

“Account” provides the account number under which the bank using the application holds the account. Exceptions here are SPA (SEPA) account types that have a customer as the account holder and is served by an external bank. Since the bank using the application does not hold this account in its own books, it makes sense to mark such account with a suffix 'SPA', for example, and thus to avoid any susbstantive overlaps with the bank's own account numbers. An account number can only be added once within an entity, i.e. with one currency and for one party.

(Account) “Name” is a descriptive field of up to 40 characters used to describe the account. The field is generated automatically, consisting of the account type and the name of the party.

“Served by” specifies the party who maintains the account. For nostro accounts this is the correspondent bank, for loro accounts this is the bank using the application.

“Server's No.” represents the account number in the books of the party serving the account. The “IBAN” (International Bank Account Number) refers to the account number in the books of the party serving the account.

(Account) “Holder” describes the party that owns the account, i.e. the owner of credit on the account. For loro account this is the bank customer, for nostro accounts the bank itself.

“Priority” enables priority of account defaulting in the event that multiple accounts exist.

The “Reimbursement Account” checkbox specifies whether the account may be used as reimbursement account in a letter of credit transaction.

“Available for” specifies whether the account may be used for “debit & credit” (default), “debit”or “credit”.

The “delete flag” indicates whether an account is normally available once again, or whether it is no longer to be offered in account defaulting. This condition is to be regarded as a preliminary stage before the account is actually deleted.

For accounts of account type SPA (SEPA account) that may also be used for 'debits' (charges), in addition the date “Mandate of” is to be specified. When creating a new entry, the “status” is to be set to 'non-recurring direct debit' and the “Service-ID” is to be selected in accordance with the mandate granted. If the FIRST debit for a SEPA account is rejected by the executing system, then the status of the account has to be manually reset from 'Subsequent debit' to 'First-time debit'.

The fields 'General' and 'Stop' can be used to capture General Information relating to the account. How these are displayed depends on the display type they have been assigned to. This is especially the case if the relevant account is to be used in a contract/settlement or if the user is to be prevented from using the account.

To delete an account of a party from the database it is important that the respective account is no longer used in any transaction or settlement (even pending). After selecting the respective account click . The account is deleted from the database when delete prompt is confirmed. Given the considerable effects that may ensue, we would recommended first setting “stop levels” for the account (using ). After a certain period, the account can then be deleted from the database. The 'STOP' command does not allow the account to be used for any settlement, etc.

Transaction Panels

Accounts



Datafields

Datafield Description
Name cf Appendix A, Table PTY field NAM
Name cf Appendix A, Table PTY field NAM
Name cf Appendix A, Table PTY field NAM
External Key cf Appendix A, Table PTY field EXTKEY
Account Type cf Appendix A, Table ACT field TYP
Account Currency cf Appendix A, Table ACT field CUR
External Key cf Appendix A, Table ACT field EXTKEY
Name cf Appendix A, Table ACT field NAM
External Key cf Appendix A, Table PTY field EXTKEY
Account Number Defined by Servicing Institute cf Appendix A, Table ACT field SERACC
International Bank Account Number cf Appendix A, Table ACT field IBAN
External Key cf Appendix A, Table PTY field EXTKEY
Account Number of Control Account of Holder (Optional) cf Appendix A, Table ACT field HOLACC
Priority for Defaulting cf Appendix A, Table ACT field PRI
Available for cf Appendix A, Table ACT field DIRFLG
Deleted Flag cf Appendix A, Table ACT field DELFLG
Reimbursement Account cf Appendix A, Table ACT field RMBFLG
Sepa Mandate ID cf Appendix A, Table ACT field SPAID
Pre-Notification advance cf Appendix A, Table ACT field SPAPRENOT
SEPA Mandate Authorisation Date cf Appendix A, Table ACT field SPADAT
SEPA Status cf Appendix A, Table ACT field SPASTA
SEPA Service ID cf Appendix A, Table ACT field SPASRVID


Info and Stop text



Datafields

Datafield Description
Text Field cf Appendix A, Table OIT field INFTXT
Display Type cf Appendix A, Table OIT field INFLEV
Text Field cf Appendix A, Table OIT field INFTXT
Display Type cf Appendix A, Table OIT field INFLEV


en/app/020cor/070ovs/010pty/0120dbiact.txt · Last modified: 2022/09/23 07:17 by bp