Qixiangyun Enterprise Tax Filing

Problem

Enterprise tax filing workflows often span multiple tax items, task states, and external login sessions. If engineers assemble raw API calls, persist login state, or expose tax authority credentials in logs or command arguments, they can end up with credential leaks, duplicate submissions, and hard-to-trace failures. This skill narrows enterprise tax filing to a controlled Qixiangyun MCP workflow, focusing on the handoff between preparation, execution, and post-filing verification, and on avoiding sensitive credentials in conversations, CLI arguments, or ordinary logs.

How It Works

The skill relies on QXY_API_KEY and the built-in agent_login session. When a business command is triggered for the first time, the script returns a one-time login_url. The Agent starts waitArgv in the background to wait for login completion, then resumes the original task with resumeArgv. Users only need to visit the login page; they should not provide a tax authority phone number, password, verification code, or login token.

Core calls are split into two layers:
- scripts/mcp_client.py: atomic calls for a single service and tool, such as listing services, inspecting tool schemas, and calling a specified tool.
- scripts/declaration_workflow.py: declaration workflows covering roster_entry, initialize_data, declaration_submission, pdf_download, declaration_query, and missing_declaration_check.

The workflow handles period fields, tax-item cycles, polling states, and PDF download results. Enterprise-level orchestration requires one login authorization to bind to one enterprise; multi-enterprise scenarios must be split by enterprise. Output should preserve the current script, module, service alias, tool name, key business parameters, aggOrgId, taskId, and businessStatus.

Boundaries

This skill is intended for the controlled Qixiangyun MCP path and should not fall back to raw curl, browser automation, or old login state when a script fails. The provided material explicitly lists BDA0610135 Individual Income Tax as a known unsupported item. Multi-tenant or cloud deployments should isolate --login-context-id and the login-flow directory, and avoid exposing raw session proofs, internal login context, or enterprise identifiers.