Autoreconciliation of Receipts and Payments Created in Period (n+1) Can Be Reconciled With Receipts and Payments Created in Period (n)
(Doc ID 1525417.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Cash Management - Version 12.1.3 and later
Information in this document applies to any platform.
Auto Reconciliation is behaving differently to Manual Reconciliation.
There is a bug in the auto reconciliation program allowing reconciliation GL dates to be older than transaction GL dates.
It is observed that the Bank Statement GL Date in the Statement Header is always updated to whatever date the User enters as the GL Date Parameter in
the Autoreconciliation Request.
Manual reconciliation is not allowing reconciliation of any transaction, Receipt or Payment, with reconciliation GL_DATE earlier than the transaction GL_DATE:
The user is shown messages such as:
i. The clearing/reconciliation GL date cannot be earlier than the unclearing/unreconciliation GL date of this receipt.
ii. The cleared date cannot be earlier than the original GL date of the receipt.
iii. The Clearing/Reconciliation GL Date cannot be earlier than the Clearing/Unreconciliation GL Date of this Payment (UN_DATE = 05-OCT-2012)
Historically the reason given for this was that the Accounting had to be performed in Chronological Order.
It is not desirable to be able to Reconcile and account in August Period, then Unreconcile and account in September Period and then re-reconcile and account in August Period
To be able to do this would have a serious impact on the GL Reconciliation Report ( CEXRECRE.rdf )
Lets say some Trx was Reconciled and Accounted in Month (n).
It was found to be wrong on the first day of the next month and unreconciled and accounted in Month (n+1)
Then Autoreconciliation was run with the GL Date Parameter being the Last Day of Month (n) and accounted in Month (n).
This means the Payment Hits GL Cash Account Twice in Month (n) and only in the following month is the GL Cash Account Balance corrected.
The Auto Reconciliation Program is allowing to reconcile any transaction(receipt/payment) with reconciliation GL_DATE earlier than the unreconciliation date (assuming the period is open)
In CE, Auto Reconciliation should be in sync with manual Reconciliation and not allow to reconcile any transaction(receipt/payment) with reconciliation
GL_DATE earlier than the unreconciliation or transaction GL_DATE
The issue can be reproduced at will with the following steps, both for RECEIPTS and PAYMENTS:
Payments Test Case
1.Create a Bank Account and Create a Payment from that Account
2.Create a Bank Statement to which the Payment Can be Reconciled
Ensure the Statement Header GL Date is in an Open Period
3.Manually Reconcile the Line
Notice the GL Date is Defaulted from the Statement Header
4.Manually Unreconcile the Line
(Unless the User Changes it, the sysdate is defaulted here.
The GL Date on the statement header remains unchanged, despite this being
the latest GL Date used for Reconciliation or Unreconciliation)
5.Attempt to Manually Reconcile the Line
Receive Error message
The Clearing/Reconciliation GL Date cannot be earlier than the
Clearing/Unreconciliation GL Date of this Payment (UN_DATE = 05-OCT-2012)
The Sysdate is offered as the Default GL Date, however it can be updated to
any date in an Open AP and AR Period, which could be the same as the
Statement Header GL Date, or even one before that and before the Payment
Autoreconciliation is completed and
Payment GL Date = 13-AUG-2012
Payment Clearing GL Date = 31-AUG-2012
Payment Unclearing GL Date = 05-OCT-2012
Payment Clearing GL Date = 31-AUG-2012
Receipts Test Case
1. Go to Cash management--> Bank statements -->Bank statements and
Reconciliation query for any account number and date (GL period should be open)
2. Click on review button
3. Click on reconcile button.
4. Now take any one of the transactions and try to un-reconcile and reconcile
manually with GL date earlier than the receipt/transaction GL date.
5. Two errors
i. The clearing/reconciliation GL date cannot be earlier than the
unclearing/unreconcilation GL date of this receipt.
ii. The cleared date cannot be earlier than the original GL date of the
6. Run the auto reconciliation program for that unreconcilied
transaction with the GL date prior to the bank statement date
7. Now query and notice the receipt is reconciled.
NOTE: While doing manual reconciliation system is giving the error messages
and it is not allowing us to reconcile. But auto reconciliation program
reconciled that particular transaction without giving any error message.
<Bug 12913977>: AUTORECONCILIATION UPDATES ORIGINAL GL DATE TO SUBMISSION GL DATE ON BANK STATEM
Package : CE_AUTO_BANK_MATCH
Procedure MATCH_PROCESS calls procedure UPDATE_GL_DATE just before opening the line cursor to update the GL Date of the statement to the GL Date given as Autoreconciliation parameter.
Hence the GL Date is updated on every run of the Autoreconciliation program with the GL date provided as input to the program.
This is an expected functionality. This is done to signify the last GL date used to reconcile transactions from that bank statement.
There is no requirement for the Statement Header GL Date to be the same as the Bank Statement Date.
This has been verified as expected behaviour by Product management.
Before update there is a check to verify that the Period is Open in AP and AR.
There is no verification at this point as to any Prior Reconciliation or Unreconciliation GL Date.
<Bug 14390315>: MANUAL RECONCILIATION IS NOT DEFAULTING THE CURRENT DATE AS GL DATE
For manual reconciliation, the GL date entered on the bank statement header gets defaulted as the Reconciliation GL Date. This functionality is already existing and works for all the
transactions reconciled manually.
The GL date on the bank statement header, upon statement creation , defaults to the bank statement date and must be a date in an open period in Payables and Receivables.
This is not a bug in the application and system is working correctly for manual reconciliations.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document