Standardization
Map the branch's source-system codes — GL accounts, charge types, delinquency statuses, reimbursables, and bank accounts — to Associa/C3 standards, at both the global and association tiers.
Overview
Standardization is where the branch's source-system codes are mapped to Associa/C3 standard codes. This is Phase 6, and it requires branch and Implementation working together: the branch knows the source codes, Implementation knows the Associa standards. Engineering cannot do this alone.
Do this work under the Standardize section of the app.
The five mapping tools
There are five mapping tools, with a dependency order:
| Tool | Depends on | Notes |
|---|---|---|
| Chart of Accounts (GL) | — (map first) | Grouped by signature; asset-type GL accounts are excluded here (they're mapped via Bank Accounts). |
| Charge Types | GL Accounts | Each charge type links to a mapped GL account. |
| Delinquency Statuses | Charge Types | Each status links to mapped charge types. |
| Reimbursables | — (parallel) | Independent; can be mapped at any time. |
| Bank Accounts | GL Accounts (standards) | Maps each bank account to an asset-type standard GL account. |
Map GL accounts first, then charge types, then delinquency statuses. Reimbursables can be mapped in parallel with any of these. Each tool is a separate item under Standardize in the sidebar.
Global vs. association tiers
Each mappable entity exists at two source tiers, and you can map at either:
- Global (organization-level) — the deduplicated set of codes across the whole branch, with a usage count showing how many associations carry each code. Map here first. A global mapping is applied once and propagates automatically to every association whose source record matches the code's signature.
- Association-level — the per-association source records. Use this for individual overrides, where one association's code needs to map differently. Overrides are preserved when global mappings re-propagate.
Global mappings are anchored to a synthetic Setup Association (C3 Id 1). It's hidden from every
app surface; its only purpose is to carry the organization's global mapping set into C3 at load time.
Signature grouping
For GL accounts, source records are grouped by signature — code + description + type + summary group + department. Mapping one member of a group maps all members that share the signature, so you map a distinct code once rather than repeating the work for every association that uses it.
Two ways to map
Every tool supports both methods, at either the global or the association scope:
- Excel template — download a workbook pre-populated with the source records and a reference sheet of the Associa standards, fill in the targets, and upload it to apply the mappings in bulk.
- In-app editing — grids and dialogs for mapping individual records or grouped signatures.
The change log
Each mapping tool has a Change Log tab: a derived diary of how the organization's mappings diverge from the C3-preconfigured standards — new codes versus modifications, at global or association scope. It's recomputed after every upload or edit, and reviewers can annotate entries with notes and track application status.
The change log is observational. It doesn't drive the load; the mapped records themselves remain the canonical input.
What standardization produces
The output is the set of mapped records — the canonical input the C3 loading pipelines consume: mapped GL accounts, charge types, delinquency statuses, and reimbursables, per association, with the Setup Association carrying the global set. See C3 UAT Loading & Testing.
Completion
Standardization is complete for a wave when all source codes are mapped at the global tier, per-association exceptions are overridden where needed, and mapping completeness is verified for the wave. Completing it advances the mappable entities to the Standardized lifecycle state.
The four mappable entities (GL accounts, charge types, delinquency statuses, reimbursables) are reviewed here in their Standardize tools — not in the Review dashboards.
Data Availability & Configuration
Confirm each entity has been ingested, see its migration state, and view each association's ingested billing and delinquency configuration.
Review
Spot-check data quality, field completeness, and entity relationships across every entity, using KPI cards, paginated grids, and detail pages — filterable by wave.