Preface¶
In financial and expense reimbursement auditing, a common practice is to open the National Tax Platform or third-party tools to verify invoices one by one, and then transcribe the results into Excel. When there are many invoices, field entry, format verification, and exception summarization take up a significant amount of time. If you want to submit key fields for multiple invoices at once in a conversation, allowing an Agent to perform format and logic pre-checks according to unified rules and output a ledger and an exception list, the community Skill “Batch Invoice Verification” (@user_70c2f807/batch-invoice-verification) on SkillHub provides a set of workflow guidelines based on SKILL.md, rather than a direct verification API connected to the tax system.
What is this¶
“Batch Invoice Verification” is an Agent Skill from the SkillHub community (community), categorized as professional. The current version is 1.0.0, published by user_70c2f807. The page indicates requires_api_key=false; no additional API Key configuration is required after installation.
The Skill’s positioning is: when users mention requirements such as invoice verification, batch ticket verification, or invoice ledgers, it guides the Agent to collect fields such as Invoice Code, Number, Date, Amount, and Verification Code, perform checks on format compliance and logical consistency, and batch generate ledgers and exception reports. The official description explicitly states: It cannot connect to the Tax Bureau online, and cannot replace the final authenticity determination of official channels; it is also not applicable to scenarios such as issuing invoices, reimbursement processes, tax declarations, or financial bookkeeping.
Core Functions¶
The following capabilities are derived from the Skill’s SKILL.md instructions, and the Agent executes them according to the documented steps:
- Format Validation: Compliance checks such as Invoice Code digit count and Number rules.
- Logic Validation: Whether the invoice date is reasonable, whether amounts are consistent, whether tax rates match the industry, etc.
- Suspicion Identification: Flags questionable or abnormal items against common fraud characteristics.
- Batch Ledger: Generates a standard ledger based on the list provided by the user, supporting summarization by month, type, or supplier.
- Exception Report: Distinguishes between normal, questionable, and abnormal, and provides tiered handling suggestions and statistical summaries.
The recommended maximum batch size is 100 invoices per session (the documentation suggests 50–100 to ensure the quality of item-by-item verification); if information is incomplete, it will request the completion of fields such as Code, Number, Date, Amount, and Verification Code.
Installation and Activation¶
The installation method provided on the official SkillHub page is: instruct the Agent to install the coordinate @user_70c2f807/batch-invoice-verification by following the SkillHub Installation Documentation.
If the skillhub CLI is already available locally, you can first confirm the version, then install it to the current Agent’s skills directory (if --dir is not specified, it defaults to ./skills/, which some clients may not load):
command -v skillhub && skillhub --version
If the CLI is not installed, you can use the official script to install it (the complete installation includes the CLI and default Skills):
curl -fsSL https://skillhub-1388575217.cos.ap-guangzhou.myqcloud.com/install/install.sh | bash
When installing this Skill, --dir needs to point to the skills directory recognized by the current environment, for example:
skillhub install @user_70c2f807/batch-invoice-verification --dir ~/.cursor/skills/
Other common paths (also from the SkillHub installation documentation): Claude Code uses ~/.claude/skills/; Codex uses ~/.codex/skills/ or .agents/skills/ under the project. After installation, restart or refresh according to your client’s requirements to load the Skill.
Typical Usage¶
Trigger words in the Skill documentation include: invoice verification, verify invoice, fake invoice, invoice scan, batch verification, invoice ledger, invoice QR code, etc. Below is a reproducible conversation direction consistent with the official “Quick Start” (you only need to replace the content with actual data):
-
Single Batch Verification
User: “Help me verify if this batch of invoices is real.”
The Agent will ask the user to provide the Invoice Code, Number, Date, Amount, and the last 6 digits of the Verification Code, etc., and then output a report following a four-step process (Collect info → Format & Logic check → Exception marking → Generate ledger). -
Batch Ledger Entry
User: “I have 50 invoices to enter into a ledger.”
After providing the list of invoice information, the Agent generates a standard ledger and marks suspicious points. -
Monthly Summary
User: “Help me organize this month’s invoice details.”
The Agent classifies and summarizes by dimensions such as type, date, and amount.
If the user requests “online verification,” the Skill requires the Agent to explain that it cannot connect directly to the tax system and suggest verifying via the State Taxation Administration official website, while still performing format and logic pre-checks.
The output structure is defined in the documentation as a verification report (containing verification summary, invoice ledger table, exception details, statistical analysis, etc.), emphasizing that every exception must be traceable to specific fields.
Applicable Scenarios and Notes¶
Who is it for
- Finance, administration, or R&D personnel who need to quickly organize fields for multiple invoices in a conversation and perform unified pre-checks.
- Teams that want to filter out invoices with obvious format or logic anomalies first, and then use official channels for a small number of suspicious items.
Limitations and Pitfalls
| Key Point | Description |
|---|---|
| No Official Online Verification | Cannot connect to the Tax Bureau; passing the check does not equal a real invoice, final judgment must go through official channels. |
| Depends on User Input | Complete key fields must be provided; ambiguous or missing fields need to be supplemented against the original. |
| Batch Upper Limit | It is recommended not to exceed 100 invoices per session; larger quantities should be split into batches. |
| Privacy | The documentation states that invoice information is not stored; when involving amounts and suppliers, desensitization is recommended. |
| Misuse | Do not use this Skill as an invoicing, reimbursement approval, tax reporting, or bookkeeping tool. |
The SkillHub page currently displays a rating of 100000 and 858 downloads (based on the page and crawled metadata).
Conclusion¶
“Batch Invoice Verification” consolidates field collection, format and logic pre-checks, ledgers, and exception lists for multiple invoices into a single Agent workflow, making it suitable as an auxiliary step before manual item-by-item verification. Final authenticity remains subject to official tax verification. For installation and details, see SkillHub:
- Skill Page: https://www.skillhub.cn/skills/user_70c2f807/batch-invoice-verification
- Coordinate Page: https://api.skillhub.cn/user_70c2f807/batch-invoice-verification