Tutorial

Cancel an unused draft or reservation

Set up properties and rooms; reserve accommodation, check occupants in, cancel unused reservations and check out departing occupants. Link existing employees, customers, contacts and projects.

Updated 14 October 2026 · Native ERP foundation

The native ERP foundation is published: properties, rooms, stays, service requests, charges and physical-key custody. The hotel engine and electronic lock connectors are not commissioned. Food, catering and room service are request and ERP-order workflows; a restaurant POS, kitchen display, online booking engine and automatic keycard encoding are not provided by this release.

Use your own authorized ERP account. These text tutorials describe the published native fields and actions. Screenshots and click markers for this new app will be added in a later documentation pass.

Step 1 of 2

Step 1

Open the Draft or Reserved stay and confirm that cancellation is the intended outcome.

Expected URL expression{ERP_URL}/desk/nexcom-lodging-stay/{RECORD_ID}

Open the list without /{RECORD_ID}. New forms use a temporary new-record identifier. ERP_URL is your organization’s ERP origin.

Expected result: The selected stay has not been checked in.

Step 2 of 2

Step 2

Choose Stay → Cancel and verify the saved status.

Expected URL expression{ERP_URL}/desk/nexcom-lodging-stay/{RECORD_ID}

Open the list without /{RECORD_ID}. New forms use a temporary new-record identifier. ERP_URL is your organization’s ERP origin.

Expected result: Status becomes Cancelled. Terminal stays cannot be reopened by changing the status back; review linked documents separately.

If the action is blocked

Check required fields, current status, linked company and record permissions. Return outstanding keys before checkout. Room and key conflict checks cannot be bypassed by editing their identifiers. For Finance and stock drafts, review native validation messages before submitting.