How to calculate Closing Cost in Arizona

8 min read

Published April 15, 2026 • By DocketMath Team

Quick takeaways

  • “Closing cost” in Arizona (real estate context) usually means the total of fees and charges due at or before closing. Those charges can include settlement/transaction fees, taxes and recording items, and lender-related charges—and there isn’t one single statewide statutory “closing cost formula” you can copy/paste.
  • DocketMath’s closing-cost calculator helps you compute a jurisdiction-aware total by entering line items and using the tool’s calculation structure (for example, totals, category subtotals, and payment-to-party breakdowns if you include allocations).
  • If your workflow also touches legal timelines, be careful not to mix concepts: Arizona’s general statute of limitations (SOL) period is 2 years under A.R.S. § 13-107(A). That rule relates to criminal law timing, not the mechanics of how escrow/lender fees are calculated. This post keeps the fee math separate from SOL considerations.

Note: This guide explains how to calculate closing cost totals using DocketMath. It does not provide legal advice, and it doesn’t replace the closing disclosure, lender estimate, or your transaction’s settlement statement.

Inputs you need

Before you start, collect the items you expect to appear on your settlement statement (purchase) or closing disclosure (loan-related). DocketMath is easiest to use when you break costs into repeatable categories that match what’s on the statement.

Use this intake checklist as your baseline for Closing Cost work in Arizona.

  • jurisdiction selection
  • key dates and triggering events
  • amounts or rates
  • any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

A. Core cost inputs (line items)

Look for the following types of charges (you can enter the ones that apply to your deal):

  • Loan-related fees
    • Example: origination fee, underwriting fee, lender processing/admin fees
  • Third-party services
    • Example: appraisal, credit report, pest inspection (if applicable), survey (if applicable)
  • Title-related charges
    • Title search
    • Title insurance (lender’s and/or owner’s policy, if shown separately)
    • Escrow/closing/settlement service fee
  • Recording fees
    • County/city recording charges (sometimes shown under “Recording fees” or “Government recording”)
  • Transfer taxes (if any apply in your transaction)
  • Prepaids
    • Items collected in advance (often escrowed), such as insurance premium or property tax escrow
  • Interest adjustments
    • Sometimes day-of-close interest or per-diem adjustments appear as separate line items
  • Owner’s charges/credits
    • Credits or offsets that reduce amounts due (for example, seller credits) if your settlement statement breaks these out

B. Calculation inputs (how the tool should total)

To make your results match the settlement statement style, you’ll typically want to set:

  • Who pays which category (borrower, seller credits, lender credits, etc.)
  • Whether fees are fixed-dollar or percentage-based
  • Any optional components that change with elections (for example, a policy choice that changes an amount)
  • Payment timing so prepaids and due-at-closing amounts stay clear in your output

C. Arizona-specific rule you might encounter in mixed use-cases (clarification)

Sometimes people doing “closing” work also review legal timelines. If that’s your situation, note this jurisdiction data:

Your brief also notes that no claim-type-specific sub-rule was found, so 2 years is treated as the general/default period under A.R.S. § 13-107(A).

Important: This SOL rule is about time limits for criminal actions. It does not control how escrow, recording, or lender fees are computed.

How the calculation works

DocketMath’s closing-cost calculator is designed around totaling and allocating closing charges based on the line items you enter. Conceptually, the workflow has three parts: convert inputs to numeric amounts, apply the tool’s structure to compute subtotals and the grand total, and separate outputs into audit-friendly components.

1) Convert your line items into numeric amounts

For each cost category, enter either:

  • Fixed-dollar amounts
    • Example: “Recording fee: $185”
  • Percentage-based amounts, plus the base amount
    • Example: “Origination: 1.00% of loan amount” where the base is the loan amount

If you’re estimating before you have final numbers, use the best available base (such as lender estimate figures). Then update once you get final disclosures.

2) Apply the calculation structure to compute totals

Once categories are entered, DocketMath groups your charges into practical subtotals (the exact labels depend on how you enter categories), commonly including:

  • Settlement/transaction fees subtotal
  • Title & escrow subtotal
  • Recording & government charges subtotal
  • Prepaids subtotal
  • Adjustments & interest subtotal (if you include them)
  • Overall estimated closing cost total

If your workflow includes allocation (who pays what), it can also output a breakdown by party, which helps your computed total line up with what the settlement statement reports.

3) Output both the grand total and the components

A good “closing cost” workflow is more than the final number. Use the output to:

  • Confirm the grand total
  • Review category-level breakdowns so you can spot unusual items
  • Compare scenarios (for example, with vs. without a prepaid choice, or revised loan amount)

To get started, you can use DocketMath here: /tools/closing-cost.

Arizona jurisdiction-aware considerations (what’s different)

In practice, Arizona-specific elements usually show up in which line items apply and what amounts are typical for Arizona transaction documents—not because there’s one statewide statutory formula that forces every closing total to follow the same equation.

So “jurisdiction-aware” in DocketMath generally means:

  • Add any relevant government/recording items your county process would include
  • Use correct base amounts for percentage fees (purchase price vs. loan amount, or policy amounts as applicable)
  • Keep prepaids separated from due-at-closing items so the output matches how disclosures are structured

Warning: Don’t mix “closing cost” totals with a separate “statute of limitations” concept. Arizona’s A.R.S. § 13-107(A) (general 2-year period) is about criminal law timing, not fee calculation for escrow and lenders.

Common pitfalls

Even with a calculator, closing-cost totals often drift because inputs aren’t mapped carefully. Watch for these common issues:

  • missing a required input
  • using a stale rate or rule
  • ignoring calendar or holiday adjustments
  • skipping documentation of assumptions

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

1) Entering percentage fees without the correct base

If a lender fee is 1.00% of loan amount, the base must be the loan amount, not the purchase price. In DocketMath terms, make sure the percentage fee’s base field points to the correct number.

2) Double-counting prepaids

Prepaids can look like “fees,” but they’re often handled separately on disclosures. A common error is:

  • entering a prepaid item in prepaids, and
  • also adding it again under a “fees” category as an estimate of the same cost

Checklist:

  • Prepaids go only under prepaids
  • Don’t add the same insurance/tax estimate twice under different categories

3) Omitting credits or payoff/adjustment offsets

Seller credits or other offsets can reduce the net amount due. If you enter everything as a charge and ignore credits/allocations, the total won’t match the settlement statement.

Use DocketMath’s allocation/breakdown features (when applicable) to mirror the statement’s structure.

4) Assuming a single “Arizona closing-cost statute equation”

Arizona closings generally follow disclosure and settlement statement formatting plus lender/third-party rules. There isn’t typically one universal statutory equation that a calculator can derive from two inputs. Your accuracy depends on:

  • correct line item mapping
  • correct base amounts for percentages
  • careful treatment of prepaids and credits

5) Confusing jurisdiction-aware time rules with fee math

If you’re working in a mixed context (transaction planning plus legal review), remember:

  • A.R.S. § 13-107(A) → general 2-year SOL for criminal matters
  • That does not determine how closing costs are computed

Sources and references

Note: This citation is included because your jurisdiction data specified it. It does not determine closing-cost fee calculations; it is relevant only to the legal-timeline aspect described in the brief.

Next steps

  1. Get your settlement statement (or lender estimate) and list each line item you see.
  2. Map each item into the closest DocketMath category (loan-related, third-party, title/escrow, recording/government, transfer taxes, prepaids, adjustments, and any credits).
  3. For percentage-based items, enter the correct base (commonly loan amount for lender fees; purchase price is not always the base).
  4. Run a first scenario using best-guess amounts, then update when final invoices/disclosures arrive.
  5. If the total changes after updates, compare category subtotals—not only the final number—so you can identify exactly what moved.

If you want to calculate now, use: /tools/closing-cost.

Related reading