R12.2:27037971:CFDI For Payments Is at Invoice Level And It Should Be at Payment Level.

(Doc ID 2323715.1)

Last updated on NOVEMBER 01, 2017

Applies to:

Oracle Financials for the Americas - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Latin America Payables

CFDI for payments is at the invoice level.

CFDI for payments should be at the payment level.

The issue can be reproduced at will with the following steps:

1. Responsibility: Oracle Payables - Mexico localization
2. Path: Invoices -> Entry -> Invoices
3. Query an invoice
4. Go to the Scheduled Payments
5. Open the global flexfield

CFDI for payments is at the invoice level when it should be at the payment level.

The SAT (Mexico's taxing authority) is requiring companies to track the CFDI that is received from the supplier that is paid once they receive payment.
This requirement takes effect December 1, 2017. The fields to capture this information is currently at the Invoice Level on the Scheduled Payments tab.
The fields need to be at the Payment Header level.

In its current state, users will have to make thousands of entries each month. As an example, one payment can cover 20 invoices.
The user will have to query each invoice separately in order to navigate to the Scheduled Payments tab in order to enter the unique CFDI for the payment.
The Invoice Workbench does not allow queries based on payment number. If the company makes 500 payments in the month and they pay an average of 10 invoices
with each payment, the users are querying 5000 invoices, navigating to the Scheduled Payments tab, scrolling to the Global DFF, clicking into the field,
selecting the context field, entering the payment CFDI, and pressing (or clicking) the OK button multiple times.
They are clicking multiple times because the popup form will not close after the first click on the OK button.
If the fields were at the Payment Header Level, then the user only has to make 500 queries and entries of the CFDI number.
In its current state, the amount of extra work that is being put on the users is tremendous, and would cause a hardship for AP department processing.

Note that the unique payment CFDI is not know until after the supplier receives payment and is not know at the time of invoice entry.


The issue has the following business impact:
In its current state, the amount of extra work that is being put on the users is tremendous, and would cause a hardship for AP department processing.

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