> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/common-workflows/reviewing-transactions.md).
# Reviewing Transactions
Sign off on transactions field by field, see who reviewed what and when, and filter to what still needs eyes.
Review is how your team signs off on transactions, the way you'd work a traditional bank feed: validate the numbers, validate the coding, and make sure nothing slips by.
Review works at the field level. Instead of marking a whole transaction as done, you sign off on the individual fields you checked, and Kick records who reviewed each one and when.
***
### Fields You Can Review
* Category (shown only in workspaces that use categories)
* Counterparty
* Class
* Entity
* Cash ledger
* Accrual ledger (the transaction's Review section shows it only when the entity has an accrual ledger)
* Memo (shown only when the transaction has a memo)
Reviewing a field never changes its value. It records that a person checked it.
A few fields can't be marked reviewed until they're ready: an empty Category, Entity, or Memo, a category still set to Uncategorized, and ledger fields on [personal transactions](/common-workflows/personal-to-business.md). Kick skips these automatically in bulk actions.
***
### Mark a Field as Reviewed
On a single transaction:
1. Open the transaction from the Transactions tab
2. Open the **Review** section
3. Click **Mark reviewed** next to each field you checked
To undo a review, click **Undo review** on that field.
In bulk:
1. Select the transactions
2. Open the actions menu (or press **⌘K**) and choose **Mark reviewed**
3. Pick a field, or **All fields** to sign off on everything at once
**Mark unreviewed** works the same way in reverse.
**The Review column.** Add the **Review** column from the Views button on the toolbar. Each row shows a check when at least one field has been reviewed and a dotted icon when none have. Click it to open the transaction with the Review section already expanded, and sort the column to push unreviewed rows to the top.
Each reviewed field shows the reviewers' avatars. Hover one to see who signed off, with the date and time. Reviews also appear in the transaction's [activity log](/working-with-your-team/activity.md).
***
### More Than One Reviewer
Multiple team members can review the same field. Each sign-off is stored separately with the person and the date, so a preparer and a reviewer (or an entire team) can each leave their mark.
***
### What Happens When a Reviewed Field Changes
If a field's value changes after it was reviewed, like a category swap or a recategorization that moves the transaction to a different GL account, Kick clears all reviews on that field. Only the changed field is affected; sign-offs on other fields stay, so a review always refers to the value currently on the transaction.
***
### Filter by Review Status
On the Transactions tab, open **Filter** → **Review**. The filter has three sections:
* **Reviewed**: find transactions where fields have been reviewed. Choose **Any field** (at least one of the selected fields is reviewed) or **Every field** (all of them are), then check the fields you care about
* **Unreviewed**: the same, in reverse. **Any field** means at least one selected field still needs review; **Every field** means none of them have been touched
* **Reviewers**: filter by who signed off. Choose **Any member**, **All members**, or **None of the members**, then check specific teammates
***
### Common Review Workflows
You decide how much gets human eyes. Some teams review everything; others only review what matters and let the AI handle the rest. Once a combination works for you, save it as a view so it's one click from the Transactions tab next time.
* **Review everything.** Filter **Unreviewed**, work the list top to bottom like a bank feed, and mark fields reviewed as you go
* **Review what's material.** Combine **Unreviewed** with an amount filter so only transactions above your threshold land in the queue
* **Watch specific accounts.** Combine **Unreviewed** with the account filter to keep eyes on the accounts you care about most
* **Check the matches.** Combine the Review or Unreviewed filter with the Match filter to confirm matched transactions were paired correctly
* **See what a teammate has covered.** Filter **Reviewers** by a specific person to see what they've signed off on, or what they haven't gotten to
***
### FAQs
Does reviewing a field change its value?
No. Review is a sign-off. The value only changes if someone edits it.
Can more than one person review the same field?
Yes. Each review is stored with the person and the timestamp.
What happens if a field is edited after it was reviewed?
The reviews on that field are cleared automatically for all reviewers. Reviews on the transaction's other fields are not affected.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.kick.co/common-workflows/reviewing-transactions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.