CT Agency Suite billing

Medicaid billing that knows your visits.

Generate claims directly from the same record system that holds the visits, plans, and authorizations you bill against. Ingest 835 ERA remittance automatically. Track denials with reason codes that link back to the consumer record. Stop reconciling spreadsheets between two systems.

Apply for early access How billing works

One click: Claim generation from visit data
835 ERA: Auto-reconciled remittance
Reason-coded: Denials linked to records

Why billing breaks today

Two systems that don't agree on truth

Most agencies run case management and billing on separate vendors. Reconciling between them eats Friday afternoon.

Visits live in case management
Claims live in a separate billing tool
Remittance lives in a third system
Spreadsheets bridge the gaps

835 ERA

Auto-reconciled

Audit trail

Every claim attributable

Multi-state

Cross-state operations supported

HIPAA-aligned

Encryption + access controls

Why this matters

When billing and case management don't share data, every reconciliation is archaeology.

Most human services agencies run billing on a separate clearinghouse vendor that has no idea what their case management system thinks happened. Visits documented in one place, claims generated from manually-entered data in another, remittance imported into a third tool, denials tracked in a spreadsheet. Friday afternoon becomes a reconciliation ritual: did this claim actually correspond to a real visit? Why was that one denied? Where did the units come from?

CT Agency Suite collapses that. Billing runs on the same unified data model as visits, plans, consumers, and authorizations. CozziTech IS the clearinghouse, so a claim is generated from the visit it bills against and 835 ERA remittance lands in the platform automatically — no third-party clearinghouse to integrate, no file drops to manage. Denials show with their reason codes and link back to the specific consumer record so the billing team knows exactly where to look.

For multi-state agencies, the platform handles cross-state billing nuances without forcing you to keep separate billing systems per state. Authorization-to-claim linkage means you can prove every billed unit traces to an authorized service for an eligible consumer in a verified visit — the audit chain that auditors and payers expect.

What integrated billing changes

Friday-afternoon reconciliation goes away — systems agree on what happened
Claims trace to visits — not typed in from a printed report
Denials are actionable — reason codes link to the consumer record
Audit chain is intact — visit → authorization → claim → remittance

Billing capabilities

What integrated Medicaid billing actually delivers.

One-click claim generation from visit data

Claims generated from the visit records you've already documented. No re-keying from printed reports. No spreadsheet bridges between case management and billing. The claim's data is the visit's data.

835 ERA remittance, automatic

CozziTech is the clearinghouse, so 835 ERA remittance lands in the platform automatically — no file drops, no third-party imports. The platform auto-reconciles claims to payments. Paid claims close automatically. Denials surface with reason codes. Partial payments get flagged for review.

Denial management with reason codes

Every denial shows with its CARC/RARC reason codes and a link to the consumer record. Billing teams know exactly which visit, plan, or authorization the issue traces to — and resubmission flows through the same record system.

Authorization-to-claim linkage

Every billed unit traces to an authorized service for an eligible consumer in a verified visit. The audit chain visit → authorization → claim → remittance is intact end-to-end. Auditors get a clean record.

Multi-state billing support

Cross-state agencies bill from one platform with state-specific rules applied per claim. No separate billing system per state, no reconciling between disparate vendors.

Aging and reconciliation dashboards

See unpaid claims by aging bucket, denial rate by service category, average days-to-payment, and outstanding balance per consumer. The billing team works a worklist instead of an archaeology project.

What it looks like in practice

A few ways teams use this.

Month-end close, billing team

End of month, billing manager pulls the unpaid claims dashboard. 12 claims aging beyond 30 days — eight are pending state review (visible in the dashboard), three were denied with reason codes (one missing authorization, two dates outside coverage), one is on hold for a documentation issue the SC needs to resolve. The work is concrete and prioritized in 10 minutes. No 'where do I start' analysis.

Denial investigation

Insurance denies a batch of 14 claims. Billing opens the denial view, sees they all have the same reason code (provider not eligible for service category on those dates). Clicks into the consumer records, sees the credentialing gap, fixes the underlying provider record, resubmits the batch. What used to be a week of phone calls and PDFs is a 90-minute fix because the data was connected.

Multi-state agency closing the books

Agency operates across three states with different Medicaid programs. Month-end, controller pulls the aggregated revenue dashboard with per-state breakdowns. Each state's claims and remittances reconcile independently. No spreadsheet stitching, no separate billing system per state.

Frequently asked

What billing teams ask before they switch.

Does CT Agency Suite include a clearinghouse, or do we keep ours?

CozziTech IS the clearinghouse. There is no separate clearinghouse to integrate with or pay for. Claim submission and 835 ERA remittance happen inside the platform — you don't drop in 835 files or reconcile against an outside system. This is part of why billing is so much faster: the systems aren't separated.

How does the platform handle Medicaid managed care plans?

The platform supports Medicaid fee-for-service and managed care plan billing. Per-payer configuration handles the routing rules, authorization requirements, and reason-code dictionaries that vary between MCOs. Each managed care plan is configured once, then claims route correctly without per-claim manual decisions.

What happens when a denial requires a corrected claim?

Resubmissions flow through the same record system. The platform tracks corrected claims as part of the claim's history, so you can see the full lifecycle from original denial through correction through final payment. The audit trail is preserved end-to-end.

Can the platform export to our accounting system?

Yes. Standard exports for revenue recognition feed common accounting systems. Per-claim, per-payer, and per-period exports cover most accounting workflows. Custom integrations are available for early-access partners with specific accounting stacks.

How does multi-state billing work in practice?

Each state's Medicaid program is configured with its specific service codes, modifier rules, authorization requirements, and reason-code dictionaries. Claims are submitted to the correct state's payer based on the consumer's program. Reporting aggregates across states or breaks out per-state as needed.

What's the migration path from a separate billing vendor?

Early-access onboarding includes a billing-specific migration plan: importing historical claim history, mapping service codes to your prior billing setup, parallel-running the new billing alongside your existing system for a defined evaluation period, and cutting over module-by-module. Most agencies see meaningful billing consolidation within 60-90 days of go-live.

Stop reconciling between two systems.

Apply for the CT Agency Suite early-access program. We'll walk through your current billing stack and map a sequenced consolidation plan.

Apply for early access Back to CT Agency Suite