How do per-structure routing and overrides work?

How do per-structure routing and overrides work?

Structures can differ in routing and treatment without duplicating your cost data.

Routing per structure

Each structure routes materials, subcontracts, travel and ODC on its own. For example, one structure sends materials and subcontracts to MSOH while an alternative sends materials to the overhead base. The routing rules still apply (see How do I route materials, subcontracts, travel and ODC?).

Allocation data per structure

If a structure has an intermediate pool such as Facilities, it needs driver data (see How do I enter intermediate pool allocation data?). Choose the structure at the top and each one can have its own. A structure you leave alone matches the Baseline.

Review and structure overrides

This tab lets one structure treat something differently from the others. Everything you don't override uses the shared mapping.

  1. Open Review & structure overrides.
  2. Override a whole category: for example, in the structure without MSOH, treat Facilities expenses as overhead expense instead of an intermediate pool.
  3. Override a single account: an account override wins over its category override. For example, move telecommunications to G&A while the rest of Facilities stays in overhead.
  4. To start another alternative from the same overrides, use Copy all overrides from.

If this doesn't work: if a red message says cost data is left out of a structure, see 'Cost data not used by this structure' red message.

Watch: Per-structure routing and overrides, from 1:13

Full guide section: Enter Cost Data

Related: How do I add alternative structures to compare? | How do I compare structures side by side? | How do I route materials, subcontracts, travel and ODC?