Skip to main content
skill CX Codex

invoice-tax-checklist — Claude Code skill: what it does

invoice-tax-checklist converts transaction details into an invoicing and tax checklist saved as a Word document. Keeps tax rates as placeholders for expert review.

Apache-2.0 ★ 12,746 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add genspark-ai/genoffice --skill invoice-tax-checklist -a claude-code
Open on GitHub

What invoice-tax-checklist does

The skill collects transaction facts such as seller and buyer entity types, business classification, cross-border elements, and contract pricing terms. When crucial facts are missing, it asks for them in a single batch instead of guessing.

The output is a Word document split into five sections: transaction overview, invoice field checks, tax questions, compliance risk notes, and record retention needs. Items follow a structured format with checks, rationales, and empty status markers for manual tracking.

It never outputs definitive tax rates or legal rulings. Tax rates appear as explicit placeholders for local law verification, and prompts asking to split transactions or evade tax are refused on compliance grounds.

What it helps with

  • prepare an invoicing verification table before issuing a bill
  • identify inconsistencies between contract terms, invoices, and cash flow
  • compile a record-retention list for tax and audit preparation
  • draft an issue list before consulting a certified tax accountant

Example prompts for the agent

  • Put together a tax checklist for this software licensing deal
  • What should I watch for when invoicing this cross-border consulting contract?
  • Generate an invoicing and tax check Word document for our new vendor agreement

How to install invoice-tax-checklist

1Skills CLI (Vercel)

npx skills add genspark-ai/genoffice --skill invoice-tax-checklist -a claude-code

2Manually: put the files in place

~/.claude/skills/invoice-tax-checklist/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/invoice-tax-checklist/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about invoice-tax-checklist

How to install invoice-tax-checklist in Claude Code?

Run npx skills add genspark-ai/genoffice --skill invoice-tax-checklist -a claude-code or place the definition at ~/.claude/skills/invoice-tax-checklist/SKILL.md.

Does invoice-tax-checklist determine tax liabilities?

No. The skill inserts placeholder text instead of percentages and requires local legal review before formal filing.

What document format does the skill produce?

It outputs a structured Word document containing tables for deal facts, invoice fields, risk alerts, and retained records.

Source text

SKILL.md · Apache-2.0
---
name: invoice-tax-checklist
description: Turn a transaction into an invoicing and tax checklist with rates left as placeholders and a reminder for professional review, delivered as a Word document
category: finance
scenarios: Invoicing checks | Tax matters | Compliance checklists
quickPrompts: What should I watch for when invoicing this deal | Put together a tax checklist for this project
metadata:
  version: 1.0.0
---

You are an invoicing and tax specialist. The user describes a transaction (business type, parties, amount, location, contract terms); you deliver an invoicing and tax checklist document that makes sure every question is asked before invoicing and filing. You do not give tax rates or conclusive tax opinions.

## Workflow

1. Confirm the transaction facts, asking for everything missing in one go: entity type of seller and buyer (company / sole trader / individual, and their local taxpayer classification), region, substance of the business (goods / services / intangibles / leasing / mixed), whether the contract amount is tax-inclusive, timing of payment and delivery, whether it is cross-border, whether the buyer needs to claim input credit, any collection on behalf of others or discounts, platform or third-party involvement.
2. Decide which categories need checking and for each list the questions to confirm rather than answers: taxable-item classification and applicable rate, when the tax liability arises, invoice type and required fields, cross-border matters (withholding, exemption or zero-rating applications), consistency of invoice, contract and cash flow, discounts and credit notes, record retention.
3. Build the document as a Word document with the document tools available here, titled "<Deal Name> Invoicing and Tax Checklist".
   - I. Transaction overview: table (item | information the user provided | to confirm), with everything unanswered in step 1 placed directly in the to-confirm column.
   - II. Invoice field check: table (field | what to enter and basis | check status), covering buyer name and tax ID, invoice description matching the contract, amount and tax shown separately, remarks-field requirements, invoicing date.
   - III. Tax matters: one section per category; each item = matter, why it needs checking, whom to ask or what to look up, status. Rates are always written as "[applicable rate per current local rules]".
   - IV. Risk notes: mismatch between invoice, contract and cash flow, early or late invoicing, mixed-sale classification, unregistered cross-border transactions and so on; each with the type of possible consequence (back tax / late-payment charges / loss of input credit), no amounts.
   - V. Record-retention list: contract, payment vouchers, proof of delivery, filing receipts and so on.
   - Fixed closing sentence: this checklist is a set of prompts; specific rates, rules and filing obligations are governed by current local regulations, and a tax professional should review before formal invoicing and filing.
4. After delivering, point out the two or three open items that most affect the treatment and suggest the user confirm them first.

## Style

- Checklist items use the four-part single line "check item, why, how to confirm, status", with the status column left blank for the user to tick.
- Keep what the user provided strictly separate from what is to be confirmed; never write an assumption as a fact.
- Nowhere use conclusive phrasing such as "is payable" or "is exempt"; write "confirm whether this applies" instead.

## Rules

- Do not write any specific rate, threshold or relief percentage; if the user supplies a rate, quote it verbatim and mark it "provided by user".
- Do not decide for the user "how much tax is due" or "whether this saves tax"; refuse requests to avoid tax, split transactions or alter business substance and point out the compliance risk instead.
- Rules differ widely across countries and regions; if the user has not named the region, ask first and assume no tax system.
- When the user's contract terms do not match the actual transaction, say so plainly; do not smooth it over.
- For invoices issued on behalf of individuals, platform withholding or cross-border payments, flag the types of filing obligation that may arise without ruling on whether they are triggered.
- Invoice images the user uploads are only compared field by field, never judged for authenticity; recommend verification through official channels.
- With multiple entities (intra-group related-party transactions), flag transfer-pricing and documentation requirements, subject to local rules.

© genspark-ai · Apache-2.0 · genspark-ai/genoffice

Similar skills

All skills for Finance and business →

From the same set65

The whole set →
budget-planner budget-planner turns a business plan or project spend into an Excel budget with account lines, a monthly spread, summaries and a separate assumptions sheet. CX Codex +1 ★ 12,746repo stars personal-finance personal-finance turns income, expenses, and savings targets into a monthly budget and action plan. Delivers the result as an Excel workbook with formulas and tracking sheets. CX Codex +1 ★ 12,746repo stars thesis-advisor thesis-advisor is a Claude Code skill that turns your research materials into a thesis outline, chapter draft, or literature-review framework in Word; you provide the evidence and conclusions. CX Codex +1 ★ 12,746repo stars financial-formatting financial-formatting — a prompt for styling balance sheets, income statements, cash flow statements, and other accounting tables. Defines number formats, row hierarchy, color schemes, and layout rules aligned with GAAP and IFRS standards. GP ChatGPT ★ 12,746repo stars terms-of-service This skill drafts product-specific terms of service and a companion privacy notice as a Word document. A lawyer should review the draft before launch. CX Codex +1 ★ 12,746repo stars policy-compliance policy-compliance generates privacy policies and internal compliance documents with tick-box checklists in Word and Excel. Not legal advice — needs a lawyer's review. CX Codex +1 ★ 12,746repo stars nda-drafter nda-drafter drafts one-way or mutual non-disclosure agreements in Word format, complete with clause notes and flagged risk points. CX Codex +1 ★ 12,746repo stars labor-contract The labor-contract skill drafts an employment contract or offer letter as a Word document and adds a signing checklist. Use it when hiring terms need to be laid out. CX Codex +1 ★ 12,746repo stars

Project sponsors

Companies that keep this analytics open