# GASB 96 for colleges and universities: finding and reporting every SBITA

> Source: https://www.usehabeo.com/blog/gasb-96-sbita-higher-education
> Published: 2026-11-20
> Updated: 2026-11-20
> Tags: compliance, gasb, gasb-96, sbita, saas

*GASB 96 puts cloud subscriptions on a public university's balance sheet. The accounting is the easy part. Finding every subscription on campus is the hard part.*

GASB Statement No. 96, *Subscription-Based Information Technology Arrangements*, has applied to public colleges and universities since fiscal years beginning after June 15, 2022. For an institution with a June 30 year-end, FY2023 was the first year. Most controllers' offices got through that first close with a spreadsheet and a lot of email. The question now is whether the second, third and fourth closes keep depending on someone remembering which departments bought what.

This guide covers what GASB 96 asks for, where higher education trips over it, and the inventory work that makes the accounting repeatable.

## What is GASB 96?

GASB 96 is the Governmental Accounting Standards Board's standard for cloud software and other subscription IT. It requires a government — including a public college or university — to recognize a **subscription liability** and an intangible **right-to-use subscription asset** for each subscription-based IT arrangement (SBITA) it holds, much as GASB 87 does for leases.

Before GASB 96, most institutions simply expensed SaaS invoices. Now a multi-year Canvas, Workday, Slate or Salesforce contract shows up on the statement of net position, and the asset is amortized over the subscription term.

Private, nonprofit institutions don't follow GASB. They report under FASB, where cloud computing arrangements are generally service contracts and only qualifying implementation costs are capitalized (ASC 350-40). If you're at a private college, the inventory advice below still applies; the journal entries don't.

## What counts as an SBITA?

An SBITA is a contract that conveys control of the right to use another party's IT software, alone or together with tangible capital assets, for a period of time, in an exchange or exchange-like transaction. In practice that covers:

- SaaS platforms: the LMS, the CRM, the SIS if it's hosted, research administration, ticketing.

- Hosted software bundled with hardware, when the software isn't an insignificant part of the deal.

- Multi-year enterprise agreements for productivity or security suites.

Some things are explicitly out:

- **Perpetual licenses.** You own those outright; they're intangible assets under GASB 51.

- **Contracts where the software is incidental to a tangible asset.** That's a lease under GASB 87.

- **Public-private and public-public partnerships**, which GASB 94 covers.

The test that matters most day to day is *control of the right to use*. If the contract gives the institution the right to obtain the software's present service capacity and to determine how it's used, it's in scope, even if no one in central IT has heard of it.

## Is there a short-term exception?

Yes. A **short-term SBITA** is one whose maximum possible term is 12 months or less, including any options to extend, regardless of how likely you are to exercise them. Short-term SBITAs skip the asset and liability entirely; you expense the payments as the contract calls for them.

This is where most of a campus's long tail lands: the month-to-month survey tool, the annual design-software seat, the one-year analytics pilot. The catch is the word *maximum*. A one-year contract that auto-renews, or that offers a renewal option, isn't short-term just because each invoice covers a year. Read the term and renewal language, not the invoice.

## How is the subscription measured?

The headline mechanics follow GASB 87:

1. **Subscription term.** The period you have a noncancellable right to use the software, plus extension periods you're reasonably certain to exercise and termination-option periods you're reasonably certain *not* to exercise.

2. **Subscription liability.** The present value of the subscription payments expected over that term. Discount at the rate the vendor charges if it's known; otherwise use your incremental borrowing rate.

3. **Subscription asset.** The liability, plus payments made at or before commencement, plus capitalizable implementation costs, less any vendor incentives received.

4. **Amortization.** Straight-line over the shorter of the subscription term or the useful life of the underlying IT assets.

GASB doesn't set a dollar threshold for SBITAs. Many institutions apply a materiality-based capitalization policy so a $900 annual subscription doesn't turn into an amortization schedule. Set that policy deliberately, write it down, and agree it with your auditors before year-end rather than during fieldwork.

## Which implementation costs get capitalized?

GASB 96 sorts implementation activity into three stages:

- **Preliminary project stage** — evaluating alternatives, choosing a vendor, deciding to proceed. Expense as incurred.

- **Initial implementation stage** — configuration, coding, installation, testing, and other work to put the subscription asset into service. Capitalize into the subscription asset.

- **Operation and additional implementation stage** — maintenance, troubleshooting, and ongoing use. Expense as incurred, unless the activity adds functionality the asset didn't have.

Training is expensed whatever the stage. For a large ERP or SIS cutover, the capitalizable implementation costs can dwarf the first year of subscription fees, so the project's cost tracking needs to separate stages from the first invoice, not reconstruct them afterwards.

## Why is GASB 96 hard in higher education?

Not because of the present-value math. Because of decentralization.

A typical public university has central IT contracts, procurement-run enterprise agreements, and then hundreds of subscriptions bought by departments, labs, centers and individual faculty — on purchasing cards, on grants, through reimbursements, or through a PunchOut catalog nobody in finance reviews line by line. GASB 96 doesn't care who signed. If the institution is the subscriber and the arrangement is in scope, it belongs on the schedule.

The first-year scramble usually looks like this:

1. Controller's office pulls accounts-payable and P-card transactions coded to software or "dues and subscriptions."

2. Someone filters out the obvious non-software and emails every department about what's left.

3. Contracts are requested, found or not found, and read for term and renewal language.

4. Anything material goes into a lease-and-SBITA workbook or tool; the rest is documented as short-term or below threshold.

Every step depends on a list of subscriptions that nobody maintains between closes. Next year, the scramble repeats.

## How do you build a GASB 96 inventory that lasts?

Treat the subscription list as an asset register, not a year-end report. The same discipline that keeps hardware auditable keeps SBITAs auditable.

**Record each subscription once, with the fields GASB 96 needs.** Vendor, product, contract owner, department, funding source, start date, end date, renewal and termination options, payment schedule, and whether it's been assessed as short-term, below threshold, or reportable. The assessment and its reasoning belong on the record, not in last year's email thread.

**Feed it from where purchases actually happen.** AP and P-card exports are the most complete source on most campuses. Run them through the register on a schedule — monthly is plenty — so a new subscription is flagged within weeks, not discovered at close.

**Tie subscriptions to people and departments.** When the faculty member who bought a tool leaves, the renewal still arrives. Knowing who owns each subscription is what lets you reclaim unused seats before the renewal and keeps the term data current.

**Keep renewal dates in front of someone.** A renewal is the moment a short-term arrangement quietly becomes a multi-year one, or the moment a reportable SBITA gets renegotiated. A renewal pipeline that procurement and the controller both watch catches remeasurement events as they happen.

**Reconcile before close, not during it.** A quarterly pass that compares the register to AP spend, and flags new vendors with no record, turns year-end into a review instead of a hunt.

## Where Habeo fits

Habeo keeps SaaS in the same ledger as hardware and people. Each subscription carries its vendor, seat count, cost per seat, billing cadence, contract start and renewal dates, whether it auto-renews, and the grant fund paying for it, with seats assigned to named people. That's most of what a GASB 96 term assessment starts from, so the register *is* the starting list rather than a copy of it. License activity can be imported by CSV, which flags idle seats ahead of the renewal, and the renewal pipeline puts upcoming term changes in front of procurement and finance. See the [SaaS license management feature](/features/saas) for how that works.

To be clear about the boundary: Habeo is the inventory, not the general ledger. It doesn't compute your subscription liability or post amortization entries. Its job is to make sure the list you hand to whoever does — your ERP's lease module, a dedicated lease-accounting tool, or the controller's workbook — is complete and current.

## A year-end GASB 96 checklist

- Pull AP and P-card software spend for the fiscal year and reconcile it to the subscription register.

- For each new or renewed subscription, record the maximum possible term including options.

- Classify each one: short-term, below your capitalization policy, or reportable.

- For reportable SBITAs, confirm the payment schedule, discount rate and commencement date.

- Separate implementation costs by stage for any subscription that went live this year.

- Flag modifications, terminations and renewals since the prior close for remeasurement.

- Document the capitalization policy and any changes to it.

Related reading: [GASB 34 and 35 capital assets for public universities](/blog/gasb-34-35-capital-assets-universities) covers the tangible side of the same balance sheet, and the [glossary entry on GASB 96](/glossary/gasb-96) is the short version of this page.

*This article explains the standard in general terms and isn't accounting advice. Confirm your institution's policies and conclusions with your auditors.*
