Linking an Expense to a Property, Unit, or Maintenance Request

Every expense in Landager can be optionally linked to three levels of your data hierarchy: Property, Unit, and Maintenance Request. These links turn a flat list of dollar amounts into a structured financial map of your portfolio.

Level 1: Linking to a Property

Why: Assigns the cost to a specific building for per-property profitability analysis. Example: Your annual landscaping contract costs $2,400. Link it to "Sunset Towers" so the expense appears when you review the financial health of that building.

Level 2: Linking to a Unit

Why: Narrows the cost to a specific rentable space within the building. Example: Replacing the dishwasher in Unit 3A costs $450. By linking to both the Property and the Unit, you can track exactly how much money that specific unit has cost you over its lifetime.

Level 3: Linking to a Maintenance Request

Why: Connects the financial cost directly to the operational ticket that initiated the work. Example: Tenant reported a leaking pipe (Maintenance Request #MR-0047). Plumber fixed it for $175. By linking the $175 expense to the specific maintenance ticket, you can view the full story: who reported the issue, what was done, who fixed it, and exactly how much it cost.

How the Links Appear

Once linked:

• The Property Detail View will display the expense under its financial tab.
• The Maintenance Request Detail View will reference the associated expense cost.
• The Exported Reports will include the property and unit columns for grouping and pivot table analysis.

Best Practice

Always link expenses to at least the Property level. An expense floating in your database with no property assignment is essentially invisible to your per-property profitability calculations—it exists in the global total but doesn't tell you which building ate the cost.