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 in industries like energy, infrastructure, real estate, and manufacturing. Yet many organizations still manage joint venture accounting using spreadsheets, offline reconciliations, and manual settlements.

This is exactly where Oracle Joint Venture Management (JVM) changes the conversation.

 

Oracle Joint Venture Management enables a managing partner of a single joint venture or thousands of joint ventures to manage the distribution of financial transactions among joint venture partners.

Oracle Joint Venture Management can perform following tasks

Oracle JVM provides flexibility to adjust for changes in the Joint Operating Agreement during its life cycle such as:

• Adding/Removing Partner
• Managing Ownership Percentages
• Direct Billing including applying full transaction amount to an individual partner or specific partner instead of Ownership Percentages
• Auditing
• Reporting

In this blog, I will walk through the key Oracle Joint Venture Management (JVM) configurations and explain how they align with and extend Project Financial Management (PFM). We’ll look at how joint ventures are defined, how ownership and allocation rules are configured, and how project costs and revenues flow seamlessly from PFM into joint venture processing. By understanding this connection, organizations can move from manual, spreadsheet‑driven allocations to a controlled, auditable process—ensuring accurate partner distributions while staying fully aligned with project financials.

Lets Start with Configuring PFM :

Consultants must configure and enable Oracle Joint Venture Management as a source within the Project Costing module.

Navigation: Setup and Maintenance >Project Financial Management> Project Costing Base>Manage Project Transaction Source

Source Name: Oracle Fusion Joint Venture Management

Document: JV Partner Remboursements

Document Entries: Distribution, Distribution Reversal, Rebill

Next Step is to Configure Receivables Module- Enable the Oracle Joint Venture Management Transaction Source and Setup Distribution for JV Invoice and JV Credit Memo Transaction Types.

Configuring Joint Venture Management is pretty convenient on Redwood Page:

• Joint Venture Management Systems

Configure JVM System Options to map the interaction with Financials and Project Management Module

Under Primary Segment- Map the Company Segment for Joint Venture Management

Transaction Date References and defaults: Map the Transaction Date to capture- I have setup the GL Effective Date

Click 'Continue'

Enter the Project Mapping Details such as Project ID, Task ID,Expenditure Type, Date and Organization.

Once the system Options are completed- the next step is to define the Invoicing Partners

Invoicing Partners in Oracle Joint Venture Management (JVM) refers to the process of billing joint venture partners for their share of costs (and, in some cases, revenues) incurred by the operating entity.

In simple terms, once costs or revenues are allocated to partners based on joint venture rules, Oracle can automatically turn those allocations into partner invoices.

Enter either the Supplier Information or the Customer Information for each Invoicing Partner

Next Step is defining the Joint Venture Definition

A Joint Venture Definition is the foundational configuration object in Oracle Joint Venture Management (JVM). It represents the business agreement under which multiple parties share costs, revenues, assets, or liabilities, and it governs how transactions are identified, allocated, and settled among partners.

In simple terms, the Joint Venture Definition answers the question:

“Who are the partners, what are we sharing, and how should it be split?”

Enter Joint Venture Name, Description, Business Unit, Chart of Accounts, Legal Entity , keep the status as Initiated till you complete the Definition

Enter the Billing Information i.e. Payables and Receivables Account for JVM 

.Select the Account Information i.e. Accounts to Identify its JVM Transaction -since we are going to identify JV Transactions from PFM , you can ignore this step

Oracle Provides you to select single Project or a Project Sets for your JVM Distributions-select accordingly

Assign you Stakeholders/Invoicing Partners and Ownership Percentage

With the basic configurations completed- let's now run a Process Demo to integrate JVM with Project Costing and Accounts Receivables

 Step 1: Create AP Invoice , Approve Invoice , Post to GL and Import Cost to PFM

Step 2: Run Identify Joint Venture Transactions Process

Step 3: View your Transactions in Manage Joint Venture Transactions 

Navigation: Joint Venture Management-->Joint Venture Transactions

Step 4: Once Identified, you can run Create Joint Venture Distributions Process with Processing Mode Create Joint Venture Distributions

Step 5: Run Create Joint Venture Invoices and Journal Entries Process with Processing Mode Create Invoices for Joint Venture Distributions

This process will automatically create the AR Invoice

You can now run Cost Import for Joint Venture Management Source to validate these cost now deducted on your Joint Venture Management Project

By getting the Joint Venture Management configurations right and aligning them closely with Project Financial Management, organizations can move beyond manual reconciliations and build a transparent, scalable, and audit‑ready foundation for managing joint ventures in Oracle Cloud ERP.

Oracle Fusion Tax Reporting

 

Tax reporting can quickly become overwhelming, especially when organizations are processing thousands of transactions across payables and receivables. Between staying compliant, reconciling balances, and responding to audits, tax teams often spend more time pulling data than actually reviewing it. Oracle Fusion Tax helps cut through that complexity by offering a flexible and centralized reporting solution that supports both operational reporting and statutory compliance.

One of the biggest advantages of Oracle Fusion Tax is its reporting flexibility. Users can generate operational reports to track day‑to‑day tax activity and reconciliation reports to confirm that tax balances align between subledgers, tax data, and accounting. Because the reports pull information directly from Oracle Payables and Oracle Receivables, finance and tax teams get a single, consistent view of tax data across the entire transaction lifecycle. This eliminates the need to manually stitch together data from multiple sources.

From a compliance standpoint, Oracle Fusion Tax is designed to support statutory and regulatory reporting with minimal friction. Users can generate reports specifically for tax return preparation, helping ensure accuracy and reducing last‑minute surprises during filing periods. The reporting framework is flexible enough to adapt to local tax rules and country‑specific requirements, which is especially useful for organizations operating across multiple jurisdictions.

Where Oracle Fusion Tax really stands out is in transaction‑level transparency. In addition to summary and reconciliation reports, users can run detailed reports that show exactly how tax was calculated on individual invoices, credit memos, and other transactions. This level of detail is invaluable when investigating discrepancies, responding to audit queries, or simply understanding how tax rules are being applied in real scenarios.

Oracle Fusion Tax also allows organizations to configure a Tax Reporting Solution to support country‑specific reporting requirements. This includes associating tax setups with tax reporting codes and applying document fiscal classifications at the invoice level. These configurations enable more granular, transaction‑based reporting and help meet local compliance needs without heavy customization.

According to Oracle documentation, Oracle Fusion Tax supports reporting based on the tax point date, centralized data extraction for tax auditing and reporting, and multicurrency tax reporting. It also provides predefined reports for several countries, including the US and UK, and gives users the flexibility to build OTBI reports when additional or tailored reporting is required.

All of this is underpinned by the Tax Reporting Ledger. The Tax Reporting Ledger is designed as a single solution for handling complex global tax reporting needs for both sales and purchases. When a tax report job is submitted, the ledger extracts tax‑related transactions and accounting details from Oracle Fusion Receivables, Oracle Fusion Payables, and the Tax Repository. This ensures reporting is based on complete, consistent, and auditable data. More details are available in Oracle’s documentation here:

 

https://docs.oracle.com/en/cloud/saas/financials/25d/fautx/tax-reporting-ledger.html

 

Out of the box, Oracle Fusion Tax also delivers several predefined reports, including the Tax Register, Financial Tax Register, Tax Reconciliation Report, Tax Audit Trail Report, and Sales Tax Report. These standard reports help teams get started quickly and meet common reporting and compliance requirements without building everything from scratch. Additional details can be found here:

https://docs.oracle.com/en/cloud/saas/financials/25d/fautx/oracle-fusion-tax-predefined-reports.html#Running-the-Predefined-Reports

 

Overall, Oracle Fusion Tax takes much of the heavy lifting out of tax reporting. By centralizing tax data, supporting detailed and summary reporting, and offering flexibility for local and global requirements, it allows tax and finance teams to focus less on data gathering and more on analysis, compliance, and control.

Oracle Fusion Tax- Fiscal Classifications and Tax Registrations

Fiscal Classifications provide tax-determination values based on Party, Place, Product, and Process. Oracle Fusion Tax enables you to define tax rules using fiscal classifications to control tax applicability and add greater granularity.

For example, a specific supplier (such as Supplier XYZ) may always be treated as zero-rated or self‑assessed for tax, regardless of other conditions. Fiscal classifications help enforce such scenarios consistently.

I have used fiscal classifications for B2B transactions, specifically for Accounts Payable (AP) invoices. It is important to note that fiscal classification is an optional configuration, unlike some of the other setups discussed in the previous blog.

Party Fiscal Classifications

To define party fiscal classifications, you must first create a Classification Category along with the applicable Classification Codes. These classifications can then be assigned to any party, such as a Business Unit or Legal Entity, Supplier, or Customer, and can be leveraged by tax rules to determine tax treatment accurately.

Create Classification Category

Navigation: Setup and Maintenance-->Financials-->Customers-->Manage Classification Categories

Various Classification Categories- you can select any category and add new codes/additionally create new classification categories and related codes.

Create Party Fiscal Classification

Navigation: Setup and Maintenance-->Financials-->Customers-->Manage Party Fiscal Classification

Similarly you can create Product Based Fiscal Classification

Tax Registrations

Tax Registrations can be created for First Parties or Third Party Suppliers

Tax registration in Oracle Fusion Tax represents the official tax identity of a party (such as a legal entity, business unit, supplier, or customer) with a tax authority, and it is a key driver for tax calculation, reporting, and compliance.

What Tax Registration Means

A tax registration captures details such as:

Tax Registration Number (for example, GST, VAT, HST, or Sales Tax number)

Tax Regime and Tax

Issuing tax authority

Effective dates

Registration status (active, inactive)

Oracle Fusion Tax uses this information to determine whether tax should be charged, self‑assessed, or exempt, and how it should be reported. (Source: Oracle Help Center)

Navigation:

Setup and Maintenance--> Financials-->Transaction Tax-->Manage Tax Registrations

Configuring Fiscal Classifications and Tax Registrations effectively in Oracle Fusion Tax is critical for achieving accurate tax determination, compliance, and reporting. While tax registrations establish the legal eligibility for charging, self‑assessing, or recovering tax, fiscal classifications add the necessary business context to apply tax rules with greater precision.

When used together, these configurations enable organizations to handle complex scenarios such as zero‑rated suppliers, reverse‑charge mechanisms, and B2B transactions with confidence. Although fiscal classifications are an optional setup, they can significantly enhance tax accuracy and flexibility when standard tax rules alone are not sufficient.

A well‑designed tax framework in Oracle Fusion not only reduces manual intervention and errors but also ensures consistency across transactions and readiness for audits and regulatory changes. Thoughtful planning and alignment with business and statutory requirements are key to unlocking the full potential of Oracle Fusion Tax.

Advanced Tax Configuration

In the previous blog, we explored a simple tax model for US Sales and Use Tax using foundational tax configuration. However, as in real life, things are rarely that simple.

When tax scenarios become more complex—such as when certain products must be tax-exempt or specific parties need to be charged additional tax—we must move beyond basic setup. In these cases, Advanced Tax Configuration is required to accurately address the business and regulatory requirements.

Advanced Tax Configuration includes the following components:

• Determining Factor Sets

• Condition Sets

• Formulas

• Rules

• Registrations and Classifications

These components work together to evaluate complex tax conditions and calculate the correct tax outcomes. To ensure advanced tax functionality works as expected, each component must be configured in the correct sequence, which we will walk through in detail in the following sections.

Tax Determining Factor Sets

A Tax Determining Factor Set is a logical grouping of transaction attributes—such as party (customer or supplier), product, geography, or business process—used to define conditions within tax rules. These factor sets evaluate transaction data to determine how tax should be applied, calculated, and reported. (Source: Oracle Help Center)

Party--> Customers or Suppliers

Place--> Location (Bill From, Ship To, Ship From)

Product--> Item

Process --> P2P Process, O2C Process

Navigation: Setup and Maintenance-->Financials (Offering)-->Transaction Tax-->Manage Tax Determining Factor Sets

Conditions Sets

Tax Condition Sets in Oracle Fusion Cloud Financials define a structured set of criteria used within tax rules to determine how tax should apply to a transaction. They evaluate specific transaction attributes—such as party (customer or supplier), product, geography, or business process—to check whether a particular tax outcome (for example, a specific tax rate) is applicable, thereby enabling accurate and precise tax calculation. (Source: Oracle Help Center)

Navigation: Setup and Maintenance-->Financials (Offering)-->Transaction Tax-->Manage Tax Condition Sets

Tax Rules

Oracle Fusion Tax Rules are configurable, step-by-step logic components within Oracle Cloud Financials that automatically determine and calculate transaction taxes such as VAT, GST, and Sales Tax. These rules enable organizations to apply the appropriate tax rates, tax statuses, and recovery rules based on transaction attributes including geography, party, and product, ensuring accurate tax calculation and regulatory compliance. (Source: Oracle Help Center)

Navigation: Setup and Maintenance-->Financials (Offering)-->Transaction Tax-->Manage Tax Rules

Advanced Tax Configuration in Oracle Fusion Cloud Financials provides the flexibility required to handle complex real‑world tax scenarios that go beyond basic tax setups. By carefully defining determining factor sets, condition sets, formulas, rules, and registrations in the correct sequence, organizations can accurately apply exemptions, special rates, and party‑ or product‑specific tax treatments. When designed thoughtfully, advanced tax configuration not only ensures regulatory compliance but also improves consistency, transparency, and accuracy in tax calculation and reporting across all transactions.

In the next and final blog of this tax series, we will shift focus from configuration to tax reporting, where all these setups come together. We’ll explore how Oracle Fusion Cloud Financials enables accurate tax reporting, reconciliation, and compliance, helping organizations turn complex tax calculations into meaningful and auditable reports.

Oracle Lease Accounting – Part 2: Configuration and Expense Lease Execution

 

In Part 1 of this blog series, we laid the foundation by exploring the fundamentals of Oracle Lease Accounting and understanding how the solution supports compliance with modern leasing standards such as ASC 842 and IFRS 16. With the conceptual groundwork in place, it’s time to move from theory to hands-on execution.

In Part 2, the focus shifts to configuration and execution, where we’ll walk through how to set up Oracle Lease Accounting for an expense lease and demonstrate the end-to-end process within the application. This includes key configuration steps, important functional considerations, and a practical demo that shows how an expense lease flows from setup through accounting and reporting.

Whether you are a functional consultant, implementation lead, or finance professional looking to deepen your understanding of Oracle Lease Accounting, this part of the series is designed to help you confidently translate requirements into a working solution. By the end of this walkthrough, you should have a clear view of how expense leases are configured, processed, and accounted for in Oracle Fusion.

 

Initial Configuration

 

Setup and MaintenanceàFinancials (Offering)àLease Accountingà Manage Lease Accounting Configuration

 

Click on + Sign  (System Options)

 

Ensure the select option you have is selected as Select System Options

Select Business Unit

Primary Accounting Standard- Options are ASC842, IFRS or Japanese GAAP

If you have Secondary Ledger- you can select Secondary Accounting Standard as well.

Select Interest Calculation Method: Daily Compound Interest or Periodic Compound Interest.

Daily Compound Interest: daily compound interest refers to the way interest expense on a lease liability is calculated and accrued by compounding the interest every day, rather than monthly or annually.

Period Compound Interest: Calculation as per periods -select the calculation calendar if you want to select Period Compound Interest (Monthly,Semi-Monthly)

Auto Lease Numbering: Lease Numbering (Automatic or Manual)

Lease Transaction Approval: Enable Approvals for Lease Transaction Yes or No

Default Currency Conversion Type: Select Currency Conversion

Ledger Name: Enter Primary Ledger Name

Amortization Calculation Frequency: Frequency of Amortization Calculation (Daily,Monthly, Yearly)

Asset Numbering: Automatic or Manual

 

As I am currently configuring expense leases, I will focus only on the related setup.

Select Item Master

Payables Integration: Mark it as Yes if you want to create AP Invoices for leases

Require Property Definition: If you want to select the property which you are the lessee you can select it. Recommend to select as  NO

 

Save and Close

Lets Create Discount Rate Index

 

Click +

Select Business Unit

Index Name: Name of the Discount Rate Index

Index Rates

Start Date

Discount Rate

Final (Please note, the discount rate index will not be active till its marked as Final)

 

Lets create Expense Lease Template now

 

Quick Entry Form will Open- enter required information

Business Unit

Asset Type (Equipment or Property)

Template Type (Payment or Option)

Template Name

Payment Purpose (Rent,Depreciation,etc)

Payment Type (Base Rent, Deposit)

Frequency – Monthly, Yearly

 

Enable Generate Invoices if you want Oracle Lease module to create Invoices for you

Enable Lease Liability and Right-of-use if you want Oracle to calculate it for you.

 

Provide Distributions

Save and Close

 

Expense Lease Process

 

Click on Lease

Click on + to create new Expense Lease

Enter following in the quick entry box

Business Unit

Lease Type : Expense

Legal Entity

Lease Number

Asset Type

Lease Start and End Date

Supplier (Lessor Name)

Primary Accounting Classification Method (Finance Lease,Operating Lease,Exempt)

Discount Rate Index

All Data from the template will automatically be pre-populated for you – you can also attach Project Number and Expenditure Organization if you need the lease accounting invoices to be costed in PPM

Next is you create an Asset- provide Asset Number Location, Amortization End Date, Item information to save the same.

 

Enter Payment Information and Accounting Information

 

 

Typically- all accounting information is populated from template- enter data here only if you need to override it at the Lease level

 

 

Validate and Submit the Lease

 

Click on Process Expense Lease Payments task whenever you need to generate the AP Invoices for Payments

Select Payment Processing, Export to Payables and Launch Import Payables Invoice alongwith Process type and Business Unit information to generate invoices- you can schedule the process as well.

You can review the Payment and Invoice Information by Navigating to task Manage Expense Payments

This concludes Part 2 of the Oracle Lease Accounting series, where we focused on configuring the application and walking through the end-to-end expense lease process using a practical demo. By now, you should have a clearer understanding of the key setup decisions, how those configurations impact lease processing, and how Oracle Fusion consistently handles accounting in line with compliance requirements.