A UAE company needs a few things to exist before any of the features can do useful work — a UAE tax-configuration row, and sensible print defaults where the printing features are present. In many systems that is a checklist somebody has to remember, and the day it is forgotten is the day a return comes out wrong. Odoone does not leave it to memory.

The mental model: it runs itself. Per-company setup fires on two events. It runs when a UAE chart of accounts is loaded, and it runs when the pack is installed over companies that are already fiscally AE. There is no button to press, no wizard to walk through and no checklist item to tick. If you have loaded the chart or installed the pack, it has already happened.

What it creates. It creates the UAE tax-configuration row, and it seeds print defaults where those features are installed. That last clause carries real weight: the step is a no-op for any feature whose module is not installed, so it will not create excise settings on a company that never ticked Excise Tax, and it will not seed print defaults for a print pack that is not there. The automatic setup respects the choices you made in Lesson 3.

Idempotent — the word that should let you relax. Running the setup again is safe. It only creates what is missing and never overwrites your edits. That is what idempotent means here, and it is the reason you can reload a chart, upgrade the pack or reinstall it without first taking a backup of your carefully adjusted defaults. Software that re-seeds on every upgrade teaches people to fear upgrades; this does not.

How to make it run again, if you ever need to. Reload the UAE chart, or reinstall or upgrade the pack. Those are the same two events that triggered it the first time, and they are the whole answer — there is nothing to run by hand and no hidden maintenance action to hunt for under a technical menu.

Worked example. On Marina Ridge Trading LLC the UAE chart is loaded on the Sunday, and the tax-configuration row is created in the same action without anyone asking for it. Over the following week the finance manager adjusts a print default to match the company's own paperwork. The next month the pack is upgraded, per-company setup runs again, and the adjusted default is still exactly as it was left. Only genuinely missing records were created.

The failure mode. "Per-company setup did not run." It is triggered by loading the UAE chart and by installing the pack, so reload the chart, or reinstall or upgrade the pack. Then check the second half of the answer before you conclude anything is broken: the step is a no-op for any feature whose module is not installed, so a setting you expected may simply belong to a feature you never ticked. Lesson 4's empty-section rule and this one are the same rule seen from two directions.