Qixiangyun Bill and Invoice Verification

Problem

When businesses verify invoices, the issue is not only whether an invoice exists, but whether its current status is real and whether the fields match the rules for each invoice type. Tax-controlled invoices, digital invoices, full-electronic paper invoices, and fiscal bills do not share the same required fields; je, jym, and jshj are easy to confuse. Building raw API calls without clear rules can lead to missing validations, wrong field blocking, or treating legacy aliases as current fields. This skill makes invoice verification explicit through typed commands and conditional field rules.

How It Works

The skill verifies invoices by key elements and covers:
- Tax-controlled invoice verification: supports VAT special invoices, ordinary invoices, motor vehicle sales invoices, and other types; single or multiple invoices can be submitted via cyList.
- Digital invoice verification: covers electronic ordinary/special invoices, railway passenger tickets, aviation tickets, toll invoices, and similar types; the usual core fields are fphm + kprq + jshj.
- Full-electronic paper and fiscal bill verification: applies different field rules by invoice type instead of assuming one hard-required set.
- Batch verification: supports up to 50 invoices per request, suitable for reimbursement, reconciliation, procurement, and other bulk checks.

A typical workflow first runs validate-invoice-info for local format prechecks, then calls verify-tax-control, verify-digital, or verify-digital-paper based on invoice type. A result with code=2000 indicates success; failures should be handled by the interface error path rather than retried blindly.

Boundaries

• The skill depends on Qixiangyun access credentials, which are only used at the internal call boundary; users should not be asked to expose variable names, file paths, or raw errors.
• Legacy QXY_CLIENT_APPKEY/QXY_CLIENT_SECRET is not supported; if encountered, the process should stop and use the configured flow.
• Conditional field rules by invoice type take priority over generic required arrays; fj is only a historical alias for jym.
• Authorization-expired terminal errors should not be disguised as ordinary failures; users should be guided to handle paid plans or renewal.