A school may be able to sell eligible unpaid tuition and fee receivables, but a portfolio sale is not a routine accounting step. Before transferring accounts or student-linked data, the institution should confirm its authority, the underlying contract rights, applicable privacy rules, and the collection controls that will apply after transfer. A sale can provide agreed upfront proceeds and shift defined collection economics, but it does not remove the school’s responsibility to make a lawful, well-documented decision.
What is an education receivable?
For this article, an education receivable is an amount owed directly to a school or educational institution for services or charges such as tuition, required fees, housing, meal plans, books, or property charges. The account agreement, the person legally responsible for payment, and the institution’s policies determine what is owed and whether the account is suitable for any collection strategy. This is distinct from a federal student loan or another education-finance product administered by a lender or government program.
An account that is past due is not automatically a sound sale candidate. Before an institution evaluates a buyer or an agency, it should be able to identify the agreement or notice supporting the charge, the amount and its components, payments and credits, financial-aid or scholarship adjustments, known disputes, and the present account status. That recordkeeping protects both the institution and the person alleged to owe the balance.
Portfolio sale and agency placement are different models
A portfolio sale and a collection-agency placement can both address delinquent accounts, but they allocate ownership, cash flow, and oversight differently. The transaction documents—not the marketing label—determine the legal effect.
| Question | Portfolio sale | Agency placement |
|---|---|---|
| Who holds the assigned collection rights? | The purchaser receives the rights specified in the sale agreement. | The institution commonly retains the account while an agency acts under its agreement. |
| How is the institution paid? | The purchaser pays the agreed purchase price under the sale terms. | The institution commonly receives recoveries less the agreed agency compensation. |
| What must be reviewed? | Assignment authority, permissible data transfer, buyer practices, and post-sale obligations. | Agency authority, permissible data access, communications practices, and performance oversight. |
Neither model is automatically less burdensome. An institution should compare the actual agreement, the eligible account population, the expected proceeds or costs, and the ability to protect students and account holders. A public institution may also have procurement, governance, records, or other state-law constraints that a private institution does not share.
Resolve authority and privacy before pricing the portfolio
Pricing discussions should follow, not replace, legal and operational review. A practical review normally addresses the following questions:
- Scope: Which account types are in scope, and which must be excluded because of a dispute, adjustment, restriction, or other account-specific issue?
- Contract rights: Do the enrollment, tuition, payment-plan, guaranty, and policy documents support the proposed collection or assignment approach? Who is the actual obligor?
- Institutional authority: Does the institution’s governing authority, policy framework, and—where relevant—state or local law permit the transaction and the contemplated approval process?
- Data disclosure: What information is necessary for due diligence and transfer, and what lawful basis supports each disclosure?
- Security and retention: How will the parties limit access, secure the transfer, manage subcontractors, respond to incidents, and dispose of information when it is no longer needed?
For institutions subject to the Family Educational Rights and Privacy Act (FERPA), the starting point is that personally identifiable information from an education record may be disclosed without consent only when a listed condition is met. The current FERPA regulation at 34 C.F.R. § 99.31 describes those conditions. Its school-official provision can cover an outsourced institutional service or function only when the outside party performs a function the institution would otherwise use employees for, is under the institution’s direct control regarding use and maintenance of records, and is subject to use and redisclosure restrictions.
The U.S. Department of Education further explains that a third party using the school-official exception must also meet the institution’s published school-official and legitimate-educational-interest criteria. See the Department’s school-official guidance. Those criteria do not create a blanket authorization for an arm’s-length purchaser of a receivables portfolio. Counsel should determine whether a proposed data disclosure is supported by valid consent or a specific, applicable exception and should separately assess state privacy law and institutional policy.
For early valuation, an institution can often begin with aggregated or de-identified account characteristics, such as balance bands, aging ranges, and documented account types. Any later disclosure of identifiable account data should be limited to what the approved transaction requires. De-identification is a risk-control technique, not a substitute for the legal analysis of the particular records and transfer.
Collection protections after a transfer
Federal debt-collection rules do not apply in the same way to every institution, account, purchaser, or agency. Regulation F defines a covered consumer debt as an obligation arising from a transaction primarily for personal, family, or household purposes, and defines a debt collector by the entity’s principal purpose or regular collection activity, subject to stated exclusions. The controlling terms are available in 12 C.F.R. § 1006.2. Whether a particular tuition or fee balance, and a particular actor, fall within those definitions depends on the facts; a portfolio label alone does not answer the question.
When an entity is a covered debt collector, 12 C.F.R. § 1006.34 requires validation information in the initial communication, within five days after it, or orally in the initial communication, subject to the regulation’s terms. The rule specifies information about the collector, the creditor, the account and amount, and consumer protections including written disputes during the validation period. State licensing, collection, privacy, and consumer-protection requirements may add obligations, so federal compliance should not be treated as a complete state-law review.
As an operating matter, an institution should vet a proposed buyer’s or agency’s licensing analysis, complaint process, training, vendor oversight, information-security controls, and escalation path for disputes or newly discovered credits. The agreement should make clear who handles communications, who can correct account information, how the institution receives complaints or data incidents, and what records remain available for audit or response. These controls are not a substitute for legal review; they are a way to make that review operational.
Build a usable, controlled portfolio review
Start with documentation, not a face-value total
A buyer will generally need enough information to assess whether the accounts are documented and collectible under the agreed scope. The institution should first reconcile its own records: original obligation records, account statements or ledgers, payment and credit history, adjustments, contact-history controls, and dispute flags. It should separately identify accounts that merit additional legal or policy review rather than treating every past-due balance as interchangeable.
A stated purchase price is not a universal percentage of face value. It reflects the particular account population, documentation, age, balance mix, permitted collection path, data limitations, buyer assumptions, and contract terms. Comparing bids without a common account definition and a record of exclusions can produce a misleading result.
Put controls in the agreement
The parties should use transaction documents to address the account schedule, excluded accounts, permitted data use, security safeguards, subcontractors, consumer-complaint escalation, corrections to balances, record retention, audit cooperation, and the treatment of disputes discovered after closing. The institution should avoid promising documentation or enforceability it has not verified. A well-defined agreement also helps the buyer understand which information is authoritative and where questions must be directed.
A practical decision sequence
- Define the objective: immediate liquidity, outsourced collection work, or another operational goal.
- Map the account types and exclude records that require special handling.
- Obtain legal and compliance review of assignment authority, privacy, consumer-collection, and public-sector requirements.
- Use a controlled, minimum-necessary data process for any approved due diligence.
- Evaluate bids together with buyer practices, security controls, dispute handling, and proposed contract terms.
- Maintain post-transaction oversight for complaints, corrections, data incidents, and retained records.
The disciplined outcome may be a portfolio sale, an agency placement, a narrower account group, or no transfer at all. The appropriate choice depends on the institution’s authority, the documentation, and the real protections available to affected students and account holders.
Frequently asked questions
Can accounts receivable be sold?
Receivables can be transferred when the governing contract and applicable law permit it. For education receivables, an institution should first confirm its authority to assign the accounts and its lawful basis for sharing any student-linked information. For institutions subject to FERPA, the relevant disclosure analysis begins with 34 C.F.R. § 99.31; a proposed buyer should not be assumed to qualify for an exception simply because it wants to evaluate the portfolio.
What is a debt buyer?
In ordinary usage, a debt buyer purchases accounts and then seeks payment itself or through another collector. The legal coverage of a buyer is not determined by that label alone. Under Regulation F’s definitions, whether an entity is a debt collector depends on its business and collection activity, as well as the regulation’s exclusions.
What is the difference between a debt buyer and a debt collector?
A debt buyer is associated with purchasing the account; a debt collector may collect for another creditor or owner. The roles can overlap, because a buyer may also collect accounts. For an entity covered by Regulation F, the validation-notice rule sets specific information that must be provided to consumers. The exact obligations remain fact- and jurisdiction-dependent.
Related reading
For broader portfolio-planning context, read portfolio value planning and data privacy considerations for debt buyers.