> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/company/vendor-1099s/review-transactions.md).
# Review 1099 transactions and mark a vendor ready for filing
Check an eligible vendor's invoice transactions, split each amount across the 1099 boxes, and mark the vendor ready for filing.
Use this page to decide which of an eligible vendor's transactions go on its 1099, and in which box, before you mark the vendor ready for filing. Open it with **Review Transactions** on the **1099 Eligible** or **Ready For Filing** tab of **Company > Vendor 1099s**. Owners and Super Admins can use it.
{% hint style="info" %}
**Vendor 1099s** is under **Company** in the sidebar. For the whole year-end workflow, see [Prepare vendor 1099s](/company/vendor-1099s.md).
{% endhint %}
## What the page shows
At the top is the vendor's name, followed by its business name in parentheses when that's different. A reminder under it says only invoice transactions count for 1099s.
Above the table are three running totals: **1099-MISC Box 1 Eligible Total**, **1099-MISC Box 3 Eligible Total** and **1099-NEC Box 1 Eligible Total**. Each adds up that box's amounts on every row ticked in **1099 Eligible?**, and updates as you edit.
The table lists the vendor's invoices from every production in your company that were issued or added in the current 1099 year, or whose payment was sent or arrived in it, most recently added first. The columns are:
* **1099 Eligible?**: whether the transaction counts toward the 1099. US dollar rows start ticked.
* **Production**: the production the transaction is on.
* **Transaction Amount**: the invoice total.
* **1099-MISC Box 1 Eligible**, **1099-MISC Box 3 Eligible** and **1099-NEC Box 1 Eligible**: how much of the amount is reported in each box.
* **1099 Notes**: your notes for the 1099.
* **Categories**: the budget categories the invoice is coded to. If the production uses a chart of accounts, it shows the debit and credit accounts instead.
* **Notes From Transaction**: the invoice's own notes.
* **Issue Date**, **Payment Date** (when the payment was sent) and **Created At**.
* **File**: a file button, when the transaction has a file.
## Leave a transaction out
1. On the transaction's row, untick the box in the **1099 Eligible?** column.
The change saves right away. The row's box amounts go blank and can't be edited, and the row drops out of the totals. To count it again, tick the box. The amounts saved on the row come back.
Only transactions in US dollars can count. For any other transaction, the box is unticked and can't be changed, and pointing at it shows "Only USD transactions are eligible for 1099s".
## Split an amount across the 1099 boxes
Until you change a row, RollCredits puts the whole **Transaction Amount** in the box that matches the vendor's **Default 1099 Location**, and $0 in the other two. If the vendor's default is **Ineligible For 1099**, all three start at $0.
1. On a ticked row, select the **1099-MISC Box 1 Eligible**, **1099-MISC Box 3 Eligible** or **1099-NEC Box 1 Eligible** cell.
2. Type the amount for that box.
3. Press Enter or select another cell. The amount saves and the total at the top updates.
4. Repeat for the other boxes on the row.
Clearing a cell saves $0. RollCredits doesn't check that a row's three boxes add up to its **Transaction Amount**, so compare them yourself.
{% hint style="warning" %}
The first time you change a row, any box you haven't typed an amount into is saved as $0. This happens even when you only add a 1099 note, or untick and tick the row again. If a suggested amount drops to $0, type it in again.
{% endhint %}
## Add 1099 notes
If a transaction needs more explanation for its 1099, add it in **1099 Notes**.
1. Select the row's **1099 Notes** cell.
2. Type your note.
3. Press Enter or select another cell to save it.
You can add notes on every row, including rows that don't count.
## Check a transaction's file or details
To see a transaction's file, select the file button in its **File** column. The file opens in a panel beside the table. Select the **X** at the top of the panel to close it.
To open the transaction itself, select the eye button at the end of its row. The Transactions page opens in a new tab, on the transaction's production. If that's the production you have open, the transaction opens in its side panel too. Otherwise, find it in the table there. See [Review and edit a transaction](/transactions/transactions/edit-a-transaction.md).
## Mark the vendor ready for filing
1. Check the totals and each row's box amounts.
2. Select **Ready For Filing**.
RollCredits says "Vendor marked as ready for filing. Navigating back to the vendors list...", moves the vendor to the **Ready For Filing** tab and takes you back to the **1099 Eligible** tab of **Vendor 1099s**. Mark every eligible vendor ready for filing by the date shown on **Vendor 1099s**.
Once a vendor is ready for filing, its page no longer shows the **Ready For Filing** button. You can still open it with **Review Transactions** on the **Ready For Filing** tab and edit it the same way.
## Go back to Vendor 1099s
Select **Back to Vendor 1099s** at the top of the page. It opens the **Ready For Filing** tab if the vendor is ready for filing, and the **1099 Eligible** tab otherwise.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledge.rollcredits.io/company/vendor-1099s/review-transactions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
