NexCommand AINexCom Knowledge Base
Field reference

Payment Gateway Account

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

Finance & AccountingUpdated 12 October 2026Configuration-aware guidance
Open Payment Gateway Account ↗Module guide

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: Payment Gateway, Company, Payment Account.

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 Gateway Account 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 Gatewaypayment_gatewayLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Payment Gateway

Payment Channelpayment_channelSelect
Optional		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Email
  • Phone
  • Other
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

Is Defaultis_defaultCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.
Payment Accountpayment_accountLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Account

CurrencycurrencyRead Only
Optional		System-provided value; correct its source record or calculation rather than overwriting the displayed result.
Default Payment Request MessagemessageSmall 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?