# ErrorState

> With the financial reassurance sentence.

Source: https://lopifi.com/components/error-state
Part of: Lopifi — US GAAP books on autopilot, reviewed by a CPA (https://lopifi.com)

---

- **Family:** System & states — ---
- **Status:** Implemented
- **Spec:** https://lopifi.com/docs/catalog/08-system-states

## Install

```bash
npx shadcn@latest add @lopifi/theme
npx shadcn@latest add @lopifi/error-state
```

## Specification

```
Couldn't load transactions. ⓘ        ← the technical account, one press away
No transactions were affected.       ← the financial reassurance
[Try again]  [Contact support]
```

**The reassurance sentence is the most important line, and it is the only prose that stays on screen.** In a financial product, an error makes users worry that something happened to their money. Saying explicitly that nothing did is worth more than the retry button — and worth more than the paragraph explaining the outage.

The `detail` — which endpoint, which timeout, which missing rate — is real and belongs to the person who asks for it, so it rides an `InfoTip` on the title rather than a third paragraph. An `InfoTip` and not a `Tooltip`: it opens on press, so the account of the failure survives touch.

Variants: network · permission · not-found · server · stale-data. Each states what happened, what it means for their money, and what to do.

## Rules this component obeys

Money is minor units, never floats. `null` is not `0` and neither is redacted. Negatives render in accounting parentheses with the parenthesis column reserved on both sides. Debit and credit are two columns. Per-currency decimal places. Polarity is explicit — up is not always good. Every figure states its period, entity, currency, basis and as-of.