Chart of accounts configuration

GL account types

Every GL account in Arvexi belongs to one of six standard types. The account type determines how balances behave (normal debit or credit), where they appear in financial statements, and how they interact with reconciliation and close workflows.

• Asset: Normal debit balance. Appears on the balance sheet. Includes cash, receivables, fixed assets, ROU assets, and prepaid expenses.
• Liability: Normal credit balance. Appears on the balance sheet. Includes payables, accrued liabilities, lease liabilities, and deferred revenue.
• Equity: Normal credit balance. Appears on the balance sheet. Includes retained earnings, common stock, AOCI, and non-controlling interest.
• Revenue: Normal credit balance. Appears on the income statement. Resets to zero at period close.
• Expense: Normal debit balance. Appears on the income statement. Includes operating expenses, interest expense, depreciation, and tax provisions.
• Statistical: No balance direction. Used for non-financial tracking (headcount, square footage, lease count) that supports ratio analysis and allocations.

To add accounts, go to Settings → Chart of Accounts and click Add Account. Enter the account number, name, and type. You can also import accounts in bulk via CSV using the Smart Import Wizard.

Account mapping for consolidation

When your entity hierarchy includes entities with different charts of accounts (common after acquisitions or in multi-country operations), you need a mapping layer that translates local accounts to a consolidated chart.

Arvexi uses a two-tier mapping approach:

• Local chart: The entity’s own chart of accounts, imported from their ERP. This is what appears on entity-level reports.
• Consolidated chart: The global chart used for group-level reporting. Each local account is mapped to exactly one consolidated account.

To configure mappings, select an entity in the hierarchy, open the Account Mapping tab, and link each local account to its consolidated equivalent. Many-to-one mappings are supported, and multiple local accounts can map to the same consolidated account.

Segment dimensions and values

Beyond the account number, Arvexi supports up to 10 segment dimensions that add analytical depth to every transaction. Common dimensions include:

• Cost Center: The department or team responsible for the expense (for example, “Engineering,” “Sales,” “G&A”).
• Project: A project or initiative code for tracking project-level spend.
• Location: A physical site or office code, useful for property-level reporting in lease accounting.
• Intercompany: The counterparty entity code for intercompany transactions, used to drive elimination during consolidation.
• Custom dimensions: Up to six additional dimensions that you define, such as product line, region, channel, or contract.

Configure dimensions in Settings → Chart of Accounts → Segments. For each dimension, define the list of valid values. Arvexi validates segment values on data import and journal entry creation, rejecting records with invalid combinations.

Account grouping

Account groups let you organize accounts into logical clusters for reporting and analysis without changing the underlying chart structure. Groups are hierarchical and independent of the GL account numbering scheme.

Common grouping patterns:

• Financial statement line items: Group accounts by their presentation on the balance sheet or income statement (for example, “Current Assets,” “Long-term Debt,” “Cost of Revenue”).
• Reconciliation categories: Group accounts by the type of reconciliation they require (for example, “Bank Accounts,” “Intercompany,” “Accruals,” “Fixed Assets”).
• Regulatory classifications: Group accounts by reporting standard requirements (for example, ASC 842 lease accounts, ASC 606 revenue accounts).

Each account can belong to multiple groups. Groups drive dashboard widgets, report filters, and close task scoping. For example, you can create a close task that applies to all accounts in the “Accruals” group and assign it to the appropriate team.

AI-assisted mapping suggestions

When you add a new entity or import a new chart of accounts, Arvexi Cortex analyzes the account names, numbers, and types to suggest mappings to your consolidated chart automatically.

Cortex uses three signals to generate suggestions:

1. Name similarity: Cortex compares the local account name against consolidated account names using semantic matching. It recognizes that “Accounts Receivable” and “Trade Receivables” and “Debtors” refer to the same concept.
2. Account number patterns: If your numbering scheme follows a standard pattern (for example, 1xxx for assets, 2xxx for liabilities), Cortex uses the number range to narrow suggestions.
3. Historical mappings: Cortex learns from mappings you have already confirmed across other entities. If you mapped “Mietaufwand” (German for rent expense) to “6100: Rent Expense” for your German entity, Cortex suggests the same mapping for any new entity with a similar account.

Suggestions appear as pre-filled mappings with a confidence score. Accept them with one click, or override with your own selection. Every suggestion Cortex makes is logged, so you can review its accuracy over time and provide feedback to improve future suggestions.

For organizations with complex charts spanning thousands of accounts, Cortex typically maps 80–90% of accounts correctly on the first pass, reducing manual mapping work from days to hours.