7.1 The Payment Process and Payment Process Request Templates

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.1 The Payment Process and Payment Process Request Templates

Key Takeaways Explain This Topic AI

A PPR runs these steps: select documents, assign bank account and profile, validate documents, build and validate payments, optional review and approval, create, validate and format the payment file, then transmit or print.

Selection criteria decide which installments are chosen; payment attributes such as payment date, bank account and profile don't affect selection.

With a date basis of Pay Date and a site pay date basis of Discount, an installment is selected once the pay-through date reaches its first discount date, and the payment date decides which discount is taken.

Processing options include Apply credits up to zero amount payment, Review installments, Review proposed payments, Create payment files immediately, and validation failure handling for documents and for payments.

A transaction calendar on the PPR template moves pay-through dates and payment dates that fall on weekends or holidays to the next business day.

Last updated: October 2026

The published objectives are Understand the Payment process and Manage Payment Process Request Templates . Payment questions often ask why an installment wasn't selected, why a discount was or wasn't taken, or where a run stopped.

The disbursement process step by step

Oracle describes the flow from Payables into Payments:

• Step What happens
• 1. Create documents Payables creates documents payable (invoice installments)
• 2. Select documents The PPR selects installments that meet its criteria
• 3. Submit PPR The request is passed to Payments

4. Assign bank account and profile Taken from the PPR, or derived from usage rules. If that isn't possible, the user supplies them on Assign Payment Process Attributes .

5. Validate documents Document-level validations from the payment method and format. Failures are removed or stop the request, depending on the options.

6. Create and validate payments Documents are grouped into payments using the profile's rules, then payment-level validations run

• 7. Review and modify Optional stop: remove payments or documents, after which validations run again
• 8. Approve or reject When payment approval is enabled (section 6.3)
• 9. Create payment file Payments are grouped into files by bank account, profile and grouping rules

10. Validate payment file File-level validations. Failures can be fixed by removing payments, or overridden.

11. Create extract and format Oracle Analytics Publisher applies the format template to an XML extract

12. Transmit or print Electronic files go to the payment system. Printed files go to check stock, and you record the print status.

13. Post-processing Separate remittance advice, positive pay and payment file register

If anything needs your input, the process pauses , whatever the processing options say.

How selection and discounts work

The date basis on the PPR is Pay Date or Due Date . With Pay Date , the supplier site's pay date basis ( Discount or Due ) decides which installment date is compared with the pay-through date . Oracle's example installment has these dates:

• due 30 August;
• first discount on 15 July (USD 150);

second discount on 30 July (USD 100).

The site's pay date basis is Discount .

• Pay-through date Payment date Always take discount Selected? Discount taken
• 14 July 17 July Either No: the pay-through date is before the first discount date None
• 15 July 17 July Either Yes USD 100 : the payment date is after the first discount date but before the second
• 15 July 31 July Off Yes None: the payment date is after both discount dates
• 15 July 31 July On Yes USD 150 : always take discount takes the first discount
• 15 July 31 August On Yes USD 150, and interest may be calculated

If the date basis is Due Date , or the site's pay date basis is Due , the installment is selected only when the pay-through date is on or after the due date .

Payment process request templates

You can submit a PPR directly, or define a template on Create Payment Process Request Template . Templates let you:

• reuse settings;
• run the Payables Cash Requirement report against the template before submitting, to see the cash needed;

schedule the PPR to run regularly.

A template has three tabs.

Selection criteria (these decide which installments are chosen)

Criterion Meaning

Pay through date / Pay from date Latest and earliest installment due date. Scheduled templates calculate these relative to the run date, for example with pay-through days.

• From / To payment priority Range of installment payment priorities
• Date basis Pay Date or Due Date (see above)
• Include zero amount invoices Selects zero-amount installments
• Pay groups All by default, or specific pay groups
• Currencies Invoice or payment currencies

Business units A payment BU finds installments for the invoice BUs it services. An invoice BU finds only its own installments.

Legal entities, supplier type, payment method , invoice conversion rate type, supplier or party, invoice group Further filters

Payment attributes (these don't affect selection)

Payment date , disbursement bank account, payment process profile, bank charge bearer and similar values. They apply to the documents selected. Bank charge bearer values are Payee , Payer , Shared , Following Service Level and Payee Pays Express Charges .

Processing options (how automated the run is)

Option Effect

Apply credits up to zero amount payment Applies credits and creates a zero-amount payment if the grouped installments would otherwise be negative. If bank charges apply, those installments are rejected.

Review installments Stops after selection so you can add or remove installments, edit payment and discount amounts, enter user conversion rates, and calculate withholding and interest

Review proposed payments Stops after installments are grouped into payments, before the payments are built

Create payment files immediately Creates files for this request instead of waiting to combine its payments with other requests' payments

Validation failure handling for documents and for payments Whether failing items are removed and the rest continue, or the request stops for resolution

Transaction calendars

A transaction calendar on the template skips weekends and holidays. Define it with Manage Transaction Calendars (Financial Reporting Structures): name the calendar, set the default business days, generate it, and clear the Business Day box on holidays. Then select it in the template's Transaction Calendar field. Pay-through dates and payment dates that fall on non-business days move to the next available date . In Oracle's example, a payment date on Saturday 7 October that is a holiday in the calendar moves to Monday 9 October.

Payment process request status reports

When the Payment Process Request Status Report is set to submit automatically at completion (Manage Disbursement System Options), each finished request produces a report of its contents and status.

Loading diagram...