Skip to content

Companies, Divisions, Areas

The corporate hierarchy in SMART is Company → Division → Area → Community → Project → Lot. Almost every report and security check anchors on one of these.

At a glance

  • 6 levels: Company (legal entity, owns BC books) → Division (region) → Area (market) → Community (named neighborhood) → Project (phase / product line) → Lot (ProjectID + BuildingID + UnitID).
  • 14 Companies, 14 Divisions, 47 Areas, 918 Communities, 775 Projects, 29,386 Lots in the test database.
  • Every dollar lives inside a Company. Switching a Lot’s Company is a serious operation.
  • IDs: ProjectID is char(8), BuildingID is char(3), UnitID is char(4).
1Company
A legal entity with its own QuickBooks / Business Central books.
2Division
An operating region inside a company (e.g. Atlanta, Houston).
3Area
A market or geographic area inside the division.
4Community
A named neighborhood being marketed and sold.
5Project
A book of construction inside a community (a phase or product line).
6Lot
The addressable home: ProjectID + BuildingID + UnitID.

As of the test database snapshot:

LevelTableRows
CompanyCompany14
DivisionDivision14
AreaArea47
CommunityCommunity918
ProjectProject775
LotLot29,386

The headline rules: dollars at Company, sales / permissions at Division, plans / cost books at Project.

What's configured at each hierarchy level
  • Company owns the financial books. POs, bills, deposits — every dollar sits inside a Company. Switching a Lot’s Company is rare and a serious operation (Transferring Lots to a Different QuickBooks Company Backfill.sql).
  • Division drives reporting, sales-team assignment, and many access permissions.
  • Area groups communities for the regional teams.
  • Community is what marketing and the public see.
  • Project is the unit we build to. Standard Plans, Cost Books, Price Books, and lot lists are all attached to a Project.
AppWhere
SMARTAdministrationCompany, Division, Area, Community, Project
SMART 2.0administration/ and project-management/ modules
Trade Portalcommunities.aspx
Builder PortalDefault project in session (DefaultProject.aspx under Admin); landing page is Schedule.aspx