NexCommand AINexCom Knowledge Base
Field reference

Payment Order

How to use Payment Order 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

Prepare the required information: Series, Company, Company Bank Account, Payment Order Reference.

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 Order 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. 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
Seriesnaming_seriesSelect
Required
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • PMO-
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

Payment Order Typepayment_order_typeSelect
Required · Read-only
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Payment Request
  • Payment Entry
SupplierpartyLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Supplier

Posting Dateposting_dateDate
Optional
Choose the business date required for this field. Confirm its relationship to other dates on the record.
Bankcompany_bankLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Bank

Company Bank Accountcompany_bank_accountLink
Required
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Bank Account

AccountaccountData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Payment Order ReferencereferencesTable
Required
Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Payment Order Reference

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: Payment Order

Child tables

Payment Order Reference — child-row fields
FieldType / behaviorHow to use it
Typereference_doctypeLink
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: DocType

Namereference_nameDynamic Link
Required · Read-only
Select the record identified by the associated document-type field. Verify both the type and the linked record.
AmountamountCurrency
Required · Read-only
Enter the monetary amount in the applicable currency. Review the transaction and company currency before using the value.
SuppliersupplierLink
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: Supplier

Payment Requestpayment_requestLink
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: Payment Request

Mode of Paymentmode_of_paymentLink
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: Mode of Payment

Bank Accountbank_accountLink
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: Bank Account

AccountaccountLink
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: Account

Payment Referencepayment_referenceData
Optional · Read-only
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.

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.