Skip to content
ERPNext Data Model
Esc
navigateopen⌘Jpreview
On this page

Setup

Company, Item Group, UOM, Territory, Employee and the other cross-cutting masters every other module links to.

Organisation-wide masters that nearly every other module points at: Company, Item, Customer, Supplier, Brand, UOM, Territory, and the sales/purchase person hierarchies. This is the root of the dependency graph.

What it does

Setup holds the masters that have no module of their own but that everything else depends on. A Company is the top-level accounting and reporting boundary; Item Group, UOM, Brand, Territory, Customer Group and Supplier Group are the classification trees that pricing, taxes and reporting slice by. Get these right and most of an implementation is done — they are referenced from almost every transaction in the system.

Key features

  • Company — the multi-company boundary. Every ledger row, warehouse and default account hangs off it.
  • Classification trees — Item Group, Customer Group, Supplier Group, Territory and Sales Person are nested-set trees used for pricing rules, taxes and reporting rollups.
  • Units and terms — UOM with conversion factors, Incoterm, Terms and Conditions, and print/naming defaults.
  • Party-adjacent masters — Employee, Department, Designation, Sales Partner and Authorization Rule.
  • Global defaults — Global Defaults, Naming Series and per-company default accounts drive what every new document is pre-filled with.

Entity relationships

Each diagram below is one connected cluster of entities. Edges are labelled with the fieldname that carries them — see relationship notation for how to read the crow’s feet.

Company

Company anchors the setup model: these clusters show the organizational masters and default records that are scoped to, or selected by, a legal entity.

Split across 4 diagrams so each stays legible; Company repeats in each.

Document composition

Parent documents and the child tables they own.

Entity reference

Look it up

Was this page helpful?