This is a real, working import — pick an agency and a .xlsx file below and it's parsed live in your browser (nothing uploads anywhere). Built from your sample file's exact "Hours" sheet: identity columns (name, County, Medicaid #, Waiver Type, Provider) are forward-filled from each person's first row, and people are matched by Medicaid Number.

Note: if you're viewing this inside Claude's in-app preview, the live parsing may not run — open the file directly in your web browser (double-click it in your folder) to try the real upload.

This is a real, working parser for eMBS's "Upload Flat File" submission format (the 75-byte-per-line layout from DODD's own eMBS flat file guide) — not the after-the-fact report exports. Drop in the exact flat file you're about to submit (or already submitted) and it will:
1. Calculate the total billed (units × rate) per agency, detected automatically from each line's 7-digit contract number.
2. Cross-check every line against the most recently imported PAWS data for that agency: is the recipient on file, does the service date fall inside an authorized period, and does the units billed stay within what's still authorized.
3. Flag structural problems eMBS itself would reject — like blank lines or lines that aren't exactly 75 bytes.

Note: one limitation — eMBS's 3-letter service codes (e.g. "FPC") don't share a documented crosswalk with PAWS's rollup codes (e.g. "A22"), so this can't yet confirm a specific service code was authorized, only that the person, date, and unit balance check out. If you have or find that crosswalk, share it and I can tighten this check.

If you're viewing this inside Claude's in-app preview, open the file directly in your browser for the parsing to run.

Parses DODD's invoice/payment report (e.g. an INVCFLAT file) and sums the actual amount paid. To find the right billing entry to attach it to, tell us which agency and which billing period this invoice is for — matching is done by agency + exact billing period, not by anything inside the invoice file itself.

This creates a real invite. The person opens the portal's sign-in page, clicks "First time here?", enters this exact email, and sets their own password — Zenith never sees or sets it.

Creates a real invite for this agency. The person opens the portal's sign-in page, clicks "First time here?", enters this exact email, and sets their own password.

In production, this button opens Stripe's secure hosted form (or embedded Payment Element) — card/bank details go directly to Stripe and never touch Zenith's servers.