VERMIETER

What is this for?

With VERMIETER you manage the people / companies that act as landlords in contracts.

Typically, there are only a few landlords (often only one per tenant — yourself), but in multi-operator or association structures, multiple landlords can also make sense.

For each landlord you can record, among other things:

• Name
• Address
• Contact details
• Bank details / tax info (if available in the schema)
• Logo / data relevant to letterheads

This data appears in contracts and is also used in PDF documents.

---

Common tasks (day-to-day)

• Create / maintain a landlord
• Update address or bank details
• Delete a landlord (only if no longer used in any contracts)

---

Step by step

1) Open the landlord list

• Landlords → Landlords (/vermieter/vermieter).

2) Create a new landlord

1. "New" (/vermieter/vermieter/new).
2. Fill in the fields.
3. Save (POST /vermieter/vermieter).

3) Edit a landlord

• Open the entry → "Edit" (/vermieter/vermieter/{id}/edit) → save (POST /vermieter/vermieter/{id}).

4) Delete a landlord

• POST /vermieter/vermieter/{id}/delete.

---

Common questions / problems

"Wrong landlord data appears in the contract PDF"

• Check the master data on the landlord.
• Check the contract template in the TEMPLATING plugin — there it is defined which fields are pulled.

"I can't delete it"

• It is most likely still referenced in contracts.

---

Technical URLs (quick reference)

User area (/vermieter/vermieter):

• GET /vermieter/vermieter — list
• GET /vermieter/vermieter/new — new
• POST /vermieter/vermieter — create
• GET /vermieter/vermieter/{id}/edit — edit
• POST /vermieter/vermieter/{id} — save
• POST /vermieter/vermieter/{id}/delete — delete

Notes

• VERMIETER is a prerequisite for VERTRAG.
• Don't change master data "retroactively" without thought — old PDFs keep their old state, new PDFs use the new state.