FAQs When Creating Joint Venture Receivables Invoices

I've invoiced the partners for a cost transaction incurred in operating the joint venture. Why has this transaction circled back into Oracle Joint Venture Management and invoiced again?

Check if you've used a distributable account as the partner account to create your joint venture receivables invoices. Partner accounts are written in the Revenue accounting class in Oracle Fusion Cloud Financials. Accounts set up as distributable for your joint venture will pull in corresponding cost transactions into Joint Venture Management regardless of whether a transaction was already processed and invoiced to partners.

To prevent invoice and journal transactions generated by Joint Venture Management from being identified and processed by Joint Venture Management again, you must perform one of these configurations:

• Override a segment of the partner account with an account that isn't identified as distributable in your joint venture definition.

  To do so, you set up subledger accounting to replace a segment value that creates an account that represents reimbursement transactions for your joint venture. See Set Up Partner Accounts for Joint Venture Receivables Invoices for more information.

• Enable the "Exclude joint venture transactions" option in your joint venture definition.

  See Exclude Joint Venture Invoices and Journals from Oracle Joint Venture Management Processing for more information.

Why can't I create invoices for joint venture distributions that originated from transactions with Liability account type?

You can create invoices only for joint venture distributions that originated from transactions of account type Assets, Expense, and Revenue. The "Identify Joint Venture Transactions" process marks the transactions of other account types (for example, Liability) as "Distribution Only" when these are identified as joint venture transactions. The distributions created from these transactions are marked as "Distribution Only" and can't be invoiced.