Warranty Accrual Accounting: Recognition, Measurement, Entries
By MDMS Team · 17 August 2026

Warranty Accrual Accounting: Recognition, Measurement, Entries

Recognize a warranty provision when three conditions line up: a present obligation exists from a past sale, an outflow of resources is probable, and you can reliably estimate the amount. That test comes straight from AASB 137, and it governs almost every warranty accrual decision your team will make this year.
Four standards matter here, and you should be ready to cite all of them in a note or an audit conversation. AASB 137 sets recognition and measurement. AASB 15 governs warranties sold as separate performance obligations. AASB 17 determines whether a warranty is really an insurance contract in disguise. AASB 112 handles the tax effect of the provision once you have measured it.
On measurement, the standard’s rule is simple to state and harder to execute:
- Use the best estimate of the expenditure needed to settle the obligation.
- For large populations of similar warranty items, calculate that estimate as the expected value across all possible outcomes.
- Discount to present value only when the time value of money is material to the amount.
Key Takeaways
A warranty provision under AASB 137 requires a probable outflow and a reliable estimate, measured at expected value for large claim populations and adjusted prospectively as estimates change.
| Point | Details |
|---|---|
| Recognition needs all three tests | Present obligation, probable outflow above 50%, and a reliable estimate must all be satisfied before booking a provision. |
| Assess probability by class | Aggregate probability across the whole population of sales, not the risk of any single unit failing. |
| Use expected value for large populations | Weight each outcome by probability, as in the $400,000 example: Most goods have no defects, some develop minor faults, and a small number develop major faults. |
| Separate assurance and extended warranties | Bundled warranties sit under AASB 137; separately sold coverage defers revenue under AASB 15. |
| Update estimates prospectively | Changes in failure rate or cost adjust the current period’s profit and loss under AASB 108, with no restatement. |
| Centralize claims data for audit readiness | Moderndms consolidates claims, parts, and labor history so provision assumptions are reconciled and exportable. |
Authoritative Sources and Further Reading
- AASB 137 recognition and measurement covers the core provision test, with a worked expected-value example.
- AASB 108 on accounting estimates governs prospective adjustments when claims experience changes.
- AASB 17 guidance on product warranties addresses the insurance scope exclusion and subsidiary pitfalls.
Keep these on hand as audit support alongside your assumptions register.
This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.
Table of Contents
- Recognition Criteria Under AASB 137 for Warranty Provisions
- How Do You Measure a Warranty Provision?
- Assurance Warranties vs. Separately Sold Extended Warranties
- Worked Example: Calculating the Warranty Provision and Journal Entries
- Presenting the Provision and What Your Notes Need to Say
- Handling Changes in Estimate and Contingent Liabilities
- What Data and Controls Support a Defensible Estimate
- Where the Numbers Actually Come From
- What Auditors Actually Flag in Warranty Files
- Making the Data Work for You Instead of Against You
- FAQ
Recognition Criteria Under AASB 137 for Warranty Provisions
A warranty provision qualifies for recognition only when all three tests are met. Miss one, and you are looking at a contingent liability disclosure instead of a balance sheet entry.
- Present obligation from a past event. The sale itself creates the obligation, whether it comes from statute, contract, or your dealership’s own published policy.
- Probable outflow. AASB 137 requires more than a 50% likelihood that resources will be needed to settle the obligation as a class, not as isolated units.
- Reliable estimate. You need enough claims history or industry data to put a number on the exposure. Vague uncertainty is not the same as an unreliable estimate.
The “class of obligations” concept trips up more preparers than the other two criteria combined. You do not assess probability unit by unit. You assess it across the whole population of sales covered by the warranty. Even when the chance that any single machine fails is genuinely small, aggregate probability across the class can still clear the 50% threshold and trigger recognition.
AASB’s illustrative example makes this concrete: a manufacturer sells goods with a warranty covering manufacturing defects. Past experience shows most goods have no defects, but some develop minor faults and a small number develop major faults. Because it is probable that some claims will arise across the population, a provision is recognized for the expected cost of all claims. That holds even though no individual customer is likely to make one.
How Do You Measure a Warranty Provision?
Once recognition is settled, measurement is where the real judgment lives. The “best estimate” concept splits into two distinct approaches depending on what you are measuring.
Use the expected value method when you are dealing with a large population of similar warranty obligations, such as a fleet of machines sold under a standard warranty term. Use the most likely outcome when you are measuring a single, standalone obligation, such as a one-off dispute over a bespoke build. Where other possible outcomes skew materially higher or lower than the most likely figure, the best estimate shifts accordingly rather than just sitting at the mode.
Building the number in practice follows a repeatable sequence:
- Segment warranty claims by product line or equipment class, since failure rates rarely match across categories.
- Pull claim frequency and repair cost data from claims history, ideally covering at least one full warranty cycle.
- Weight each outcome scenario by its probability to produce the expected value.
- Layer in claim lag, since claims reported six months after sale still belong to the period of sale, not the period of the claim.
- Apply a risk adjustment for uncertainty, but do it once. Double-counting prudence by padding both the cost assumption and the probability weighting is a common preparer error.
Discount the provision to present value only when settlement is expected far enough in the future that the time value of money is material, typically multi-year warranty programs rather than twelve-month coverage. And keep the tax effect out of this calculation entirely. The provision is measured before tax, with tax consequences addressed separately under AASB 112.
Assurance Warranties vs. Separately Sold Extended Warranties
Not every warranty belongs on the AASB 137 side of the ledger, and getting this classification wrong is one of the most consequential mistakes a preparer can make. An assurance-type warranty, bundled into the sale price and required by statute or standard trade practice, sits under AASB 137 as a provision. A warranty your dealership sells separately, with its own price tag and its own negotiation, is a distinct performance obligation under AASB 15, which means deferring revenue and recognizing it over the coverage period rather than accruing a cost estimate.
Run this checklist on every warranty program:
- Is the warranty priced or negotiated separately from the underlying sale? If yes, it is AASB 15 territory.
- Is coverage included automatically at the point of sale with no separate transaction? If yes, AASB 137 applies.
- Does the warranty transfer significant insurance-like risk that goes beyond simple product assurance?
That last question opens the door to AASB 17. Product warranties can technically meet the definition of an insurance contract, but a mandatory scope exclusion typically keeps warranties provided at the time of sale out of insurance accounting. The exclusion gets murkier fast when a subsidiary, rather than the selling entity, issues the warranty.
The mandatory scope exclusion for warranties in AASB 17 may not apply in a subsidiary’s individual financial statements when a different group entity stands behind the coverage. Judgment on timing and pricing is unavoidable here, and it belongs in your accounting policy note, not just your working papers.
Worked Example: Calculating the Warranty Provision and Journal Entries
Here is the calculation AASB’s own guidance uses, adapted for a dealership’s mixed equipment sales. Assume you sold a quantity of units under a twelve-month warranty this period, and your claims history splits into three outcome bands.
Add the weighted contributions and the expected value of the provision comes to $400,000. That is your best estimate, not a worst-case reserve and not a best-case guess split down the middle.
Post the initial recognition at period end with a straightforward debit and credit:
- Debit Warranty Expense $400,000
- Credit Provision for Warranty Claims $400,000
When claims come in during the following period and repairs get performed, you draw down the provision rather than hitting the expense line again:
- Debit Provision for Warranty Claims (actual repair cost)
- Credit Cash / Accounts Payable / Inventory (parts consumed)
If your claims experience diverges from the original estimate, adjust the provision balance with a corresponding entry to expense, recognized in the current period. Present the expense within operating costs on the profit and loss statement, and show the provision as its own line item on the balance sheet, separate from trade payables.
Presenting the Provision and What Your Notes Need to Say
Auditors and users of the financial statements expect warranty provisions presented as a distinct line, never folded into trade payables or general accruals. The provision sits on the balance sheet; the corresponding expense sits in the profit and loss statement, typically within cost of sales or operating expenses depending on your chart of accounts structure.
Your notes need to cover four elements at minimum:
- The nature of the obligation, described in plain terms a reader outside the finance team can follow.
- The expected timing of the resulting cash outflows.
- The major assumptions used in the estimate, including failure rates and cost per claim.
- A reconciliation of the provision’s opening balance, additions, amounts used, and closing balance for the period.
A disclosure that simply states “a warranty provision of $X is held” tells an auditor nothing about how you got there. The standard exists precisely so readers can assess the uncertainty behind the number, not just the number itself.
A workable disclosure structure reads something like: “The company provides warranties on [product category] sold during the period. The provision represents the expected value of claims based on [X years] of claims history, adjusted for [specific factor]. Movements in the provision during the period were: opening balance, additions charged to expense, amounts utilized, closing balance.” Adapt the bracketed detail to your own claims data and cross-reference the tax effect to your AASB 112 note.
Handling Changes in Estimate and Contingent Liabilities
Failure rates shift. New defect patterns emerge. When they do, AASB 108 requires a prospective adjustment, not a restatement of prior periods. Update the provision in the current period’s profit and loss statement using the latest reliable claims data you have.
- If a previously disclosed contingent liability becomes probable, move it from the notes into a recognized provision in the period the outflow becomes probable.
- Document the basis for every estimate change, since auditors will ask what triggered the revision.
- Keep tax consequences separate. Measure the provision before tax, then apply AASB 112 to determine the associated deferred tax position.
What Data and Controls Support a Defensible Estimate
A warranty provision is only as reliable as the data behind it. Auditors will test whether your inputs are current, complete, and consistently applied period over period.
- Historical claim rates by product line and model year.
- Average repair or replacement cost per claim, split by parts and labor.
- Supplier or manufacturer reimbursement rates, since these offset your net exposure.
- Claim lag analysis, tracking the gap between sale date and claim notification.
Controls need an owner. Someone in finance should hold responsibility for the assumptions register, review it at least quarterly, and reconcile the recorded provision against actual claims processed through your warranty claim and recovery workflows.
Pro Tip: Run a sensitivity table alongside your point estimate, showing the provision at your base case plus a 10% swing in failure rate either direction. Auditors respond well to evidence that you have already stress tested your own number.

Where the Numbers Actually Come From
Every input in that expected-value table has to originate somewhere, and for most dealerships it comes from disconnected spreadsheets, technician notes, and separate parts systems that do not talk to each other.
- Claim volumes and claim types by product line.
- Parts usage and labor hours logged against warranty work orders.
- Historical repair cost per unit, tracked over multiple warranty cycles.
A system with a proper audit trail turns these into exportable reports rather than a manual reconciliation project every quarter.
Pro Tip: Pull a data snapshot at each reporting date and archive it. When your estimate shifts next quarter, you want to show exactly what the numbers looked like when you made the original call.
What Auditors Actually Flag in Warranty Files
The mistakes we see most often are not exotic. Teams misclassify extended warranties as provisions when they should defer revenue under AASB 15. They roll forward last year’s failure rate without checking whether it still holds. They apply a risk adjustment on top of an already-conservative cost assumption, doubling up on prudence without realizing it.
Auditors focus on consistency of assumptions period over period, reconciliation between the recorded provision and actual claims paid, and whether the discount rate, if used, is justified. The fix is unglamorous: keep a controlled assumptions register, update it on a fixed schedule, and reconcile monthly rather than scrambling at year end.
Making the Data Work for You Instead of Against You
The hardest part of warranty accrual accounting is rarely the accounting rule itself. It is getting reliable claims history, repair costs, and parts data into one place before you can even start the calculation. Dealerships running warranty claims through separate systems from their parts and service records tend to spend days each quarter reconciling numbers that should already agree.

Moderndms brings claims, parts consumption, labor hours, and repair cost history into a single platform built for equipment dealers, so the inputs to your expected-value calculation are already reconciled before you touch a spreadsheet. Every claim carries its own audit trail, which means the assumptions behind your provision are backed by exportable records rather than a memory of what happened last quarter. For dealerships running warranty programs across industrial capital equipment, that data consistency is what turns a stressful quarter-end estimate into a routine reconciliation. If your finance team is still pulling claims data from three different systems to build one number, book a demo and see how the numbers come together instead.
FAQ
How Do You Record a Warranty in Accounting?
You record a warranty by debiting warranty expense and crediting a provision for warranty claims at the amount of your best estimate, typically calculated as expected value for large populations under AASB 137.
Are Warranties Expensed or Capitalized?
Assurance-type warranties are expensed through the provision at the time of sale rather than capitalized, since they represent an obligation tied to goods already sold, not a future asset.
How Do You Account for Warranty Costs When Claims Are Settled?
Settling a claim draws down the existing provision rather than creating a new expense; you debit the provision and credit cash, accounts payable, or inventory for parts consumed in the repair.
Is Warranty Expense Part of Cost of Sales?
Warranty expense typically sits within cost of sales or operating expenses on the profit and loss statement, depending on your dealership’s chart of accounts, while the corresponding provision appears as a separate liability line on the balance sheet.

How Does a Dealer Management System Help With Warranty Accruals?
A platform like Moderndms centralizes claim volumes, parts costs, and labor hours so finance teams can pull consistent, reconciled data for the expected-value calculation instead of rebuilding it from disconnected spreadsheets each quarter.