Create your first property
Register a property once and TaxLens geocodes its address, maps it to the right jurisdiction, and remembers its tax-driver defaults so every booking is pre-filled and correct.
Why register a property
A property is a reusable record of a place you operate — its address, the jurisdiction it sits in, and the tax-relevant attributes of the unit. Once it exists, a booking can simply reference property_id and TaxLens fills in the location and tax drivers for you, instead of you re-specifying them every time. Properties are org-scoped, so they belong to your active organization.
Create a property
- 1Open Properties and add one
Go to Properties in the dashboard and start a new property.
- 2Enter the name and address
Give the property a name and its address (at minimum address line 1 and a country). The more complete the address, the better the geocoding result.
- 3Save and let TaxLens map it
On save, TaxLens geocodes the address and resolves it to a jurisdiction. You'll see the matched jurisdiction, a confidence level, and a mapping status.
Geocoding & jurisdiction mapping
TaxLens geocodes the address and walks the result down to the most specific jurisdiction it can confirm — district, city, county, region, and finally country — so a property lands on the correct city-level node rather than just its country. Three fields tell you how the mapping went:
| Field | Type | Description |
|---|---|---|
| jurisdiction_code | string | null | The matched jurisdiction, e.g. ES-CT-BCN. This is what the calculator uses. Null if mapping couldn't resolve one. |
| jurisdiction_confidence | "high" | "medium" | "low" | How sure TaxLens is about the match. Review medium/low matches before relying on them. |
| mapping_status | "mapped" | "unresolved" | "stale" | mapped = resolved cleanly; unresolved = needs your attention; stale = the address changed and a remap is due. |
unresolved or with low confidence, refine the address (add the city, region, or postal code) and remap — or set the jurisdiction_code explicitly. Learn how the hierarchy works in Jurisdictions.Tax-driver defaults
Beyond location, a property stores the attributes that change which taxes apply. These are the tax drivers, and a booking that references the property inherits any it doesn't specify itself:
| Field | Type | Description |
|---|---|---|
| property_type | string | e.g. hotel, apartment, vacation_rental — drives type-specific rules. |
| property_classification | string | null | An optional finer classification used by some classification-tiered rates. |
| star_rating | number | null | Star rating, where a jurisdiction taxes by hotel class. |
| property_postal_code | string | null | A tax postal code used by geofenced rules (e.g. a downtown improvement-district ZIP). Distinct from the mailing postal code. |
A property also carries its issuer defaults — default_legal_issuer_id and default_supplier_legal_issuer_id — covered in Legal issuers.
Remapping & immutability
If you edit a property's address or change its defaults, TaxLens can re-run the mapping. A changed address marks the property stale until you remap. Two things to keep in mind:
- Remaps and default changes affect future bookings only. They never rewrite history.
- Persisted booking and issued-invoice snapshots are immutable. Each booking froze the location and drivers it used at the time, so re-mapping the property won't alter an already-calculated booking or an issued document.
property_id and an explicit jurisdiction_code that conflict with the property's mapping, TaxLens rejects the request rather than silently guessing.With a property in place, run a calculation against it in Run your first calculation.