Last updated on MARCH 27, 2017
Applies to:Oracle Receivables - Version 12 to 12.0.6 [Release 12.0]
Information in this document applies to any platform.
In R12, We have two customer accounts defined for customer 'XXX' - Account Number '1' and '2'.
The bank account is created with the Bill To Site having account number '1'.
There are invoices in the system for account number '1'.
There are no account relationships defined between account '1' and '2'.
In AR System Options - Allow Payment for unrelated invoices has been set to 'No' - Unchecked.
And when the Lockbox file is processed, the we expect the Receipt to be created for Account '1'.
Now when processing lockbox file which has payments with Bank Account that is associated with Account '1', the Lockbox process creates Receipt with Account Number '2'. And since there are no invoices in Account Number '2', the receipts are created with claim investigations.
This is incorrect. Although the Bank account is defined for account '1' (and there is no Bank Account associated with '2'), the receipts are incorrectly created under account '2'.
- '1' and '2' are 2 accounts under same party
- This issue happens only in such case. It does not happen when there is one account under one party.
Symtom#1: When attempting to run Lockbox for customer which has MICR numbers associated, the following error occurs:
Error MICR and customer number do not refer to the same customer.
Symptom#2: When there are multiple customer accounts under one party, Lockbox is identifying Incorrect customer account using the MICR Number.
Create a party.
Create two customer accounts under the same party.
Create a bank account.
Assign the bank account to the customer with min customer id from above
Import the Lockbox with MICR number only. No customer information.
Lockbox will identify wrong customer, the customer with max customer id.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms