My Oracle Support Banner

EAP: Why is the Payment Posting Process Copying the Chartfields From Expense Distribution When Creating Payment Escheatment Accounting Entries? (Doc ID 2906244.1)

Last updated on OCTOBER 31, 2022

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


When payments are canceled in accounts payable with a reason of Escheatment the payment posting process is not creating correct accounting entries.

The expectation was the process should use the chartfields the same as the ones used for Cash Payment Post entries(CAC/CAS).

Currently, the system uses the chartfield values from Expense distribution accounting entries(APA). Which is not correct as per the below references:

Payment Escheatment: “Note: Escheatment liability entries will reverse all chartfields from cash entry, except ACCOUNT and ALTACCT. Intra Unit entries will not be generated as chartfield values will be inherited from cash entries. Inter Unit entries will be created accordingly.”

Why is the payment posting process copying the chartfields from expense distribution when creating accounting payment escheatment accounting entries?


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.