Bank Statement Processing – BSP

The Working process

SAP Business One
Version 9.0

INTE
RNA
L
Objectives

After completing this unit, you will be able to:

 Enter the bank statement details to initiate the process.
 Process and finalize the bank statement results.
 List the operations BSP creates automatically in SAP Business One.

© 2014 SAP AG. All rights reserved. 2

The Working Process with BSP

After SAP Business One has been configured, you can start working with the
bank statement processing:

 Enter the relevant information in marketing invoices.

 Record your bank statement details.

 Process the Bank Statement.

© 2014 SAP AG. All rights reserved. 3

Enter the Relevant Information in Marketing Invoices

 In those cases where you

have defined the BP
Reference No. parameter as
matching criteria rule, you
need to ensure that the user
enters the reference number
in the Customer/ Vendor Ref.
No. field when creating
marketing documents.

© 2014 SAP AG. All rights reserved. 4

Record the Bank Statement Details

 On a regular basis, Maria the accountant at OEC Computers records the bank
statement details as received from the company house bank.

Banking  Bank Statement and External Reconciliation  Bank Statement Processing

 To automatically import the bank statement choose the Import from File button.

© 2014 SAP AG. All rights reserved. 5

Record the Bank Statement Details

 The Import from File

button is activated only if
you selected the Imported
Bank Statement box for
this bank in the House
Bank Accounts – Setup
window.

© 2014 SAP AG. All rights reserved. 6

Import from File

 The bank statement

information appears in the
Bank Statement Details
window.
 This is the .txt bank file that
was imported.

© 2014 SAP AG. All rights reserved. 7

Import from File

 Each line begins with a line

header; a two digit number.
This designates the type of
information present in the
line.

© 2014 SAP AG. All rights reserved. 8

Import from File

© 2014 SAP AG. All rights reserved. 9

Import from File

© 2014 SAP AG. All rights reserved. 10

Import from File

 The set of external codes

used for the bank account is
defined in the bank definition.
 If an internal code value has
been assigned, it will be
automatically populated.

© 2014 SAP AG. All rights reserved. 11

Import from File

 The amount for each row will

appear as an incoming
amount when the letter C
precedes the amount in the
bank file and as an outgoing
amount when D precedes the
amount.
© 2014 SAP AG. All rights reserved. 12
Import from File

Business Partner Details

 In the business partner fields

you can specify the details of
the business partner whose
transactions you want to
reconcile.

© 2014 SAP AG. All rights reserved. 13

Import from File

Dates for Posting

Creation

 The dates to be assigned to the transaction created by the BSP appear in the
corresponding date fields.
 By default, these columns are populated according to the definition set for the
particular bank in the Banks – Setup window.

© 2014 SAP AG. All rights reserved. 14

Record the Bank Statement Details

 While reviewing the import results, you can enter missing data and update existing data.
 After you enter all required transaction rows in the Bank Statement Details window, you
can begin to reconcile the bank statement.
 Or, you can save the bank statement as a draft and process it at a later time.

© 2014 SAP AG. All rights reserved. 15

Demo – Record the Bank Statement Details

© 2014 SAP AG. All rights reserved. 16

Process the Bank Statement

 After recording your bank statement details either manually or by import from the
bank, you can start processing the bank statement:

1. Initiate the reconciliation process.

2. SAP Business One retrieves payments and
journal entries.
3. Review proposals:
• The posting proposals for every
transaction row.
• The matching between the posting
proposal and the bank statement.
4. Approve or reject the posting proposals and
the reconciliations.
5. Finalize to post the payment transactions and to reconcile the open line items.
6. Check the postings in the system.

© 2014 SAP AG. All rights reserved. 17

1. Initiate the Reconciliation Process

SAP Business One prepares posting proposals for the transaction rows in the bank
statement based on the matching criteria.

© 2014 SAP AG. All rights reserved. 18

2. SAP Business One Retrieves Documents and JE

Posting proposals

Bank statement row

 Posting proposals are references to existing transactions proposed for linking with
transactions from bank statement rows.

© 2014 SAP AG. All rights reserved. 19

2. SAP Business One Retrieves Documents and JE

 The objective is to clear all bank statement rows.

 When a proposed transaction has a full match with a transaction row, they are both
selected.

© 2014 SAP AG. All rights reserved. 20

3. Review Proposals

© 2014 SAP AG. All rights reserved. 21

3. Review Proposals

 The results of the G/L Account from/to

Bank Account posting method.

© 2014 SAP AG. All rights reserved. 22

3. Review Proposals

© 2014 SAP AG. All rights reserved. 23

3. Review Proposals

 While reviewing the proposals generated by the system use the Matching Criteria Log
column to see the round in which the matching was found.

© 2014 SAP AG. All rights reserved. 24

4. Approve/ Reject Posting Proposals and Reconciliations

© 2014 SAP AG. All rights reserved. 25

 4. Approve/ Reject Posting Proposals and Reconciliations

 The expected results from the first row, based on the posting method, are:
 An incoming payment from Parameters Technologies.
 An internal reconciliation between the invoice the and the new payment. And,
 An external reconciliation between the bank statement row and the new payment.

 The BP from/to Bank Account posting method is designed for businesses that intensively
use direct bank transfer for incoming payments. They are not aware of the received
payment until getting the updated bank statement from the bank.

© 2014 SAP AG. All rights reserved. 26

4. Approve/ Reject Posting Proposals and Reconciliations

© 2014 SAP AG. All rights reserved. 27

4. Approve/ Reject Posting Proposals and Reconciliations

© 2014 SAP AG. All rights reserved. 28

4. Approve/ Reject Posting Proposals and Reconciliations

 The default value in the Applied Amount field is the Total field in the original document
or transaction in the payment currency.
 Choose Ctrl+B (or the Copy Balance Due option from the context menu) to update the
Applied amount field.

Ctrl + B

© 2014 SAP AG. All rights reserved. 29

4. Approve/ Reject Posting Proposals and Reconciliations

 Now the reconciliation is balanced and the Balance field at the top of the window is set
to zero.
 Note that if the difference between the documents total amount is within the allowed
payment difference, it will go to the underpayment/overpayment account and the
invoice will be closed.

© 2014 SAP AG. All rights reserved. 30

 5. Finalize the Bank Statement

 You can finalize the bank statement or save it as draft.

 You cannot finalize a bank statement until:
 Every bank statement row is cleared and,
 The Difference field is set to zero.

© 2014 SAP AG. All rights reserved. 31

5. Finalize the Bank Statement

Starting Balance: 89.386,89

Ending Balance: 75.274,03
Difference: 0,60

Incoming: 6.122,00
Outgoing: 20.235,46

Starting balance 89.386,89

+ +
Total incoming amount 6.122,00
Difference = - -
0,60 Total outgoing amount 20.235,46
- -
Ending balance 75.274,03

© 2014 SAP AG. All rights reserved. 32

6. Check the Postings in the System

Banking  Banking Reports  Bank Statement Information

© 2014 SAP AG. All rights reserved. 33

Demo – Process the Bank Statement

© 2014 SAP AG. All rights reserved. 34

Outgoing Payment Created by the Payment Wizard

 The transaction row represents a payment created by the payment wizard using an
interim account. The posting method is Interim Account from/to Bank Account.
 For each house bank you can specify a G/L account to be used as an interim account
when a payment run takes place.

© 2014 SAP AG. All rights reserved. 35

The Payment Wizard in SAP Business One

Payment Wizard

Incoming Payments: Bank Account Outgoing Payments:

 Bank Transfer  Checks
 Bank Transfer

Bank Payment File

Transfer

© 2014 SAP AG. All rights reserved. 36

The Payment Wizard in SAP Business One

Administration  Setup  Banking  Payment Methods

The transactions created by the payment

run are posted to the interim account and
not to the house bank G/L account.

© 2014 SAP AG. All rights reserved. 37

Business Example with an Interim Account

 The payment wizard creates:

 Payment to vendor.
 Payment file which is sent to the bank.
 The bank processes the payments and updates the bank statement they send to you.
© 2014 SAP AG. All rights reserved. 38
Business Example with an Interim Account

 You record the payment in the bank statement with the posting method Interim Account
from/to Bank Account.
 On creation of the journal entry there is:
 An internal reconciliation between the interim bank account postings from the
payment wizard and the payment.
 An external reconciliation in the bank account against the bank statement row.
© 2014 SAP AG. All rights reserved. 39
Thanks

You have completed the BSP working process topic

Thank you for your time!

© 2014 SAP AG. All rights reserved. 40

© 2014 SAP AG or an SAP affiliate company.
All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an
SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or
SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 41