ESA Invoice Requirements for Enrichment Teachers in Arizona

Getting approved as a ClassWallet vendor is the first hurdle. The second one is submitting invoices that actually get paid. A lot of enrichment teachers get through vendor registration and then find out the hard way that a missing field or a wrong date range is enough to get an invoice rejected. That means chasing the family, rebuilding the document, and waiting another cycle.

This guide covers exactly what needs to appear on every ClassWallet invoice, why each field matters, and the mistakes that cause rejections.

What ClassWallet actually looks at

ClassWallet is the platform Arizona uses to distribute ESA (Empowerment Scholarship Account) funds. When you submit an invoice, a reviewer is checking that:

• The expense is eligible (enrichment classes are)
• The vendor on the invoice matches the registered vendor in their system
• The student on the invoice matches the ESA account holder
• The service dates fall within the correct ESA quarter
• The invoice is complete with no missing fields

Any mismatch or missing information is grounds for rejection. ClassWallet does not always tell you specifically what went wrong, which makes getting it right the first time worth the effort.

Every field required on a compliant invoice

Your information:

• Your full legal name, exactly as it appears on your ClassWallet vendor registration
• Your ClassWallet display name or business name (if you registered under a DBA), exactly as it appears in the system
• Your phone number
• Your email address

Student and family information:

• The student's full first and last name
• The parent or guardian's full name
• The parent's phone number
• The parent's email address

Service details:

• The exact date of every session included in the invoice (specific dates, not a range)
• A description of the service (e.g., "Weekly watercolor painting class for ages 6-12")
• The price per session or the total amount
• The ClassWallet expense category

If your class meets weekly for eight weeks, your invoice needs to list all eight session dates individually. A summary like "8 sessions in March" is not sufficient and will likely be rejected.

The ESA quarter system

This is where most invoicing errors happen. Arizona ESA funds are managed by quarter:

• Q1: July 1 through September 30
• Q2: October 1 through December 31
• Q3: January 1 through March 31
• Q4: April 1 through June 30

ClassWallet will not reimburse an invoice that spans two quarters. If your class runs across a quarter boundary, you need to submit separate invoices: one for the sessions in Q3, one for the sessions in Q4.

Example: A class that meets every Wednesday from March 18 through April 22 spans both Q3 (March 18, 25) and Q4 (April 1, 8, 15, 22). That requires two invoices: one for the two March sessions, one for the four April sessions. One invoice covering all six dates will be rejected.

This also means you need to plan your invoice submissions around the quarter calendar, not just around when your class ends. The Q4 expense reporting deadline is June 30. All Q4 invoices need to be submitted before that date.

Name matching: the most common rejection cause

Your vendor display name on the invoice must match your ClassWallet vendor registration exactly. Not approximately. Exactly. A middle initial, a hyphen, different capitalization, or a shortened version of your business name is enough to cause a rejection or payment problem.

If you registered as "Sarah J. Martinez," your invoice should say "Sarah J. Martinez" and not "Sarah Martinez" or "S. Martinez."

If you registered under a business name, use that business name exactly as it appears in ClassWallet. If you're unsure what name you registered under, log into your ClassWallet vendor portal and confirm before you submit anything.

The same logic applies to the student's name. The name on your invoice needs to match the name on the family's ESA account. If the family uses a nickname or a legal name they don't go by day-to-day, that mismatch can cause delays. Ask families at enrollment: "What name is on your ESA account?" and use that name exactly.

Processing fees

ClassWallet charges vendors a processing fee of typically 2 to 2.5 percent of each transaction. Some teachers absorb this cost and bake it into their class pricing. Others itemize it as a separate line on the invoice.

Both approaches are acceptable. If you itemize it, add a line item labeled something like "Processing fee (2%)" with the dollar amount. If you bake it in, no separate line item is needed.

What you should not do is surprise families with a fee after the fact. If you're passing the processing fee to the family, let them know before enrollment.

What to do when an invoice is rejected

First, find out why. ClassWallet may or may not give you a specific reason. If they don't, the most common causes are name mismatch, cross-quarter dates, and missing fields. Go through the checklist above and compare your invoice line by line.

Once you've identified the problem:

1. Void the rejected invoice (do not resubmit the same document)
2. Correct the error: update the name, split the dates by quarter, or add the missing field
3. Generate a new invoice with a new invoice number
4. Resubmit through the ClassWallet vendor portal

Do not alter the original rejected document and resubmit it. Generate a fresh invoice to avoid confusion in the audit trail.

Keeping records

ClassWallet can audit invoices at any time. When they do, they may ask for:

• Signed attendance records showing which student attended which sessions
• Session notes or class descriptions
• Proof of your credentials for the subject you're teaching

Keep records for every class, every session, every enrolled student. A simple attendance sheet with student name, session date, and a signature line is enough. Store them somewhere you can retrieve them quickly: a shared folder, Google Drive, or a filing cabinet all work.

How Pydia fits in

Building invoices by hand for every ESA student takes a predictable chunk of time every month and introduces predictable opportunities for error. The right fields, the right dates, split by quarter, matched to your ClassWallet registration exactly.

Pydia generates ClassWallet-compliant invoices automatically when an ESA family enrolls in your class. Every required field is populated from information the family provides at enrollment: their student's name, their contact information, your registered vendor name, and the exact session dates for the quarter. You review it, submit it to ClassWallet, and mark it done. No PDF templates, no manual tracking, no cross-quarter math.

If you're building invoices manually right now, apply to join the Pydia founding cohort. Founding partners get free access while the platform is in early release, then lock in at $19.99/month for life.

Quick reference: invoice checklist

Before submitting any ClassWallet invoice, confirm:

• Your full legal name matches your ClassWallet vendor registration exactly
• Your business name (if applicable) matches exactly
• Your phone number and email are included
• The student's full name matches the name on their ESA account
• The parent's name, phone, and email are included
• Every session date is listed individually (not as a range or summary)
• All session dates fall within a single ESA quarter
• The service description is specific
• The expense category is correct
• The invoice has a unique invoice number

One rejected invoice is a learning experience. Two is a system problem. If you're submitting invoices regularly and finding that some come back, work through this checklist against each rejected document. The pattern will usually point to the same field every time.