Bank Statements 

Definition

This is a business object in Account Management (FS-AM) that represents a legally binding information medium used by the bank for customers. This medium displays information on the turnovers and the balance of an account. In addition, account settlement information is displayed on the bank statement. For more information, see Statement of Settlement Information on Bank Statements.

Bank statements can be provided to customers via different channels (for example, from the bank statement printer or by mail).

The balance confirmation is a feature of the account in Account Management. For more information about editing account contract features, see the Editing Features section of the SAP Library. The bank statement also has a feature attribute in the product upon which an account is based. For more information about product attributes and their characteristics, see: Product.

Use

You can create one or more bank statements, You can either trigger the bank statement output immediately, or create correspondence requests for bank statements and then output them later.

An account must be live before you can generate bank statements for it.

The different options for generating a bank statement in Account Management are described in more detail below:

Immediate Generation

If the statement is generated immediately, then the scheduling time is the same as the generation time of the correspondence request.

Bank Statement via Bank Statement Printer/Internet

This is a bank statement that is called up via a business application programming interface (BAPI). For more information, see Business Application Programming Interface (BAPI) and the documentation for the BAPI BankStatement.Execute in the BAPI explorer.

Bank Statement in Single Run

This is a bank statement created by a member of staff at a bank, using application online entry. For more information, see Creating Bank Statements.

Generation as Part of Periodic Tasks in the Mass Run

Regular Bank Statement

This is a bank statement that you schedule in the mass run on a periodic basis. For more information, see Scheduling Bank Statements for the Mass Run.

Event-Controlled Bank Statement

This is a bank statement that is generated as a result of a business event in banking, for example:

-         Non-execution of a payment or standing order.

-         Credit memo from bank transfer returns

-         Debit memo return

-         Check return

-         Non-call-up of bank statements from the binding agreement at the bank statement printer within a particular period of time after an account flow

To generate an event-controlled bank statement, you need to enter settings in the Customizing for Account Management first. For more information, see Integration and Editing and Displaying Creation Dates.

If a business event has occurred, whose information does not require any special attachments other than the bank statement, the bank customer can also call up this information with the next bank statement or outside of the mass run environment by using the statement printer.

If a business event has occurred, whose information does require special attachments other than the bank statement, the bank customer cannot call up this information with the next bank statement or outside of the mass run environment by using the statement printer.

Once a correspondence request has been created for a bank statement, you can view the data on the created bank statement in a bank statement history and then go directly to the archived bank statement document. For more information about the bank statement history, see Displaying Bank Statement Histories. In addition, you can also display an application log for bank statements generated in the mass run from SAP Easy Access screen, by choosing Account Management ® Logs ® Bank Statement.

Structure

Bank statement data is grouped as follows (this data is partly master data and partly flow data):

Master and Flow Data

Master data is general data required for generating and transferring a bank statement. It includes the name of the bank statement recipient and the dispatch address, and whether the recipient is to receive the original statement or a duplicate.

Flow data is follow-on data, which is needed to ensure the bank statement continues seamlessly from the data on the previous bank statement. This data includes the balance on the last bank statement and information regarding the length of time for which items have been appearing on former bank statements.

·        General data (master data)

·        Bank statement agreements (master and flow data)

·        Time periods of agreements (master data)

·        Events (flow data)

·        Correspondence recipient management (Correspondence Recipient tab page) (master data)

General Data

In the General Data area you can set up general conditions for structuring and generating bank statements. To change this data, enter the values you require:

·         Maximum number of turnovers that are allowed to be displayed for each bank statement at the bank statement printer.

·         Maximum number of days that are allowed to elapse after a turnover before a bank statement must be generated for the binding agreement, if this is an agreement for a bank statement printer.

Bank statement agreement

For each account that has the bank statement as a feature, there is an automatic binding bank statement agreement, to which you can add further agreements.

You can supply control parameters and a recipient group separately for each agreement. These define how, when and to whom the bank statements created for this agreement are to be sent. Each agreement is documentation of an independent turnover.

Binding Agreement

The binding agreement differs from other agreements in that it sends customers the original bank statement that is legally valid. Events that the system schedules are defined in the binding agreement. The bank statements for this agreement contain information on events that have occurred as well as the item information. This agreement cannot be deleted or deactivated, thereby ensuring that customers always receive all their correspondence via this agreement.

You cannot transfer the Binding indicator from one agreement to another. The binding agreement exists for the same length of time as the account.

For more information about the data to be entered for a bank statement agreement, see Editing Bank Statement Data.

Time Periods

In the Time Periods area you can set up the calculation method for the next date for each agreement. You must set the Periodicindicator in the bank statement agreement area to be able to do this. When you have selected the bank statement agreement you want to process, the system displays the fields for the detail entries required to determine the period calculation.

·        Time periods every X days, weeks, months, years

·        Starting date

·        Working day shift.

If you change these details, the next due date is recalculated for the mass run.

Events

You can use the Displaying and Editing Generation Dates transaction to see which events the customer still needs to be informed about, and when the next bank statement is (at the latest) due to be generated for each bank statement agreement for an account. You can delete these entries, with the exception of event 9999, which ensures that the bank fulfils its obligation to notify customers.

You can schedule new generation dates for bank statements by either using the online transaction Displaying and Editing Generation Dates or by the method BankStatement.AddEvent. For more information about the method, see the corresponding documentation in the BAPI Explorer.

Correspondence Recipient Management (Correspondence Recipient Tab Page)

To differentiate in more detail to whom, by which method and in which form a bank statement is dispatched, make the relevant additional settings on the Correspondence Recipient tab page in correspondence recipient management. For more information about Correspondence Recipient Management, see Correspondence Recipient Management.

Methods

In Account Management (FS-AM), you can use one of the following channels for processing objects:

·        Dialog

·        Business Application Programming Interface (BAPI)

·        Direct Input (DI)

The following overview shows which methods (and the channel) you can call up for the bank statement:

Method	Channel
	Dialog	BAPI	DI
Creating Bank Statements	x	x
Displaying and Editing Generation Dates	x	x
Displaying the Bank Statement History	x	x
Start Mass Run	x
Change Flow Data for Bank Statement		x
Edit Master Data for Bank Statement	x	x	x
Read Master Data for Bank Statement	x	x

Dialog

You can call up the following transactions in dialog mode:

Transaction Code	Short Description
F9N7	Generating Bank Statements
F9N35	Editing and Displaying Generation Dates
F9N33	Displaying Bank Statement Histories
F9N1	Mass Run for Bank Statement Generation

Business Application Programming Interface (BAPI)

You can call up the following methods using the BAPI Explorer:

Method	Short Description
BankStatement.AddEvent	Add Generation Dates for Bank Statement
BankStatement.Execute	Creating Bank Statements
BankStatement.GetHistory	Provide History Data for Bank Statement
BankStatement.RemoveEvent	Delete Generation Dates for Bank Statement
BankStatement.ChangeDue	Change Flow Data for Bank Statement
CMAccountAM.BankStatementChange	Edit Master Data for Bank Statement
CMAccountAM.BankStatementGetDetail	Read Master Data for Bank Statement

Direct Input

Direct input is not implemented for the contract element Bank Statement. For more information, see Account

For additional technical information on the contract element Bank Statement, see the Technical Documentation button on the initial screen of the account.

Integration

Customizing

The bank statement has the following Customizing settings in Account Management under Item Management ® Bank Statement:

·        Set Up Control Parameters for Bank Statement

·        Triggering Events for Event-Controlled Bank Statements  ®

¡        Define Events

¡        Set up Event-Control Parameters

In addition, the following settings are relevant for the bank statement:

·        Payment items: Choose Item Management ® Basic Functions ® Transaction Types and Transaction Type Groups ® Maintain and Assign Transaction Types for Payment Items

·        Returns: Choose Item Management ® Basic Functions ® Returns ® Define Returnable Transaction Types

·        Payment Orders: Order Management ® Payment Order ® Select Trigger for Event-Controlled Bank Statement

·        Standing Orders: Order Management ® Standing Order  ® Select Trigger for Event-Controlled Bank Statement.

For more information, see the documentation in the IMG activities.

Thematic Link with Other Areas in Account Management

·         Release Object CN (Account)

If you use the release tool you can, for example, forward the account to the release process if there are changes made to the bank statement data. For more information, see Release Object CN (Contract).

·         Correspondence in Account Management

If you use the correspondence tool, you can, for example, determine the format, dispatch route and recipients of a bank statement. For more information about the authorization checks in Account Management (FS-AM), see Correspondence in Account Management.