Income Share Agreement Accounting: How Bootcamps Should Recognize ISA Revenue

A student walks into a coding bootcamp having paid nothing up front. Twelve weeks later they graduate, land a $75,000 developer job, and start sending the school 15% of their paycheck every month for the next two years. The school's bank account fills up gradually, unpredictably, and only if that student actually gets hired.

Now ask the obvious question: when did the school actually earn that revenue? On day one, when it delivered the curriculum? On graduation day? Or only as each paycheck-linked payment arrives — some of which may never arrive at all?

This is the accounting puzzle at the center of income share agreements (ISAs), and it's one that a lot of bootcamps, trade schools, and alternative education providers get wrong — sometimes with regulatory consequences far more serious than a restated financial statement.

What an Income Share Agreement Actually Is​

An ISA replaces upfront tuition with a promise: the student pays nothing (or a small deposit) to attend, and in exchange agrees to pay the school a percentage of their income for a fixed period after graduation — but only once they're earning above a minimum salary threshold.

Terms vary widely by school, but the common shape looks like this:

• Income percentage: typically 8%–25% of gross monthly income
• Duration: usually 1–4 years of payments after the student starts earning above the threshold
• Minimum salary threshold: commonly $35,000–$50,000 per year before any payment is owed
• Repayment cap: many programs cap total repayment at roughly 1.5x–1.75x the sticker-price tuition, so a fast high-earner doesn't pay indefinitely

A few real-world examples illustrate the range: one well-known bootcamp structured its ISA at 17% of income for two years with a $50,000 salary floor; another used a lower 7.75% rate stretched over five years with a $35,000 floor; a third capped total payments at a flat dollar amount regardless of how long it took to hit it. No two ISA programs are priced the same way, which is exactly why they're so hard to account for consistently.

Contrast that with deferred tuition, which sounds similar but is fundamentally different: deferred tuition is a fixed total cost paid in installments after employment starts — more like a payment plan than a variable contract. Deferred tuition behaves like ordinary accounts receivable. An ISA behaves like nothing else in a typical school's chart of accounts, because the total amount owed is unknown, unknowable, and contingent on a human being's future career.

Why ISAs Break Normal Revenue Recognition​

Under ASC 606, the standard five-step revenue model assumes you can determine a transaction price. Step 3 is literally "determine the transaction price" — and for a fixed-tuition program, that's trivial. For an ISA, the transaction price isn't fixed; it's a range of possible outcomes:

• The student could get hired quickly at a high salary and pay off the cap fast.
• The student could get hired slowly, at a modest salary, and pay a smaller total.
• The student could never clear the minimum salary threshold and pay the school nothing at all.

This is a textbook case of variable consideration. ASC 606 requires the school to estimate variable consideration using either the "expected value" method (probability-weighted average across likely outcomes) or the "most likely amount" method, and then apply the constraint: the estimate must be reduced to the amount that's not probable of a significant future reversal. In plain terms, a school can't book the full expected repayment as revenue on day one — it has to hold back enough of the estimate that its books won't need a dramatic write-down later when actual placement and salary outcomes come in below projections.

That constraint isn't optional conservatism — it's the mechanism that keeps schools from overstating revenue based on optimistic job-placement assumptions, which is precisely the failure mode regulators have gone after.

The bigger complication: is it revenue at all?​

Here's where ISA accounting gets genuinely thorny, and where a lot of bootcamps have stumbled into regulatory trouble rather than just an accounting technicality. In March 2022, the U.S. Department of Education ruled that ISAs constitute private education loans. That reclassification matters enormously for how a school should book them:

• If an ISA is a loan, the school isn't earning tuition revenue over time as payments come in — it delivered the education service upfront (or over the enrollment period) and should have recognized that revenue then, based on the fair value of the loan/receivable it created, not the eventual cash collected.
• The ongoing income-share payments the school collects afterward are then a mix of principal recovery and imputed interest income on that loan receivable — governed by financial-instrument and receivables guidance (ASC 310/326), not ASC 606's variable-consideration framework.
• This means schools that were quietly recognizing ISA cash as it arrived — treating it like layaway tuition — were arguably misstating both when revenue was earned and what kind of income it was.

This isn't a hypothetical academic distinction. The CFPB has taken enforcement action against ISA-based bootcamps for exactly this kind of mischaracterization: one prominent bootcamp was found to have told students its income-share contracts "were not loans," when regulators determined they carried an implicit finance charge (effectively interest) averaging around $4,000 per student. The school was permanently banned from consumer lending activity and its CEO was banned from student lending for a decade. A separate class-action suit against a different bootcamp and its ISA administrator alleged similarly deceptive practices.

The lesson for anyone running or advising an ISA-funded school: how you talk about an ISA to students and how you book it internally need to be consistent with each other and with how regulators now classify the instrument. If it walks and quacks like a loan for compliance purposes, it should probably be booked like one, too.

A Practical Framework for Booking ISA Revenue​

For a school (or bookkeeper) trying to get this right, a defensible approach looks like this:

1. Determine whether the ISA is structured as a loan or a tuition-deferral contract. This is a legal and structural question first — look at how the ISA agreement itself is drafted, whether a third-party loan originator or servicer is involved (many programs use outside administrators to fund and service ISAs), and how your state and federal regulators would characterize it. Get this wrong and everything downstream is wrong too.

2. If treated as a financing arrangement, recognize education revenue when the service is delivered (i.e., during the program, same as a cash-pay student), and separately track the ISA receivable at estimated fair value, with future collections split between principal and interest income as they arrive.

3. If treated as variable-consideration tuition revenue, estimate the transaction price using historical placement rates, salary outcomes, and attrition data for prior cohorts — then apply the ASC 606 constraint before recognizing anything. Update that estimate every reporting period as real payment data comes in, and be ready to true it up (in either direction) as actual outcomes diverge from the model.

4. Track cohort-level outcome data obsessively, regardless of which method you use. Placement rate, average starting salary, time-to-payment-start, and default/never-pay rate by cohort are the inputs that make your revenue estimate defensible — both to an auditor and to a regulator asking how you calculated your job-placement claims.

5. Reserve for non-payment realistically. A meaningful share of ISA students never clear the minimum salary threshold, and estimating too rosy an outcome is the single most common way schools have gotten into trouble — both financially and legally.

For most small and mid-sized schools without a public-company audit requirement, the practical version of this is simpler than it sounds: keep the ISA receivable ledger separate from tuition revenue, record revenue conservatively against actual and reasonably probable collections rather than optimistic projections, and revisit the estimate every quarter rather than "set and forget" it at enrollment.

Why Clean Books Matter More for ISA-Funded Schools​

Schools running ISA programs are, whether they intend to be or not, running a small lending operation alongside an education business. That combination draws more regulatory attention than tuition-only schools ever face — from the CFPB, from state attorneys general, and increasingly from the Department of Education. Clean, auditable, contemporaneous financial records aren't just good practice here; they're the difference between being able to demonstrate your placement-rate and revenue claims were reasonable at the time versus discovering, in an investigation, that your books can't support what you told students.

That's a much broader lesson than ISAs alone: any business with variable, contingent, or deferred revenue — subscription businesses, royalty deals, revenue-share partnerships — benefits from keeping a transparent, versioned record of exactly what was estimated, when, and on what basis, rather than a single opaque revenue number that's hard to reconstruct later.

Keep Your Financial Records Transparent and Auditable​

Whether you're managing ISA receivables, deferred tuition, or any other form of variable revenue, the underlying discipline is the same: know exactly what you've recognized, why, and when the estimate changed. Beancount.io offers plain-text accounting that's transparent, version-controlled, and easy to audit — every adjustment to a revenue estimate is a diffable, timestamped change rather than a black-box update. Get started for free and see why finance teams handling complex or contingent revenue are switching to plain-text accounting.