Study guide
1.3 Business Units and Reference Data Sets
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.3 Business Units and Reference Data Sets
Key Takeaways Explain This Topic AI
Payment terms use the sharing method "assignment to multiple sets, no common values allowed"; the reference group is Payables Payment Terms and the determinant type is business unit.
A business unit can use a payment term only if the term is assigned to the reference data set that the business unit uses for the Payables Payment Terms reference group.
Oracle requires the Immediate payment term to be assigned to the business unit's reference data set before you define Common Options for Payables and Procurement.
To assign payment terms to a set, the implementor needs a data role generated from the Financials Common Module Template for SetID.
Invoice options, payment options, distribution sets and expense templates are defined per business unit and aren't shared through reference data sets.
Last updated: October 2026
Large enterprises run dozens of business units. Without a sharing mechanism, every unit would need its own copy of each payment term and similar setup. Reference data sharing solves this. Setup records are grouped into reference data sets , and each business unit is told which set to use for each kind of reference data. The published objective is to describe the purpose of Business Units and Reference Sets . Expect questions where a value is missing from a list of values because of a set assignment.
Key terms
Term Meaning
Reference data set A named group of reference data records, for example US Set or EMEA Set . Oracle predefines a Common Set (COMMON) that works like any other set.
Reference group A category of set-enabled data that is assigned as a unit, for example Payables Payment Terms
Determinant type The kind of entity that decides which set applies. Oracle's determinant types are asset book, business unit, cost organization, project unit and reference data set . Payables reference groups use business unit .
Determinant value The specific entity, for example the US East business unit
Set assignment Mapping a business unit to a reference data set for each reference group. A business unit has a default set , which you can override for individual reference groups on Manage Business Unit Set Assignment .
Sharing methods
Oracle defines how each kind of reference data can be shared:
Assignment to one set only, no common values. Each record belongs to exactly one set.
Assignment to one set only, with common values. A record belongs to one set, and records in the common set are also available.
Assignment to multiple sets, no common values allowed. One record can be assigned to several sets.
Payables payment terms use assignment to multiple sets, no common values allowed . The reference group is Payables Payment Terms and the determinant type is business unit . You can still assign a term to the predefined common set, which then behaves like any other set: unless you also assign the term to other sets, only business units that use the common set can select it.
Worked example: sharing payment terms
Oracle's documentation uses this pattern:
Net 45 is assigned to the North America set.
Net 30 is assigned to both the North America and Europe sets.
The United States and Canada business units use North America for Payables Payment Terms.
The France business unit uses Europe .
- Business unit Set for Payables Payment Terms Terms available on its invoices
- United States North America Net 45, Net 30
- Canada North America Net 45, Net 30
- France Europe Net 30 only
If a French clerk complains that Net 45 is missing from the Payment Terms list, the answer isn't a security problem or a closed period. Net 45 simply isn't assigned to the Europe set.
Setup steps Oracle lists for payment terms
Assign a reference data set to the business unit for the Payables Payment Terms reference group, either when you define the business unit or later on Manage Business Unit Set Assignment.
Generate a data role for the reference data set using the predefined data role template Financials Common Module Template for SetID .
Provision that data role to the implementor who creates the payment terms.
Create the payment term and assign one or more sets in the Set Assignment section of the Create Payment Terms page.
Important
Before you define Common Options for Payables and Procurement, Oracle requires the Immediate payment term to be assigned to the reference data set for the business unit. If it isn't, the common options setup for that business unit can't be completed correctly.
What is not shared through reference data sets
A frequent mistake in drafts and practice tests is to assume that every Payables setup is set-enabled. Many important objects are tied to a single business unit :
Setup object Level Practical consequence
Invoice options (Manage Invoice Options) Invoice business unit Each invoice BU has its own terms date basis, approval and matching options
Payment options (Manage Payment Options) Business unit Payment accounting option, overrides and currency conversion settings differ by BU
Distribution sets Invoice business unit Defined "for invoice business units"; a default can be set on the supplier site assignment
Common Options for Payables and Procurement Business unit Default liability and prepayment distributions, offset segments
Expense report templates Business unit Oracle states that expense templates can't be shared across business units
Expenses system options All business units, with business-unit overrides Uses its own two-level model, not reference data sets
Global setups apply everywhere and aren't partitioned at all: Manage Disbursement System Options , payment methods (controlled by usage rules , see section 6.1) and payment process profiles (also usage rules). Usage rules are a separate mechanism from reference data sets. They limit where a payment method or profile can be used, by business unit, legal entity and other attributes.
Design guidance
Use few sets. A typical design has one set per region or regulatory regime, with the common set reserved for truly universal values.
Check the default set. When a business unit is created, its default set covers every reference group you don't explicitly override. Review overrides during design so a business unit doesn't inherit an unintended set.
Separate sharing from security. A term missing from a list of values points to the set assignment. A user who can't see any invoices points to data access (section 1.2).
Loading diagram...