Give government grants their own subledger.

A model arrives, and the long pole is the data.

On 4 December 2025 the FASB issued Accounting Standards Update No. 2025-10, Government Grants (Topic 832): Accounting for Government Grants Received by Business Entities. The Update opens by stating the problem it solves: GAAP did not provide specific authoritative guidance about the recognition, measurement and presentation of a grant received by a business entity from a government. In its absence, many entities analogised to IAS 20, and some to Topic 450 on contingencies or to Subtopic 958-605 on not-for-profit revenue recognition, and when applying that guidance by analogy they did not always apply all of it. The Board says plainly that this produced diversity in practice.

Topic 832 already existed, but only as a disclosure Topic. ASU 2021-10, issued in November 2021, added the requirement to disclose the nature of transactions with a government, the accounting policies applied, the line items and amounts affected, and the significant terms and conditions including any provisions for recapture. That has been in force for annual periods beginning after 15 December 2021, which for most calendar year companies means every annual report since 2022 has carried some version of it.

The new Update is effective for public business entities for annual reporting periods beginning after 15 December 2028, and for everyone else a year later. Early adoption is permitted for any period whose financial statements have not yet been issued. Three years is a comfortable runway for a policy decision, and it is not a comfortable runway for the thing that actually takes time, which is assembling condition level information about awards signed years ago by people who negotiated them for reasons that had nothing to do with accounting.

That gap between the easy half and the slow half is the opportunity here. Almost everything the new model asks for, the conditions attached to an award, whether compliance with them is probable, what the money was conditioned on, and what would trigger a clawback, is information a company already needs for the disclosure it owes today. Build the record once and it serves the note you are already writing and the recognition model you will owe in 2029. Leave it and you will be assembling the same facts twice, the second time under a deadline.

What counts as a grant, and what quietly does not.

The Master Glossary defines a government grant as a transfer of a monetary asset or a tangible nonmonetary asset, other than in an exchange transaction, from a government to an entity. The definition carries a useful parenthetical: an exchange transaction is still an exchange transaction even where it is at a significant discount to fair value. Paragraph 832-10-15-2 applies the Topic to all entities other than not-for-profit entities and employee benefit plans within the scope of Topics 960, 962 and 965.

The word government is drawn broadly. Paragraph 832-10-15-5 covers domestic, foreign, local, regional and national governments and entities related to them, including departments, independent agencies, boards, commissions and component units, and extends to intergovernmental organisations and to other organisations such as nongovernmental organisations or government-sponsored enterprises that have authority from a government to administer grants on its behalf. A grant that reaches you through an intermediary is still a grant.

The practical consequence of that table is that a single negotiated incentive package can span three or four different accounting outcomes. A state deal that combines a construction grant, a parcel of land, a property tax abatement and a subsidised training programme produces one grant related to an asset measured under this Topic, one tangible nonmonetary asset also under this Topic but measured differently depending on the election, one item outside the Topic entirely because it reduces a liability rather than transferring an asset, and one item outside it because it is a service. Splitting the package is the first piece of real work, and paragraph 832-10-55-7 acknowledges as much, noting that where a grant arrives as part of a package of financial or fiscal aid containing a number of conditions, judgement is needed to identify the conditions that determine the periods over which the grant is recognised.

The recognition gate is three tests, and one of them is about you.

Paragraph 832-10-25-1 is short and worth reading closely. An entity shall not recognise a government grant until it is probable both that the entity will comply with the conditions attached to the grant and that the grant will be received, and until it meets the recognition guidance for a grant related to an asset or a grant related to income. That is two probability tests, plus a spend test that comes from the recognition guidance the second limb points to.

The first test is the interesting one, because it is a judgement about your own future conduct rather than about an external fact. Whether it is probable that you will keep 240 people employed at a site for five years, or complete a build by a stated date, is a question the finance team cannot answer alone and cannot answer once. It has to be formed each period, against conditions that are usually written in a document nobody in the close process has read.

That is a control, and controls need an owner, a cadence and a record. It is also, for most companies, the single piece of the new model with no existing home in any system. A spreadsheet can hold it for a while. What a spreadsheet cannot do is tell you, two years later, what the assessment was in a particular quarter and what it was based on.

The asset election looks like presentation and behaves like architecture.

For a grant related to an asset, paragraph 832-10-25-4 gives two choices. Recognise the grant separately as deferred income, or reflect it as an adjustment to the cost basis in determining the carrying amount of the asset. Both are permitted, both are recognised as the entity incurs the related costs, and on the face of it the choice looks like a presentation preference.

The Update illustrates the difference with a clean example at 832-10-55-8 through 55-11. An entity is awarded a grant of five million dollars to assist with the cost of purchasing a building with a forty year useful life, and that purchase is the only condition attached. Under the deferred income approach the grant sits as deferred income and, once the building is placed in service, is recognised in earnings over forty years in proportion to depreciation, revised if the building is disposed of or impaired. Under the cost accumulation approach the grant reduces the carrying amount and never appears in earnings again as a grant at all. The same five million dollars, two quite different sets of numbers in the accounts.

The place this stops being presentation is repayment. Paragraph 832-10-35-1(b) provides that where a grant related to an asset becomes repayable and the cost accumulation approach was applied, the carrying amount of the asset increases by the amount repayable and all related expenses, such as the cumulative depreciation that would have been recognised in earnings to date in the absence of the grant, are recognised immediately in earnings. Paragraph 832-10-35-2 then sends you back to reconsider impairment and depreciation on the new carrying amount.

Read that as a systems requirement and it says something specific. The cost accumulation election deliberately removes the grant from the face of the ledger, and the repayment guidance then asks you to compute a depreciation history for a cost basis you chose not to record. Nothing in the general ledger can produce that number. It has to come from a memo record that holds the gross cost, the grant applied, and the basis that would have been depreciated. Keeping those three figures is trivial on the day the asset is capitalised and close to impossible to reconstruct seven years later, which is roughly when a recapture clause is most likely to bite.

The artefact: a grant record, with conditions as rows.

Everything above collapses into one object. A grant record holds the award, the split between asset related and income related, the conditions as individually assessable rows, the probable conclusion with its date and author, the election and who made it, the assets it funded at the amounts applied, the recapture terms, and the memo figures the cost accumulation approach removes from view. It is a small record. It is also the only place several of these facts can live.

# Grant register: one record per award, with conditions as rows

grant:
  reference: GR-2026-0042
  title: "Example state capital grant (placeholder)"
  grantor:
    name: "Example State Development Agency (placeholder)"
    level: regional              # local, regional, national, foreign, intergovernmental
    administered_by: "Example State Development Agency (placeholder)"
  award:
    signed_on: 2026-03-11
    total_awarded: 5000000.00
    currency: USD
    form: cash                   # cash | tangible_nonmonetary_asset | forgivable_loan | refundable_credit
    received_to_date: 2000000.00
  classification:
    type: grant_related_to_asset # conditioned on purchase, construction or acquisition
    basis: "Conditioned on constructing the Example Plant. See memo TA-2026-031."
    split_from_package: yes      # the same package also held a tax abatement, out of scope
  recognition:
    probable_compliance: yes
    probable_receipt: yes
    assessed_on: 2026-07-31
    assessed_by: technical.accounting.lead
    basis: "Construction 46 percent complete against the milestone plan; no conditions in breach."
    costs_incurred_to_date: 2300000.00
    recognised_to_date: 1150000.00
  election:
    approach: cost_accumulation  # cost_accumulation | deferred_income
    elected_on: 2026-04-02
    elected_by: group.controller
    presentation: not_applicable # other_income | deducted_from_expense, where deferred income
  linked_assets:
    - asset: FA-118204
      gross_cost: 8400000.00
      grant_applied: 3000000.00
      net_basis: 5400000.00
      useful_life_years: 30      # disclosed under 832-10-50-3B
  conditions:
    - id: C1
      text: "Complete construction of the Example Plant by 31 December 2028."
      status: on_track
      evidence_ref: "PRJ-2026-0091 milestone report"
      last_assessed: 2026-07-31
    - id: C2
      text: "Maintain 240 full time roles at the site for five years from completion."
      status: not_yet_due
      evidence_ref: "HR certification schedule, annual"
      last_assessed: 2026-07-31
  recapture:
    applies: yes
    trigger: "Headcount below 240 measured annually, or disposal of the site."
    period_years: 5
    maximum_amount: 5000000.00
    earliest_exit: 2033-12-31
  memo_only:
    # kept because cost accumulation removes the grant from the face of the ledger
    grant_in_carrying_amount: 3000000.00
    depreciation_absent_grant_to_date: 210000.00
  disclosure:
    policy_note_ref: "FS-2026-832-01"
    last_reviewed: 2026-07-31

The shape matters more than the syntax. Conditions have to be rows rather than a paragraph, because each one carries its own status, its own evidence and its own assessment date. The link to the fixed asset register has to be a relationship rather than a reference in a comment, because the release schedule under the deferred income approach follows depreciation and has to follow it through impairments and disposals. And the memo block exists precisely because the accounting election chosen above it makes those numbers disappear from everywhere else.

The award, the agency, the amounts, the plant and the headcount figures in that record are a placeholder built to show the shape, not a real programme. Every company real award will have its own condition set, and the conditions are the part that resists a template.

An implementation checklist for the runway.

Ordered by what unblocks the most downstream work rather than by what is most urgent, because nothing here is urgent yet and that is the whole point.

• Start an inventory of live awards before you start the policy. Every award the company holds, the government or agency behind it, the conditions attached, the money still to come, and the date the last assessment of compliance was made. Most companies find this faster than expected and find more awards than expected, because incentives are negotiated by people who do not sit in the accounting team.
• Split each award into the part conditioned on acquiring an asset and the part that is not. The definitions at the front of the Update do the work here: a grant related to an asset is conditioned on the purchase, construction or acquisition of an asset, and everything else is a grant related to income. Paragraph 832-10-55-7 notes that a package of aid with many conditions takes judgement to unpick, so record the reasoning at the same time.
• Make the probable assessment a dated record with an owner, not a conversation. Two tests, compliance and receipt, per award, re-formed each period. This is the single piece of the new model that has no natural home in most systems today, and it is also the piece an auditor will ask about first.
• Decide the asset grant election deliberately, and decide it per grant. The Update allows either approach, and the two produce different depreciation, different presentation and very different disclosure. Picking one by default and discovering the consequence at the first repayment is the avoidable version of this.
• Keep a memo record of the grant amount even when you elect cost accumulation. This is the point most likely to be missed. Under cost accumulation the grant is folded into the carrying amount and never appears again in earnings, yet paragraph 832-10-35-1(b) asks you, on a repayment, to work out the depreciation that would have been recognised in its absence. That calculation needs a number your ledger has stopped carrying.
• Capture the recapture terms as structured fields. Paragraph 832-10-50-4 already asks for significant terms and conditions including provisions for recapture and the conditions under which it is allowed. Storing that as a paragraph of prose in a contract folder makes the annual disclosure a research exercise every year.
• Model the release schedule where the depreciation schedule already lives. A deferred income grant on a depreciable asset is released in proportion to depreciation, per 832-10-55-6, and revised if the asset is impaired or disposed of. Wiring it to the fixed asset register rather than to a spreadsheet is what makes the revision automatic.
• Use the disclosure you already owe as the acceptance test. ASU 2021-10 has required the nature of the transactions, the accounting policies, the affected line items and amounts, and the significant terms and conditions since annual periods beginning after 15 December 2021. If the new record cannot produce this year note without help, it is not finished.
• Choose the transition approach early, because it decides what history you need. Paragraph 832-10-65-2 offers a modified prospective approach, a modified retrospective approach and a full retrospective approach. The first two turn on which grants are complete, meaning substantially all the proceeds have been recognised, at a particular date. That is a data question long before it is a policy question.

Failure modes, and what each looks like from inside.

• Treating cash received as the recognition event. It is the most natural mistake and the Update closes it twice, at 832-10-25-2 and again in the Board discussion at BC37. Money can arrive before the costs are incurred, and when it does it sits as a liability rather than in earnings.
• Letting the award document be the only record of the conditions. Conditions decide the recognition pattern, the disclosure, and whether a repayment is coming. A PDF in a shared folder can be read by a person, and cannot be reported on, reminded about, or reconciled.
• Electing cost accumulation without keeping the grant amount anywhere. The election is legitimate and often the simpler presentation, but it deliberately removes the grant from the face of the accounts. A repayment then requires reconstructing a depreciation history for an asset at a cost basis you never recorded.
• Assuming an incentive package is one thing. A single negotiated package can hold a cash grant, a transfer of land, a tax abatement and a training programme, and the Update puts those in different places. The abatement and the training are outside the Topic entirely, per 832-10-55-5, while the cash and the land are inside it under different measurement rules.
• Sorting credits by name rather than by mechanism. The line at 832-10-15-4A(a) is about whether the credit is within the scope of Topic 740, and 832-10-55-4(d) brings a refundable credit outside Topic 740 into grant accounting. Two credits with similar marketing names can land on opposite sides of that line.
• Deferring the work because the effective date is years out. Public business entities have until annual periods beginning after 15 December 2028, and that is genuinely comfortable for a policy memo. It is not comfortable for assembling condition level data on awards signed years earlier by people who have since moved on, which is the part that takes real time.
• Recognising a grant on an asset that has been impaired without revisiting the schedule. Paragraph 832-10-25-5 names depreciation, gain or loss on sale, and impairment as the expenses a deferred income grant is released against, so a change in any of them changes the release. A static schedule quietly stops matching the standard.
• Building the release schedule outside the fixed asset register. It works while there is one grant. It stops working at the first partial disposal, and the reconciliation that follows is harder than the original build would have been.

Data and interface considerations.

• The missing object is a grant record, sitting between the contract and the general ledger. Most finance architectures have somewhere to put a customer contract and somewhere to put a fixed asset, and nowhere at all to put an award with conditions attached. Everything the new model asks for keys off that record.
• Conditions are rows, not a text field. Each condition needs its own status, its own evidence, and its own assessment date, because the probable test at 832-10-25-1(a)(1) is made against the conditions collectively but supported condition by condition.
• The probable assessment is a dated attribute with an author. Store the conclusion, the date, the person, and the basis. The question that actually gets asked later is not whether you thought compliance was probable, but when you thought it and what you knew at the time.
• Grants and assets need a real relationship, not a note. A grant related to an asset points at one or more assets in the fixed asset register, and under the deferred income approach its release has to follow their depreciation. One to many in both directions is common, because one award can fund several assets and one asset can attract several awards.
• Keep the gross cost even when the ledger carries the net. Under cost accumulation the balance sheet holds the reduced figure, and that is correct. The register should still hold the gross cost, the grant applied and the resulting basis as three separate numbers, because the repayment guidance at 832-10-35-1(b) needs all three.
• Recapture provisions belong in structured fields with dates. What triggers recapture, over what period, up to what amount, and what the earliest exit date is. These are the facts that turn into a disclosure once a year and into a real cash question exactly once, without much warning.
• The presentation election is data, not formatting. Whether a grant is shown as other income or deducted from the related expense drives which account the release posts to, so it belongs on the grant record where the policy decision was made and can be seen.
• Model repayment as a supported transaction from the start. It is rare, which is exactly why nobody builds it, and it is the one event in this Topic that requires arithmetic the ledger cannot supply from its own balances.

Audit evidence worth capturing from the first award.

• The award document as executed, with the conditions extracted into fields rather than only stored as a file. The extract is what makes the disclosure repeatable, and the file is what supports the extract.
• The probable assessment for each period, dated, with the person who made it and what they relied on. This is the core judgement in the whole Topic and it produces almost no natural evidence unless somebody designs for it.
• The election made for each asset related grant, with the date it was made and by whom. Paragraph 832-10-50-3(b) requires the accounting policy to be disclosed, naming whether the deferred income or the cost accumulation approach was applied, so the file should show the decision rather than imply it.
• The link between each grant and the assets it funded, at the amounts applied. Under cost accumulation this is the only surviving record of the grant inside the fixed asset population.
• The release schedule with its revisions, and the reason for each revision. Impairment and disposal both change the pattern under 832-10-25-5, and a schedule that has never been revised across a period with disposals in it invites the obvious question.
• The fair value determination for any tangible nonmonetary asset received. Paragraph 832-10-50-3C requires the fair value to be disclosed in the period the grant is recognised even when the cost accumulation approach is applied, so the valuation is needed either way.
• The compliance evidence you actually filed with the grantor, held next to the accounting record. Progress reports, headcount certifications and expenditure claims are the strongest available support for the compliance half of the probable test, and they usually sit in a different department.