Skip to content

TransactionRow

Desktop row.
Spec only
Status
Specified
Family
5 of 13

TransactionRow is specified but not yet built. The spec below is the contract it will be built against — reviewed before the code, which is the order that makes the review worth doing. See the roadmap for where it lands.

The four-layer spec

[checkbox] [date] [mark] [description / merchant] [category] [account] [status] [amount]

Description truncates; amount never does. Merchant name on a second line at caption/--text-secondary when it differs from the description. Row actions revealed on hover/focus, right-aligned, always present on touch.

Lifted verbatim from Ledger & tables. The doc and this page are the same paragraphs, so they cannot disagree.

The accounting it encodes

Concepts this component renders. Each one is defined once, in the lexicon, and used identically in the code and the copy.

Also in Ledger & tables

See also

A component is specified in one place, defined in another, and running in a third. All three, from here.

Elsewhere in the system

Where TransactionRow sits in the rest of the system — the live section it renders in, the calculators that compute what it displays, and the ledger payloads it is fed from.

Components are copied into your repository and meant to be edited — rounding policy, fiscal calendar and compliance copy differ per company.

Told when Ledger & tables changes

Components are copied into your repo, so a fix here does not reach you on its own. One email when a component in this family changes in a way that needs a migration — and nothing when it does not.

One address, no list rental, unsubscribe in one click.

Works in your QuickBooks Online or Xero file

Get your books closed every month

Lopifi is building AI bookkeeping that keeps your books closed on US GAAP as transactions happen, with a CPA review every quarter, for $200 a month. We’re not open yet.

$200/month when we open. No card now.