TRUSTEE OS
← Journal · US

Classification and voting: similar claims are the beginning, not the whole test

A defensible voting structure connects legal similarity, treatment, and a reproducible ballot record.

A class is more than a reporting category

Section 1122(a) permits a claim or interest to be placed in a class only if it is substantially similar to the other claims or interests in that class. The wording establishes a constraint; it should not be rewritten as a universal command that every similar claim must always share one class. The classification analysis needs to examine the characteristics relevant to the proposal and the applicable legal context.

The thesis is that classification should be explained before ballot results are used to defend the plan. A label such as trade, lender, or other creditor may be convenient for financial reporting but may not answer the legal question. Claims can differ in priority, security, rights, or dispute status. The team should maintain a bridge from the claims register to proposed classes and then to treatment, identifying which differences support each classification choice.

Efficient coordination or engineered acceptance?

Separate classes can make a plan easier to explain and implement. They can also raise concerns that the structure was chosen principally to produce a favourable voting outcome. Section 1122(b) specifically permits a class of smaller unsecured claims within its terms, but that provision does not resolve every other classification debate. The fact that a grouping improves administration does not eliminate the need for a reasoned legal basis.

Section 1126 governs acceptance and rejection, including the statutory thresholds for an accepting class of claims and the treatment of impaired or unimpaired positions. Reviewers should distinguish claim amount, claim count, actual votes, and eligibility for the relevant calculation. A recovery chart is not a ballot tally. Likewise, a proposed distribution that appears attractive does not establish that a class accepted the plan under the statute.

Keep classification, ballots and treatment in one version

The practical workflow starts with an identified claim, its proposed class, and the rationale for that placement. Ballot records then link to the relevant amount and status. Any change in ownership, allowance, or treatment should be reflected in the correct version rather than silently altering an earlier tally. Disputed records need explicit handling under the relevant procedure, not an assumption that missing information means support.

A useful review also tests the financial effect of the classification design. Compare distributions, timing, interest, and other rights across proposed groups, while keeping the legal question separate from the arithmetic. The opposing concern deserves a substantive answer: why is the grouping coherent, and how does it relate to the reorganized business? Classification and voting can support legitimate coordination when they remain traceable. They become harder to assess when a presentation shows only a final acceptance percentage and leaves the underlying claims, rules, and choices invisible to everyone except the drafter.

Primary sources

  1. [1] 11 U.S.C. § 1122 — official GPO edition — § 1122(a)–(b) ↗

    Substantial similarity within a class and the convenience-class provision.

  2. [2] 11 U.S.C. § 1126 — official GPO edition — § 1126(a), (c), (f) and (g) ↗

    Acceptance and rejection rules, including class-of-claims voting and impairment-related provisions.