← ExamplesSpecification
Financial specification navigation

Update account

Financial workspace workflows and project contracts

Open application

Wireframe

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

Operating checking

Type
Asset
Commodity
USD
Parent account
Assets
Source
Created in the example
Month-end observed balance
Not required
Balance
$15,611.00

Balance · Operating checking

$15,611.00

━ Actual┄ Expected scenario
Actual balances from seeded transactions; dashed values are an authored scenario, not a financial forecast.
Jun 20, 2026Sep 18, 2026

Actual balances use seeded opening balances and transactions. The dashed scenario is illustrative, not a prediction.

Transactions

Operating checking transactions
DateDescriptionVerificationAccountAmount (USD)
Sep 18, 2026Client paymentVerifiedOperating checking$3,200.00
Sep 17, 2026Cloud hostingVerifiedOperating checking-$89.00

Edit Operating checking

Example accounts use generic types and USD, with a root parent matching the account type. Month-end observations are not required for these fixtures.

Cancel

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.
  • Names SHALL contain 1–80 characters and be unique ignoring case, excluding the account being updated.
  • Account type SHALL be one of Asset, Liability, Equity, Revenue or Expense; parent SHALL match that type root.
  • Commodity SHALL be USD, subtype SHALL be Generic and month-end observation SHALL be not required.
  • Native required validation SHALL precede submission; server validation SHALL reject invalid requests independently.
  • A successful submission SHALL validate only: seeded accounts and submitted private values SHALL NOT be stored.
  • The editor SHALL begin with the exact account's seeded values.
  • Cancel or Escape SHALL return to that account without submitting.
Update account