When accommodations are owned by third parties, the concept of owners is applicable in business. This often involves charging periodical or incidental costs as well as settling owner income (potentially related to rental income).

An owner can be present in different forms and contexts, in which different combinations of charging and settling can occur. Some examples:

Owners who use the accommodation exclusively for own use (non-renting owners). These owners are periodically charged costs (annual resort costs, local taxes, energy consumption etc)
Owners of which accommodation is rented out by MXT client (renting owners) and receive income based on that. Any costs are settled with rental income.
Owners who receive income based on the rental activity, but also receive and pay separate standalone invoices for periodical costs, maintenance etc.

Concept

Depending on the type of owner (renting or non-renting), the following entities are in scope:

Owner objects
Yearround reservations
Rentable objects
Contracttype
Contract
Ownership
Fiscal type

Refer the visualisation below

Approach

Depending on the business and system context, a highlevel flow can be followed.

Note: Alternative flows, touching into fewer steps, are possible. This occurs when a non-renting owner becomes a renting owner, or if a client previously did not invoice owner costs via MXT system and wishes to do so in future. Scenario's like these require a custom approach.

The flowchart leads to the following chronological sequence of events:

Step	Task	Extra info
1.	Collect owner data	Owner data format blank.xlsx
2.	Clarify contractual rules	Contracttype data blank.xlsx
3.	Configuration of owners
4.	Configuration of contracttypes
5.	Configuration of owner object
6.	Configuration of accommodationkind, DC, RC
7.	Configuration of rentable objects
8.	Link unit to owner, create contract
9.	Create yearround reservations on owner objects

Browser not supported