Microschool Billing Software: What Founders Actually Need (and What They Don't)

Why microschool billing is different

A traditional private school invoice is simple: family owes $X, due on this date. A microschool invoice is more complicated. Many families have an ESA scholarship that covers part of tuition. The school receives some money from the ESA program and the rest from the family directly. A single invoice needs to reflect both.

This is called dual-status billing, and it's the one billing feature that most general-purpose invoicing software doesn't support.

What dual-status billing actually means

Take a family with a $7,200/year Step Up For Students scholarship and $12,000/year tuition at your microschool:

• Monthly ESA portion: $600 (Step Up reimburses this after submission)
• Monthly private pay: $400 (parent pays directly)
• Monthly invoice total: $1,000

Your invoice needs to show:

• ESA portion: $600 — Status: Submitted / Pending / Approved / Paid
• Private pay: $400 — Status: Paid / Unpaid / Late

These two statuses change independently. The ESA reimbursement might be sitting in pending while the private-pay portion was paid on time. Or vice versa.

Standard invoicing tools (QuickBooks, FreshBooks, Wave) show one status per invoice. They have no concept of an ESA reimbursement pipeline.

The microschool billing software checklist

When evaluating billing software for a microschool, look for:

Dual-status invoicing

• ESA portion tracked separately from private-pay portion
• Each portion has its own status (submitted, approved, paid)
• Dashboard shows outstanding balances for each payment type

ESA program integration

• Step Up For Students reimbursement tracking
• ClassWallet tracking
• Manual ESA tracking for other state programs
• Stall detection (flags requests pending over 21 days)

Stripe payment processing

• Parents can pay the private-pay portion online
• Automatic receipts on payment
• Stripe fee handling (passed to school or absorbed)

Invoice history by family

• Full billing history per family, going back to enrollment
• Searchable and exportable
• Current balance visible at a glance

Parent portal billing view

• Families can see their current invoice, balance, and ESA status
• Reduces "what do we owe?" emails to near zero

Why QuickBooks doesn't work for microschool billing

QuickBooks handles invoicing and payments well. It does not handle:

• ESA reimbursement tracking
• Dual-status invoicing
• Step Up or ClassWallet integration
• Compliance document attachment to invoices
• Parent portal with ESA status visibility

You end up running QuickBooks for general accounting and a separate spreadsheet for ESA tracking. These two systems drift apart, and reconciliation becomes a weekend project.

Why Stripe alone doesn't work

Stripe is a payment processor, not a billing system. It handles credit card and ACH payments well. It does not:

• Generate microschool-specific invoices
• Track ESA reimbursement status
• Organize billing history by family
• Create a parent portal
• Generate compliance-ready reports

Many microschool founders use Stripe for payment processing + another tool for billing. This works, but creates fragmentation. Cohorta uses Stripe as the payment processor under the hood while building the microschool-specific billing layer on top.

What microschool billing looks like in practice

In a well-run billing system for a 20-student microschool:

• Monthly invoices are generated in bulk (all families, one action)
• Each invoice shows ESA status and private-pay status separately
• Families pay the private portion online via Stripe link in the invoice email
• ESA submissions are tracked in the same system, linked to the same invoices
• Parent portal shows each family's current balance and ESA status
• End-of-month reconciliation: dashboard shows total ESA revenue vs. total private-pay revenue vs. total outstanding

This is what Cohorta's billing module is built to do.