Payment Data

The payment data tables store payment information that you entered directly online or through the payment interface. Payments are processed when you:

• Apply them through a payment worksheet or automatically with Payment Predictor.

• Journal them directly to the general ledger.

The end result of the payment application process (whether it occurs online or during background processing) is the transformation of each payment into a group and its components. The system restates the payment data in pending item data format for submission to the Receivables Update process. The system stores the pending item data in the pending item tables.

After you post the group and its components and distribute it to your general ledger, the posted data tables contain all the information necessary to reference payment information for customer questions. For example, you can review the payment application on the Item Activity From A Payment page. The item activity table stores the payment ID.

When all payments in a deposit have been completely posted, you may want to retain the original entered format of the payment data so you can use the inquiry pages to view totals and a summary of the status of deposits and payments received.

You must keep deposit and payment information, in addition to the related group and pending items to unpost a payment. If you archive a deposit and its payments or the associated pending item data, you cannot unpost any of the payments within the deposit.

For directly journaled payments, the accounting entries in the PS_PAYMENT_MISC_DST table must remain in PeopleSoft Receivables until the Journal Generator Application Engine process (FS_JGEN) processes them.

A suggested approach for archiving payment data is to select deposits that have been completely posted and processed by the Journal Generator process and whose accounting date matches the archive criteria.

When all relevant conditions for a given deposit have been met, remove the data in all eight payment tables.