Required Data

The core entities a branch must provide (breadth) and the minimum fields within each (depth) for a successful onboarding.

Two dimensions of "required"

A successful onboarding needs data in two dimensions:

Breadth — which entity types are included.
Depth — which fields within each entity are populated.

The authoritative, always-current list of every entity and field — with which are required — is the Entity Explorer. This page is an orientation; the Entity Explorer is the source of truth.

Required breadth: core entities

Provide these core entity types. They load in dependency order, rooted at the association — each depends on the ones above it.

Order	Entity	What it is
1	Organization	The management company (set up by Associa).
2	Associations	The HOAs being managed — the root every other entity links to.
3	Association configuration	Each association's billing and delinquency configuration, and fiscal-year months.
4	Unit Types	Property classifications that drive assessment amounts.
5	Units	The individual properties.
6	Accounts	Financial accounts that track balances and payments.
7	Members	People — owners, tenants, occupants — to bill and contact.
8	Bank Accounts	Operating (and, optionally, investment) bank accounts.
9	Recurring Charges	Regular assessment schedules.
10	GL Accounts, Charge Types, Delinquency Statuses, Reimbursables	The source codes that are standardized against Associa/C3 standards.

Implementation waves are not provided as data — they're planned in the app during Wave Planning. Association billing and delinquency configuration are ingested with the association's data, not entered in the app.

Required depth: minimum fields

Every entity has fields the system needs in order to link and use the record. A few of the most important:

Organization — name; your unique ID.
Associations — name; external ID (your unique ID for the association); organization ID.
Units — unit number; unit ID; the association it belongs to.
Unit Types — name (e.g. "SFH", "2BR Condo"); the association it belongs to.
Accounts — account number (your unique ID); the unit it belongs to; current balance.
Members — name; member ID; the account they're associated with; role (owner, tenant, or occupant); a primary contact (email or phone).
Bank Accounts — the association; account number; routing number; partner bank name; whether it's the primary operating account.
Recurring Charges — the association; the unit type the charge applies to; charge type; assessment amount; frequency; begin date.

Consult the Entity Explorer for the complete required-vs-optional field list per entity.

Optional and supplemental entities

These add functionality and can come later:

Financial — investment bank accounts, direct debits, account transactions, account addresses, account notes.
People — board members, CAMs, emergency contacts.
Vendors — vendor master data and association-vendor relationships.
Geography — regions and locations (access hierarchy).
Tracked Items — physical items such as gate remotes, keys, and passes.

Why breadth and depth both matter

Without the required entities, the system can't track properties (Units), bill (Accounts), or process payments (Bank Accounts). Without the required fields — especially your unique IDs — records can't be linked or kept in sync. See the Data Identity Model for why your IDs matter.

Questions?

See the FAQs for common questions about entity requirements and load order.