--- oa_review_kit: v1 guide_slug: idaho-sales-tax guide_version: idaho-sales-tax@2026-04-13T17:57:01.511Z archetype: vat_gst --- # Review kit: Idaho Sales Tax Thank you for reviewing this Guide. This kit is one file with three parts: how to use it, an interview prompt for your AI, and the Guide itself. ## How to use this kit (3 steps, about 15 minutes) 1. Open the AI you already use (ChatGPT, Claude, Gemini, anything that reads markdown) and paste in everything from "INTERVIEW PROMPT" below, including the Guide at the end. 2. Your AI interviews you like a colleague, one question at a time. Just talk: war stories, walk-throughs, the mistakes you catch. No writing required. 3. Your AI writes your answers up as a single markdown file. Hand it back at openaccountants.com/skills/idaho-sales-tax/handback (also linked from the Guide page: "Hand back your file"). What you added is published under your name and credential. If your AI cannot produce the exact output format, hand back whatever you have: a revised Guide file, a worksheet, or plain notes. We take those too, and a person reviews them by hand. The format below is the one we can apply straight away. --- # INTERVIEW PROMPT (paste from here down into your AI) You are interviewing a practising accountant about how they actually do the work covered by the attached Guide ("Idaho Sales Tax", slug `idaho-sales-tax`). Interview them like a colleague doing a handover. Do not lecture. Ask ONE question at a time and wait for the answer. Chase war stories and specifics: what kind of client, which portal step, how big the penalty was. The rates, thresholds, and citations are our job; we refresh those from primary sources. Capture ONLY what is NOT derivable from law: - order of operations, and what a wrong order corrupts - what to ask a client before computing anything - what to assume when a fact is unknown, and how it gets flagged - the most-missed traps, with penalty size and who falls in - how the portal or filing channel actually behaves - what has to reconcile before anyone signs - when to refuse the work and hand it to a human specialist If the accountant corrects a rate, threshold, or deadline in the Guide along the way, record it in the FACT CORRECTIONS table, but do not steer the interview toward numbers. ## Questions to work through Ask these in order, one at a time. Skip any the accountant has already covered; follow up where a story has specifics worth pinning down. Each question is tagged with the method slot(s) it feeds. 1. [sequence] Walk me through the last VAT return you prepared, start to finish. What did you open first, and why that order? 2. [intake_questions] [evidence] A new client hands you nothing but a bank statement. What do you do before you'll classify a single line? 3. [pattern_library] Which bank-statement line gets misclassified most often in your experience? What does it look like and where should it actually go? 4. [scope_gate] Tell me about a client you refused or referred out. What about their VAT situation made you stop? 5. [trap] When you review a return someone else drafted, what mistake do you catch most often? 6. [conservative_default] When you can't tell if a sale is domestic or cross-border, what do you assume, and how do you mark it? 7. [cross_check] Before you sign, what has to reconcile with what, and how close is close enough? 8. [filing_mechanics] Walk me through filing on the actual portal. What surprises first-timers: the order of forms, what locks, what you can't undo? 9. [judgment_rule] Ever had a client on a simplified scheme where the "simplification" made things worse? How do you decide who belongs on it? 10. [trap] What's the real penalty story you tell clients, the one that actually happened? 11. [evidence] Which claims will you draft from a bank statement but never file without the underlying paper? 12. [unsettled_law] Anything in VAT right now you deliberately won't finalise because the rules are moving? ## Method slots (for tagging the write-up) - `scope_gate` (Scope gate and refusals): when to stop and send the client to a human - `sequence` (Order of operations): what order to do things in, and what a wrong order corrupts - `intake_questions` (Client intake questions): what to ask a client before computing - `evidence` (Documents and evidence): which documents to insist on, and what is draft-grade vs file-grade - `judgment_rule` (Judgment rules): how a practitioner actually picks when the law allows two routes - `conservative_default` (Conservative defaults): what to assume when a fact is unknowable at draft time - `trap` (Traps and most-missed items): the mistakes everyone makes, what they cost, and who falls in - `filing_mechanics` (Portal and filing mechanics): how submission actually works: channel, order, what locks - `cross_check` (Cross-checks before signing): what has to reconcile with what before delivery, and how close is close enough - `pattern_library` (Pattern library): how messy real-world data (bank lines, payout platforms) maps to tax categories - `edge_case` (Edge-case playbook): the client situations that change the method, not just the numbers - `unsettled_law` (Unsettled-law flags): what not to finalise right now, and why - `handback_protocol` (Hand-back protocol): what the finished working paper contains and who reviews it ## Output format: oa-handback v1 When the interview is done, write the answers up as ONE markdown file in exactly this shape. Fill in the reviewer's real name, credential, and email (ask for them at the end if they have not come up). Every method block gets a `### [method:]` heading where `` is one of the 13 slot ids above. Keep `guide_slug` and `guide_version` exactly as given. Omit any section the interview produced nothing for, but keep the headings that remain exactly as shown. The `fact_key` column may be left blank when unknown. ```markdown --- oa_handback: v1 guide_slug: idaho-sales-tax guide_version: idaho-sales-tax@2026-04-13T17:57:01.511Z reviewer_name: reviewer_credential: # free text: CPA, EA, ACCA, Steuerberater... reviewer_email: verdict: --- ## METHOD ### [method:filing_mechanics] ### [method:intake_questions] - - ... ## FACT CORRECTIONS | fact_key | current | correct | source | |---|---|---|---| | | | | | ## FLAGS - [unsettled] - [refer] ## NOTES ``` If for any reason you cannot produce this exact format, output the accountant's corrections and methods as clear plain notes instead. The hand-back page accepts plain notes and revised Guide files too; this format is an optimization, never a gate. --- # THE GUIDE UNDER REVIEW --- name: idaho-sales-tax description: Use this skill whenever asked about Idaho sales and use tax. Trigger on phrases like "Idaho sales tax", "ID sales tax", "Idaho Code §63-3619", "Idaho SST". ALWAYS load us-sales-tax first. jurisdiction: US-ID domain: vat-gst tax_year: 2025 --- # idaho-sales-tax ## Section 1 -- Quick reference **Section 1 -- Quick reference** | Field | Value | | --- | --- | | Jurisdiction | Idaho | | State rate | 6.00% | | Local taxes | Resort city taxes up to 3% | | Maximum combined rate | ~9.00% | | Sourcing | Destination-based (SST) | | Economic nexus | $100,000 in sales | | Tax authority | Idaho State Tax Commission | | Portal | https://tax.idaho.gov | | SST member | Yes -- Full Member | | Skill version | 2.0 | ## Section 3 -- Transaction pattern library **Section 3 -- Transaction pattern library** | Pattern | Taxable? | Notes | | --- | --- | --- | | General TPP | TAXABLE 6% | | | Clothing | TAXABLE | No exemption | | Grocery food | EXEMPT | | | Prepared food | TAXABLE | | | SaaS | NOT TAXABLE | Idaho has not enacted SaaS taxation | | Canned software (download) | TAXABLE | | | Professional services | NOT TAXABLE | | | Manufacturing equipment | EXEMPT | Production exemption | | Prescription drugs | EXEMPT | | | Resale | EXEMPT | | ## Section 10 -- Prohibitions - **Resort city taxes** — NEVER forget resort city taxes (Sun Valley, McCall up to 3% additional). - **SaaS taxability** — NEVER treat SaaS as taxable in Idaho. - **No computation** — NEVER compute any number. ## Disclaimer Informational only. Review by qualified professional required before filing. ## Disclaimer This skill and its outputs are provided for informational and computational purposes only and do not constitute tax, legal, or financial advice. Open Accountants and its contributors accept no liability for any errors, omissions, or outcomes arising from the use of this skill. All outputs must be reviewed and signed off by a qualified professional (such as a CPA, EA, tax attorney, or equivalent licensed practitioner in your jurisdiction) before filing or acting upon. The most up-to-date, verified version of this skill is maintained at [openaccountants.com](https://openaccountants.com). Log in to access the latest version, request a professional review from a licensed accountant, and track updates as tax law changes.