STATE LAW – ARIZONA LIBRARY – GUIDE 06
Stacking & Multiple Insurance Policies
When more than one Arizona UM/UIM policy or coverage may apply, whether the benefits can be combined, how an insurer may validly limit stacking, and how Franklin and the 2026 Arizona Supreme Court decision in Balzan work together.
Arizona permits UM/UIM stacking unless the insurer validly limits it under A.R.S. § 20-259.01(H).
One policy · multiple vehicles
Franklin holds that a single multi-vehicle policy provides separate UIM coverages for each
covered vehicle. Those coverages can be stacked unless the insurer satisfies subsection (H)’s requirements.
Multiple policies · same insurer
Subsection (H) allows an insurer to limit applicable UM/UIM coverage to one policy or coverage, selected
by the insured, when the statutory conditions and effective anti-stacking language are satisfied.
Who purchased the coverage?
Balzan holds that purchaser status turns on the named insured who exercised the legal authority
to procure UM/UIM coverage—not merely on who contributed money toward the premium. Joint named insureds
who jointly procure coverage function as one purchasing unit for subsection (H).
Current rule:
Read Franklin and Balzan together. Franklin identifies the coverages available to
stack; Balzan clarifies who counts as the statutory purchaser when the insurer invokes subsection (H).
01 · What Stacking Means
Stacking combines more than one applicable UM/UIM coverage for the same accident or claim.
Arizona stacking questions usually arise in two configurations. The distinction matters because
Franklin directly addresses multiple coverages within one policy, while Balzan addresses
multiple policies and the identity of the statutory purchaser.
Intra-policy stacking
One policy insures several vehicles. The question is whether each insured vehicle carries a separate
UM/UIM coverage that can be combined with the others.
Primary authority: Franklin v. CSAA General Insurance Co.
Inter-policy stacking
Two or more separate policies or coverages apply to the same accident. The analysis includes who procured
the policies and whether a valid subsection (H) limitation permits the insurer to require selection of one.
Current purchaser authority: State Farm v. Balzan
Do not start with the policy’s label.
First identify every potentially applicable policy and coverage. Then determine whether Arizona law permits
the insurer to limit those otherwise applicable coverages.
02 · Statutory Test
A.R.S. § 20-259.01(H) is the controlling anti-stacking provision.
Subsection (H) allows an insurer to limit multiple policies or coverages purchased by one insured on
different vehicles so that only one policy or coverage, selected by the insured, applies to one accident.
1
Are there multiple applicable policies or coverages?
Identify every UM/UIM policy or coverage that would otherwise apply to the accident or claim.
2
Are they on different vehicles?
Subsection (H) speaks specifically to multiple policies or coverages purchased on different vehicles.
3
Were they purchased by “one insured”?
Under Balzan, look to the named insured purchaser who exercised the statutory authority to
obtain the UM/UIM coverage. Joint named insureds who jointly procure the coverage function collectively
as a single statutory purchaser.
4
Does the policy validly limit stacking?
The statute is permissive, not self-executing. Effective policy language must clearly implement the
permitted limitation and preserve the insured’s statutory right to select the applicable policy or coverage.
5
Was the selection right properly communicated?
If the policy does not contain a statement informing the insured of the selection right, subsection (H)
requires written notice within 30 days after the insurer receives notice of the accident.
03 · Franklin
A multi-vehicle policy carries separate UIM coverages for stacking purposes.
The holding
In Franklin v. CSAA General Insurance Co., the Arizona Supreme Court held that A.R.S.
§ 20-259.01 requires a single policy insuring multiple vehicles to provide separate UIM coverages for
each vehicle.
The consequence
An insurer cannot avoid subsection (H) merely by drafting the policy to characterize the multi-vehicle
contract as supplying only one UIM coverage. If the insurer wants to prevent intra-policy stacking,
it must satisfy Arizona’s statutory anti-stacking requirements.
Franklin remains controlling after Balzan.
Balzan relies on Franklin; it does not eliminate Franklin‘s separate-coverage rule.
04 · 2026 Current-Law Update
State Farm v. Balzan clarifies “purchased by one insured.”
The July 6, 2026 Arizona Supreme Court opinion resolves a recurring household-policy question under
§ 20-259.01(H): who is the relevant purchaser when several people are insured or contribute to premiums?
Named insured is the statutory purchaser
Purchaser status follows the named insured who exercises the statutory authority to accept the insurer’s
UM/UIM offer and procure the coverage.
Joint procurement can equal “one insured”
When multiple named insureds jointly procure the policies, they function as one purchasing unit and
constitute “one insured” for subsection (H).
Premium contribution is not the test
The source of the premium money does not itself create purchaser status. The Court focused on who had
and exercised the legal authority to obtain the coverage.
Important limit on the holding:
Balzan does not create a blanket prohibition on household stacking. It determines who counts as the
purchaser for subsection (H). The insurer still needs an effective anti-stacking provision and must satisfy
the statute’s selection requirements.
Lindsey cleanup:
Use the Arizona Supreme Court’s Lindsey decision for the proposition that subsection (H)’s predecessor
is not self-executing and that anti-stacking language must effectively implement the statute. Do not rely on
the vacated Court of Appeals opinion’s community-property reasoning to identify the purchaser; Balzan
expressly treats that reasoning as inapposite to the current purchaser inquiry.
05 · Selection & Policy Language
An anti-stacking limitation must preserve the insured’s statutory choice.
Policy language
- Locate the UM/UIM anti-stacking provision.
- Determine whether it clearly applies to multiple policies, multiple coverages, or both.
- Compare its wording with § 20-259.01(H).
- Confirm that it recognizes the insured’s right to select the applicable policy or coverage.
30-day notice rule
- Check whether the policy itself states the selection right.
- If not, identify when the insurer received notice of the accident.
- Look for written notice of the selection right within 30 days.
- Preserve the notice and proof of delivery in the claim file.
Same insurer includes the group context.
For subsection (H), Arizona’s statute defines “insurer” to include every insurer within a group of insurers
under common management.
06 · Coverage Workflow
Audit stacking in a fixed order.
Step
Question
Record
1
How many vehicles, policies, and UM/UIM coverages exist?
Declarations, policy numbers, vehicles, limits, endorsements.
2
Which coverages apply to the accident before any anti-stacking limitation?
Insured status, occupancy, household status, applicable exclusions.
3
Who procured each policy or coverage?
Named insureds, applications, declarations, acceptance of UM/UIM coverage.
4
Is the situation intra-policy, inter-policy, or both?
Apply Franklin to multi-vehicle coverage and Balzan to purchaser identity.
5
Does the anti-stacking clause satisfy subsection (H)?
Exact policy wording and right-to-select language.
6
Was any required 30-day selection notice sent?
Date of accident notice, insurer letter, proof of delivery.
7
Which policy or coverage did the insured select?
Written selection, limits selected, payment, reservation, or denial.
07 · Authorities
Authorities for this Guide
A.R.S. § 20-259.01(H)
Arizona Anti-Stacking Provision
Permits an insurer, under the stated conditions, to limit multiple policies or coverages purchased by
one insured on different vehicles to one policy or coverage selected by the insured. It also supplies the
30-day written-notice rule when the policy does not itself state the insured’s selection right.
Official source · Arizona Legislature
Franklin v. CSAA General Insurance Co., 255 Ariz. 409, 532 P.3d 1145 (2023)
Multi-Vehicle Policy Creates Separate UIM Coverages
Holds that a single policy insuring multiple vehicles necessarily provides separate UIM coverages for
each vehicle for subsection (H) purposes. An insurer seeking to prevent intra-policy stacking must comply
with Arizona’s statutory requirements.
Official opinion · Arizona Supreme Court
State Farm Mutual Automobile Insurance Co. v. Balzan, No. CV-24-0140-PR (Ariz. July 6, 2026)
Named-Insured Purchaser & Joint Purchasing Unit
Holds that “purchased by one insured” refers to the named insured purchaser who exercised legal authority
to obtain UM/UIM coverage. Multiple named insureds who jointly procure coverage function as a single
purchasing unit and constitute “one insured” for subsection (H).
Official opinion · Arizona Supreme Court
American Family Mutual Insurance Co. v. Sharp, 229 Ariz. 487, 277 P.3d 192 (2012)
Subsection (H) Governs UM/UIM Stacking Limitations
Arizona Supreme Court authority explaining that subsection (H) is the UM/UIM Act provision authorizing
stacking limitations. Read with Franklin and Balzan.
Verify case · Arizona Judicial Branch opinion resources
State Farm Mutual Automobile Insurance Co. v. Lindsey, 182 Ariz. 329, 897 P.2d 631 (1995)
Anti-Stacking Statute Is Not Self-Executing
Holds that the statutory permission to limit stacking requires effective policy language. The policy
limitation must implement the statute and preserve the insured’s selection right. The Supreme Court did
not adopt the vacated Court of Appeals opinion’s community-property purchaser analysis.
Verify case · Arizona Judicial Branch opinion resources
Taylor v. Travelers Indemnity Co. of America, 198 Ariz. 310, 9 P.3d 1049 (2000)
UM/UIM Act Is Remedial
Frequently cited for the principle that Arizona’s UM/UIM statute is remedial and generally favors
coverage, while subsection (H) supplies a specific statutory mechanism allowing insurers to limit stacking.
Verify case · Arizona Judicial Branch opinion resources
08 · Verification
Formal QC for an Arizona stacking conclusion.
Statute QC
- Open the current A.R.S. § 20-259.01 text.
- Read subsection (H) together with subsections (A), (B), and (G) as relevant.
- Confirm that the policy and accident dates do not implicate a prior statutory version.
- Do not paraphrase the 30-day notice requirement without checking the policy first.
Case QC
- Use Franklin for separate coverages under a multi-vehicle policy.
- Use Balzan for the current purchaser analysis under “one insured.”
- Use the Supreme Court Lindsey opinion—not the vacated Court of Appeals opinion—for its surviving holding.
- Check later Arizona appellate decisions before publishing a new proposition.
Policy QC
- Collect every policy and declarations page.
- Identify every named insured and each policy’s procurement history.
- Read the exact anti-stacking and selection provisions.
- Preserve post-accident selection notices and correspondence.
Registry QC
- Tag Balzan to canonical topic UM-030.
- Keep Franklin paired with Balzan in the authority set.
- Mark prior community-property purchaser summaries for correction.
- Clear the page-update flag only after the published page reflects the current rule.
QC status:
A.R.S. § 20-259.01(H), Franklin, and Balzan were checked against current Arizona Legislature
and official Arizona Supreme Court sources on Sept. 26, 2026. The page was revised specifically in response
to the July 6, 2026 Balzan decision.
09 · Questions
Questions that usually determine whether stacking is available.
Does Arizona generally permit UM/UIM stacking?
Yes, subject to A.R.S. § 20-259.01(H). The statute permits insurers to limit stacking under specified
conditions, but the limitation is not automatic.
If one policy covers several vehicles, is there only one UIM coverage?
No. Franklin holds that a multi-vehicle policy provides separate UIM coverages for each vehicle
for purposes of Arizona’s stacking statute.
Does Balzan prohibit stacking whenever a married couple pays premiums with community funds?
No. The source of premium funds is not the controlling test. Balzan focuses on who exercised the
legal authority to procure the UM/UIM coverage. Joint named insureds who jointly procure coverage function
as one statutory purchasing unit under subsection (H).
Can every household member who contributes money toward insurance be treated as a separate purchaser?
No. Balzan rejects purchaser status based merely on financial contribution. Purchaser status
follows the named insured who exercised the statutory authority to obtain the coverage.
Can an insurer prohibit stacking just because subsection (H) allows it?
No. Lindsey explains that the statutory permission is not self-executing. The insurer must use
effective policy language that implements the statutory limitation.
Who chooses which policy or coverage applies when stacking is validly limited?
Subsection (H) gives the insured the right to select the one applicable policy or coverage.
What if the policy does not tell the insured about the right to select?
A.R.S. § 20-259.01(H) requires the insurer to notify the insured in writing of the selection right within
30 days after receiving notice of the accident.
Did Balzan overrule Franklin?
No. Balzan cites and applies Franklin. The two decisions address related but distinct
parts of the stacking analysis.
10 · Related Topics
Continue the Arizona coverage research path.
UM-020
Uninsured & Underinsured Motorist Coverage
Use this for the underlying scope, trigger, offer, and claim requirements for Arizona UM/UIM benefits.
Coverage Interpretation
Policy Interpretation, Exclusions & Coverage Disputes
Use this when the dispute turns on policy wording apart from the specific statutory stacking rules.
AUTH-010
Arizona Case Authority Library
Verify Franklin, Balzan, Sharp, Lindsey, and later Arizona decisions affecting this topic.
Research Maintenance
Current-law update completed · Balzan integrated
Canonical topic
UM-030
Change trigger
Balzan · July 6, 2026
Last formal source check
Sept. 26, 2026
Routine review cycle
15 days
Registry action
Page-update flag may be cleared after publication
Architecture test passed:
The new authority changed UM-030, so this page was revised without requiring changes to unrelated Arizona
claims, damages, lien, or settlement pages. The page keeps its semantic URL even if the public guide sequence expands.
Research guide, not legal advice.
UM/UIM stacking depends on the policies, named insureds, procurement history, covered vehicles, accident facts,
selection notices, and current Arizona law. Confirm the complete policies and controlling authority before
deciding what coverages may be combined.
Official Sources
Verify current Arizona law at the source
The detailed authority links above are preserved from the reviewed Arizona guide. Use current official sources and the operative policy before legal reliance.