Many implementations default the Place of Supply to:

• Ship To
• Ship From
• Warehouse location
• Logistics location

In practice, this often creates inconsistent tax behaviour, missing ZX_LINES records, reporting issues, and unnecessary rule complexity.

After working on EBTax implementations across multiple jurisdictions and GCC VAT rollouts, the most stable and scalable approach is almost always the following:

·Default Place of Supply = Bill From for AR and AP

·Only use Ship To / Ship From as exception-based rules

·Use Tax Status rules rather than Tax Rate rules

·Only classify products when they differ from the standard treatment

This article explains why.

The Core Principle: Place of Supply Activates the Tax Regime

The single most important thing to understand in Oracle EBTax is this:

Place of Supply determines whether the tax regime activates at all.

Only after the regime activates will Oracle:

• derive tax status
• derive tax rate
• create ZX_LINES records
• report transactions in the tax register

If your Place of Supply logic prevents the regime from activating, Oracle does not create a “0% tax” result — it creates nothing.

This is why many users see:

• NULL tax in AR
• no ZX_LINES records
• missing tax register entries

even though they expected a 0% reporting line.

Why Bill From Is the Best Default

The reason Bill From works so consistently is because it is tied directly to the legal entity or supplier registration country.

That makes it the most reliable determining factor.

By contrast:

Ship To

• may not exist on all transactions
• is often optional
• varies between modules and transaction types

Ship From

• is frequently inconsistent
• may reference warehouses rather than registrations
• becomes unreliable with virtual warehouses, drop shipments, or 3PL providers

Warehouse-Based Logic

Warehouses are logistics concepts, not tax registration concepts.

The warehouse location is not always the jurisdiction where the legal entity is registered for VAT/GST purposes.

Recommended Default Design

The best practice approach is normally:

• Default Place of Supply = Bill From if calculating tax for both AP and AR
• Default Place of Supply = Bill From if only using tax for AP
• Use Ship To / Ship From only as exception rules

This creates a stable baseline where the correct tax regime consistently activates.

Why ZX_LINES Sometimes Do Not Get Created

A very common misunderstanding is assuming that a 0% tax result and “no tax regime activation” are the same thing.

They are not.

If the tax regime activates and Oracle derives:

• a Tax Status
• linked to a 0% Tax Rate

Then Oracle creates:

• ZX_LINES
• tax register reporting
• tax audit records

However, if the Place of Supply logic prevents the regime from activating entirely, Oracle produces:

• NULL tax
• no ZX_LINES
• no tax register entry

This distinction is critical.

Do Not Classify Every Inventory Item

Another very common mistake is assigning tax classifications to every inventory item.

If 95% of items are standard rated, there is no benefit in explicitly classifying all of them as standard rated.

Instead:

• make the standard VAT rate the default regime treatment
• create rules only for exceptions

Item fiscal classifications should normally only be used for:

• zero-rated items
• exempt items
• reduced-rate items
• special treatments

This dramatically reduces maintenance overhead and simplifies rule management.

The Correct Way to Return 0% Tax

The correct approach is not to stop the tax regime from activating.

Instead:

1.  Allow the regime to activate

2.  Return a reporting Tax Status linked to a 0% Tax Rate

The best practice approach is normally:

• create a Place of Supply rule using Bill From
• create a Tax Status rule
• return a reporting status with a linked 0% rate
• prioritise the rule before standard-rate rules

This ensures:

• ZX_LINES are created
• tax register entries exist
• reporting remains complete
• transactions show 0% instead of NULL

AP Imports Require an Exception Rule

Imports are one of the main scenarios where Bill From alone is insufficient.

For example:

• Supplier = Saudi Arabia
• Legal Entity = Bahrain

If Place of Supply remains Bill From, Bahrain VAT will never activate because the supplier country is Saudi Arabia.

The standard solution is:

• If Bill From != Bahrain
• And Bill To = Bahrain
• Then Place of Supply = Bill To

This allows imported AP invoices to activate Bahrain VAT correctly.

The Exception: Multiple VAT Registrations

There is one major exception to the standard Bill From design.

This occurs when the same legal entity or operating unit has multiple VAT registrations.

For example:

• Legal Entity established in Bahrain
• Additional VAT registration in UAE
• UAE customers must be charged UAE VAT

In this situation, global rules alone are not sufficient.

The Correct Multi-Registration Design

The UAE tax regime should still default to:

• Place of Supply = Bill From

However, this alone would never activate UAE VAT because the Bill From country remains Bahrain.

The correct approach is to create an operating unit-specific Place of Supply rule:

• Configuration Owner = Bahrain Operating Unit
• Condition = Ship To country = UAE
• Result = Place of Supply = Ship To

This activates UAE VAT only for:

• that operating unit
• that customer geography

However, once UAE VAT is activated, Bahrain VAT must also be suppressed.

So you create a corresponding Tax Applicability rule:

• Configuration Owner = Bahrain Operating Unit
• Condition = Ship To country = UAE
• Result = Tax Not Applicable

This prevents dual taxation.

The Overall Design Pattern

The most stable Oracle EBTax architecture is generally:

1.  Use Bill From as the default Place of Supply

2.  Use Ship To only as an exception rule

3.  Use Tax Status rules rather than Tax Rate rules

4.  Only classify exception products

5.  Scope secondary VAT registrations using Configuration Owner rules

6.  Suppress the originating regime with Tax Applicability rules

7.   

This approach consistently produces:

·stable tax calculations

·proper ZX_LINES creation

·cleaner reporting

·lower maintenance

·scalable multi-country tax designs

When configured properly, Oracle EBTax is actually one of the most powerful and flexible enterprise tax engines available.