NexCommand AINexCom Knowledge Base
Field reference

Payroll Period

How to use Payroll Period in Payroll: access, working steps, fields, related records and troubleshooting.

Human ResourcesUpdated 12 October 2026Configuration-aware guidance
Open Payroll Period ↗Module guide

Purpose and access

Maintain salary components, structures and assignments, then prepare payroll for the selected period. Review attendance and leave effects, deductions and employee details before submission and payment. Payroll access is private.

This page is a record page in Human Resources → Payroll. 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: Company, Start Date, End Date.

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 Payroll Period from Human Resources → Payroll, 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. Add the required child rows. Review each row’s identifiers, linked records and values, using the child-table field reference below.
  5. Save the record and address validation messages. Reload and verify the saved values and relationships.
  6. 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
CompanycompanyLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Company

Start Datestart_dateDate
Required		Choose the business date required for this field. Confirm its relationship to other dates on the record.
End Dateend_dateDate
Required		Choose the business date required for this field. Confirm its relationship to other dates on the record.
Payroll PeriodsperiodsTable
Optional		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Payroll Period Date

Child tables

Payroll Periods — child-row fields
FieldType / behaviorHow to use it
Start Datestart_dateDate
Required		Choose the business date required for this field. Confirm its relationship to other dates on the record.
End Dateend_dateDate
Required		Choose the business date required for this field. Confirm its relationship to other dates on the record.

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?