> ## Documentation Index
> Fetch the complete documentation index at: https://docs.geldee.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Correct transactions

> A controlled workflow for selected category corrections, using proposals or explicitly authorized editing.

## Ask for a proposal first

```text theme={null}
Find the transactions I identify and suggest the category corrections.
Show the exact selected payments and proposed categories. Submit a proposal
only if you have that permission, then let me approve it in Geldee.
Do not create a future merchant rule.
```

## Agent workflow

1. Check identity, permission and account selection.
2. Read the exact date range and every page. Resolve category IDs from the current catalog.
3. Freeze the exact eligible payment IDs, with at most 100 per atomic batch. Do not turn a date range into a changing write target.
4. Use `propose_change` when proposal permission is granted. Tell the owner to review the pending result in Geldee.
5. Only use direct editing when explicitly authorized for transactions and requested by the user. Follow the exact preview/apply flow.
6. Inspect the receipt, reread the records and check canonical totals before reporting completion.

## Keep different actions separate

Changing selected payments does not create a future keyword rule. Saving a rule needs its own permission. Transfers, split payments, month allocations and linked bill records can require their dedicated flows.

A read-only connection cannot submit the proposal or inspect a direct-edit preview. It can explain the permitted records and ask the owner to make the change.

See [proposals and editing](https://docs.geldee.com/ai/changes.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.