ExamFinch.com My Study

Study guide

7.2 Completing Payments: Printing, Electronic Confirmation, Bank Acknowledgments, Single Payments, Stops and Voids

Practice this exam

Oracle Fusion Cloud Financials Payables and Expenses 2026 Implementation Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview, Enterprise Structures & Security

1.1 Exam Facts, Hands-On Format & How to Use This Guide 1.2 Enterprise and Financial Reporting Structures & the Data Security Model 1.3 Business Units and Reference Data Sets

2 Chapter 2: Master Data, Taxes & Cash Management Setup

2.1 Supplier Master Data: Profile, Addresses, Sites and Site Assignments 2.2 Supplier Controls: Registration, Income Tax Details, Site Holds and Third-Party Payments 2.3 Bank Account Master Data: Banks, Branches, Internal Accounts and Security 2.4 Transaction Tax Setup for Procure-to-Pay 2.5 Configuring Cash Management for Payables: Statements, Reconciliation Rules and Clearing

3 Chapter 3: Supplier Invoices — Options, Entry & Matching

3.1 Invoice Options and Common Options for Payables and Procurement 3.2 Supplier Invoice Processing: Invoice Types, Components and Distribution Sets 3.3 Matching Invoices to Purchase Orders, Receipts and Consumption Advice

4 Chapter 4: Supplier Invoices — Tolerances, Holds & Approvals

4.1 Invoice Validation, Invoice Tolerances, Holds and Releases 4.2 Invoice Approval Rules: Workflow, Spreadsheet Rules and Approval Actions 4.3 Prepayments, Recurring Invoices, Credit and Debit Memos

5 Chapter 5: Invoice Automation, AI & Subledger Accounting

5.1 AI in the Supplier Invoices Process: IDR, Document IO, the Payables Agent and Intelligent Defaulting 5.2 Importing Invoices: File-Based Data Import, Import Payables Invoices and Corrections 5.3 Setting Up Subledger Accounting for Payables

6 Chapter 6: Payments — Configuration

6.1 Payment Options, Payment Methods, Defaulting Rules and Payment Terms 6.2 Payment Process Profiles, Formats, Payment Systems and Transmission 6.3 Disbursement System Options, Payment Security and Payment Approval Rules

7 Chapter 7: Payments — Processing, Withholding, Accounting & AI

7.1 The Payment Process and Payment Process Request Templates 7.2 Completing Payments: Printing, Electronic Confirmation, Bank Acknowledgments, Single Payments, Stops and Voids 7.3 Withholding Tax Setup and US 1099 Reporting 7.4 Payment Accounting: Issue and Clearing, Gains and Losses, Discounts, Cross-Currency Payments and Bills Payable 7.5 AI in the Payments Process: the Payments Agent, Discount Intelligence, Virtual Cards and Fraud Controls

8 Chapter 8: Accounts Payable Balances & Period Close

8.1 Payables Calendars and Payables Accounting Period Statuses 8.2 Payables to General Ledger Reconciliation 8.3 The Payables Period Close Process: Unaccounted Transactions, Sweep and Close Exceptions 8.4 Balancing, Accruals and Year-End Activities in Payables 8.5 Accounts Payable Analysis and Reporting: Landing Pages, Dashboards, Aging Periods and Key Reports

9 Chapter 9: Expenses — Processing, Setup & Policies

9.1 Expenses Processing: From Expense Entry to Reimbursement 9.2 Expenses System Options, Expense Report Templates and Expense Types 9.3 Managing Expense Policies: Categories, Rate Determinants and Enforcement 9.4 Mileage and Per Diem Policies, Oracle Maps and Cumulative Mileage 9.5 Conversion Rate Policies, Receipt Requirements and Payment Hold Rules

10 Chapter 10: Expenses — Approvals, Cards, Advances, Audit & Travel

10.1 Configuring Expense Approval Rules in the BPM Worklist 10.2 Configuring Corporate Card Programs: Payment Options, Transaction Files and Accounting 10.3 Managing Cash Advances: Policies, Approval, Accounting and Application 10.4 Managing Audit Rules, the Expense Audit and Reimbursement 10.5 Configuring Travel Integration: Travel Partners, Itineraries and Trip Expense Reports

11 Chapter 11: AI, Mobile, Automation & Redwood

11.1 AI, Mobile and Automation in Expenses: Expense Assistant, Email Receipts and Touchless Expenses 11.2 Enabling Redwood Capabilities and Their Impact on Existing Configurations

7.2 Completing Payments: Printing, Electronic Confirmation, Bank Acknowledgments, Single Payments, Stops and Voids

Key Takeaways Explain This Topic AI

Printed payments are confirmed by recording the print status; once payments are confirmed, the payment file can't be terminated and problem payments must be voided.

A skipped numbered check is marked Skipped on Record Print Status and later checks are renumbered; a spoiled one is reprinted on a new number or marked Spoiled.

Electronic files are confirmed automatically when formatted or when transmitted, or manually if the profile allows it.

ISO 20022 acknowledgments come at three levels (L0 file syntax within minutes, L1 file and payment status within hours, L2 clearing rejections in 2–3 days), and rejected payments can be voided automatically.

When you void a payment you can cancel the invoices, put them on hold, or leave them available for payment, and Oracle reverses the payment accounting and realized gain or loss.

Last updated: October 2026

After a payment process request (PPR) builds payments and creates a payment file, the payment still has to be printed or transmitted, confirmed, and sometimes corrected. These steps complete the published objective Understand the Payment process . Payment approval is covered in section 6.3.

Printed payments

A printed payment file goes through a sequence of statuses:

  • Created
  • Formatted (or Formatted and ready for printing when printing is deferred)
  • Submitted for printing
  • Printed

If you print outside Oracle, the file goes to Formatted and ready for recording .

When another payment file has locked the payment document (the check stock), the file waits as Created and ready for formatting or Created and ready for printing .

After printing, record the result on the Record Print Status page:

Situation What to do Result

All checks printed correctly Record the print status as printed The payments are confirmed . Payables is notified and accounts for the payments.

A numbered check was skipped by the printer Mark it Skipped Later documents are renumbered for your review. The skipped stock can be kept for a later single or manual payment, or destroyed and voided in Cash Management on the Edit Bank Account page.

A numbered check was spoiled and you'll reprint Reprint on the Reprint Payment Documents page, then report the payment as issued on Record Print Status The spoiled number is noted and the payment gets the new number

A check was spoiled and you won't reprint Mark it Spoiled and destroy it The number is recorded as spoiled

Once printed payments are confirmed , you can't terminate the payment file; the Terminate Payment Process action no longer appears. Problem payments must be voided . Positive pay files and separate remittance advice come from the profile's Reporting tab (section 6.2).

  • Electronic payments
  • Confirmation

A confirmed electronic payment file is complete . Payments then notifies Payables so it can create the accounting. Confirmation happens in one of two ways:

Automatically , at the profile's confirmation point: when the payment file is formatted , or when it is transmitted to the payment system.

Manually , from Manage Payment Files or the Payment File page. This needs an electronic profile with manual confirmation allowed, and a file in the status Formatted , Formatted and Ready for Transmission , Transmitted or Transmission Failed . Manual confirmation suits cases where you wait for a bank notification.

As with printed payments, once a file is confirmed you can't terminate it. You void individual payments instead.

When transmission fails

  • Option When to use it Result
  • Transmit the file again The failure was temporary, or the setup has been fixed The file is sent again

Ignore the transmission failure The file reached the bank by other means, or the bank confirms receipt The status is forced to Transmitted

Stop the payment process The file mustn't be sent The file is Terminated , its payments are Canceled , and the documents are unlocked for a later run

ISO 20022 acknowledgments

For ISO 20022 credit transfers, Oracle can retrieve and process the bank's acknowledgment files . Banks can send up to three levels:

  • Level Timing Content
  • L0 Within minutes File-level: the schema and syntax are correct
  • L1 Within hours File and payment-level status
  • L2 2–3 days Payment-level rejections from clearing; one file can cover several payment files

The settings are on the payment system account of the predefined ISO20022 Payment System :

  • automatic retrieval interval in minutes;
  • automatic voiding option for rejected payments;

acknowledgment format ( ISO Disbursement Acknowledgment Format or JP Morgan Disbursement Acknowledgment Format );

  • acknowledgment transmission configuration (SFTP, HTTPS or UCM);
  • voiding invoice action ;
  • email of acknowledgment details;

payment file register format.

When the file is processed, its status is Completed and pending acknowledgment . After the acknowledgment is processed, the file and each payment become Acknowledged or Rejected . For rejected payments, Oracle can void them automatically and put the invoice on hold or cancel it . With no action, the invoice goes back to Unpaid . A payment file register with the acknowledgment details is produced automatically. You can also retrieve acknowledgments manually with Retrieve Acknowledgment on Manage Payment Files.

Single payments from the Create Payments page

The PPR is for batches. The Create Payments page handles one-off payments:

A Quick payment is created, formatted and printed or transmitted for selected installments of one supplier.

A Manual payment records a payment already made outside Oracle, such as a handwritten check or a wire sent through the bank's portal, so Payables can account for it and mark the installments paid.

Supplier refunds are recorded against credit balances.

Remember that payment approval doesn't apply to payments from this page (section 6.3).

Stop payment requests

A stop payment request records when a stop order was placed with, or released by, the bank. Oracle's sequence:

A supplier says a payment wasn't received.

You ask the bank to stop it.

You record the stop payment request with the Manage Payments task. If the bank confirms the stop, you void the payment. If the payment had already cleared, you cancel the stop request.

Voiding payments

You can void individual payments, or a whole payment file once all its payments are voided. When you void, you choose what happens to the invoices:

  • cancel them;
  • place them on hold ;

leave them available for payment.

Oracle then reverses automatically :

  • the payment accounting and payment records;
  • realized gains or losses on foreign-currency invoices;
  • interest invoices related to the payment, if interest invoices are enabled;

withholding taken at payment: a reversing invoice to the tax authority offsets the withholding tax invoice.

With budgetary control, a void triggers a funds reservation for the negative payment amount. If that fails, the payment stays Negotiable . Reissue voids the original and issues a new payment in one action.

Loading diagram...