Skip to content
ERP Expert

Station 8 of 10

Tax and e-invoicing in Oracle Fusion

Ahmed Hassan Algammal6 min read

What you leave this station with

Setting tax by rule rather than per invoice, and knowing the exact line where the product stops and a second invoice starts.

Station seven explained how the journal is written. This station is about the one party that accepts no explanation from you: the state.

It also carries the widest gap on this path between what a demo says and what an invoice says.

Tax: the product’s real strength

The tax engine here is among the strongest at this tier, and its structure is understood once.

Layer What it settles
Regime and jurisdiction Which tax applies, over what geography and legal scope
Status and rate Standard, zero-rated, exempt — and the percentage for each
Determination rules When each applies, by a written condition
Registrations The tax registration number per entity per jurisdiction

The principle that marks out somebody who has mastered it: tax is determined by rule, not selected on the invoice.

Let users pick the rate on every line and you have built a system that errs to the attentiveness of your weakest employee. Write the rules correctly once and you get a correct invoice every time, and a return you can defend.

The four cases that test any Gulf tax configuration:

  • Export outside the GCC — zero-rated, subject to proof of exit.
  • An intercompany sale between two entities in two countries — treated differently from an external sale.
  • A discount at invoice level rather than line level, and its effect on the taxable base.
  • Reverse charge on an imported service — and the journal that produces both sides at once.

Test fewer than four and you have tested nothing.

E-invoicing: where the product stops

Here is the sentence demos dislike: Gulf e-invoicing is not part of the priced core.

That is not an inference or an opinion. It is a reading of Oracle’s own published global price list, where it appears as a separate line under a third party’s name.

Line Price Minimum
Oracle Thomson Reuters Global E-invoicing US$770 per thousand documents per month 10
Global Indirect Tax (Thomson Reuters or Avalara) US$350 per thousand records —

The minimum means from US$7,700 a month for e-invoicing alone — on top of a licence whose own floor is US$75,000 a year, as set out in the system guide.

Three routes are open to a Gulf customer, and there is no fourth:

  1. The priced third-party service above — ready, priced per document, and added to the annual bill permanently.
  2. A local accredited service provider integrated through an integration layer — the common choice in Saudi Arabia and the UAE, and cheaper at volume.
  3. Building the integration in house over the cloud integration layer — a project with a budget, an owner and a test cycle, rather than a setting.

One question exposes all of this in a demo. When somebody says “the system supports ZATCA”, ask: which line item on the quotation, at what price per thousand documents, and who signs off the authority’s accreditation? Three seconds of silence after the question is an answer.

What you need to know about the requirement itself

This station is about the product rather than the legislation, and the legislation is covered where it belongs.

What belongs to this station is one thing: what leaves the system for the provider, and at what quality. An invoice leaving with a missing field is rejected at the authority rather than at the provider, and the fix goes back to the master data you designed in station three. Get the tax registrations and entity addresses right there and this problem never appears.

Arabic on screen

Oracle lists Arabic among the language packs for Fusion cloud applications. The difference between a language appearing in a list and a screen working in it is what decides user acceptance.

The practical rule: ask to see the screen in Arabic during the live demo. Three screens specifically: supplier invoice entry, a balance report, and a printed sales invoice. The last one is what reaches the customer and the authority, and it is the one discovered late.

And recall what station two said: machine translation of the training material helps comprehension, and the term the exam asks about is the English one.

What you actually do in this station

  • Write the tax rules for the four cases above for a Saudi company and its UAE subsidiary.
  • Post a reverse charge invoice and read both sides of the journal.
  • List the fields the electronic document requires, and mark where each is populated in master data.
  • Calculate annual e-invoicing cost for a company issuing 40,000 invoices a month at the published price above. The number alone changes your recommendation.
  • Ask any partner you speak to for screenshots of those three screens in Arabic.

The three commonest mistakes

One: assuming e-invoicing is inside the price. Discovered after signature, and then either paid for or the project slips.

Two: selecting the tax rate by hand on the invoice. The return becomes a reflection of staff attentiveness rather than of written rules.

Three: deferring the Arabic printed invoice test. Its problems surface in the last week before go-live, which is the worst week to find them.

The acceptance test for this station

  1. Explain the four layers of the tax engine and each one’s job.
  2. Write a determination rule for an export outside the GCC and another for an intercompany sale.
  3. Name the separate e-invoicing line and its price, and compute a year at a stated volume.
  4. Name the three routes to e-invoicing and the drawback of each.
  5. Name the three screens asked for in Arabic in a demo, and why the third matters most.

What comes next

You know where the product stops in front of the state. The next station is where it stops in front of you: extensibility and quarterly updates — a four-rung ladder, and four mandatory updates a year you cannot defer.