My Oracle Support Banner

GST : AR Credit memo though rejected ,its loaded GST taxes are hitting GL_Interface , Jai_tax_journal_entries tables resulting in incorrect accounting (Doc ID 2450575.1)

Last updated on JULY 28, 2020

Applies to:

Oracle Financials for India - Version 12.1.1 and later
Information in this document applies to any platform.


Reported Issue

When AR record is loaded via interface or webadi and if Auto invoice import rejects the record from importing find that Taxes which are loaded on the transaction are imported into GL Interface and jai_tax_journal_entries.

Steps for Replication

1. Load Credit memo data into ra_customer_trx_all table.
2. For the sake of testing / validation , credit memo amount is with positive sign.
3. Apply taxes on the Credit memo either through OFI tax interface form
    loading into jai_interface_lines_All table.
4. Run the Auto Invoice import.
5. Credit memo is NOT interface as credit memo is created with positive sign.

Error message as per Autoinvoice Import Error log is

Errors: 1) The document created must have a non-positive total amount because the creation sign for your transaction type is Negative

6. Equally the applied tax is appearing in GL Interface and jai_tax_journal_entries table.
7. Now, when the credit memo sign is corrected and re-run again , now this is causing duplicate tax entries
    because of step 6 orphan records for tax appearing in.
8. It is leading to incorrect tax accounting .

Expected Behavior

Autoinvoice import program has rejected the record owing to sign issue for credit memo where it is with different sign.
For such cases , the tax shouldn't be allowed as it turns these are orphan records.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.