AP RCM Liability Generating In Back Period If Two Period Are Opened (Doc ID 2151245.1)

Last updated on JUNE 26, 2016

Applies to:

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

Symptoms

On : 12.2.4 version, Service Tax Setups - General

ACTUAL BEHAVIOR
---------------
Reverse charge liability generating in back period if two period simultaneous open.

When we are booking backdated invoices, after 3 month, normal invoice accounting is happening as per requirement.

But after 3 month when it is creating reverse charge liability, it is appearing correctly on 10th May as transaction date.

When system is generating accounting entry for transferring liability from interim liability to liability date is of 1-april-16.

In ideal scenario this should hit GL on the date when it is Hitting repository(Point of Taxation Date).

EXPECTED BEHAVIOR
-----------------------
Expected to get posted into the open period.

STEPS
-----------------------
Issue is observed for transactions which are back dated and where
two open periods are opened.
1. Create a Backdated 3 months old invoice
where reversal for invoice is setup as 3 months.
2. Validate , Account.
3. On transferring liability
from interim liability, system is not inserting
on POT date , rather getting posted in old period.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot post the entries into the current period.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms