Review how SPRK organizes accounts by code, parent-child hierarchy, type, subtype, posting role, control-account role, and active status so you can maintain a usable account list without changing posted balances.


When To Use This
Use this article when you need to understand how accounts are grouped, created, edited, imported, exported, or deactivated in the Chart of Accounts page.
Before You Start
- 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,Status,Posting, andControl. - The list can show
NonpostingandControlcolumns so you can tell why an account is available for structure review but not every posting workflow. - If the company is configured with
Required account fields = Name, account-code columns and code-first labels can disappear from the visible chart and related account pickers.
- 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
Nonposting accountwhen the account is a parent or summary account that should not receive posted activity directlyControl accountwhen the account should be controlled by a subledger or source workflow instead of new manual journal linesActive
- If you import chart data, review account-role columns before relying on downstream pickers:
- Spreadsheet-style account imports can map boolean fields such as
Nonposting AccountandControl Account. - Ordinary yes/no or true/false style values map to those switches.
- A QuickBooks account type of
Nonpostingis not the same as SPRK’s account-levelNonposting accountswitch.
- Use status carefully:
- Active accounts remain available for normal use.
- Deleting an account from this page sets it inactive instead of removing its history.
What Happens Next
You can organize the account list into a clearer structure and keep accounts available for downstream workflows.
- 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.
Nonposting accountkeeps a parent or summary account visible in the chart but removes it from current posting-oriented account pickers unless the specific surface explicitly supports nonposting accounts.Control accountmarks an account as subledger controlled and can make it unavailable for new manual journal-entry posting. It is a posting restriction, not an inactive or deleted account.- Name-only account presentation changes how accounts are shown and sorted in supported lists. It does not delete stored account codes or change balances.
If Something Looks Wrong
| What You See | What To Check | What To Do Next |
|---|---|---|
| The page does not show the expected result | Expecting Delete to erase prior history |
SPRK marks the account inactive instead |
| You are about to take an action that may affect the result | Importing parent relationships without valid parentId values |
Confirm the visible company, page, and workflow state before continuing |
| Two similar workflows or fields are easy to mix up | Treating subtype as required for every account when the page only exposes it as an optional field | Use the specific workflow or control named on this page |
| The result looks ready, but a key check is unresolved | Assuming missing visible account codes mean the codes were deleted | Check the company’s Required account fields setting first |
| The result looks ready, but a key check is unresolved | Assuming every active account appears in every selector | Nonposting accounts and control-restricted accounts can be hidden from posting, default-account, Banking, journal, or report selectors even when they remain visible in Chart of Accounts |
| The result does not match what you expected | Confusing account-level Control account with the company-level Control accounts setting |
Both protect source-workflow accounts, but they are configured in different places |