1.2 Enterprise and Financial Reporting Structures & the Data Security Model

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

1.2 Enterprise and Financial Reporting Structures & the Data Security Model

Key Takeaways Explain This Topic AI

A primary ledger is defined by its chart of accounts, accounting calendar, ledger currency and subledger accounting method.

A business unit only processes Payables and Expenses transactions when it has the Payables Invoicing, Payables Payment or Expense Management business function it needs.

A payment business unit can process payments for the invoice business units it services through a service provider relationship (centralized payment processing).

Payables grants data access by business unit through Manage Data Access for Users, while General Ledger users are secured by data access sets.

A job role such as Accounts Payable Specialist gives page access, but the user sees no invoices until a Business Unit security context is assigned for that role.

Last updated: October 2026

Every hands-on question about invoices, payments or expenses happens inside an enterprise structure. If you can't tell which business unit owns an invoice, which ledger it accounts to and which legal entity owns the bank account, you won't be able to predict defaults, approvals or accounting. This section covers the first two objectives of the common-configurations area: enterprise and financial reporting structure components, and the data security model.

Enterprise structure components

• Component What it represents Why it matters for Payables and Expenses
• Enterprise The top-level organization for the deployment Holds global setups shared by all entities

Legal entity A registered body that can own assets, sign contracts and incur liabilities Owns internal bank accounts, is the first party for tax, and is recorded on invoices and payments

Legal reporting unit The lowest level at which statutory reporting happens Carries tax registrations used by Oracle Fusion Tax

Ledger The accounting book: chart of accounts, calendar, currency, accounting method All Payables and Expenses accounting lands in a primary ledger, and optionally in secondary ledgers or reporting currencies

Business unit (BU) The unit that performs business functions and owns transactions Invoices, payments, expense reports and most setups (invoice options, payment options) are business-unit specific

Department / cost center An organization usually represented by a cost center segment value Feeds default expense accounts for employees and cost center owner approvals

The ledger and its four defining attributes

A primary ledger is defined by four things, sometimes called the "4 Cs":

Chart of accounts: the accounting key flexfield and its segments.

Accounting calendar: the periods.

Ledger currency.

Accounting convention: the subledger accounting method, such as Standard Accrual.

A secondary ledger can differ in any of these four. A reporting currency changes only the currency. Section 5.3 explains how one Payables event produces journals for both a primary and a secondary ledger.

Financial reporting structure components

The financial reporting structure is the set of objects that shape how accounting appears in reports:

Chart of accounts segments and segment labels. The primary balancing segment identifies the company or fund. Other labels are the cost center , natural account and intercompany segments.

Value sets and values. Natural account values carry an account type and an optional financial category . Payables reconciliation depends on the financial category: Oracle requires you to assign the Accounts Payable financial category to every liability natural account value you want on the Payables to Ledger Reconciliation report (section 8.2).

Account hierarchies (trees) used for reporting roll-ups and for some approval and security rules.

Cross-validation rules , which stop invalid account combinations. When a derived account breaks a rule, Payables raises an account hold or an accounting error.

Business functions and service provider relationships

A business unit only performs the work its business functions allow. For this exam, three functions matter most:

Payables Invoicing: enter, match, validate and approve supplier invoices.

Payables Payment: pay installments and own payment processing.

Expense Management: process employee expense reports.

Business units can also act as service providers :

A Procurement BU can serve one or more requisitioning business units.

In Payables, a payment business unit can service several invoice business units . This is centralized payment processing.

When you submit a payment process request (PPR) for a payment business unit, the selection finds installments for every invoice BU that the payment BU services. Two other places this matters: if you implement centralized payment processing, you reconcile Payables to the general ledger by ledger rather than by business unit; and payment templates list only the invoice groups you can reach through those relationships.

The data security model

Oracle Fusion security has two layers. Exam scenarios often test the gap between them.

Layer 1: function security (what you can do)

Job roles such as Accounts Payable Specialist, Accounts Payable Supervisor, Accounts Payable Manager, Cash Manager, Expense Manager and Financial Application Administrator inherit duty roles . Duty roles in turn carry privileges . Oracle's Payables documentation names several privileges you should recognize:

Privilege What it allows

Create Payables Invoice ( AP_CREATE_PAYABLES_INVOICE_PRIV ) Create invoices and complete incomplete scanned invoices

Edit Payables Invoice ( AP_EDIT_PAYABLES_INVOICE_PRIV ) Update invoices, including those in the imaging repository

Force Approve Payables Invoice ( AP_FORCE_APPROVE_PAYABLES_INVOICE_PRIV ) Use the Force Approve action when invoice options allow it

View Scanned Payables Invoice ( AP_VIEW_SCANNED_PAYABLES_INVOICES_PRIV_OBI ) Receive routed incomplete scanned invoices

Manage Bank Account Security ( CE_MANAGE_BANK_ACCOUNT_SECURITY_PRIV ) Change the user-and-role security on internal bank accounts

You manage roles in the Security Console . If a custom role is missing a privilege, the user sees odd behavior. Oracle's example: an approver who clicks View Invoice in a notification gets a blank page if the role lacks View Payables Invoice, Manage Payables Invoices and Manage Payables Invoices Activities.

Layer 2: data security (which records you can see)

A role alone doesn't expose any transactions. Payables limits access to invoices and payments by business unit , and the permission must be granted explicitly to each user. You do this on Manage Data Access for Users with four values:

• User name
• Role (for example, Accounts Payable Specialist)
• Security context, such as Business Unit
• Security context value, such as US1 Business Unit

Other modules secure data differently:

General Ledger users are secured by data access sets , which are built on ledgers or primary balancing segment values.

Cash Management can optionally secure bank account setup by legal entity , using the Legal Entity-Based Data Access for Bank Account Setup feature.

Internal bank accounts have their own business unit access and user-and-role security (section 2.3).

The reconciliation report shows the difference clearly. GL users see GL data for the balancing segment values in their data access set, plus Payables and SLA data for all business units linked to the ledger. Payables users see Payables and SLA data for their business units, plus GL data for the whole ledger.

Loading diagram...