What the audit packet contains
The quarterly audit packet is the single artifact state ESA reviewers ask for. CohortLedger generates it in one click. It contains:
- School info (legal name, address, EIN, founder, school year)
- Quarter info (program, platform, funding window dates)
- Per-student summary (tuition charged, ESA received, OOP received, days present, days late)
- Compliance log (every state task completed in the quarter with dates and evidence)
- Totals and certification timestamp
1. Open the audit packet
From either Compliance or Billing, click the Generate Q1 audit packet CTA at the top. CohortLedger renders the HTML version of the packet for the current quarter on a single page, formatted for print or PDF.
2. Review before sending
Skim the per-student summary table. Confirm the ESA received amounts match what landed in your bank reconciliation. Confirm the attendance numbers look right. If something is off, fix the source record (Students, Billing, Attendance) and regenerate the packet.
State reviewers do not need to see your bank statements — only the per-student totals. CohortLedger never exposes the operator’s own banking details in the packet.
3. Download CSV for state portals
Some states (Arizona ASDOE, Florida Step Up) prefer CSV upload over PDF. Click Download CSV. The export includes a preamble (school + quarter), per-student rows, and a compliance log section, formatted as one file the state portal can ingest.
4. Print or PDF for paper records
Use Cmd+P (Mac) or Ctrl+P(Windows) from the HTML packet view. CohortLedger’s print stylesheet hides the sidebar and nav, renders the packet on US Letter size with clean margins, and includes the certification timestamp footer on every page.
5. Archive a copy
Save the PDF and CSV to your operator records. Most state ESA programs require operators to retain quarterly records for at least 4 years (Arizona is 4, Texas TEFA is 7). CohortLedger keeps every previous quarter’s packet inside the dashboard, but a local copy is good practice.
Next
If you are bringing in a co-administrator to handle some of this work, see Inviting a co-administrator.