3.2 Supplier Invoice Processing: Invoice Types, Components and Distribution 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

3.2 Supplier Invoice Processing: Invoice Types, Components and Distribution Sets

Key Takeaways Explain This Topic AI

A Payables invoice has a header, lines, distributions and installments; installments carry the due dates, due amounts, discount dates and payment method.

Invoice types include Standard, Prepayment, Credit memo, Debit memo, Withholding tax, Interest, Standard invoice request, Credit memo invoice request and Payment request.

Distributions are created by matching, by a distribution set, by allocating freight or miscellaneous lines, or manually on Manage Distributions.

A 100 percent distribution set allocates by fixed percentages, while a 0 percent (skeleton) set creates the distributions and leaves the amounts for the user to enter.

Allocate All Lines prorates a freight or miscellaneous charge, less inclusive tax, across item lines; Allocate Specific Lines can use selected lines, amounts or percentages.

Last updated: October 2026

The published objectives are Describe Supplier Invoices processing and Manage Distribution sets . You need to recognize each invoice type and component, and predict what the distributions will be after you match, allocate or apply a distribution set.

Invoice types

• Type Description
• Standard A supplier invoice for goods or services

Prepayment An advance payment to a supplier. After the first validation its status is Unpaid until it is paid (section 4.3).

• Credit memo A supplier document that gives a credit
• Debit memo Created when a supplier doesn't send you a credit memo document, so you record the credit yourself

Withholding tax Generated automatically to pay a tax authority. Can be created manually if Allow manual withholding is enabled (section 7.3).

• Interest Generated automatically for interest on overdue invoices when interest invoices are enabled
• Standard invoice request A non-PO invoice submitted in Supplier Portal, waiting for the requester's approval

Credit memo invoice request A non-PO credit memo submitted in Supplier Portal, waiting for the requester's approval

Payment request A request from Oracle Expenses or Oracle Receivables to pay someone who isn't set up as a supplier , such as an employee reimbursement or a customer refund

Invoice components

An invoice has four components:

Header: invoice number and amount, supplier and site, payment terms, currency, dates, and the default liability distribution.

Lines: the goods and services, including tax, freight and miscellaneous charges. Lines also carry the details needed by Oracle Assets, Projects and Purchasing. They can be created by matching to a PO, receipt or consumption advice, or entered manually.

Distributions: the accounting information, meaning the accounting date, distribution combination and project details. Accounting entries are created from distributions.

Installments: due dates, due amounts, discount dates and payment method. Payment process requests select installments (section 7.1).

Line types :

Item: goods and services.

Freight and Miscellaneous: charges that can be allocated to item lines.

Prepayment: created automatically when a prepayment is applied or unapplied.

Tax and withholding appear in the Taxes section of the invoice pages rather than as user-entered line types.

How distributions are created

Oracle lists four ways:

Matching to a purchase order, receipt or consumption advice (section 3.3).

A distribution set .

Allocating a freight or miscellaneous line.

Manually on the Manage Distributions page.

Tax distributions are usually created when the invoice is validated.

The distribution combination on the invoice line only defaults into Manage Distributions. Changing a distribution there doesn't change the line's value. Subledger Accounting can also be set to take accounts from a source other than the invoice distribution (section 5.3).

Freight and miscellaneous allocations

Allocating a charge creates distributions that use the same distribution combinations as the item lines it is allocated to. With Landed Cost Management configured, the charge becomes part of the item cost. Tax is calculated automatically when you choose an allocation action, so the inclusive tax is known.

Allocate All Lines spreads the charge, less inclusive tax, across all item lines in proportion. Oracle's example: an invoice for USD 110 has item lines of USD 75 and USD 25 and freight of USD 10. Allocating to all lines creates freight distributions of USD 7.50 and USD 2.50 .

Allocate Specific Lines lets you choose the target lines, give an amount for each line, or give a percentage for each line.

You can change saved allocations until the distributions are generated. If no allocation is done and the Common Options Freight or Miscellaneous distribution is blank, the charge is prorated across item lines.

Distribution sets

A distribution set creates distributions automatically for invoices that aren't matched to purchase orders . Oracle's example is an advertising supplier whose expense is split across four departments.

Key facts:

Distribution sets are defined for invoice business units , not shared through reference data sets.

A default distribution set can be set on the Site Assignments tab of the supplier site. You can also pick or override a set during invoice entry.

A set can include income tax types (for 1099 suppliers), project information (copied to the distribution and overridable), and descriptive flexfields (copied to the distribution).

Tax codes aren't used in distribution sets.

With percentages or without

Set type How it works Use it when

100 percent distribution set Each line has an account and a percentage. Percentages must total 100 and may include negative values. You know the split, for example rent at 70% sales facility and 30% administration

0 percent distribution set (a skeleton set) Each line has an account and no percentage . The distributions are created and the user enters the amounts. The accounts are known but the split changes each time, for example facilities expense split by monthly headcount

A skeleton set doesn't mean a partially defined account that the clerk finishes off. It means the accounts are complete and the amounts are blank . If an invoice is saved with distributions that don't add up to the line amount, validation places a Dist Variance hold, which can't be released manually (section 4.1).

Putting it together: an unmatched utility invoice

A USD 1,000 utility invoice arrives for site POWERCO . Its site assignment has the default distribution set FACILITIES-SPLIT , a 100 percent set with 60% to 10-100-6200 and 40% to 10-200-6200.

The invoice is entered with one item line of USD 1,000. The distribution set creates USD 600 and USD 400 distributions.

Validation calculates tax and checks for holds. With Hold unmatched invoices set to No for this site, no Matching Required hold is placed.

Installments come from the payment terms and terms date.

If the business unit instead used a 0 percent set, step 1 would create two USD 0 distributions. The clerk would have to enter 600 and 400 before validation could pass.

Loading diagram...