Skip to main content

How detailed should the production code structure be?

Start with fewer production codes. Put several contracts under one code and use groups, instead of one code per supplier.

We recommend starting with fewer production codes, especially while you are learning the way of working. A very fine-grained structure creates a lot of extra follow-up. In AIMZ you don't need one production code per supplier, because several contracts can sit under the same code and be followed up separately.

How to think when you build the structure

  1. Start simple. How fine-grained the structure should be depends on the size of the project and the contract type, but fewer codes are easier to keep up to date.

  2. One code can have several contracts. A code for technical trades can, for example, have one contract for the plumber and one for the electrician. Many people create extra codes because it is cumbersome to follow up several contracts on one code in Excel, but in AIMZ it isn't necessary.

  3. Use groups for structure. If you need a better overview, give the production codes a group, for example Technical, Setup and Operation or Other goods purchases, instead of creating more codes.

  4. Split where you need the final figure early. On large projects it can pay off to split own production into phases, so you know what each phase ended at when it is finished.

A production code opened from Prod. codes. 1: the group the production code belongs to. 2: two contracts on the same production code.

Good to know

The level of detail in AIMZ doesn't have to be the same as in the accounts, but if AIMZ is more detailed than the accounts, invoices must be allocated manually. Keep the structure at a level the accounts can also post to.

Related questions

Did this answer your question?