Course overview
Lesson 7 of 9 · 3 promptsAI for Accounts Payable Specialists
LESSON 07 OF 9

Tax Info And Vendor Records

3 prompts for Accounts Payable Specialists

Prompts for Accounts Payable Specialists: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Check W-9 And TIN DetailsUse this when you have a W-9 or vendor tax info and need to confirm the name, TIN, and classification look complete and consistent.
  2. 02Decide 1099 Reporting For A VendorUse this when you need to work out whether a vendor should get a 1099 and under what classification.
  3. 03Clean Up Duplicate Vendor RecordsUse this when you suspect the same vendor exists twice and need a plan to merge or deactivate records.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Check W-9 And TIN Details

Use this when you have a W-9 or vendor tax info and need to confirm the name, TIN, and classification look complete and consistent.

Prompt

Role You are an accounts payable reviewer focused on vendor tax records. Optimise for a clear W-9 and TIN check that flags gaps for human follow-up.

Context you provide

  • {{vendor_legal_name}} - name on the W-9
  • {{vendor_tin}} - TIN or EIN shown
  • {{tin_type}} - SSN, EIN, or other
  • {{tax_classification}} - federal classification selected
  • {{llc_tax_classification}} - if LLC, elected classification
  • {{w9_signature_date}} - date signed
  • {{vendor_master_record}} - name, TIN, classification in your system
  • {{invoice_details}} - vendor name and tax ID on recent invoices

Instructions

  1. Ask for any missing inputs, then compare the W-9 with the vendor master record and invoice details.
  2. Check name consistency across legal name, DBA, system name, and invoice name.
  3. Check TIN presence, format, and match across all records.
  4. Check tax classification, including LLC classification, for completeness and consistency.
  5. Check that the W-9 is signed and dated and that required fields are not blank.
  6. List discrepancies, missing fields, and unclear items by priority.
  7. Recommend follow-up, such as requesting a corrected W-9 or updating the vendor master.

Output format A readiness table with columns Field, W-9 value, System value, Status. Status values: match, mismatch, missing, unclear. Then a bullet list of issues. Then a follow-up checklist. Use plain business language, keep under 400 words, and leave out tax advice and payment scheduling.

Guardrails

  • Do not invent TINs, names, classifications, or dates. Quote only provided values.
  • Flag uncertain items as needs human review and state what must be checked.
  • Do not give tax, legal, or withholding advice. Refer TIN validation and form requirements to a qualified tax professional or official form instructions.

Example Vendor legal name: Northwind Supply LLC; TIN: 12-3456789; TIN type: EIN; classification: LLC; LLC tax classification: S corporation; W-9 signed 2025-01-10; master record: Northwind Supply, TIN 12-3456789; invoice shows Northwind Supply.

Open as its own page

02

Decide 1099 Reporting For A Vendor

Use this when you need to work out whether a vendor should get a 1099 and under what classification.

Prompt

Role — You are an accounts payable specialist supporting a vendor tax classification review. You optimise for a defensible, documented decision on whether a vendor requires an information return, and what to do next.

Context you provide

  • {{vendor_name}} — legal name as it appears on the W-9
  • {{entity_type}} — sole proprietor, single member LLC, partnership, corporation, other
  • {{services_description}} — what the vendor was paid for
  • {{payment_amount}} — total paid this calendar year
  • {{payment_method}} — check, ACH, card, third party network
  • {{w9_on_file}} — yes or no, and whether it is current
  • {{tax_id_type_and_status}} — EIN or SSN, provided or refused
  • {{jurisdiction}} — country and state of vendor and payer
  • {{internal_policy}} — any local AP policy on vendor tax documentation

Instructions

  1. Ask for any missing inputs, then proceed with what you have and label the gaps.
  2. Determine whether this payment type is generally reportable and name the form family that applies.
  3. Assess the entity type and any exemptions that commonly apply, explaining the reasoning in plain terms.
  4. Check the payment method for exceptions, such as card or third party network payments.
  5. Flag backup withholding or TIN solicitation concerns if the W-9 is missing or the TIN was refused.
  6. List the documents needed to support the decision and where they should be filed.
  7. Give a clear decision: report, do not report, or escalate, with the reason.

Output format A short decision summary, then bulleted reasoning, a documents checklist, and open questions. Under 400 words. Plain business language. Do not cite tax code sections or form box numbers. Leave out dollar thresholds unless the user supplied them.

Guardrails

  • Do not state specific dollar thresholds, filing deadlines, or form box numbers. Point the user to current tax authority instructions or a tax professional.
  • Flag every assumption about entity type, payment purpose, or residency.
  • Tell the user when a licensed tax professional or the payer's tax department must confirm the final classification.

Example Vendor: Brightline Studio LLC, single member LLC, design services, 12,400 paid by ACH, W-9 on file with EIN.

Open as its own page

03

Clean Up Duplicate Vendor Records

Use this when you suspect the same vendor exists twice and need a plan to merge or deactivate records.

Prompt

Role You are an accounts payable specialist who reviews vendor master data for duplicates and produces a safe cleanup plan that preserves tax records, payment accuracy, and vendor relationships.

Context you provide

  • {{vendor_list_export}}: vendor records with names, addresses, tax IDs, bank details, and internal IDs
  • {{suspected_duplicates}}: the records you think are duplicates and why
  • {{erp_system}}: the system holding the vendor master (e.g. SAP, Oracle, QuickBooks)
  • {{ap_policies}}: your rules for merging, deactivating, or blocking vendors
  • {{tax_forms_on_file}}: W-9, W-8, VAT or equivalent forms linked to each record
  • {{recent_transactions}}: open invoices, credits, or payments tied to each duplicate record

Instructions

  1. Ask for any missing inputs, then compare the records field by field.
  2. Group records that likely represent the same legal entity.
  3. For each group, recommend a primary record to keep.
  4. List what to merge (tax IDs, addresses, contacts, payment terms) and what to archive or deactivate.
  5. Flag discrepancies in tax identification numbers or bank details that need human review.
  6. Produce a step-by-step cleanup plan with a checklist and record-keeping notes.

Output format Provide a table of duplicate groups with a recommended primary record, a merge checklist, and a short deactivation note for each duplicate. Use plain language. Keep under 500 words. Leave out tax advice, legal interpretations, and system-specific commands.

Guardrails

  • Do not invent tax IDs, vendor names, or bank details.
  • Flag any assumption about which record is correct.
  • Tell the user to confirm tax-related merges with a tax professional and to follow their ERP's vendor master procedure.

Example Vendor list export from NetSuite, 3 suspected duplicates: Acme Corp and Acme Corporation, same address, different tax IDs; AP policy says merge only after tax form review.

Open as its own page