Which is the final step in processing a payment batch?

In Oracle E-Business Suite R12 Payables, the standard payment process request (traditionally referred to as a payment batch) lifecycle consists of selecting invoices, building payments, formatting payments, and finally, confirming the payments. Confirming the payment batch is the definitive final step within the batch processing itself. During this confirmation step, Oracle Payables assigns final payment numbers, updates the associated invoice statuses to 'Paid', and records the payment completion in the system. Subsequent actions, such as creating accounting entries or transferring data to the General Ledger, are separate downstream concurrent processes and are not considered steps within the payment batch lifecycle itself.

A. Cancel the payment batch: Canceling is an exception-handling action used to abort a batch before completion, not a standard final processing step.
C. Validate the payment batch: Document validation occurs much earlier in the process (during the build phase) to ensure invoices meet payment requirements before formatting.
D. Run the create accounting process: Create Accounting is a separate Subledger Accounting (SLA) concurrent request executed only after the payment batch is fully processed and confirmed.
E. Transfer the batch to General Ledger: Transferring to the GL is a sub-process of the accounting cycle, occurring entirely outside and after the payment batch processing is finished.

1. Oracle Corporation. (2010). Oracle Payables User's Guide, Release 12.1 (Part No. E13415-06). Chapter 5: Payables Payment Process, Section: "Confirming Payments" (pp. 5-23 to 5-25).

2. Oracle Corporation. (2010). Oracle Payments Implementation Guide, Release 12.1 (Part No. E12893-04). Chapter 4: Payment Processing, Section: "Payment Process Request Flow" (pp. 4-2 to 4-5).