← ExamplesSpecification
Financial specification navigation

View accounts

Financial workspace workflows and project contracts

Open application

Wireframe

/examples/application/accounts?organization=example-household&environment=production&ledger=alex&search=&accountType=all&status=all&account=all&sort=name&filters=&state=&range=90&comparison=expected
Ledger navigation

Accounts

Create account
0 selected
Account hierarchy
NameTypeCommodityBalanceActions
AssetsAssetUSD$28,561.00
Operating checkingAssetUSD$15,611.00
SavingsAssetUSD$5,000.00
Tax reserveAssetUSD$7,950.00
LiabilitiesLiabilityUSD-$775.00
Business credit cardLiabilityUSD-$775.00
EquityEquityUSD$0.00
RevenueRevenueUSD$0.00
ExpensesExpenseUSD$0.00
Unassigned expenseExpenseUSD$0.00

Sequence

Rendering diagram…

Rules

  • Application, Specification and API documentation SHALL share the documentation's sky brand theme; success, warning and error colors SHALL remain semantic.
  • PageTopBar SHALL contain brand and breadcrumbs; a visible PageHeader SHALL contain the page title and page actions.
  • Search and Add filter SHALL precede the table. Search SHALL submit a native GET on Enter; applied filters SHALL appear beneath as editable, individually removable chips.
  • Each structured filter SHALL appear at most once and filters SHALL compose using AND. Clear all SHALL appear only while structured filters are active and SHALL preserve Search.
  • Sorting SHALL use column-heading destinations and SHALL retain active search, filters and workspace.
  • Selecting rows SHALL replace Search and Add filter with X selected, Review selected and Clear selection in the same toolbar; applied filters SHALL remain visible. At zero selection, count and bulk commands SHALL be hidden.
  • Table SHALL own native keyed selection and a screen-reader announcement; the consumer SHALL own the visible count, commands and review feedback. Native fallback SHALL offer toolbar review for checked rows.
  • The toolbar SHALL remain above the row-scrolling viewport and column headings SHALL remain sticky. Counts, commands, review feedback and pagination controls SHALL NOT appear below the table.
  • This finite example SHALL NOT imply an infinite-scroll endpoint or all-matching selection. The composition SHALL allow a consumer to supply additional stable-keyed rows without a table footer.
  • Filter changes SHALL resolve a new server-rendered collection with selection cleared. Review outcomes SHALL retain public collection controls and workspace, without retaining submitted selected keys.
  • Type roots SHALL begin at hierarchy depth zero; accounts SHALL sit one level below their root.
  • Search, type filter and sort SHALL be server-rendered URL controls.
  • Record links SHALL identify the exact account and open View account.
  • Table SHALL own native keyed checkboxes; the page SHALL own selection review and feedback.
  • Review SHALL accept available account IDs and type-group keys, rejecting an empty or unknown selection without changing financial data.
View accounts