Qixiangyun Digital E-Invoice Issuance

Problem

In digital e-invoice workflows, agents often have to coordinate tax-authority login state, seller account context, tax classification codes, buyer details, invoice confirmation, and asynchronous result queries. Exposing raw tool parameters to users or relying on model memory for default product codes can cause incorrect invoices, cross-tenant confusion, or sensitive-data leakage.

How It Works

The skill centers on scripts/invoice_issuance_workflow.py and builds a resumable invoice-draft pipeline:
- One-time login: It creates a web login session through the Qixiangyun agent_login MCP service. After the user selects the enterprise account, the script validates nsrsbh, accountId, and aggOrgId, then issues a short-lived Agent Grant.
- Drafting and confirmation: It parses natural-language requirements, enriches buyer data through title lookup, queries product tax classifications via invoice_classification, and generates a confirmation_summary. Real invoice issuance happens only after explicit user confirmation.
- Results and red-letter correction: It supports invoice detail queries, PDF/OFD/XML download links, face-scan status checks, and red-letter correction after validating the original blue invoice.

Boundaries

The skill requires Qixiangyun API credentials and a valid tax-authority login state. Multi-tenant deployments must inject secrets at the platform boundary and isolate state directories. Write operations such as invoice issuance, red-letter correction, and login-session creation are not automatically replayed; success should not be claimed until an invoice number or document URL is returned.