Receivables

No Ship to on intercompany invoices – solution

This posting is a direct copy from the Oracle website based on note 1048431.6

For years we have been using a work around but Oracle have now provided the following solution to help with the missing ship-to information badly needed to correctly determine the tax.

Reference INCIAR – Ship-To/Shipto Address Does Not Appear On Intercompany AR Invoices (INCIAR) (Doc ID 1048431.6)

GOAL

The “ship to” address is not appearing on intercompany AR invoices.

The “ship to” address for Intercompany AR Invoices is not populated after the AR Autoinvoice process is completed.

This document includes all version of Oracle E-Business Suite 11i and Release 12.

SOLUTION

Continue Reading

Oracle R12: The problem with using Legal Entities for Tax!

So, here is my problem. We have a client who has a UK legal entity but has several locations globally that are registered for local indirect tax and some other reporting but are not legal entities in their own right. According to Oracle, these are legal entity Establishments.

Oracle Definition of Legal Entity Establishment

“Legal Establishment: First party legal entities identify your organization to the relevant legal authorities, for example, a national or international headquarters. First party legal establishments identify each office, service center, warehouse and any other location within the organization that has a tax requirement. When you create a legal entity, the system automatically creates a legal entity establishment. You can create additional legal establishments according to your needs. For each legal establishment there are one or more tax registrations, depending upon the tax requirements of the applicable tax authority.”

More can be found at note 1064366.1

So what is wrong?

Continue Reading

Oracle R12 – Withholding Tax on Receivables (AR) Transactions

This article explains how in Oracle R12, you can create an invoice that has the correct total amount but with the lines adjusted down in accordance with the potential to automatically adjust the AR transaction to record the withholding tax.

To do this you will need to create a separate tax regime which takes a % based on the compounded GB VAT tax rate, as shown below.

Oracle R12 Withholding Tax for AR

 

 

 

 

 

 

In the example above you will see the original line amount was for 1000 but had 20% tax applied to it. By withholding 20% of the total invoice you would get 240, meaning that the original line amount of 1000 is now actually only 760.

By modifying the auto-accounting rules you can set the withholding tax line to be the same as the revenue account. In the example below you can see that 1. Is the original tax line and 2. Is the withholding tax line.

Oracle R12 Withholding Tax for AR

 

 

 

 

 

 

 

Whilst withholding tax is only applied to the AP transaction, it is often required to show what amount of withholding tax is required on the AR invoice that is sent to the customer. With a modification to the way the invoice is formatted, it is possible to automate the creation of the withholding tax line on the AR transaction without actually effecting any of the normal tax calculation.

 

 

Oracle eBTax – How to populate the Tax Date automatically

For some reports for European VAT, the Tax Date of a transaction needs to be populated. This is an unreasonable task to expect users to do as it can only be done manually meaning that for every order that is imported, the transaction would need to be uncompleted and the tax date would have to be manually updated!

Oracle offer a patch for the supported countries to populate the tax date from Orders but this does not work if you do not have the localisations turned on which could be the case if you are a German entity who has a site in Hungary and charges Hungarian VAT when they ship from there. The Operating unit is German and the localisation country would be Germany but the tax in this instance is Hungarian! Another reason why this does not always work is that for any manual transactions, these would also need to be manually updated.

So, how can we automate this?

Very simply!

Create a request that does the following “update jg_zz_vat_trx_details set tax_invoice_date = trx_date where tax_invoice_date is null“. Then create a request set which first has the EMEA VAT SELECTION PROCESS and then your request to update the tax date.

Now there is no need to populate any of the tax dates as these will automatically take the transaction date if the tax date is NULL but is the user does put in a tax date manually, then this will be chosen instead.