Return keys and check out a stay
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.
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
Filter custody records by the stay and inspect all Issued keys. Physically receive each returned key and use Return key.
{ERP_URL}/desk/nexcom-key-custody/{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: No issued key remains against the stay. A lost key must follow the documented loss process.
Step 2
Review the stay charges and their invoice links. Coordinate remaining billing with Finance.
{ERP_URL}/desk/nexcom-lodging-charge/{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: Billing is reviewed independently; checkout does not automatically submit or settle an invoice.
Step 3
Open the Checked In stay and choose Stay → Check out.
{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 Checked Out, the departure time is recorded, and the room becomes Dirty. Outstanding key custody blocks checkout.
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.