Reviewing Bank Guarantee Management (2NZ)

Trade Finance Management helps you to better manage your trade finance instruments.

This scope item supports common functionalities of Bank Guarantee without SD integration. Bank Guarantee issuing and receiving are covered.

In addition to functions for creating and changing bank guarantees, the system also supports functions for rollover, contract settlement, and contract termination. Cash collateral and bank guarantee fees are also covered.

The Trade Finance Management process generally covers the creation of financial transactions and executing of payments for fees and cash collateral for bank guarantee issuing. For further processing, the roll over and termination of transactions is possible.

All of the financial transactions can be monitored and reported upon.

Trade finance transactions are used for special financial transactions provided by banks and financial institutions which facilitate trade transactions. One type of trade finance transactions is a bank guarantee.

The bank guarantee is a pledge on the part of a bank to make someone's debt good in the event that they cannot pay it. These types of guarantees are essentially like agreements to stand as a cosigner on a transaction. In the event that the original party cannot follow through, the bank can be called upon to provide the payment.

SAP S/4HANA Cloud offers common functionalities of bank guarantees, which enable users to better manage bank guarantee related transactions. Bank guarantee transactions include transaction types for issuing and receiving bank guarantees. Use the app Create Bank Guarantee to perform these steps.

Below are the product types and transaction types covered in this scope item:

86A Bank Guarantee

• 100: Issue

• 200: Receive

The SAP S/4HANA Cloud System supports two forms of guarantee

• Direct Bank Guarantee: Issued by the applicant's bank (issuing bank) directly to the guarantee beneficiary without involving a correspondent (advising) bank.
• Indirect Bank Guarantee: Issued by a correspondent bank (usually the guarantee beneficiary's bank) upon the counter-guarantee of the guarantee applicant's bank.

Once a bank guarantee transaction is recorded and saved, it needs to be settled before further processing. Normally this needs to be done once you receive the bank guarantee from the bank.

Each financial transaction contains flows that must be paid. The treasury back office uses the Pay Only functionality in the Post Flows app to create the payment request for outflows, it does not create posting in financial accounting. Afterwards the posting related cash flows need to be transferred to the FI interface that generates the relevant postings in financial accounting.

Once the bank guarantee is issued by the bank, if the amount or validity term of the bank guarantee needs to be changed, you can negotiate with the bank regarding adjusting the bank guarantee amount or term. When the bank agrees to do the adjustment, you can roll over the bank guarantee in the SAP S/4HANA Cloud system (that is, changing the Bank Guarantee amount or end of term).

Use the Process Trade Finance Transactions app to perform such a roll over in the system.

During the validity period of a bank guarantee, if the bank guarantee is not needed or the related duties have been performed, then you need to terminate the bank guarantee.

Once the bank guarantee is in Termination status, it releases the facility it used in the transaction automatically. If a bank guarantee is terminated, then it needs to be settled before further processing is possible.

At the time a bank guarantee is terminated, the cash collateral should be returned by the bank and the bank fees should be calculated and paid to the bank.

Use the Create Bank Guarantee app again to receive a bank guarantee.

Other than issuing bank guarantees, you might also receive bank guarantees from your business counterparties. SAP S/4HANA Cloud fully supports all the processes of receiving a bank guarantee.

In case you receive a bank guarantee, you need to enter the bank guarantee information into SAP S/4HANA Cloud system. Normally, as the receiver or beneficiary of a bank guarantee, you don't need to pay any cash collateral and the issuing bank won't charge you. So normally there won't be any outgoing or incoming payments to be done. However, in some special cases (for example back-to-back bank guarantees), there could be payments coming with receiving bank guarantees. SAP S/4 HANA Cloud system can fully support these business processes.

Once the transaction is recorded and saved, the transaction must be settled before further processing. Normally this needs to be done once you receive the bank guarantee from the bank.

In Treasury and Risk Management, financial data is analyzed based on the financial objects created automatically for each object you want to analyze. Additional information that is required for risk analysis is also entered into the financial object.

Financial objects are created for the following:

• Money market transactions
• Foreign exchange transactions
• Over-the-counter (OTC) derivatives
• Security transactions
• Security class positions in securities accounts
• Trade finance transactions
• Exposure positions

Bank accounts

The structure of financial objects mainly consists of three parts:

General part: General data (such as the product type) for the financial object

• Company Code
• Transaction
• Product Type
• Source System

Analysis: Data that is relevant for Market Risk Analysis

• Transaction Start
• Transaction End
• Contract Type
• Security Class ID
• Securities Account

Default Risk Limit: Data about the Default Risk and Limit System

• Credit Risk (CR) Active
• Limit Product Group
• Monitoring Unit
• Default Risk Rule

If you are creating a new financial transaction, you can set the values for the Counterparty Risk - for example, here with a Fixed-Term Deposit on the tab Default Risk Limit.

Set the indicator Counterparty Risk Active (CP Risk Active), so that an attributable amount is calculated for the transaction.

Enter the following limit characteristics:

• Limit Product Group (the limit product group you enter here overwrites the default limit product group)
• Monitoring Unit (freely definable reporting characteristic)
• Rating (the rating you enter here overwrites the rating for the business partner, but this is not the case for the integrated external business partner).

Enter the following evaluation parameters:

• Default Risk Rule (the default risk rule you enter here overrides the one set in Customizing)
• Recovery Rate

In the next end-of-day processing run, the system calculates an attributable amount for the transaction to which you assigned this financial object.

The financial objects are created automatically by the system when you create financial transactions, exposure positions, and bank accounts. The field values are derived according to predefined derivation rules and customer-defined substitution rules. When you create a financial transaction, you can change the derived financial object data manually. Financial objects are created immediately following the creation of financial data. 

Financial objects are created for the following reasons:

• Treasury and Risk Management
• Cash Management

When you create financial transactions, the system offers dialog entry screens in which you can change the financial object data manually. If you do not enter the data manually, they are derived automatically by the system. For exposure positions and bank accounts, the financial objects are always derived automatically by the system. When you save the transaction, the system checks the information in the various parts of the financial object.

During the derivation process, the predefined derivation rules are executed first. The predefined derivation rules do not overwrite any field values. Therefore, a field value that is entered manually, for example, is not overwritten by the predefined rules. In the second step, the substitution rules are executed. When the system executes the substitution rules for the market risk data, the system first executes the rules for the specific business contexts and then the rules for the general context. The substitution rules can overwrite the fields that have already been filled manually - either by predefined derivation rules or by an earlier executed substitution rule - if the Overwrite indicator was set in the definition of the substitution rule. Note this when you define your substitution rules.

With the Financial Objects Substitution Rules - Default Risk Data app, you can display, change, and create substitution rules for some fields of the financial objects that are relevant for default risk limit management. The rules are executed during the automatic derivation process of financial objects, whereby you can replace the field values that have already been filled, for example, from the predefined derivation rules.

Using the Financial Objects Substitution Rules - Default Risk Data, your business configurations expert can define substitution rules for the values of the following fields of the financial object data that are relevant for default risk limit management:

• Business Partner as Limit Characteristic
• Default Risk Rule
• Transaction End Date for CL Counterparty/Issuer Risk
• Transaction Start Date for Counterparty/Issuer Risk
• Limit Product Group
• Counterparty/Issuer Risk Active indicator

The fields available for defining preconditions are different for each business context. This enables you to substitute values of the target fields dependent on attributes specific to the business context.

You can define substitution rules to fill the following fields:

• CR Active
• Business Partner as Limit Characteristic
• Limit Product Group
• Default Risk Rule
• Start Date
• End Date

If you changed or created new substitution rules, business user can start the Update Financial Objects app to update the data of all existing financial objects.

The Financial Objects Substitution Rules - Market Risk Data app facilitates the display, change, and creation of substitution rules for some fields of the financial objects that are relevant for market risk analysis. The rules are executed during the automatic derivation process of financial objects, whereby you can replace the field values that have already been filled, for example, from the predefined derivation rules.

You manage substitution rules by business context. A context represents the circumstances in which the substitutions are defined and applied. It determines the fields that are available in the rule definition. There are several applicable business contexts defined by SAP. It is important to note that those can not be changed. Examples of these are as follows:

• Bank Accounts: Market Risk Data
• Derivatives: Market Risk Data
• Exposure Positions: Market Risk Data
• General: Market Risk Data

When the system executes the substitution rules for the market risk data, the system first executes the rules for the specific business contexts and then the rules for the General: Market Risk Data context.

The fields available for defining preconditions are different for each business context. This enables you to substitute values of the target fields dependent on attributes specific to the business context.

The same fields are also available as source fields for the substitution.

Note

You are responsible for ensuring that the data used in the substitution rule is used in accordance with the applicable legal or business requirements. The results, which substitution rules were applied, and the values of the target fields are visible in the apps for users with treasury business roles and must therefore not contain any sensitive data.

With this app, you can update the data of your existing financial objects. The report starts the derivation process of financial object data for the selected financial objects and updates the values, if needed.

You use this report in the following cases:

• If your business configuration expert created new substitution rules for specific fields of the financial object using the Financial Objects Substitution Rules - Market Risk Data and Financial Objects Substitution Rules - Default Risk Data configuration apps
• If your business configuration expert changed the settings in the Assign Product Categories and Default Risk Rules and Assign Product Categories and Limit Product Groups configuration steps
• If an error occurred during the automatic integration process of financial objects and the data could not be derived

You execute the report for a specific financial object type, whereby you can also restrict the number of financial objects according to financial object type-specific selection criteria.

You can execute the report as a test run or as an update run.

Account assignment references are assigned to each treasury position.

You use the account assignment reference to determine the G/L account in which the position is managed.

You make the assignments of the G/L accounts dependent on the account assignment reference for the relevant account symbols (position and interest revenue) for posting the positions, dividend payments, interest payments, accruals and deferrals, incoming payments, and repayments in the general ledger.

For example, you can define different account determination settings for an update type, depending on the valuation area. You could, for example, assign posting specifications to an update type in valuation area 002 that differ from the posting specifications for the same update type in valuation area 003. Alternatively, you could use the same posting specifications, but assign different G/L accounts to a account symbol for each valuation area.

In order to derive the correct account assignment reference, the following requirements are set in the system:

• You have defined the chart of accounts and all the required accounts in Financial Accounting.
• You have defined all account assignment references in the step Define Account Assignment References.
• In the Define Account Symbols configuration step, you have defined abstract account symbols.
• You have defined your update types.
• The system posts flows in the parallel valuation areas only if an update type is set as relevant for posting in the Indicate Update Types as Relevant to Posting configuration step, and if posting specifications have been defined, for the corresponding update types in this configuration step.

The determination process of account assignment references starts when an over-the-counter (OTC) transaction or security purchase is created.​

During the determination process of account assignment references, the system runs through the following sequence:

1. The system searches for a suitable substitution rule. If it finds a suitable substitution rule, it uses it to determine the account assignment reference.
2. If the system can not find a suitable substitution rule, it searches for a suitable determination rule. If it finds a suitable determination rule, it uses it to determine the account assignment reference.
3. If the system can not find a suitable determination rule either, it derives the account assignment reference using predefined rules in the content.

The single items and dependent Fiori apps will be analyzed in more detail below.

The Account Assignment Reference - OTC Transactions (Substitution Rules) app helps you to display, change, and create substitution rules to determine the account assignment references of OTC transactions. Account assignment references are assigned to each treasury position. ​You use the account assignment reference to determine the G/L account in which a treasury position is managed.

The substitution rules are executed during the automatic process for determining account assignment references when an OTC transaction is created.​

Rules for the determination of account assignment references can be defined by you and are predefined in the content:

• You can define rules in the Account Assignment References - OTC Transactions (Substitution Rules) and Account Assignment References - Securities (Substitution Rules) configuration apps
• If you have the Define Determination Rules - Account Assignment References in use, the settings are still relevant for the determination process of account assignment references.
• The predefined content also contains derivation rules that are also still relevant for the determination of account assignment references.

During the determination of account assignment references, the system runs through the previously described sequence.

The table exemplifies the different fields for available defining preconditions by business context. This enables you to substitute values of target fields dependent on attributes specific to the business context. The target field is the Account Assignment Reference of Position Management.

Using the Account Assignment Reference - Securities (Substitution Rules) app, you can display, change, and create substitution rules to determine the account assignment references of securities. Account assignment references are assigned to each treasury position. ​You use the account assignment reference to determine the G/L account in which a treasury position is managed.

The substitution rules are executed during the automatic process for determining account assignment references when a securities transaction is created.​

You manage substitution rules by business context. A context represents the circumstances in which the substitutions are defined and applied. It determines the fields that are available for the definition of rules.

At runtime, business users create financial transactions. This triggers the automatic determination of the account assignment references for the corresponding treasury positions, and the rules that you have defined are applied automatically. In case of a substitution the system derives, replaces, or clears values for the relevant fields defined in the substitution rules. The substitutions take place at the time of data entry with no system messages.

View the previous example to learn about how the target field (account assignment reference) is derived.

Using the Define Determination Rules - Account Assignment References app, you can define rules for the automatic determination of account assignment references for parallel valuation areas. You define the rules for each product group and subledger position that enables you to make postings to a position. Business rules for OTC Transactions and Securities are available.

Note

The Account Assignment References - OTC Transactions (Substitution Rules) and Account Assignment References - Securities (Substitution Rules) apps replace this app. The Define Determination Rules - Account Assignment References app is deprecated and will soon be deleted from the launchpad. We recommend that you switch to the successor apps.

Note

The Define Determination Rules - Account Assignment References app is deprecated and will soon be removed from the launchpad. However, if you have the Define Determination Rules - Account Assignment References app already in use, the settings are still relevant for the determination process of account assignment references.

Various account assignment references are predefined in the Define Account Assignment References configuration step under the following: Manage Your Solution → Configure Your Solution → Finance → Treasury and Risk Management → Treasury Accounting.

As outlined above, the predefined account assignment references are used if otherwise no suitable rule can be found and applied in the SAP S/4HANA Cloud system.

Differentiation terms are used to determine how the positions are created. Some differentiation terms are defined by the system for each product group, and others can be selected additionally. The differentiation SEC. ACCOUNT is defined and assigned for all company codes and valuation areas that do not have a specific differentiation assignment. For Securities, the following is predefined:

• Valuation area
• Special valuation class
• Accounting code
• Security class ID number
• Securities account

In addition to that, you can define and assign your own differentiation in the Define and Assign Differentiation configuration activity. This enables you to use account assignments of other areas, such as Cost Center, Profit Center, WBS Element, and Functional Area, to differentiate treasury positions in Treasury and Risk Management. When the flows are posted to Financial Accounting, the account assignment values for a treasury position are also transferred to Financial Accounting.

The simulated period-end closing uses the framework of the operative period-end closing functions. Therefore, the simulated valuation includes, for example, all relevant valuation results that are also generated by the real valuation during period-end closing.

Click on the single elements of the simulated period-end closing below to learn more.

In order to run the simulated period-end closing, the following prerequisites must be met:

• Make sure that the market data (such as exchange rates and interest rates) are up-to-date because the simulated period-end closing operations require current market data.
• Net Present Values (NPV) values need to be stored in advance of the valuation of treasury positions and of the classification. You can enter the NPVs manually (using the Enter Net Present Values app), or start the calculation of the NPVs using Calculate Net Present Values - With CVA and DVA.
• You must execute the simulated valuation before or together with the simulated classification.

Note

The system does not check the availability of current market data for the key date.

In the Simulate Period-End Closing app, key figures are used to verify how balance and P&L figures have been developing since last period end.

The simulated key figures cover all relevant Period-End Close figures, which are usually generated within the period end closing process. The idea for the simulation key figures is to call the wrapped functionality, which is used in the operative transactions, and reuse the calculated results for reporting without generating any persistent flows in and postings from the subledger.

Therefore, the simulated key figures are using the same framework as the operative procedure to assure coherence between reporting and subledger values. Based on the most recent book value from the last period end closing without reset the customer can see at a glance the balance effects, the P&L revenue and expenses as well as potential interest payables/receivables as of today.

You can use the following procedure to work on the simulated period-end closing:

1. Select the treasury positions for which you want to perform the simulated valuation. To do this, you must choose the relevant product groups. In addition, you can use the fields available under General Selections to restrict the selection of the treasury positions. The General Selections area of the interface provides selection criteria - Company Code, Valuation Area, Product Type, and Valuation Class - as relevant for all product groups, as well as selection criteria relevant for specific product groups.
2. In the Simulation Parameter area, you control how the report is run.
   • If you want to recalculate outdated simulated valuation results of the selected treasury positions, set the Recalculate Outdated Sim. Val. indicator. The recalculation can be executed for outdated treasury positions for a specific date or period, or for all outdated treasury positions. Enter the date range for recalculation according to your needs.
   • If you want to carry out simulated period-end closing, you must enter the simulation date as the key date.
3. Choose which function you want to execute:
   • Valuation
   • Accrual/Deferral
   • Classification

The result of the simulated period-end closing is composed of the following:

• For the selected treasury positions, the selected period-end closing operations are executed on the entered simulation date according to the settings of the position management procedure and the relevant configurations for the period-end closing operations based on the current market data.
• A message log is shown for the simulated period-end closing run.
• The results are shown in the results list. Each row represents a treasury position and shows the simulation results, such as the new book value in position currency and in valuation currency and also all other new position component values. You can mark a row and choose Display. In the following Details box, you see the information for the selected treasury position, the new book value of the treasury position in position currency and in valuation currency and all other position component values (empty fields are not displayed).
• The results are stored in database tables.

The Delete Results of Simulated Period-End Closing app deletes the results of simulated period-end closing for a specific date from the database tables.

Simulated Period-End Close results which are invalidated automatically by a real Period-End Close run can be deleted from the database tables in this way.

The result of this action is that simulated valuation results for the selected treasury positions and the position value date entered are deleted from the database table. A message log is shown for the deletion run of simulated valuation results.

Use the Enter Book Values for Manual Valuation app to enter the new book values for treasury positions for a specific key date.

After you have entered the new book values, you can start the valuation of the treasury positions using the Run Valuation app executed with the valuation category Manual Valuation With Reset or Manual Valuation Without Reset.

This valuation categories allows you to write-up or write-down a position to the book values entered in position currency and valuation currency in the Enter Book Values for Manual Valuation app, independent of the valuation rules defined.

The following valuation steps support manual valuation:

• Security valuation
• Foreign currency valuation
• One-step price valuation
• Index valuation

Select the Manage Your Solution app in order to get to the Configuration screen.

The task Configure Your Solution will allow you to maintain certain processes.

By performing this configuration step you can create your own bank guarantee types to be used for the trade finance process.