Linking an owner to an object and creating an agreement

When an object is sold, the new owner must be linked to the object via an owner's agreement. This is necessary to be able to make invoices and settlements through Booking Experts, and to apply the agreement made between you and the owner.

Creating a new owner's agreement

Go to the Setup tab and then to Objects. Click the object to which you want to link an owner. You can also use the search bar at the top of your screen to find the right object.

Once you have clicked the object, go to the 'Owners' tab. Then click '+New agreement'. Enter a starting date and select the right owner via the dropdown. Select the appropriate commission agreement.

Are there any costs you want to settle with the owner? If so, enter these here.

The next step is to choose the applicable Owner profile. The owner profile determines which owner permissions the owner gets via the owner's portal.

Then tick the periodic costs applicable to this owner.

Periodic costs have a default price. A custom price can be entered manually. Set the custom price at zero if this periodic cost should be free.

If applicable, specify the discount percentage the owner is allowed to receive on own stays.

If the owner is exempt from tourist tax, you can indicate this by ticking the box. This tick also applies when the owner buys off his tourist tax annually (lump sum to government). When ticked, costs of the type β€˜tourist tax’ will not be applied to reservations of the owner themselves.

The newly created agreement can also be found in the agreements overview under the 'Owners' tab.

Editing an owner's agreement

You can delete or edit a created appointment if no invoices are linked to it yet. To do so, click on the start date.

When creating a new agreement, any invoices that have already been created under a previous agreement must be taken into account. If they overlap the new period/agreement, an error message is generated.

πŸ‡³πŸ‡± πŸ‡©πŸ‡ͺ

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.