Data Availability & Configuration
Confirm each entity has been ingested, see its migration state, and view each association's ingested billing and delinquency configuration.
Overview
All source data enters the platform through the ingestion pipeline — there is no in-app data upload. As the ingestion team loads each entity for the branch (Phase 5), data engineers confirm it on the Data Availability page, and the app surfaces each association's operational configuration read-only.
Open it at Setup → Data Availability.
The Data Availability page
The Data Availability page tracks, per entity for the branch:
- Whether the entity has been ingested and confirmed available.
- Each entity's current migration lifecycle state.
Data engineers record the ingestion confirmation here as each entity is loaded. Because ingestion is branch-wide, entities appear as they become available rather than wave by wave.
Configuration is ingested, not configured in the app
Each association's operational configuration is ingested along with its data, not entered in the app. Two per-association entities carry it:
- Billing configuration — billing method, coupon settings, and related billing parameters.
- Delinquency configuration — the association's delinquency process configuration.
Fiscal-year start and end months are ingested as columns on the association itself, and GL periods are generated by the pipeline.
Viewing configuration
The app shows this configuration read-only, in two places:
- Under Review → Associations, as Delinquency and Billing sub-tabs.
- On each association's detail page, on its Configuration tab.
To change a value, the correction is made in the source system and re-ingested — it is not edited in the app.
Data quality on ingestion
As each entity is ingested, data quality rules run automatically. Each rule either warns (flags the violation and ingests the row, carrying the original source value forward) or drops (excludes the row). Violations are recorded on each record and surfaced throughout the Review dashboards.
Related
- Entity Model — load order and the configuration entities.
- Review — where ingested data and its quality issues are inspected.
- Migration Tracking & Sign-off — the lifecycle states shown here.
Implementation Waves
Group associations into waves for phased go-live, set go-dark and go-live dates, and use the wave detail page as the hub for a cohort's progress.
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.