A property name feels unique until a street name changes, a unit is added, or two properties share a nickname. A short property ID gives every row a stable anchor even when the display name changes. Using property IDs in rental spreadsheets keeps the history stable when a property name changes.
Choose an ID that will not move
Use a simple code such as P-01, P-02 or a short internal reference. Avoid embedding a tenant name, a rent amount or a year in the ID. The ID should still make sense after a sale, a renumbering or a new manager.
Keep a mapping table
| Property ID | Display name | Address label | Status |
|---|---|---|---|
| P-01 | Harbor House | 12 Harbor Lane | Active |
| P-02 | Maple Unit | 8 Maple Street, Unit 2 | Active |
| P-03 | Old Mill | 44 Mill Road | Sold 2025 |
The names and addresses above are fictional. The mapping table is the only place where a display name is allowed to change; transaction rows keep the ID.
Use the ID in every transaction field
Enter the ID in income, expense, receipt and summary rows. If your spreadsheet has a property dropdown, make the ID the stored value and the display name the label. Avoid merged cells and free-text property columns, which are common sources of near-duplicate entries.
Do not recycle an ID
When a property is sold, mark it inactive rather than assigning its ID to a new property. Reuse creates a history that looks continuous when it is not. If you must archive, keep the old mapping and start the new property with the next unused number.
Check the ID before the total
A correct total under the wrong ID is still a reporting error. Filter the month by property and compare the row count with the receipts. A quick visual check of the ID column often catches a copy-down mistake before it reaches the summary.
For category consistency, read the rental expense categories guide. For the monthly check, use the reconciliation checklist.
Related: common spreadsheet entry errors includes more ID and date checks.
When you export or share the file
Keep the ID column visible in exports and summaries. If you share a filtered view, include the mapping table so a reader can resolve P-01 without guessing. A stable ID is useful only when the people receiving the record can interpret it.