Every piece of Indiana property tax software — county CAMA, GIS portals, payment systems, the state's databases, our own — agrees on exactly one identifier: the 18-digit state parcel number. It's the join key of the entire system. It's also a small data-standard marvel that encodes real information about your property, and the single most common reason a parcel search "fails" is not knowing how it's structured.
Two minutes to learn it, and every portal in the state gets easier to use.
The Anatomy
The format is defined by Indiana's data standards rule, 50 IAC 26-8-1. Formatted, a parcel number looks like:
49-06-15-104-002.000-601
Reading left to right:
| Segment | Digits | Meaning |
|---|---|---|
49 | 2 | County code — DLGF's numbering (this one is Marion) |
06 | 2 | Congressional township/range reference |
15 | 2 | Section under the U.S. Public Land Survey |
104 | 3 | Block/area designation (zeros where unused) |
002.000 | 6 | Permanent parcel number — the decimal lets splits keep lineage (a parcel split from 002.000 might become 002.001) |
601 | 3 | Taxing district — the code that determines your tax rate |
Two segments repay attention. The parcel segment's decimal suffix records history: splits and subdivisions mint children that trace back to the parent. And the final three digits are your taxing district — meaning your rate assignment is baked into your parcel number, and the district-level rate differences worth real money are visible right there. (The two-digit county code uses Indiana's standard alphabetical 1–92 county numbering — Adams is 01, Marion is 49, Whitley is 92.)
Why Your Search Keeps Failing
Different systems render the same number differently, and most search boxes are strict about their own format:
| Format | Example | Where you'll see it |
|---|---|---|
| Fully formatted | 49-06-15-104-002.000-601 | Record cards, TS-1 statements |
| Unformatted 18-digit | 490615104002000601 | State datasets, GIS exports, APIs |
| Partial / local | 104-002 or a legacy local ID | Older county systems, plat references |
If a portal rejects your number: strip (or add) the dashes and dot, confirm you're not pasting a duplicate number (the treasurer's billing ID, a different identifier that also appears on your statement), and make sure the leading county digits match the county whose portal you're on. Our county software guide notes each portal family's quirks; our property lookup accepts the common formats and normalizes them for you.
Where You'll Need It
The parcel number is the passport for every task in the stack: paying online, pulling the record card, filing a Form 130, tracking a portfolio, locating drainage assessments, even registering business locations in PPOP-IN. Keep the full 18 digits for every parcel you own somewhere you can paste from — your closing documents and TS-1 both show it.
Note
For data work, always store the unformatted 18-digit string and format for display only. We learned this building our statewide pipeline: joining county CAMA extracts, state geometry data, and assessment rolls means reconciling every format variant above — and parcels that "don't match" between systems almost always match once normalized. The same lesson applies to a landlord's spreadsheet.
For Developers and Analysts
The parcel number's structure makes it a natural composite key: county rollups from the first two digits, district-level rate joins from the last three, split lineage from the decimal. Indiana's statewide parcel geometry (via the IGIO parcel layers) and assessment datasets key on it — one warning: some state feeds store county identifiers as strings, so '58' and 58 are different lookups; type coercion bugs around parcel keys are a rite of passage. If you'd rather consume normalized data than build the reconciliation yourself, that's our data API, and the API-vs-scraping tradeoffs post covers the build decision honestly.
The parcel number is the thread that ties together all four layers of Indiana's property tax systems — see the complete software guide for the map.