Review how SPRK organizes accounts by code, parent-child hierarchy, type, subtype, and active status so you can maintain a usable account list without changing posted balances.
Purpose
Use this article when you need to understand how accounts are grouped, created, edited, imported, exported, or deactivated in the Chart of Accounts page.
Prerequisites
- An active company is selected.
- You know whether you are adding a brand-new account, reorganizing an existing one, or reviewing the current structure.
Steps
- Open
Chart of Accounts. - Review the page header tools:
Newopens the account form.Refreshreloads the list.Exportdownloads the current chart aschart-of-accounts.csv.Importaccepts.csv,.txt,.iif,.xls, or.xlsxfiles.
- Use the search field to find accounts by code or name.
- Use the grouping controls to regroup the list and the expand or collapse controls to change how much of the hierarchy is visible.
- Review the account list structure:
- Accounts are sorted by code.
- Child accounts can be linked by a saved parent account or inferred from account codes when the code structure supports it.
- Filters let you narrow by
Type,Subtype, andStatus.
- Select
Newor the edit pencil for an existing row when you need to maintain an account record. - When creating or editing an account, fill in the fields SPRK supports publicly:
CodeNameType- optional
Subtype - optional parent account
- optional description, bank number, or notes
- Use status carefully:
- Active accounts remain available for normal use.
- Deleting an account from this page sets it inactive instead of removing its history.
Expected Result
You can organize the account list into a clearer structure and keep accounts available for downstream workflows. Current general ledger impact as of 2026-05-02:
- Creating, editing, importing, exporting, or deactivating accounts from
Chart of Accountsdoes not post a journal entry by itself. - These actions change account setup and availability, not existing account balances.
- Export produces a file only and does not change ledger data.
Common Mistakes
- Expecting
Deleteto erase prior history. SPRK marks the account inactive instead. - Importing parent relationships without valid
parentIdvalues. - Treating subtype as required for every account when the page only exposes it as an optional field.
Related Articles
- Record journal entries
- Understand ledger import and export behavior
- Understand audit-sensitive ledger behavior
Info
- App sections:
chart - Last validated: 2026-05-02
- Screenshot status:
not-started