Building Lists

County Tax Balances vs. Provider Flags: Our Arizona Check

Our dated 177-parcel Arizona investigation shows why tax flags, historical delinquency and current county balances need separate interpretation.

A property-data tax flag is a reason to check a tax account, not proof of the amount still unpaid today. To evaluate it, identify the parcel, bill year, amount remaining and date checked. A historical delinquency can be accurately recorded even after the owner has paid.

Our October 8–9, 2026 Arizona investigation found materially different results when provider flags were checked against dated county balances. PropertyRadar identified more qualifying cases inside this selected cohort, but no provider flag served as a current-debt certificate. The screen and the cohort are essential to understanding the numbers.

TL;DR

The screen we applied, and why it matters

The historical investigation used a broad screen: at least $500 still due on past-due bills for 2025 or earlier at the October 2026 check. This is the definition used to interpret the table, not a universal definition of delinquency or a statement of Homebase's current selection rules.

Within the 177 investigated parcels, 45 met that screen. The table shows how many flagged properties met it, not whether every flagged record was wrong or right under its own product definition.

Provider Flagged parcels in this cohort Flagged parcels meeting the dated screen Flagged parcels not meeting that screen
DataTree 54 23 31
BatchData 39 17 22
PropertyRadar 130 44 86

A parcel could be flagged by more than one provider. Do not add these rows to calculate unique properties, and do not interpret a larger flagged list as a cleaner list. PropertyRadar surfaced more of the 45 qualifying cases in this cohort while also flagging many properties that did not meet this particular screen.

Method and limits: The October 8–9 check investigated selected Arizona parcels, including controls, with selection enriched for potential issues. It was not a nationwide random sample. County evidence was dated, provider flags overlapped, and changing the amount or bill-year definition changed relative results in later screening. We have not rerun those county accounts for this article. Counts do not measure current nationwide precision, recall or seller response.

Why our initial tax-label check was insufficient

An earlier DataTree comparison appeared to confirm 36 of 36 historical tax labels. Checking county balances later showed why that agreement could not establish current debt. Two products can agree that an account had a delinquency without answering whether a qualifying balance remains.

Likewise, failing our historical screen did not mean a property was debt-free. Smaller balances, bill dates, later payments and payment contracts could matter. A flag may also use a different year or definition. The right finding is “does not meet this dated screen,” followed by the reason, rather than an unsupported accusation that the record is false.

Product scope still matters. PropertyRadar's coverage guide separates county availability for different record categories. A nationwide footprint does not make every local field equally complete. PropertyRadar coverage guide

Use a ladder of evidence for tax status

Evidence Appropriate use Question still open
Provider flag Identify accounts worth investigating Which bill, year, definition and source date?
Historical delinquency year Establish a reported past event Was it paid or otherwise changed?
County bill and dated account detail Check the relevant remaining balance and status Have payments or adjustments posted since the check?
Current confirmation for a transaction Resolve the amount and process needed for that transaction Other obligations and title questions still require their own work

Start by confirming the parcel. Open the relevant bills, distinguish the current tax year from past-due years, and record the amount still due rather than copying the original bill amount. Note payment or contract information when the account shows it. If the account is ambiguous, record that uncertainty and ask the responsible county office what the displayed status means.

For a mailing list, retain the check date and refresh before the next send. For a purchase, have the appropriate closing professionals obtain the current tax information needed for settlement. A dated research screenshot cannot settle a later transaction.

Put tax evidence inside the local strategy

Homebase concluded that the evaluated vendors were equivalent at the source-data layer for our local buying purposes. We therefore handle sifting, derived signals and stacking in-house. That conclusion does not make tax flags, coverage or update dates interchangeable; this investigation shows why their interpretation needs its own work.

Our Source, Sift, Stack, Skip framework begins with the neighborhood and buyer's houses, then audience, then one motivation per list. A tax list can stand alongside a probate or code-case list without demanding that the same owner appear in all three. Combine, deduplicate, remove do-not-mail entries and refresh before consistent sends.

For the broader process of finding and approaching these owners, see our tax-delinquent property guide. The lesson from this investigation is narrower: decide what tax condition you mean, then verify that condition against dated account evidence.

Direct mail to the neighborhoods where you want to buy

Homebase handles direct mail to property owners in the neighborhoods where you want to buy. Enter one address to find your neighborhood and get your first neighborhood analysis free. No card required.

Analyze a neighborhood free