ASAP Implementation Methodology

CONFIGURATION REFERENCE TEMPLATE

MANUAL CHECK DEPOSIT

Copyright © 2010 SAP AG. All rights reserved 1 of 20

ASAP Implementation Methodology

TABLE OF CONTENT

1. SCOPE ............................................................................................................................................... 3
2. DOCUMENT REVISION HISTORY ..................................................................................................... 4
3. BUSINESS REQUIREMENTS ............................................................................................................ 4
4. CONFIGURATION RATIONALE......................................................................................................... 4
5. TECHNICAL REQUIREMENTS .......................................................................................................... 4
5.1 Business Rules or Data Requirements .......................................... Error! Bookmark not defined.
5.2 Programming or Configuration Logic ............................................. Error! Bookmark not defined.
6. CONFIGURATION .............................................................................................................................. 5
6.1 Client 410 SAP Easy Access Menu .............................................................................................. 5
6.2 Define Origin Groups..................................................................... Error! Bookmark not defined.
6.3 Define Cost Element for WIP Calculation ...................................... Error! Bookmark not defined.
6.4 Define Line IDs.............................................................................. Error! Bookmark not defined.
6.5 Define Assignment ........................................................................ Error! Bookmark not defined.
6.6 Define Update ............................................................................... Error! Bookmark not defined.
6.7 Define Posting Rules for Settling Work In Process ........................ Error! Bookmark not defined.
7. TESTING........................................................................................................................................... 12
7.1 Testing Consideration / Assumptions ............................................ Error! Bookmark not defined.
7.2 Test Scenarios Identified ............................................................... Error! Bookmark not defined.
7.3 Unit / Integration Testing ............................................................................................................ 15
8. USER ACCEPTANCE TESTING ............................................. ERROR! BOOKMARK NOT DEFINED.

Copyright © 2010 SAP AG. All rights reserved 2 of 20

ASAP Implementation Methodology

1. Scope

1.1 Introduction
Bank reconciliation is a process whereby you are matching your accounting records with the bank record. At a particular point in
time, your accounting record may or may not match the bank record. This is due to the time difference between recording
transactions in the company’s books of account and the bank’s transaction postings. At the end of the month or at a particular time
interval agreed to with the bank, the bank sends a bank statement to the company.
The company compares the bank statement with the transactions recorded in its books of account. This process may bring up the
true balance with the bank, a transaction the company failed to record, or a transaction recorded by the bank that does not pertain to
the company. Because of these differences the bank account as per the books of accounts may not exactly match with the bank
statement.

When the company passes these entries, the main bank account balance will agree with the bank balance as per bank.

Important acronyms
BRS is Bank REconciliation Statement.
MBS Manual Bank Reconciliation Statement
EBRS is Electronic Bank Statement
BRS and MBS are one and same, these terms are used synonymously. In this document we are going to cover BRS/MBS but not
EBS.
In case if bank provides the bank statement manually or physical copy, we use manual bank reconciliation. Here we need to do the
reconciliation for each transaction by transaction manually.
In case if bank provides the bank statement in electronic form, we use Electronic bank statement. In this case we can directly
uploaded the statement in SAP and reconciliation happens automatically based on the configuration and predefined parameters.

Prerequisites: Before configuring Bank reconciliation statement/Manual Bank Statement, we need GL Accounts, House Bank and
Check lots

Reference: http://scn.sap.com/docs/DOC-43446

Copyright © 2010 SAP AG. All rights reserved 3 of 20

ASAP Implementation Methodology

2. Document Revision History

Date Version Revision Description Issue # Process Author

(Projects Only) Flow
Verified
07/17/2013 1.0 Initial Document Joy Ann Gunay

3. Business Requirements
To be able to handle several customer payments faster

4. Configuration Rationale

5. Technical Requirements

Copyright © 2010 SAP AG. All rights reserved 4 of 20

ASAP Implementation Methodology

6. Configuration
6.1 Client 1000 SAP Easy Access Menu
Changes are performed in the following transactions:

Transaction SPRO
Menu Path: IMG Financial Accounting (New)  Bank Accounting  Business
Transactions  Check Deposit  Define Posting Keys and Posting
Rules for Check Deposit

Transaction OT45
Menu Path: IMG Financial Accounting (New)  Bank Accounting  Business
Transactions  Check Deposit  Define Variant for Check Deposit

Transaction OT52
Menu Path: IMG Financial Accounting (New)  Bank Accounting  Business
Transactions  Payment Transactions  Manual Bank Statement 
Create and assign Business Transactions

Copyright © 2010 SAP AG. All rights reserved 5 of 20

ASAP Implementation Methodology

6.2 Define Posting Keys and Posting Rules for Check Deposit
Define Posting Keys and Posting Rules for Check Deposit

In this activity you store the posting keys and posting rules for check deposit.

Creating Keys for Posting Rules

Under this node, you define a posting rule for check deposits. The key determines the posting rules for general ledger and
subledger accounting. The posting rule represents the business transactions typical of the check deposit, such as:

 Incoming check to check clearing

 Check clearing to customer

 Bank to incoming check

Defining Posting Rules

You specify the posting rules for either one or two posting areas, depending on whether the posting transaction affects only
the general ledger or also the subledger.

For example, you need only one posting area if you do not use any clearing accounts, but instead directly debit the bank
account and credit the incoming check account.

Creating Account Symbols

You then control the account determination for each posting transaction and set up an account symbol for this.

In account determination, an account symbol previously setup depending on various modification factors is replaced by an
account to be posted to.

Account symbols are used to group together similar business transactions (such as incoming checks) and to direct them to
different accounts according to a pre-determined differentiation. This enables you to have flexible account determination for
clearing accounts that are to be posted to differently.

Examples of flexible account determination

1) You want to manage incoming checks in foreign currency (e.g., DEM) in a clearing account different from the account
where you manage incoming checks in local currency (e.g.,US$). You can do this with the following setup:

Account symbol Currency G/L account

Incoming checks + ++++++++09 (LC cash inflow)

Incoming checks DEM ++++++++14 (FC cash inflow)

The completely masked entry (++++++++++) in the "G/L account" field would lead to the outgoing account entered during
check deposit.

Copyright © 2010 SAP AG. All rights reserved 6 of 20

ASAP Implementation Methodology

2) You want to direct checks from the US to an account different from the one intended for incoming checks in US$. To do
this, you must create an account modification for this business transaction and specify the account to post to:

Account symbol Account modification G/L account

Incoming checks Checks USA 0000099999 (checks USA)

Incoming checks + ++++++++08(other checks
in US$)

Actions

1. Depending on the posting transaction, create one or two posting areas:

a) one for the bank posting
b) one for the subledger posting.
2. Store the posting rules for each posting area.
3. Create account symbols for the required transactions.
4. Store account determination rules for the affected account symbols.

Additional Information

You will find general information about account determination in the text on the posting interface.

Figure 1: Configuration Path for Posting Keys and Posting Rules for Check Deposit

Copyright © 2010 SAP AG. All rights reserved 7 of 20

ASAP Implementation Methodology

Figure 2: Creating Account Symbols

Figure 3: Assign Accounts to Account Symbols

Copyright © 2010 SAP AG. All rights reserved 8 of 20

ASAP Implementation Methodology

Figure 4: Create Keys for Posting Rules

Figure 5: Define Posting Rule for Check Deposit

Figure 6: Define Posting Rule for Check Issued

Copyright © 2010 SAP AG. All rights reserved 9 of 20

ASAP Implementation Methodology

Figure 7: Define Posting Rules for Check Received

Copyright © 2010 SAP AG. All rights reserved 10 of

20
ASAP Implementation Methodology

Figure 8: Define Posting Rules for Bank Charges

6.3 Check Deposit Transactions Configuration

Figure 9: Create and Assign Business Transaction Configuration Path

Create and Assign Business Transactions

In this step you store transaction indicators for check deposit and allocate these indicators to a posting rule.

You specify this indicator in the "Transaction" field on the initial screen of check deposit.

Account Modification

You may want to post individual transactions to an account different from the one provided by the posting method for the
posting rule in question. To do this, you create an account modification.

By specifying an account modification, you can control account determination so that the system posts the transaction to a
modified subaccount and not to the standard account. For more details on account determination see the section "Define
posting rules for check deposit".

Actions

1. Define transaction indicators.

2. Allocate a posting rule to each transaction indicator.
3. If necessary, set up an account modification.

Copyright © 2010 SAP AG. All rights reserved 11 of

20
ASAP Implementation Methodology

Figure 10: Create and Assign Business Transactions

6.4. Define Variants for Check Deposit

Define Variants for Check Deposit

In this step you can create your own account assignment variants for check deposit in order to modify the arrangement and/or
selection of account assignment fields according to your company-specific requirements.

One variant is delivered as a default. It cannot be changed.

If you do not want to work with the standard variant, you can deactivate it. New variants must be activated after you create
them.

Actions

1. To create a new variant, select Variant --> New variant --> Create....
2. In the pop-up window, enter the variant ID, description and the number of account assignment lines.
On the next screen, you see the possible account assignment fields in the right column. The fields for the account
assignment variant you will use are to be entered in the left column. The field Amount is predefined as a required
field.
3. Select the required fields from the list of possible fields.
The fields you select are transferred to the list of current fields and displayed one after the other (up to 80
characters). The offset column provides information on how many characters are needed in an account assignment
field.
4. Save your account assignment variant and then activate it.

Changing a Variant

Variants that are created can be modified at any time.

1. To delete an account assignment field, select Edit --> Delete field.

2. To add a new account assignment field, place the cursor on the preceding field and select the field you require
from the possible fields in the right column.

Copyright © 2010 SAP AG. All rights reserved 12 of

20
ASAP Implementation Methodology

If necessary, adjust the field positions by using the function "Change offset".

Figure 11: Define Variants for Check Deposit Configuration Path

Copyright © 2010 SAP AG. All rights reserved 13 of

20
ASAP Implementation Methodology

Figure 12: Create Screen Variant for Check Deposit

Copyright © 2010 SAP AG. All rights reserved 14 of

20
ASAP Implementation Methodology

6.4 Unit / Integration Testing

Environment: DEV 100

Test Scenario: Payment of Customer Invoices
Date of Test: 08/01/2013
Resource(s): Joy Ann Gunay

Step Action Data Input Expected Results Actual Results Pass Resolution
/ Documents / Fail
1 Select Customer
Open Invoices to be
Paid
2 Process Incoming
Payment via FF68

Steps:
1. Select Invoices to be paid.

2. Go to FF68, go to Settings > Specifications

3. Enter required details as shown:

Copyright © 2010 SAP AG. All rights reserved 15 of

20
ASAP Implementation Methodology

4. Enter details as shown:

5. Click Enter.
6. Input check details.

Copyright © 2010 SAP AG. All rights reserved 16 of

20
ASAP Implementation Methodology

7. For multiple items, double click document no. field. Input further values.

8. Click Save .

9. Click Post Individual List .

10. Go to SM35.

Copyright © 2010 SAP AG. All rights reserved 17 of

20
ASAP Implementation Methodology

11. Process Session.

Result:

Copyright © 2010 SAP AG. All rights reserved 18 of

20
ASAP Implementation Methodology

Copyright © 2010 SAP AG. All rights reserved 19 of

20
ASAP Implementation Methodology

Copyright © 2010 SAP AG. All rights reserved 20 of

20