Leases

Context and Why This Exists

Ownership tells you who owns an asset. A lease tells you who is using that asset under a formal arrangement.

StructureGram records leases as a dedicated relationship type between:

• a lessee as the source entity,
• and an asset as the target.

This lets you separate legal ownership from use rights, payment terms, review clauses, options, and other lease details.

What the Feature Does

Lease relationships are supported across the main asset and relationship surfaces that already exist in the app.

You can currently:

• create and edit leases from entity detail pages,
• create leases from the asset-side Leased By panel in the diagram inspector,
• create lease links directly on ownership diagrams,
• review leases in the Leases section on entity detail pages,
• and see lease indicators on asset rows where the asset is leased.

Important behavior:

• There is no standalone leases register like the loans page.
• Leases are still first-class relationships, but they use dedicated forms because the metadata is more structured than a simple relationship row.

Relationship Rules

Direction

Lease direction is:

• source = lessee,
• target = asset.

The relationship means the source entity leases the target asset.

Who can be the lessee

Current lease flows allow these lessee entity types:

• individuals,
• companies,
• trusts,
• SMSFs,
• partnerships.

What can be the target

• The target must be an asset.
• Assets cannot be the lessee.

Duplicate behavior

The app blocks a duplicate lease for the same lessee and asset pair. If a lease already exists, you need to edit the existing one instead of creating a second copy of the same pairing.

Lease Metadata Options

Current metadata fields

Current lease create and edit flows support these metadata options.

Legacy metadata you may still see

Older lease records may still contain legacy compatibility fields:

• annualCost
• leaseType

These are still read and preserved for backward compatibility. For example, older rows may display an annual cost on cards even if they do not use the newer payment amount and frequency fields.

How to Use It

Create a lease from an entity detail page

1. Open an individual, company, trust, partnership, or SMSF.
2. Go to the Leases section.
3. Click Add Lease.
4. Select the asset.
5. Enter any lease dates and metadata you want to track.
6. Save.

Expected result:

• The lease appears in that entity's Leases Held list.
• The asset-side displays can then show that it is leased to that entity.

Create a lease from the asset-side diagram inspector

1. Open an ownership diagram.
2. Select an asset node.
3. In the asset inspector, find Leased By.
4. Click Add Lease.
5. Select the lessee.
6. Enter the lease details.
7. Save.

Expected result:

• The new lease appears under Leased By for that asset.
• The diagram can show the lease link if the lease toggle is on.

Create a lease directly on the ownership diagram

1. Open an ownership diagram.
2. Drag from an eligible entity to an asset.
3. In the relationship inspector, choose Lease.
4. Enter the lease details.
5. Save.

Expected result:

• The lease link is created directly on the diagram.
• Lease metadata can be entered in the inspector during creation.

This is similar to loans in one respect: both can be created directly on the diagram by dragging a relationship and selecting the type in the inspector.

The difference is what happens next:

• loans can then add security and guarantor child links inside the loan inspector,
• leases are a flat entity-to-asset relationship with no child-link workflow.

Edit or delete a lease

You can edit or delete leases from the entity-side lease cards.

1. Open the relevant Leases section.
2. Use the edit action on the lease card to update dates or metadata.
3. Use the delete action if the lease should be removed.

Expected result:

• edits update the same relationship,
• deletion removes the lease only.

Where You Can Review Leases

Entity detail pages

Entity detail pages expose a dedicated Leases section for:

• individuals,
• companies,
• trusts,
• partnerships,
• SMSFs.

That section can show:

• Leases Held when the entity is the lessee,
• Leased To when the current context represents the asset side of the relationship surface.

Asset-side inspector

Assets do not have a standalone lease page. Instead, the asset-side inspector shows a Leased By panel listing current lessees and allowing new lease creation.

Asset rows and allocation views

Where asset rows show lease indicators, you can see summaries such as:

• who the asset is leased to,
• and the payment summary when payment metadata exists.

Diagram Display and Settings

Ownership diagrams include a dedicated Lease visibility toggle in Settings.

To show lease links:

1. Open the ownership diagram.
2. Open Settings.
3. Go to the Relationships tab.
4. Turn on Lease.

Expected result:

• lease links appear between the lessee and the asset,
• and leased assets can show the lease-related visual indicators used by the diagram.

Validation and Data Rules

Date rules

• Expiry must be after commencement.
• Commencement and expiry are optional, but if both are provided they must be in a valid order.

Numeric rules

• Term (months) must be a whole number of at least 1.
• Payments ($) must be a non-negative whole-dollar amount.
• Bond / Bank Guarantee ($) must be a non-negative whole-dollar amount.

PPSR-SIN handling

• PPSR-SIN is stored as digits only.
• UI entry is formatted for readability, but the saved value is normalized.

Edge Cases and Expected Behavior

Older lease records may show annual cost instead of payment amount

That is expected for legacy data.

Current forms prefer:

• payment amount,
• payment frequency,
• review settings,
• option terms,
• bond,
• PPSR-SIN,
• notes.

Older records can still surface annualCost where it exists.

Lease category labels may come from the asset type

Current cards can derive a lease-style label such as commercial or residential from the asset type, even when you are not actively editing a legacy leaseType field.

There is no separate leases register

That is current behavior.

Use the entity detail sections, asset-side inspector, diagram creation flow, and asset indicators instead.

Troubleshooting (Q&A)

I cannot create a lease for this target

Most likely cause:

• the target is not an asset.

Fix:

1. Confirm the relationship is being created against an asset.
2. If you are on a diagram, drag from the entity to the asset.

The app says the lease already exists

Most likely cause:

• a lease already exists for that same lessee and asset pair.

Fix:

1. Find the existing lease card.
2. Edit the existing lease instead of creating a duplicate.

My payment information is not showing as expected

Most likely cause:

• the record uses older annualCost data,
• or the newer payment amount and frequency fields were left empty.

Fix:

1. Edit the lease.
2. Populate Payments ($) and Frequency if you want the newer payment display.

Best Practice

• Record lease dates even when the financial fields are still being worked out.
• Use the newer payment amount and frequency fields for consistent display across the app.
• Use Review Date, Review Type, and Option Terms when the lease has ongoing review or renewal mechanics worth preserving.
• Use the asset-side Leased By workflow when you are auditing one asset at a time.
• Use direct diagram creation when you want to model a simple lease quickly between an entity and an asset.

Related Topics

• Diagrams
• Relationship Types Reference
• Company Entities
• Trust Entities
• Partnership Entities
• SMSF Entities
• Individual Entities
• Asset Entities