Ledger review
Correct the meaning without rewriting the source.
Position preserves the bank row. Reviewed category, semantic type or links change analysis without deleting the evidence.
Current app path
Ledger → transactions need review → transactionTransaction review, splits, semantic treatment and bounded local learned rules are available through the external beta.Required
- Amount, date, currency and direction
- A valid category and type when changed
Optional
- Merchant
- Purchase description
- Notes
- Recurrence
- Category split
What can block completion
- An invalid required field
- An unresolved conflict
- Split parts that do not equal the original amount
- Local financial data
- Edits, source links and learned rules are stored in the local ledger.
- Privacy or AI boundary
- Manual review is local. Suggest can use AI; a suggestion remains unsaved until you apply and save it.
- If it does not work
- Cancel preserves the transaction. Reopen source evidence, correct the required field or split total, then choose Save transaction.
01
Review a classification
- Open Ledger.
- Select the transactions need review row, or open the transaction.
- Read the warning and Statement evidence.
- Correct category, type, direction or split, then Save transaction.

03
Learned local rules
A saved correction can become a bounded local rule. Explicit corrections take precedence without overwriting stronger future evidence.
04
Fictional example
The approved frame shows low-confidence classifications remaining visible and actionable until review.

