NexCommand AINexCom Knowledge Base
Field reference

NexCom Employee Request

How to use NexCom Employee Request in HR Requests: access, working steps, fields, related records and troubleshooting.

Human ResourcesUpdated 12 October 2026Configuration-aware guidance
Open NexCom Employee Request ↗Module guide

Purpose and access

Route routine requests to the assigned supervisor and keep payroll and loan requests within the designated HR/Finance process. Include the requested dates, reason and supporting documents without distributing unnecessary personal information.

This page is a record page in Human Resources → HR Requests. Use the link above to open the configured destination; permissions are checked by the destination service.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Before you start

Prepare the required information: Request category, Subject, Request details.

Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.

Working steps

  1. Open NexCom Employee Request from Human Resources → HR Requests, or use ERP Search.
  2. Filter the list and open the relevant record. To add a record, use Add/New when your role provides that action.
  3. Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
  4. Save the record and address validation messages. Reload and verify the saved values and relationships.
  5. Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.

Field reference

These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.

FieldType / behaviorHow to use it
EmployeeemployeeLink
Required · Read-only		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Employee

Requestersubmitted_byLink
Required · Read-only		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

Request categorykindSelect
Required		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • HR letter
  • Profile correction
  • Attendance correction
  • Employment request
  • Payroll inquiry
  • Loan request
  • Advance inquiry
  • Confidential HR
SubjectsubjectData
Required		Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Request detailsdescriptionSmall Text
Required		Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.
Attendance dateattendance_dateDate
Optional		Choose the business date required for this field. Confirm its relationship to other dates on the record.
Requested loan amountrequested_amountCurrency
Optional		Enter the monetary amount in the applicable currency. Review the transaction and company currency before using the value.
CurrencycurrencyLink
Optional		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Currency

Requested loan term (months)desired_term_monthsInt
Optional		Enter a whole-number value.
StatusstatusSelect
Optional · Read-only		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Pending supervisor
  • Pending HR
  • Pending Finance
  • Returned
  • Approved
  • Rejected
Assigned supervisorapproverLink
Optional · Read-only		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

Released review reasonpublic_messageSmall Text
Optional · Read-only		Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.
Last reviewerreviewed_byLink
Optional · Read-only		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

Last decision timereviewed_atDatetime
Optional · Read-only		Record the date and time in the configured system/user time zone.
Private Helpdesk tickethelpdesk_ticketLink
Optional · Read-only		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: HD Ticket

Internal HR / Finance notesinternal_notesSmall Text
Optional		Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.

Troubleshooting

  • Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
  • Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
  • Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
  • Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.
Was this useful?