Aller au contenu principal

Account Structures Configuration

Navigation Path: General Ledger module > Chart of accounts > Account structures

Overview​

The Account structures page is pivotal for defining the valid combinations of main accounts and financial dimensions. By establishing robust account structures, you enforce stringent data entry constraints at the time of transaction posting, thereby ensuring reporting accuracy and structural integrity.

An account structure consists of a linear progression of dimension segments (starting universally with the MainAccount) and specific rules (constraints) dictating the permissible values for each segment.

Structure Details​

  • Name & Description: The unique identifier and contextual purpose of the structure (e.g., "Expense Account Structure").
  • Active Status: A structure must be meticulously validated and activated before it can be assigned to a Ledger and utilised in transaction processing.

Structure Rules (Segments and Constraints)​

This grid constitutes the core logic engine of the account structure.

Segments (Columns)​

You may expand the structure horizontally by adding dimension segments (e.g., Department, CostCenter, Project) via the Add segment action in the toolbar. The sequence of these segments dictates the hierarchical evaluation order during transaction entry.

Constraints (Rows)​

Each row represents an acceptable pattern of dimension values. The system evaluates a transaction against these rows sequentially; a match on any single active row permits the transaction to post.

Constraint Syntax Rules​

When defining constraints within a grid cell, you must utilise the following strictly enforced syntax constructs. The system's underlying evaluation engine meticulously parses these strings:

  • Wildcard / Any (* or %): Matches absolutely any value, including an empty (blank) dimension value. Example: *
  • Exact Match: Matches a singular, specific value perfectly. Example: 1010 or SALES
  • Prefix / Partial Wildcard: Matches any value beginning with the specified sequence. Example: 110* (Matches 1100, 1101, 110A, etc.)
  • Range (Closed): Defines an inclusive continuum of values, separated by ... You may explicitly use square brackets [] or implicitly omit them. Example: 1000..1999 or [1000..1999]
  • Range (Open/Mixed): Utilise parentheses () to denote an exclusive boundary. Example: (1000..1999) (Exclusive of 1000 and 1999) Example: [1000..1999) (Inclusive of 1000, exclusive of 1999)
  • List (Comma-Separated): Provides a discrete enumeration of valid exact values, separated by commas. Example: 1010, 1020, 1030

Note: The system intelligently assigns specificity scores to these constraints during evaluation. An Exact Match is prioritised over a List, which is prioritised over a Range, with a Wildcard possessing the lowest specificity.