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.

This field contains the reference number of the Guarantee being established. The reference number can be up to 16 characters long. The field should be defined as a database key field to optimize performance. The field can also be used to search for a guarantee from the database.

This field holds the descriptive name of the Guarantee displayed in the application used to describe and to search for a contract. In the standard version, this field is set by a default rule based on the contract amount and the main party and cannot be modified by the user.

This field holds the User ID of the person responsible for handling this contract.

This field holds the INR of the transaction which opened/issued the contract.

This date field identifies the date the entry was physically added to the database.

The field holds the opening/issuing date of the contract. If this field is set, the contract has been legally established and it might be used for business transactions. This date describes the point in time when this contract became legally binding. This might be a date prior to the creation date, when the contract was legally binding before it was stored in the database.

This fields indicates the closing date of a contract. If an entry has been made, the contract is closed and may no longer be used to process business transactions except special transactions like Settling Charges or Common Messages.

This field specifies the old reference of the Guarantee (if the contract has been migrated, for instance).

This field contains the date of the last amendment processed under the contract. If it is empty the contract is still in its original condition. This date is automatically updated by the relevant amendment transactions.

This field specifies the date when the customer passed instructions to the bank.

This field is used to store the number of amendments made to the contract so far. This field is automatically updated from the relevant amendment transaction.

This field counts the number of pending (unclosed) claims under the guarantee.

This field defines whether the fees and commissions of the bank using the application are to be borne by the beneficiary (=“B”), by the Applicant side (='U') or by others. Depending on the selection made in this field, the roles in the second settlement table (own commission / fees) are proposed.

Meaning of 'Applicant side': If, in the fee settlement field, 'Applicant side' was selected or if the field is not completed, then own fees will be proposed in the settlement to the debit of the customer SIDE.

Meaning of 'Beneficiary side': Own fees in the settlement are proposed to the debit of the beneficiary SIDE

Meaning of 'Others': No role is proposed on the fees in the settlement panel.

This field describes the expiry of the contract. If the field is empty, the 'Unlimited Validity' field defines the logical meaning of this empty value. If the expiry date is empty and 'Unlimited Validity' is filled, the contract has unlimited validity. If both fields are empty, no expiry has been defined.

The field identifies a date that marks the end of the bank's liability in the contract. If the field is empty, the 'Unlimited Liability' field defines further logical significance. If the 'Liability until' field is empty while 'Unlimited Liability' is not, the bank is subject to unlimited liability. However, if both fields are empty,liability has not been defined. In this case, both fields need to be checked - one should be empty to define the existence of liability.

The field can be used for statistical purposes and allows the bank to evaluate the country risks it may have incurred by issuing the guarantee.

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 specifies the handling type.

In the case of a direct guarantee, the applicant requests his house bank (bank using the application) to issue a guarantee in favor of a beneficiary abroad.

In the case of an indirect guarantee, the applicant's bank (bank using the application) requests an issuing bank abroad to order the guarantee on his behalf.

In the case of advice with/without confirmation, a foreign bank has issued a guarantee which is to be advised through the bank using the application to the beneficiary.

“Guarantees received” are guarantees issued in favor of the bank using the application (and not in favor of one of its customers).

Checking this box enables the guarantee text to be modified.

If this flag is activated, the guarantee text in second language can be modified manually by the user.

Depending on contents of the 'Handling Type', 'Type of Guarantee' and 'Legal Form' fields, different guarantee texts may be defaulted and selected here from the combobox. In the field is empty, this means that no fitting guarantee text was found for this selection. Accordingly, the guarantee text has to be entered manually in the “Guarantee Text” panel.

Depending on contents of the 'Handling Type', 'Type of Guarantee' and 'Legal Form' fields, different guarantee texts may be defaulted and selected here from the combobox. In the field is empty, this means that no fitting guarantee text was found for this selection. Accordingly, the second guarantee text has to be entered manually in the “Guarantee Text” panel.

This field specifies the language of the guarantee. The guarantee language can be different from the language used in other bank correspondence. Example: According to the party definition in 'Displaying Party', the customer is to receive all correspondence in German. Guarantee language can however be set to English – The customer receives the cover letter in German, the Guarantee is in English.

If the checkbox 'Bilingual' on the overview panel is checked, here the second language is shown.

This field is used to refine the logical meaning of an empty value in field expiry date. This field may only be set if 'Expiry Date' is empty. When set to a non-empty value, this identifies the unlimited validity of the contract.

This field is used to refine the logical meaning of an empty value in the 'Liability Until' field.

This field may only be set, when 'Liability Until' is empty.

´Setting the field to a non-empty value identifies a bank's unlimited liability.

This field specifies the receiver of the guarantee.

This field specifies the reason why the undertaking/guarantee has been canceled.

This field is set from the 'Pre-Creating a Guarantee' transaction when a pre-advice is done. The field is also required in the outgoing T68 in the 'Creating a Guarantee' transaction.

This field is set from the 'Pre-Creating a Guarantee' transaction if a declaration of readiness is at hand.

Contract status flag. If not empty, the contract has been reserved and only a few basic fields have to be filled in. Visible in 'Pre-Creating a Guarantee' (GITPOP) and 'Info Guarantee' (INFGID). Invisible in all other transactions.

This field contains the type of goods shipped. The goods code is used to evaluate contracts by the type of goods. The codetable can be customized by the bank according to their needs.

This field contains the currency of the total amount (TAG 34B) of the MT 769 message to be remitted to the sender of the message.

This field contains the reduction amount (TAG 33B) of the MT 769 message to be remitted to the sender of the message.

This field contains the Date of Reduction or Release in TAG 30 of the incoming message MT 769 (Advice of Reduction or Release).

This field specifies the currency of the outstanding amount of the guarantee as received in the incoming MT769 (Advice of Reduction) in Tag 34B.

This field contains the open amount after reduction (TAG 34B) of the MT 769 message to be remitted to the sender of the message

This field contains the confirmation status of the bank ising the application and therefore indicates whether the bank has added its confirmation to the guarantee or not. “Silent” indicates a silent confirmation which is not disclosed to the issuing bank.

This fields contains the percentage rate of a partial confirmation. The field is only enabled for user entries, if the guarantee is confirmed by the bank using the application.

This field contains the confirmation date of the guarantee.

This field defines whether the amount or the percentage has been confirmed in a partially confirmed contract.

Based on this information, the percentage or amount are protected and calculated from the other field.

Contract status flag. If not empty, the outgoing message “Declaration of Indemity” is created on the messages panel unless it has already been issued in a preceding transaction.

The declaration of indemnity is usually a letter predefined by the bank, signed by the customer and returned to the bank.

This fields holds the information about whether the contract amount or the original percentage rate is the leading field for automatic calculation of the contract amount/percentage rate. It is necessary, to allow the correct calculation of these values.

Possible values: A = Amount P = Percentage I = from incoming message or empty = not defined

This flag is set in the (pre)opening transaction in case an incoming message is rejected. The contract is closed directly.

If this checkbox is checked, the guarantee is bilingual. Then a panel 'Second Guarantee Text' is offered.

This field holds the external key of the owning entity 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 are visible to the user.

This field specifies the date when the sales contract between the importer and the exporter was concluded.

'Date of the original contract formatted in the language of the guarantee' is to be used, if the date is required in the language of the guarantee text.

This field specifies the reference of the sales contract concluded between the importer and the exporter.

This field specifies the currency of the contract concluded between the buyer/importer and seller/exporter.

This field specifies the contractual amount concluded between the buyer/importer and seller/exporter.

This field specifies the percentage of the contract amount in relation to the guarantee amount.

This field specifies the reference of the tender guarantee/bid bond.

This field specifies the date of the tender guarantee/bid bond.

The 'Tender Date' is used, if the tender date is required in the language of the guarantee text.

This field contains the final or closing date of the bid bond. FMTTENCLSDAT must be used if the final or closing date of the bid bond is necessary in the language of the guarantee text.

This field specifies the legal venue for the underlying guarantee.

This field specifies the law that applies to the underlying guarantee.

This field holds the account number of the account which is to be credited under an advance payment guarantee.

This field holds the undertaking / guarantee type.

This field specifies the latest date of transmission.

For indirect guarantees, this field is used to inform the issuing bank abroad of the latest date for issuing the original guarantee in favor of the beneficiary.

“Latest Transmission Date” is to be used, if the latest date of transmission is required in language of guarantee text.

This field specifies the legal undertaking form. 'Applicable Rules', the text field of the rule and the 'Undertaking Form' are closely related. 'Undertaking Form' has been used in the application before 'Applicable Rules' and the text field of the rule have been introduced by SWIFT. In older and large installations with many guarantee texts, 'Undertaking Form' is used to segment the list of defaulted guarantee text ('Undertaking Form' is available in 'Displaying a Guarantee Text Definition' (DBIGTX)). This is efficient if the bank has various own standard texts. In smaller installations, 'Applicable Rules' and the text field of the rule may be sufficient.

This selection list contains the type of request. Select “draft” to create a draft for “direct” or “indirect” guarantee. Select “preadvise” to create preadvise for a guarantee received from a third party. Select “declaration of readiness” if a draft or preadvise already contains a liability on your part.

For Auto-Renewal Undertakings: The undertaking expires on this date and after this date no further Auto-Renewals are allowed.

For Auto-Renewal: Advising Period for an Auto-Renewal.

For Auto-Renewal: Period for the next renewal of the undertaking.

For Auto-Renewal: Period of advance notification about the next renewal.

If marked, a new panel for Auto-Renewal details opens. There, additional values for the Auto-Renewal have to be entered.

For jobs that are executed 'monthly' or with longer periods: Day of the month when job is to be executed.

For Direct payment: Indicator, if the principal amount shall be reinstatable.

For Direct payment: Indicator, if the interest amount shall be reinstatable.

For Direct payment: Reinstanciation period in days (after claim payment)

Flag to activate assignment of proceeds registration.

This field specifies the rules governing the reimbursement authorization.

Flag to activate participation sold logic.

'Own Text' means that the customer provided the requested Guarantee text. Else, it states the requested standard text. Select the same text in panel Overview, field Choice of Text.

Customer's instructions to who the original Guarantee should be sent.

This field specifies the date on or by which the requested local undertaking is to be issued.

The field will be used in Tag 31C of the MT760 ( Sequence C ).

This field specifies the purpose of this message.

The field will be used in Tag 22A of the MT760 (Mandatory in Sequence A).

ACNF Advice and confirmation of issued undertaking ADVI Advice of issued undertaking ISSU Issuance of undertaking ICCO Issuance of counter-counter-undertaking and request to issue counter-undertaking ISCO Issuance of counter-undertaking and request to issue local undertaking

This field contains confirmation instructions from the issuing bank to the advising party.

Conditional in mandatory sequence B (49)

CONFIRM The requested confirmation party is requested to confirm the credit MAY ADD The requested confirmation party may add its confirmation to the credit WITHOUT No confirmation is requested

This field contains details about the automatic extension of the expiry date. DAYS Number of calendar days after latest expiry date ONEY Same date one year later OTHR Other extension clause

Conditional in mandatory sequence B (23F)

This field contains details about the automatic extension of the expiry date. Conditional in sequence B.

This field specifies if partial and/or multiple demands are not permitted. Optional in mandatory sequence B (48B)

This field specifies that the undertaking is transferable Conditional in mandatory sequence B (48D). Absence of this field indicates that the undertaking is not transferable.

This field specifies the method by which the original undertaking is to be delivered Conditional in mandatory sequence B (24E)

This field specifies the method by which the original undertaking is to be delivered. Conditional in mandatory sequence B (24E)

This field specifies to whom the original undertaking is to be delivered or by whom the original undertaking is to be collected.

If Code is OTHR, then Name and Address must be specified.

Conditional in mandatory sequence B (24G)

This field specifies the purpose of the message as taken from the incoming message MT760 Tag22A

ACNF Advice and confirmation of issued undertaking ADVI Advice of issued undertaking ISSU Issuance of undertaking ICCO Issuance of counter-counter-undertaking and request to issue counter-undertaking ISCO Issuance of counter-undertaking and request to issue local undertaking

If set, this field specifies that the wording of the terms and conditions must be the standard wording of the local undertaking issuer.

Optional in optional sequence C 22Y

This field specifies the requested ISO 639 language code for the wording of the local undertaking .

Optional in optional sequence C 40D

This field contains details about the automatic extension of the expiry date. DAYS Number of calendar days after latest expiry date ONEY Same date one year later OTHR Other extension clause

Conditional in optional sequence C (23F)

This field contains details about the automatic extension of the expiry date. Conditional in optional sequence C

This field specifies the minimum number of calendar days prior to the current expiry date by which notice of non-extension must be sent. Conditional in optional sequence C (26E)

This field specifies the final expiry date after which the local undertaking will no longer be subject to automatic extension.

Conditional in optional sequence C (31S)

This field specifies the method by which the original undertaking is to be delivered Optional in optional sequence C (24E)

This field specifies the method by which the original undertaking is to be delivered. Conditional in optional sequence C (24E) Has to be filled if DELORIC contains COUR or OTHR.

This field specifies to whom the original local undertaking is to be delivered or by whom the original local undertaking is to be collected.

If Code is OTHR, then Name and Address must be specified in DELTOADR.

Optional in optional sequence C (24G)

If this flag is activated, the guarantee text of the counter undertaking can be modified manually by the user. If not activated the guarantee text is either taken from the database or from any incoming message and is not changed by the user.

This flag indicates if the guarantee is a domestic guarantee or not. The guarantee is termed as domestic if - for issued gurantees - The country of the issuing DOKA-NG Entity and the beneficiary's country are same

- for advised guarantees - The country of the issuing DOKA-NG Entity and the applicant's country are same

This field specifies whether partial and/or multiple demands are not permitted. Optional in optional sequence C (48B)

If set, this field specifies that the local undertaking is transferable.

Optional in optional sequence C (48D) Absence of this field indicates that the local undertaking is not transferable.

If RNWPERC is set to DAYS, this field contains the number of days. Used for 23F in optional section C

This fields holds the information about whether the contract amount or the original percentage rate of the counter untertaking is the leading field for automatic calculation of the contract amount/percentage rate. It is necessary, to allow the correct calculation of these values.

Possible values: A = Amount P = Percentage I = from incoming message or empty = not defined

This field specifies the date when the customer has passed his instructions to the bank.

Depending on contents of fields 'Handling Type', 'Type of Guarantee' and 'Legal Form' different guarantee texts may be defaulted and selected here from the combobox. In case field is empty no fitting guarantee text for this selection has been defined. Accordingly the guarantee text has to be entered manually in panel “guarantee text”.

to be due to Standard SR2021 means: are all mandatory fields, which are needed for handling after SR2021 activation filled;

Draft number to be printed in Score MT 771 Score message. Incremented in GITPOP

This field contains confirmation instructions from the issuing bank to the advising party.

Conditional in mandatory sequence B (49)

CONFIRM The requested confirmation party is requested to confirm the credit MAY ADD The requested confirmation party may add its confirmation to the credit WITHOUT No confirmation is requested

Flag for activation of auto extension condition for sequence C.

This field specifies the form of local undertaking (independent or dependent).

Mandatory in optional Sequence C (22D) of MT760

This field specifies the type of the local undertaking.

Conditional in optional sequence C (22K)

This field specifies whether the local undertaking has a specified expiry date or is open-ended or is dependent on a documentary condition or event.

The field will be used in Tag 23B of the MT760 ( in optional sequence C).

COND: Expiry condition (including option for specified date of expiry). FIXD: Specified date of expiry (either with or without automatic extension). OPEN: No specified date of expiry.

This field specifies whether the undertaking has a specified expiry date or is open-ended or is dependent on a documentary condition or event.

The field will be used in Tag 23B of the MT760 (in mandatory sequence B).

COND: Expiry condition (including option for specified date of expiry). FIXD: Specified date of expiry (either with or without automatic extension). OPEN: No specified date of expiry.

This field specifies the Country Code of the governing law that is applicable to the local undertaking. Optional in optional sequence C (44H)

This field specifies the Country Code of the governing law that is applicable to the undertaking. Optional in mandatory sequence B (44H)

This field specifies the details of the governing law that is applicable to the local undertaking. Optional in optional sequence C (44H)

This field specifies the amount of the contract (local undertaking) which has been concluded between the buyer/importer and seller/exporter.

Use FMTORCAMT if the contract amount is required in the language of the guarantee text.

This field specifies the currency of the contract (local undertaking) which has been concluded between the buyer/importer and seller/exporter.

This field specifies the date when the sales contract (local undertaking) between the importer and the exporter has been concluded.

Use FMTORCDAT if the contract date is required in the language of the guarantee text.

This field specifies the percentage of the contract amount (local undertaking) in relation to the guarantee amount.

Use FMTORCRAT if the percentage is required in the language of the guarantee text.

This field specifies the reference under which the sales contract (local undertaking) between the importer and the exporter has been concluded.

This field specifies the closing date of the tender guarantee/bid bond.

Use FMTTENCLSDATC if the closing date of the tender guarantee is required in the language of the guarantee text.

This field specifies the reference of the tender guarantee/bid bond.

This field specifies the date of the tender guarantee/bid bond.

Use FMTTENDATC if the tender date is required in the language of the guarantee text.

This field specifies the latest date of transmission.

For indirect guarantees, this field is used to inform the issuing bank abroad when the original guarantee must be issued in favor of the beneficiary at latest.

Use FMTTRMDATC if the latest date of transmission is required in language of guarantee text.

This field holds the account number which is to be credited under an advance payment guarantee (counter undertaking).

This field specifies the place of jurisdiction which is underlying the guarantee.

Depending on contents of fields 'Handling Type', 'Type of Guarantee' and 'Legal Form' different guarantee texts may be defaulted and selected here from the combobox. In case field is empty no fitting guarantee text for this selection has been defined. Accordingly the guarantee text has to be entered manually in panel “guarantee text”.

This text is read from ATX

Used for data integrity with allNETT in the following scenario: ISCO and Undertaking Type on panel 'Sequence C: Overview' is set to OTHR.

When an incoming ISCO is handled, the incoming Seq. C tags are mapped into the Seq. B fields in DOKA, ie tag 22K is mapped into the field GIDGRP\REC\GARTYP.

So add this field to show “C”-content in “B”-Overview

If this flag is activated, the Document and Presentation Instructions can be modified manually by the user. If not activated the Document and Presentation Instructions is either taken from the database or from any incoming message and is not changed by the user.

If this flag is activated, the Document and Presentation Instructions ( Seq. C ) can be modified manually by the user. If not activated the Document and Presentation Instructions is either taken from the database or from any incoming message and is not changed by the user.

If this flag is activated, the Expiry Condition/Event can be modified manually by the user. If not activated the Expiry Condition/Event is either taken from the database or from any incoming message and is not changed by the user.

If this flag is activated, the Liability Condition/Event - Counter Undertaking can be modified manually by the user. If not activated the Liability Condition/Event - Counter Undertaking is either taken from the database or from any incoming message and is not changed by the user.

If this flag is activated, the Document and Presentation Instructions can be modified manually by the user. If not activated the Document and Presentation Instructions is either taken from the database or from any incoming message and is not changed by the user.

If this flag is activated, the Document and Presentation Instructions can be modified manually by the user. If not activated the Document and Presentation Instructions is either taken from the database or from any incoming message and is not changed by the user.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the PRDCOD shall identify the business sector together with some key criteria like confirmed or unconfirmed LC in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the PRDSUB shall identify the business sector specific bankside defined products adding some key sub criteria in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the product variant is intended as possible extension to setup specific variants below the product and subproduct code.

If this flag is set, the reimbursement panel becomes visible and reimbursement information can be entered under the guarantee.

This field contains the codes for reimbursing bank's charges according to specification of TAG 71A of the outgoing SWIFT MT740 (reimbursement authorization).

Account number of the reimbursing bank in the books of the reimbursing bank. (related to LIDGRP\RMB\PTS\DFTACT)

This field contains the date of the original authorization to reimburse

This field specifies where the gurarntee expires. The expiry place is closely linked to the expiry date, as it specifies the place where documents have to be presented under the guarantee in more detail.

Depending on contents of fields 'Handling Type', 'Type of Guarantee' and 'Legal Form' different guarantee texts may be defaulted and selected here from the combobox. In case field is empty no fitting guarantee text for this selection has been defined. Accordingly the guarantee text has to be entered manually in panel “guarantee text”.

This text is read from ATX

Flag that marks an incoming message as message received from corporate (i.e. DTA, Bolero, allNETT, SWIFT Score).

Set in transaction init.

Unique internal ID of a linked facility record.

If this flag is activated, the choice of guarantee text can be modified manually by the user. If not activated the choice of text is taken from incoming message and is not changed by the user.

If this flag is activated, the choice of guarantee text can be modified manually by the user. If not activated the choice of text is taken from incoming message and is not changed by the user.

If this flag is activated, the Underlying Transact. Det. is set from an incoming message.

If this flag is activated, the Underlying Transact. Det. for Sequence C is set from an incoming message.

Flag to suppress the applicant details in sequence C of the outgoing message (example: Sequence C of MT760).

Flag to suppress the applicant details in sequence B of the outgoing message (example: Sequence B of MT760).

This field specifies an additional sub section for sub divsion of the country. Here, the county/state or even specifed details about the Governing Law such as “English Law” in addition to the place of jurisdiction can be mentioned.

This field specifies an additional sub section for sub divsion of the country. Here, the county/state or even specifed details about the Governing Law such as “English Law” in addition to the place of jurisdiction can be mentioned.

This field specifies the negative tolerance to the nominal amount of the underlying contract as percentage minus that amount.

This field specifies the positive tolerance to the nominal amount of the underlying contract as percentage plus that amount. In order to calculate the maximum amount (e.g. the maximum risk of the bank), the positive tolerance amount is added to the nominal amount.