When ESA Expenses Get Rejected: The Invoice Standard¶
The call comes from the family, not from the state.
A parent reaches out in October to ask about a letter they received from ADE. ClassWallet approved and paid the expense back in March. Seven months later, the annual account review caught something. The letter says the documentation does not meet the itemized standard. The family may need to repay the funds.
You look at the invoice you issued in March. It has the student name at the top. A date. A total. Your school's name. It looks fine to you.
That invoice is exactly why the expense was flagged.
What the annual review actually is¶
ClassWallet approves transactions in real time, at the point of purchase, based on merchant category codes. When a family uses their ClassWallet card at your school, the system checks the merchant category code and either approves or declines. That real-time approval is not a guarantee that the underlying documentation will pass a review later.
ADE conducts annual account reviews on a rolling basis. These reviews look behind the approval at the actual invoice: what did the document say, does the service description match the approved expense category, does the invoice identify the specific student by name. A payment that cleared ClassWallet in September can still be flagged the following spring when an auditor pulls the transaction history.
In May 2026, Arizona's Auditor General released findings from a review of ESA account activity. Auditors examined $251,446 across a sample of accounts and flagged $86,599 as having compliance problems. That is 34% of the sampled total. The auditors cited documentation failures as the primary driver, not intentional misuse.
Texas runs its own separate program, the Texas Education Freedom Accounts (TEFA), administered by the Comptroller through the Odyssey platform. The same dynamic applies there: Odyssey pre-approves vendor categories, but the Comptroller's review looks at the documentation behind each payment. A vendor approval in Odyssey does not protect against a documentation deficiency finding.
The review is always retrospective. The gap between "ClassWallet paid it" and "this expense holds up in review" is exactly where documentation failures live.
Why a receipt fails where an invoice passes¶
A point-of-sale receipt records a transaction. An itemized invoice records a service. The distinction is not semantic. ESA programs fund educational services, not commercial transactions, and the documentation standard reflects that.
Here is what a typical receipt contains: merchant name, transaction date, total amount, last four digits of the card. Sometimes a category description. Almost never: the student's legal name, individual service dates, per-item pricing broken out by line, or a description of what the educational service actually was.
Here is what ADE's documentation standard requires on an invoice:
| What a receipt typically has | What an ESA invoice requires |
|---|---|
| Merchant name | Provider legal name and mailing address |
| Transaction date | Service date(s), one per session or billing period |
| Total amount | Itemized line items with unit price per item |
| Card last four | Student legal name as it appears in the ESA account |
| Sometimes a category | Description of each service (specific, not a category label) |
| Not included | Quantity times unit rate equals line total |
One point that trips up many founders: the difference between "date of invoice" and "dates of service." ADE wants to see the dates when the service was delivered, not the date you generated the invoice. If you billed for 20 sessions in September as a single line item, the invoice needs to show the service window (September 2, 2025 to September 30, 2025) or individual session dates. "Invoice date: October 1, 2025" on a September billing period is not the same thing.
The specific rejection triggers in ClassWallet¶
The 2026 audit findings and ClassWallet's vendor documentation point to five rejection triggers that appear repeatedly. These are not edge cases.
1. Missing student identification. The invoice names the school or the parent but not the individual student. In a household with multiple ESA children, this is unresolvable in review. The auditor cannot determine which student's account the expense belongs to.
2. Lump-sum billing. A single line item that reads "Monthly tuition: $1,200" with no breakdown of services underneath. ADE's itemized standard requires that different services appear as separate line items, particularly when they map to different eligible expense categories. If your tuition covers core instruction and a curriculum materials component, those are two line items, not one.
3. Category mismatch between invoice description and MCC. The merchant category code on the ClassWallet transaction might be "educational services" while the invoice description says "art supplies." These are different eligible categories with different documentation requirements. ClassWallet approves based on MCC at the point of purchase. The annual review checks whether the invoice description actually matches the category the transaction was processed under.
4. Vendor name discrepancy. The name on your ClassWallet-approved vendor account does not match the legal name on your invoice. This comes up for microschools operating under a DBA or for founders who registered with a personal name and invoice under a school name. The names need to match exactly.
5. No service date range. The invoice shows "September 2025" rather than a specific window like "September 2, 2025 to September 30, 2025" or individual session dates. A month name without dates is not sufficient documentation.
Any one of these can trigger a documentation deficiency finding on an otherwise eligible expense. The expense category can be perfectly appropriate and the payment still gets flagged because the invoice field is missing or mismatched.
How repayment works when an expense is rejected¶
ADE notifies the ESA account holder: the family. Not the school. The family receives written notice identifying the flagged expense, the amount, and the documentation deficiency. The school does not get notified directly. Most founders find out when the family calls.
The family owes the funds back to ADE, not to the school. The school keeps whatever it was paid. This asymmetry is worth sitting with: if your invoice caused the documentation failure, the financial consequence lands on the family. That is not a position anyone wants to put a family in.
Repayment typically comes from the family's remaining ESA funds. If the account balance is insufficient, ADE can require out-of-pocket repayment or reduce future disbursements. For a family depending on ESA funds to cover tuition at your school, a repayment demand can cascade into a real financial problem for that household.
Patterns of documentation failures can also trigger a full account audit rather than a single line-item rejection. The 2026 audit's findings have put ADE under political pressure to increase review rigor. That pressure produces more reviews, not fewer.
The operational consequence for your school is relationship damage that cannot be repaired by fixing the invoice afterward. The right time to get the invoice right is before the payment, not after a family has received a repayment letter.
Texas TEFA: a different rulebook¶
Arizona's ClassWallet program and Texas's Education Freedom Accounts are separate programs run by separate agencies with different eligible expense categories, different documentation standards, and different review processes. They are not interchangeable.
TEFA is administered by the Texas Comptroller through the Odyssey platform, not ClassWallet. The eligible expense categories overlap substantially with Arizona's but diverge in meaningful ways. TEFA explicitly excludes some recreational activities that Arizona allows under its extracurricular category. TEFA covers transportation expenses in certain ways that ADE does not. The category definitions matter because a school that accepts both Arizona and Texas ESA families and uses a single invoice template is creating exactly the kind of category mismatch that surfaces in documentation reviews.
The structural invoice requirements in Odyssey look similar to ADE's on the surface: student name, service description, date of service, unit price. But the category mapping is different, and what the description needs to say to satisfy a Texas reviewer is different from what satisfies an Arizona reviewer.
A school billing families from both programs needs two invoice templates: one mapped to ADE's eligible expense categories, one mapped to TEFA's. This is not extra paperwork for its own sake. It is the only way to ensure that the description on each line item matches the category it is being billed under in the program that will review it.
If you are expanding to Texas, Odyssey's published support documentation lists the TEFA eligible expense categories in detail. Read it before you issue your first invoice to a Texas family, not after.
ESA invoice checklist: use this before every submission¶
These are the fields ADE and the Texas Comptroller check during documentation review. Go through this list before submitting any invoice to ClassWallet or uploading one to Odyssey.
Student identification
- [ ] Student's legal name (exactly as it appears in the ESA account, not a nickname or preferred name)
- [ ] Program name if you serve families from both states (Arizona ESA or Texas TEFA)
Provider identification
- [ ] Provider legal name (must match the name on your approved vendor account exactly)
- [ ] Provider mailing address
Service documentation
- [ ] Each service appears as its own line item (no bundled descriptions)
- [ ] Service date(s) listed per line item, not just the invoice date
- [ ] Description of each service (specific and descriptive, not a category label)
- [ ] Quantity and unit price for each line item
- [ ] Line totals and invoice total
Category alignment
- [ ] Each line item maps to an eligible expense category for this specific program
- [ ] The line item description matches the MCC under which your vendor account is categorized in ClassWallet or Odyssey
Format
- [ ] Invoice number (for your records and for any dispute process)
- [ ] Invoice date
- [ ] The document is labeled "Invoice" (not "receipt," "statement," or "tuition notice")
Two notes on using this checklist. First, the category alignment items are program-specific. Run them against Arizona's eligible expense list for ClassWallet submissions and against TEFA's list for Odyssey submissions. Second, the word "Invoice" needs to appear on the document itself. An email with a tuition amount attached to a PDF labeled "Spring Statement" is not an invoice in ADE's terms.
What to do if an expense is already flagged¶
Step 1: Get the rejection notice from the family. ADE's notice will cite the specific line item and the deficiency reason. "Documentation deficiency" is not specific enough to act on. The notice will name the field that failed. Get the exact language before doing anything else.
Step 2: Pull the original invoice and compare. Set it next to the checklist above and go line by line. The deficiency is almost always traceable to a specific missing or mismatched field: no student name, no service dates, lump-sum billing, or a description that does not match the expense category. Find the field.
Step 3: Determine whether the expense category itself was eligible. This matters because the resolution path is different. If the deficiency is documentation-based (a field is missing or wrong), the family may be able to submit supplemental documentation to ADE. If the deficiency is category-based (the service was not on the approved list), no amount of corrected documentation will resolve it. Category-based rejections require the family to contact ADE directly. You cannot resolve a category rejection for them.
Step 4: Fix your invoice template. Whether this specific rejection gets resolved or not, the same deficiency will appear on every future invoice that uses the same template. Fix the template before the next billing cycle. This is the step that most often gets skipped.
Do not try to resolve a repayment demand on the family's behalf. ADE's dispute and repayment process is between the agency and the account holder. What you can do is provide the family with documentation that might support their case, and do it promptly. ESA response deadlines are real and they are short.
The invoice standard is not complicated once you know what fields it requires. The documentation failures in the 2026 audit almost always came from schools issuing receipt-style documents when the program requires invoice-style documents. The fields are different. The formats are different. The consequences of using the wrong one fall on the family, not the school.
NavEd handles the student records layer that ESA documentation depends on: enrollment verification, per-student attendance history, and the records that confirm a student was actively enrolled and attending during the billing period you are invoicing for. If you want to see how that fits into your documentation workflow, nav.education is a good place to start.
Last updated: July 30, 2026. ESA program rules change. Verify current requirements with ADE (Arizona) or the Texas Comptroller's TEFA program office before making compliance decisions.