NexCommand AINexCom Knowledge Base
Field reference

Repost Payment Ledger

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

Finance & AccountingUpdated 12 October 2026Configuration-aware guidance
Open Repost Payment Ledger ↗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: Company, Posting Date.

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 Repost Payment Ledger 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
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

Posting Dateposting_dateDate
Required		Choose the business date required for this field. Confirm its relationship to other dates on the record.
Voucher Typevoucher_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

Add Manuallyadd_manuallyCheck
Optional		Ignore Voucher Type filter and Select Vouchers Manually
Repost Statusrepost_statusSelect
Optional · Read-only		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • Queued
  • Failed
  • Completed
Repost Error Logrepost_error_logLong Text
Optional		Complete the value according to the field label and the record’s validation rules.
Selected Vouchersrepost_vouchersTable
Optional		Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Repost Payment Ledger Items

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: Repost Payment Ledger

Child tables

Selected Vouchers — child-row fields
FieldType / behaviorHow to use it
Voucher Typevoucher_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

Voucher Novoucher_noDynamic Link
Optional		Select the record identified by the associated document-type field. Verify both the type and the linked record.

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?