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

# Find who needs a 1099

> Your AI lists the vendors a QuickBooks Online client paid enough to need a 1099, and which ones are not marked for 1099 or have no tax ID on file. It also advises, from the expense accounts each vendor was paid through, which ones look like they need one. After you say yes, LedgerSync marks them for 1099 in QuickBooks.

# Find who needs a 1099

Ask your AI. It lists the vendors who need a 1099, and after your yes, LedgerSync marks them for 1099 in the client's QuickBooks.

**For QuickBooks Online clients.** Not set up yet? Go to [Start here](https://docs.ledgersyncappv2.com/ai/start-here.md). Added it a while ago? Do
[After a LedgerSync update](https://docs.ledgersyncappv2.com/ai/troubleshooting.md#after-an-update) once.

## Start

Step 1 of 5

Start a new chat

In Claude, ChatGPT or Grok. In ChatGPT, also type **@** and pick **LedgerSync**.

Step 2 of 5

Ask the AI

Type *"Which vendors need a 1099 for Acme?"*, with your client's name, and press **Enter**.

Step 3 of 5

Check the list

The AI lists the vendors paid enough to need a 1099, highest first. It says which ones are not marked for 1099 in
QuickBooks and which have no tax ID on file. It also says, from the expense accounts each vendor was paid through,
whether it looks like it needs a 1099, and why.

Step 4 of 5

Answer its questions

When the accounts don't settle it, the AI asks you about the vendor, one at a time. For example: were the repairs
someone's work, or parts bought on their own? You decide.

Step 5 of 5

Say yes to the preview

Ask it to mark the vendors you checked. It shows each one before and after. Say yes, and allow it each time Claude or
ChatGPT asks. Nothing changes before that.

**Only some accounts count for 1099?** Tell the AI which ones, for example Contract Labor and Legal Fees. It counts
only those, as QuickBooks' own 1099 setup does. Nothing is saved, so tell it again next time.

**A read-only connection cannot mark vendors.** It still shows the list: turn on 1099 tracking in QuickBooks itself
instead.

**Using Grok?** Tell it to wait for your yes before it marks anything.

**Tax IDs are never shown.** The list only says whether one is on file. Don't type a tax ID in the chat.

## More details

> [accordion] What happens after you ask
>
> 1. The AI finds the client. LedgerSync reads the year's payments from the client's QuickBooks. For a client with a
>    lot of activity, the AI may say LedgerSync is still reading, and asks again about 30 seconds later.
> 2. The AI shows you the vendors paid at or over the 1099 amount for the year: $2,000 for 2026 payments, $600 for
>    2025\. For each vendor: how much counts, whether it is marked for 1099 in QuickBooks, and whether a tax ID and an
>    email are on file. It also gives its advice, from the expense accounts the vendor's payments were booked to: it
>    points to a 1099, points away from one, or asks you, with the reason.
> 3. It asks you about the vendors the accounts don't settle, one at a time, and about the vendors marked for 1099
>    whose accounts point away. You decide.
> 4. Want only some accounts to count, as in QuickBooks' own 1099 setup? Tell the AI which ones. It lists the vendors
>    again, counting only those accounts and the accounts under them, and tells you how much it left out and how many
>    vendors dropped off the list. Nothing is saved: tell it again next time.
> 5. It goes through the vendors not marked for 1099, and the ones with no tax ID on file, with you. A vendor with no
>    tax ID on file needs a W-9 before you file.
> 6. You pick the vendors to mark, or to unmark. The AI shows you a preview: each vendor's 1099 setting before and
>    after, and the vendors LedgerSync would leave as they are, with the reason. Nothing has changed yet.
> 7. You say yes. Claude and ChatGPT also ask you to allow it: allow it if the preview looked right. LedgerSync turns
>    on 1099 tracking for each vendor in QuickBooks and changes nothing else on the vendor. A minute or so later, the AI
>    tells you which vendors were marked and which were left as they were, and why.
> 8. Changed your mind? Ask the AI to undo it. It shows which vendors would go back, and puts them back after your yes.
>    A vendor someone changed in QuickBooks since is left as it is.
> 9. At the end, the AI tells you what the list does not cover, and offers a dashboard of the list or the same check
>    for your other clients.
>
> **Which payments count?** Checks, cash and bank payments to a vendor, and bill payments, by the date they were paid.
> A bill counts when it is paid. Card payments, and payments through PayPal,
> Venmo, Square, Stripe or Cash App, are left out: the card company or the app reports them on a 1099-K.
>
> **How the advice works.** LedgerSync looks at the expense accounts each payment was booked to, and for a bill
> payment, the accounts on the bills it paid. It reads each account's name first, then the type QuickBooks gives it.
> Services and legal fees point to a 1099-NEC, and rent to a 1099-MISC. Goods, travel, utilities, phone, freight,
> insurance, taxes, wages and bank fees point away. Repairs, advertising and catch-all accounts such as Uncategorized
> Expense get a question, and so do supplies on a contractor's bill with the work. Each form needs $2,000 on its own
>         for 2026 payments, so $1,500 of labor and \$1,000 of rent to one vendor also get a question. It is advice: you decide.
>
> **Corporations.** Most corporations need no 1099, but lawyers and medical providers do. QuickBooks cannot tell which
> vendors are corporations, so the list keeps them. Check each vendor's W-9. The advice counts legal fees even when
> the law firm is a corporation.
>
> **What changes in QuickBooks.** Only each vendor's 1099 tracking. Nothing else on the vendor changes, and LedgerSync
> never shows or changes a tax ID. LedgerSync keeps who said yes, and in which AI app.

> [accordion] What it does not cover
>
> * Royalties.
> * Gross proceeds paid to attorneys.
> * Medical and health care payments.
> * Which 1099 form and box each payment goes in. The AI only suggests a form from each account's name, and your
>   client's 1099 setup in QuickBooks may map an account differently.
> * Payments entered as journal entries.
> * Asking vendors for a W-9.
> * Filing. File the 1099s through your usual 1099 service. For 2026 payments, 1099-NEC forms are due February 1, 2027.
> * Clients that use another accounting app, such as QuickBooks Desktop or Zoho Books.

> [accordion] Before you start
>
> * **LedgerSync is in your AI app:** Claude, ChatGPT or Grok. Not yet? Go to [Start here](https://docs.ledgersyncappv2.com/ai/start-here.md). Added it
>   a while ago? Do [After a LedgerSync update](https://docs.ledgersyncappv2.com/ai/troubleshooting.md#after-an-update) once, so your AI gets the 1099
>   tools.
> * **The client is connected to QuickBooks in LedgerSync**, the same connection you use to sync transactions from
>   the LedgerSync app.
> * **The client uses QuickBooks Online.**

> [accordion] Your client's data
>
> **Your client's vendors go through your AI account.** The AI app reads the client's vendors and what each was paid,
> and keeps the chat under your AI account's settings. Check that account's data settings before you start. Tax IDs
> never leave LedgerSync: the list only says whether one is on file.

> [accordion] Optional: the full instructions to paste
>
> You don't need these: LedgerSync already gives your AI the same steps. If your AI does not follow them, give it
> these instructions.
>
> Instructions for your AI
>
> \`Find who needs a 1099 for a LedgerSync client.
>
> 1. Find the client with ledgersync\_find\_clients in this chat and pass its client\_name with its client\_id to every tool. Never reuse a client id from an earlier chat or from memory: LedgerSync refuses a client\_id given with another client's name. The 1099 list works for QuickBooks Online clients.
>
> 2. Call ledgersync\_get\_1099\_summary. It lists the vendors the client paid at or over the 1099-NEC threshold in the tax year (2,000.00 for 2026 payments, 600.00 for 2025 payments), leaving out card and payment app payments, which go on a 1099-K. If it answers status running, call it again with the same arguments in about 30 seconds.
>
> 3. Show the user the list, highest amounts first: each vendor's reportable amount, whether it is marked for 1099 in QuickBooks, whether a tax ID and an email are on file, the evidence, and the advice with its advice\_reason. The advice comes from the expense accounts the vendor's payments were booked to: points\_to\_1099, points\_away, or ask when the accounts do not settle it. It is advice: the user decides. The list never shows a tax ID; never ask the user to type one here.
>
> 4. First ask the user about the vendors whose advice is ask, one at a time, with each one's advice\_reason: for example, whether repairs were someone's work or parts bought on their own. Then point out the vendors marked for 1099 whose advice is points\_away, and ask whether they should stay marked.
>
> 5. If the user wants only some accounts to count, the way QuickBooks' own 1099 setup does, call ledgersync\_get\_1099\_summary again with count\_only\_account\_ids: the account ids from its expense\_accounts, or from ledgersync\_list\_quickbooks\_categories for any other account. Vendors paid only through other accounts drop off the list: tell the user how much the choice left out and how many vendors dropped off. Nothing is saved, so ask again next time.
>
> 6. With the user, go through the vendors not marked for 1099 (the ones whose advice is points\_to\_1099 first) and the ones with no tax ID on file. A vendor with no tax ID on file needs a W-9 before filing. Corporations usually need no 1099 (lawyers and medical providers do), and QuickBooks cannot tell them apart: the user decides from each vendor's W-9.
>
> 7. For the vendors the user wants marked for 1099, or unmarked, call ledgersync\_preview\_ledger\_changes. Show each vendor's 1099 flag before and after, and the vendors it leaves as they are, with the reason. Nothing has changed yet. If the preview says marking is not open to this firm, or that this connection is read-only, tell the user to turn on 1099 tracking for those vendors in QuickBooks itself.
>
> 8. Only after the user says yes, call ledgersync\_apply\_ledger\_changes with the preview's confirmation\_id and the same client\_id and client\_name. Then follow ledgersync\_get\_ledger\_changes\_status until it finishes, and tell the user which vendors were changed and which were left as they were, and why.
>
> 9. If the user changes their mind, call ledgersync\_undo\_ledger\_changes: the first call only shows which flags would go back. Only after the user says yes, call it again with the undo\_id.
>
> 10. Before you finish, tell the user what the list does not cover: royalties, gross proceeds paid to attorneys, medical and health care payments, and which 1099 form and box each payment goes in. The form shown for an account is suggested from its name, and the client's own 1099 setup in QuickBooks may map that account differently. For 2026 payments, 1099-NEC forms are due February 1, 2027; the firm files them through its own 1099 service.
>
> 11. End by offering a dashboard of the list or of the advice by account, and the same check on the firm's other clients.\`
>
> 1) Click **Copy** above.
> 2) In Claude, ChatGPT or Grok, start a new chat.
> 3) Click the message box and press **Ctrl+V** (**Command+V** on a Mac).
> 4) At the end, type the client's name. For example: *Acme*. Then press **Enter**.
>
> **Using Claude Code?** The instructions are also a LedgerSync command there. Type **/**, pick **form\_1099\_season**
> (it says **(MCP)** next to it) and press **Enter**. Then tell it the client.

## If something goes wrong

> [accordion] Most common messages
>
> | The AI says | Do this |
> | - | - |
> | It doesn't know how to do this | Your AI may still have an older copy of LedgerSync's tools. Do [After a LedgerSync update](https://docs.ledgersyncappv2.com/ai/troubleshooting.md#after-an-update), then start a new chat. |
> | **QuickBooks is not connected for this client in LedgerSync.** | In the LedgerSync app, click **Rules Engine**, then **QuickBooks**. In the menu on the left, click **Manage Connections**. Find the client and click **Authorize**, then sign in to the client's QuickBooks. Then ask the AI again. |
> | **The client's QuickBooks connection in LedgerSync stopped working.** | Open **Manage Connections** the same way. At the top, next to the client's name, click **Reconnect** and sign in to QuickBooks again. Then ask the AI again. |
> | LedgerSync is still reading the client's payments | Wait. The AI asks again about 30 seconds later. |
> | **Marking vendors for 1099 from an AI app is open to a few test firms first; it opens to everyone soon.** | Turn on 1099 tracking for those vendors in QuickBooks itself for now. The list still works. |
> | A vendor is inactive in QuickBooks | QuickBooks refuses any change to an inactive vendor. Make it active in QuickBooks, then ask the AI to preview again. |
> | A vendor changed in QuickBooks since the preview | LedgerSync left it as it is. Ask the AI to preview it again. |
> | **LedgerSync has no default 1099 threshold for** a year | Tell the AI the amount to use for that year, for example 600. |
> | **None of these accounts is in the client's QuickBooks**, or **the client's QuickBooks has no account** you chose | Ask the AI to show the client's accounts, then tell it again which ones count. When only some are missing, the AI still shows the list for the others. |

> [accordion] More messages: preview expired, change not confirmed, LedgerSync busy, read-only, limits, undo
>
> | The AI says | Do this |
> | - | - |
> | **This confirmation is unknown or expired. Preview the changes again.** | A preview works for 30 minutes. Ask the AI to preview again. |
> | LedgerSync **did not confirm** the change, so it may or may not be made | Don't ask it to mark again. Wait a minute, then ask it to check the status. |
> | **These changes are already being applied.** | Wait a minute, then ask the AI for the status. |
> | **Other changes are being applied; try again in a minute.** | Nothing was changed. Wait a minute, then ask the AI to mark them again with the same preview. A preview works for 30 minutes. |
> | **This connection is read-only or lacks permission for this action.** | This connection can read but not change anything. Turn on 1099 tracking in QuickBooks itself, or email [support@ledgersync.com](mailto:support@ledgersync.com). |
> | This connection has used a tool too many times this hour or this day | Each AI app you connect can preview 60 times an hour, mark 30 times a day and undo 10 times a day. Try again next hour or tomorrow, as the AI says, or do it in QuickBooks itself. |
> | It cannot find the client | Ask "Find my client ..." first. Not the firm owner or an administrator? You see only the clients assigned to you in LedgerSync. |
> | Some vendors could not be put back | Ask the AI to undo again: it tries those vendors again. |
> | The client is now connected to a different QuickBooks company | LedgerSync can undo only while the client is connected to the QuickBooks company the changes were made in. |

Anything else? See [Troubleshooting](https://docs.ledgersyncappv2.com/ai/troubleshooting.md).

> [accordion] For developers: the 5 tools and what they change
>
> | Tool | What it does | Changes data |
> | - | - | - |
> | `ledgersync_get_1099_summary` | The vendors a QuickBooks client paid at or over the 1099 threshold in a tax year, each with its QuickBooks 1099 flag, whether a tax ID and an email are on file (never the tax ID itself), a suggested next step, and advice from the expense accounts its payments were booked to; `count_only_account_ids` counts only the accounts the accountant chooses | No |
> | `ledgersync_preview_ledger_changes` | Checks marking up to 100 of the client's vendors for 1099, or unmarking them, and shows each one's 1099 flag before and after | No |
> | `ledgersync_apply_ledger_changes` | Marks or unmarks the previewed vendors for 1099 in the client's QuickBooks, in the background | Yes |
> | `ledgersync_get_ledger_changes_status` | How each vendor's change went, and after an undo how the undo went | No |
> | `ledgersync_undo_ledger_changes` | Shows which flags would go back; after a yes, puts them back | Yes |
>
> * The instructions above are also an MCP prompt, `form_1099_season` ("Find who needs a 1099"), with optional
>   `client` and `tax_year` arguments. Claude Code lists it as a command.
> * Every ready answer of `ledgersync_get_1099_summary` ends its `next_step` with what the list does not cover,
>   before its offers, so an AI that never sees the prompt still says it.
> * Each vendor carries `advice` (`points_to_1099`, `points_away` or `ask`) and an `advice_reason`, and the first
>   page lists the accounts behind them in `expense_accounts`. The `next_step` asks about the `ask` vendors first,
>   then, when some vendors are in question or point away, offers `count_only_account_ids`. Nothing about the
>   choice is saved.
> * The list and the status need `read:accounting`; the preview, the apply and the undo need `write:accounting`.
>   A read-only connection can read the list but cannot mark vendors.
> * Marking is open to every firm. On the sandbox connector it is still limited to test firms: for any other firm
>   there, the preview and the apply answer `access_not_active`.
> * Each `vendor_id` in the 1099 list is sealed to its client: the id, a dot and 8 more characters. The preview takes
>   it only as the list gave it for that client: one from another client's list, or one with no seal (as
>   LedgerSync gave ids before), is refused with `invalid_request`, and its `next_step` tells the AI to list this client's vendors again. The apply
>   takes the preview's
>   `confirmation_id` with the same `client_id` and `client_name` the preview named.
> * On the sandbox connector, marking really changes the Intuit sandbox QuickBooks company the client is connected
>   to. There is no dry run.
> * See [For developers](https://docs.ledgersyncappv2.com/ai/developers.md) for every field.

> [accordion] For developers: limits
>
> * One preview takes up to 100 vendors.
> * Each connected AI app can make 60 previews an hour, 30 applies a day and 10 undos a day. An apply or an undo
>   that never reaches LedgerSync is not counted.
> * A preview's confirmation works for 30 minutes, and an undo's `undo_id` for 15 minutes.
> * One set of changes runs at a time for each client.

Stuck? [Book a call with
our team](https://ledgersync.com/book-a-demo) and we'll help you, or email
[support@ledgersync.com](mailto:support@ledgersync.com) with the step and what the screen says.
Never send passwords or card numbers.


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