> 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/preview-transactions.md).
# Decide whether a vendor gets a 1099
Look through a vendor's invoice transactions for the 1099 year, then mark the vendor eligible or ineligible for a 1099.
Check a vendor's transactions here before you decide whether they get a 1099. To open this page, select **See Transactions** in the vendor's row on the **Unmarked** tab of **Company > Vendor 1099s**. Owners and Super Admins can use it.
{% hint style="info" %}
**Vendor 1099s** is under **Company** in the sidebar.
{% endhint %}
## What the page shows
The vendor's name is at the top, with a reminder that only invoice transactions count for 1099s. The list shows the vendor's invoices from every production in your company that were issued, added or paid in the current 1099 year, most recently added first.
* **Production**: the production the invoice is on.
* **Transaction Amount**: the invoice total.
* **Categories**: the budget categories it's coded to, or its debit and credit accounts if the production uses a chart of accounts.
* **Notes From Transaction**: the invoice's notes.
* **Issue Date**, **Payment Date** and **Created At**: when the invoice was issued, when its payment was sent, and when it was added to RollCredits.
* **File**: a file button, when the invoice has a file.
The list is read-only. Once the vendor is eligible, you choose which amounts count on its review page. See [Review 1099 transactions and mark a vendor ready for filing](/company/vendor-1099s/review-transactions.md).
## View a transaction's file
1. Select the file button in the row's **File** column. The file opens in a panel beside the list. Its **...** menu has **Download** and, for a PDF or image, **Print**.
2. Select the **X** at the top of the panel to close it.
## Open a transaction in Transactions
1. Select the eye button at the end of the row.
The transaction opens on the **Transactions** page in a new browser tab.
{% hint style="info" %}
If the transaction is on another production, the new tab switches to that production's **Transactions** page without opening the transaction. Find it in the table there.
{% endhint %}
## Mark the vendor eligible
1. Select **Mark Eligible**. The **Review Vendor Information** window opens.
2. Check and complete the vendor's details. For each field, see [Prepare vendor 1099s](/company/vendor-1099s.md).
3. Select **Confirm and Mark Eligible**.
You're taken back to the **Unmarked** tab, and the vendor moves to the **1099 Eligible** tab. Select **Cancel** to close the window without marking the vendor.
## Mark the vendor ineligible
1. Select **Mark Ineligible**.
The vendor is marked ineligible right away, with no confirmation step. You're taken back to the **Unmarked** tab, and the vendor moves to the **1099 Ineligible** tab. To change your mind, select **Mark Eligible** in its row there.
## Go back without deciding
Select **Back to Vendor 1099s** at the top of the page. The vendor stays on the **Unmarked** tab.
---
# 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/preview-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.
