Settings That Affect Printed Payment Files Statuses

The application processes printed payment files. Printed payment files are printed onto checks or promissory notes. As a printed payment file is processed, the payment file status changes, depending on the actions performed by the source product, Oracle Fusion Payments, and you.

The following settings in the header of the Create Payment Process Profile page affect printed payment file statuses:

• Processing Type choice list: Printed.

• Default Payment Document choice list

• Send to file radio button: Produces a formatted output file, which is printed outside of Oracle Fusion Applications

• Send to printer radio button

• Automatically Print After Formatting check box

• Default Printer choice list

• Payment File Format choice list. You can specify the payment file format to use for the printed payment file.

Tip: If you don't want to print payment files immediately, you must manually submit the payment file for printing. Manual submission is done on the Print Payment Documents page.

How Printed Payment Files Statuses Are Impacted

The following figure illustrates the flow of statuses when printing payment files, which includes printing to a file as well as to a printer.

The following table describes the stages and statuses of printed payment files and the subsequent action taken by you or the application.

Printed Payment File Stage	Printed Payment File Status	Action You or the Application Takes
The payment file is created and validated, but fails validation.	Failed validation and pending action	You must take remedial action.
You review a payment file that failed validation and remove payments or override errors.	Retry payment file validation	Payments validates the payment file again.
The payment file passes validation.	Created	Payments starts the formatting process.
The payment file is terminated.	Terminated	Payments returns the documents payable to the source product.
The payment file failed formatting.	Failed formatting and pending action	You must take remedial action.
Payments was set up to allow printing outside the application rather than within it. The data extract was created and formatting is complete.	Formatted and ready for recording	The payment file is created, formatted, and ready to be recorded.
Payments was set up to allow printing outside the application rather than within it. Creation of the data extract and formatting are incomplete because another payment file has locked the payment document.	Created and ready for formatting	The payment file is created and ready to be formatted.
Creation of the data extract and formatting are incomplete for a printed payment file because another payment file has locked the payment document.	Created and ready for printing	The payment file is created and ready to print.
Creation of the data extract and formatting is complete for a printed payment file. Payments was set up to print immediately, but the print program has not yet submitted the file to Oracle Analytics Publisher. This status is very short-lived and is rarely seen.	Formatted	The payment file is created and formatted.
Creation of the data extract and formatting was completed for a printed payment file. Payments was set up for deferred printing.	Formatted and ready for printing	The payment file is created, formatted, and ready to print.
You initiated printing on the Print Payment Documents page or on the Reprint Payment Documents page.	Submitted for printing	The payment file is sent to the printer. You can reprint payments or record the print status.
The printer prints the payment file.	Printed	You record the final print status on the Record Print Status page.
You void a payment.	Terminated	If the payment was the last one in the file, the payment file is terminated.