NexCommand AINexCom Knowledge Base
Tutorial

Record lodging charges and prepare an invoice

Coordinate food, catering, room service, housekeeping and maintenance requests. Record charges and create linked ERP invoice or stock drafts; use MRO and Helpdesk links where configured.

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 4

Step 1

Open the stay and choose its Billing customer before invoicing.

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 stay identifies the customer to invoice.

Step 2 of 4

Step 2

Create a charge for the Stay. Choose Billable item, positive Quantity and Rate, and optionally Related service and Description. Save each billable line.

Expected URL expression{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: Charges are recorded against the stay. Amounts are not automatically derived from a room rate engine.

Step 3 of 4

Step 3

Choose Finance → Create / open invoice draft.

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: Uninvoiced charges are added once to a matching draft, or a new invoice is created. Repeating the action without new charges does not duplicate lines.

Step 4 of 4

Step 4

Review company, customer, currency, tax, item accounts and payment terms in Finance. Submit and collect payment through the normal authorized workflow.

Expected URL expression{ERP_URL}/desk/sales-invoice/{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 linked draft is not automatically submitted or paid. If an earlier invoice is submitted, later charges can create a subsequent draft; cancelled invoice handling requires Finance review.

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.