Text for Syndication Agreements and different types of Guarantees can be created and stored in the database. The text (Syndication Agreements or Guarantee Text) can be selected based on the “Text Definition Type” field.

Within the “Text Definition Type” it can be decided if the “Object Type” will be created and defaulted for a “Party”, a “Country” or the “Group” of a Party. The values have to be chosen in the respective fields.

Syndication agreements can be distinguished by language, agreement type (e.g. master participation agreement, forfeiting agreement, etc.). It can be stored as a default, country, group or a party-specific texts. Specific fields and panels have been defined for each type of text under syndication. For an object type, default text values such as 'Offer', 'Amendment request', 'Funding request' and 'Demand for payment' can be defined under the same template. These texts are then used under various transactions of the syndication business module. Based on the selected transaction and template, the text is properly filled to the respective fields in the Syndication module. For more information see Syndication.

Fields have to be entered in the text (Guarantee text or Syndication agreement) together with their technical paths and in curly brackets so that the application can recognize that the field in curly brackets is to be replaced by content captured in the transaction.

Example: To insert the Syndication Deal reference number, the field has to be entered as {SDDGRP\REC\OWNREF}. Similarly, if a field has a code and a longtext and to display the longtext instead of the code, it is required to format it differently as {=gettbltext(SCDGRP\REC\SYPTYP,“SYPTYP”, “EN”)}

Guarantee texts can be distinguished by

• “Language”,
• “Purpose of Outgoing” undertaking message (ISSU, ISCO or ICCO for sequence B, ISCO or ICCO for sequence C),
• “Undertaking Type” (e.g. advance payment guarantee, bid bond, etc.),
• “Form of Undertaking” (e.g. demand undertaking, dependent undertaking, Standby L/C, etc. )
• and its period of validity to destinguish between “Unlimited” Guarantees, 'limited' or 'both'.

It is also possible to weigh the most frequently used texts using field “Priority”, ensuring that the most used appear at the top of the list in guarantee transactions.

Another panel is available to store the texts with “Further Guarantee Information” for other fields such as “Presentation Instructions”, “Expiry/ Liability Conditions”, and “Underlying Transaction Details”. The stored text is then populated to the corresponding fields in the guarantee transaction.

Guarantee texts are maintained under (Advanced Text Definition).

Fields appearing on the Details panel during pre-creation and/or creation of the guarantee depend on the selection criteria made during maintenance of the related guarantee text. This feature allows guarantee texts to be very easily customized to meet the needs of each guarantee type.

The following fields are available in the Details panel and may be incorporated into the definitions of guarantee texts:

Unformatted date fields, such as “Tender Date” ({GIDGRP\REC\TENDAT}), are formatted in the “Date Short” format defined in the transaction “Maintaining System Parameters”. The MyModelbank uses the format: “DD.MM.YYYY”

* Some fields are also available as formatted fields which are expressed in the language of the guarantee and as long text (see table below).

The following fields, including contract fields, are available as pre-formatted fields:

The following fields are available for Seq.C:

Fields have to be entered in the guarantee text together with their technical paths and in curly brackets so that the application can recognize that the field in curly brackets is to be replaced by content captured in the transaction.

Example: if the subject matter of the contract in the guarantee text is to be issued, the technical description of the field {GIDGRP\BLK\COVGODSRV} has to be entered at the appropriate position in the guarantee text.

Formatted datafields are processed in the respective guarantee language. If, for example, the user enters the date “24.12.2018” under “Tender Date” on the “Details” panel the date will be displayed as “24. Dezember 2018” in a German guarantee text and as “24. December 2018” in an English guarantee text.

If there are fields that always have to be issued in guarantee texts, these have to be defined as database fields in the customer overlay. Here, a decision needs to be made whether such fields are solely relevant for guarantee texts, or for the whole contract. Fields only required for guarantee texts have to be positioned on the Details panel of the opening transaction. The reason for this is that fields positioned on the Details panel and used in the selected guarantee text are automatically enabled in opening transactions and are defined as mandatory fields.