Tuesday, March 31, 2026

Oracle Fusion Tax Series Part 3- Simulating and Enabling Tax

 Configuring tax rules in Oracle Fusion is only half the journey—understanding how those rules behave in real business scenarios is what truly defines a successful implementation. In Part 3 of the Oracle Fusion Tax Series, we shift from configuration to validation by focusing on simulating and enabling tax.

Tax simulation is a critical step that allows organizations to test tax setups before they go live. It helps uncover gaps, conflicts, or unexpected outcomes by replicating real transaction scenarios such as procure-to-pay, order-to-cash, and intercompany flows. By simulating taxes in advance, implementation teams can ensure that rates, rules, jurisdictions, and recovery logic work exactly as intended—without impacting actual financial data.

In this part of the series, we will explore how to effectively simulate tax calculations, review tax results, and confidently enable tax for production use. Whether you’re preparing for go-live or validating changes in an existing environment, this blog will help you bridge the gap between tax configuration and real-world execution, ensuring accuracy, compliance, and business confidence.


Step 1: Enable Taxes for Simulation

Navigation--> Setup and Maintenance-->Manage Taxes

Search for US SALES and USE TAX enable Tax for Simulation-enable it for City. County and State
City:


County:
State:



Save all records- double check if its saved


Navigation--> Setup and Maintenance-->Manage Simulator Transactions
- Click on +

- Document Event Class-> Purchase Invoice
- Legal Entity--> Enter Legal Entity Information
- Taxation Country-->US
- Business Unit--> Enter BU Information
- Document Number--> Invoice Number <TEST>
- Document Date--> Enter Today's Date
- Supplier and Site Information


Click Save and View Tax Lines



Once setup looks Okay Enable Tax for transactions

Navigation--> Setup and Maintenance-->Manage Taxes

Enable All 3 Taxes (City, County and State)


Test on AP Invoice


Once you’ve simulated and enabled tax with confidence, you’re setting yourself up for fewer surprises, smoother transactions, and a much more controlled go-live in Oracle Fusion.


In my next blog, I’ll give you a sneak peek into Oracle Fusion Lease Accounting and its key features—before picking things back up with Part 4 of the Oracle Fusion Tax Series, where we dive into Advanced Tax Rules. Stay tuned!


Wednesday, March 25, 2026

Oracle Fusion Tax Series-Part 2- Configuring Tax Foundation Objects

 

In my previous blogs, I introduced Oracle Fusion Tax and walked through some of the key concepts you need to understand before getting started. In this second blog of my Oracle Fusion Tax series, I’ll be focusing on the foundational setup required for Cloud Tax. In the blogs that follow, we’ll move into more advanced topics and share additional insights to consider when implementing Fusion Tax. For this blog, since my client is based in the US, I’ll be configuring Oracle Fusion Tax specifically for US Sales and Use Tax.

Manage Tax Regime

As mentioned in my previous blog, we set up tax regimes for each geographical region—typically at the country level (or by zone in the case of the EU)—where the client operates and where distinct tax regulations apply.

Navigation: Setup and MaintenanceàFinancials OfferingàTransaction TaxàManage Tax Regime

Tax Regime Code: US SALES AND USE TAX

Tax Regime Name: US SALES AND USE TAX

Regime Level: Country

Country: United States

 

Under Control and Defaults provide some common configuration options such as :

Tax Currency : USD (Since Configuring US Tax)

Minimum Accountable Unit: 0.01 (Minimum Tax to be Applied)

Tax Precision: 2 (How many maximum decimals should be calculated)

Tax Inclusion Method: Standard Non Inclusive Handling (Will there be separate Tax Line on the invoice or will it be included in the Invoice Lines)

Rounding Rule: Nearest (Round Rule Required)

Under Configuration Options and Service Subscriptions, use the Configuration Options tab for the Business Units or Legal Entities for which you want to configure this tax regime. The Service Subscriptions option is intended for scenarios where thirdparty tax servicessuch as Avalara or Vertexare being implemented. For the purpose of this blog, I will focus on configuring the regime directly within the Fusion Application.

Party Name: Enter Legal Entity or Business Unit you want this regime to be enabled

Configuration for Taxes and Rules: Common Configuration with party overrides (this is generally the Best Practice-however this may change as per client requirements)

Configuration for Product Exceptions: Select Common Configuration

Refer Oracle Documentation for more information on these items-

Link: Tax Configuration Options

 

 

Save and Close

Manage Taxes

While Manage Geographies is ideally the next step in the configuration process, we generally set up geographies during the Enterprise configuration itself, making this step unnecessary.

Once the geographies are confirmed, we move on to the next step in the Manage Taxes configuration. Here, we set up the tax details under the tax regime. Each tax is defined using its tax status, tax rates, and the applicable tax rules.

Navigation: Setup and MaintenanceàFinancials OfferingàTransaction TaxàManage Taxesà Scope :US Sales and Use Tax

For US Sales and Use Tax – we typically configure 3 Taxes i.e. State, County and City- I will configure all of them step by step.

Enter Tax Information Entered in the screenshot:

 

Tax Regime Code: US SALES AND USE TAX

Configuration Owner: Global Configuration Owner (Use Global Configuration Owner if you need the following configurations for all BU’s/LE Defined)

 

Tax: STATE

Tax Name: STATE

 

Under Tax Information:

Geography Type: STATE (This is defined from Manage Geography Structure)

Parent Geography Type: Country

Parent Geography Name: United States

Tax Currency: USD

Applied Amount Handling: Prorated

 

Controls and Defaults

Tax Point Basis: Invoice (Typically what should be the basis for calculating Tax)

Tax Inclusion Method: Standard Non Inclusive Handling

Rest you can copy over directly for the screenshot- it is self explanatory.

Tax Rule Defaults (Depends on Client Requirements-best to confirm)

Place of Supply:

Procure to Pay

Bill From Party

Supplier Site Header Address

Bill to Party

Business Unit Address

Ship to Party

Ship to Location

Ship From Party

Supplier Site Header Address

Ship to, use bill to if not found

Use Ship to Location on the Invoice Line- if missing use Business Unit Address

 

Order to Cash

Bill from Party

Business Unit/Legal Entity Address

Bill to Party

Customer Site Bill To

Ship to Party

Customer Site Ship to

Ship from Party

Warehouse Address (Inventory Org Location)

Ship to, use bill to if not found

Customer site bill to or ship to

 

Tax Applicability: Applicable

 

Indirect Defaults

Create Defaults for Tax Jurisdiction, Status and Rate- for US since we have multiple states, you can default the Jurisdiction where the business Operates.

 

 

Tax Accounts

 

Enter Tax Accounts such as Liability Account for the required Business Unit you are configuring Tax for.

 

Save and Close- do the same exercise for other 2 Taxes (County and City)

In the above screenshots I have already shown how to create a Jurisdiction ,Status and Tax Rates- if you have additional Jurisdiction, Status or Rates you can directly create them from their respective tasks i.e. Manage Tax Jurisdiction, Manage Tax Status and Manage Tax Rates and Tax Recovery Rates.

 

Blog 3 of the Tax Series will touch upon Advanced Tax Conditions- stay tuned

Oracle Joint Venture Management

  Joint ventures are not new. What is new is the scale, contractual complexity, and regulatory scrutiny under which they operate—especially ...