Skip to content

Setting up the category tree

Updated:

Finer purchasing categories beside the fixed nine, with UNSPSC, CO₂ factors and GHG categories.

Open Settings in Fiatto
In this article

Under Settings → Category tree (/dashboard/settings/categorieboom, Master data group) you build a hierarchy of purchasing categories, up to five levels deep. The tree sits beside the fixed list of nine purchasing categories, not in its place: every branch maps back to one of the nine, so existing requests, reports and postings keep working. As long as the tree is empty, nothing changes. The page is for admins.

Steps

  1. Open Settings → Category tree and click Add the nine standard categories for the top level.
  2. Refine below them with Add a category: choose the Parent category, a code, a name, the Code scheme (Own, UNSPSC or eCl@ss) and optionally the Mapped purchasing category (empty = inherit from the parent).
  3. Working with UNSPSC? Under Import UNSPSC, paste one eight-digit code per line, a semicolon and the description, then click Import. Fiatto adds missing intermediate levels; existing codes stay unchanged.
  4. Optionally record per category: a CO₂ factor (kg CO₂e per €), the GHG Scope 3 category, a CN code for CBAM (8 digits) and whether the category is Outside procurement compliance (such as taxes or insurance). These values also apply to everything below, until a subcategory gets its own value.
  5. Via Edit you move a category (Move to) or set it inactive; no new work starts under an inactive category.

Tips

  • Automatic matching: when a request line arrives via punchout with a classification code, Fiatto looks up the matching category in the tree; if the finest code does not exist, it climbs to the nearest level that does.
  • Core or non-core: via Edit, give a category the class Core (direct, cost of sales) or Non-core (indirect, overhead), or let it inherit with Inherit from the parent category; a deeper category may differ. The Class column shows whether the class is its own or inherited. Under Suggestions for core and non-core, Fiatto suggests a class based on the postings of the last twelve months when at least 80% of the measured spend points one way; you decide with Accept or Ignore. If the books point the other way from your own classification, you see it under The books point the other way.
  • The tree feeds, among other things, mandates and document requirements per category in the purchasing policy, category budgets in budgets, the category cockpit in spend analytics and the CO₂ footprint.
  • Deleting also removes all subcategories; request lines keep their purchasing category.
  • Restore an exported tree via Promote category tree (link at the bottom of the page). Do this before the GL mapping policy, which refers to categories.
Was this article helpful?
View all articles in this topic

Find another answer

A task, feature or short question is enough.