How to become an ESA vendor in Alabama

Detailed operating guide

A full Alabama vendor application and operating plan

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 CHOOSE Act source, category guidance, provider agreement and in-portal instruction.

Start with six separate approval questions

A vendor application is easier to manage when “approved” is not treated as one vague condition. First ask whether the legal business can participate. Second, verify whether the person actually delivering a regulated or credential-gated service qualifies. Third, map each offering to a current expense or provider category. Fourth, check the student or account context without collecting more personal information than the workflow requires. Fifth, follow the payment path assigned to that transaction. Sixth, preserve enough evidence to explain the approved amount and eventual deposit. A green answer at one layer does not silently answer the other five.

For Alabama, the recorded program is CHOOSE Act and the recorded payment surface is ClassWallet. Those two names belong together in your internal procedure. Do not copy another state’s application, document list, fee assumption or payout timing simply because it uses the same platform. Use a folder, account label or operating checklist that includes the state and program name so staff do not submit the right document to the wrong workflow.

Work through every recorded application condition

The following conditions come from the structured Alabama record. For each one, keep three things together: the source instruction you relied on, the evidence you submitted, and the resulting status or correspondence. This creates a review trail and makes a later renewal or correction far less dependent on memory.

Build an offering catalogue that can survive review

Provider approval and offering approval are not always the same decision. Create a catalogue in which each service or product has a truthful public name, a plain-language educational purpose, the proposed program category, price and unit, applicable credential, delivery method, and the evidence you will retain after fulfillment. Avoid category stuffing: a broad educational purpose does not automatically turn an ordinary consumer purchase into an allowed expense.

Design the invoice before the first sale

Do not wait for a payment request to discover that the service log, product identifier or account information was never captured. Map every recorded invoice field to a source in the ordinary workflow. Identity fields should come from controlled business and customer records. Service dates and quantities should come from delivery logs. Product details should connect to order and fulfillment records. Prices and totals should calculate from the displayed units rather than being typed as disconnected numbers.

1. 1. Provider (vendor) full legal name and address. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
2. 2. Student's full name. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
3. 3. Parent / account-holder name. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
4. 4. Invoice date and the dates of service covered. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
5. 5. Itemised description of each service or product. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
6. 6. The educational subject / purpose of each service. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
7. 7. Quantity / hours, unit price, and total amount due. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.
8. 8. Provider credentials or license where the service requires one. Decide where this value originates, who verifies it, and what evidence supports it. Put the field in the template only when it applies, but do not omit a current state-required element because a national template calls it optional. Review the live transaction instruction before submission.

Turn Alabama dates into provider actions

A program date is not a revenue forecast. It is a planning signal that should trigger a source recheck, capacity decision or customer communication. Keep the official date beside the operational action and note when it was verified.

January 2, 2026 — 2026-2027 new-applicant family portal opens

Reopen the official guidance before this date, confirm that the event still applies, and decide whether application staffing, inventory, appointment capacity or customer communication needs to change. Education Service Provider applications are accepted year-round. Preserve the source version used for the decision.

July 1, 2026 — 2026-2027 ESA funds usable for approved expenses

Reopen the official guidance before this date, confirm that the event still applies, and decide whether application staffing, inventory, appointment capacity or customer communication needs to change. The current record does not add a separate operational note, so do not infer a funding or payment promise from the date alone. Preserve the source version used for the decision.

Three realistic vendor scenarios

A service business with several professionals

The business account may be accepted while the program still needs evidence for each person delivering a regulated or credential-gated service. Maintain a roster that connects the professional, credential or background status, effective dates, approved service category and delivered sessions. When staffing changes, verify the new professional before ESA-funded work begins. The invoice should identify the real service and period without disclosing unnecessary clinical or student information.

A seller with mixed eligible and ordinary products

Separate offerings at the catalogue and invoice level. A mixed order can be difficult to review if an allowed educational item, shipping charge, subscription, accessory and unrelated consumer item are collapsed into one line. Use distinct identifiers, descriptions, quantities and prices. Preserve the order, any approval, and fulfillment evidence. If the current workflow excludes or treats a line differently, do not hide it inside a broader educational description.

A provider serving more than one state

Create a separate rule set for Alabama even if the same staff, service and payment platform appear elsewhere. State program identity, provider review, expense definitions, credentials, authorizations, document fields, fees and settlement instructions can differ. The safest reusable asset is the underlying truthful evidence; the submission wrapper should be built for the current program rather than cloned from another state.

Source-check and revision protocol

Before relying on this page, reopen the official CHOOSE Act 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

The Alabama provider evidence chain in six visuals

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.