NexCommand AINexCom Knowledge Base
Field reference

Contract

How to use Contract in Contracts: access, working steps, fields, related records and troubleshooting.

Purpose and access

Record the contracting parties, validity dates and agreed terms. Associate the contract with the relevant commercial activity where supported. Uploading a signed document does not automatically change the status of an ERP order.

This page is a record page in Sales & Marketing → Contracts. 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: Party Type, Party Name, Contract Terms.

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 Contract from Sales & Marketing → Contracts, 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. When the draft is complete and you are authorized, submit it through the available approval process. Submission can create operational or accounting effects. Use the permitted cancellation/amendment process for later corrections.

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
Party Typeparty_typeSelect
Required
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Customer
  • Supplier
  • Employee
Signedis_signedCheck
Optional
Enable or disable the named option only when it matches the intended record behavior.
Party Nameparty_nameDynamic Link
Required
Select the record identified by the associated document-type field. Verify both the type and the linked record.
Party Userparty_userLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

Party Full Nameparty_full_nameData
Optional · Read-only
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Start Datestart_dateDate
Optional
Choose the business date required for this field. Confirm its relationship to other dates on the record.
End Dateend_dateDate
Optional
Choose the business date required for this field. Confirm its relationship to other dates on the record.
SigneesigneeData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Signed Onsigned_onDatetime
Optional
Record the date and time in the configured system/user time zone.
IP Addressip_addressData
Optional · Read-only
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Contract Templatecontract_templateLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Contract Template

Contract Termscontract_termsText Editor
Required
Maintain formatted content for the record; review any public-facing output before publishing.
Requires Fulfilmentrequires_fulfilmentCheck
Optional
Enable or disable the named option only when it matches the intended record behavior.
Fulfilment Deadlinefulfilment_deadlineDate
Optional
Choose the business date required for this field. Confirm its relationship to other dates on the record.
Fulfilment Termsfulfilment_termsTable
Optional
Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Contract Fulfilment Checklist

Signee (Company)signee_companySignature
Optional
Complete the value according to the field label and the record’s validation rules.
Signed By (Company)signed_by_companyLink
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

Document Typedocument_typeSelect
Optional
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Quotation
  • Project
  • Sales Order
  • Purchase Order
  • Sales Invoice
  • Purchase Invoice
Document Namedocument_nameDynamic Link
Optional
Select the record identified by the associated document-type field. Verify both the type and the linked record.
Amended Fromamended_fromLink
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: Contract

Child tables

Fulfilment Terms — child-row fields
FieldType / behaviorHow to use it
FulfilledfulfilledCheck
Optional
Enable or disable the named option only when it matches the intended record behavior.
RequirementrequirementData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
NotesnotesText
Optional
Provide the required record description or content. Keep operational instructions clear and applicable.
Amended Fromamended_fromLink
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: Contract Fulfilment Checklist

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.