ESA for Microschools in West Virginia

Detailed operating guide

A full West Virginia operating guide for microschools

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

Translate the state program into a microschool workflow

The West Virginia record includes microschools, but a category mention is only the beginning. Build a workflow around enrollment, service, tuition and staff records. Verify the legal entity and every applicable rendering professional, define the offering at the level the program reviews, check the student and transaction context, and follow the assigned ClassWallet route. The current official Hope Scholarship source controls over this educational guide.

Keep sales promises narrower than the evidence. You can explain that the program record contains the provider surface and help a customer follow the current route. You should not promise that a family can use funds for a specific purchase, that approval will occur by a particular date, or that settlement will take the same time as another transaction. Confirm before delivery when nonpayment would create hardship.

Application checkpoints for this provider type

Checkpoint 1: Apply to become an approved Hope Scholarship vendor / service provider.

Identify whether this applies to the business, owner, staff member, offering or payout account. Assign an owner, save the current instruction, submit the correct evidence and record the resulting status. For microschools, connect any credential, background, qualification or offering evidence to the person or service it actually covers rather than assuming the business account extends it automatically.

Checkpoint 2: Onboard with ClassWallet for payments.

Identify whether this applies to the business, owner, staff member, offering or payout account. Assign an owner, save the current instruction, submit the correct evidence and record the resulting status. For microschools, connect any credential, background, qualification or offering evidence to the person or service it actually covers rather than assuming the business account extends it automatically.

Checkpoint 3: Confirm allowable-expense categories for your services.

Identify whether this applies to the business, owner, staff member, offering or payout account. Assign an owner, save the current instruction, submit the correct evidence and record the resulting status. For microschools, connect any credential, background, qualification or offering evidence to the person or service it actually covers rather than assuming the business account extends it automatically.

Assess every recorded expense category conservatively

An expense category can be relevant without matching this provider type. Begin with the real offering, then test it against the current definition, exclusions, provider qualification, student context and evidence. Do not begin with the category name and rewrite the offering to fit.

Could “Tutoring” fit?

Possibly, but the state record alone does not decide the transaction. Compare the real microschool offering with the official definition and current portal route. Check price or quantity limits, authorization, dates, delivery method and supporting evidence. If the match depends on a regulated service, product feature or student circumstance, document that fact accurately and avoid a blanket eligibility statement.

Could “Curriculum & instructional materials” fit?

Possibly, but the state record alone does not decide the transaction. Compare the real microschool offering with the official definition and current portal route. Check price or quantity limits, authorization, dates, delivery method and supporting evidence. If the match depends on a regulated service, product feature or student circumstance, document that fact accurately and avoid a blanket eligibility statement.

Could “Therapies” fit?

Possibly, but the state record alone does not decide the transaction. Compare the real microschool offering with the official definition and current portal route. Check price or quantity limits, authorization, dates, delivery method and supporting evidence. If the match depends on a regulated service, product feature or student circumstance, document that fact accurately and avoid a blanket eligibility statement.

Could “Supplemental instruction” fit?

Possibly, but the state record alone does not decide the transaction. Compare the real microschool offering with the official definition and current portal route. Check price or quantity limits, authorization, dates, delivery method and supporting evidence. If the match depends on a regulated service, product feature or student circumstance, document that fact accurately and avoid a blanket eligibility statement.

Could “Tuition” fit?

Possibly, but the state record alone does not decide the transaction. Compare the real microschool offering with the official definition and current portal route. Check price or quantity limits, authorization, dates, delivery method and supporting evidence. If the match depends on a regulated service, product feature or student circumstance, document that fact accurately and avoid a blanket eligibility statement.

Create an evidence-led service or product catalogue

For each offering, record a stable internal identifier, plain-language name, the approved tuition, instruction or program component, price and unit, delivery or service method, applicable professional or credential, proposed state category, and the evidence retained after fulfillment. This catalogue should drive the website description, portal listing, customer expectation, invoice line and internal ledger so five different versions of the same offering do not drift apart.

Microschools should avoid collapsing tuition, tutoring, supplies, fees and extracurricular items into a single unexplained charge. Review packages, discounts, deposits, cancellations, refunds, subscriptions and shipping separately. Ordinary commercial terms still need to be consistent with the provider agreement and program rules; ESA participation should not be used to obscure charges or limit a customer’s ability to understand what is being purchased.

Build invoice data during delivery, not afterward

The strongest invoice is assembled from ordinary source records. Capture covered period, student, rate or unit and applicable school/provider record as the work or fulfillment occurs. Then the final document can summarize evidence rather than reconstructing it from calendar fragments, messages and memory.

Invoice control 1: Provider (vendor) full legal name and address

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 2: Student's full name

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 3: Parent / account-holder name

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 4: Invoice date and the dates of service covered

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 5: Itemised description of each service or product

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 6: The educational subject / purpose of each service

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 7: Quantity / hours, unit price, and total amount due

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Invoice control 8: Provider credentials or license where the service requires one

Decide which controlled record supplies this value and who checks it. Confirm that the final value matches provider, customer, service, product, date, quantity, price and qualification records as applicable. A complete-looking invoice can still fail when adjacent fields contradict each other or when the selected ClassWallet path requires a different document.

Protect privacy while preserving proof

Collect and disclose only the information the authorized workflow requires. Separate public catalogue content, accounting records, provider credentials, service or fulfillment evidence, and sensitive student or clinical material. Limit access by role, use secure storage, and retain the version actually submitted. “Audit ready” does not mean placing every record into one widely shared PDF.

State-record evidence 1: Approved-vendor status

Check whether the current microschool transaction requires it, what period and person it covers, and who may access it. Name the file so it can be connected to the correct account and invoice without exposing sensitive details. Preserve effective dates and do not substitute a business-level record for individual evidence where the current program distinguishes them.

State-record evidence 2: Itemised invoices

Check whether the current microschool transaction requires it, what period and person it covers, and who may access it. Name the file so it can be connected to the correct account and invoice without exposing sensitive details. Preserve effective dates and do not substitute a business-level record for individual evidence where the current program distinguishes them.

State-record evidence 3: Service records

Check whether the current microschool transaction requires it, what period and person it covers, and who may access it. Name the file so it can be connected to the correct account and invoice without exposing sensitive details. Preserve effective dates and do not substitute a business-level record for individual evidence where the current program distinguishes them.

Three microschool payment scenarios

The offering is approved but the transaction is returned

Preserve the message and distinguish offering approval from student, authorization, document and transaction review. Compare the return with the source evidence, make a versioned correction if supported, and use the existing reference. Do not make the customer resubmit blindly or promise that a cosmetic invoice change will resolve an eligibility issue.

The portal says approved but the deposit is absent

Record the approval date and amount, then check settlement status, payout account, remittance and bank posting separately. Approval is not the same event as settlement. Contact support with the transaction reference and a focused question if the current instruction or agreement indicates the expected next event has not occurred.

The deposit does not equal the invoice

Compare the invoice total, approved amount, line decisions, stated adjustment, authorized fee, payout report and bank deposit. Do not rewrite the historical invoice or infer a standard platform fee from another state. Record the supported difference and investigate any remainder before the transaction is closed.

A practical 30-day launch sequence

Week one: verify the current program and category, assign application owners, inventory business and professional evidence, and identify gaps. Week two: submit the controlled application and build the offering catalogue, invoice fields and fulfillment records. Week three: test the complete customer-to-payment workflow with non-sensitive sample data, train staff on status and privacy controls, and prepare accurate customer language. Week four: review the portal status, answer only documented requests, publish approved offerings where permitted, and begin measuring real conversion, return and settlement outcomes. Do not publish performance claims until the sample is large and representative enough to support them.

Source-check and revision protocol

Before relying on this page, reopen the official Hope Scholarship 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 for Microschools in West Virginia

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.