Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 1

11/8/2019
SAP In-House Cash (FIN-FSCM-IHC)

Generated on: 2019-11-08
SAP ERP | 6.0 EHP8 SP13
PUBLIC
Original content: https://help.sap.com/viewer/da5ab0fa48b34143a25d0e08448f5219/6.18.13/en-US
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/viewer/disclaimer.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=22067557&topics=9900c5536a51204be10000000a1… 1/85
11/8/2019
SAP In-House Cash (FIN-FSCM-IHC)

Purpose
SAP In-House Cash is used for processing internal and external payment transactions within a group or company. By using SAP
In-House Cash you can reduce the number of external bank accounts you hold and the volume of foreign payments you have to
make. SAP In-House Cash is implemented at a central location within a group of companies, for example, in head office.
With SAP In-House Cash , you can process the following transactions:
Internal payments
Central payments
Local payments
Central incoming payments
The following graphic shows the ow of data within a group of companies that uses SAP In-House Cash in its head office.
Implementation Considerations
To use the In-House Cash functions, make the necessary system settings in the Implementation Guide (IMG) by choosing
Financial Supply Chain Management In-House Cash.
Make the following settings in the implementation guide (IMG) under Financial Accounting for the subsidiary companies and head
office.
11/8/2019
Note
This documentation refers to the new functions in SAP ERP2004. If under exceptional circumstances, you do not use these
functions, you can refer to the documentation for previous release (SAP Enterprise 4.70) of SAP In-House Cash in the SAP Help
Portal.
Integration
SAP In-House Cash is connected to the head office's Financial Accounting (FI) system, and uses its functions, such as the
payment program. The affiliated companies also use Financial Accounting (FI) functions. For instance, they also use the payment
program to clear open items. The IDocs generated as a result automatically forward payment orders to the in-house cash center.
Electronic account statements for the house bank of the head office can be imported to Financial Accounting (FI), and the data is
passed on to the in-house cash center. The affiliated companies also receive an account statement from the in-house cash center.
If you create an IHC nancial status , you can forward this to SAP Cash Management .
Scope of Functions
The main component of SAP In-House Cash is the in-house cash center which processes payments between the various
subsidiary companies. The in-house cash center is basically a virtual internal bank where subsidiaries hold current accounts.
Current account processing depicts receivables and payables between the in-house cash center and affiliated subsidiary
companies. It calculates the turnover and balances of the current accounts and forwards this information in summarized form to
Financial Accounting (FI).
Note
You can decide to implement one or more in-house cash centers within your group of companies.
You can nd the SAP In-House Cash functions on the SAP Easy Access screen under Accounting Financial Supply Chain
Management In-House Cash .
Example
The following graphic shows a group of companies, organized to enable both cross-bank-area and local payments:
Two companies use SAP In-House Cash and both serve as internal banks for a certain number of subsidiary companies.
They are also mutual clearing partners.
Subsidiaries 3 and 4 carry out local payments as clearing partners for other subsidiaries.
International Group Structure
11/8/2019
Bank Area
De nition
Organizational unit of Bank Customer Accounts that allows independent account management. This also means that the account
numbers that exist in a bank area must be unique.
Note
In SAP In-House Cash , the number of bank areas that you de ne corresponds to the number of cash centers you have.
Structure
Customizing Settings
You make settings for bank areas in Customizing for Bank Customer Accounts (BCA). The important settings are described
below:
Bank key
Check digit method that controls or checks the issuing of account numbers
Time at which posting cut-off is to be automatically executed every day
Exchange rate category that stores conversion rates in the system
11/8/2019
Country, language, and the public holiday calendar used
Special Feature: Bank Area and Bank Key
The bank key is particularly signi cant, since bank keys, along with the account number, are used for the processing of payment
transactions. All banks participating in payment transactions can be identi ed by a unique numerical labeling.
Branch offices either have their own bank identi cation number or one that is related to their main office.
The internal organization of a bank may require several bank areas to depict the bank structure.
One Bank Key Can Involve Several Bank Areas
The system checks that the account number is unique in all bank areas with the same bank key. In addition, to avoid the creation
of the same account number simultaneously in different bank areas, the system locks this account number in all bank areas
belonging to the bank key.
Note
If the previous or feeder system transfers payment items, the bank area must rst be determined by means of the bank key.
The system is equipped with suitable checks for this.
When payment items are forwarded externally, the system may not be able to determine the appropriate bank area. If such a
payment item is forwarded by a Business Application Programming Interface (BAPI) to the system and the system cannot
determine the bank area, the BAPI is terminated with the return code system error. This means that no items are processed.
Integration
The bank area, as the central element, affects almost every unit of the system.
Assignment of Company Code
If you use SAP Financial Accounting (SAP FI), you must assign one company code to a bank area. You can assign more than one
bank area to a company code, but can assign only one company code to a bank area.
Financial Accounting System Assignment
You can assign different nancial accounting systems to different bank areas. However, you cannot assign more than one nancial
accounting system to a particular company code.
Example
You assign the following company codes and nancial accounting systems to the bank areas listed below:
Bank Area Company Code Financial Accounting System
0001 0001 A
0002 0002 A
0003 0001 A
0004 0003 B
11/8/2019
You now want to assign bank area 0005 to company code 0002 and nancial accounting system C. The system does not allow you
to save this record since company code 0002 is already associated with the nancial accounting system A.
The following graphic illustrates the assignment of company code and nancial accounting systems to bank areas:
Example
If you are using multiple accounting systems (FI), and are using the Reserve for Bad Debt (RBD) tool to aggregate accounts for
a business partner, you must ensure that you do not aggregate accounts across company codes.
Current Account Master Data

Purpose
Normally you create master data once, and this then serves as point of reference for transaction data. However, if necessary, it is
possible to make changes. Master data forms the data basis to enable you to work with the system.
Implementation considerations
You must rst have created master data before you create transaction data for this master data.
11/8/2019
Integration
The current account system uses the Financial Services Business Partner.
Scope of functions
The following components belong to the master data of current accounts:
Business partner
This data contains all details on business partners with whom a bank or the In-House Cash Center is affiliated. Business partners
can be customers, other banks or In-House Cash Centers, but also internal organizational units that, for example, assume the role
of account manager.
Conditions
The master data of the conditions contains all the important information needed for interest and charge settlement of an account
and also for value date activities .
Limits
The master data of the limits is needed to restrict the amount-based drawing on an account and therefore affects account
management.
Product de nition
Products can be con gured, step by step, much along the lines of a 'building block' principle. An account is characterized by the
attributes of the freely de nable product assigned to it. Contained in the product are the possible conditions, relevant transaction
types and functions, and also the media with which the customer has access to the account.
Account
You create accounts as characteristic of a product. In the master data of an account you nd all the important information on
account management and on the administration data.
Business Partner in the Current Account

System
De nition
Bank Customer Accounts (BCA) uses the SAP Business Partner for Financial Services. For more information, see SAP Business
Partner for Financial Services. In this section there is a short description of the special features that you must be aware of when
you use the SAP Business Partner for Financial Services in Bank Customer Accounts (BCA).
Use
A business partner can have different roles for an account. The following standard roles are supported by the standard system:
Account holder
A business partner in this role must be assigned to every account. As well as being a source of information, this business
partner is also checked during payment transactions. Only one account holder can exist for an account. If the account was
11/8/2019
opened for a group of persons, (a married couple, for example), you must de ne this as a separate business partner. You
must assign the individual persons to the account accordingly as authorized drawers.
Authorized drawer
An authorized drawer has the same access to the accounts as the account holder. The account holder is also the
authorized drawer for the account. If the account holder is not a natural person, you must specify at least one authorized
drawer for the account.
Note
In Customizing you can set the check for the existence of an authorized drawer when an organization is assigned as
account holder. The system runs the check by using a function module stored for event
BKK_BKKA_EVENT_DCHCK_AUTH_AV. If you deactivate this event in the business partner event control, the system
does not run the check. See also: Events (Business Transaction Events)
Account maintenance officer
Organizational unit of the bank that is responsible for the management of the account. This is normally one of your
employees.
Bank statement recipient
If a bank statement recipient has not been speci ed, the account holder takes on this role. However, if a business partner is
assigned in the role of bank statement recipient, only this partner receives a statement, not the account holder. If you want
the account holder to also receive a statement, create the holder as another bank statement recipient. The account holder
then receives a copy.
Contact person
If the account holder is an organization, you can assign more than one contact person to an account. The assignment is
purely for information purposes.
These roles are standard roles in the SAP Business Partnersystem. Use only the following standard roles delivered by the
component:
BKK010 Account Holder
BKK020 Authorized Withdrawer
BKK030 Bank Statement Recipient
BKK200 Account Maintenance Officer
Validity Restriction
The validity of a role of a business partner is restricted in the system. When you create the business partner, it has unlimited
validity in this role from the system date of creation.
BCA enables you to shift the validity start into the past. You may only make a change for a future date if there are no active
accounts for this business partner.
You cannot directly change the Valid To date. This date is set to the account closure date when you close the account, if the
business partner in this role is not active in any other account.
Delete and Archive the Business Partner
You can delete a business partner in a role if the business partner is not active in this role in an account.
11/8/2019
You can archive or delete business partners only if the business partner is not associated to an active account.
Total Commitment for a Business Partner
You can use the Total Commitment feature to view a cross-system summary of the accounts and contracts for a business partner,
with a limited amount of master data. You can also navigate to the account maintenance screen in Bank Customer Accounts from
the Total Commitmenttab page.
Restriction of Payment Order Recipient
Payment order recipients are accounts that are set up for a business partner to use for transactions.
On the Payment Transactions tab page for the business partner, you can specify which accounts are to be used. These accounts
are then available in a dropdown list for bank details in the recipient of the payment order, forward order, and standing order. Since
IBAN and business partner identi cation is required for successful SEPA transactions, the IBAN is shown in this dropdown list
instead of the bank number and bank account. The system also validates the ordering party mandate to ensure that the mandate
sender (paying party) IBAN is an authorized account.
Condition
De nition
Use
A condition determines the basis for balancing in account balancing and payment transactions. Interest calculation, charge
levying and value date methods are controlled by conditions.
Each condition is of a certain category. This condition category determines the functions with which a condition is applied to the
calculation of charges, interest and the value dating. The customer can create additional condition categories, but these are not
recognized by the system unless you make additions to the standard system. The condition categories are divided into the
following groups: interest, charges and value date.
The following displays the condition categories supplied in the standard system:
Group Condition categories
Interest Debit interest
Debit interest is used for calculating the interest on debit balances.
Credit interest
Credit interest is used for calculating the interest on credit balances.
Overdraft interest
Overdraft interest is used for calculating the interest on amounts

that exceed the overdraft limit de ned for the account. The
overdraft interest relates to the debit interest.
Transaction interest
The transaction interest is used for certain business transactions

such as returned debit memos, and relates to the transaction type.
Commitment interest
11/8/2019
Commitment interest is used for non-utilized limits. This is based on
the difference between overdraft limits and value date balances.
Interest penalty
The interest penalty is used for amounts that are included in the
allowance, and is based on the transaction type. The penalty is
calculated when the withdrawal is made.
Bonus
The bonus calculation is enabled by business transaction event

00010860 in account balancing.
Charges Transaction charge
Transaction charges are levied for certain transactions and depend

on the operation.
Item charge
Item charges are levied for each item posted to an account.
Dispatch expenses
Dispatch expenses are levied for each bank statement sent out
(counter must be updated externally).
Account maintenance charge
Account maintenance charges are levied each time the account is

balanced.
Direct charges:
Direct charges can be levied for functions used on the account (for
example, account closure).
Value dating Value date
Value date conditions determine the point in time of the value

dating.
You can specify that the value date is based on the due date of the
payment transaction instead of the posting date by selecting the
relevant checkbox on the editing screen for value dates.
Value date subject to nal payment
Subject to nal payment conditions determine the inclusion of an

item in the subject to nal payment balance.
You can specify that the value date is based on the due date of the
payment transaction instead of the posting date by selecting the
relevant checkbox on the editing screen for value dates.
Conditions are organized (as are condition groups and item counters) in condition areas. You need to assign a condition area to a
product in Customizing (the decision must be made globally). First you set up the condition areas and then, with the help of the
Product Con gurator, you assign them to the product.
Structure
A condition consists of a condition header and one or more condition items (note on terminology: The condition header is
described in the system as a condition, which also applies in this documentation. The term Condition Header is only used if there
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=22067557&topics=9900c5536a51204be10000000a… 10/85
11/8/2019
is some doubt as to whether the term Condition describes the condition header and condition items, or only the condition
header).
In the condition you de ne what the condition is, the calculation methods it is based on, and the data that controls it.
Depending on Customizing, a condition can be time-dependent or static. For time-dependent conditions you must specify time
periods to which the header data to apply. Static conditions apply without restriction from the time the condition is created. Note
that you cannot change the condition data once the condition has been used to balance an account.
The condition items contain interest and charge rates and are always time-dependent, meaning that they have a certain validity
period.
You can assign more than one condition item to a condition if:
The condition items have differing validity periods. This means you can view the historical condition items for the condition
at any time.
The condition is scaled, whereby different conditions are de ned for different areas of the assessment basis.
Example: The interest rate applied up to 10,000.00 is different from that applied to higher amounts.
You assign a new condition to an account by means of a condition group (individual conditions are an exception to this) in which
all relevant standard conditions for a group of accounts are summarized.
A condition group always belongs to a certain condition group category. The standard system contains the categories Interest
Condition Group, Charge Condition Group and Value Date Condition Group.
Integration
You can assign certain conditions to a product by using the condition area for which the conditions were created. You de ne the
possible assignment in Customizing by choosing Master Data Conditions Basic Settings .
In Customizing, you can specify the duration of the interest guarantee for selected products when offers are created. Choose
Master Data Conditions Specify Periods for Interest Guarantee for Offers . If the account contract is created within this
period, it is not possible to change the conditions. Once this period has expired, you can decide whether the xed interest is to still
be transferred if a contract is created.
Principle of dual control
Once you have created conditions, it is possible to prevent their use for balancing accounts until after they have been released by
another user with the appropriate authorization. In the Implementation Guide (IMG) you can decide to apply the principle of dual
control by choosing Master Data Conditions Basic Settings De ne Conditions (Dual Control Principle indicator).
Creation of Conditions
Purpose
You create conditions as basis for balancing and for payment transactions. It is important to identify the validity range for which
you wish to create a condition. The condition can be valid for all accounts of a product, it can be assigned to more than one
account, or be restricted as an individual condition to one account. The general procedure is described below, whereby there are a
few special features that apply to the assignment of standard conditions to products, and to individual conditions, but the basic
process ow remains the same.
11/8/2019
Process Flow
1. You determine the condition area for which you create conditions. The condition area determines the products that are to
be affected by the conditions according to your customizing settings.
2. You select the condition category (such as Interest Condition, Charge Condition, or Value Date Condition ) to be created
and then create a condition header. Next you de ne the basic calculation methods to be used, and specify whether you
want to divide the condition into levels.
To create more complex conditions, you can divide a condition category even further by using differentiation types. You can
use any customer or account attributes to divide the category. The combination of a condition category with the
characteristic of a differentiation type (known as differentiation value) each forms a new condition.
Caution
However, note that all conditions of the same condition category must have the same differentiation type and that each
differentiation value (or combination of two differentiation values) can only have one condition.
Example
You can combine the condition category Transaction Charge and the differentiation type Transaction Type to control
the calculation of a transaction charge for each item according to the transaction type that created the item.
Condition category Differentiation type Differentiation value Amount
Transaction charge Transaction type Debit 0.30
Transaction charge Transaction type Credit 0.10
Transaction charge Transaction type Cash deposit 0.00
The use of up to two differentiation types enables more complex combinations.
Example
The Periodic Charge condition category could, for example, be differentiated according to the creditworthiness of the
customer and the category of card used.
1. Diff. type 1. Diff. value 2. Diff. type 2. Diff. value Amount
Credit rating Good Card Debit card 10.00
Credit rating Good Card Credit card 15.00
Credit rating Good Card Customer card 0.00
Credit rating Poor Card Debit card 20.00
Credit rating Poor Card Credit card 30.00
Credit rating Poor Card Customer card 10.00
The following differentiation types are provided in the standard system: Transaction Type, Medium, Item Counter,
Dispatch Expense Counter, Transaction Type Category, Feature, Activity, Dynamic Balance, Term Unit
Days/Month/Year and Term Level Month/Year. In Customizing you can also create other differentiation types based on
any kind of account or business partner attributes.
11/8/2019
If you have de ned your own differentiation values to calculate your balances for the term-dependent conditions and the
bonuses in Customizing, you can also use these as additional differentiation types (choose Master Data -> Conditions ->
Differentiation Values -> Maintain Differentiation Values ). You are provided with a BTE for the calculation of the balances
and bonuses. Account balancing includes the differentiation values for the terms.
3. You create condition items for this condition, in which you specify the validity term and the amount or the percentage rate
of interest or a charge. In the case of interest conditions you can choose between linear and exponential interest
calculation. You must enter several items for a condition if you want to specify different validity periods or if you want to
create a condition with different levels (for example, interest scale).
As a result, you have a condition master record, which you assign to one or more products using the condition area. You
can assign a condition to a certain group of accounts by using a condition group (for more information, see Assigning
Standard Conditions to an Account ).
If you activated the principle of dual control for conditions in Customizing, the condition cannot be used for a balancing until it is
released by another user.
For more information, see: Releasing Conditions .
Creating Conditions
1. Choose Conditions -> General Conditions (or the respective condition class) -> Edit, and choose the appropriate interest,
charge or value date condition category, and the condition area for which the condition is to apply. The following condition
categories are supported by the standard system:
Interest conditions Charge conditions Value date conditions
Debit interest Transaction charges Value date
Credit interest Item charges Subject to nal payment value date
Overdraft interest Account maintenance charges
Transaction interest Direct charges:
Commitment interest Dispatch charges
Interest penalty
Bonus
2. The system displays an overview of all the conditions of the selected condition category already existing for this
condition area. Choose Conditions -> Create , or the appropriate button. Enter the name of the condition, the currency
and, if required, a sort term.
3. To differentiate the condition using on certain characteristics of the account or the business partner, choose one of the
preset differentiation types and the corresponding value.
To further differentiate the condition, enter another differentiation type and the corresponding value.
If you have chosen time-dependency for conditions, you base the following settings on a certain time period. In this
case, specify as of when the condition is to apply.
4. For interest conditions and some charge conditions you can also make speci cations regarding the calculation methods to
be used.
5. For various interest and charge conditions you can scale the condition according to intervals. You can create the amount of
interest, for example, making it dependent on the size of the existing balance (scaled/interval conditions).
11/8/2019
6. In the case of interest conditions you can choose between linear and exponential interest calculation. If you select the
Exponential Interest Calculation eld, you specify exponential interest calculation for this condition item.
7. Choose Transfer . You have now created a new condition.
8. If the principle of dual control for conditions is activated, release the condition ( Releasing Conditions ).
Creation of Interest Conditions

When you create an interest condition, you need to specify its calculation methods. The following settings are available:
Interest method
You specify an interest calculation method .
Linear interest calculation
If you do not select the eld for exponential interest calculation, the system calculates the interest as follows:
Amount = calculation base amount x percentage rate / 100 x days / base days
Exponential interest calculation
If youselect the eld for exponential interest calculation, the system calculates the interest as follows:
Amount = calculation base amount * ( q** (days / base days) - 1)
where
q = 1 + percentage rate / 100 (compounding factor).
When you create a transaction interest condition, you can specify an allowance for which no transaction interest is calculated.
When you create an overdraft interest condition , you can use the Additional Debit Interest indicator to calculate the interest that
you de ned in the condition in addition to the debit interest de ned for the account.
When you create an interest penalty condition you can de ne the number of days for which the interest penalty is to be calculated
in the Calculation Method of Interest Penalty eld. The 90 and 900 day methods are implemented.
Interest Calculation Method

The interest calculation method determines according to which time-dependent basis interest is calculated for mid-year
payments. The various methods take differences in the length of the months and leap years into consideration in different ways.
The interest calculation method is de ned by the quotients
days
---------------
daily basis
The methods for calculating the number of days of each calculation period (meaning the number in the counter) are:
ACT
11/8/2019
The actual number of calendar days between two dates is calculated.
360
For this method the year is considered to have 360 days and a month 30 days. The 31st of a month is not considered to be an
interest day.
Contrary to method 360E, the time from February 27 to February 28 is considered to be one day, the time from February 28 to
March 1 as three days.
Example: Days Calculation Method 360
360E
For this method, used, for example, on the Euro market, the number of days results similarly to the formula above.
The number of days between two dates D1/M1/Y1 and D2/M2/Y2 is calculated as follows:
(Y2 - Y1)*360 + (M2 - M1)*30 + (D2 - D1)
The time between February 27 and February 28 of a year is calculated as three days.
Example: Days Calculation Method 360E
The following are de ned for the daily basis (denominator value):
360
A year is considered to have 360 days.
365
366
A year is considered to have 365 days, a leap year 366 days.
The system supports the following so far:
360E/360 (bank calendar Euro market)
360/360 (German method)
ACT/360 (French method)
ACT/365, ACT/366
Creation of Charge Conditions

When you create certain charge conditions you can calculate the charge in different ways. The following settings are available:
Free items : When you create an item charge, enter the number of posting items to be executed free of charge in each balancing
period. When the system balances accounts it deducts the number of free items from the item counter and thus charges for fewer
items. The number of free items must not exceed the total number of items.
11/8/2019
Time period and time unit: When you create a periodic charge, enter the frequency (time period) for the charge. You de ne the
time unit in a separate eld.
Example: A charge of 10.00 USD is incurred on a monthly basis (time period of one month). For a balancing period of three
months, therefore, a charge of 30.00 USD is levied.
When you create conditions for the calculation of item charges , note the following:
You need to create conditions for item charges as differentiation conditions. Choose the supplied differentiation type Item
Counter . The individual differentiation values correspond to the item counters de ned in Customizing. The value of each counter
is multiplied by the respective charge amount. Any free items (see above) are taken into account.
Example
Example:
There is an item counter for interest and charge items (free) and an item counter for all other items. These are to be charged at
0.05 USD.
The differentiation type would be Item Counter in this case. Specify a charge amount of 0 for the differentiation value of item
counter 1 and a charge amount of 0.05 for the differentiation value of item counter 2.
The same applies to dispatch expenses (differentiation type dispatch expense counter).
Period Charge Not Based on Balancing

Purpose
It is possible to levy account maintenance charges in two different ways:
Based on the de ned balancing period
Based on when they are due
The system uses the whole period to calculate the charge based on the balancing period. If the charge is levied based on when it is
due, the amount is related to the actual time period involved.
You can levy function of charges when they are due for opening and closing accounts, and when you change the balancing data.
You can de ne this charge for new accounts and also for existing account maintenance charges.
Function Description
An account maintenance charge is generally due on a monthly basis. When an account is opened or closed, however, the time
period on which the charge is based can differ from one month.
When you create an account maintenance charge, the Time Period , Time Unit , and Pro Rata Calculation elds allow you to
adjust the charge. If you use these elds, you can specify that the charge amount is not to be levied for the balancing period as a
whole, but is only to apply for a certain length of time.
Example of a period-based calculation:
Condition: 20 USD account maintenance charge for two months
11/8/2019
Balancing period:
1 month -> 10.00 USD
2 months -> 20.00 USD
3 months -> 30.00 USD
Condition: 0.10 USD account maintenance charge for one day
Balancing period:
12/31/99 – 01/31/00 -> 3.10 USD
12/31/99 – 02/28/99 -> 5.90 USD
12/31/99 – 03/31/00 -> 9.00 USD
Procedure
Choose Conditions → Charges → Edit
Enter the condition area and choose Account Maintenance Charge as the condition category.
Choose Create Condition or double-click on an existing account maintenance charge.
Enter the Valid From date.
Enter the time period and the time unit.
This data means that the charge amount is not calculated for the whole balancing period, but proportionately.
Specify whether the calculation is to be pro rata.
The system uses this eld to determine how the remaining days are to be dealt with. You have three alternatives to choose from:
No inclusion: The charge is only levied for the full months.
Full inclusion: The whole charge is levied for an additional full month.
Pro rata calculation: The system calculates the charge amount proportionately for the remaining days.
Example without pro rata calculation:
Condition: 10.00 USD account maintenance charge for one month
Period for balancing: Two months and 15 days
No inclusion 20.00 USD
Full inclusion 30.00 USD
Example of pro rata calculation:
Condition: 20 USD account maintenance charge for two months
11/8/2019
Balancing from 15/06/99 to 08/31/99
The charge amount is 10 USD per month.
The balancing period amounts to two months and 16 days
End date of the period of full months is 08/15/99
The next end date would be 09/15/99
The period between 08/15 and 09/15 is 31 days
The charge for the period of the full months is 20 USD
The charge for the remaining days is 10 USD/31 days x 16 days = 5.16 USD
This means the entire charge is 25.16 USD.
Direct Charge
De nition
A direct charge is a condition category that is applied in your bank / company for one-off activities. This can include, for example,
a percentage rate or xed rate charge for the provision of credit. A direct charge could also be a charge for copying a bank
statement.
Note
The statements relating to checks / check management and standing orders apply for banks only.
Use
To create conditions for the calculation of direct charges , proceed as follows:
Note that for direct charges the differentiation type must always be ʻFeature’, so that this can correspond to the Customizing
settings.
The following settings are necessary for bank statement duplicates:
1. Choose Conditions Charges → Edit Direct Charges,and thenCreate Condition .
2. As the rst differentiation type, enter ʻFeature’.
3. As the differentiation value, enter ʻBank Statement’.
4. As the second differentiation type, enter ʻActivity’.
5. As the differentiation value, enter ʻCreate Duplicate’ (D1).
The following settings are necessary for issuing and locking checks:
1. As the rst differentiation type, enter ʻFeature’.
2. As the differentiation value, enter ʻCheck’.
11/8/2019
3. As the second differentiation type, enter ʻActivity’.
4. As the differentiation value, enter ʻCreate’ (01) or 'Lock' (05).
Note:
ʻDirect charges’ are always linked to features. If features are not de ned, no automatic charge postings are
generated.
You want to de ne different charges for issuing checks, for example, a different charge for Euro checks than for
crossed checks. In this case, instead of choosing the differentiation type Activity , choose the differentiation type
Position Type . The direct charge speci ed then applies for issuing checks of the selected position type.
Structure
It is possible to levy a charge in the following areas:
Bank statement:
For the creation of a bank statement duplicate
Check (cheque) management:
For issuing checks
For locking checks
Account closure
Standing orders
Overview of possible differentiation types:
Operation 1. Diff. type 1. Diff. value 2. Diff. type 2. Diff. value
Bank statement Feature Bank statement Activity Creating duplicate
Check (Cheque) Feature Check (cheque) Activity Create / lock

Management
Position type Euro-check / order

check...
Account closure Feature Account closure Activity Execute
Medium Document / EFT /

online...
Transaction type Account closure

internal / account
closure external ...
Standing Order Feature Standing Order Activity Create / change /

delete
Caution
The differentiation type feature is used exclusively for the determination of the transaction type for charge posting
(assignment: Feature - charge transaction type).
11/8/2019
In a condition group, the differentiation types for all 'Direct Charges' conditions must be identical (to ensure uniqueness).
This does not apply if the condition is a markup condition.
Posting Charges Separately

Use
To show the income from different charge types separately (possibly as a service for your customers or for accounting reasons),
you can post the charges separately depending on what they are for.
Prerequisites
Prerequisite 1:
In the Implementation Guide (IMG), set the indicator "Post charges separately" by choosing
Master data Product de nition Product Create product Feature Account balancing Indicator: Post charges separately.
If the indicator is set, the charges are posted as separate transaction types and shown as such accordingly.
If the indicator is not set, the charges are grouped together and posted as one transaction.
You can specify the following charge types:
22 - item charge debit
23 - item charge credit
24 - dispatch expense charge debit
25 - dispatch expense charge credit
26 - account maintenance charge
(The credits of the above-mentioned charge types are not direct reversals of the debits, but apply in the case of negative values on
item counters. Negative items, on the other hand, can result from reversals).
Prerequisite 2:
Create new transaction types in the Implementation Guide (IMG). Do this by choosing Account management Basic functions
account management Maintain transaction types. In this IMG section you can also create your own transaction types.
The following transaction types are supplied with sample Customizing:
1220 - item charge
1230 - dispatch expenses
1240 - account maintenance charge
6220 - credit from item charge
11/8/2019
6230 - credit from dispatch expenses
Prerequisite 3:
Assign the transaction types to the posting categories in the Implementation Guide (IMG). To do this, choose Account
management Assign posting categories to transaction types.
Procedure
1. Choose Account Create.
2. Choose Balancing .
3. In the Account balancing section, set the indicator "Post charges separately".
If you create an account, the default setting stored for the product applies. However, you can change this setting on the account
and have the charges grouped together as usual.
Result
If the indicator is set, the charges are shown separately. However, if it is not set, the charges are grouped together and also
transferred together as one posting to the general ledger.
Creating Value Date Conditions

When you create value date conditions, you must differentiate them with the differentiation type Transaction Type.
Note
If the value date condition is to apply for all transaction types, use the default control by entering " " (blank) in the
differentiation value.
Since value date conditions often relate only to differentiation type and differentiation value, you can create a value date
condition for all currencies. To do so, enter " " (blank) in the currency eld. When editing this condition, the system rst checks
if there is a condition for the account currency. If this is not the case, the system checks if the condition was saved under a
blank space, meaning it applies for all currencies.
Note
You can specify that the value date or the value date subject to nal payment condition is based on the due date of the
payment transaction instead of the posting date. From the SAP Easy Access menu, choose Bank Customer
Accounts Conditions Value Dates Edit. Select the VDt on Due Date checkbox.
Scaled Conditions
As scaled condition, the credit interest rate is calculated using the scales/levels.
Scale/level from to Interest rate
1 0 5000 2%
2 5000 5%
11/8/2019
If the balance is 4,000.-, 2% of 4,000.- is credited. If the balance is 7,000.-, 5% of 7,000.- is credited.
If the credit interest rate is de ned as scaled condition based on intervals, in accordance with the example above, if the balance is
4,000.- there is a credit of 2% of 4,000.-. If the balance is 7,000.-, 2% of 5,000.- + 5% of 2,000.- is credited.
This means it is possible to depict interest-free base amounts.
Creation of Scaled/Interval Condition Items

To create a scaled condition, you need to create a condition item for every level of the condition or for every interval. In the eld
amount limit , specify what limits apply for the level.
If you activated the Amount To eld when you created the condition, then it applies to up to and including the amount entered.
The next level above begins after this amount has been reached. If you did not activate the eld, the speci ed amount is the lower
limit for the level.
Example
Example:
The credit interest for an account is to be 2% for a balance of 5,000 USD and 4% for a balance of 10,000 USD.
There are two options for creating the condition items:
If the indicator Amount To is not activated:
Scale Amount limit Interest rate
1 5,000 2%
2 10,000 4%
This is the usual procedure, which is clari ed below in an illustration of what happens when the Amount To indicator is set:
Scale Amount limit Interest rate
1 5,000 0%
2 10,000 2%
3 99,999,999,999 4%
However, this option is only useful if the amount for which interest is to be calculated is to have an upper limit.
You can specify the valid to date only for the rst scaled condition item, which is entered automatically for the other items.
For debit and credit interest, and interest penalty, you can either create a scaled calculation based on the current balance, or a
scaled calculation based on the contract amount.
Creation of Markup and Markdown

Conditions
11/8/2019
The system uses the Markup Condit. (Condition) indicator to determine if a condition applies as a markup or a markdown on an
existing condition of the same condition category.
Note
Before de ning a markup or markdown condition, you must create a base condition.
The system adds the value of a markup condition to the base condition value and reduces the value of a markdown condition from
the base condition value.
Note
The value of the base condition is internally set to zero if the markdown condition results in a negative overall condition.
The following rules determine the condition combinations that are used for balancing:
A standard markup condition is always only added to a standard condition while a standard markdown conditions is always
only reduced from a standard condition.
If both an individual condition and an individual markup or markdown condition exist, both are taken into account. Any
existing standard conditions and standard condition markups or markdowns are ignored.
If a standard condition, a standard markup or markdown condition, and an individual markup or markdown condition exist,
all 3 conditions are totaled.
The markup or markdown condition is ignored if the Level Interval indicator has different values for the standard condition and the
markup or markdown condition.
Creating Condition Items

Prerequisites
After you have created a condition you create items for this condition.
Procedure
1. Position your cursor on a condition in the condition overview and choose Item (position) Create.
2. Specify from which date and to which date the condition item is to apply (including the rst and last day).
3. Setting the end date for the validity range of a condition is optional and this, initially, usually remains blank. If you specify
an end date, for example for individual conditions or for expiring products, the condition no longer applies after this date
and you must create a new condition item.
Always ensure that no account exists without conditions. If you create a new condition item with a current valid from date,
this automatically applies without you having to set a valid to date for the old item.
If an individual condition and a standard condition are assigned to an account and the individual condition expires, the
standard condition assigned to the account applies automatically.
4. Depending on the condition category, the following other details are also necessary:
Interest condition item
Charge condition item
11/8/2019
Value date condition item
1. If you wish to create another item for this condition, choose the ʻNew item’ icon. If you wish to adopt the item, choose
ʻTransfer’.
2. Save your entries.
Note
Note:
You can only create condition items with a start date in the past provided they have not been used for a settlement balancing or
by payment transactions.
When editing, by choosing All items or Current item you can choose if you want to have all condition items shown or only those
valid currently and in the future.
Special Features of Interest Condition Items

When entering items for an interest condition, you must enter additional interest data.
Specify either
a xed interest rate in percentage points or alternatively
a reference interest rate (internal reference interest rate such as standard interest rate for the product or external
reference interest rate such as the LIBOR) with appropriate markups or markdowns. Make entries in the elds as follows:
Enter the interest markup / markdown in percentage points (absolute). Markdowns are identi ed by a minus sign after the
amount. Markups have no +/- sign.
For those interest conditions that depend on a reference rate, the minimum and maximum interest rate limit the lower and upper
interest amount respectively. Specify these interest rates in percentage points.
Note
You can update the values for the reference interest rates by choosing Current settings De ne reference interest rates.
Special Features of Charge Condition Items

When creating items for a charge condition, you must enter additional data.
In the case of items of a transaction charge you enter the transaction charge either as a percentage of the transaction amount, or
as an absolute amount. If you specify the transaction charge as a percentage, you can additionally specify a minimum and
maximum amount that is used if the charge calculated falls below or exceeds the minimum and maximum amount.
For account maintenance and periodic charges there is no provision for calculation of a percentage-based charge. Absolute
amounts are handled as above.
Note
11/8/2019
For a markdown charge, enter a minus sign (-) after the value and for a markup charge enter the value without a plus (+) or
minus (-) sign.
Special Features of Value Date Condition

Items
When creating items for a value date condition, you must enter additional data.
Valid to: This date restricts the validity of a condition item. Note that for standard conditions and individual conditions, the
following applies:
Standard condition: If, after the valid to date, you do not enter a new condition item with a later valid from date, no further
calculation for the condition takes place.
Individual condition: If you do not enter a new condition item with a later valid from date after the valid to date, the
standard condition of the condition group applies again.
Number of days : Here you de ne the number of days by which the value date is to be later or earlier (in the case of
negative values) in relation to the posting date (posting date + number of days = value date).
Tolerance days: (Value date max) and tolerance days (value date min.): Using the elds value date max. and value date
min. you can control what value dates speci ed by the ordering party are accepted. The basis for this comparison is the
value date calculated for number of days (above).
Value date max: This eld for the upper limit of the tolerance range indicates the maximum number of days the speci ed
value date can be in the future.
Value date min: This eld indicates the maximum number of days a speci ed value date can be in the past.
Shift to a working day: If the value date day determined falls on a Sunday or public holiday (determined in accordance with
the public holiday calendar stored for the account), with the indicator Shift to a working day you can control if and in which
direction the value date is to be shifted to the next or previous working day. When updating the value date you can specify
calendar days and working days.
The following applies if you update with calendar days: If the value date falls on a public holiday, this indicator determines if and in
which direction a shift to a working day is made.
0 no shift
+ shift to the next working day
- shift to the previous working day
If you update with working days (value W), value dates fall always only on the following working days. For the calculation of the
tolerance limits the system also interprets the days stored as working days.
Special Features of Scaled/Interval

Conditions
You can stagger the intervals of most conditions. Staggering is possible for the condition categories debit interest , credit interest
, transaction interest , transaction charge , item charge , dispatch expenses and for value date and subject to nal payment
11/8/2019
value date conditions (in the case of the last two, however, only as a scaled condition). To do this you must enter the following for
the condition:
Scaled/Interval:
You specify whether to stagger the condition, and if so, the type of calculation that is required.
If you choose Scaled Calculation, the condition item created applies to the whole balance up to the each level.
If you choose Interval Calculation, the condition item created applies only to the amount between the lower interval limit
and the upper interval limit.
Examples for Scaled Conditions
Amount To :
If you have created the condition as an interval or scaled condition, specify here whether the condition items/positions
apply up to the speci ed value or from the speci ed value. Valid From values apply including the limit, Valid To values
excluding the limit.
You must create a condition item for every level of the condition.
Note
Note that there are scale conditions based on the account balance and based on the contract amount.
Changing Conditions
Prerequisites
You can enter Customizing settings to determine whether retroactive condition changes are allowed or not, by choosing Master
Data Conditions De ne Basic Settings for Conditions. If you allow retroactive condition changes, then you can also de ne the
number of periods to which these changes may apply. You can decide whether the retroactive condition changes are to also apply
to a scal year that has already been closed.
Retroactive condition changes not allowed

If retroactive condition changes are not allowed, you can make a retroactive change to a condition (header and position) only if
this condition has not been used to balance an account, or if the condition has not yet been used in payment transactions.
You have the following options:
You can specify a new validity period for the condition header data. This option is only possible if you have activated time-
dependency of the conditions in Customizing. If this is not the case, you need to create a new condition.
To change the condition item data you must create a new item with a current validity date and changed values.
To change a single condition item of a scaled condition or insert an additional level from a certain date, you need to create the
entire scale with a new date.
Retroactive condition changes allowed

If retroactive condition changes are allowed, you can change standard or individual conditions that have already been used in
account balancing. There are, however, two restrictions: The Valid From date and the interest calculation method cannot be
changed retroactively.
11/8/2019
Once you have changed standard conditions, you need to nd the affected accounts, by choosing Retroactive Change to
Standard Condition Find Affected Accounts.
During the next balancing, the system runs retroactive accounting for all the accounts found from the relevant date onwards.
Change History
To see a history of all changes that affect conditions (such as creations, deletions, or eld changes), choose Goto Condition
History.
To display a list suitable for auditing, choose InformationSystem Condition History.
Releasing Conditions
The system locks new and changed conditions if you have activated the dual control principle in customizing under Master
Data Conditions De ne Basic Settings for Conditions. These must be released by another user.
Procedure
1. Choose Conditions General Conditions (or each condition class) Release.
2. The system displays an overview of all conditions not yet released. Place your cursor on a condition and choose Release
. If you choose Release All , you release all the displayed conditions.
Deleting Conditions
To delete a condition, proceed as follows:
1. Choose Conditions Condition Assignment Edit and delete the assignment of the condition to the condition group.
2. Choose Conditions General Conditions (or the respective condition type) Edit and specify the condition area and
condition category.
The system displays the condition overview.
3. Place your cursor on the item and choose the Select Item button.
4. Select the entry and choose the Delete button.
To delete a single condition item, follow steps one and two above, then proceed as follows:
Steps 1 and 2 as above.
1. Place your cursor on the item and choose the Select Item button.
2. Select the line with the position to be deleted and choose the Delete button .
Note
A condition can be deleted only if it has not been used in account balancing or been used by payment transactions. You
can delete all entries except the last entry in the condition header.
In all other cases, you can void conditions by setting the Valid To date of a condition item or by creating a new condition
item as of the current date.
11/8/2019
Note
Principle of dual control
The system ags the conditions for deletion only, if you have activated the dual control principle in customizing under
Master Data Conditions De ne Basic Settings for Conditions. The agged conditions are deleted only when another
user releases them.
Releasing Deleted Conditions

Use
The system locks new, changed, and deleted conditions if you have activated the dual control principle in customizing under
Master Data Conditions De ne Basic Settings for Conditions. These must be released by another user.
Procedure
1. Choose Conditions General Conditions Release Deleted Conditions .
2. Choose the condition area and a condition category, then choose Continue.
The system displays an overview of all conditions that are agged for deletion.
3. Place your cursor on a condition and choose Release .
If you choose Release All , you release all the displayed conditions. Choose Reactivation to reject the deletion.
Assigning Standard Conditions to an

Account
Purpose
Typically, when an account is created, certain standard conditions are already assigned to it by virtue of the choice of the product
and the condition group de ned for it. If you do not want these conditions to apply or if you want the conditions of another product
to apply, it is possible to assign other standard conditions .
Prerequisites
The conditions must already have been de ned. To nd out how to do this, read Creating Conditions . In this case you also need to
consider if the change to the conditions is only to apply to this one account and if it would not be preferable to create an individual
condition instead.
Process ow
1. Check to see if the required combination of standard conditions already exists in a previously de ned condition group. If
this is not the case, create a new condition group and assign the conditions to it.
2. Within the account, change the assigned condition group for the corresponding condition group category.
11/8/2019
Assigning Standard Conditions to a

Condition Group
Prerequisites
You must already have de ned the conditions. To nd out how to do this, read Creating Conditions .
If the condition group does not yet exist, rst create it. You do this in the Customizing of the condition master data (in the IMG by
choosing Master data Conditions De ne condition groups).
Procedure
1. Choose Conditions Condition assignment Edit , and specify the condition area and the category of the condition
group. Using the function button F4 you obtain a preselection of the condition groups of the corresponding category.
Choose a condition group.
2. This brings you to an overview of the conditions assigned to the condition group. Review this to see if a condition for the
required condition category already exists in the condition group. Delete the assignment by positioning the cursor on the
condition and choosing Undo assignment.
3. Choose Assign , and enter the required condition category. For this category choose one of the conditions already created.
4. Within a condition group there can always only be one condition of a condition category. There are exceptions for
differentiated conditions. Note, however, that all conditions of the same condition category must have the same
differentiation type and that per differentiation value (or per combination of two differentiation values if you are using two
differentiation types) there can only be one condition.
It is also possible that several conditions of the same condition category are assigned in different currencies. The condition
created in the respective account currency always applies for an account.
As an alternative to assigning conditions already created, you can also create conditions directly on this screen by
positioning the cursor on the condition group and then choosing Create condition . The condition created is automatically
assigned to the condition group.
5. If you have activated the principle of dual control for conditions, the assignment of the condition to the condition group
must rst be released by another user. To do this, choose Conditions Condition assignment Release .
Note
Tip:
For a history of all changes concerning the assignments of conditions to condition groups (new creations, deletion), choose
Goto Assignments history.
Assigning a Condition Group to an Account

Prerequisites
There must already be a condition group de ned in the Implementation Guide (IMG) and you must already have assigned standard
conditions to this.
11/8/2019
Purpose
Generally, when an account is created, condition groups for interest, charge or value date conditions are already assigned to the
account. These default settings relate to the condition area that applies for an account. If there are no default settings, assign the
respective condition groups. It is also possible to change the speci ed condition groups.
To assign a condition group to an account, proceed as follows:
1. Choose Account Change and enter the account number. Then choose the screen Balancing .
2. In the section Condition groups , assign the respective condition group for interest, charges and value date. Note that you
must assign a condition group for value date conditions to every account.
If you wish to change the assignment of the condition group and change the condition group of the account, note the following:
The conditions that apply are not used proportionately for the settlement period. For the settlement of the whole period, the
condition group assigned at the time of settlement is the one that always applies.
If individual conditions exist, these initially remain unchanged when the condition group is changed.
Proceed as follows:
1. In the section Condition groups , change the respective condition group for interest, charges or value date.
2. Save your entries. If you have changed a condition group for which individual conditions exist, a dialog box appears in which
you are asked how you want these handled. You have the following options to choose from:
Continue : The new condition group is adopted and the individual conditions remain in existence, unchanged.
Delete: The new condition group is adopted and the existing individual conditions are deleted.
Termination : The old condition group and the individual conditions are retained.
Interest Calculation Method

The interest calculation method determines according to which time-dependent basis interest is calculated for mid-year
payments. The various methods take differences in the length of the months and leap years into consideration in different ways.
The interest calculation method is de ned by the quotients
days
---------------
daily basis
The methods for calculating the number of days of each calculation period (meaning the number in the counter) are:
ACT
The actual number of calendar days between two dates is calculated.
360
11/8/2019
For this method the year is considered to have 360 days and a month 30 days. The 31st of a month is not considered to be an
interest day.
Contrary to method 360E, the time from February 27 to February 28 is considered to be one day, the time from February 28 to
March 1 as three days.
Example: Days Calculation Method 360
360E
For this method, used, for example, on the Euro market, the number of days results similarly to the formula above.
The number of days between two dates D1/M1/Y1 and D2/M2/Y2 is calculated as follows:
(Y2 - Y1)*360 + (M2 - M1)*30 + (D2 - D1)
The time between February 27 and February 28 of a year is calculated as three days.
Example: Days Calculation Method 360E
The following are de ned for the daily basis (denominator value):
360
365
366
A year is considered to have 365 days, a leap year 366 days.
The system supports the following so far:
360E/360 (bank calendar Euro market)
360/360 (German method)
ACT/360 (French method)
ACT/365, ACT/366
Days Calculation Method: 360

There are 28 days in the period from February 1 until February 28, 1999 (inclusive).
There are 32 days in the period from February 28 until March 3, 1999 (inclusive).
Days Calculation Method: 360E

There are 30 days in the period from February 1 until February 28, 1999 (inclusive).
11/8/2019
There are 30 days in the period from February 28 until March 3, 1999 (inclusive). This method treats February 28 as if it were
February 30.
Creating Individual Conditions

Context
Individual conditions are conditions that you assign directly to an account and that are only valid for this account. They are used to
modify conditions for an account, without having to de ne a completely new product. If an individual condition is created for an
account, this is indicated next to the standard condition groups assigned to the account.
An individual condition assigned to an account overrides the respective standard condition assigned to the account. Special
features apply for markup conditions (Special Features of Markup Conditions).
If the individual condition is deleted or no longer valid, the standard condition automatically applies again.
You create individual conditions directly on the account for which the individual condition is to apply. The basic procedure is
similar to the creation of a standard condition.
Procedure
1. Choose Account Change and then the Account Balancingtab page.
2. The ConditionGroups group box displays the condition groups for interest, charge and value date conditions used for the
account. To add more conditions to these individual conditions, or to overwrite them, choose either the Detail Interest or
Detail ChargesorDetail Value Date buttons next to the condition group.
3. The system displays the condition overview, where you create your individual condition and the items belonging to it. For
more information, see Creating Conditions. Note the following important points:
The validity period is de ned in the condition header. If you specify a Valid To date, the standard condition becomes active
again for the account after this date has expired.
You create the various condition items with their validity data. If you have de ned an end date for an item that extends
beyond the validity period de ned in the condition, the period de ned in the individual condition is the maximum that
applies.
To change an individual level of a scaled condition, you need to identify all levels as an individual condition.
4. Go back to the main screen.
5. Save the account.
The word Individual is displayed next to the condition group. This shows if individual conditions exist that are valid on the
system date.
Releasing Individual Conditions

Use
You can have individual conditions displayed cross-account by the system according to various selection criteria. It is possible to
branch from the displayed list to any account itself or to a total overview of all conditions for an account. You can also select just
those conditions you wish to release. When you enter the "valid to" date, the system selects all individual conditions that expire on
this date.
11/8/2019
You effect release either by branching to the respective account or by a mass release of all conditions on the list by setting the
indicator in front of the condition in question.
Prerequisite
If you have activated the principle of dual control in the Implementation guide (IMG), new, changed, and deleted conditions are
initially locked. These must be released by another user.
Procedure
1. Choose Account Release Release Individual Condition or Release Deleted Individual Condition .
2. Enter the account whose individual conditions or deleted individual conditions are to be released.
3. Choose Execute. This brings you to the list displaying the individual conditions for the selected account or account interval.
4. Select the condition you wish to release and choose single or mass release .
Result
The individual conditions have been released.
Limits
Use
Limits serve basically to restrict the amount-based disposal of accounts.
SAP supports six categories of limits:
Account overdraft limit : Basis for the calculation of overdraft interest for account balancing. The debit interest rate is applied to
any overdrafts tolerated that exceed this limit.
Internal account limit : Controls the coverage check of payment transactions. The account may be overdrawn up to this limit.
External account limit : The limit of which the customer is informed. This limit is for information purposes only and is generally
identical to the account overdraft limit. The external limit must always be lower than or equal to the internal limit.
Limit categories for interest compensation:
Interest compensation overdraft limit: Basis for the calculation of overdraft interest for interest compensation.
Internal interest compensation limit : Controls the coverage check of payment transactions. The account pool for interest
compensation may be overdrawn up to this limit.
External interest compensation limit : The limit of which the customer is informed. This limit is for information purposes only.
The limit categories for interest compensation are de ned exclusively on the root account. They are needed during the posting
operation since they provide information as to whether or not, according to the limit, a posting is permitted. For more information,
see the documentation on Interest Compensation .
Note:
11/8/2019
You can de ne other limit categories in the IMG. These are not supported by functionality in the standard system and must be
customer-speci cally programmed.
Integration
The issuing of limits can be subject to release in accordance with the principle of dual control, meaning that every limit must rst
be released by a second user with the appropriate authorization before it can be used for an account. You set whether or not the
limit of an account is subject to the principle of dual control in the Implementation Guide (IMG) by choosing Master data Limits
Maintain the principle of dual control for limits . An entry in this table means that the principle of dual control is to apply.
You must grant separate authorization for releasing, since releasing limits is an activity in its own right. The authorization for
releasing limits is independent of the authorization for changing an account.
When a limit is released, this replaces any limit existing for the same time period.
If you wish to assign a new limit to an account, note the following: The to-date of a limit being newly created is open,
meaning you can choose it freely.
When you newly create and release limits, the system checks if limits already exist and if the time periods possibly overlap.
Checking of the limit to be released is always in comparison with the limits already released.
Limits not released at the time of creation are checked against the limits that are not yet released.
For a certain time period you can only assign a limit of a certain category to an account, as the limits are time-dependent.
In Customizing you can de ne standardized limits for a bank area and a currency. This simpli es their application. You can assign
these reference limits to the account in the same way as an individual limit.
If the interval range of a new limit to be released overlaps the time period of a limit that already exists, the time period of the
existing limit is reduced. This means that during the overlapping period, the new limit applies.
Following are some examples to illustrate this:
Example
Old Limit New Limit
From To From To
1.1.98 10.1.98 9.1.98 15.1.98
From 01/01/98 - 01/08/98, the old limit applies, from 01/09/98 - 01/15/98 the new limit applies. After this date there are no
speci cations.
Old Limit New Limit
From To From To
1.1.98 10.1.98 3.1.98 15.1.98
From 01/01/98 - 01/02/98, the old limit applies, from 01/03/98 - 01/15/98 the new limit applies. After this date there are no
speci cations.
11/8/2019
Old Limit New Limit
From To From To
1.1.98 10.1.98 30.12.97 8.1.98
From 12/30/97 - 01/08/98, the new limit applies, from 01/09/98 - 01/10/98 the old limit applies. After this date there are no
speci cations.
Old Limit New Limit
From To From To
1.1.98 10.1.98 3.1.98 7.1.98
From 01/01/98 - 01/02/98, the old limit applies, from 01/03/98 - 01/07/98 the new limit applies, from 01/08/98 - 01/10/98
the old limit applies.
Additional Limit Functions in SAP In-House

Cash
In addition to the limit checks listed under Limits , the system also carries out a limit check on the payer account when payments
are initiated internally (such as a bank transfer). In the case of provisionally and nally posted IHC payment orders, the system
also takes the amounts in the provisionally posted IHC payment orders into account.
An IHC payment order cannot be provisionally or nally posted if the payer account check in the account management system
reveals that the total amount of the following postings exceeds the limit:
Postings to the payer account
Provisionally posted payment orders
Outgoing payments to be posted
The system converts the currency of provisionally posted IHC payment orders with a transaction currency that differs from the
account currency. It converts the total of the amounts listed above for each currency, using the average rate on the date of
execution, into account currency and uses the total amount in account currency for the limit check.
Note
When postings are reversed or payments are initiated externally (such as debit memos), the system does not take provisionally
posted IHC payment orders into account.
Nor does it take credit memos from provisionally posted payment orders into account.
The amounts set as limits in the account master data of the account management system therefore denote the upper limit of all
nally posted transactions including all debit memos from provisionally posted payment orders.
11/8/2019
Assigning Limits to an Account

To assign standard or individual limits to an account, proceed as follows:
1. Go in change mode into the account whose limits you wish to change.
2. Choose the limits screen.
You are now in the limits overview where the following sections are displayed:
3. - Account limits - account overdraft limit, internal and external account limit
- Interest compensation limits - needed for interest compensation
- Other limits - these are displayed if you have de ned your own limit categories in the Implementation Guide (IMG).
The system only displays the currently valid limits. Using the time breakdown icon you can branch to the detail display of
every limit category supplied by SAP.
4. Choose the time breakdown icon.
5. Choose Create limit.
6. Now you can decide if you want to assign a standard limit (the reference limits used for this are prede ned by Customizing)
or if you want to individually control limit assignment. You have the following options:
7. Reference limits:
8. Specify the validity period and select the ID of a reference limit. Any speci ed individual limit amount is always overwritten
by the limit amount of the reference limit. The account currency applies as currency.
9.
Reference limits can change in the course of time. To enable you to react quickly to changes in the reference limits, by
choosing Environment Current settings you have the option of making adjustments. You can change a reference limit
without having to create a new reference limit with a new ID and without having to maintain it in the affected accounts.
Furthermore, the change is valid in the past and does not lead to erroneous account balancing results.
Individual limits:
10. Enter the validity period, the amount and the currency.
11. Choose Continue .
Whether or not the limits are subject to the principle of dual control is de ned in Customizing. If the principle of dual control is
de ned, the limits must be released by another user with authorization for the account before they can be used.
Note that overdraft limits must always be released if they are subject to the principle of dual control. If overdraft limits exist that
are not released, the account is not balanced. The unreleased limit is only taken into consideration for a simulation.
Limit check of the internal limit
If the limit check is activated for the product, it is possible to maintain the internal limits for the account.
An internal limit must exist at all times. The system enters limits for any missing intervals. To do this, the system sets the indicator
ʻLimit check’ and sets the limit amount at 0. If the limit check for the product is inactive, the system sets a limit on the account
anyway. This limit has the validity period 01/01/0001 - 12/31/9999, the amount is zero and the limit check is inactive.
11/8/2019
Procedure
Activate the limit check in the Implementation Guide (IMG) by choosing Master data Product de nition Product.
Releasing Limits
Use
Before it can be used, (depending on the setting in the Implementation Guide (IMG)), it is possible that the limit must be released
in accordance with the principle of dual control by a second user with authorization for the account.
Releasing can be done directly on the account or using a list that displays all limits to be released. In the list of limits to be
released, the processing status is displayed by a traffic-light symbol.
Green = releasing is possible
Yellow = an indication that you were already in the detail display “Account”
Red = unreleased limits in mass processing due to an error
No traffic-light = limit has been released.
Procedure
1. Choose Account Release Release Limit .
A list of limits to be released appears in accordance with your speci cations.
2. To release all the limits, choose the mass release icon or to release selected limits, choose the single release icon.
Result
The created limits have been released and are now available for account management and payment transactions.
Note
Limits that you cannot release due to the principle of dual control or the authorization checks are not displayed in the list.
Deleting Limits
Use
Deletion of a limit, (depending on the setting in the Implementation Guide (IMG)), might need to be released in accordance with
the principle of dual control by a second user with authorization for the account before the limit is actually deleted.
You can delete limits directly on the account or using a list that displays all limits agged for deletion. In the list of limits to be
deleted, the processing status is displayed by a traffic-light symbol.
Green = deletion is possible
Yellow = an indication that you were already in the detail display "Account"
Red = limits not deleted in mass processing due to an error
11/8/2019
No traffic-light = limit has been deleted.
Caution
Overdraft limits that are valid before the last account balancing cannot be deleted. (They are still needed for postings in periods
already settled.) Before the deletion process, create a new limit that is valid from the account balancing and then delete the old
limit. The system automatically deletes any overlaps in the validity periods between the old and the new limit.
Procedure
If limits are subject to the principle of dual control
Flagging limits for deletion:
1. Go in change mode into the account whose limit you wish to delete.
2. Choose the Limits screen.
3. Set the delete indicator next to the limit you wish to delete.
4. Choose Save .
The limit is now agged for deletion.
Releasing the deletion process:
1. Choose Account Delete Limits .
2. Choose the account whose limit you wish to delete.
3. Release the deletion process of the limit with the icons mass release or single release .
If limits are not subject to the principle of dual control
1. Go in change mode into the account whose limit you wish to delete.
2. Choose the Limits screen.
3. Choose the limit you wish to delete. Choose Delete limits.
4. Choose Save .
The limit is now deleted.
Result
The limit has been deleted.
Product De nition
Purpose
In the area of customer current accounts, product de nition exibly supports products and their special features for every
individual customer group. Products can be con gured, step by step, much along the lines of a 'building block' principle. An
account is characterized by the attributes of the freely de nable product assigned to it. Contained in the product are the possible
11/8/2019
conditions, relevant transaction types and functions, and also the media with which the customer has access to the account. You
can create products in several versions, enabling you to react exibly to market requirements.
Implementation considerations
You de ne products in the Implementation Guide (IMG) by choosing Master Data Product De nition In the application, you can
only have the products displayed.
Scope of functions
You can de ne products exibly, fast and without programming. As well as determining the conditions, transaction types and
functions, the product also controls the view of the account data. This results from every attribute being assigned to exactly one
view, although every view can relate to one or more products. It is also possible for you to set up speci c additional elds as
customer-speci c enhancements, without having to modify the program. See the documentation on the Business Data Toolset.
This exibility for product con guration enables you to adapt various transaction types such as debit transactions at points of
sale, overdraft arrangements, check operations and other account movements using Customizing functionality.
The transaction type describes the business operation on which the payment item that is to be processed is based. It controls,
among other things, if the account is debited or if the amount is credited and also the checks that are to be made before updating
is executed.
When con guring products, it is possible to de ne the calculation of standard conditions dependent on various characteristics as,
for example, the calculation of debit interest depending on a customer’s creditworthiness. It is possible to design an account
(product) in such a way, that it is tailor-made to suit the individual requirements of a customer. (The following graphic applies
mainly to banks).
Example (for banks)
A product for schoolchildren or students without their own income "Young Account" could be con gured so that it is managed
exclusively in credit and includes interest payment on the balance. In addition, you could restrict the issuing of checks and credit
cards, exclude debit collections and permit or prohibit access using T-Online.
Product Con gurator

De nition
11/8/2019
The Product Con gurator is a tool using which you can de ne products without any programming effort.
The Product Con gurator facilitates the de nition of the business and technical features of a product, its version creation and the
layout of the functions on the interface. In addition, it enables you to make simple enhancements with regard to the inclusion of
attributes and offers general services such as change documents.
With the Product Con gurator you can maintain all information on a product and have the different information (transaction types,
media, eld modi cation, assignment of conditions) uniformly displayed.
Use
The product re ects the activities of a current account. You need the Product Con gurator to design the products. From the
perspective of the current account system, the product is the result of the de nition of elds, features and payment transaction
operations. General processing characteristics are controlled by products, these processing characteristics being transferred to
the assigned accounts.
You de ne a product and create accounts for this product. The products serve as a template and framework for accounts. A
product can exist in several versions. An account is always linked to one version of the product. If you change a product, you
decide if you wish to save the change in the existing version or in a new one. If you create a new version, the change only affects
accounts created in the future, the existing ones are not affected.
Structure
The structure of the Product Con gurator is designed as follows:
The Product Con gurator is base on the Business Data Toolset .
SAP supplies sample products.
You create products with the help of the Product Con gurator in the Implementation Guide.
The interface of the Product Con gurator is divided into three parts:
The initial screen
The administration data
The attributes
The last two are also applications from the perspective of the Business Data Toolset .
Advantages
Simple and user-friendly creation of bank products
Graphical support
No programming required
Proposed default values when de ning products
Administration of various versions of individual products
Creation of Products
11/8/2019
Prerequisites
Before creating products, you must rst have maintained a pre x for your name range and the attributes.
Pre x:
The pre x is part of a globally unique internal identi cation key. This key consists of the pre x and a consecutive number. It is
automatically generated and assigned to every attribute or product. This means you set the pre x once, and subsequently, for
every new creation of an attribute or product, the system automatically assigns the identi cation key in the set name range.
The pre x is needed to enable differentiation between attributes and products from different manufacturers. Use an own pre x for
each system so that newly created attributes and products do not overwrite existing ones.
You maintain the pre x in the Implementation Guide (IMG) by choosing Master data Product de nition Set pre x.
It is not possible to save attributes and products without specifying a pre x.
Attributes:
Attributes determine the functionality of a product, so the more attributes you assign to a product, the greater its functional
quality. This assignment is optional.
For a clearer overview, attributes are arranged in hierarchies. For technical reasons, the grouping attribute is on the rst hierarchy
level and the other hierarchy levels are attached to it. The grouping attribute has no other function.
Each attribute belongs to exactly one attribute category, the following of which are supplied:
Grouping attribute: Attributes of this category have no direct function. They serve primarily to construct the attribute
hierarchy, to classify the attributes and to assign them to attribute groups.
Field: This attribute is a visible eld in an account. You can assign a default value and a eld modi cation (required,
optional, display, hidden) to a eld. You can assign several default values to multiple-value elds. An example of a eld with
one value is the currency, an example of a eld with several kinds is the check type.
Feature: Each feature attribute involves a function that you activate by assigning the feature attribute, or deactivate by not
assigning it. Example: Bank statement, checks (cheques).
Matrix: This attribute involves two values, the cross product of which you assign to the product. Example: Payment
transaction operation. An operation consists of a transaction type and a medium. There is a certain number of transaction
types (n) and a certain number of media (m). You can assign each of the possible n*m cross products to a product.
When you maintain attributes, you rst set the attributes you basically wish to use. You have the following options:
1. You can adopt the attributes supplied by SAP without changing them, and need then make no other settings.
2. You can alter the attributes supplied by SAP by changing the hierarchy or the name.
3. You can create your own attributes in addition to those supplied.
Consider the following before maintaining the attributes: Which attributes do you need in your company and which can you do
without? How do you want the products to be designed, meaning which general and which speci c characteristic features do you
want to apply? In which sequence do you want the individual screens with the attributes to appear?
You de ne attributes in the Implementation Guide (IMG) by choosing Master data Product de nition Product attributes.
There is a description of how to change attributes or create new ones in the Implementation Guide.
11/8/2019
Process ow
1. In the Implementation Guide (IMG), choose Master data Product de nition .
2. Create a pre x for the name range in which you wish to operate.
3. Maintain the attributes you wish to use. All attributes used by the current account system are supplied.
4. Maintain the products you wish to use.
5. Note:
You cannot literally delete products. If you no longer wish to use products, archive them. You can reactivate the archived
products again if necessary.
6. If required, assign products to bank areas, as products are rst created cross-bank area. This assignment is advisable if
you wish to restrict the selection of products. You can use a product in several bank areas.
Result
You have successfully created products and can now assign accounts to them. In the application itself you have the option of
having the products displayed. Choose Product Display product .
Management of Products
11/8/2019
Purpose
The products are stored in product management in accordance with the following criteria:
Product name
Version
Status
Validity period
Cross-version data
Product name: This name is the external product ID. You assign this name when you create a product. It clearly and unmistakably
identi es the product. The description, that contrary to the product name is language dependent, is part of the product name.
Version: There can be several different versions of a product. When you create a product, the rst version of this product is
created. When you change a product, you have the option of creating a new version when you save. Versions with the status
"active" may not overlap the validity period of one another. If you create an account for a product, this relates to the version that is
active on the account opening date.
Example
Example (for banks)
In version 001 of the product Checking - Junior the securities ID is hidden. In version 002, however, it is shown.
Status: A version of a certain product can be either active or inactive. You can only create accounts for a version of the product if it
has the status "active". For all other status types it is inactive, meaning you cannot create any accounts.
You can change the status by selecting a pushbutton. This pushbutton is to take into consideration whether you have just created
a product or if it is already active. The system proposes the status changes accordingly.
SAP makes provision for the following statuses:
Parked/new product
Parked/new version
Flagged to be activated
Active
Flagged for archiving
As long as accounts exist for a version, this version must keep the status "active". If accounts still exist for a version in your
productive system, this version may also not be deactivated in the previous/feeder system (ʻ agged for archiving’).
Validity period: : The term of a version ("valid from" and "valid to") indicates the time period in which accounts can be created for
an active version. At any certain point in time there can only be one active version of a product, meaning that the validity periods
of the active versions may not overlap .
Cross-version data: Some of the administrative data is cross-version, other is version-dependent. The cross-version data includes
the description, authorization group, old and internal product ID, administrative data on the creation of the product.
Note
11/8/2019
Authorization group:
To create the authorization group for a product, specify an authorization group in the cross-version data. Only employees with
authorization for this authorization group can maintain the products.
Version concept
You can hold versions in parallel, if, for example, you are planning a new version for a later point in time. Note that in this case you
can create active versions and also create accounts for these versions, but that their opening date must be in the future.
During any one validity period always only one version can be active, meaning that active versions may not overlap each other in
their validity area.
Versions can also have accounts when they are not valid but only active. However, you cannot create accounts for invalid versions.
Example:
In your currently valid version 1 the default setting for currency is DEM. From July 1 you wish to de ne the default currency Euro for
a version 2.
All accounts created in the validity area of version 1 have DEM as default currency and those created for version 2 have Euro.
Already as of 01/01 you can 'park' accounts for version 2, even though the opening date may not be before 07/01.
Account
Use
The account is the central object of the current account system.
You can use accounts within the current account system for the normal purposes of a current account (demand deposit account).
The components of a current account are supported, such as balance-based balancing and processing payment transactions. The
system also supports term deposits ( xed deposits, overnight money, deposit at notice), savings bonds (normal interest) and
savings deposits with an agreed or a three-month period of notice.
You create accounts as characteristic of a product . A product is a group of services based on the requirements of individual bank
customers. You de ne the product using elds, features and payment transaction operations. General processing characteristics
11/8/2019
are controlled by products, whereby these processing characteristics are transferred to the assigned accounts.
SAP provides you with the Product Con gurator to enable you to con gure products. The Product Con gurator facilitates the
de nition of the business and technical features of a product, its version creation and the layout of the functions on the interface.
You can use the Product Con gurator to add to the features of the products. (See also: Product De nition ).
Structure
The structure of products and accounts in connection with the tool Product Con gurator is as follows:
The Product Con gurator is used for creating different products such as a junior bank account, a commercial bank account, xed
deposits of 30 days, and variable xed deposits of between 60 and 90 days. These products serve as a template and basis for
accounts that you create for them. An account is always related to one version of the product, although the products can exist in
several versions. You can make use of these versions when, for example, you have changed a product but the accounts relating to
the old version of the product have not been closed.
The product controls
The functions that can be used on the account
The posting operations that can be used
The media used for initiating postings
The attributes that exist for an account and the way in which the elds are displayed in the application.
Every product is de ned according to a Bank Area . However, in the Implementation Guide (IMG) you can restrict the products for
certain bank areas.
Integration
Similar characteristics apply for the de nition of accounts as for the de nition of business partners. The technical tool used for
the creation of the account master data is the SAP Business Data Toolset . This has the same advantages as listed for the central
business partner. Account creation is exible, which means that you can create as many bank elds as you require by using the
product, and without the need for modi cations.
You can de ne the layout of the screens to suit your bank requirements. Online transactions and interfaces for data transfer are
provided to enable you to process account master data. The search function is supported by search and matchcode elds.
Scope of Functions
You can choose the de nition and description of the products as required. As mentioned above, attributes are assigned to each
product or account, which control the executable functions, the standard conditions and the screen layout or the view of an
account. You can provide the account with individual conditions, limits and the appropriate business partners.
You achieve the depiction of single or joint accounts by assigning an account holder to an account. It is also possible to
display different relationships between accounts and business partners. One business partner assigned to an account, for
example, can be the account holder, another business partner the authorized drawer, and another business partner the
bank statement recipient.
You can de ne the allowed business transactions for every account type (for example, it is not permitted to overdraw an
account kept on a non-borrowing basis).
It is possible to manage accounts “for the bene t of a third party”.
11/8/2019
You de ne nostro and vostro accounts accordingly, and maintain and use them in a similar way as customer current
accounts. The only differences are the different attributes.
An account can be managed in any currency. Provision is made for the conversion accounts to Euro and also the alternative
display in Euro and the EMU joining currency. A customer can have the account managed in Euro from the date she or he
requires.
You can create relationships between different accounts as a tree structure (account hierarchy). Operational usage
includes cash concentration (the clearing of lower-level accounts in favor of a higher-level account) and interest and charge
compensation.
You always create accounts for a certain bank area. This means it is possible for accounts with the same account number
to exist in different bank areas.
You can assign conditions to the account as standard conditions or individual conditions.
Special functions for deposit banking are as follows:
Rollover and notice (partial and full amount) and their management.
Monitoring of the term start, overpayment, or underpayment on each account.
Control over the processing of incoming and outgoing payment items (post, in postprocessing, reject) during one of the
saving phases (preliminary phase, xing phase, maturity phase).
Interest calculation with account-based interest rates (term, amount and currency based), the preliminary interest
calculation and posting interest calculation results.
Creation of Accounts
Use
The account is the central element of the current account system. The system provides convenient entry options for creating the
account master records. Different information is required or already defaulted according to the product to which you have
assigned the account to be created.
Prerequisites
The business partner or partners related to the account can be created before you create the account.
Process
You create an account as follows:
1. You choose a product for the creation of the account. This controls the main characteristics, such as the screen sequence
for the creation of the account, the data to be entered, any standard conditions assigned, and the basic functions that can
be used on the account.
2. You maintain the account master data, for example, the account number.
3. You assign an account holder and, where necessary, other business partners in various roles to the account. You must
enter the account holder for all account types (for organizations you also need to specify an authorized drawer). Other
assignments such as the bank statement recipient or authorized drawer can be useful for some products. The following are
possible scenarios:
The business partner is already created in the correct role. In this case you can assign the business partner directly.
11/8/2019
The business partner is already created, but in a different role. In this case you need to allocate the correct role to
the business partner in partner management before you can make the account assignment. This ensures that all
information relevant for the role is maintained in the business partner master record.
The business partner is not yet created. You need to create the business partner in business partner management
in the appropriate roles. Alternatively you can create the business partner in a role when you create the account.
The above steps are required for all cases. The following steps may also be useful in some situations and with some products:
1. The condition groups for interest calculation, charges and value dates set for the product are already assigned to the
account. You have the following options:
If the account corresponds to the standard product, leave these as they are.
To adjust the product for the customer, you can assign other conditions from the pool of standard conditions
already created for other products to the customer, or you create an individual condition especially for this
customer.
2. You can restrict the functions assigned to the account through the product assignment by specifying lock reasons. For
more information, see Account Locks.
3. You de ne the conditions for amount notice and rollover for deposit products.
4. You can assign different limits to the account (for example, overdraft limit, internal and external account limit) that control
the extent to which an account can be overdrawn. If you do not assign limits to an account, the system sets the
corresponding limit at 0. In this case, the account cannot be overdrawn.
5. You also need to specify if checks are to be issued for the account.
6. You specify when the account is to be balanced.
7. You manage the standing orders here and also the time that bank statements are to be created.
8. You can specify a bank key on the Administration Data tab page.
Note
The external account number is unique for the bank area and bank key. If two bank areas have the same bank key, the
external account number must be unique for the common bank key. However, another bank key in a second bank area
can have the same external account number.
Example
If bank areas 0001 and 0002 are assigned the bank key 90000001, external account number 15 can be assigned to
either bank area 0001 or 0002. If bank area 0001 now has account 15 with bank key 90000001, then the system
does not allow account 15 to be created with bank key 90000001 in bank area 0002. However, the system allows the
account number 15 to be created in bank area 0002 if you use another bank key, for example 90000002.
Note
You can assign the bank key only during the creation of an account and only if it is assigned to the bank area (see
Customizing for Bank Customer Accounts (IS-B-BCA), under Basic Settings Bank Area Assign Additional Bank Keys
to Bank Area ).
If you do not enter an external account number when you create an account, the system generates the IBAN when you
save your entries. After the account is saved, you cannot change the bank key. If you enter an external account number
when you create an account, the system generates the IBAN by using the default bank key for the product. If there is no
default bank key for the product, the system generates the IBAN with the default bank key for the bank area. However,
you can change the bank key; when you save your entries, the system checks the bank key, and regenerates the IBAN.
11/8/2019
Administration of the direct debit orders is also part of account management.
Result
Once you have completed the steps above and saved your data, the account is created in the system.
Creating an Account
1. Choose Account Create.
2. Specify the bank area to which the account is to be assigned.
If you want the program to assign the account number internally , leave the Account Number eld blank. The system then
assigns a number from the set number range, determined in accordance with the set check digit procedure.
The system initially ʻ ags’ the assigned account number and then displays it when you save the account.
If you assign the account number ( external number assignment ) manually when you save the account, or if you select the
Check button, the system also checks the number in accordance with the set check digit procedure. You can deactivate
this check by selecting a checkbox.
3. If necessary, change the opening date.
4. Specify the product to which the account relates.
5. If required, set the checkboxes to Offer and Deactivate Check Digit .
6. Enter a bank control key.
In Customizing, you can specify if and how the bank control key is to be entered when the accounts are created, according
to the country and the product. Choose Master Data Account De ne Country Settings for Bank Control Key. When you
create standing orders, payment orders, forward orders, and reference accounts, you can specify it to identify an external
account.
The system displays the next screen with the different tab pages that are available. These tab pages contain elds grouped
by business topic. Depending on the product, you can display either all or only some of the followng tab pages:
Basic Data
Term Agreement for Fixed Deposits
Balancing
Limits
Holds
Payment Transactions
Amount Notice
Bank Statements
Correspondence Receiver Administration
Standing Orders
Control Data
11/8/2019
Administration Data
Maintaining Basic Data

Use
As basic data you maintain the base data of the account, for example, assigned business partners or the account currency.
Procedure
1. In the Identi cation section, enter the currency in which the account is to be managed, the account description, and the
search terms. The account description can be, for example, the name of the account holder. You can also freely choose the
search terms. They later serve as search help for accounts.
2. In the Administration section, specify the status of the account. The current status is displayed. Prerequisite for this is that
you have stored the possible statuses in Customizing for Bank Customer Accounts (BCA) by choosing Master
Data Account De ne Status.
Note
You activate the account by using the Status eld.
You can also specify that the customer must be informed when the account master data is modi ed by setting the Print
Change Correspondence indicator. The system calls the Business Transaction Event (BTE) 00011060 when you save the
changes. You must implement the BTE to use this function.
3. In the Account Closure section, enter the planned date of closure, closure reason, reference account for closure, and the
account closure correspondence that is to be generated.
4. In the Notes section, you can record comments and events for this account. You can create the notes in different languages
and have the notes that are already created displayed, either in a short overview or long overview.
5. In the Account Holder section, de ne the account holder.
Assigning affiliated business partners to the account:
Note that at this point you can only assign business partners who have been created in the role of account holder. Selecting the F4
help brings you to a search screen that helps you search for existing business partners.
Creating business partners during account assignment:
If the business partner you wish to use as account holder does not exist, you can create the business partner by choosing with
the quick info text Create Business Partner . On the following screen, enter the appropriate data, and save your entries.
1. In the Other Business Partners section, create business partners in the role of authorized drawer and account
maintenance officer. In this section you can, of course, de ne other business partners in different roles (for example,
contact person). You can use existing business partners or create new business partners.
Note
Enter the proof of identity for the business partners on the Identi cation tab page of the business partner maintenance
screen .
Result
11/8/2019
You have maintained the basic data for the account.
Maintaining Balancing Data

Use
On the balancing data screen you specify the condition groups and the dates for account balancing and cash concentration.
Procedure
1. The condition groups that were assigned to the product are stored under Condition Groups. To display the details of this
condition group, choose Details. See also: Assigning a Condition Group to an Account
For more information about conditions, see Condition.
2. In the section Account Balancing, de ne the time periods for account balancing. Specify whether the account is relevant
for capital yield tax (CYT). Specify whether the balancing is to be carried out on a reference account. To create a reference
account choose Create. See also: Creation of a Reference Account for Balancing.
If an internal or external reference account is stored, the bank area and account number or bank country, bank key and
account number are also displayed.
Note
The reference account may not already refer to another account.
3. In the Cash Concentration section, specify the circumstances under which the actual account balancing with interest and
charge calculation is to take place.
Example:
Period Period unit Day of the week Key date Meaning
1 days every day
1 week 1 every week on Monday
3 months 15 every 3 months
1 months 31 on the last day of every

month
You can also enter on which date the next balancing is to be performed.
Result
You have maintained the period data for account balancing and cash concentration.
Maintaining Limits
Use
On this screen you maintain the limits. Limits serve basically to restrict the amount-based disposal of accounts.
11/8/2019
SAP supports six categories of limits, three account limits and three interest compensation limits. You can also de ne other limit
categories by means of Customizing. (See Limits ).
Procedure
To learn how to maintain the limits of an account, read Assigning Limits to an Account .
Maintaining Holds
Use
Holds enable you to adapt the available amount for an account by increasing or decreasing it.
You decrease the available amount if certain amounts are to be held as securities or as part of another business transaction on the
customer account. This prevents money from being withdrawn from the remaining available amount on the account.
You increase the available amount if you want to provide the customer with an extra limit for a particular period of time.
Prerequisites
You have activated the Holds feature for the product under Conditions and Limits.
You can de ne an amount-based authorization check in Customizing for the product in bank area currency under Authorization
Management -> Amount-Dependent Authorization -> Maintain Amount Limit for Hold.
Procedure
The holds are displayed on the Holds tab page in the Holds group box. You can create, change, and delete holds. The changes
made are saved only when you save the account.
The following parameters de ne a hold:
Reservation category
01 for long term holds that reduce the available amount by the reserved amount (hold).
02 for suspending the long term hold that reduces the available amount by the negative reserved amount.
Reserved amount (hold)
Amount in account currency by which the available amount is to be reduced. You need to enter the amount with a negative
plus minus sign to suspend the long term hold.
Valid from and to
Period of time during which the hold is valid, whereby more than one hold can be valid at one time.
In addition, you can specify a reference number for internal use.
Choose Account Balance to display an overview of the outstanding holds.
Result
11/8/2019
The active holds affect the payment transaction and balancing. If you process a payment item, the active holds are summarized
and subtracted from the available amount. If the payment item exceeds the available amount, the system issues an error
message.
During balancing, the system checks whether there are any open active holds,issues an error message if there are, and places
account balancing in postprocessing.
Choose Information System -> List of Holds to generate a list of holds for selected accounts. The list also displays the deleted
holds with their deletion date.
Payment Transactions Administration

Use
This function enables you to do the the following for an account:
De ne allowed payment transaction features and activities
De ne extended payment transaction functions
Display mandates with the Locked status
Display global lock details for mandates
De ne allowed check (payment form (PF)) types
Prerequisites
If you want to lock any functions, you have de ned locking reasons in Customizing for Bank Customer Accounts (BCA) by
choosing Master Data Account De ne Account Locking Reasons.
Features
Locked Functions
You specify the features and activities that must be locked for the account in the Locked Functions screen area.
You can assign any number of locking reasons to each account. You can use a function for an account if both the following
criteria are met:
The function is allowed for the product associated with the account
The function is not locked by any locking reason
The system displays both the locked and available functions in the Functionalities screen area. The following
applies:
If you do lock the function by using a locking reason, the traffic light is red
If you allow the function in the product, the traffic light is green
If you do not allow the function in the product and do not lock the function, there is no traffic light
To obtain an overview of the functions allowed for the account, choose the detail view for the account. See also:
Account Locks .
Mandate Lock
11/8/2019
You can display locked mandates for a particular creditor ID, or combination of creditor ID and debtor IBAN. Or you can display the
globally locked mandates for the combination of Creditor ID and Debtor IBAN.
Extended Payment Transaction Functions
In the Extended functions screen area, you specify the following:
Whether the payee is allowed to collect receivables by means of a collection authority agreement
Whether value date speci cation is allowed for payment transactions created from the dialog
Check (PF) Types (Only for banks)
You can de ne special attributes for every check (PF) type. These attributes control the issue of checks (PF) and check
(PF) numbers for the account.
Activities
De ne the locked functions and extended functions, display mandate locks, and check (PF) details as required.
When checks (PF) are presented for payment, the system makes the following checks based on the check (PF)-related
settings:
The system checks if the check (PF) number already exists in check (PF) management.
If the check (PF) number exists, the system updates the check (PF) status to Redeemed/Settled .
If the check (PF) number does not exist, and check (PF) number allocation on presentation is allowed, the system
transfers the check (PF) to check (PF) management with the status Redeemed/Settled .
If the check does not exist, and check (PF) number allocation on presentation is not allowed, the system does not
allow you to post the payment transaction.
Bank Statement and Balance Noti cation

Administration
Use
This function enables you to specify when, to whom, how often, and the manner in which bank statements are to be dispatched.
You can also specify the frequency of balance noti cations. The system uses these details as control parameters for the
generation of the bank statements and balance noti cations.
Prerequisites
You have activated the Bank Statement and Balance Noti cation features for the product on which the account is based.
Features
Bank Statement Recipients
You can specify the bank statement recipient details, dispatch method and the document type (original or copy). You also de ne
the time periods for bank statements.
11/8/2019
If you activate both methods of recipient determination (bank statement and correspondence receiver administration) in the
product, you cannot edit business partner and other correspondence related information on the Account Statements tab page.
Balance Noti cation
You can specify the time periods for balance noti cations.You can also specify whether interest information is to be included in the
balance noti cation. The balance noti cation data is transferred by Business Transaction Event (BTE) 00012900 ( ).
For performance reasons, we recommend that you only include interest information if it isabsolutely necessary
Display of Historical Data
You can view details of the bank statements and balance noti cations that were created to date.
Number of Bank Statements
You can create up to 999999 bank statements for the account in a year.
Activities
Enter the time periods and the next date when the bank statement and balance noti cation must be generated.
Period Period unit Day of the week Key date Description
1 Days Every day
1 Week 1 Every week on Monday
3 Months 15 On the fteenth of every

third month
1 Months 31 On the last day of every

month
Enter details of the bank statement recipient.
If you have activated the Correspondence Receiver Administration feature for the product, you must specify the bank statement
details on the Correspondence Recipients tab page . However, bank statements do not use the correspondence tool.
To obtain paper bank statements, choose IHCPAP as the bank statement format, and the dispatch type 01 (applies to SAP In-
House Cash only).
Maintaining Control Data

Use
11/8/2019
You specify the data for the processing control on the Control Data tab page.
In the General Ledger Transfer group box, you specify information on the cumulation of the data during the transfer of the
account ows to the general ledger.
Prerequisites
The system offers the general ledger groups for selection that are de ned in Customizing under Periodic Tasks General Ledger
Transfer Maintain General Ledger Group.
The Business Area attribute has been set up accordingly for the product on which the account is based.
Procedure
Group BoxControl
1. You specify whether the account to be created is a single, AND, or OR account.
2. If required, set the Third Party Bene t indicator. You can set the indicator only in combination with the indicators for
individual or joint accounts.
Group BoxGeneral Ledger Transfer
1. Assign the account to one general ledger group.
Note
When the general ledger is updated, the cumulated postings of all accounts with the same general ledger group are
transferred to the general ledger in separate debit and credit totals to ensure that the balance sheet display is correct.
The cumulated debit or credit totals of the period of time to be transferred is calculated in such a way that one balance
is initially calculated for each account (including the balance carryforward from the previous transfer). This balance
then determines (according to its plus/minus sign) whether the total of account ows from the transfer period is to be
added to the debit or credit total of each general ledger group.
If you change the assigned general ledger group, you need to note the following:
The general ledger group can be changed only if the balance sheet preparation for the account has been completed,
and there are no items in postprocessing or in release.
During the next balance sheet preparation, the balances of the receivables and payables accounts from the old
general ledger group are transfer posted to the receivables and payables accounts in the new general ledger group.
2. Assign the account to a netting groupif there is to be netting for at least one additional account with the same business
partner. Otherwise, leave this eld blank for performance reasons. The name of a netting group is of no more than four
characters.
Note
The general ledger update must add to a single receivable or payable all the ows not yet transferred from the accounts,
and that have the same account holder, and that formally have the same interest conditions. This complies with the
legal requirements of the balance sheet statement (for example, § 10 of the German bank accounting law). The
corresponding accounts of an account holder must all have the same netting group, and be balanced before the
cumulation of the general ledger groups to make this possible. This operation is called balance netting.
3. Assign the account to a business areaif the product allows this.
If you change the assigned business area, you need to note the following:
11/8/2019
You can change the business area only if the balance sheet preparation for the account has been completed, and
there are no items in postprocessing or in release.
During the next balance sheet preparation, the balances of the general ledger accounts are taken off the books with
the old business area and put back on again with the new business area. They are then posted on the general ledger
during the general ledger transfer.
Group BoxLegacy Data Transfer
If there is a legacy data transfer for the account to be created, specify the Go-Live Date and the Balance Transfer Date. SAP
provides a report for the legacy data transfer. The system does not post balancing data from the period between the Balance
Transfer Date and the Go-Live Date. These elds are relevant if you want to balance accounts before the go-live date.
Maintaining Administration Data

Use
On this screen you maintain the administration data.
Procedure
1. In the Administrative Data group box, specify the bank key under which bank data from the respective country is stored.
You can also assign a default value for the bank key in the Product Con gurator, which can be changed during account
creation. This enables your bank to identify transactions as being internal if the recipient account related to an incoming
transaction is assigned to a different bank key
2. Enter the authorization group. To be able to edit accounts, the user must have authorization for the authorization group
entered here.
3. Specify the public holiday calendar. The public holiday calendar key indicates the public holiday calendar on which value
dating is based. If required, enter another public holiday calendar, for example, if you often execute postings with a certain
country.
4. Specify a resubmission reason and the resubmission date. The possible resubmission reasons are de ned in Customizing
for Bank Customer Accounts (IS-B-BCA) under Master Data Account Maintain Resubmission Reasons . Under
Infosystem Accounts for Resubmission , you can select the accounts pending resubmission.
Result
The administration data has been maintained.
Account Display
Use
This function enables you to display the account master data centrally.
Features
Account Balance Display
11/8/2019
You can display the current account balance by choosing Account Balance . To avoid the display of unwanted information to
customers, the system displays the external view rst. The external view shows account balance details after considering the
external limit de ned for the account. You can choose Internal <-> External to switch to the internal view.
Payment Item Display
You can display a list of all payment items posted on the account by choosing Display Turnovers and specifying a posting period.
You can, additionally, display payment item details by choosing the payment item number or item position.
The system does not display parked items, archived items, and those in postprocessing.
For payment items that you have already viewed, the traffic light is yellow.
Correspondence History
You can display a list of all correspondence requests created for the account by choosing Corresp. History (Correspondence
History).
Bank statement details are not displayed in the correspondence history.
Parameters for Printing
You can set the print parameters, such as the printer and output format, by choosing Print Parameters
The system uses this setting if you print the account creation or change correspondence immediately.
Interest Penalty Display
You can display the interest penalty that is to be posted during the next account balancing run by choosing Display Interest
Penalty and specifying a posting period. The system displays a list of payment items. Double-click a list entry to view the item
details.
The system only displays this button if you have selected the Amount Notices feature for the product on which the account is
based, and if interest penalty is due for posting during the next balancing run.
Activities
To display the account, go to the SAP Easy Access screen and choose Account → Display , then enter the bank area and account
number.
The system displays the account master data on several tab pages.
You can display the data for another account by choosing Account → Other Account
Changing an Account
11/8/2019
Procedure
To change the master data of an existing account, proceed as follows:
1. In the application menu choose Account Change.
2. Specify the account number of the account and the corresponding bank area.
3. Choose Continue , change your data, and save your entries.
To assign another product to an account, proceed as follows:
1. In the application menu choose Account Change.
2. Specify the account number of the account and the corresponding bank area and then, on the initial screen, choose
Edit Assign product .
3. Specify the new product.
Note the following when you change the assignment of a new product to the account:
You must appropriately maintain any additional elds, particularly the required elds that have possibly been added by
the change to the new product.
When you change the product, some account elds may get hidden. However, the system does not delete such eld values
from the database.
If changing the product also leads to a change in the conditions, you must take this into account accordingly. Before
changing the product, we recommend you balance the account to avoid any inconsistencies.
You can only change the condition area (that could be different for the new product) if you have so far made no
postings to the account and have not executed a balancing.
Creation of a Reference Account for

Balancing
Purpose
When you balance accounts, you can either post the result on the account itself or on another account (the reference account).
You can de ne the root account of an interest compensation hierarchy as a balancing reference account. A reference account
cannot, in turn, refer to another account.
To prevent a debit account balance for accounts with the Amount Notices feature, you can also post the result of the balancing
run on a special CpD (suspense) account. You specify the special suspense account in Customizing for Bank Customer Accounts
(BCA) by choosing Account Management Maintain CpD-Accounts for Special Purposes.
It is also possible to balance an account that has an external reference account (that is managed by an external bank). In this case,
the system creates a payment order. The interest and charges are posted on the account referring to the reference account
(referencing account) as usual (one payment item position per condition category). The offsetting item is posted as one total.
Prerequisites
If you have created an entry in Customizing for the account bank area for which you are creating the reference account for the
account balancing, you can select the account identi cation for an external reference account. You make this entry in Customizing
11/8/2019
for BCA by choosing Account Management Basic Functions in Account Management Set up Recipient Account Identi cation .
Process Flow
Creating a reference account
1. Choose Account Change.
The system displays the initial screen for the display of an account.
2. Enter the bank area, account number, and, if required, the business partner data.
The account maintenance screen appears.
4. Choose the Account Balancing tab page.
5. In the Account Balancing group box, choose a reference account type (whether internal or external).
6. Choose with the quick info text Create Reference Account .
7. Enter the required data and choose Continue .
Note
If a reference account already exists, you need to delete it rst by choosing with the quick info text Delete Reference
Account .
Displaying a reference account
The Balancing group box has the following buttons that that enable you to specify the type of reference account:
No Reference Account
This indicator shows that the balancing result is not posted to a reference account.
Internal Reference Account (Direct)
This indicator shows that the balancing result is posted directly to a reference account. In this case, the account
referring to another account (referencing account) and the reference account are both in the same bank area. The
interest and charges are posted directly to the reference account. No posting is made to the referencing account itself,
but the interest and charges are displayed in the referencing account overview for the balanced periods. The general
ledger is updated in accordance with the general ledger account assignment of the referencing account.
Internal Reference Account (Indirect)
This indicator shows that the balancing result is posted to the referencing account and then transferred to the
reference account. In this case, a payment order is created automatically, and can be a bank transfer or a debit.
External Reference Account
This indicator shows that the balancing result is posted to the referencing account and then transferred to the
reference account. In this case, a payment order is created automatically, and can be a bank transfer or a debit. An
external reference account is a reference account that is in a different bank area from the account referring to it.
When you specify an internal or an external reference account, the bank area and account number (for internal accounts), or
the bank country, bank key, and account number (for external accounts) are also displayed.
11/8/2019
Result
The reference account iscreated. You can now use the reference account for account balancing.
Error Processing:
Internal reference account (direct) If an error occurs on the referencing account, nothing is balanced.
You must correct the error and then restart the account balancing
run.
If the error occurs with the reference account, the balancing item
(interest and charges) is placed in postprocessing. The referencing
account is still completely balanced.
Internal reference account (indirect) If an error occurs on the referencing account, nothing is balanced.
You must correct the error and then restart the account balancing
run.
If the error occurs on the recipient side of the payment order (for
example, the transaction type is locked), the ordering party side is
posted and the recipient side is placed in postprocessing.
If the error occurs on the ordering party side, the system does not
balance the account interval that contains the incorrect account. If
the error cannot be corrected immediately, it is advisable to lock the
referencing account before the restart, to allow the rest of the
account interval to be balanced.
External reference account See the description for the internal reference account (indirect)
Creation of a Reference Account for Account

Closure
Purpose
When you close an account, you can specify another account to which the remaining balance is to be transferred when the
account is closed. This reference account can be an external or an internal account.
For accounts with an external reference account for account closure, you can also de ne a special CpD (suspense) account for
collecting the debit balance on account closure in Customizing for Bank Customer Accounts (BCA). De ne the special suspense
account by choosing Account Management Maintain CpD-Accounts for Special Processes.
Prerequisites
If you have created an entry in Customizing for the account bank area for which you are creating the reference account for account
closure, you can select the account identi cation for an external reference account. You make this entry in Customizing for BCA by
choosing Account Management Basic Functions in Account Management Set up Recipient Account Identi cations.
Process Flow
The system displays the initial screen for the display of an account.
2. Enter the bank area, account number, and, if required, the business partner data.
11/8/2019
The account maintenance screen appears.
4. In the Basic Data tab page, enter the date of the closure.
5. Specify if the reference account is managed internally or externally (at another bank).
6. Choose with the quick info text Create Reference Account .
7. Specify the account details of the reference account on which the balancing result of the account closure is to be posted.
Result
You have successfully created the reference account that is used in account closure.
Account Locks
Use
The scope of functions of an account is always determined by the product to which the account is assigned. You use account locks
to exclude other features, media and transaction types from this basic scope of functions.
To lock an account completely or for certain transaction types, features and media, there are two options that you use in
combination:
Setting the account status:
You can set an account either as Active or as Inactive . If you set an account at Inactive , no postings can be made to the
account.
You set the status using the status eld on the Basic Data screen.
Assignment of de ned account locks
To only permit certain business transactions, functions and access media for an account, you can individually lock certain
functions. You do this by assigning locks to the account. These locks must be de ned in Customizing.
Example
Example for banks
The features standing order, account balancing and bank statement, the media EFT and T-Online, and the transaction
types credit, debit, cash deposit and cash withdrawal/payment are assigned to the product checking account online.
You assign the New Opening lock to a new account, and this excludes the transaction types cash payment and debit
and also the medium T-Online. After this, all functions of the product can be used on the account, but only the
transaction types credit and cash deposit. Access is only possible using the medium EFT. All other accounts assigned to
the product remain unaffected.
Example
Example for In-House Cash Centers
A subsidiary company leaves the group. No more payments can be processed.
11/8/2019
You do not have to specify just one lock, but can de ne several locks at the same time. These can also involve locks for
functionalities that are not contained in the product.
Features can be subdivided as follows :
Medium
Identi es the medium with which a payment order was initiated.
Examples of this include
EFT (electronic funds transfer)
T-Online, Internet
Document
EDIFACT
Internal (internally initiated payment order)
Feature
This concerns features prede ned by SAP, for example, balancing, standing order, bank statement, bank closure, cash
concentration.
Transaction type
The customer de nes transaction types of payment transactions. In the previous or legacy payment transaction system,
text keys and text key enhancements are displayed by a neutral transaction (in Germany by DAT). You must maintain these
transactions in the payment transaction system and in the SAP system. In the SAP system, attributes that specify the
payment transactions are assigned to the transactions. The attributes are prede ned by SAP.
To restrict functions for one individual account, you use locking reasons . Like the function group, a locking reason can include
entries of media, transaction types and features, and locks the speci ed functions in the scope of functions of an account.
Other notes
If you select One Lock on the function section, the system displays what effect this lock has.
If you select All Locks , the system displays what effect all locks have.
Assigning Locks to an Account

Prerequisites
Before you can assign locks to an account, you need to de ne locking reasons in Customizing (in the Implementation Guide (IMG)
by choosing Master Data Account De ne Locking Reasons ).
Procedure
1. When you maintain the account, choose the Payment Transactions screen.
2. In the Locked Functions section, choose a line and specify a locking reason using the F4 help.
You can control the functions locked for the account by choosing the detail view of the account in the Functions section.
11/8/2019
The Functions section displays the locked and available functions. All existing features and payment transaction
operations are always displayed. The following applies:
Red traffic-light = locked by a locking reason
Green traffic-light = assigned by the product
No traffic-light = not assigned and not locked.
The Functions section shows all the functions still available for the account. This list includes the prede ned functions for the
product, and those that you have locked using locking reasons. The display is based on the criteria above.
Removing Locks from an Account

Procedure
1. When you maintain the account, choose the Payment Transactions screen.
2. In the Locked Functions section select a line.
3. Choose the Delete icon.
You can control the individual functions that are locked for the account by choosing the detailed view of the account in the
Functions section.
The system displays the locked and the available functions in the Functions section. All existing features and payment
transaction operations are always displayed. The following applies:
Red traffic-light = locked by a locking reason
Green traffic-light = assigned by the product
No traffic-light = not assigned and not locked.
Result
The locks are deleted and the functions are all available again.
Creating Account Hierarchies

Use
Relationships can exist between accounts in the form of a hierarchy, which you can show in a tree structure.
You can create any types of hierarchies. In the standard system, the hierarchy types for cash concentration and interest
compensation are used, but you can also create other hierarchy types, for example, for information purposes.
A hierarchy consists of a root account, for which n subordinate accounts can exist. You can also assign n subordinate accounts to
each of these subordinate accounts. The number of hierarchy levels depends on the hierarchy type.
Relationships within the hierarchy are always valid for a certain time period. You specify this when you create the hierarchy. To
ensure clarity, an account may exist only in one hierarchy at any given time, and within one hierarchy type.
11/8/2019
Within the hierarchy it is possible for accounts to belong to different bank areas, provided these are internally managed accounts.
You can only use external accounts as a root account. You can manage the accounts in different currencies, provided the currency
is one participating in the EURO changeover. You can impose restrictions for every hierarchy type, for example, to prevent your
employees from using any cross-bank area accounts.
For more information, see also:
Cash Concentration
Interest Compensation
Creating an Account Hierarchy for Interest

Compensation
Use
You use this function to create a hierarchy of the account pool for interest compensation. You de ne the root account of the
hierarchy rst, and can later assign subordinate accounts to it.
11/8/2019
Procedure
Choose Account → Account Hierarchy → Create .
Specify the bank area and account number of the root account for the account hierarchy.
A root account cannot refer to another account in an interest compensation hierarchy.
Enter the validity period.
Note on the validity period
Valid From Date
If you have created the root account speci cally for this purpose, the Valid From date of the hierarchy must be the same as the
opening date. In this respect, a new account is one that has not been balanced before, but postings are permitted.
If the root account has already existed for some time, the Valid From date must be one date after the date of any of the future
balancing runs. Also, the root account may not be balanced on the same date as the Valid From date. This means that the date of
the last balancing must be before the Valid From date.
11/8/2019
If you enter any other date, the system issues an error message.
You cannot change the balancing data for an account once it is used in a hierarchy, (even if the hierarchy becomes valid only after
a few months). The balancing data includes the balancing date, key date, and time periods. This restriction is due to technical
reasons, since the checks that the system makes regarding the suitability of the data only take place during the creation of a
hierarchy. If you wish to change the balancing data, remove the account from the hierarchy, change it, and then insert the account
back into the hierarchy.
Valid To Date
If you do not enter a date, the system automatically enters12/31/9999in this eld. This means that the hierarchy has an unlimited
validity.
If you wish to enter the date, ensure that the Valid To date corresponds to one of the future balancing dates of the root account.
If you enter any other date, the system issues an error message.
Enter the Interest Compensation Method as the H ierarchyT ype , and choose Continue .
The system displays the hierarchy tree, which initially comprises only the root account.
Assign (subordinate) accounts to this hierarchy tree by choosing Hierarchy → Account → Create, or with the quick info text
Create .
The system displays an overview where you can specify the accounts on the next hierarchy level. Specify the bank area and
account number of the subordinate account for each line.
Subordinate accounts for interest compensation:
Note the following prerequisites for interest compensation subordinate accounts:
If the account was created after the Valid From date of the hierarchy, the balancing date of this account must be the same as the
next balancing date of the hierarchy.
If the account was created before the Valid From date of the hierarchy, ensure that the balancing date +1 at some time
corresponds to the Valid From date of the hierarchy.
The next balancing date of the subordinate account isDecember 31, 2000, and the Valid From date isFebruary 1, 2001. The
subordinate account is balanced onJanuary 31, 2001. If you add a day, this results in the following date: February 1, 2001.This date
corresponds to the Valid From date, making it valid.
Once you have entered all the accounts of this hierarchy level, choose Transfer If you wish to assign other accounts to the
hierarchy, position the cursor on the relevant account and repeat the steps from point 6. You can do this until the rst account
balancing for this hierarchy.
Save the hierarchy structure.
Result
You have successfully created an account hierarchy for interest compensation.
11/8/2019
Creating an Account Hierarchy for Cash

Concentration
Use
You create the account hierarchy that you need for the cash concentration. Cash concentration is the generation of payment
orders to credit or debit accounts in an account hierarchy that a user has created.
Procedure
1. Choose Account -> Account Hierarchy -> Create .
2. Specify the bank area and account number of the root account for the account hierarchy.
You cannot use accounts that have the Term Agreement Control feature as a root account.
3. Choose Cash Concentration as the hierarchy type and specify the time period in which the hierarchy is to be valid.
To specify an external root account, choose the Root Account Int/Ext button, then enter the bank country and the bank
key.
4. Specify the type of carryforward.
5. The system displays the hierarchy tree, which initially comprises only the root account. Assign (subordinate) accounts to
the hierarchy tree by choosing Hierarchy -> Account -> Create, or the Create symbol.
6. The system displays an overview where you can specify the accounts on the next hierarchy level. Specify the bank area
and account number of the subordinate account for each line.
You cannot use accounts that have the Term Agreement Control and/or Amount Notice feature as the subordinate
account.
Subordinate accounts for cash concentration:
In addition to the bank area and account number, specify the required minimum and maximum balance and the minimum transfer
amount or base amount, and choose Copy (Enter) . The system checks that your entry exists and if it is unique.
For carryforward types that are divided into debit and credit:
Minimum balance: The minimum balance that an account must have after cash concentration and to which it is lled if this
amount is not reached.
Maximum balance: Any amounts above this are cleared to higher-level accounts. If you do not specify a value here, the
account is fully cleared, providing there is no speci ed minimum.
The text for the payment notes is transferred during the carryforward to the higher-level account.
Minimum transfer amount: The amount from which an account amount is carried forward.
If you only specify a minimum balance, the system sets the maximum balance to the same level as the minimum balance. If you do
not enter a value for the minimum balance, the system sets this to zero (if you do not want to specify a minimum value for an
account, you can set the minimum value to a high negative amount).
1. Once you have entered all the accounts of this hierarchy level, choose Transfer/Copy . To assign other accounts to an
account, place your cursor on the relevant account and repeat steps 4 and 5.
11/8/2019
2. Save the hierarchy structure.
Result
The account hierarchy of the hierarchy type cash concentration has been successfully created.
Creation of an Account Hierarchy with a

Template
When you create a new account hierarchy, you can make use of the structure of a hierarchy that already exists. This is particularly
useful when you want to create the same account hierarchy with a different validity period.
When you create an account with a template, a new hierarchy tree is formed. This consists of the new root account speci ed by
you and all the subordinate accounts of the template hierarchy.
The de nitions you make for the new root account (validity period) apply to all relationships in the new hierarchy.
It is only possible to create a hierarchy using a template within one hierarchy type.
If both the current and the template hierarchy belong to cash concentration, all the cash concentration amounts (minimum
balance, maximum balance, minimum transfer amount) are also copied to all the copied accounts.
When you create the hierarchy tree, the system informs you how many accounts have been transferred.
Creating an Account Hierarchy with a

Template
Use
If you wish to create an existing account hierarchy for cash concentration with a different validity period, you can copy this to
another root account.
Prerequisites
The account hierarchy you are using as a template has the same hierarchy type, but a different validity period.
Procedure
1. In the main menu choose Account Account Hierarchy Create.
2. Specify the bank area and account number of the root account for the account hierarchy. Choose a hierarchy type and
specify the time period in which the hierarchy is to be valid.
3. Specify the root account and all other data from the template hierarchy. Using the F4 help provides you with a selection of
all hierarchies already created.
Result
11/8/2019
When you create the hierarchy tree, the system informs you how many accounts and cash concentration amounts have been
transferred, and displays the new hierarchy tree.
Displaying an Account Hierarchy

1. In the main menu choose Account Account hierarchy Display.
2. Specify the bank area and the root account of the required hierarchy. Choose a hierarchy type and specify the time period
in which the hierarchy in question exists. If there is only one hierarchy with the same root account, you need not enter the
time period.
3. Using the F4 help in the account number eld you can view all the root accounts already used.
4. If the chosen hierarchy is a hierarchy for cash concentration, go to one of the hierarchy nodes and choose ʻdisplay’ to see
the cash concentration amounts.
Example
Double clicking on a node provides you with more information on the account behind a node. The system then branches to the
account display.
Changing an Interest Compensation

Account Hierarchy
Prerequisite
To change a current (used) interest compensation hierarchy, you must rst neutralize this, then copy it and make the changes to
the copy.
If a hierarchy is being used, the following actions cannot be performed directly in the hierarchy. Used in this connection means
that an interest compensation run has already been executed.
You cannot add an account to the hierarchy that was created before the hierarchy, or to which you have already made
postings.
You cannot remove an account from the hierarchy
You cannot change the interest compensation method of the hierarchy
You cannot change the “valid from” date of the hierarchy
You cannot change the balancing date, key date and time periods of an account in the hierarchy
Caution
Do not frequently change the interest compensation account hierarchy. Frequent changes have a negative effect on the
performance of account balancing: Every change to the interest compensation account hierarchy has to be taken into
consideration during account balancing.
Procedure
1. In the main menu choose Account Account hierarchy Change.
11/8/2019
2. Specify the bank area and the account number of the root account and choose Enter .
3. Choose either the icon Change interval or the menu option Hierarchy Change interval .
4. Change the “valid to” date to the last balancing date of the hierarchy and save your entries.
The current interest compensation hierarchy has been neutralized.
5. In the main menu choose Account Account hierarchy Create.
6. In the upper section “Account Hierarchy”, specify the bank area and the account number of the root account of the
hierarchy just neutralized.
7. In the upper section “Account Hierarchy”, as "valid from" date enter the last balancing date +1.
8. In the lower section “Template”, also specify the bank area and the account number of the root account of the hierarchy
just neutralized.
Result
The new hierarchy corresponds exactly to the neutralized hierarchy, the only difference being that the copied hierarchy has not yet
been used and can, therefore, be changed. Now you can add new accounts to or remove accounts from the hierarchy.
Changing a Cash Concentration Account

Hierarchy
1. In the main menu choose Account Account hierarchy Change.
2. Choose the required account hierarchy.
The hierarchy tree is displayed. Now you have the following options:
To newly create a node , position your cursor on the next higher (next superior) hierarchy level and choose Hierarchy
Account Create , or the corresponding icon. The input screen for accounts appears and you can create new nodes on the
next lower hierarchy level.
To change the cash concentration amounts , go to one of the nodes and choose Change .
To shift a node within the structure, rst select the node ( Edit Select node ). Then go to the node to which the target
node is to be attached and choose Hierarchy Account Reassign, or the respective icon. Now you can choose if you
want to insert the target node on the same hierarchy level or on the next lower lever. If you wish to shift an entire sub-tree,
select it by choosing Edit Select subtree and proceed as above. During reassignment, the system checks the currencies
of the accounts. You can only reassign accounts managed in the currencies participating in the Euro changeover or in Euro
itself.
To change a node , go to the node and choose Hierarchy Account Rename . Then overwrite the account number of the
node with the new account number. This change has no effect whatsoever on the master data of the account. All that
happens is that the hierarchy is adjusted.
To change the type of carry forward , choose Hierarchy Type of carry forward. The input screen for the carry forward
appears and you can now change the type of the carry forward.
It is possible to display all the changes made with the change history pushbutton.
11/8/2019
Account Closure
Purpose
You can use this process to close an account. Closing an account revokes the business connection for the account between the
customer and your bank. This process involves a series of tasks such as clearing the remaining account balance, account
balancing, and nally setting the account status enhancement to Closed .
You can either close a single account by using the Single Account Closure report or several accounts by using the Mass Account
Closure report. For more information about these reports, see the system documentation.
Prerequisites
You have enabled the Account closure feature for the product on which the account is based.
In Customizing for Bank Customer Accounts (BCA), you have de ned the following:
The behavior for some account objects by choosing Master Data → Account → Account Closure → De ne Behavior of
Dependent Objects
The balancing date for account closure by choosing Master Data → Account → Account Closure → De ne Balancing Date for
Account Closure
The message type (whether error, warning, or information) by choosing Tools → Change Message Control.
Process Flow
Account Closure Master Data Maintenance
You de ne the account closure reason and reference account for closure on the account master record. If you want to use a mass
run, you must also de ne the planned closure date.
To collect the debit balance on account closure for accounts that use an external reference account for closure, you can de ne a
special suspense account. De ne this suspense account in Customizing for Bank Customer Accounts (BCA) by choosing
Account Management → Maintain CpD-Accounts for Special Purposes.
Release Procedure
When you enter or changethe master data for account closure:
If you have not set up the release principle, the system changes the account status enhancement directly to Closure - Planned .
If you have set up the release principle, depending on criteria de ned for the release procedure, the system ags the account for
release by changing the account status enhancement to Closure – In Release Process .
Subsequently, another user with the appropriate authorization releases the account closure process, which then changes the
account status enhancement to Closure - Planned .
11/8/2019
If the user rejects the closure process, the system changes the account status enhancement to Active and clears the planned
closure date, closure reason, and closure reference account.
You can de ne a release work ow to manage the account closure process in Customizing for Bank Customer Accounts (BCA) by
choosing Master Data → Account → Account Closure → Release . For more information, see Release Object ACCNT_CLOS .
Function Execution
You execute the single closure or mass closure functions.
Account Closure Checks
The system performs several checks before actually closing the account. These include, for example, checks for the existence of
standing orders and direct debit orders.
For more information, see Account Closure Checks .
Account Balancing
The system balances the account based on the balancing date de ned for account closure in Customizing for BCA. If you de ned a
charge condition for account closure, the system also computes the closure charge and posts it to the account.
If the account is part of an interest compensation hierarchy, the system balances all accounts in the hierarchy and adds the
accrued interest on the account to the account balance. For more information, see Interest Compensation .
The system also uses the balancing date to determine the transfer posting date and any accrued settlement postings.
Payment Order Creation
To transfer the nal account balance to the reference account, the system creates a payment order with the following details:
Posting date as the current transaction posting date
Value date as the planned closure date, or the balancing date based on the balancing date de ned for account closure in the
Customizing activity De ne Balancing Date for Account Closure .
If the account has the Amount Notices feature enabled, the system:
Determines if interest penalty is applicable
Computes the interest penalty
For more information, see Interest Penalty Calculation .
Posts the interest penalty immediately even if you de ne the IP Posting type as Debit at Balancing .
You can use the Business Add-In (BAdI) Payment Notes Creation Based on Transaction Types to transfer the payment notes
speci ed for reference accounts to the payment order.
Bank Statement Generation
The system prepares the bank statement data and supplies it to the bank statement interface.
Business Partner Validity Update
11/8/2019
The system updates the date up to which a business partner is valid with the account closure date for the following business
partner roles:
Account Holder
Authorized Drawer
Correspondence Recipient
The system updates the date up to which a business partner is valid:
Only if the business partner is not used on any other account in the particular role
For the roles that are actually associated to the account
Correspondence
If you have made the required correspondence settings, the system generates account closure correspondence that noti es
customers about the account closure.
For more information, see Correspondence .
Result
When the account closure process is successfully completed, the system performs the following activities:
Sets the account status to Inactive with the status enhancement as Closed.
If the account closure process fails at any stage, the system sets the account status enhancement to Closure – Postprocessing
and the account status to Active.
Updates the actual account closure date
Writes change documents to record all the changes, including those made to the limits. The system uses the change document as
the basis for limit reactivation.
You cannot edit a closed account.
Reactivating an Account
Use
You can use this function to reactivate an account that has already been closed(this function is used by banks).
11/8/2019
When an account is closed, the system performs several checks before actually closing the account. These include, for example,
the check to see if standing orders still exist or if the account is used in account hierarchies. Additionally, the account is balanced
and the balance brought to zero. See also: Closing Accounts
You can reset account closure if required. Once an account has been successfully reactivated, it shows the status "New" and a
balance of zero.
If standing orders exist for this account, (at closure they were given the status "deleted"), the system issues a warning and also a
note in the long text suggesting you check the deleted standing orders and create them again if necessary.
You can de ne whether limits are to be reactivated if they were changed by the account closure. The system nds these by means
of the change documents of the account closure.
If an account was involved in an account hierarchy, the system issues an appropriate message when you reactivate it. This serves
as an aid if an account was closed by mistake and you wish to include it in this hierarchy again.
Prerequisites
You have closed an account and want to reactivate it for a particular reason (for example, a customer request).
Procedure
2. Enter the data for the account you want to reactivate.
3. Choose Edit Reactivate account.
The system displays the Reactivate Account dialog box.
4. Select the check box Reactivate Limits Changed by Closure to reactivate limits.
Result
The account has been successfully reactivated and is now available for further processing. If you select the selection eld, the
limits changed during the account closure regain the status they had when the account was closed.
Euro Changeover
Purpose
This section describes how you can depict the currency changeover to the European uniform currency with the help of the current
account system.
This system supports you during the dual currency phase with the changeover of the account currency and with the processing of
payment orders in different currencies. The changeover of the account currency to Euro can only be performed for accounts in one
of the participating currencies.
De nition of terms:
In the following explanations the following terms apply:
11/8/2019
Account currency:
The currency in which an account is managed. Postings are always made in account currency.
Reporting account currency:
During the dual currency phase, for every account managed in one of the participating currencies, there is, in addition to
the actual account currency, a reporting account currency purely for information purposes. All turnovers are shown both in
the account currency and in the reporting account currency.
Participating currency:
A currency taking part in the changeover process to Euro.
Transaction currency:
The transaction currency is the currency in which cash ows from one account to another.
Integration
The “Euro changeover” part of the current account system serves to:
Change over the currency of accounts from a participating currency to Euro.
Process payment transactions during the dual currency phase in Euro and in participating currencies.
Display the turnovers, items and balances during the dual currency phase.
The system supports currency changeover for the following:
Standing orders
Forward orders
Planned items
Direct debit orders
Prenotes
Holds
All accounts including amount notices and xed term deposits
Scope of functions
During the dual currency phase, the following dependencies between the account currency and the reporting account currency
apply:
Original currency of the account Account currency Reporting account currency
Non-participating currency, e.g. US $ US dollars Not supported
Participating currency, e.g. German Marks DM Euro
Participating currency, e.g. German Marks Euro DM
11/8/2019
Original currency of the account Account currency Reporting account currency
New opening in Euro Euro The bank area currency applies
If the bank area is a participating currency,

this applies.
If the bank area currency is Euro, the bank

area currency before the changeover
applies.
Changeover of the Account Currency

Purpose
This process describes how you can changeover accounts in the current account system to the European single currency Euro.
Note
Since clearing accounts and CpD (suspense) accounts are currency-dependent and are not changed over, you must create
these before changeover per bank area and per currency as new accounts in the Euro currency.
Process ow
1. Adjust the limits.
2. You must newly create individual limits from the changeover date in Euro.
3. Newly create both overdraft limits as well as internal and external account limits. SAP also offers a report for these limits
that converts the amount in accordance with the exchange rate to Euro for the period after changeover and enters a new
limit in EUR.
4. Reference limits are currency-dependent. This means that for an account that refers to a reference limit, the limit always
applies in account currency.
Example: There is an internal reference limit for students of 1,000 DEM. A reference limit of 500 EUR has already been
created with the same reference limit ID. An account with this reference limit has an internal limit of 1,000 DEM before
changeover and 500 EUR after changeover.
5. Create conditions in Euro. You can assign conditions in Euro to the condition groups at any time. Until one day before the
changeover key date, the conditions in the old account currency apply for the individual accounts and as of the changeover
key date these conditions are replaced by the Euro conditions. You have to maintain individual conditions manually.
6. Make the required setting on each respective account that is intended for currency changeover.
7. Activate the executable program that periodically changes over all accounts agged for changeover.
Result
During the changeover, items and balances in a participating currency are rst taken off the books and then put back on the books
again in Euro. After the changeover of the account, all items from balancing are posted in Euro - including those for periods ending
before the changeover key date (value dates in the past).
The account is now managed in Euro.
11/8/2019
Example
Changing over an account from DM to Euro
Posting date Value date Amount Account currency
05/15 05/01 + 500 DM
05/15 05/04 -200 DM
05/30 06/02 + 50 DM
Euro Changeover on June 1.
06/01 06/01 -300 DM
06/01 06/02 -50 DM
06/01 06/01 +150 Euro
06/01 06/02 +25 Euro
Changing Over an Account

Prerequisites
In Customizing , de ne for each bank area which currencies you plan to change over to Euro and set the indicator for release
according to the principle of dual control. This indicator prevents an erroneous currency changeover. Releasing in accordance with
the principle of dual control is optional, but SAP recommends you adopt this procedure.
Caution
It is not possible to undo an erroneous currency changeover of accounts.
If you convert the account but not any related prenotes, the prenotes do not affect the available balance . This would also
mean an incorrect result in the limit check.
Procedure
1. Go in change mode into the account you wish to change over.
2. Specify the account number of the account and the corresponding bank area.
3. Choose the section ʻcurrency changeover’.
4. Enter the request/order date and the changeover date.
Once you have maintained the changeover dates, the account has the changeover status (not the account status) ʻcreated’.
Until released, the dates can be changed.
Note
Alternatively, you can execute a mass changeover by choosing Periodic tasks Currency changeover Prepare currency
changeover. You can make the selection of the affected accounts using bank area, account number, account holder,
product and currency before changeover.
11/8/2019
Release
1. Release the changeover data by choosing Account Release Release Currency Change.
2. Enter the required data and choose Execute .
Executing the release is subject to the authorization check. After execution, the accounts for processing appear in list form.
In the rst column of the list, a traffic-light shows the editing status of the accounts:
Red= release must be effected by another user
Yellow = release has been executed
Green = release is to be executed
3. Position your cursor on the relevant line.
4. Press the button ʻRelease’.
Once released, the changeover data can no longer be changed. The status of the currency changeover stands at ʻFlagged
for changeover (released)’.
5. On the speci ed changeover date, a program is automatically started that checks which changeover dates are before the
next posting date and then changes over these accounts.
Deletion of the release
If you have erroneously released the changeover data and wish to undo this action, you must delete the release.
In the currency changeover section, a delete indicator also appears after release. Select the delete indicator eld in the currency
changeover section and then release the deletion, so that the release is removed from the account master data.
If the changeover data is agged for deletion in the account master, (delete indicator is set), there is an error message in the log of
the execute program (report) that checks the changeover data on the changeover date. The system does not perform currency
changeover for these accounts.
Changeover without principle of dual control
Prerequisite for this is that you have not set the principle of dual control indicator in the Implementation Guide (IMG).
1. Go in change mode into the account you wish to change over.
2. Specify the account number and the corresponding bank area.
3. Choose the section ʻcurrency changeover’.
4. Enter the request/order date and the changeover date.
Once you have maintained the changeover dates, the account has the changeover status ʻ agged for changeover’ (released). You
can still change the dates until the execute program changes over the account.
Result
The selected account has been changed over from one of the participating currencies to Euro.
Note
By agging an account for Euro changeover, a block indicator is automatically set on the account. As long as the account is not
changed over to Euro, all postings with a posting date after or on the changeover date are held back. These items are noted in a
11/8/2019
separate table and updated later. No updating of the general ledger takes place. Prerequisite for the oating of items is that the
amount can be determined in account currency after the currency changeover. If this is not the case, the item is rejected
showing the indicator ʻimport error’.
Changing Over an Account after Account

Balancing
Use
It is possible to set for the bank area that the date for currency changeover of an account is linked to account balancing. This
means that the currency changeover must always take place one day after an account balancing run.
The public holiday calendars are taken into consideration for the calculation of the changeover date.
There are two options in the algorithm for the calculation of the changeover date.
It is assumed that an account balancing is executed on a working day. This means that if, in the list of future account balancing
dates, one of the dates falls on a public holiday, the system increases this until it falls on a working day.
It is assumed that the currency changeover also only takes place on a working day. This means that once the system has added
one day to the potential account balancing date, it then checks if the potential currency changeover dates fall on a public holiday.
If this is the case, the system once again adds a day until the respective date falls on a working day.
This is illustrated in three examples:
Example 1:
Official account balancing Monday
Assumed account balancing Monday
Account balancing + 1 day Tuesday
Calculated currency changeover day Tuesday
Example 2:
Official account balancing Friday
Assumed account balancing Friday
Account balancing + 1 day Saturday
Calculated currency changeover day Monday
Example 3:
Official account balancing Saturday
Assumed account balancing Monday
Account balancing + 1 day Tuesday
Calculated currency changeover day Tuesday
11/8/2019
Prerequisite
You have entered the public holiday calendar in the Implementation Guide (IMG).
Procedure
The changeover takes place automatically. If the date of the changeover is changed, a warning message appears.
Result
The changeover is related to account balancing.
Payment Transactions in the Dual Currency

Phase
Use
Postings to an account are always only in the currency in which it is managed. This means that before changeover, postings to the
account are in the participating currency. After the changeover, postings to the account are in Euro. This applies independently of
the posting date and value date. To ensure smooth-running payment transactions during the dual currency phase, the amounts of
the individual payment items exist both in an account currency and also in a reporting account currency.
It generally applies that a payment order must always be speci ed in the account currency (a currency participating in Euro
changeover and Euro) of the ordering party.
The following currency elds are provided for payment items:
Account currency
Transaction currency
Reporting account currency
Example
A payment item with the transaction currency of 200 DM is received for an account managed in the account currency
Euro. The system converts this payment item and credits the amount in Euro.
Internally initiated payment transactions:
Before the dual currency phase, the transaction currency corresponded to the account currency. During the dual currency phase,
the transaction currency can correspond to the account currency or the reporting account currency.
Externally initiated payment transactions:
In the case of externally initiated payment transactions, the system assumes either the transaction currency or the reporting
transaction currency.
Scope of functions
Direct debit orders (only applies for banks)
11/8/2019
Direct debit orders can be entered both in account currency and also in reporting account currency. If there is a direct debit order
in reporting account currency, the conversion from account currency to reporting account currency is done in the system.
Direct debit orders can be changed over independently of the account changeover.
Changing over standing orders (only applies for banks)
Standing orders can be entered both in account currency and also in reporting account currency. If there is a standing order in
reporting account currency, the conversion from account currency to reporting account currency is done in the system.
You can change over the standing orders independently of the account changeover.
Account balancing:
After the changeover of the account, all items from balancing are posted in Euro - including those for periods ending before the
changeover key date (value dates in the past).
Postings to prior periods:
For postings to prior periods containing payment items with a posting date before the changeover, Euro applies as account
currency.
Example
Postings to prior periods
Item Post. date Value date Amount
(10) 03/29 04/30 75 EUR
Transaction gures: Post. date Value date Currency Amount
(0) 03/30 03/28 DEM 800
(0) 03/29 04/02 DEM 200
(1) 04/01 04/01 DEM -200
(1) 04/01 04/02 DEM -800
(3) 04/01 04/01 EUR 400
(3) 04/01 04/02 EUR 100
(4) 04/03 03/30 EUR 500
(10) 03/29 03/30 EUR 75
Value date balance Post. date Currency Amount

carry forward
(0) 03/31 DEM 800
(4) 03/31 EUR 500
Post. date balance Value date Currency Amount

carry forward
(1) 03/31 DEM 800
(10) 03/31 EUR 75
11/8/2019
Account balance:
(4) EUR 1000
(10) EUR 1075
Returns:
It is assumed that a payment item with transaction currency Italian Lire (ITL) and account currency German Marks (DM) is posted
to and account in DM. Then the account is changed over to the Euro currency (EUR). Following this, the payment item is to be
returned.
Since the account currency after changeover is EUR, interest and charges for the return can only be calculated in EUR. Returns are
always made in the original currency. Since in this case, the original transaction currency was ITL, the interest and charges are
also converted to Lire. For this reason, the system creates and executes a return order with the original transaction currency ITL
and the account currency EUR.
Display Options for Turnovers and Amounts

Use
To enable the display of the prepared currency changeover data stored on databases, the display options have been enhanced by a
few elds.
Amounts Display Formats
Turnovers Account currency
Payment orders Reporting account currency
Transaction currency
Limits Account currency
Subject to nal payment balance Reporting account currency
Subject to nal payment-free account balance
Conditions
Account balances
Available amount
Scope of functions
Limits:
The limits are displayed depending on their validity in account currency.
Account balance:
The account balance and also the limit relating to this account, the subject to nal payment balance, the subject to nal payment-
free balance and the available amount are displayed in account currency. With the help of a pushbutton you can switch the display
to the reporting account currency. If the account is in the changeover phase, the account balance is automatically displayed in the
reporting account currency.
Turnovers:
11/8/2019
The turnovers are displayed in accordance with the pre-setting in account currency. It is possible to switch to display in the
reporting account currency using a pushbutton. Note that before the account changeover, the amount of the turnovers in
reporting account currency is 0. The list overview provides you with a view of the turnovers in account currency, reporting account
currency and transaction currency.
Bank statement:
The following columns are provided for bank statements:
Account currency
Old account balance
New account balance
Reporting account currency
If the transaction currency is not the same as the account currency, this is explicitly displayed as for foreign currency.
A check module is called up within the conversion report before the currency changeover. This checks if current items for the
account exist with a posting date before or on the changeover date that were not yet on a bank statement. If the check result is
positive (meaning items do exist), a statement is created. The items are shown in the current account currency (for example,
DEM) and in the reporting account currency (for example, Euro). If the account currency is not the same as the transaction
currency, there is an additional display in transaction currency. The balance is only displayed in account currency.
If no items are selected, no action is taken.
Within the conversion report a bank statement is created in all cases after the currency changeover. This contains noti cation that
the account has been changed over. The old balance is shown in the old account currency (DEM) and the new balance in the new
account currency (EUR).
Example
<Address>
Changeover date: 01/01/99
Date of request/order: 12/01/98
Old balance: 500 DEM
Your account has been changed over from DEM to EUR.
New balance: 250 EUR
The subsequent bank statements are the same as those before the changeover, except that the account currency (now EUR) and
the reporting account currency (now DEM) have been swapped. The balance is again only shown in the account currency (now
EUR).
Interest scale:
If the Euro changeover key date falls in a period for which an interest scale is created, the turnovers, balances and interest are
shown before the changeover key date, for example, in DM and after the changeover key date in Euro.
Example
11/8/2019
Turnover Balance Interest
03/31 1,000.- DM 1,000.- DM 10.- DEM
04/04 200.- DM 1,200.- DM 12.- DEM
04/08 Changeover 600.- EUR 6.- EUR
04/12 300.- EUR 900.- EUR 9.- EUR
This means it will not be possible to display the whole period only in DM or only in Euro.
Activities
To have the amounts displayed in the respective currencies, go to the overview function as required, for example, to the document
overview of the turnovers. To look at the turnovers in the currency you want, press the pushbutton to have the display in account
currency or reporting account currency and for payment transactions also the transaction currency.
Note
For overview lists relating to account balances, the amounts are rst displayed in the account currency. To enable a display for
the whole bank area, it is possible to make a conversion from account currency to bank area currency.
Overview of Currencies Posted for Balancing

Use
The combination of the data listed below determines the currency display of the periods to be settled and the currency in which
posting actually takes place.
In most cases, the currency display of the balancing and the currency in which is posted are identical.
One exception is the combination of "next balancing date is before the changeover date" and "changeover date is before the
posting date of the next balancing". In this case the currency displayed (DEM) is not the posting currency (EUR) if the account has
already been changed over to Euro. The system automatically executes a balancing (in DEM) and converts to Euro. The difference
in the currencies has no effect on the posting.
If you wish to avoid the situation of having different currencies in the display and for posting, ensure that the posting date of the
balancing is before the changeover date.
The following statements of the balancing currency and actual posting currencies result, depending on the dates:
Combination of the dates Displayed balancing Actual posting Note
Next balancing date for account DEM DEM Before the changeover can take
place, balancing must be carried
before the
out
posting date of balancing,
before the
changeover date
Posting date of balancing, DEM DEM Before the changeover can take
place, balancing must be carried
before the
11/8/2019
next balancing date for account out
before the
changeover date
Next balancing date for account DEM EUR Account is Euro-blocked,

meaning it must be changed
before the
over before balancing can take
changeover date place.
before or on the
Posting date of balancing, EUR EUR Account is Euro-blocked,

before the
changeover date place.
before or on the
next balancing date for account
Changeover date EUR EUR Account is Euro-blocked,

before or on the
next balancing date for account place.
before the
Changeover date EUR EUR Account is Euro-blocked,

before or on the
posting date of balancing, place.
before or on the
next balancing date for account

Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 1

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 1

Загружено:

Авторское право:

Доступные форматы

11/8/2019

SAP In-House Cash (FIN-FSCM-IHC)

SAP ERP | 6.0 EHP8 SP13

Original content: https://help.sap.com/viewer/da5ab0fa48b34143a25d0e08448f5219/6.18.13/en-US

For more information, please visit the https://help.sap.com/viewer/disclaimer.

SAP In-House Cash (FIN-FSCM-IHC)

Central incoming payments

They are also mutual clearing partners.

International Group Structure

Time at which posting cut-oﬀ is to be automatically executed every day

Exchange rate category that stores conversion rates in the system

Special Feature: Bank Area and Bank Key

One Bank Key Can Involve Several Bank Areas

Assignment of Company Code

Financial Accounting System Assignment

Bank Area Company Code Financial Accounting System

Current Account Master Data

Business Partner in the Current Account

Account maintenance oﬃcer

Bank statement recipient

BKK010 Account Holder

BKK020 Authorized Withdrawer

BKK030 Bank Statement Recipient

BKK200 Account Maintenance Oﬃcer

Delete and Archive the Business Partner

Total Commitment for a Business Partner

Restriction of Payment Order Recipient

Group Condition categories

Interest Debit interest

Debit interest is used for calculating the interest on debit balances.

Credit interest is used for calculating the interest on credit balances.

Overdraft interest is used for calculating the interest on amounts

The transaction interest is used for certain business transactions

The bonus calculation is enabled by business transaction event

Charges Transaction charge

Transaction charges are levied for certain transactions and depend

Item charges are levied for each item posted to an account.

Account maintenance charge

Account maintenance charges are levied each time the account is

Value dating Value date

Value date conditions determine the point in time of the value

Value date subject to nal payment

Subject to nal payment conditions determine the inclusion of an

Principle of dual control

Condition category Diﬀerentiation type Diﬀerentiation value Amount

Transaction charge Transaction type Debit 0.30

Transaction charge Transaction type Credit 0.10

Transaction charge Transaction type Cash deposit 0.00

The use of up to two diﬀerentiation types enables more complex combinations.

1. Diff. type 1. Diff. value 2. Diff. type 2. Diff. value Amount

Credit rating Good Card Debit card 10.00

Credit rating Good Card Credit card 15.00

Credit rating Good Card Customer card 0.00

Credit rating Poor Card Debit card 20.00

Credit rating Poor Card Credit card 30.00

Credit rating Poor Card Customer card 10.00

For more information, see: Releasing Conditions .

Interest conditions Charge conditions Value date conditions

Debit interest Transaction charges Value date

Credit interest Item charges Subject to nal payment value date

Overdraft interest Account maintenance charges

Transaction interest Direct charges:

Commitment interest Dispatch charges

(Y2 - Y1)360 + (M2 - M1)30 + (D2 - D1)