6.2 Payment Process Profiles, Formats, Payment Systems and Transmission

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.2 Payment Process Profiles, Formats, Payment Systems and Transmission

Key Takeaways Explain This Topic AI

A payment process profile needs payment formats, a payment system with its payment system account, and a transmission configuration set up first (a payment system is optional for printed payments).

Profile usage rules limit a profile by payment method, disbursement bank account, business unit and currency, and narrow rules let Payments pick a profile without user intervention.

An electronic profile sets the payment confirmation point (when the file is formatted or when it is transmitted); a printed profile sets the default payment document and printing options.

The Payment tab groups documents payable into payments, and the Payment File tab groups payments into files and sets batch booking, overrides, limits, sorting and bank instructions.

Every Payments format is an Oracle Analytics Publisher template applied to a data extract; ISO 20022 profiles use the SEPA or CGI versions.

Last updated: October 2026

The published objective is Manage Payment Process Profiles . Oracle calls the payment process profile (PPP) the blueprint for disbursement processing. It links setups, controls usage, decides formatting, printing and transmission, controls how payments and payment files are created, and automates reports.

Setups a profile depends on

Setup What it is Notes

Format A data file with an Oracle Analytics Publisher (BI Publisher) template applied Every Payments format has one Analytics Publisher template and uses a data extract. Formats produce checks, electronic payment files and reports.

Payment system The bank, or a third-party gateway or processor, that processes your payments Not needed for printed payments , but can be used to send positive pay files

Payment system account Your account and settings with that payment system Selected on the profile's Payment System tab

Transmission protocol How files are sent, for example HTTP(S), SFTP or FTP, with the parameters it needs Payments predefines industry-standard protocols. Oracle notes FTP is unsecured, for legacy needs only.

Transmission configuration Values for the protocol's parameters, specific to one payment system Created on Manage Transmission Configurations and assigned on the profile. Supports PGP encryption and digital signature and two-factor authentication with a security key file. Test it with the transmission test.

Formats can also have validations . These are predefined or user-defined rules that run on documents payable, payments or payment files, before the file is sent.

Usage rules: when a profile applies

A profile's Usage Rules tab can be set to All or Specify for:

payment methods ;
disbursement bank accounts ;
business units ;

currencies .

For example, restrict a currency when the format accepts only that currency.

When you submit a payment process request (PPR) with a profile, any document whose attributes conflict with the profile's usage rules fails validation . With no profile on the PPR, Payments looks for the profile whose rules match each document. If none match, or more than one could match, a user must choose one on the Assign Payment Process Attributes page. Oracle's advice: keep usage rules no broader than necessary , for example one profile for business unit X and another for Y, so the profile can be picked automatically.

Header settings

Setting Electronic profile Printed profile
Processing Type Electronic Printed

Payment File Format For example, ISO20022 Common Global Implementation Format For example, Standard Check Format (Stub after Payment)

Payment Confirmation Point When the payment file is formatted or when it is transmitted , plus Allow Manual Setting of Payment Confirmation Payments are confirmed when you record the print status (section 7.2)

Printed-only options n/a Default Payment Document ; Send to file (print outside Oracle) or Send to printer ; Automatically Print After Formatting ; Default Printer

The printed profile and the payment document (check stock on the bank account, section 2.3) must use the same format .

The tabs that build payments and files
Payment tab: documents into payments

Document grouping rules say which attributes must match for documents payable to share one payment. If a rule is enabled for an attribute, documents with different values go into separate payments. Examples include due date , settlement priority and delivery channel . Document limits , such as Maximum Documents per Payment , cap how many invoices go in one payment.

Some separation happens whatever the rules say. A single payment always has one payee, one payment currency and one disbursement bank account, so documents that differ in any of these are always paid separately.

Payment File tab: payments into files

Payment grouping rules decide which attributes split payments into separate files.

Batch booking: one debit entry for a group rather than for each credit.

Overrides: the file carries the service level and delivery channel you choose instead of those from the supplier setup. Without an override, a file can contain several combinations.

Payment limits: the maximum number of payments in a file.

Payment sorting: the order of payments in the file and in the payment file register.

Bank instructions: text included in every file from this profile.

Periodic sequences: sequential numbering of files for the bank.

Grouping tab (ISO 20022)

ISO profiles group transactions within a file the way the ISO standard requires. Oracle's example selects payment date, disbursement bank account, service level and delivery channel. Oracle provides ISO 20022 payment formats in two versions: SEPA for European payments and CGI (Common Global Implementation) for the rest. It also documents upgrading ISO 20022 templates to the 2019 version.

Reporting tab

You can generate three reports automatically:

Payment file register: details of the payments in a file, for your records.

Positive pay: a list of issued checks sent to the bank to stop fraudulent checks. It can be transmitted automatically.

Separate remittance advice: sent to suppliers listing the invoices paid, for example by email . It can be submitted automatically when payments are confirmed, and you can choose a condition such as All payments .

Worked setup: an ISO 20022 electronic profile

Oracle's electronic payments walkthrough:

Create a profile with the ISO20022 Common Global Implementation Format and processing type Electronic . Set the confirmation point to When the payment file is transmitted .

Usage Rules: All for payment methods, bank accounts, business units and currencies, or narrower as needed.

Payment System: ISO20022 Payment System . Select Automatically transmit payment file after formatting and assign a transmission configuration to the CGI payment system account.

Payment: group documents by due date, settlement priority and delivery channel.

Payment File: set service level and delivery channel overrides as needed.

Grouping: payment date, disbursement bank account, service level, delivery channel.

Reporting: payment file register with document detail , and separate remittance advice by email when payments are confirmed.

Loading diagram...