Understanding statements

The app has two main views of your activity: Events and Statements. They show the same underlying data, but from different angles.

Events vs. statements

An event is what you record — a financial action like borrowing money, buying a security, or making a payment. Events carry intent: they know why something happened, how borrowed and personal funds were allocated, and how the deductible split changed. You enter events, edit events, and delete events. They're the source of truth.

A statement transaction is what your bank or brokerage would show for the same activity — a line item on a statement. It describes the observable money or asset movement in a specific account, without any allocation logic or tax treatment. You don't create or edit statement transactions directly; they're generated automatically from your events.

Think of it this way: you tell the app “I borrowed $10,000 and transferred it to my brokerage.” That's one event. The Statements view shows it as two transactions — a withdrawal on your credit account and a deposit in your brokerage — exactly as it would appear on your real statements.

Why statements exist

The Statements view is there for reconciliation. When your bank sends you a monthly statement, you can compare it line-by-line with what the app shows. If something doesn't match, you know an event is missing or has the wrong amount.

Statements also provide a familiar format. If you're used to reading bank and brokerage statements, the Statements view shows your activity in the same shape — dates, descriptions, amounts, symbols — without the deductibility logic that makes the Events view more complex.

How events map to statements

Most events produce one statement transaction. A few produce two — one per account affected. The mapping is deterministic: the same events always produce the same statement rows.

Navigating between views

Every statement transaction links back to the event that produced it. Click the event link on any statement row to jump to that event's detail view, where you can see the full allocation logic and explanation.

Going the other direction, clicking an event in the Events view can filter the Statements view to show only the transactions generated by that event — useful for understanding exactly what a single action looks like on your statements.

Related topics

• How balances are tracked — the event-driven model behind both views
• Setting up your first tracking — the basic event cycle