← ExamplesSpecification
Financial specification navigation

View transactions

Financial workspace workflows and project contracts

Open application

Wireframe

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

Transactions

0 selected
Transactions
DateDescriptionVerificationAccountAmount (USD)
Sep 18, 2026Client paymentVerifiedOperating checking$3,200.00
Sep 17, 2026Cloud hostingVerifiedOperating checking-$89.00
Sep 16, 2026Office suppliesUnverifiedBusiness credit card-$125.00
Sep 15, 2026Tax paymentVerifiedTax reserve-$450.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.
  • Amounts SHALL be signed decimal USD values; dates SHALL be date-only values.
  • Verification SHALL be independent of amount.
  • Empty results SHALL preserve filter controls.
  • Selection review SHALL validate available transaction IDs without changing verification or moving money.
View transactions