Entity Explorer

Core information for homeowner associations including identifying data, contact information, and contract terms. Operational configuration (billing, accounting setup, etc.) is managed separately.

Associa branch regions (the C3 ACCESS_REGION analogue) that group the branch locations managing associations. Loaded before locations.

Associa branch locations (the C3 ACCESS_LOCATION analogue) that manage associations and roll up to a region. Each association is managed by one location.

Core information for unit type classifications including identifying data and assessment details. Units can reference types by any unique identifier (ID, name, or composite).

Core information for individual properties or units within the community. Units are the physical properties (homes, condos, lots) that have accounts and are associated with owners/tenants.

Core information for billing accounts for units or properties. Accounts are where charges are applied, payments are received, and balances are tracked. THIS DATA IS REQUIRED for migration.

Core information for people associated with accounts in specific roles. Each member has an account-level role (owner, tenant, or occupant) and optionally one or more association-level roles (board member, CAM). This represents the minimum data needed to identify people and their relationships to billing accounts and the HOA.

Partner banking institutions (the shared bank identity — name, routing, address, contact) that bank accounts reference. Deduplicated per organization and loaded before bank accounts.

Charge/assessment type codes that categorize different types of charges billed to homeowners.

Delinquency status codes that track collections workflow stages for accounts with overdue balances.

Billable item codes for charges the management company bills back to the Association (postage, copies, professional services, accounting fees, etc.).

Core information for association bank accounts (operating and reserve): designation, flags, account number, balances, check routing, check return address, and GL link. The bank institution identity (name, routing, address, contact) lives on the separate Banks entity and is referenced by Bank ID.

Core information for recurring assessments or fees applied automatically to accounts based on unit type and schedule. This is how regular HOA dues, maintenance fees, and other periodic charges are defined.

Late fee, late interest, and friendly reminder rules for an association. One configuration per association, ingested through the pipeline.

Billing method, coupon providers, remittance address, and statement/coupon text for an association. One configuration per association, ingested through the pipeline.

Core information for additional mailing addresses for accounts. Use when correspondence should be sent to an address other than the property address (e.g., owner's home address, property manager's office, power of attorney).

Core information for notes and annotations associated with accounts, providing additional context and historical record of account-related information.

Physical items tracked by the HOA and issued to homeowners, requiring deposits, tracking, or return management (gate remotes, pool passes, parking permits, keys, etc.).

Core information for transaction and balance data for accounts. Supports multiple transactions per account.

Homeowner authorization for automatic payment (ACH) of assessments. Contains sensitive banking information that must be properly secured.

Investment-specific detail (type, term, rate, maturity) for an account, attached to a parent bank account that holds the shared identity. Contains sensitive account information that must be properly secured.

Core information for service providers and contractors including identifying data and contact information. Operational configuration (payment methods, tax processing, work orders) is managed separately.