(FIN04) Finance - Cash & Banking v1.0

Bank Accounting
PLI Business Transformation – Aligning Systems and Processes
SI COPY
30 November 2016
Design Confirmation Workshop
April 2017
© 2017 PETROLIAM NASIONAL BERHAD (PETRONAS)
All rights reserved. No part of this document may be

reproduced, stored in a retrieval system or transmitted in any
form or by any means (electronic, mechanical, photocopying,
recording or otherwise) without the permission of the copyright
owner.
©Petroliam Nasional Berhad (PETRONAS) 2017 1
Safety First: The Safe Way Is The Best Way
Where are We are on Level 26, Integra Tower

we? Syntium 1
Presenters Josephine Lim

for the Day
Proceed to the front doors on both sides of the

Emergency
room and follow the instructions of floor safety
Exits
manager
Floor Safety
Managers

Session Ground Rules
Silent your phones during the sessions

and limit laptop usage to allocated breaks
only
Be punctual at all times
LISTEN to be heard
Speak up so that everyone can hear you

Objectives of Design Confirmation Workshop (DCW) in
the next 2 weeks
DCW is meant to…

• Design Adoption - Understand the PLI global design by business
functions and how it can be adopted globally
• Identify global gaps from the global solution based on business needs
• Assess the impacts of the gaps identified in terms of people, process,

data, technology and policy
DCW is not…
• DCW is not a training session – the intent is to understand the global
design. System training will be provided closer to deployment dates
• DCW is not a local requirement gathering session – remember that

we are here to confirm global design. Local requirements can be
highlighted but will be discussed separately by region based on the
agreed global design

Remember why you are here – PLI Global Design
Role Expectations
All Attendees Knowledgeable in respective functions, actively
participate in sessions and empowered to make decisions
GBPO Accountable for overall global design steer and sign off
AGBPO To inherit GBPO accountabilities when deputized
Functional To provide functional expertise/knowledge in assigned

Specialists area to achieve PLI’s global system design
Regional Business To understand and provide feedback on the global design

Representative from a regional perspective and highlight localization
requirements (legal/statutory)

How to get the most from your DCW session
Focus on our #1 objective - we are working

towards standardizing & unifying PLI businesses
globally
Listen with an open mind - consider changes

to your current way of working for the greater
good of PLI
Conduct constructive discussions - respect

each other’s opinions & keep conversations above
the line

3
Integrated Finance Operations Procurement
INT01: DCW Kickoff FIN01: Finance - OPS01: SCM PRO01: SCM
and Global General Ledger & Operations - Plant Procurement -
Enterprise Interco Maintenance & Prod Enterprise
APR Structure AM PM Master Data PM Structure PM
DCW Schedule – Week 1
4
Finance Finance Operations Procurement
FIN01: Finance - FIN08: Controlling OPS02: SCM PRO02 & PRO03:
General Ledger & - CCA/PCA Operations - Plant SCM Procurement -
Interco Work Management Master Data
APR AM PM
5
Integrated Operations Operations Procurement
INT03: Business OPS04: SCM OPS05: SCM PRO04: SCM
Partner (Vendor & Operations - Operations - Procurement -
Customer Master) Production Quality Direct Procurement
APR AM Execution AM Management PM PM
6
Finance Operations Operations Procurement
FIN02: Finance - OPS06: SCM OPS03: SCM PRO05: SCM
Accounts Operations - PP/QM Operations - Prod Procurement -
Receivable Reporting Planning, Indirect
APR AM Scheduling PM Procurement
7
Finance Integrated Operations Procurement
FIN03: Finance - INT06: Finance & DAT03: SCM PRO06: SCM
Accounts Payable SCM Procurement - Operations - Data Procurement -
Invoice Verification Migration Strategy Vendor Evaluation
APR AM PM AM AM

10
Commercial Finance Integrated Integrated
COM01: FIN06: Finance - INT07: SCM INT04: SCM Proc -
Commercial - Asset Accounting Procurement - Inventory & W/hse
Enterprise Requisition Mgmt (Raw Mat/ S-
APR Structure PM AM F, F) PM
DCW Schedule – Week 2
11
Commercial Integrated Finance Integrated
COM02: INT02: Commercial FIN04: Finance - INT05: SCM Proc -
Commercial - & Finance - Billing Cash & Banking Inventory & W/hse
Master Data (Spares/Generic/
APR AM PM Pckg) AM
12
Commercial Finance Procurement
COM03: FIN09: Controlling DAT04: SCM
Commercial - Sales - COPC / COPA Procurement - Data
Management &
APR Operations
Migration Strategy
PM
13
Commercial Finance Finance
COM04: FIN05: Finance - FIN07: Finance -
Commercial - Project Planning & Tax
Pricing & Rebate Control (WBS)
APR AM PM
14
Commercial Commercial Finance Finance
DAT01: COM05: FIN10: Finance - DAT02: Finance -
Commercial - Data Commercial & Period End Closing Data Migration
APR Migration Strategy
AM
Operations -
Logistics PM AM
Strategy
PM

Objectives of this Session:
FIN04 : Cash and Banking
1 Understand Cash and Bank accounting design in S4 HANA
2 Align proposed to be payment instruction process
3 Align proposed To-Be bank reconciliation process

Indicating your attendance
Verify sessions details – for each session, you’ll be provided

with an attendance acknowledgement sheet. Check the session
details
Indicate your attendance – fill in your

2 3
personal details and sign on the sheet
Record any localisation requirements

or global design feedbacj – should
you have any local requirements that
needs to be addressed after
understanding the global design or
feedback on the global design, please
note it down here

Business Impact Assessment (BIA)
WHAT IS THE BIA?
The BIA is used to identify key impacted areas (system & business processes)
which will then be used as input for tailored change management interventions
where needed
HOW ARE WE COLLECTING DATA FOR THE BIA?
I. For system changes – II. For business process &

the project team will role changes – input
leverage on the Global from participants on the
Design Template, the changes if applicable via
main outcome of the this BIA Questionnaire
DCWs
HOW YOU CAN CONTRIBUTE IN 10 MINS!
 Help us complete the BIA Questionnaire by clicking on the link sent to you via email Subject:
BIA Questionnaire or scan the QR code above
 It is accessible via mobile and desktop
Table of Content
• Bank Master Data
• Bank Determination
• Payment Instruction
• Bank Reconciliation
• Cash and Bank Reporting

Key Design Decision
Bank Accounting Process Overview

Master Data
1. Maintain 2. Maintain 3. Maintain
Bank Key House Bank ID Account ID
Payment Process
1. Bank 2. Payment 3. Petty Cash

Determination Instruction
Bank Reconciliation
1. Manual Bank 2. Electronic
Reconciliation Bank
Reconciliation
Bank Accounting Reporting

1. Bank
Statement
Report

Key Design Decision
Bank Key
• A bank key is used to store physical bank details like Bank name, street, city, branch,
SWIFT code.
• Bank key denotes the ID for each bank branch (i.e: sort code/IFSC). For MY, bank
key needs to be cleansed accordingly to FS2 guidelines.
• SWIFT code is mandatory for overseas transfer.
• Bank Key will be migrated to S4 HANA as part data migration object.

Key Design Decision
Bank Key
• Vendor bank details consists of bank key which defines which bank followed by the
vendor bank account no.

Key Design Decision
House Bank
• Bank used by legal entities to pay vendors and receive payment from
customers.
• When there is more than one bank account within the same bank, a
separate house bank is to be setup.
Proposed Coding: Coding Rationale:
Code Description Position Description
Stands for Bank Name

CIB01 CIMB Bank Behard 1-3
“CIB”
Running Number
4-5
“01”

Key Design Decision
Account ID
• Bank Account ID incorporates attributes of bank account. This ID refers to

bank account when entering specifications for the payment program and in
the GL master records.
• A separate account ID to be setup per currency for each individual house
bank.
Proposed Coding: Coding Rationale:
Position Description
Code Description
Stands for Currency
1-3
MYR01 MYR Account “MYR”
Running Number
USD01 USD Account 4-5
“01”

In discussion – not finalised
Key Design Decision
Bank Accounts
• There is a plan for PLISB and PBOM to be onboarded of IFSSC (Integrated Finance
Shared Service Center). Payment process – In-house account with IFSSC will be
covered under IFSSC design document.
• For Malaysia business to confirm if there is a plan to close current bank account in the
event of IFSSC onboarding.
• For Europe as part of Bank Account Rationalization (BAR) project the new Citibank
bank accounts and the approved local banks will be setup in S4 HANA. Additional
bank accounts may be added if the Credit Card Facility is synchronized (for all the
European entities) with a new banking partner. This is to be validated during
localization session.
• Attached is the list of house bank collected from business and to be setup in S4
HANA. Aside from pending items in point 2 and 3 above house bank information still
pending from China and Americas and will be collected during localization session.

Key Design Decision
Bank Sub-Accounts
• Each bank will have the 3 Bank GL accounts created

1471XXXX – Main Bank Account
1472XXXX – Incoming Clearing
1473XXXX – Outgoing Clearing
House Bank
GL clearing a/c for GL clearing a/c for

outgoing payment Incoming payment
Automatic Payment
Program
DR Vendor payables
CR Outgoing Clearing GL account
Bank Reconciliation Bank Reconciliation
DR Outgoing Clearing GL account DR Main Bank Account

CR Main Bank Account CR Incoming Bank Clearing GL account
OR
DR Main Bank Account
CR Customer

Key Design Decision

Master Data
Payment Process

Bank Reconciliation
1. Manual Bank 2. Electronic
Reconciliation Bank
Reconciliation
Bank Accounting Reporting

1. Bank
Statement
Report

Key Design Decision
Process Payment – Bank Determination
• House bank determination is to confirm the house bank to use per payment method.
• There are three ways to input payment bank details for payment transactions
 Bank details can be entered in vendor business partner master data
ILLUSTRATIVE

Key Design Decision
• Bank details can be entered in invoice transaction posting

ILLUSTRATIVE

Key Design Decision

 Payment bank details can be determined in ranking order setup in
automatic payment program.
 Details to be collected during localization session.
ILLUSTRATIVE
Payment Methods: Ranking order determines the ranking

of house banks to use for a particular
• 1 Payment by Cheque
payment method using the automatic
• E Payment by EFT
payment program.
• T Payment by TT

Key Design Confirmation – Payment Instructions
• For auto payment run (F110), there are 2 options payment instruction can happen:
1. After execution the payment, system will post payment entry in system.
Business will base on this payment posted and login to the bank website to provide
manual instruction to the bank to release the payment.
2. System will auto generate a ISO Pain 001.001 payment file in XML format to
the bank. This payment file serves as a payment instruction for bank to
release payment to vendor. It contains the payment details vendor name, vendor
bank details, payment amount and details of invoice paid etc.
The payment file generated by system can be host to host (H2H) or manual download
and upload:
 Host to Host (H2H) means: the payment file will be pushed

automatically to bank server, this requires the connection to establish from
PLI server to bank server
 Manual download: payment file generated from SAP, business will

download the payment file to local drive and manually upload the payment
file into bank website.

Key Design Confirmation – Payment Instruction by Regions
Europe:
• For Citibank payment /XML file. Whether it is H2H or manually download and upload to
the bank website?
• Non Citibank for Belgium, Poland, UK and Germany, the payment file is generating
directly from SAP, business will download and upload the payment instruction to bank
website.
• For the remaining of the Europe, there is no payment file generated from system,
business requires to manually login to the bank website to provide manual instruction.
• 80% of the payment is RIBA payment method. Citibank BAR project does not support this
mode of payment currently. So, what is the ultimate plan for this scenario?
Americas:
• For /XML payment file is manually download and upload to the bank website for both ACH
and WIRE.
• For Cheque payment, cheque is generated by system or manual written cheque?
• Specifically for Brazil, the boleto payment is included in the /XML file which contain boleto
number in every invoice. ©Petroliam Nasional Berhad (PETRONAS) 2017 25
Key Design Confirmation – Payment Instruction by Regions
Malaysia:
• The payment listing file is only applicable for local payment. Currently, business is
manually download the payment listing and login to CIMB bank to convert to file into
bank format, then manually send the payment file generated from bank website to CIMB
bank to process the payment.
• For payment through physical bank manual payment instruction process remain status
quo.
• This is still pending the final decision on IFSSC onboarding and will be covered under
IFSSC design document.
• For payment using cheque is remain status quo, manually write the cheque and send to
vendors.
India and China:
• For India, only cheque payment currently. A hardcopy cheque book is used to issuing
cheque for any outgoing payment made.
• For China, payment process is manual. Business requires to sent manual instruction to
the bank to instruct on the payment made.
Key Design Confirmation – Payment Methods by Regions
• The table below summary the different types of payment method for each regions:
Country Manual Auto Payment File Payment Remark

Listing
H2H Download
Malaysia Yes Yes No No Yes
China Yes Yes No No No China will check with local bank if
electronic payment file is
supported by the local bank.
India Yes Yes No No No
Brazil Yes Yes No Yes Yes Collect the sample of payment file
USA Yes Yes No Yes Yes Collect the sample of payment file
Argentina Yes Yes No - - Will only can confirm during
localization due to Argentina is in
progress of SAP implementation.
Italy Yes Yes No Yes Yes EU is under testing electronic
payment file using Citibank. Once
Spain Yes Yes No Yes Yes Citibank project goes life, the
Belgium Yes Yes No Yes No same payment file will be
replicated in S4 Hana.
Portugal Yes Yes No Yes Yes - For non Citibank, payment listing
is being use, except Belgium,
France Yes Yes No Yes Yes
Poland, UK and Germany is the
Germany Yes Yes No Yes No electronic payment file generated
from SAP. Sample of the payment
Poland Yes Yes No Yes No file/ payment listing is required.
Great Britain Yes Yes No Yes No
Turkey Yes Yes No No No For Turkey, all the payments
handle manually.
Business Process Network
F110/F-53 V

Key Design Decision
Petty Cash - Malaysia
• Employee holding petty cash is setup as petty cash vendor.

• For petty cash reimbursement petty cash vendor will submit the petty cash
report, petty cash voucher, receipts as supporting documents.
• Petty cash expense is posted as vendor invoice (FB60):
DR Expense
DR Input Tax
CR Petty Cash Vendor
• Petty Cash Reimbursement is posted via vendor outgoing payment (F-

53/F110):
DR Petty Cash Vendor

CR Bank Outgoing Clearing

Key Design Decision
Petty Cash – non MY
• Petty cash expense and reimbursement is posted as journal entry (FB50):

Petty Cash Expense
DR Expense
DR Input Tax
CR Petty Cash
Petty Cash Reimbursement

DR Petty Cash
CR Bank Outgoing Clearing

Key Design Decision

Master Data
Payment Process

Bank Reconciliation
1. Manual Bank 2. Electronic Bank
Reconciliation Reconciliation
Bank accounting Reporting

1. Bank
Statement
Report

Business Process Maturity
Tcode: FF_5,
FF67
Tcode:
Tcode: FB50/F-03
FEBA_BANK_
STATEMENT

Key Design Decision
Bank Reconciliation
• Bank reconciliation process

 Electronic bank statement
Step 1 : Upload bank statement via FF_5
Step 2 : To re-process the unmatched items via FEBA_BANK_STATEMENT
Step 3 : Perform GL/AR clearing via F.13/F-03
 Manual bank statement

Step 1 : Manually enter bank statement item via FF67
Step 2 : Perform GL/AR clearing via F.13/F-03
 Journal Entry
Step 1 : Clear Customer open item F-32
Step 2 : Clear bank outgoing clearing F-03
Step 3 : Post bank charges/interest/fund transfer FB50
• Automatic GL Clearing F.13 will be setup as a daily background job to

perform clearing on incoming/outgoing clearing GL

Key Design Decision
Electronic Bank Statement
• The electronic document can be remitted by the bank in the following

formats SWIFT MT940, Multicash, BAI etc. This statement is used in SAP to
perform automatic reconciliation.
• For format not supported by SAP, manual bank statement approach will be
adopted.
• Business will download MT940 bank statement from the bank website and
upload into S4 HANA via FF_5. No host to host connection is required.
• Automatic matching and clearing is only possible when transaction type

and document search is matched.
• Any unmatched statement items need to be manually clear. (eg: Foreign

currency payment which include bank charges, customer receipts etc).

Key Design Decision
• Electronic bank statement (SWIFT MT940, Multicash, BAI) can be downloaded

from bank website or interface and store in SAP application server.
• Below is the SAP screen to post bank statement electronically.

Key Design Decision
• Below is the sample MT940 bank statement loaded into SAP

Key Design Decision
• Below is the sample MT940 bank statement loaded into SAP
Bank-specific code fo
business transaction

Key Design Decision
• Automatic posting can be configured base for bank specific business

transaction code in bank statement (eg: NTRF, NDDT, NINT, NCHG, NMSC
etc)
Tag Meaning
20 Transaction Reference Number
25 Alternate Account Number
28C Statement Number and/or Sequence Number
60F Opening Balance
61 Statement Line (One per Transaction)
86 Information to Account Holder
62F Closing Balance

Key Design Decision
Manual Bank Statement
• From the PDF/excel bank statement downloaded from banking website,

business can enter the bank statement items into S4 HANA via FF67.
• A pre-defined transaction and the corresponding accounting entries can be

setup for different business transaction.

Key Design Decision
Manual Bank Statement
DR Outgoing Clearing
CR Main Bank
DR Main Bank
CR Customer

Key Design Decision
Bank Reconciliation
Bank Reconciliation Approach MY CN IN
Electronic Bank Statement IFSSC – MT940

PMCCL - PDF/Excel
Manual Bank Statement PDF/Excel
PLSCL - PDF/Excel
Journal Entry
PDF/Excel
Malaysia
• IFSSC bank reconciliation will be covered under IFSSC design document
• For physical bank reconciliation bank statement reconciliation approach is dependent
on the IFSSC onboarding decision and discussion with CIMB
China/India
• Business to check with bank if bank is able to provide MT940 bank statement format
for auto bank reconciliation. Otherwise manual bank reconciliation approach will be
adopted. Transaction type to be collected during localization session.

Key Design Decision
Bank Reconciliation
Bank Reconciliation ES PT UK IT BE FR DE PL TR
Approach
Journal Entry
Manual Bank PDF/ PDF/ PDF/ PDF/ PDF/ PDF/
Statement Excel Excel Excel Excel Excel Excel
Citibank
Citibank
MT940
MT940 Citibank Citibank Citibank Citibank Citibank Citibank Citibank
Electronic Bank
MT940 MT940 MT940 MT940 MT940 MT940 MT940
Statement BNP-
SANTAN
MT940
DER
Europe:
• For Citibank BAR project design/approach will be adopted in S4 HANA. Electronic bank
business transaction code to be collected after project go live.
• For other banks which currently using electronic bank statement (ie: SANTANDER,
BNP) will remain status quo. Sample bank statement and business transaction code
and its corresponding accounting entry is to be collected during localization session.
• For other banks which currently using manual bank statement will remain status quo.
business transaction code and its corresponding accounting entry is to be collected
during localization session.
Key Design Decision
Bank Reconciliation
Bank Reconciliation Approach US BZ MX AR
Journal Entry
Manual Bank Statement PFD/Excel PFD/Excel PFD/Excel PFD/Excel

BANCO DO BRASIL S.A.
BANCO BRADESCO S.A.
Electronic Bank Statement BANCO ITAU S.A.
J.P. MORGAN
US/BZ/MX/AR:
• For banks which currently using electronic bank statement (ie: BANCO DO BRASIL
S.A., BANCO BRADESCO S.A. etc) will remain status quo. Sample bank statement
and business transaction code and its corresponding accounting entry is to be
collected during localization session.
• For other banks which currently using manual bank statement will remain status quo.
business transaction code and its corresponding accounting entry is to be collected
during localization session.

Key Design Decision

Master Data
Payment Process

Bank Reconciliation
1. Manual Bank 2. Electronic Bank
Reconciliation Reconciliation
Bank accounting Reporting

1. Bank
Statement
Report

Key Design Decision
Bank Statement Report

• For electronic bank statement loaded into S4 HANA bank statement report below will
be available in the system.
• Report has information on bank opening balance, total debit, total credit, details of
statement items and bank ending balance.

Requirement
No. Description Type Raised Comment

by
1. Payment/receipt are carried out in satellite system (Piteco) GAP - Elena To check
and bank statement is manually downloaded from Piteco Interface Alasia with bank
and accounting entry is manually posted in SAP (Italy) if payment
instruction
and
MT940
bank
statement
is feasible
2. Auto bank reconciliation posted automatically based on Fit Magdalena Same
customer document number stated in bank statement (Poland) approach
will be
adopted in
S4 HANA
3. China (PLSCL) requirement to post payment and incoming Fit BingBao PLSCL to
receipt directly to Main Bank GL and not posted to (China) adopt
outgoing/incoming clearing. global
design
4. China (PLSCL) bank statement not required to be loaded in Fit BingBao PLSCL to
the system. (China) adopt
global
design

Requirement

by
5. MY - Receive MT940 Bank Statement Interface Malaysia Pending
IFSSC
6. MY - Send XML payment file Interface Malaysia onboardin
g decision
and
7. For incoming receipt post to customer base on virtual Enhance Malaysia discussion
account mapping table ment with CIMB
8. For overnight sweeping change bank statement posting Enhance Malaysia

rule to NAFT ment
9. For short term investment change bank statement posting Enhance Malaysia
rule to NSTI ment
10. For service charge change bank statement posting rule to Enhance Malaysia
NCHG ment
11. For GST changes change bank statement posting rule to Enhance Malaysia
NGST ment

Requirement

by
12. Accounting Interface from Treasury need to be interfaced Interface Malaysia Pending
into new SAP platform (S4 HANA) discussion
between
PLI Group
Treasury
and GTD
Attached discussion points recognized during DCW session

Thank You
Please spend 10 minutes to submit the Business
Impact Assessment and Session Feedback Form
Scan QR code below or visit http://goo.gl/iuhQfP

Appendix
• Treasury process in terms of in house cash, cash pooling, cash flow

forecast, loan management, working capital management, manage bank
cost remain with Group Treasury (GTD). Process remain status quo.







Applicable to Malaysia
only:
- Group Treasury will
hedge on behalf with
physical bank
- Group treasury will
inform the rate and
contract to PLISB
- Base on the rate
business will perform
manual outgoing
payment in SAP
Tcode: F-53
- Business to confirm
payment process with
the bank

• MYR Placement with GTD (Accounting interface from GTD) ---- only applicable to Malaysia
Start date Posting:
DR 14751000 Investment – Short Term – Deposit - Local
CR 14708000 IFSSC – Payment Req Clearing
DR 14708000 IFSSC – Payment Req Clearing

CR 1473510 MYR Investment Bank
Maturity date posting:

DR 14725104 MYR Investment Bank
CR 14751000 Investment – Short Term- Deposit – Local
CR 27051100 Fund Investment – Local-Interest Income-Deposit
• USD Placement with Bank (posted via bank statement)

Start Date posting:
DR Investment – Short Term Deposit - Foreign
CR Main Bank
Maturity date posting:

DR Main Bank
CR Invest – Short Term Deposit – Foreign
DR Main Bank
CR Fund Investment – Foreign-Interest Income-Deposit

(FIN04) Finance - Cash & Banking v1.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

(FIN04) Finance - Cash & Banking v1.0

Uploaded by

Copyright:

Available Formats

Bank Accounting

PLI Business Transformation – Aligning Systems and Processes

Design Confirmation Workshop

© 2017 PETROLIAM NASIONAL BERHAD (PETRONAS)

All rights reserved. No part of this document may be

Where are We are on Level 26, Integra Tower

Presenters Josephine Lim

Proceed to the front doors on both sides of the

©Petroliam Nasional Berhad (PETRONAS) 2017 2

Silent your phones during the sessions

Be punctual at all times

Speak up so that everyone can hear you

©Petroliam Nasional Berhad (PETRONAS) 2017 3

DCW is meant to…

• Assess the impacts of the gaps identified in terms of people, process,

• DCW is not a local requirement gathering session – remember that

©Petroliam Nasional Berhad (PETRONAS) 2017 4

AGBPO To inherit GBPO accountabilities when deputized

Functional To provide functional expertise/knowledge in assigned

Regional Business To understand and provide feedback on the global design

©Petroliam Nasional Berhad (PETRONAS) 2017 5

Focus on our #1 objective - we are working

Listen with an open mind - consider changes

Conduct constructive discussions - respect

©Petroliam Nasional Berhad (PETRONAS) 2017 6

©Petroliam Nasional Berhad (PETRONAS) 2017 7

©Petroliam Nasional Berhad (PETRONAS) 2017 8

1 Understand Cash and Bank accounting design in S4 HANA

2 Align proposed to be payment instruction process

3 Align proposed To-Be bank reconciliation process

©Petroliam Nasional Berhad (PETRONAS) 2017 9

Verify sessions details – for each session, you’ll be provided

Indicate your attendance – fill in your

Record any localisation requirements

©Petroliam Nasional Berhad (PETRONAS) 2017 10

WHAT IS THE BIA?

HOW ARE WE COLLECTING DATA FOR THE BIA?

I. For system changes – II. For business process &

HOW YOU CAN CONTRIBUTE IN 10 MINS!

• Bank Master Data

• Cash and Bank Reporting

©Petroliam Nasional Berhad (PETRONAS) 2017 12

Bank Accounting Process Overview

1. Bank 2. Payment 3. Petty Cash

Bank Accounting Reporting

©Petroliam Nasional Berhad (PETRONAS) 2017 13

• SWIFT code is mandatory for overseas transfer.

• Bank Key will be migrated to S4 HANA as part data migration object.

©Petroliam Nasional Berhad (PETRONAS) 2017 14

©Petroliam Nasional Berhad (PETRONAS) 2017 15

Proposed Coding: Coding Rationale:

Code Description Position Description

Stands for Bank Name

©Petroliam Nasional Berhad (PETRONAS) 2017 16

• Bank Account ID incorporates attributes of bank account. This ID refers to

Proposed Coding: Coding Rationale:

©Petroliam Nasional Berhad (PETRONAS) 2017 17

Key Design Decision

©Petroliam Nasional Berhad (PETRONAS) 2017 18

• Each bank will have the 3 Bank GL accounts created

GL clearing a/c for GL clearing a/c for

Bank Reconciliation Bank Reconciliation