NexCommand AINexCom Knowledge Base
Field reference

Bank Transaction Rule

How to use Bank Transaction Rule 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: Rule Name, Transaction Type, Priority, Company, Description Rules, Classify As.

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 Bank Transaction Rule 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. 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
Rule Namerule_nameData
Required
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Transaction Typetransaction_typeSelect
Required
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Any
  • Withdrawal
  • Deposit
PrioritypriorityInt
Required
Enter a whole-number value.
Min Amountmin_amountCurrency
Optional
Enter the monetary amount in the applicable currency. Review the transaction and company currency before using the value.
Max Amountmax_amountCurrency
Optional
Enter the monetary amount in the applicable currency. Review the transaction and company currency before using the value.
Rule Descriptionrule_descriptionSmall Text
Optional
Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.
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

Description Rulesdescription_rulesTable
Required
Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Bank Transaction Rule Description Conditions

Classify Asclassify_asSelect
Required
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Bank Entry
  • Payment Entry
  • Transfer
AccountaccountLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Account

Bank Entry Typebank_entry_typeSelect
Optional
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Single Account
  • Multiple Accounts
Party Typeparty_typeLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: DocType

PartypartyDynamic Link
Optional
Select the record identified by the associated document-type field. Verify both the type and the linked record.
AccountsaccountsTable
Optional
Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Bank Transaction Rule Accounts

Child tables

Description Rules — child-row fields
FieldType / behaviorHow to use it
CheckcheckSelect
Required
Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Contains
  • Starts With
  • Ends With
  • Regex
ValuevalueSmall Text
Required
Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.
Accounts — child-row fields
FieldType / behaviorHow to use it
AccountaccountLink
Required
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Account

Party Typeparty_typeLink
Optional
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Party Type

PartypartyDynamic Link
Optional
Select the record identified by the associated document-type field. Verify both the type and the linked record.
DebitdebitData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
CreditcreditData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
User Remarkuser_remarkSmall 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.