Bank Reconciliation 

Use

Bank statements comprise transactions that need to be posted in FI and transactions that have been posted to bank interim (clearing) accounts. You now have to clear (match) these postings with postings in the main G/L account. Companies in the United Kingdom can use the Import Bank Statement: Great Britain (RFEBGB00) report to upload and process a bank transaction file in the UK APACS format.

If you work with banks that can supply bank transaction files in other formats, for example, BAI or SWIFT MT940, use the generic report Bank Statement: Various Formats (SWIFT, MultiCash, BAI…) (RFEBKA00) to import and process the file.

Features

The Import Bank Statement: Great Britain (RFEBGB00) report imports bank statements into the SAP System, and then creates batch input sessions to post to G/L and subledger accounts.

By selecting the parameters, you can specify whether the two sessions are generated in one run or whether only the session for G/L accounts is generated first. The batch input session names are generated by the program, in which case you can choose from two rules:

·        House bank ID and account ID (for example, LL001-CURR1)

·        House bank ID and bank statement number (for example, LL001-034)

The session name for subledger accounts always begins with /.

Check payments are matched based on the check number assigned by the International Payment Medium – Check (with Check Management) (RFFOUS_C) report. The check encashment date is updated by the posting from the bank reconciliation.

BACS payments are matched to the bank clearing account based on the SAPBACS reference on the bank transaction record assigned by the DME tree format GB_BACS, used with the Payment Medium Workbench.

Activities

Customizing

The program checks whether the business transaction codes (external transactions) used by the bank were allocated to an internal transaction within system configuration. This is a necessary since the system posts to the G/L and subledger accounts using the posting rules stored for the internal transaction. You maintain the required entries in Customizing for Financial Accounting, by choosing Bank Accounting ® Business Transactions ®Payment Transactions ® Electronic Bank Statement ® Make Global Settings for Electronic Bank Statement. Choose the Create Transaction Type dialog structure and select the transaction type GB-APACS for UK: APACS Lloyds. Choose the Assign External Transaction Types to Posting Rules dialog structure and make the following entries:

       1.      Enter all external transaction codes. Obtain a complete list of each transaction code used by your bank. The delivered external transactions codes are based on the codes used by Lloyds bank. Add or change these external codes, as required.

       2.      Normally, banks use every bank transaction code excluding the codes for incoming and outgoing payments. Fill the Sign field with "+" for cash receipts and "-" for cash disbursements.

       3.      The Processing type field is used only in the United Kingdom and specifies further processing. The following entries need to be described:

¡        01 - clearing with check: To be able to make a clearing, the data for the transmitted check number must already exist in the system.

¡        05 - customer cash receipt: Customer payments in our favor are to be identified by the transferred reference text. The reference text normally contains the invoice or document number.

¡        05 - BACS transfer/ BACS bank collection: The bank confirms payment orders or bank collections that have been executed. The reference number transferred identifies the affected payment documents.
 To use processing type 05, always maintain the two entries. To differentiate the entries, the system supplements the external transaction code in BACS with the character string "SAPBACS" after the third character.
Example:
"17        ","-","17_A","05","00"
"17 SAPBACS","-","17_B","05","19"

¡        06 - bank charges / interest / dividends: In this processing type, the parameter enables you to store various G/L accounts for one account symbol in account determination.
To do this, enter, for example, INTEREST or CHARGE in the Account modification field in the Assign Accounts to Account Symbol dialog structure. To determine the required G/L account during G/L account determination, the system compares the note to payee transferred by the bank with the values in the Account modification field.

       4.      Only specify the interpretation algorithm for BACS transactions (processing type 05). Use algorithm 19 as the interpretation algorithm.

If the program finds an external transaction that is not maintained in the corresponding table, it terminates after fully importing the bank statement, and outputs a list with the missing entries (error log). You must maintain these missing entries so that the system can generate the posting transactions in the appropriate sessions. You then have to restart the program, making sure you deselect the Import data field this time since the bank statement is already in the SAP System.

When restarted, the program searches the buffer for all line items that are not yet indicated as posted in the respective posting area. A line item is only regarded as posted if a posting is put into a session.

Output

The posting log provides information, separated according to posting area, on all postings put into the batch input session. It also lists the external business transaction codes and the internal transactions which control posting.

The processing statistics show you:

·        The number of postings that were created for each session and the number that could not be created due to an error

·        The number of line items for which postings could not be created, by definition.