Review overdue keys and reconcile custody
Follow the steps below on this page. Screenshots for Garrison & Lodging will be added separately.
Before you start
URL key: {ERP_URL} is your ERP origin, such as https://enterprise.nexcommand.ai or https://erpstaging.nexcommand.ai. Open the list URL first; saved records append /{RECORD_ID}. New drafts use a temporary new-record identifier. Queries and selected tabs may add parameters.
Step 1
Filter Status Issued and Return due earlier than the review time. Review the linked key property, room and holder.
{ERP_URL}/desk/nexcom-key-custodySaved record{ERP_URL}/desk/nexcom-key-custody/{RECORD_ID}Expected result: The list identifies overdue custody records.
Step 2
Contact the responsible holder using the approved operational process and physically reconcile keys against the register. Do not overwrite issue history to show a different holder.
{ERP_URL}/desk/nexcom-key-custodySaved record{ERP_URL}/desk/nexcom-key-custody/{RECORD_ID}Expected result: The original handover remains traceable.
Step 3
Use Return key only after receipt. For a genuinely lost key, enter Loss / exception details and save Status Lost.
{ERP_URL}/desk/nexcom-key-custodySaved record{ERP_URL}/desk/nexcom-key-custody/{RECORD_ID}Expected result: Return time is recorded, or the lost key is disabled for new issue.
Step 4
Arrange physical rekeying or authorized access response where required. Electronic credentials are not revoked by this register.
{ERP_URL}/desk/nexcom-lodging-keySaved record{ERP_URL}/desk/nexcom-lodging-key/{RECORD_ID}Expected result: The incident response addresses actual security, not merely the ERP status.
Step 5
Before checkout, confirm no Issued custody remains for the stay. Departure key exception does not bypass this check.
{ERP_URL}/desk/nexcom-lodging-staySaved record{ERP_URL}/desk/nexcom-lodging-stay/{RECORD_ID}Expected result: Checkout can proceed only after custody is resolved.