Skip to main content
Share / Export

GL Account Parts

Company Tracker action: implementation-setup-gl-account-parts Milestone: General Ledger / Module Setup (milestone_id=3, core_milestone_id=2) Order: 4 Estimated duration: 1 hour Typical owner: Controller

Purpose​

Define GL account parts (and instances) so the chart of accounts can be entered and multi-part formats (branch/dept/location) have their instance lists.

Prerequisites​

  • Code Format Design decisions for account parts (count, lengths, meaning of each part).
  • Company ready for GL setup.
  • Typically before GL Chart of Accounts (Part 1 must exist first).

Vista configuration article​

See the detailed Vista guide:

Configuring GL Account Parts

Field meanings and form steps live there. Do not restate them on this page.

Implementation guidance​

  • Part 1 is mandatory. It is the base part of the GL account. Without Part 1, you cannot enter the Chart of Accounts.
  • Also add additional parts (2, 3, 4, …) that Code Format Design decided (branch, department, location, and so on).
  • On the Instances tab for those extra parts, list each instance code and description (example: Part 2 is two-digit department → instances 01, 02, 03 with descriptions).
  • Part 1 instances are auto-populated when GL accounts are first entered. If GL account descriptions are updated after the initial save, those updates do not flow back to Account Parts descriptions.

Done when​

  • Part 1 exists (required).
  • All in-scope additional parts exist.
  • Instances listed for non-Part-1 parts as needed.
  • Team understands Part 1 instance auto-create vs no description sync on later COA edits.