Tutorial

Return a key or record a lost key

Register physical keys, record issue and return, track holders and due times, and handle loss incidents. Electronic keycard issuance remains disabled pending hardware selection and commissioning.

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 3

Step 1

Open the Issued custody record and verify the physical key against its Key code.

Expected URL expression{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: The correct custody event is selected.

Step 2 of 3

Step 2

For a returned key, receive it and choose Return key. For a loss, enter Loss / exception details, choose Lost and save.

Expected URL expression{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: A return records the return time. A loss requires incident details and makes the key unavailable; it does not remotely revoke electronic access.

Step 3 of 3

Step 3

Verify the key availability and follow the organization’s security and replacement process for lost or compromised keys.

Expected URL expression{ERP_URL}/desk/nexcom-lodging-key/{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 custody trail is retained and affected stay checkout can be reviewed.

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.