2.4 Transaction Tax Setup for Procure-to-Pay

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

2.4 Transaction Tax Setup for Procure-to-Pay

Key Takeaways Explain This Topic AI

Regime-to-rate setup defines tax regimes, taxes, tax jurisdictions, tax statuses and tax rates, in that hierarchy.

Tax determination starts by identifying the first party from the transaction's business unit, then finds applicable regimes, candidate taxes, applicability, registration, status and rate.

Tax rules are evaluated in priority order until one succeeds; if none does, the default value defined in setup is used.

Self-assessment (reverse charge or use tax) is triggered by marking the first party's tax registration "Set as self-assessment (reverse charge)", usually with a registration rule for unregistered suppliers.

When a user overrides calculated tax on a Payables invoice, Oracle compares the change with both the tax tolerance amount and percentage, uses the lower limit, and places a hold if it is exceeded.

Last updated: October 2026

The published objective is Set up Transaction and Withholding Taxes . Withholding has its own Payables-specific setup and is covered in section 7.3. This section covers transaction taxes : the VAT, GST, consumption and sales-and-use taxes that Oracle Fusion Tax calculates when an invoice is validated or an expense report is processed. Oracle Fusion Tax is a single service for every Fusion application, so the same configuration serves Payables, Expenses, Purchasing and Receivables.

Task lists and the regime-to-rate hierarchy

In Setup and Maintenance, Oracle splits tax setup into two task lists:

Define Tax Configuration , for the basic setup of each tax regime.

Define Advanced Tax Configuration , for exceptions such as complex rules, fiscal classifications and exemptions.

Rapid-implementation spreadsheets, such as the Manage Tax Regimes spreadsheet, can load the basic setup in bulk.

The core is regime-to-rate setup:

Level What it holds Example

Tax regime One per country (or tax zone) per tax type. Defaults and controls: tax currency, precision, minimal accountable unit, rounding rule, tax inclusion method, conversion rate type, and the reporting and collecting tax authorities. GB VAT , or US Sales and Use Tax

Tax Each separate tax in the regime GB VAT , or a tax per US state, county and city

Tax jurisdiction Links a tax to a geography or tax zone where an authority levies it A county jurisdiction for each California county

Tax status The taxable nature of a product for that tax Standard , Zero , Exempt , Reduced
Tax rate The rate for a status, or a jurisdiction-specific rate 20% standard VAT

For a regime, you choose a regime level of Country or Tax zone . You can also nominate a parent regime for grouped reporting.

Configuration owners and party tax profiles

A configuration owner is the party whose tax setup applies. In each regime subscription, the first party's configuration option decides which taxes are candidates:

Configuration option Taxes considered
Common configuration Taxes owned by the global configuration owner
Party-specific configuration Taxes owned by the first party itself
Common configuration with party overrides Both; if both define the same tax, the first party's version wins

Parent first-party configuration with party overrides The first party's and its parent first party's taxes; the first party wins on duplicates

Party tax profiles hold each party's tax information:

First parties. Legal entities, legal reporting units and business units. A business unit can either use its legal entity's tax setup (the Use subscription of the legal entity option) or keep its own configuration options.

Third parties. Suppliers, customers and their sites, holding registrations, fiscal classifications and reporting codes. Oracle notes you don't need third-party profiles for tax to calculate.

Tax authorities. Collecting authorities, reporting authorities, or both.

How tax determination runs

Oracle documents the sequence for each transaction line:

Identify the first party. Start from the transaction's business unit , then use its own configuration or its legal entity's, according to the party tax profile.

Determine applicable tax regimes. Use the regime determination set: the predefined TAXREGIME (geography-based), STCC (standard tax classification code, mainly for migrated data) or a user-defined set. A third option is integration with a tax partner.

Find candidate taxes using the configuration option above.

Determine tax applicability. Direct tax rate rules are processed first. Then come tax applicability rules and place of supply . If no jurisdiction is found for the place-of-supply location, the tax doesn't apply. Oracle's example: UK VAT doesn't apply to goods shipped from a French warehouse to a German customer.

Determine tax registration, tax status and tax rate.

Determine the taxable basis and calculate the tax.

For purchases, determine the recovery rate.

Tax rules

Each step can be shaped by a tax rule type:

Place of supply
Tax applicability
Tax registration
Tax status
Tax rate
Taxable basis
Tax calculation
Tax recovery rate

Rules are tied to a regime, configuration owner and tax. They have event class and geography associations, effective dates, and condition sets of determining factors. Rules are evaluated in priority order until one evaluates successfully. If none does, the default from setup is used. Simple implementations rely mostly on defaults. Rules handle the exceptions.

Payables-specific tax topics
Recovery

Tax recovery is the full or partial reclaim of tax paid on purchases. It is calculated at the item distribution level. The recovery rate comes from the tax rate, the tax's default, or a Determine Recovery Rate rule; Canada, for example, can need primary and secondary recovery types. The recoverable portion goes to a recoverable tax distribution. The rest is nonrecoverable and is generally charged to the item's expense or asset account.

Self-assessment

Sometimes the supplier has no nexus or registration where the goods are received. The buyer must then self-assess the tax: reverse charge in the EU, use tax in the US. The tax is calculated on the invoice but doesn't change the amount payable to the supplier . It is accounted as a tax liability instead.

Oracle's recommended method:

Set Set as self-assessment (reverse charge) on the first party's tax registration, typically the legal reporting unit's.

Add a tax registration rule that uses the first party's registration when the supplier's registration status is Not Registered or blank.

Self-assessment applies only to Payables transactions. Older alternatives, still available, are offset taxes (a matching negative-rate tax), reporting-only taxes and use taxes .

Overrides, tolerances and tax holds

The configuration owner tax options for the Payables event classes can limit how far users may override calculated tax. You set a maximum override amount and a maximum percentage . When a user overrides tax and the difference exceeds the limits, the invoice goes on hold . Oracle compares the override against both limits and uses the lower one .

Validation can also place the predefined Tax Variance (percentage) and Tax Amount Range (amount) holds when tax amounts fall outside the configured tolerances. Tax Difference is a matching hold for invoice and PO tax code mismatches. All three can be released manually.

Prepayment tax differences

When the rate changes between a prepayment and the invoice it is applied to, the difference can go to the Prepayment Tax Difference distribution in Common Options for Payables and Procurement. This only applies when the tax's Applied Amount Handling is Recalculate .

Loading diagram...