Straight2Bank Access Lite

Straight2Bank Access Lite

Pre-Implementation Questionnaire

June 10, 2016 1

Straight2Bank Access Lite

TABLE OF CONTENTS

1. Introduction ................................................................................................................. 3
2. Functional Requirements ............................................................................................ 3
2.1. Payment Run Process ....................................................................................... 3
2.2. Bank Reconciliation........................................................................................... 5
3. Security requirements ................................................................................................. 6
4. Network and Connectivity ........................................................................................... 7
5. System Requirement .................................................................................................. 7
6. For any other requirements, please elaborate below ................................................... 8

June 10, 2016 2

Straight2Bank Access Lite

1. INTRODUCTION

Straight2Bank Access Lite is an add-on to the client’s SAP ERP to automatically generate a
payment file in IPAYMENT CSV format and to automatically send this file to the Bank for payment
processing via SAP’s inbuilt Web Services connectivity.

The Bank returns File and Transaction level statuses and End-of-Day account statements to the
SAP ERP. Straight2Bank Access Lite uploads these files to desired location and allows monitoring
of these files through SAP ERP screens.

Straight2Bank Access Lite leverages on the SAP ERP’s automatic payment run, Web services
connectivity and Security functionality to enable these capabilities.

The below document captures the client’s current process flows on the ERP and aids in accessing
the scope of Straight2Bank Access Lite implementations.

2. FUNCTIONAL REQUIREMENTS
2.1. Payment Run Process

Straight2Bank Access Lite automates the payment run process to enable a straight-through
processing of payables.

Automatic payment is the process, which will complete a payment transaction automatically. To
create a payment run program, certain parameters should be maintained in the selection criteria. In
the Execution of the payment proposal list, logs get generated, items may be blocked for payments
and updates can be made in order to remove or add the block. After the Proposal run the actual
payment run gets executed. Access Lite leverages on SAP’s F110 transaction/F-53 Manual
payments, F-48 Down Payments.

The questions below elicit details on the current payment process and SAP ERP configurations.

Question Answer (Please elaborate)

What is the Payee type currently 1) Individual Payee

used?
2) Down payments 1 & 2 both applies.

Please list, if others:

June 10, 2016 3

Straight2Bank Access Lite

Question Answer (Please elaborate)

What are all the deductions made? 1) Tax Deductions at Source (TDS)

2) Credit Memo
TDS at Source , Credit Note
3) Any other:

What are all the payment methods 1) Book Transfer

used?
2) Telegraphic Transfer

3) Corporate Cheque

4) Demand Draft/Payorder

5) RTGS

6) Payroll

Please list, if others:

Is Automatic Payment Run

Configuration used or it is already Currently using Manual Payment F-53 , Provision for
configured in the system (SAP TCode Automatic Payment F110 will also be used later on.
FBZP)?
NOTE: Best practise is to create
separate payment methods per bank
Briefly describe the current
automatic payment generation
Refer to the answer given above.
process (SAP TCode F110)

Please include workflows, details on

the automatic payment run, handling
on the ERP and any manual steps
involved, if any
Briefly describe the current manual
payment generation process (SAP
TCode F’53/ F’43/ F’48/ F’58) F-53 - Manual Outgoing Payment for entering the payment within
the system after receiving necessary approval.
Please include workflows, details on
the manual payment run, handling on
the ERP and any manual steps
involved, if any

Please explain the payment approval

work flow

June 10, 2016 4

Straight2Bank Access Lite

Question Answer (Please elaborate)

Currently do you generate any XML

payment file format today?
No
e.g.
a) Customized ZRFXX SAP Script
b) Customized XML
What are the table and field names Not applicable
currently used for specifying the
Data Table Name Field Remarks
following information to the Bank
Name
Print Location
Clearing Zone Code
FX rate
FX contract number
Charger Bearer To specify
SHARE, Borne by
Creditor, Borne by
Debtor
Delivery Method To specify Mail to
Debtor, Courier to
Creditor
Remittance Method To specify EMAIL or
FAX to send the
remittance advice to
recipient
Remittance Email If Remittance advice
method is by email.

2.2. Bank Reconciliation

Straight2Bank Access Lite supports automatic upload of bank statements onto the ERP (SAP
TCode FF_5).

Further, posting rules may be defined to automatically post the entries in the bank statements into
the General Ledger (GL) after closing out the corresponding open items on the ERP.

Question Answer (Please elaborate)

What is the current re-conciliation Automatic or Manual Reconciliation ?

process?
Is automatic upload of bank
statements required? Manual
Are automatic bank statement
configurations required? Not yet

(Ex: Posting rules configurations, GL

June 10, 2016 5

Straight2Bank Access Lite

Question Answer (Please elaborate)

entries)
What is the format of the end-of-day
bank statement expected? MT940
What posting SAP TCodes are 1) SWIFT SAP TCodes
required in the bank statements?
Swift MT940 format Electronic Bank Statement format required
for auto reconcilliation

Please list, if others:

Is there any special characters used

in any of the fields?
Are there any other reports required? Report File Format (please specify)
Daily Bank Statement MT940
If so, please mention the required
format

3. SECURITY REQUIREMENTS
Open source PGP based signing and encryption software is provided in the Straight2Bank Access
Lite installation bundle, which can be configured to secure the transmission of the data between
ERP and the bank.

NOTE: SAP’s Crypto library (transaction STRUST) is required to establish a secure transport layer
(SSL) connection with the bank.

Question Answer (Please elaborate)

For data level security, is PGP

signing and encryption required or
will SAP’ Message Level Signing
(MLS) be used?

Please encircle the preferred

option(s
What is the system landscape? a) 3 system landscape - Development, Quality, Production
At least 2 system landscape is
expected.
Currently we have 3 system landscape as given above

June 10, 2016 6

Straight2Bank Access Lite

4. NETWORK AND CONNECTIVITY

Question Answer (Please elaborate)

Is there a proxy required for ERP to

Bank flows?

Is Web dispatcher or Reverse proxy

required for the Bank to ERP flows?

Access Lite will use SAP’s Web

services connectivity that is available
out of the box.

Is there any other connectivity

requirement? (EX: SFTP, others)

5. SYSTEM REQUIREMENT
DEVELOPMENT QUALITY PRODUCTION
What is the
ERP version
and support
package level?
What is the
ERP
component
Software Release Level Software Release Level
Software Release Level
level? Component Component Component
SAP_ABA SAP_ABA SAP_ABA
SAP_BASIS SAP_BASIS SAP_BASIS
SAP_AP SAP_AP SAP_AP
SAP_APPL SAP_APPL SAP_APPL

What is the
Operating
system of the
ERP?

Please select
the OS used.

June 10, 2016 7

Straight2Bank Access Lite

What is the
system bit
level? Is it 32
bit or 64 bit?

Which is the
Back end
database?

Please select
the database
used.

What is the
Java version of
the Operating
System?

Is Crypto
library installed
on the system?

SAP Tcode:
/nSTRUST
Check for SNC
SAPCryptolib
folder
existence.

Is HTTPS port
created?

What is the
system Internet
Explorer
version?

IP Address

Host Name

NOTE: Host
name should be
fully qualified
domain name

6. FOR ANY OTHER REQUIREMENTS, PLEASE ELABORATE BELOW

June 10, 2016 8

Straight2Bank Access Lite

June 10, 2016 9