NexCommand AINexCom Knowledge Base
Field reference

Payment Term

How to use Payment Term in Banking & Payments: access, working steps, fields, related records and troubleshooting.

Purpose and access

Record receipts, payments and transfers with the correct party, accounts, currency and allocation. Reconcile bank activity with ERP entries. A payment record is not a bank transfer instruction unless a separately configured integration performs that action.

This page is a record page in Finance & Accounting → Banking & Payments. 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

Review the current settings or existing records and prepare the information needed for the change.

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 Payment Term from Finance & Accounting → Banking & Payments, 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
Payment Term Namepayment_term_nameData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Invoice Portion (%)invoice_portionFloat
Optional
Enter a numeric value using the required unit and precision.
Mode of Paymentmode_of_paymentLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Mode of Payment

Due Date Based Ondue_date_based_onSelect
Optional
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Day(s) after invoice date
  • Day(s) after the end of the invoice month
  • Month(s) after the end of the invoice month
Credit Dayscredit_daysInt
Optional
Enter a whole-number value.
Credit Monthscredit_monthsInt
Optional
Enter a whole-number value.
Discount Typediscount_typeSelect
Optional
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Percentage
  • Amount
DiscountdiscountFloat
Optional
Enter a numeric value using the required unit and precision.
Discount Validity Based Ondiscount_validity_based_onSelect
Optional
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Day(s) after invoice date
  • Day(s) after the end of the invoice month
  • Month(s) after the end of the invoice month
Discount Validitydiscount_validityInt
Optional
Enter a whole-number value.
DescriptiondescriptionSmall 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.