Glossary

A

Association — a homeowners association (HOA) or similar community organization. The root entity of the data model; every other entity references an association.

Association Mapping — mapping a source code for a single association, used as an individual override of a global mapping. See Standardization.

Assessment — a fee charged to owners for association services and maintenance.

B

Branch — a newly acquired or partnered management company being onboarded into C3. Also the team affiliation for that company's staff (NewCo / Source System).

Billing Configuration — an association's billing method, coupon settings, and related billing parameters. An ingested per-association configuration entity, shown read-only in the app.

C

C3 — the target TownSq platform that onboarded data is loaded into.

C3 Id — the C3 identifier assigned to a migratable record during loading. See the Data Identity Model.

Chart of Accounts (GL) — the set of general ledger accounts. Source GL accounts are standardized against Associa/C3 standard GL accounts.

Charge Type — a category of charge. A mappable entity standardized against standard charge types; each links to a mapped GL account.

Change Log — a derived, observational record of how an organization's mappings diverge from the C3 standards, available per mapping tool.

Cutover — the switch from the source system to TownSq at go-live.

D

Data Availability — the app surface where data engineers confirm each entity has been ingested and where each entity's lifecycle state is visible. See Data Availability & Configuration.

Data Quality Rule — a rule applied automatically during ingestion. Each either warns (flags and ingests the row) or drops (excludes the row).

Delinquency Configuration — an association's delinquency process configuration. An ingested per-association configuration entity, shown read-only in the app.

Delinquency Status — a mappable entity standardized against standard delinquency statuses; links to mapped charge types.

E

External ID — the source-system identifier for a record, preserved on every migratable entity so records stay matched across re-ingestion.

F

Field Mapping Notes — the record of each field's availability and mapping requirements, which informs the ingestion transformation logic. See Field Mapping Notes.

Fiscal Year — the 12-month accounting period for an association. Fiscal start/end months are ingested on the association; GL periods are generated by the pipeline.

G

Global Mapping — a mapping applied at the organization level that propagates automatically to every association whose source record matches the code's signature. Carried into C3 by the Setup Association. See Standardization.

Go-Dark — the phase where fresh source data is pulled on the go-dark date and re-validated. See Go-Dark.

Go-Live — the point at which associations are live in C3 Production.

Go-Live Sign-off — the two-party gate ("Mark ready for Go-Live") that requires approval from both a Source System (NewCo) and a Target System (Associa) representative before a wave loads to C3.

H

HOA — homeowners association.

Homeowner — a property owner, represented in the system as a Member with the OWNER role.

I

Ingestion — the pipeline that transforms source data and loads it into Strata. All source data enters this way; there is no in-app upload.

M

Mapped Records — the canonical output of standardization (mapped GL accounts, charge types, delinquency statuses, reimbursables) that the C3 loading pipelines consume.

Member — a person associated with an account, with one or more roles: OWNER, TENANT, or OCCUPANT.

Migration Lifecycle — the fixed sequence of states each entity moves through, per wave: Field Mapped → Ingested → Data Quality Reviewed → Standardized → App Validated → C3 UAT Loaded → C3 UAT Validated → C3 Prod Loaded. Transitions are manual. See Migration Tracking & Sign-off.

N

NewCo — the branch / source-system team affiliation; one half of the two-party go-live sign-off.

Q

Quality Issue — a data quality rule violation recorded on a record during ingestion and surfaced in Review, with the original source value preserved.

R

Reimbursable — a mappable entity standardized against standard reimbursables; independent of the GL → charge type → delinquency chain and can be mapped at any time.

Review — the dashboards for spot-checking data quality across entities. See Review.

S

Setup Association — a synthetic association (C3 Id 1), hidden from every app surface, whose sole purpose is to carry the organization's global mapping set into C3 at load time.

Signature — the grouping key for GL accounts (code + description + type + summary group + department); mapping one member of a group maps all members that share the signature.

Standard GL Account / Charge Type / Delinquency Status / Reimbursable — Associa/C3 reference codes that source codes are mapped onto.

Standardization — mapping source-system codes (GL accounts, charge types, delinquency statuses, reimbursables, bank accounts) to Associa/C3 standards. See Standardization.

Strata — the lakebase where ingested data lives before it is loaded into C3.

Stale — an indicator on a validation whose underlying data has changed since it was completed, prompting re-validation.

T

Team Affiliation — a user's side of the migration: NewCo (Source System) or Associa (Target System). Determines each party in the go-live sign-off. See Roles & Access.

Tenant — a renter, represented as a Member with the TENANT role.

TownSq — the target platform for HOA management and community services.

U

UAT — User Acceptance Testing; here, testing migrated data in the C3 UAT environment.

UTF-8 — the character encoding used for source data files.

V

Validation Wizard — the guided, per-association validation across six data steps plus sign-off. See Validation.

Vendor — a service provider or contractor. Vendors are reviewed in Review → Vendors; they are not a standardization tool.

W

Wave — a named group of associations organized for phased go-live, carrying the go-dark and go-live dates and serving as the unit of sign-off. One branch migration has several waves. See Implementation Waves.

Availability states

The states used in Field Mapping Notes: Available, Quasi-Available, Not Available, Unknown.

Data types

String — text. Date — YYYY-MM-DD. Boolean — true/false. Decimal — numeric with decimals (e.g. currency). Integer — a whole number.