Read this if your organization operates under the Governmental Accounting Standards Board (GASB).
GASB Statement No. 96 Subscription-Based Information Technology Agreements
Summary
GASB Statement No. 96 defines the term Subscription-Based Information Technology Agreements (SBITA) as “a contract that conveys control of the right to use another party’s (a SBITA vendor’s) information technology (IT) software, alone or in combination with tangible capital assets (the underlying IT assets), as specified in the contract for a period of time in an exchange or exchange-like transaction.”
GASB Statement No. 96 determines when a subscription should be recognized as a right-to-use subscription, and also determines the corresponding liability, capitalization criteria, and required disclosures.
Why does this matter to your organization?
In 2018, Financial Accounting Standards Board (FASB) issued Accounting Standards Updated (ASU) 2018-15: Cloud Computing Arrangements for Service Contracts, and we knew it would only be a matter of time when a similar standard would be issued by the Governmental Accounting Standards Board (GASB). Today, more and more governmental entities are purchasing software in the cloud as opposed to a software that is housed locally on their machine or network. This creates the need for updated guidance in order to improve overall financial reporting, while maintaining consistency and comparability among governmental entities.
What should you do?
We are going to walk through the steps to determine if a SBITA exists—from identification through how it may be recognized in your financial statements. You can use this step-by-step guide to review each individual subscription-based software to determine if Statement No. 96 applies.
Step 1: Identifying a SBITA
There is one important question to ask yourself when determining if a SBITA exists:
Will this software no longer work/will we no longer be able to log in once the contract term ends?
If your answer is “yes”, it is likely that a SBITA exists.
Step 2: Determine whether a contract conveys control of the right to use underlying IT assets
According to Statement No. 96, the contract meets the right to use underlying IT assets by:
- The right to obtain the present service capacity from use of the underlying IT assets as specified in the contract
- The right to determine the nature and manner of use of the underlying IT assets as specified in the contact
Step 3: Determine the length of the subscription term
The subscription term starts when a governmental entity has a non-cancellable right to use the underlying IT assets. This is the period during which the SBITA vendor does not have the ability to cancel the contract, increase or decrease rates, or change the benefits/terms of the service. The contract language for this period can also include an option for the organization or the SBITA vendor to extend or terminate the contract, if it is reasonably certain that either of these options will be exercised.
Once a subscription term is set, your organization should revisit the term if one or more of the following occurs:
- The potential option (extend/terminate) is exercised by either the entity or the SBITA vendor
- The potential option (extend/terminate) is not exercised by either the government or the SBITA vendor
- An extension or termination of the SBITA occurs
If the maximum possible term under the SBITA contract is 12 months or less, including any options to extend, regardless of their possibility of being exercised, an exception for short-term SBITAs has been provided under the statement. Such contracts do not need to be recognized under the Statement and the subscription payments will be recognized as outflows of resources.
Step 4: Measurement of subscription liability
The subscription liability is measured at the present value of the subscription payments expected to be made during the previously determined subscription term. The SBITA contract will include specific measures that should be used in determining the liability that could include the following:
- Fixed payments
- Variable payments
- Payments for penalties for termination
- Contract incentives
- Any other payments to the SBITA which are included in the contract
The future payments are discounted using the interest rate that the SBITA charges to your organization. The interest rate may be implicit in the contract. If it is not readily determinable, the rate should be estimated using your organization’s incremental borrowing rate.
Your organization will only need to re-measure the subscription liability is there is a change to the subscription term, change in the estimated amounts of payments, change in the interest rate the SBITA charges to your organization, or contingencies related to variable payments. A change in the discount rate alone would not require a re-measurement.
Step 5: Measurement of subscription asset
The SBITA asset should be measured at the total of the following:
- The amount of the initial measurement of the subscription liability (noted in Step 4 above)
- If applicable, any payments made to the SBITA vendor at the beginning of the subscription term
- The capitalized initial implementation costs (noted in Step 6 below)
Any SBITA vendor incentives received should be subtracted from the total.
Step 6: Capitalization of other outlays
In addition to the IT asset, Statement No. 96 provides for other outlays associated with the subscription to be capitalized as part of the total subscription asset. When implementing the IT asset, the activities can be divided into three stages:
- Preliminary project stage: May include a needs assessment, selection, and planning activities and should be recorded as expenses.
- Initial implementation stage: May include testing, configuration, installation and other ancillary charges necessary to implemental the IT asset. These costs should be capitalized and included in the subscription asset.
- Operation and additional implementation stage: May include maintenance and troubleshooting and should be expensed.
Step 7: Amortization
The subscription asset are amortized over the shorter of the subscription terms or the useful life of the underlying IT assets. The amortization of the asset are reported as amortization expense or an outflow of resources. Amortization should commence at the beginning of the subscription term.
When is this effective?
Statement No. 96 is effective for all fiscal years beginning after June 15, 2022, fiscal and calendar years 2023. Early adoption is allowed and encouraged.
Changes to adopt the pronouncement are applied retroactively by restating previously issued financial statements, if practical, for all fiscal years presented. If restatement is not practical, a cumulative effect of the change can be reported as a restatement to the beginning net position (or fund balance) for the earliest year restated.
What should you do next?
With any new GASB Standard comes challenges. We encourage governmental entities to re-review their vendor contracts for software-related items and work with their software vendors to identify any questions or potential issues. While the adoption is not required until fiscal years beginning after June 15, 2022, we recommend that your organization start tracking any new contracts as they are entered o starting now to determine if they meet the requirements of SBITA. We also recommend that your organization tracks all of the outlays associated with the software to determine which costs are associated with the initial implementation stage and can be capitalized.
What are we seeing with early adoption?
Within the BerryDunn client base, we are aware of at least one governmental organization that will be early adopting. We understand that within component units of state governments, the individual component unit is required to adopt a new standard only when the state determines that they will adopt.
If you are entering into new software contracts that meet the SBITA requirements between now and the required effective date, we would recommend early adoption. If you are interested in early adoption of GASB Statement No. 96, or have any specific questions related to the implementation of the standard, please contact Katy Balukas or Grant Ballantyne.