Ningmengyun Invoice Issuance and Bulk Invoicing

Problem

Invoice issuance often fails because of context, not raw API calls: the wrong sales enterprise, a buyer treated as an individual or organization, an invoice type that does not match the taxpayer profile, inconsistent amount, tax, discount, or quantity fields, duplicate submissions, or issuing before preview, login, and authentication are complete. Passing free-text or spreadsheet data directly to an API can produce missing USCC values, wrong invoice types, incorrect tax calculations, or repeated invoices.

How It Works

The skill turns invoicing into a short, auditable execution chain:

• Task classification: distinguishes new tasks from continuation tasks. If buyer, seller, invoice type, amount, tax rate, remarks, or file contents change, the agent rebuilds the input JSON and reruns checks.
• Input normalization: maps natural language or file content into a standard invoices[] structure. The root object carries the current sales uscc; each invoice has an explicit invoiceType; buyer type is recorded in purchaserInfo.isNaturePerson.
• Local validation and preview: runs preflight and batch invoice info checks, validates fields, queries candidate enterprise tax IDs, checks amount consistency, and generates a preview Markdown. Links and local paths are rendered as plain text.
• Confirmation and submission: only after the full preview is shown and the user explicitly confirms invoicing does it run the confirmation command. It checks duplicate content and login status before submission.
• Authentication and result polling: when required, it starts and verifies the invoice permission authentication workflow, then polls status and reports the actual result.

Boundaries

It fits invoicing workflows where an API key, workspace, and local CLI are available, including single invoices, batch invoicing, digital invoice issuance, blue-letter invoices, and result queries. It does not replace a finance system and does not bypass preflight, preview, confirmation, authentication, or duplicate prevention. Missing buyer USCC, ambiguous amount or unit price, unclear taxpayer status, permission errors, or login issues require explicit follow-up or stopping.