Entities

These entities form the absolute core of the system and are required in the Minimum layer. Understanding these entities and their relationships is essential for successful implementation.

View all entity documentation →

Required Entities

The following entities must be loaded in as pre-requisites for migration:

1. Organization - Your management company
2. Implementation Waves - Phased rollout groups for organizing migrations
3. Associations - The HOAs/communities you manage
4. Wave Associations - Links associations to waves and stores operational setup
5. Units - Individual properties
6. Unit Types - Property classifications
7. Members - People associated with accounts (owners, tenants, occupants)
8. Accounts - Financial accounts
9. Operating Bank Accounts - Primary association bank accounts
10. Recurring Charges - Automated fee schedules
11. Delinquencies - Late fee and interest rate configurations

Important Schema Changes:

• wave_id and operational_setup have been moved from Associations to Wave Associations
• Wave Associations table provides the link between associations and implementation waves
• Operational setup (delinquency config, billing config, fiscal settings) is now stored in Wave Associations

Additional Entities

Standardization Entities

12. Standard GL Accounts - Associa's reference chart of accounts
13. Corporate GL Accounts - Your organization's GL accounts
14. Association GL Accounts - Association-specific account overrides
15. Standard Vendor Types - Associa's reference vendor types
16. Vendor Types - Your organization's vendor types
17. Vendor Type Mappings - Mappings between your vendor types and standards
18. Vendors - Vendor master data

Financial & Payment Entities

19. Investment Bank Accounts - Reserve and investment accounts (optional but recommended)
20. Direct Debits - Automatic payment arrangements (optional but recommended)

Account-Related Entities

21. Account Addresses - Mailing addresses for accounts
22. Account Transactions - Financial transaction history
23. Account Notes - Important account-level notes and documentation
24. Emergency Contacts - Emergency contact information for members

Load Sequence Overview

Entities are numbered in the recommended load sequence based on data dependencies:

• Lower numbers first - These entities have fewer dependencies and form the foundation
• Higher numbers later - These entities depend on lower-numbered entities being loaded first
• Organization (#1) - All of your data will be tied to your org. It will be set up for you by TownSq.
• Follow the chain - Each entity depends on one or more entities with lower sequence numbers

Common Questions

Can I skip the Recommended layer?

Technically yes, but you'll miss significant efficiency gains. The Recommended layer typically delivers a 30-50% reduction in manual work and pays for itself within months through operational savings.

What if I don't have data for a Minimum entity?

You'll need to gather this data before go-live. The Minimum layer represents the absolute minimum for system functionality. Missing data here will block critical operations.

Can I add Full layer entities earlier?

Absolutely! The layers represent a recommended path, not hard requirements. If you already have high-quality data for Full layer entities, include them in your initial migration.

How do I handle missing data in Recommended/Full entities?

Start with what you have and fill gaps over time. For Recommended entities, partial data still provides value. For Full entities, you can even start with empty entities and populate them through normal operations.

Next Steps

Visit the comprehensive entity documentation to explore detailed field requirements, validation rules, and relationships for each entity.