NexCommand AINexCom Knowledge Base
Field reference

Bisect Nodes

How to use Bisect Nodes in General Ledger & Closing: access, working steps, fields, related records and troubleshooting.

Finance & AccountingUpdated 12 October 2026Configuration-aware guidance
Open Bisect Nodes ↗Module guide

Purpose and access

Establish the chart of accounts and fiscal structure, review journals and ledgers, and complete period-end checks. Reconcile subledgers to the general ledger before closing; preserve the audit trail for corrections.

This page is a internal/admin record in Finance & Accounting → General Ledger & Closing. 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 Bisect Nodes from Finance & Accounting → General Ledger & Closing, 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
RootrootLink
Optional		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Bisect Nodes

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

Linked record: Bisect Nodes

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

Linked record: Bisect Nodes

Period_from_dateperiod_from_dateDatetime
Optional		Record the date and time in the configured system/user time zone.
Period To Dateperiod_to_dateDatetime
Optional		Record the date and time in the configured system/user time zone.
DifferencedifferenceFloat
Optional		Enter a numeric value using the required unit and precision.
Balance Sheet Summarybalance_sheet_summaryFloat
Optional		Enter a numeric value using the required unit and precision.
Profit and Loss Summaryprofit_loss_summaryFloat
Optional		Enter a numeric value using the required unit and precision.
GeneratedgeneratedCheck
Optional		Enable or disable the named option only when it matches the intended record behavior.

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?