Australian Pharmaceutical Industries Limited

Business Blueprint

Bank Accounting

Version 0.1
Prepared by Finance Team
06/05/2013

This document contains information that is proprietary and confidential to Australian Pharmaceutical Industries, which shall not be disclosed, transmitted, or duplicated, used in whole or in part for any
purpose other than its intended purpose outside Australian Pharmaceutical Industries. Any use or disclosure in whole or in part of this information without express written permission of Australian
Pharmaceutical Industries is prohibited. Any other company and product names mentioned are used for identification purposes only, and may be trademarks of their respective owners.

[Link] V0.1 API Commercial in C

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

DOCUMENT CONTROL

Authors
Name Role Version Description Date
Poonam Gupta OneERP Finance Team 0.1 10.06.2013
Irene Chen OneERP Finance Process 0.1 10.06.2013
Specialist
David Vaughan OneERP Finance Lead 10.06.2013

Reviewers
Name Role Date
David Vaughan OneERP Finance Lead 17.06.2013
Craig Hawke OneERP Finance Process Lead
Steve Gutmann OneERP Solution Architect
Craig Wilkeson OneERP Solution Architect
Anne Howard OneERP Technical Lead

Approvers
Name Role Date
Craig Hawke OneERP Finance Process Lead
David Vaughan OneERP Finance Lead
Kevin Geary OneERP Project Manager
Cary Farmer OneERP Project Director
Graeme Fallet OneERP Finance Process Owner

Reference Documents
Title Version Location
OneERP Project Glossary

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 2 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

CONTENTS

1 Business Requirements 5
1.1 Purpose 5
1.2 Scope 5
1.3 Audience 6
1.4 Business Rules 6

2 Solution Design 9
2.1 Overview 9
2.1.1 Key Design Principles 9
2.1.2 Key Assumptions 9

2.2 Process Design – House Bank Creation 10

2.2.1 Description 10
2.2.2 Process Flow 10
2.2.3 Process Steps 10
2.2.4 Location 11
2.2.5 Frequency 11
2.2.6 Duration 11
2.2.7 User Interface 11
2.2.8 Process Variations 11

2.3 Process Design – Electronic Bank Statement Upload Process 12

2.3.1 Description 12
2.3.2 Process Flow 14
2.3.3 Process Steps 15
2.3.4 Location 18
2.3.5 Frequency 18
2.3.6 Duration 18
2.3.7 User Interface 18
2.3.8 Process Variations 18

2.4 Process Design – Bank Reconciliation Process 19

2.4.1 Description 19
2.4.2 Process Flow 20
2.4.3 Process Steps 21
2.4.4 Location 23
2.4.5 Frequency 23
2.4.6 Duration 23
2.4.7 User Interface 23
2.4.8 Process Variations 23

2.5 Process Design – Bank Files for Customer and Vendor Payments 24
2.5.1 Description 24
2.5.2 Process Flow 24
2.5.3 Process Steps 25
2.5.4 Location 25
2.5.5 Frequency 25
2.5.6 Duration 25
2.5.7 User Interface 25
2.5.8 Process Variations 25

2.6 System Design 26

2.6.1 System Configuration 26
2.6.2 Workflow Objects 28
2.6.3 Report Objects 28
2.6.4 Interface Objects 28
2.6.5 Conversion Objects 28
2.6.6 Enhancement Objects 29
2.6.7 Form Objects 29
2.6.8 Authorisations 29
2.6.9 Legacy System Impacts 29
2.6.10 Design Dependencies 30
2.6.11 Change Impacts 30

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 3 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

3 Appendix Further Information 31

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 4 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

1 BUSINESS REQUIREMENTS
This document is the Business Blueprint for the Bank Accounting module of SAP. The Business Blueprint represents
the conceptual design of the system and will be the basis for the system’s development in the remaining phases of the
project.

1.1 PURPOSE
This Bank Accounting Business Blueprint Design (BBD) comprises the processes and procedure steps for creation of
House Banks and Bank Accounts, uploading of Bank Statements, perform Bank Reconciliations and reporting.

1.2 SCOPE
The document covers all processes relating to Bank Accounting 6.7 under area 6 Finance in the process scope below:

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 5 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

The below is a context diagram of ‘creation to reporting’ End to End business process.
End-to-End Process Overview

Figure
1:
House
Bank
Creation
to
Reportin
g

NB:
Level 1 =
High
Level
Process
e.g. Finance
Level 2 = Process level e.g. Fixed Assets, General Ledger, Bank Accounting
Level 3 = Sub Process level e.g. House Bank Creation, Electronic Bank Statement upload
During the Blueprint phase, the level 3 processes were determined (see table below).

Level 2 Level 3
6.7 Bank Accounting 6.7.2 House Bank Creation
6.7.3 Electronic Bank Statement Upload
6.7.4 Bank Reconciliation Process
6.7.5 Bank Files for Customer and Vendor Payments

The level 3 processes were analysed and decomposed into a number of level 4 process steps (documented in more detail
in Section 2 of this Blueprint).

1.3 AUDIENCE
This document will help:
 Business Process Team
 SMEs and Business Customers
 Implementation team from TCS
 Post Go Live Support team
 Project Team

1.4 BUSINESS RULES

The requirements list below only related to business process. SAP basic functionalities are understood as must have.
The performance requirements are documented in other blueprint documents. Work Instructions and other documents
will be provided during the project phases.

Criticality
ID Description Met by Design Reason not met
[H/M/L]
1 Must have the ability to create / maintain House H Yes
Banks and Accounts as required. Refer to Section
2.2.1
2 Must have the ability to create multiple bank H Yes
accounts within a house bank Refer to Section
2.2.1
3 Must have the ability to validate BSB and L Yes
account length to ensure accuracy of inputs Refer to Section
2.2.1

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 6 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

Criticality
ID Description Met by Design Reason not met
[H/M/L]
4 Must have the ability to segregate incoming / H Yes
outgoing bank transactions and account for them Refer to Section
correctly. (Posting rules for each transaction to be 2.3.1
specified)
5 Must have the ability to report on bank master L Yes
data (House Banks). Refer to Section
2.6.3
6 Must have the ability to import/retrieve and H Yes
process Bank Statement data for each predefined Refer to Section
bank account automatically and provide a manual 2.3.1
input process as a back up.
7 Must be able to ensure that Bank statements are H Yes
processed once. i.e. Control over duplicate bank Refer to Section
statement processing. 2.3.1
8 Must be able to hold all the data required to H Yes
account for bank transactions and the Refer to Section
reconciliation of those bank accounts 2.3.1
9 Must be able to allocate payments received in the M Yes Subject to RICEF
bank to the customer accounts where data is approval and further
given to support this. (E.g Merchant / Customer analysis of Bank
number) statement data.
10 Must have the ability to report on open bank H Yes
items. (Reconciliation Items) Refer to Section
2.4.1
11 Must be able to produce a Direct Debit file for H Yes RICEF Required
Amex credit card payments from customers. Refer to Section
(Specification to be provided) 2.5.1
12 Must be able to produce a Direct Debit file for H Yes RICEF Required
ASPIRE payments from customers. Refer to Section
(Specification to be provided) 2.5.1
13 Must be able to produce Direct Debit File for H Yes RICEF Required
customer direct payments Refer to Section
(Specification to be provided) 2.5.1
14 Must be able to product EFT file for payments to H Yes RICEF Required
vendors (NAB Specification) Refer to Section
2.5.1
15 Must be able to print cheques in API formats as H Yes RICEF Required
specified. (Currently two) Refer to Section
2.5.1
16 Must be able to re-print the cheque if required H Yes
and have cheque register functionality that allows Refer to Section
for a new cheque number being used, where a 2.5.1
cheque has been destroyed and provide voided
cheque lists.
17 Must be able to provide reconciliation process for H Yes
ASPIRE securitization payments from WBC to Refer to Section
NAB. This process will reconcile that all 2.5.1
payments made by Westpac are received by
NAB.
18 Must be able to calculate Merchant fee (Amex & H No Subject to RICEF
Diners)and GST based on predefined rules and approval
percentage, and post to GL
19 Must be able to process retail (corporate stores) H Yes - Refer to AR
bank transactions and provide a reconciliation BBD
mechanism for retail sales to be reconciled to
bank receipts.
20 Must be able to retrieve the bank statement file H No Not a functional
from the bank as required. team requirement.

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 7 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

Criticality
ID Description Met by Design Reason not met
[H/M/L]
To be transferred to
the Tech team.
21 Must be able to continue process bank H No Subject to RICEF
reconciliation when new transaction codes are approval
used by API. Undefined transcode must be posted
to a Global Clearing account for manual
processing.

Note: all bank interface file formats and sample files, included AMX, EFT, Direct Debit, ASPIRE, are upload in
Confluence.

[Link]

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 8 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2 SOLUTION DESIGN
2.1 OVERVIEW

2.1.1 KEY DESIGN PRINCIPLES

Id Description
1 SAP Standard House Bank creation process to be used.
2 SAP Standard Bank account number and Bank number length functionality to be used.
3 SAP Standard Electronic Bank Statement upload process to be used.
4 SAP Standard Bank Reconciliation functionality to be used.
5 SAP Standard Bank Reports to be used.

2.1.2 KEY ASSUMPTIONS

Id Description
1 This design incorporates SAP ‘Best Practice’ functionality.
2 Both Westpac and NAB Bank Statements will be received in a SAP standard format.
3 Only Westpac and NAB Bank accounts will be used.
4 Direct debit output files can be created using SAP standard DME engine configuration.

2.2 PROCESS DESIGN – HOUSE BANK CREATION

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 9 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.2.1 DESCRIPTION
House Banks are created at company code level. Each house bank of a company code is represented by a bank ID in the
SAP system. Every account at a house bank is represented by an account ID. In the SAP system, the bank ID and the
account ID is used to specify bank details. An authorisation process also overlays the creation / modification procedure
to ensure that all changes are appropriate from a Group or Company perspective and duly authorised.

At the time of House Bank creation system will validate the length of bank ID and account ID.
(Required length of bank ID and account ID needs to be confirm)

2.2.2 PROCESS FLOW

PROCESS FLOW DIAGRAM

The flowchart below details the general tasks required for House Bank Creation.

Figure 2: House Bank Creation

Visio Document Name Hyperlink

House Bank Creation [Link]
Process House+Bank+[Link]

2.2.3 PROCESS STEPS

Step Role Description Enablers / Dev ID Policies / Guidelines

1 Treasury Officer Identification of a New Bank Manual House Bank identified.
required by Business

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 10 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

Step Role Description Enablers / Dev ID Policies / Guidelines

2 Treasury Officer Request to create the House Manual Request received by the
Bank will be sent to the Treasury Team.
Treasury Team.
3 Treasury Officer Treasury performs the Bank Manual Bank Account opened at
Opening formalities and bank.
opens the Bank Account
4 Treasury Officer Identification of New G/L Manual New Bank G/L account for
creation by the Treasury the House bank has been
Team identified with the name and
description.
5 Treasury Officer Fill in the request for a New Manual The G/L creation form is
G/L creation form filled and sent for CFO
approval.
6 Treasury Officer Sent G/L creation form Manual CFO has received the creation
request to CFO for approval form for approval.
7 CFO / Finance CFO approves and sends the Manual CFO approves G/L creation
Manager request to the Central Master form request.
Data Team
8 Central Master Central master data team FS00 (Link to GL G/L has created and notified
Data Team creates G/L and notifies account creation in GL Treasury Team.
Treasury Team BBD)
9 Treasury Officer Treasury team fill up the Manual House Bank Creation form
House Bank Creation form received.
and sends it to SAP
administrator
10 SAP SAP Administrator creates FI12 House Bank has created and
Administrator the House Bank and notifies notified to Treasury, AR/AP
Treasury, AR/AP teams and teams and Business units.
Business units.

2.2.4 LOCATION
This function will be performed at Corporate Office

2.2.5 FREQUENCY
This function will performed only on request and infrequently.

2.2.6 DURATION
This function will take approximately between, a day to a week depending upon the approval process.

2.2.7 USER INTERFACE

None

2.2.8 PROCESS VARIATIONS

There are no scenario variations for House Bank creation.

2.3 PROCESS DESIGN – ELECTRONIC BANK STATEMENT UPLOAD PROCESS

2.3.1 DESCRIPTION
API will be using a daily automated processes for processing bank statements in the following format for Australia
electronically into the SAP system.

Westpac Bank – Multicash Format

NAB Bank - BAI2 format

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 11 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

SAP uses an automated process of uploading the bank statements. API banks will provide the bank statement (in
specified format) file in a secure SAP area, using an automatic process to move the required files. Any errors with the
bank statement file (e.g. statement missing for day, statement date not correct, etc.) during the upload into SAP will be
communicated to the bank by the Bank Reconciliation Officer.

A standard control will be in place to ensure that duplicate files are not processed. This control requires the bank
statements to be loaded in numerical sequence. i.e. Bank statement 1 to be loaded before the system will allow bank
statement 2 to be loaded.

Bank Statements cannot be uploaded if an unknown “new” external transaction code exists in the file, a transaction code
that is not yet configured in the system or if the statement is not placed by the bank in the secure area at the time of
batch job schedule. Where this occurs, the Bank Reconciliation Officer will communicate with the SAP Administrator
in order to update the new external transcode in SAP, prior to rerunning the bank statement upload process,
alternatively, this can be left for the next scheduled run.

The Bank statement transactions will be processed and posted in the general ledger and where required to the sub ledger
accounts based on the transaction codes and data specified in the bank statement information. Each bank “trans code” is
assigned to a particular posting rule within SAP, which directs the postings to a nominated GL bank clearing and in
certain cases, to sub-ledger accounts.

Set out below are the posting rules for different types of bank transactions for API.

Outgoing Payments: For AP EFT payments a posting rule will be defined as follows:

Posting Entry 1 will post credit entry to Main bank account and debit entry will be posted to relevant bank clearing
account

Sample Accounting Document for outgoing payments

Posting Entry 1:

Doc DR/CR Sample Account Group Description Management Accounting Amount

Type Account
SR CR Bank - SAP Main Corporate Profit Centre 100.00
SR DR Bank – AP EFT Clearing A/c/ Corporate Profit Centre 100.00
AP Cheque Clearing A/c

In the case of an outgoing payment reversal, the reversal entry will be generated by the bank statement upload
process. IE Reversals will be driven by the bank entry and are equal and opposite to normal entries.
Bank Charges & Merchandise Charges: For bank charges a posting rule will be defined as follows:

Posting Area 1: SAP will post a credit entry to the Main bank account and a Debit Entry to the relevant bank charges
account. No level 2 transaction is required.

Sample Accounting Document for Bank Charges

Posting Entry 1:

Doc DR/CR Sample Account Group Description Management Accounting Amount

Type Account
SR CR Bank - SAP Main Corporate Profit Centre 100.00
SR DR Bank & Merchant Charges Corporate Cost Centre 100.00

Incoming Electronic Payments, e.g. EFT, Credit Card etc.: Two posting rules will be defined as follows:

Sample Accounting Document for incoming electronic payments (without clearing customer invoices)
Posting Entry 1:
Doc DR/CR Sample Account Group Description Management Accounting Amount
Type Account
SR DR Bank - SAP Main Corporate Profit Centre 100.00

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 12 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

SR CR Bank – AR EFT Clearing A/c Corporate Profit Centre 100.00

Posting Entry 2:

Doc DR/CR Sample Account Group Description Management Accounting Amount

Type Account
DZ DR Bank – AR EFT Clearing A/c Corporate Profit Centre 100.00
DZ CR Customer Name 100.00

Incoming Manual Payments e.g. Cheque, Cash

Sample Accounting Document for manual incoming payments

Posting Entry 1:
Doc DR/CR Sample Account Group Description Management Accounting Amount
Type Account
SR DR Bank - SAP Main Corporate Profit Centre 100.00
SR CR Bank – AR Cheque Clearing Corporate Profit Centre 100.00
A/c

In case of a dishonoured cheque, a reverse entry will be generated by the bank statement upload process based on
the Tran code for reversal.

Doc DR/CR Sample Account Group Description Management Accounting Amount

Type Account
SR CR Bank - SAP Main Corporate Profit Centre 100.00
SR DR Bank – AR Cheque Clearing Corporate Profit Centre 100.00
A/c

Where a transaction is recognised (i.e. transaction type and document / customer reference and value) it is automatically
posted to the GL Bank, designated bank GL Clearing Accounts and subsequently to sub-ledger account.

For every House bank (Main Bank), API will have following Bank Clearing Accounts:

GL Account Description
Main Bank
AP Direct Debit Clearing
AP Cheque Clearing
AP EFT Clearing
AP Miscellaneous Credit Clearing
AR Cheque Clearing
AR EFT Clearing
AR EFTPOS Clearing
AR Direct Debit Clearing
AR Miscellaneous Credit Clearing
AR Branch Cash Clearing
AR Merchant Credit Card Clearing
Sweeping Clearing
Treasury Clearing
Payroll Clearing

Examples of sample accounting documents and bank clearing accounts needs to be updated after finalising the posting
rule details

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 13 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 14 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.3.2 PROCESS FLOW

PROCESS FLOW DIAGRAM

The flowchart below details the general tasks required for electronic bank statement upload.

Figure 3: Electronic Bank Statement Upload

Visio Hyperlink
Document
Name
Electronic [Link]
Bank Electronic+Bank+Statement+[Link]
Statemen
t upload
process

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 15 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.3.3 PROCESS STEPS

Step Role Description Enablers / Dev ID Policies / Guidelines

1 Electronic file Electronic Bank Statement File Transfer outside of Bank Statement
transfer from NAB/Westpac Bank SAP downloaded.
uploaded via Process
Integration
Central Server

2 Batch User Import the electronic FF_5 Bank Statement uploaded.

statement to SAP
3 Verify bank The system confirms the
statement bank statement is in
number and date sequence
4 Reconciliation Check whether the import is FF_5 Once the import is
Officer successful. successful follow Process
Where not successful, issues Step 07
are to be investigated and
corrected as required.
5 Reconciliation Import is unsuccessful FF_5 Check to see the error log, if
Officer there are any new transcodes
required.
6 Reconciliation Send the mapping rules to Manual Mapping rules sent to
Officer create new transcode to Finance Support Team
Finance Support Team
7 Finance Support Create the new transcode Link to update transcode New Transcode updated,
Team and assign to relevant process (Systems follow Process Step 02
posting rule. administration Document)
8 Reconciliation Move file to relevant Folder After successful import to
Officer electronic bank statement
file into SAP, move the files
to Separate folder for
electronic storage.
9 Reconciliation Check if all GL Clearing FEBA Review posting area 1
Officer account transactions have exceptions.
been posted
10 Reconciliation Check reasons for failed Manual Analyse the reasons for the
Officer transactions failed transactions, correct
the issues and as required.
11 Reconciliation Post failed clearing FEBA Post the unsuccessful
Officer transactions transactions once corrected.
FEBA
12 Reconciliation Perform Automatic/Manual F.13/F-03 To clear all Bank Clearing
Officer Clearing GL’s
13 Reconciliation File process error Is there any error for
Officer processing the bank
statement file?
14 Reconciliation In case of File error, Manual Communicate the problem
Officer reconciliation officer will to the bank. When problem
inform to bank resolved, go to process step
2

2.3.4 LOCATION
This function will be performed at Corporate Office

2.3.5 FREQUENCY
This function will be performed daily.

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 16 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.3.6 DURATION
This function will take approximately between 15 to 30 minutes if there are no processing errors but could take days if
the bank needs to make changes, or if trans codes need to be updated.

2.3.7 USER INTERFACE

Bank files to be available in the correct location.

2.3.8 PROCESS VARIATIONS

There are no scenario variations for Electronic Bank Statement Upload process.

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 17 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.4 PROCESS DESIGN – BANK RECONCILIATION PROCESS

2.4.1 DESCRIPTION
The purpose of the bank reconciliation process is to review postings generated by the electronic bank statement and
attend to unreconciled items that have arisen. All bank postings are posted to the Bank GL and one of the many bank
GL Clearing accounts. Unreconciled items will be those uncleared items in the bank GL clearing accounts. These
transactions will result bank postings where the source transaction has not yet been associated with the bank entry, or
when the originating item has yet to be processed through the bank. The clearing processes should be run on a daily
basis to ensure clearing of open items are completed regularly so that only legitimate unprocessed items remain.

Bank reconciliation officers should check that the balance on the physical bank statement agrees with the GL Bank
account on a daily basis. The Bank GL account must always reflect the transaction that occur on the bank statement and
therefore will always equal the balance per the bank statement.
Apart from the day-to-day allocation of unreconciled items, the monthly bank reconciliation process will be performed
by the appropriate departments (AR, AP, Treasury, etc.), which includes the following steps:
 Analysis and posting of proposed sub ledger postings that have not yet been posted. (AR payments received not
posted to customers)

 Analyse, clear and reconcile the Bank Clearing accounts.

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 18 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.4.2 PROCESS FLOW

PROCESS FLOW DIAGRAM

The flowchart below details the general tasks required for bank reconciliation process

Figure 4: Bank Reconciliation Process

Visio Document Hyperlink

Name

House Bank [Link]

Creation Bank+Reconciliation+[Link]
Process

2.4.3 PROCESS STEPS

Step Role Description Enablers / Dev ID Policies / Guidelines

1 Reconciliation Compare balances with Bank FBL1N Bank GL account balance
Officer GL Account and Bank should equal bank statement
Statement balance.
2 Reconciliation Errors Exist in posting Area
Officer 1 (GL)

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 19 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

Step Role Description Enablers / Dev ID Policies / Guidelines

3 Reconciliation Analyse and resolve the FEBA Where there are differences
Officer errors in posting area 1 (GL) between the bank GL account
and the bank statement, these
need to be investigated and
resolved.
4 Reconciliation Errors Exist in posting Area FEBA
Officer 2 (Sub Ledger)
5 Reconciliation Analyse and resolve the FEBA Where there are outstanding
Officer errors in posting area 2 (Sub- items for FEBA processing
ledger) these items need to be
investigated and resolved.
6 Batch User Run automatic Clearing F.13 Clear the open items in the
processes Bank Clearing and customer
accounts.
7 AR Officer Review Incoming payment FAGLB03; FD10N; The open items can be
Bank Clearing and customer FAGLL03; FBL5N analysed further to establish
accounts what needs to be done to clear
the items.
These sub processes will be
covered in the AR BBD.
8 AR Officer Manual Clearing if Required F-03; F-32; Where transactions have been
corrected, or open items can
not be cleared using the auto
clearing processes, these
items need to be cleared
manually.
9 AP Officer Review Outgoing payment F-03; FAGLB03; The open items can be
Bank Clearing accounts FAGLL03 analysed further to establish
what needs to be done to clear
the items.

These sub processes will be

covered in the AR BBD.
10 AP Officer Manual Clearing if Required F-03; Where transactions have been
corrected, or open items can
not be cleared using the auto
clearing processes, these
items need to be cleared
manually.

2.4.4 LOCATION
This function will be performed at Corporate Office

2.4.5 FREQUENCY
This function will be performed daily. Additional checks will be conducted at month end.

2.4.6 DURATION
The amount of time taken for this process will depend on the quantity of data needing to be processed, the staff doing
the processing and the accuracy of bank data.

2.4.7 USER INTERFACE

None

2.4.8 PROCESS VARIATIONS

There are no scenario variations for the bank reconciliation process.

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 20 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 21 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.5 PROCESS DESIGN – BANK FILES FOR CUSTOMER AND VENDOR PAYMENTS

2.5.1 DESCRIPTION
The following DME Bank files are required for customer’s payments.

1. Direct Debit File

2. Amex Files
3. Aspire File

The following files are required for vendor’s payment.

1. Electronic Fund Transfer (EFT)File (DME file)

2. Cheque

For the process details of the above mentioned files please refer to Accounts Payable BBD for Vendor payments and
Accounts Receivable BBD for Customer payments.

Name of Business Blueprint Document Hyperlink

Accounts Receivable BBD
Accounts Payable BBD

2.5.2 PROCESS FLOW

PROCESS FLOW DIAGRAM

The flowchart below details the Bank Files for customer and vendor payments.

Figure 5: Bank Files for customer and vendor payments

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 22 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

Visio Document Hyperlink

Name
Bank Files for
customer and
vendor payments [Link]
DME+Bank+Interface+[Link]

2.5.3 PROCESS STEPS

Step Role Description Enablers / Dev ID Policies / Guidelines

1 AR Credit Generate Direct Debit Files As per file specifications from
Controller NAB
2 AR Credit Generate Amex Files As per file specifications from
Controller Amex
3 AR Credit Generate Aspire Files As per file specifications from
Controller Westpac
4 AP Credit Generate EFT File As per file specifications from
Controller NAB
5 AP Credit Generate Cheque Forms As per file specifications from
Controller NAB

2.5.4 LOCATION
This function will be performed at Corporate Office

2.5.5 FREQUENCY
This function will performed on a daily basis

2.5.6 DURATION
The files will be created immediately on request.

2.5.7 USER INTERFACE

None

2.5.8 PROCESS VARIATIONS

There are no scenario variations for House Bank creation.

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 23 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

2.6 SYSTEM DESIGN

2.6.1 SYSTEM CONFIGURATION

DEFINE HOUSE BANKS

Company House Bank Bank Accoun Description Bank Account G/L Account Currency
Code Bank Count Key t ID Number
ry

DOCUMENT TYPES (SAP TRANSACTION OBA7)

Document Types are used in SAP to identify specific types of transaction. Every transaction processed in SAP is
associated with a Document Type. The document types will default in most cases depending on the transaction. In most
cases the document type is transparent to the user when entering the G/L posting, but can be useful when analysing and
reporting data. For example, all Bank reconciliation postings entered on-line in SAP will have a document type “SR”.
This can then be used as selection parameter in reports to list only Bank Reconciliation postings.

The following table lists the document types defined for XXXX Bank processing.
Document Description / Purpose Reversal Description
Type Document
Type
SR Bank Reconciliation SB G/L Account Posting
SB G/L Account Posting AB Accounting Document

MAKE GLOBAL SETTINGS FOR ELECTRONIC BANK STATEMENT

In this activity, make the global settings for the account statement. There are four main steps to be carried out:

CREATE ACCOUNT SYMBOLS

Specify G/L accounts (such as bank, cash receipt, outgoing cheques to which postings are to be made from account
statement.
Account Symbols
Account Symbol Text

ASSIGN ACCOUNTS TO ACCOUNT SYMBOLS

Define postings to be triggered by possible transactions in the account statement (such as bank transfer, debit memo).
Assign G/L Accounts to Account Symbols
Account Symbol Acct Mod Curr G/L acct Acct Symbol Description
BANK + +
BANK FEE + +
BR CREDITS AU + +
BR CREDITS NZ + +
CHEQUE PAYMENTS + +
CHEQUE POSTINGS + +

CREATE KEYS FOR POSTING RULES

Assign posting rules to possible transactions in account statement file. A list of assignments where one external

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 24 of 29

 Australian Pharmaceutical Industries
Business Blueprint | Bank Accounting

transaction code is assigned to one posting rule is called a transaction type.

Posting Rules
Posting Rule Text

CREATE TRANSACTION TYPES

Create the names and descriptions of the various transaction types required. House banks that use identical lists of
business transaction codes (external transactions) can be assigned to the same transaction type later.

Transaction Type Description

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 25 of 29

6.
7.

2.6.2 WORKFLOW OBJECTS

<Vendor: Specify any workflows that will need to be developed for the solution design. ID is the unique Development Register number.
Note: only valid roles from the Business Process Master List may be used>

ID Name Description Trigger Roles

2.6.3 REPORT OBJECTS

<Vendor: Specify any SAP-standard, BI or custom reports that will need to be developed for the solution design. ID is the unique Development Register number>

ID Name Description Audience Key Criteria Fields Key Output Fields Frequency Type
[Daily, Weekly, Monthly, Yearly, [SAP Standard / BI / Custom]
Adhoc]
1 S_P99_41000166 Bank Master Data Report SAP Standard

2.6.4 INTERFACE OBJECTS

<Vendor: Specify any interfaces between SAP and other applications that will need to be developed for the solution design. ID is the unique Development Register number
Note: please include any legacy system changes required to support the interface>

ID Name Description Source Target Interface Volume / Key Fields

Application Application Method Frequency
[Daily, Weekly, Monthly, Yearly,
Adhoc]
1 Westpac Bank Multicash format
Statement Upload
2 NAB Bank BAI2 Format
Statement Upload
3 Amex DME File
4 Aspire DME File As per file specifications
from Westpac
5 Direct Debit
DME File
6 EFT DME File As per file specifications
from NAB

2.6.5 CONVERSION OBJECTS

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 26 of 29

 1. Australian Pharmaceutical Industries 2.

3. Business Blueprint | Bank Accounting

5.
<Vendor: Specify any data conversions/migrations that will need to be developed for the solution design. ID is the unique Development Register number>

ID Name Description Data Data Volume Cleansing Extraction Transform Load Details
Source Owner Details Details Details

2.6.6 ENHANCEMENT OBJECTS

<Vendor: Specify any custom enhancements, and their justification, that will need to be developed for the solution design. ID is the unique Development Register number>

ID Name Description Justification Effort

H/M/L

2.6.7 FORM OBJECTS

<vendor: Specify any forms that will need to be developed for the solution design. ID is the unique Development Register number>

ID Name Description Audience Trigger Output Types Volume / Key Output Fields
Frequency
[Daily, Weekly,
Monthly, Yearly,
Adhoc]
Cheque Form As per file specifications from
NAB

2.6.8 AUTHORISATIONS
<Vendor: Specify authorisation requirements, such as segregation of duties, for any of the roles in the business process.
Note: only valid roles from the Business Process Master List may be used>

ID Transaction Description Roles

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 27 of 29

 1. Australian Pharmaceutical Industries 2.

3. Business Blueprint | Bank Accounting

5.
2.6.9 LEGACY SYSTEM IMPACTS
<API: Indicate impacts on Legacy systems and their interfaces. These can be process changes, development required, job schedule changes, alterations in user access, historical data
archiving etc.>

ID Legacy System Impact Description Effort

H/M/L
1 Basware Purchase Order sequence numbering must be updated to allow alignment with SAP Low

2.6.10 DESIGN DEPENDENCIES

<Vendor: Specify any dependencies that the solution design has on other business processes. This ensures that all end-to-end process integration is considered.
ID Process Name Dependency

2.6.11 CHANGE IMPACTS

<API: Specify the business change impacts and benefit that will be introduced by the solution design. The change actions must also be listed that will manage the change imposed by
the impacts. Note this also includes legacy system impacts>

ID Impact Description Roles Users Change Actions

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 28 of 29

 1. Australian Pharmaceutical Industries 2.

3. Business Blueprint | Bank Accounting

5.

3 APPENDIX FURTHER INFORMATION

<API, Vendor: Attach any further information, tables, figures, diagrams required>

[Link] V0.1 API Commercial in Confidence 6-Sep-2022 Page 29 of 29