IntelligentTaxProduct Documentation

Client workspace

Chart of accounts

Available

Initialize and maintain the client's account hierarchy, code rules, class, balance direction, and status.

What this menu does

Provide the client-level accounting master data used by vouchers, ledger, tax, assets, and later reporting.

Where to find it

Client workspace navigation: Accounting → Chart of accounts.

When to use it

  • Initialize an empty chart from an active firm template.
  • Search and filter accounts.
  • Create a root or child account.
  • Edit status, name, or balance direction when allowed.
  • Delete an unused account.

Before you begin

  • Open the correct client workspace.
  • Confirm the company name shown in the workspace header.

Page regions

  1. 01Ledger index and class track
  2. 02Search, class, and status filters
  3. 03Hierarchical account table
  4. 04Root/child create and edit drawer
  5. 05Code availability guidance
  6. 06Template initialization dialog
  7. 07Delete confirmation

Supported operations

01

Initialize from a template

Purpose
Create the client's first chart from an active firm template.
When available
Available only before the first client account exists.
  1. 1

    Confirm the client has no existing chart accounts.

  2. 2

    Select Create from template.

  3. 3

    Choose an active template that contains accounts and review its use case.

  4. 4

    Confirm initialization and verify the returned account count.

Result

The template is copied into a separate client chart; later template edits do not change it automatically.

02

Search and filter accounts

Purpose
Find an account while preserving hierarchy context.
  1. 1

    Enter a code/name keyword or choose class and status.

  2. 2

    Use the 1xxx-5xxx class track to jump between groups.

  3. 3

    Review matching branches; ancestors remain visible when a child matches.

  4. 4

    Reset filters when no account matches.

Result

The table shows matching hierarchy branches only.

03

Create a root or child account

Purpose
Add a valid account at the intended hierarchy level.
  1. 1

    Use New account for a root, or Add child on the intended parent.

  2. 2

    For a root, enter a four-digit code whose first digit matches class; for a child, review the suggested parent-prefixed code.

  3. 3

    Enter name, class, and normal balance direction; review duplicate and format feedback.

  4. 4

    Save and confirm the new account appears under the intended parent.

Result

A valid account is created; hierarchy and code are fixed according to the selected parent.

04

Edit or delete an account

Purpose
Maintain an account without breaking posted accounting history.
  1. 1

    Select Edit and review which fields are locked by hierarchy or posted activity.

  2. 2

    Change allowed fields and heed opposite-balance warnings.

  3. 3

    Save, or choose Delete only for an unused account with no children.

  4. 4

    Confirm deletion impact; deactivate an in-use account instead of deleting it.

Result

Allowed changes are saved; protected accounting history remains intact.

Business rules and fields

  • Root codes are four digits: assets 1xxx, liabilities 2xxx, equity 3xxx, revenue 4xxx, expenses 5xxx.
  • The system supports up to four hierarchy levels.
  • An account with posted activity cannot change protected balance/class context or become a parent.
  • Accounts with children cannot be deleted; in-use accounts must be deactivated.
  • Template initialization is first-setup only.

States you may see

ActiveInactivePostable/summary determined by account configurationLocked by posted activity

What happens next

  • The client chart remains valid for voucher selection and ledger reporting.
  • Every initialization and maintenance action is traceable.

Common problems

What you seeWhy it happensWhat to do

The page is view-only or an action is missing.

The workspace is read-only, the employee lacks maintenance access, or the record status blocks changes.

Verify the client lifecycle status and your access with a firm administrator. Do not work around the restriction in another client.

A save, generation, or load action fails.

Business validation, missing source data, an expired session, or a temporary service problem can block the action.

Read the business reason shown on the page, fix the source data, and retry once. Preserve the request identifier when asking support for help.

Visibility and access

The page follows employee permissions, client assignment, and workspace mode. Suspended clients can be view-only; draft or terminated clients cannot enter the workspace.

System screenshots

Initialize and maintain the client's account hierarchy, code rules, class, balance direction, and status.