Arizona ESA invoice requirements

The current state rules record, a worked document example, and the checks that separate invoice fields from payment-path evidence.

Rules last verified July 2026 against the official Empowerment Scholarship Account program. View the official source →

Direct answer

A Arizona ESA invoice must match the current program and transaction path

Use the recorded fields below as a preflight, then compare the finished document with the official Empowerment Scholarship Account source and the live ClassWallet instruction. A complete invoice requests payment; it does not by itself prove provider, student, expense, authorization, delivery or reimbursement eligibility.

Fields in the current Arizona ESA invoice record

Use this as a pre-submission checklist, then compare it with the current category or portal instruction. A field can be conditionally required, and a complete invoice does not by itself establish provider, service, student or transaction eligibility:

Provider (vendor) name, address, and contact information
Invoice date AND a unique invoice number
Student's full name
Itemised services with the date each service was delivered
Total charges
Provider's license number — required for therapists and qualified examiners
For reimbursements: an itemised invoice AND a proof-of-payment receipt (invoice alone is denied; direct ClassWallet vendor-pay can be invoice-only)

Illustrative comparison: investigate the actual return message rather than inferring the reason from this diagram.

Don’t build this by hand

Our free generator applies the current Arizona rules record and warns about missing fields. It cannot guarantee program approval; compare the output with the current official instruction.

Open the invoice generator Check my invoice

What a compliant Arizona ESA invoice looks like

This educational example shows how itemization and traceability can be structured. It is not an actual ClassWallet approval, and fields that fit a tutoring example may not fit a product, therapy, tuition or marketplace transaction.

Bright Path Learning LLC

123 Main St, Arizona · EIN 00-0000000

INVOICE #1042

Issued June 3, 2026

Student Ava Johnson

Parent / account holder Maria Johnson

Program Empowerment Scholarship Account (ESA)

Service dates May 5–30, 2026

Description & subject	Hours	Rate	Total
Reading & phonics tutoring (Grade 2 English/Language Arts)	8	$50	$400
Math tutoring (Grade 2 mathematics)	4	$50	$200
Total due			$600

Provider credential: include only when the current category requires it · Proposed payment surface: ClassWallet

The example connects provider identity, recipient, dates, specific tutoring work, units, rates and arithmetic. Confirm whether the current transaction requests an EIN, parent name, subject, credential, authorization, tax detail or a different document before copying it.

How to submit your invoice to ClassWallet

Identify the current program, provider category, expense and payment option for the transaction.
Build the itemized document from truthful source records and add only fields that apply.
Submit it through the route the current Arizona instruction displays; save the reference and status.
If it is returned, preserve the original and exact reason before making a versioned correction.
After approval, wait for settlement and match the approved amount, fee and bank deposit before marking it paid.

Documentation ClassWallet may also ask for

Facility Accreditation Attestation Form (tutoring vendors)
Itemised receipts
Curriculum statements connecting materials to the student's education
Quarterly documentation uploads to ClassWallet (by the end of the month after each quarter)
Current (non-expired) credentials — expired credentials invalidate payment requests

Arizona tutoring invoices: a payment receipt alone is not enough

Arizona's ESA support page says detailed invoices are required for tuition, tutoring and educational therapies, and that Square, PayPal or point-of-sale receipts alone are insufficient. Use the current handbook linked by the department for the applicable invoice guidance; do not rely on a page number copied from an older handbook. Arizona Department of Education ESA support. This document distinction was checked September 6, 2026.

Worked example: show the service behind the charge

A fictional tutor has a $112.50 payment confirmation for two reading sessions. The confirmation explains that money moved, but it may not explain which student received the service, when the sessions happened or how the amount was calculated.

The supporting invoice should make the underlying transaction understandable. In this example, a 60-minute session at $75 per hour produces $75, and a separate 30-minute session produces $37.50. Retain the actual service dates, the required student and provider identities, and the applicable supporting evidence. These example fields are a preparation baseline; the department's current category and payment-route instructions control the submission.

Review the packet before sending it

Compare the document to the session log, check the sum, and identify which file proves payment if that route requires it. An invoice and a receipt can support different parts of the same transaction. Do not rename a payment confirmation “invoice” and assume the missing service details are now present.

If a reviewer requests a correction, preserve the original submitted version and follow the stated amendment route. The correction log helps explain what changed; the tracking register records the subsequent review and payment separately.

Prepare an Arizona invoice or save my Arizona billing records.

Detailed operating guide

A field-by-field Arizona invoice review

This section turns the current state record into an operating procedure. It deliberately separates facts in the official record from practical controls that a provider can use. A checklist can improve completeness, but it cannot make an ineligible provider, offering, student or transaction eligible. Read every “check” below as a prompt to compare your evidence with the current official Empowerment Scholarship Account (ESA) source, category guidance, provider agreement and in-portal instruction.

State-specific editorial dossier

What makes the Arizona provider workflow different

The analysis below is specific to the current Empowerment Scholarship Account (ESA) record. It interprets the recorded application, expense, document, timing and payment facts without turning them into approval or payout promises.

Arizona separates ADE provider registration from ClassWallet payment access

Arizona has a mature, high-participation ESA environment, but maturity does not collapse the workflow into a single account. The state record begins with Arizona Department of Education service-provider registration and then moves an approved provider to ClassWallet. Maintain two checkpoints: the program-side provider decision and the payment-side account setup. Record the account names and identifiers used in both places so a later invoice, quarterly upload or credential renewal does not attach to the wrong business record. A vendor count or universal-program label describes market context; it does not prove that a particular tutor, microschool, therapy, curriculum item or tuition transaction is presently eligible.

Arizona tutoring and microschool evidence needs category discipline

The Arizona record specifically calls for a Facility Accreditation Attestation Form for tutoring vendors and says each instructor must meet the recorded minimum education standard. It also distinguishes non-accredited microschools registering as a vendor or service provider and billing under categories such as tutoring services, curriculum or supplemental instruction. That makes internal classification important. A microschool should separate the components it truly provides instead of placing tuition, tutoring, curriculum and supplies under one broad label. A tutoring business should keep the attestation and instructor evidence current, linked to the people who deliver the sessions, without adding sensitive or irrelevant records to every invoice.

Arizona uses recurring documentation, not a once-and-done packet

The state record names itemized receipts, curriculum statements, current credentials and quarterly documentation uploads to ClassWallet. It also warns that expired credentials invalidate payment requests. Build a calendar that closes each quarter with a completeness review before the end-of-following-month upload point. Curriculum evidence should explain the educational connection truthfully; it should not be boilerplate pasted onto unrelated consumer items. Credential monitoring needs an owner and advance reminders. When a credential renews, preserve the old version for historical transactions and the new version for work after its effective date rather than silently replacing the file.

Arizona payment questions should start with the quarter and the actual status

Because the program runs on a rolling basis, there is no single annual launch date that explains every provider situation. Identify whether the issue is registration, ClassWallet onboarding, category fit, missing quarterly evidence, an expired credential, invoice review, approval or bank matching. Save the exact portal message and transaction reference before correcting anything. A receipt proves payment already occurred, while an invoice requests payment; Arizona documentation can require different evidence depending on the path. Measure the provider’s own submission-to-decision and decision-to-deposit intervals, but do not present a small private sample as a statewide payout promise.

Understand what an invoice can and cannot prove

An invoice is a payment request and accounting record. It can identify the parties, describe what was provided, show dates and quantities, calculate the amount, and reference supporting records. It does not by itself prove that the provider was approved, the student was eligible, an authorization existed, a product arrived, a session occurred, a family already paid, or the program accepted the transaction. Those questions may require separate evidence.

That distinction matters in Arizona because the recorded payment surface is ClassWallet, while the exact workflow still depends on the program, category and transaction. Begin with the document requested in the live route. A reimbursement may require proof of payment; a marketplace order may depend on listing and fulfillment records; a vendor-payment request may use an invoice plus authorization. Never relabel an invoice as a receipt unless payment actually occurred.

Review each Arizona invoice field in context

The state record contains the fields below. For every field, the practical test is not merely “is something present?” It is whether the value is truthful, internally consistent, legible, supported by the underlying record and appropriate to the selected payment path. Compare the completed document with the official Empowerment Scholarship Account (ESA) source before it leaves your control.

Field 1: Provider (vendor) name, address, and contact information

Check the value against its source record, not a previous invoice. Ask whether it identifies the correct business, account, student, service, product, date, unit, price or qualification as applicable. Then inspect nearby fields for contradictions. A clear line description cannot repair the wrong recipient; correct arithmetic cannot prove delivery; and a credential should not be included unless it belongs to the right professional and service period.

Keep the supporting source with the final version and submission reference. If the portal changes or normalizes the value, record what was entered and what the system displayed. That small control makes a later return, partial approval or payout difference diagnosable.

Field 2: Invoice date AND a unique invoice number

Field 3: Student's full name

Field 4: Itemised services with the date each service was delivered

Field 5: Total charges

Field 6: Provider's license number — required for therapists and qualified examiners

Field 7: For reimbursements: an itemised invoice AND a proof-of-payment receipt (invoice alone is denied; direct ClassWallet vendor-pay can be invoice-only)

Supporting documents in the current state record

Attachments should answer a real review question. Sending a large unsorted packet can expose unnecessary information and make the relevant evidence harder to find. Use a short, named set in a stable order, redact only where permitted, and retain the unaltered source securely.

Evidence item 1: Facility Accreditation Attestation Form (tutoring vendors)

Confirm whether this item is required for the business, rendering provider, offering, student or transaction in front of you. Check names, effective dates, scope and expiration where relevant. Give the file a descriptive, privacy-conscious name and connect it to the invoice number or portal reference. Do not submit an expired, unrelated or over-redacted document merely because its file name resembles the requested evidence.

Evidence item 2: Itemised receipts

Evidence item 3: Curriculum statements connecting materials to the student's education

Evidence item 4: Quarterly documentation uploads to ClassWallet (by the end of the month after each quarter)

Evidence item 5: Current (non-expired) credentials — expired credentials invalidate payment requests

Translate expense categories into auditable lines

Broad categories help people discover a program, but reviewers decide real transactions. The line should say what was actually provided, for what educational purpose when required, on which dates or in what quantity, at what unit price, and with which applicable identifier or authorization. Avoid promotional language, vague bundles and descriptions written only to echo a category name.

When the proposed category is Tutoring & supplemental instruction

Verify the current Arizona definition and any limits before invoicing. Identify the actual product or service and preserve the order, service, delivery or fulfillment record that supports the billed quantity. If several categories or dates are involved, split the lines so a reviewer can assess one without guessing about the others. The presence of “Tutoring & supplemental instruction” in the state record is not a guarantee that this provider, offering or student transaction qualifies.

When the proposed category is Curriculum & instructional materials

Verify the current Arizona definition and any limits before invoicing. Identify the actual product or service and preserve the order, service, delivery or fulfillment record that supports the billed quantity. If several categories or dates are involved, split the lines so a reviewer can assess one without guessing about the others. The presence of “Curriculum & instructional materials” in the state record is not a guarantee that this provider, offering or student transaction qualifies.

When the proposed category is Therapies

Verify the current Arizona definition and any limits before invoicing. Identify the actual product or service and preserve the order, service, delivery or fulfillment record that supports the billed quantity. If several categories or dates are involved, split the lines so a reviewer can assess one without guessing about the others. The presence of “Therapies” in the state record is not a guarantee that this provider, offering or student transaction qualifies.

When the proposed category is Educational services for students with disabilities

Verify the current Arizona definition and any limits before invoicing. Identify the actual product or service and preserve the order, service, delivery or fulfillment record that supports the billed quantity. If several categories or dates are involved, split the lines so a reviewer can assess one without guessing about the others. The presence of “Educational services for students with disabilities” in the state record is not a guarantee that this provider, offering or student transaction qualifies.

When the proposed category is Tuition (for qualified schools)

Verify the current Arizona definition and any limits before invoicing. Identify the actual product or service and preserve the order, service, delivery or fulfillment record that supports the billed quantity. If several categories or dates are involved, split the lines so a reviewer can assess one without guessing about the others. The presence of “Tuition (for qualified schools)” in the state record is not a guarantee that this provider, offering or student transaction qualifies.

A ten-point preflight before submission

Confirm the state, program, provider account, category and transaction path shown in the current portal.
Generate a unique invoice number and keep the final version immutable after submission.
Match provider and recipient identity to the records the program expects, including punctuation and legal names where relevant.
Reconcile service, order and invoice dates; explain a legitimate difference instead of silently changing source records.
Use one truthful item or service per line where different categories, rates, dates or professionals need separate review.
Calculate quantity multiplied by unit price, then independently recompute subtotals, adjustments and total due.
Add only applicable credentials, authorizations and supporting documents, checking scope and effective dates.
Inspect the exported file at normal zoom for clipping, blank pages, tiny text, broken characters and missing totals.
Submit through the route shown for this transaction and retain the confirmation, timestamp and reference.
Do not mark the invoice paid until the approved amount is matched to settlement and the bank record.

Correct a returned invoice without losing the audit trail

Preserve the original file, exact status, reason, timestamp and portal reference. Convert the message into a small correction plan: what value or evidence is disputed, which authoritative record resolves it, who owns the correction, and whether the current workflow expects an edit, resubmission or support response. Change only what the evidence supports. Save a new version and describe the correction in neutral language.

A return is not always an invoice-field problem. The issue may sit at provider approval, student authorization, expense eligibility, payment-path selection, duplicate detection, fulfillment or account configuration. If the message is ambiguous, ask the program or administrator a specific question that includes the transaction reference and status but no unnecessary personal information. Do not create duplicate payment requests simply to see which one moves first.

Worked examples of stronger evidence

A recurring service

Instead of “education services — $600,” use truthful lines that identify the service, covered dates, units, rate and educational purpose where requested. Connect them to a service log and the applicable professional record. If a session was cancelled, credited or delivered by a different person, let the invoice and source log reflect that reality rather than forcing them to match an earlier estimate.

A product or resource order

List the real product name or identifier, quantity, unit price and any separately allowed charge. Keep the order and fulfillment evidence. Do not hide an accessory, subscription period, shipping amount or unrelated item inside a single “curriculum” line. Where the workflow uses a marketplace record instead of a provider-created invoice, use the requested record and do not invent a parallel document.

A reimbursement packet

Separate the itemized invoice or order from proof that the family paid. Confirm that names, vendor, dates, items and amounts connect across the documents. A bank screenshot without an itemized record may not establish what was purchased; an unpaid invoice does not prove a reimbursement occurred. Follow the current Arizona instruction for accepted formats and privacy treatment.

Source-check and revision protocol

Before relying on this page, reopen the official Empowerment Scholarship Account (ESA) source and record the date checked. Look for changes to program name, administrator, provider categories, application route, expense definitions, credentials, background requirements, invoice fields, supporting documents, transaction options, fees, deadlines and contact routes. If a handbook, portal prompt or agreement conflicts with this guide, follow the current authorized instruction and send GetESAPaid the source so the public record can be reviewed.

Keep an internal change log that states what changed, which transactions it affects, who approved the operational update and when staff or customers were notified. Do not overwrite a historical rule without preserving the version used for earlier decisions. This method supports clearer corrections and more defensible records while avoiding the false impression that any unofficial guide can guarantee approval or payment.

Six visual checks

Six visual checks around a Arizona invoice

Use these as a sequence: verify the source, pass every eligibility layer, confirm the expense, assemble the packet, follow the transaction status, then match the deposit. Each visual summarizes a separate decision and the official program still controls.

Arizona education provider reviewing the official Empowerment Scholarship Account (ESA) source beside dated research notes — 1. Trace every material rule to the official program before acting.

ESA provider organizing business, qualification and approval evidence for the Arizona Empowerment Scholarship Account (ESA) — 2. Test business, professional, offering and transaction eligibility separately.

ESA provider comparing educational products and service evidence with Arizona ESA expense categories — 3. Confirm the expense, provider, student context and transaction together.

ESA provider assembling an itemized Arizona ESA invoice with service, order and fulfillment records — 4. Connect every invoice line to truthful source evidence.

ESA provider reviewing ClassWallet submission, review, approval and settlement statuses for Arizona — 5. Treat submission, review, approval and bank settlement as different events.

ESA provider matching a Arizona ESA invoice, approved amount, remittance, fee and bank deposit — 6. Match the request, decision, adjustment and deposit before closing the record.

Continue the Arizona research path

Connected Arizona ESA guides and tools

These pages divide the same program into distinct search questions. Use the vendor guide for approval, the invoice guide for document review, the payment guide for transaction status, and the provider guide for category-specific operations.

Complete Arizona ESA vendor guide → Application, eligibility and operating workflow Arizona ESA vendor payment guide → ClassWallet status, settlement and reconciliation Arizona ESA for Microschools → Provider-specific approval, invoicing and payment controls Arizona ESA for Tutors → Provider-specific approval, invoicing and payment controls Arizona ESA for Therapists → Provider-specific approval, invoicing and payment controls Arizona ESA for Curriculum & resource sellers → Provider-specific approval, invoicing and payment controls Build a state-aware ESA invoice → Create an itemized document and check the recorded Arizona fields. Check an ESA invoice before submission → Review document risks without claiming that any unofficial tool guarantees approval.

Arizona ESA invoice FAQ

What does a Arizona ESA invoice need to include?

The current GetESAPaid Arizona rules record contains the fields listed on this page, including state-added fields where recorded. The official program and the selected payment path control the live requirement, so verify the current handbook or portal before submitting.

Why do Arizona ESA invoices get returned?

A real return must be diagnosed from its portal message. Pre-submission checks include identity, dates, itemization, category description, arithmetic, applicable credentials and using the document requested for that payment path; these are risk checks, not a claim about the most prevalent cause.

Can I use my own invoice template for Empowerment Scholarship Account?

The official source linked here does not establish a universal answer for every category and workflow. A custom document must still contain the current required information and use the format or portal route requested for the transaction.

Are receipts enough for Empowerment Scholarship Account?

It depends on the payment path. An invoice requests payment, while a receipt proves payment already occurred. Reimbursement may request both an itemized document and proof of payment; vendor pay or marketplace workflows can request different evidence.

How do I submit an invoice to ClassWallet?

Use the transaction route displayed for the current Arizona program, provider category and expense. Preserve the submission reference and status; do not assume every ClassWallet program uses the same family-approval or upload sequence.

What records should Arizona vendors keep?

The current state record includes: Facility Accreditation Attestation Form (tutoring vendors), Itemised receipts, Curriculum statements connecting materials to the student's education, Quarterly documentation uploads to ClassWallet (by the end of the month after each quarter), Current (non-expired) credentials — expired credentials invalidate payment requests. Also keep the final document, applicable service or fulfillment evidence, status history and payout match, subject to current retention and privacy duties.

Not legal advice. Verify against the official Empowerment Scholarship Account handbook before submitting. Back to the Arizona vendor guide →