6.3 Disbursement System Options, Payment Security and Payment Approval Rules

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

6.3 Disbursement System Options, Payment Security and Payment Approval Rules

Key Takeaways Explain This Topic AI

Manage Disbursement System Options holds the payment method default basis and the Enable payment approval option.

Payment approval needs Enable payment approval plus the Payment Process Request Status Report format with Automatically submit at payment process request completion selected.

Payment approval rules are configured in the BPM Worklist through Manage Task Configurations for Financials on the PaymentApproval task, and they route notifications sequentially only.

Payment approval applies only to payment process requests, not to payments created on the Create Payments page.

Rejecting payment approval terminates the payment process request; approvers who want to pay the rest first remove the unwanted payments and then approve.

Last updated: October 2026

Two published payment objectives are covered here: Manage Disbursement Options and Manage Payment Approval Rules . Both are set in the Payments functional area and, unlike payment options, apply across the deployment.

Manage Disbursement System Options

Disbursement system options are the enterprise-level defaults for how the disbursement process runs. Source products, and the individual payment process request (PPR), can override some of them. The options you need to know:

Option Effect

Payment method default basis Based only on payment method defaulting rules setup , or Override defaulting rules when default method set for payee (section 6.1)

Enable payment approval Turns on payment approval for all payment process requests

Payment Process Request Status Report format, with Automatically submit at payment process request completion Produces the report that shows a PPR's contents and status. Oracle's approval setup requires selecting it, so that an approval document exists before final payment.

Validation and processing defaults Defaults for how the payment process behaves, which a PPR or template can override, for example validation failure handling for documents and payments

Related security settings

Manage System Security Options (also in Payments) protects sensitive payment data:

Encryption of bank account and credit card data, using a master encryption key stored in Oracle Platform Security Services. Apply Quick Defaults creates the wallet and key and turns on encryption.

Tokenization of credit cards.

Masking of payment instrument numbers.

Rotation of the master encryption key and its subkeys.

Oracle requires encryption or tokenization of credit cards in Payments before corporate cards can be imported into Expenses , and tokenization if card data is used anywhere other than Expenses. Bank account access security (business unit access and user and role security) is covered in section 2.3.

Payment approval

Payment approval lets management control payments by prioritizing available funds. When it is enabled, the payment process stops at the Review Proposed Payments stage . Approvers then review the request, can remove payments from it, and approve or reject it.

Setting it up

Oracle lists three steps:

Enable payment approval. In Manage Disbursement System Options , select Enable payment approval . Select the Payment Process Request Status Report format and Automatically submit at payment process request completion .

Define a payment approval policy. Decide when approval starts, what triggers it (for example the bank account or pay group ), and who approves.

Configure payment approval rules.

Open Manage Task Configurations for Financials (the BPM Worklist).

Choose Task Configuration , then the PaymentApproval task.

On the Assignees tab, switch to vertical layout, click the diamond icon in the Payment Approval box, and choose Go to rule .

Edit the task and create the rules.

Oracle notes that payment approval rules route notifications to approvers in sequential order only . Design approval chains, not parallel panels.

Scope: what is and isn't approved

Only PPR payments are approved. Payments created on the Create Payments page, such as Quick and manual payments, aren't covered.

Every PPR is covered once approval is enabled. When a submitted PPR reaches Review Proposed Payments , approval starts and the status becomes Payments Approval Initiated .

Approvers receive email and BPM Worklist notifications.

Approval actions by channel

Where the approver acts Actions available
Review Proposed Payments page Approve, Reject, Withdraw approval, Resubmit for approval
Email notification Approve, Reject

BPM Worklist notification Withdraw approval, Resubmit for approval, Reassign, Delegate, Request for more information

Action Who can take it Result

Approve payment Approvers, when the status is Payments Approval Initiated Status changes to Approved . Processing resumes automatically, with no manual step.

Reject payment Approvers, at the same point The PPR is terminated immediately (status Terminated )

Withdraw approval The submitter or an approver The approval task ends and the status becomes Withdrawn . Active notifications are removed. Fix the issue and resubmit.

Resubmit for approval The submitter or an approver, when the status is Withdrawn from payments approval or Error in payments approval Approval restarts ( Payments Approval Initiated )

Terminate payment process request Anyone, at any time The PPR ends and notifications are removed

Because rejection terminates the whole request , an approver who objects to a single payment should remove that payment on the Review Proposed Payments page and then approve the rest. The removed payment's installments go back to Payables, unpaid, for a later run.

The Requiring Attention tab on the Payments overview page lists requests by approval status:

payments approval initiated;
pending payment approvals;
withdrawn from payments approval;

payments approved.

Exam patterns

Approvals enabled, but a Quick payment went out without approval. That is expected, because approval only covers PPRs.

An approver rejected one payment and the whole run stopped. Reject terminates the PPR. The approver should have removed the payment and then approved.

Approval should start for payments from the treasury account over USD 1,000,000. That is a PaymentApproval rule condition on the payment attributes, configured in the BPM Worklist, after enabling payment approval in disbursement system options.

Loading diagram...