Properties
Properties are your managed inventory. Each one stores a durable address-to-jurisdiction mapping and a reusable tax-driver profile, so bookings can reference a property instead of repeating its location and tax details every time.
Why register a property
A property captures, once, everything about a unit that bookings would otherwise carry inline: its address, the TaxLens jurisdiction it maps to, its property type and star rating, and — optionally — the legal entities that should appear on its invoices. A booking can then pass a property_id and let TaxLens fill the rest. Remaps and default changes affect future bookings only; the snapshots on existing bookings and issued invoices stay immutable.
Create a property
Click Add property and fill the form. Only the name, address line 1, and country are strictly required; everything else refines the mapping and the tax result.
- 1IdentityGive the property a name and, optionally, an external reference — your PMS, OTA, or listing ID — so you can reconcile it against your own systems.
- 2AddressEnter the street address, city, region, postal code, and country. TaxLens geocodes it and maps it to a jurisdiction. You can also pin a Tax jurisdiction directly when you already know the exact code.
- 3Tax driversSet the property type, star rating, an optional classification, and a tax ZIP/zone (for when the tax zone differs from the mailing ZIP). These become the defaults bookings inherit.
- 4Invoice defaults (optional)Optionally set the invoice seller and self-billing supplier issuers — see below.
On save, TaxLens geocodes and maps the property immediately. The result appears in the list with its mapping status.
Geocoding, mapping status, and confidence
Every property carries the state of its address-to-jurisdiction resolution. The list and the detail panel show three signals:
| Field | Type | Description |
|---|---|---|
| mapping_status | mapped | unresolved | stale | Whether the address resolved cleanly to a jurisdiction, failed to resolve, or needs a refresh. |
| jurisdiction_confidence | high | medium | low | How confident the geocoder is in the resolved jurisdiction. |
| tax_driver_status | status | Whether the tax-driver profile (type, stars, classification) is complete. |
Use the status filter above the list (all, mapped, unresolved, stale) to find properties that need attention. When a mapping fails, the row and the detail panel surface the error so you can correct the address.
Remap and edit
Each row offers three actions: Details (the read-only panel), Edit (change any field), and Remap.
- Remap re-runs geocoding against the current address — use it after an address correction, or when a mapping has gone stale.
- Edit updates the stored fields, including the tax drivers and issuer defaults. Changing the address and saving re-maps automatically.
Invoice and supplier issuer defaults
A property can carry two optional legal-issuer defaults that flow into bookings made against it when the booking doesn't name its own:
- Invoice seller default — the legal entity that appears as the seller on the invoice.
- Self-billing supplier default — the host/owner entity used for self-billed (389) invoices.
From the API
Properties are fully available over the API — create, list, fetch, update, and remap. The list call backs this screen:
List your organization's properties with their mapping status and tax drivers.
Sign in to run this against the live API. Read-only — nothing is saved.
For the create/update payload and the booking-time prefill behaviour, see Properties (API) and Register your first property.