Key steps:
I. Bank statements upload
II. Daily reconciliation
III. Month end recon
1. All bank statements with all statementl ines are loaded properly.
Input control:
We need to make sure that all bank statements are uploaded correctly to GFP.
Checking the “Bank Statement Interface”
In case the “missing statement” is available in the “Bank Statement Interface” there can be 2 reasons
for this:
1. An error on “Header”-level, usually a GL/AR period that is not open yet (you
can see the error by clicking on the “Errors”-button
To solve this, wait for the AR/GL period to be opened and then import the statement(s) by means of
Tools->Autoreconciliation. Use the “Import and Reconcile” option. In case you want to import multiple
dates or multiple accounts, you can leave the bank account number empty or modify the “Statement
Date From” and “Statement Date To”.
2. Line level – An error on “Line”-level, usually a missing “bank transaction code”.
Go to “Lines”, search for the line which has the “Error”-button with black text
and click on “Errors”. It will give you the error for this line.
Make a note of the transaction code (in this case 427C) and the bank account number (589613723)
and go to “XX YYY CE RDM Team Member”-responsibility.
Go to “Bank Transaction Codes” and select the bank account for which you would like to setup the
new transaction code.
After the bank transaction code has been setup, we can import the statement from the bank statement
interface by means of Tools->Autoreconciliation. Use the “Import and Reconcile” option. In case you
want to import multiple dates or multiple accounts, you can leave the bank account number empty or
modify the “Statement Date From” and “Statement Date To”.
Corrupt bank statement
Occasionally it might happen that a bank statement gets corrupted during load. In this case there are
no amounts in the bank statement for example.
You can then delete the statement lines by clicking on the red cross on the toolbar. After you deleted
all the lines, make sure to save the statement. Then close the lines screen and delete the statement
header by means of the red cross as well.
Bank statements are automatically uploaded through treasury server.
Occasionaly statement can be stuck on the interface due to several reason eg: transaction codes
set up missing.
Access for transaction codes set up: CE RDM teammember
Closing checklist file: excel file also – to be consider for implementing
A. Statement Number
statement number must be in sequence -all statements is loaded
B. Opening balance -Closing balance
closing balance must be equal to opening balance of the next day.
-It shows if there is any descrepency any statement line is missing.
2. Daily reconciliation-
Once you have loaded detailed bank statement information into Cash
Management, you must reconcile that with your AP transactions.
Cash Management provides two methods of reconciliation:
o Automatic- Bank statement details are automatically matched and
reconciled with AP transactions.
o Manual- This method requires you to manually match bank statement
details with system transactions.
Manual payments
Returned payment
payments pending for more than five days.
Bank charge ( temporarily ,after AR is implemented will be
automateded)
Fundings – JE Fundings _ will be JE ,since no cash pooling is in
place
Month end reconciliation
Instead on f manual one - one matching report based reconciliation is in place.
Timing is crucial since Oracle can pool only as is reports.
Closing activities and timing to be discussed
Report must run after the closure of the given subledger periods (AP/AR) and before
opening the next subledger ( AP/AR) period..
Standard report in Oracle Cash Mangment
Run - Single request :
Choose the bellow highlighted report.
1. BT bank statement details report
i. List all those items when you reconiled but with different amount.
BT Bank Statement Details Report will show you the partially reconciled items. The
statement line amount is not equal to the reconciled items therefore it is only partially
reconciled.
This is a key element since TAR report not showing the partially reconciled items.
This report must be run before TAR reports running at month end closing.
2. BT TAR report
It is importan to use the one starts with BT
Upcoming window to set the parameters
Show Payable documents: if it is set as, Yes and all other fields are blank the report will
bring only the available payments.
Among the avialble payments you will see all payments that were done in AP SL.
Avaialble paymentes causing differences on cash clearing account, so this parameter
to be used for reconciling 9527xx.
Exclude Payable/Receipts: If the filed Yes, than it will exclude all available payments
and remitted receipts ,so theoretically will bring only the items that cause bank
difference.
Statement line: you can see all unreconciled statement line causing difference
This is to be used for Month end bank reconciliation.
The Bank account number also can be defined, but if it is not inserted it will run for all
bank accounts within the given GFR. So with one report you can have all the
information needed.
Available receipt: the accounting of the misc. Receipts are generated when receipts are created.
o Any availbale misc. receipts will casue GL differences.
Available payments: Normally the accounting on bank GL accounts for payments are generated at
the time of reconiliation. Among the avialble payments you will see all payments that were done in
AP SL. Avaialble paymentes causing differencies on cash in transit account.
Voided: setup to be changed ( should not appear on TAR) but no effect on the bank account
Journal line: shows all the manually inserted [Link] journals always cause bank difference
Statement line: you can see all unreconciled statement line Unresolved bank lines cause GL differnce
